From mailman-admin@ietf.org  Sat May  1 09:28: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 JAA13121
	for <ietf-archive@ietf.org>; Sat, 1 May 2004 09:28: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 1BJuXF-0002HQ-Dh
	for ietf-archive@ietf.org; Sat, 01 May 2004 09:28:05 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJuWQ-00025u-00
	for ietf-archive@ietf.org; Sat, 01 May 2004 09:27:15 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJuVa-0001uZ-00
	for ietf-archive@ietf.org; Sat, 01 May 2004 09:26:22 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJu7O-0008Ev-DV
	for ietf-archive@ietf.org; Sat, 01 May 2004 09:01:22 -0400
Date: Sat, 01 May 2004 09:01:22 -0400
Message-ID: <20040501130122.27207.99205.Mailman@www1.ietf.org>
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@www1.ietf.org
To: ietf-archive@ietf.org
X-No-Archive: yes
X-Ack: no
Sender: mailman-admin@ietf.org
Errors-To: mailman-admin@ietf.org
X-BeenThere: mailman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60

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

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

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

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


                              Note Well

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

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

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

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


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

Passwords for ietf-archive@ietf.org:

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

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


From mailman-bounces@mailman.isi.edu  Sat May  1 09:47: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 JAA15008
	for <ietf-archive@ietf.org>; Sat, 1 May 2004 09:47: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 1BJupk-0006K5-D5
	for ietf-archive@ietf.org; Sat, 01 May 2004 09:47:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BJuot-00067g-00
	for ietf-archive@ietf.org; Sat, 01 May 2004 09:46:20 -0400
Received: from gamma.isi.edu ([128.9.144.145])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BJuny-0005uo-00
	for ietf-archive@ietf.org; Sat, 01 May 2004 09:45:22 -0400
Received: from gamma.isi.edu (localhost [127.0.0.1])
	by gamma.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i41CKEi28765
	for <ietf-archive@ietf.org>; Sat, 1 May 2004 05:20:14 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: isi.edu mailing list memberships reminder
From: mailman-owner@ISI.EDU
To: ietf-archive@ietf.org
X-No-Archive: yes
Message-ID: <mailman.1914.1083413065.19997.mailman@mailman.isi.edu>
Date: Sat, 01 May 2004 05:04:25 -0700
Precedence: bulk
X-BeenThere: mailman@mailman.isi.edu
X-Mailman-Version: 2.1.4
List-Id: Mailman site list <mailman.mailman.isi.edu>
X-List-Administrivia: yes
Sender: mailman-bounces@mailman.isi.edu
Errors-To: mailman-bounces@mailman.isi.edu
X-ISI-4-29-7-MailScanner: Found to be clean
X-MailScanner-From: mailman-bounces@mailman.isi.edu
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=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 ietf-admin@ietf.org  Mon May  3 03:09:55 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA10955
	for <ietf-archive@ietf.org>; Mon, 3 May 2004 03:09:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BKXaN-0005uS-36
	for ietf-archive@ietf.org; Mon, 03 May 2004 03:09:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKXXb-0005NN-00
	for ietf-archive@ietf.org; Mon, 03 May 2004 03:07:06 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKXUu-0004so-00
	for ietf-archive@ietf.org; Mon, 03 May 2004 03:04:16 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKXJB-00026A-PX; Mon, 03 May 2004 02:52:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKXB6-00073s-F1
	for ietf@optimus.ietf.org; Mon, 03 May 2004 02:43: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 BAA24697
	for <ietf@ietf.org>; Mon, 3 May 2004 01:56: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 1BKWRM-0001M9-NV
	for ietf@ietf.org; Mon, 03 May 2004 01:56:32 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKWOf-0000tD-00
	for ietf@ietf.org; Mon, 03 May 2004 01:53:47 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKWLk-0000I6-00
	for ietf@ietf.org; Mon, 03 May 2004 01:50:44 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id 624E861B9F
	for <ietf@ietf.org>; Mon,  3 May 2004 07:50:15 +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 11180-05 for <ietf@ietf.org>;
 Mon,  3 May 2004 07:50:13 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id 01AE961B7D
	for <ietf@ietf.org>; Mon,  3 May 2004 07:50:12 +0200 (CEST)
Date: Sun, 02 May 2004 22:50:07 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: ietf@ietf.org
Subject: Please note this update: IETF mission statement
Message-ID: <364559378.1083538207@[192.168.1.63]>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: multipart/mixed;
 boundary="==========7C6365F4BCB9FE84F7F8=========="
X-Virus-Scanned: by amavisd-new at alvestrand.no
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,MIME_SUSPECT_NAME 
	autolearn=no version=2.60

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

I have tried to incorporate the extremely useful feedback I got on this 
list and from the Korea plenary.

I hope this is ready to send to IETF-wide Last Call.
This is your chance to get at it early :-)

Take care,

                Harald


---------- Forwarded Message ----------
Date: 30. april 2004 15:44 -0400
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D ACTION:draft-alvestrand-ietf-mission-01.txt

A New Internet-Draft is available from the on-line Internet-Drafts
directories.


	Title		: A Mission Statement for the IETF
	Author(s)	: H. Alvestrand
	Filename	: draft-alvestrand-ietf-mission-01.txt
	Pages		: 16
	Date		: 2004-4-30
	
This memo gives a mission statement for the IETF, tries to define the
   terms used in the statement sufficiently to make the mission
   statement understandable and useful, argues why the IETF needs a
   mission statement, and tries to capture some of the debate that led
   to this point.


   The appendix giving the debate is intended to be deleted when the RFC
   is published; it is only given here as a reference and a thank-you
   note

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

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of the
message.   You can also visit
https://www1.ietf.org/mailman/listinfo/I-D-announce  to change your
subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-alvestrand-ietf-mission-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-alvestrand-ietf-mission-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

---------- End Forwarded Message ----------




--==========7C6365F4BCB9FE84F7F8==========
Content-Type: message/rfc822;
 name="I-D ACTION:draft-alvestrand-ietf-mission-01.txt"

Return-Path: <cyrus@eikenes.alvestrand.no>
Received: from eikenes.alvestrand.no ([unix socket])
	by eikenes.alvestrand.no (Cyrus v2.1.11-Mandrake-RPM-2.1.11-1mdk) with LMTP; Fri, 30 Apr 2004 22:29:03 +0200
X-Sieve: CMU Sieve 2.2
Return-Path: <i-d-announce-admin@ietf.org>
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id 6AF99621B8
	for <harald@alvestrand.no>; Fri, 30 Apr 2004 22:29:03 +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 13871-07 for <harald@alvestrand.no>;
 Fri, 30 Apr 2004 22:29:02 +0200 (CEST)
Received: from optimus.ietf.org (optimus22.ietf.org [132.151.6.22])
	by eikenes.alvestrand.no (Postfix) with ESMTP id D2E0F61B89
	for <harald@alvestrand.no>; Fri, 30 Apr 2004 22:28:58 +0200 (CEST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJe7F-0003Mg-4u; Fri, 30 Apr 2004 15:56:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJdw9-000796-GF
	for i-d-announce@optimus.ietf.org; Fri, 30 Apr 2004 15:44:41 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26206
	for <i-d-announce@ietf.org>; Fri, 30 Apr 2004 15:44:37 -0400 (EDT)
Message-Id: <200404301944.PAA26206@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-alvestrand-ietf-mission-01.txt
Date: Fri, 30 Apr 2004 15:44:37 -0400
Sender: i-d-announce-admin@ietf.org
Errors-To: i-d-announce-admin@ietf.org
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
Reply-To: internet-drafts@ietf.org
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=unsubscribe>
List-Id: <i-d-announce.ietf.org>
List-Post: <mailto:i-d-announce@ietf.org>
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=subscribe>
X-Virus-Scanned: by amavisd-new at alvestrand.no

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: A Mission Statement for the IETF
	Author(s)	: H. Alvestrand
	Filename	: draft-alvestrand-ietf-mission-01.txt
	Pages		: 16
	Date		: 2004-4-30
	
This memo gives a mission statement for the IETF, tries to define the
   terms used in the statement sufficiently to make the mission
   statement understandable and useful, argues why the IETF needs a
   mission statement, and tries to capture some of the debate that led
   to this point.


   The appendix giving the debate is intended to be deleted when the RFC
   is published; it is only given here as a reference and a thank-you
   note

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-alvestrand-ietf-mission-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-alvestrand-ietf-mission-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2004-4-30160340.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-alvestrand-ietf-mission-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-alvestrand-ietf-mission-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2004-4-30160340.I-D@ietf.org>

--OtherAccess--

--NextPart--



_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce


--==========7C6365F4BCB9FE84F7F8==========--


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


From exim@www1.ietf.org  Mon May  3 03:11: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 DAA11001
	for <ietf-archive@odin.ietf.org>; Mon, 3 May 2004 03:11: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 1BKXUy-0006lJ-1n
	for ietf-archive@odin.ietf.org; Mon, 03 May 2004 03:04:20 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4374KI2025994
	for ietf-archive@odin.ietf.org; Mon, 3 May 2004 03:04:20 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKXJB-00026A-PX; Mon, 03 May 2004 02:52:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKXB6-00073s-F1
	for ietf@optimus.ietf.org; Mon, 03 May 2004 02:43: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 BAA24697
	for <ietf@ietf.org>; Mon, 3 May 2004 01:56: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 1BKWRM-0001M9-NV
	for ietf@ietf.org; Mon, 03 May 2004 01:56:32 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKWOf-0000tD-00
	for ietf@ietf.org; Mon, 03 May 2004 01:53:47 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKWLk-0000I6-00
	for ietf@ietf.org; Mon, 03 May 2004 01:50:44 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id 624E861B9F
	for <ietf@ietf.org>; Mon,  3 May 2004 07:50:15 +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 11180-05 for <ietf@ietf.org>;
 Mon,  3 May 2004 07:50:13 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id 01AE961B7D
	for <ietf@ietf.org>; Mon,  3 May 2004 07:50:12 +0200 (CEST)
Date: Sun, 02 May 2004 22:50:07 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: ietf@ietf.org
Subject: Please note this update: IETF mission statement
Message-ID: <364559378.1083538207@[192.168.1.63]>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: multipart/mixed;
 boundary="==========7C6365F4BCB9FE84F7F8=========="
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.1 required=5.0 tests=AWL,MIME_SUSPECT_NAME 
	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>

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

I have tried to incorporate the extremely useful feedback I got on this 
list and from the Korea plenary.

I hope this is ready to send to IETF-wide Last Call.
This is your chance to get at it early :-)

Take care,

                Harald


---------- Forwarded Message ----------
Date: 30. april 2004 15:44 -0400
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D ACTION:draft-alvestrand-ietf-mission-01.txt

A New Internet-Draft is available from the on-line Internet-Drafts
directories.


	Title		: A Mission Statement for the IETF
	Author(s)	: H. Alvestrand
	Filename	: draft-alvestrand-ietf-mission-01.txt
	Pages		: 16
	Date		: 2004-4-30
	
This memo gives a mission statement for the IETF, tries to define the
   terms used in the statement sufficiently to make the mission
   statement understandable and useful, argues why the IETF needs a
   mission statement, and tries to capture some of the debate that led
   to this point.


   The appendix giving the debate is intended to be deleted when the RFC
   is published; it is only given here as a reference and a thank-you
   note

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

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of the
message.   You can also visit
https://www1.ietf.org/mailman/listinfo/I-D-announce  to change your
subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-alvestrand-ietf-mission-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-alvestrand-ietf-mission-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

---------- End Forwarded Message ----------




--==========7C6365F4BCB9FE84F7F8==========
Content-Type: message/rfc822;
 name="I-D ACTION:draft-alvestrand-ietf-mission-01.txt"

Return-Path: <cyrus@eikenes.alvestrand.no>
Received: from eikenes.alvestrand.no ([unix socket])
	by eikenes.alvestrand.no (Cyrus v2.1.11-Mandrake-RPM-2.1.11-1mdk) with LMTP; Fri, 30 Apr 2004 22:29:03 +0200
X-Sieve: CMU Sieve 2.2
Return-Path: <i-d-announce-admin@ietf.org>
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id 6AF99621B8
	for <harald@alvestrand.no>; Fri, 30 Apr 2004 22:29:03 +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 13871-07 for <harald@alvestrand.no>;
 Fri, 30 Apr 2004 22:29:02 +0200 (CEST)
Received: from optimus.ietf.org (optimus22.ietf.org [132.151.6.22])
	by eikenes.alvestrand.no (Postfix) with ESMTP id D2E0F61B89
	for <harald@alvestrand.no>; Fri, 30 Apr 2004 22:28:58 +0200 (CEST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJe7F-0003Mg-4u; Fri, 30 Apr 2004 15:56:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BJdw9-000796-GF
	for i-d-announce@optimus.ietf.org; Fri, 30 Apr 2004 15:44:41 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26206
	for <i-d-announce@ietf.org>; Fri, 30 Apr 2004 15:44:37 -0400 (EDT)
Message-Id: <200404301944.PAA26206@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-alvestrand-ietf-mission-01.txt
Date: Fri, 30 Apr 2004 15:44:37 -0400
Sender: i-d-announce-admin@ietf.org
Errors-To: i-d-announce-admin@ietf.org
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
Reply-To: internet-drafts@ietf.org
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=unsubscribe>
List-Id: <i-d-announce.ietf.org>
List-Post: <mailto:i-d-announce@ietf.org>
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=subscribe>
X-Virus-Scanned: by amavisd-new at alvestrand.no

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: A Mission Statement for the IETF
	Author(s)	: H. Alvestrand
	Filename	: draft-alvestrand-ietf-mission-01.txt
	Pages		: 16
	Date		: 2004-4-30
	
This memo gives a mission statement for the IETF, tries to define the
   terms used in the statement sufficiently to make the mission
   statement understandable and useful, argues why the IETF needs a
   mission statement, and tries to capture some of the debate that led
   to this point.


   The appendix giving the debate is intended to be deleted when the RFC
   is published; it is only given here as a reference and a thank-you
   note

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-alvestrand-ietf-mission-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-alvestrand-ietf-mission-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2004-4-30160340.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-alvestrand-ietf-mission-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-alvestrand-ietf-mission-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2004-4-30160340.I-D@ietf.org>

--OtherAccess--

--NextPart--



_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce


--==========7C6365F4BCB9FE84F7F8==========--


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



From ietf-admin@ietf.org  Mon May  3 05:48: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 FAA17521
	for <ietf-archive@ietf.org>; Mon, 3 May 2004 05:48: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 1BKa48-0000IX-Tr
	for ietf-archive@ietf.org; Mon, 03 May 2004 05:48:49 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKa05-0007U6-00
	for ietf-archive@ietf.org; Mon, 03 May 2004 05:44:39 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKZwb-0006ov-00
	for ietf-archive@ietf.org; Mon, 03 May 2004 05:41:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKZos-0002xQ-P0; Mon, 03 May 2004 05:33:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKZlG-00014u-L3
	for ietf@optimus.ietf.org; Mon, 03 May 2004 05:29: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 FAA16746
	for <ietf@ietf.org>; Mon, 3 May 2004 05:29: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 1BKZlD-0004sU-96
	for ietf@ietf.org; Mon, 03 May 2004 05:29:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKZhw-0004Jh-00
	for ietf@ietf.org; Mon, 03 May 2004 05:25:54 -0400
Received: from 251.cust42.nsw.dsl.ozemail.com.au ([203.103.121.251] helo=nosense.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKZeG-0003XY-00
	for ietf@ietf.org; Mon, 03 May 2004 05:22:04 -0400
Received: from Dupy2.nosense.org (localhost.localdomain [127.0.0.1])
	by nosense.org (Postfix) with SMTP
	id 8FDF73F02A; Mon,  3 May 2004 18:54:07 +0930 (CST)
Date: Mon, 3 May 2004 18:54:07 +0930
From: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
Cc: ietf@ietf.org
Subject: Re: Please note this update: IETF mission statement
Message-Id: <20040503185407.72b79956.ietf@130c04165a5b40404e4440445758487a.nosense.org>
In-Reply-To: <364559378.1083538207@[192.168.1.63]>
References: <364559378.1083538207@[192.168.1.63]>
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 Harald,

On Sun, 02 May 2004 22:50:07 -0700
Harald Tveit Alvestrand <harald@alvestrand.no> wrote:

> I have tried to incorporate the extremely useful feedback I got
> on this list and from the Korea plenary.
> 
> I hope this is ready to send to IETF-wide Last Call.
> This is your chance to get at it early :-)
> 

I haven't been all that involved in the IETF to have a strong
opinion on the draft. That being said, it sounds good.

Regarding deleting the appendix, I'd suggest not doing so, as I
think it fits the "Relevant" clause, namely :

"Note that it does not mean "correct" or "positive" - a
report of an experiment that failed, or a specification that
clearly says why you should not use it in a given situation,
can be highly relevant - for deciding what NOT to do."

I think including the possible mission statements that weren't
adequate will help further clarify the one that is.

If the appendix is retained, and it isn't too much effort,
expanded explanations of why the other mission statement
candidates weren't satisfactory or adequate may be of some value.

Regards,
Mark.


> Take care,
> 
>                 Harald
> 
> 
> ---------- Forwarded Message ----------
> Date: 30. april 2004 15:44 -0400
> From: Internet-Drafts@ietf.org
> To: i-d-announce@ietf.org
> Subject: I-D ACTION:draft-alvestrand-ietf-mission-01.txt
> 
> A New Internet-Draft is available from the on-line
> Internet-Drafts directories.
> 
> 
> 	Title		: A Mission Statement for the IETF
> 	Author(s)	: H. Alvestrand
> 	Filename	: draft-alvestrand-ietf-mission-01.txt
> 	Pages		: 16
> 	Date		: 2004-4-30
> 	
> This memo gives a mission statement for the IETF, tries to
> define the
>    terms used in the statement sufficiently to make the mission
>    statement understandable and useful, argues why the IETF
>    needs a mission statement, and tries to capture some of the
>    debate that led to this point.
> 
> 
>    The appendix giving the debate is intended to be deleted
>    when the RFC is published; it is only given here as a
>    reference and a thank-you note
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-alvestrand-ietf-mission-01.txt
> 
> To remove yourself from the I-D Announcement list, send a
> message to i-d-announce-request@ietf.org with the word
> unsubscribe in the body of the message.   You can also visit
> https://www1.ietf.org/mailman/listinfo/I-D-announce  to change
> your subscription settings.
> 
> 
> Internet-Drafts are also available by anonymous FTP. Login with
> the username"anonymous" and a password of your e-mail address.
> After logging in, type "cd internet-drafts" and then
> 	"get draft-alvestrand-ietf-mission-01.txt".
> 
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> 
> Internet-Drafts can also be obtained by e-mail.
> 
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE
> 	/internet-drafts/draft-alvestrand-ietf-mission-01.txt".
> 	
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use
> 	this feature, insert the command "ENCODING mime" before
> 	the "FILE" command.  To decode the response(s), you will
> 	need "munpack" or a MIME-compliant mail reader. 
> 	Different MIME-compliant mail readers exhibit different
> 	behavior, especially when dealing with"multipart" MIME
> 	messages (i.e. documents which have been split up into
> 	multiple messages), so check your local documentation on
> 	how to manipulate these messages.
> 		
> 		
> Below is the data which will enable a MIME compliant mail
> reader implementation to automatically retrieve the ASCII
> version of the Internet-Draft.
> 
> ---------- End Forwarded Message ----------
> 
> 
> 
> 

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


From exim@www1.ietf.org  Mon May  3 05:49:09 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 FAA17561
	for <ietf-archive@odin.ietf.org>; Mon, 3 May 2004 05:49: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 1BKZwc-0005xG-9G
	for ietf-archive@odin.ietf.org; Mon, 03 May 2004 05:41:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i439f2fq022884
	for ietf-archive@odin.ietf.org; Mon, 3 May 2004 05:41:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKZos-0002xQ-P0; Mon, 03 May 2004 05:33:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKZlG-00014u-L3
	for ietf@optimus.ietf.org; Mon, 03 May 2004 05:29: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 FAA16746
	for <ietf@ietf.org>; Mon, 3 May 2004 05:29: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 1BKZlD-0004sU-96
	for ietf@ietf.org; Mon, 03 May 2004 05:29:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKZhw-0004Jh-00
	for ietf@ietf.org; Mon, 03 May 2004 05:25:54 -0400
Received: from 251.cust42.nsw.dsl.ozemail.com.au ([203.103.121.251] helo=nosense.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKZeG-0003XY-00
	for ietf@ietf.org; Mon, 03 May 2004 05:22:04 -0400
Received: from Dupy2.nosense.org (localhost.localdomain [127.0.0.1])
	by nosense.org (Postfix) with SMTP
	id 8FDF73F02A; Mon,  3 May 2004 18:54:07 +0930 (CST)
Date: Mon, 3 May 2004 18:54:07 +0930
From: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
Cc: ietf@ietf.org
Subject: Re: Please note this update: IETF mission statement
Message-Id: <20040503185407.72b79956.ietf@130c04165a5b40404e4440445758487a.nosense.org>
In-Reply-To: <364559378.1083538207@[192.168.1.63]>
References: <364559378.1083538207@[192.168.1.63]>
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 Harald,

On Sun, 02 May 2004 22:50:07 -0700
Harald Tveit Alvestrand <harald@alvestrand.no> wrote:

> I have tried to incorporate the extremely useful feedback I got
> on this list and from the Korea plenary.
> 
> I hope this is ready to send to IETF-wide Last Call.
> This is your chance to get at it early :-)
> 

I haven't been all that involved in the IETF to have a strong
opinion on the draft. That being said, it sounds good.

Regarding deleting the appendix, I'd suggest not doing so, as I
think it fits the "Relevant" clause, namely :

"Note that it does not mean "correct" or "positive" - a
report of an experiment that failed, or a specification that
clearly says why you should not use it in a given situation,
can be highly relevant - for deciding what NOT to do."

I think including the possible mission statements that weren't
adequate will help further clarify the one that is.

If the appendix is retained, and it isn't too much effort,
expanded explanations of why the other mission statement
candidates weren't satisfactory or adequate may be of some value.

Regards,
Mark.


> Take care,
> 
>                 Harald
> 
> 
> ---------- Forwarded Message ----------
> Date: 30. april 2004 15:44 -0400
> From: Internet-Drafts@ietf.org
> To: i-d-announce@ietf.org
> Subject: I-D ACTION:draft-alvestrand-ietf-mission-01.txt
> 
> A New Internet-Draft is available from the on-line
> Internet-Drafts directories.
> 
> 
> 	Title		: A Mission Statement for the IETF
> 	Author(s)	: H. Alvestrand
> 	Filename	: draft-alvestrand-ietf-mission-01.txt
> 	Pages		: 16
> 	Date		: 2004-4-30
> 	
> This memo gives a mission statement for the IETF, tries to
> define the
>    terms used in the statement sufficiently to make the mission
>    statement understandable and useful, argues why the IETF
>    needs a mission statement, and tries to capture some of the
>    debate that led to this point.
> 
> 
>    The appendix giving the debate is intended to be deleted
>    when the RFC is published; it is only given here as a
>    reference and a thank-you note
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-alvestrand-ietf-mission-01.txt
> 
> To remove yourself from the I-D Announcement list, send a
> message to i-d-announce-request@ietf.org with the word
> unsubscribe in the body of the message.   You can also visit
> https://www1.ietf.org/mailman/listinfo/I-D-announce  to change
> your subscription settings.
> 
> 
> Internet-Drafts are also available by anonymous FTP. Login with
> the username"anonymous" and a password of your e-mail address.
> After logging in, type "cd internet-drafts" and then
> 	"get draft-alvestrand-ietf-mission-01.txt".
> 
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> 
> Internet-Drafts can also be obtained by e-mail.
> 
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE
> 	/internet-drafts/draft-alvestrand-ietf-mission-01.txt".
> 	
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use
> 	this feature, insert the command "ENCODING mime" before
> 	the "FILE" command.  To decode the response(s), you will
> 	need "munpack" or a MIME-compliant mail reader. 
> 	Different MIME-compliant mail readers exhibit different
> 	behavior, especially when dealing with"multipart" MIME
> 	messages (i.e. documents which have been split up into
> 	multiple messages), so check your local documentation on
> 	how to manipulate these messages.
> 		
> 		
> Below is the data which will enable a MIME compliant mail
> reader implementation to automatically retrieve the ASCII
> version of the Internet-Draft.
> 
> ---------- End Forwarded Message ----------
> 
> 
> 
> 

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



From exim@www1.ietf.org  Mon May  3 10:11:12 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 KAA02372
	for <ietf-archive@odin.ietf.org>; Mon, 3 May 2004 10:11: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 1BKdsT-0002gv-Nx
	for ietf-archive@odin.ietf.org; Mon, 03 May 2004 09:53:10 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i43Dr15e010345
	for ietf-archive@odin.ietf.org; Mon, 3 May 2004 09:53:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKdjn-0007z5-0O; Mon, 03 May 2004 09:44:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKd6S-0007Uq-Sr
	for ietf@optimus.ietf.org; Mon, 03 May 2004 09:03: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 JAA26635
	for <ietf@ietf.org>; Mon, 3 May 2004 09:03: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 1BKd6R-0000MZ-7E
	for ietf@ietf.org; Mon, 03 May 2004 09:03:23 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKd1z-0007UE-00
	for ietf@ietf.org; Mon, 03 May 2004 08:58:48 -0400
Received: from mailhost.jlc.net ([199.201.159.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKcwZ-0006eg-00
	for ietf@ietf.org; Mon, 03 May 2004 08:53:12 -0400
Received: by mailhost.jlc.net (Postfix, from userid 104)
	id 7AD91E0718; Mon,  3 May 2004 08:53:03 -0400 (EDT)
Date: Mon, 3 May 2004 08:53:03 -0400
From: John Leslie <john@jlc.net>
To: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
Cc: Harald Tveit Alvestrand <harald@alvestrand.no>, ietf@ietf.org
Subject: Re: Please note this update: IETF mission statement
Message-ID: <20040503125303.GA12377@verdi>
References: <364559378.1083538207@[192.168.1.63]> <20040503185407.72b79956.ietf@130c04165a5b40404e4440445758487a.nosense.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040503185407.72b79956.ietf@130c04165a5b40404e4440445758487a.nosense.org>
User-Agent: Mutt/1.4.1i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=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>

Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org> wrote:
> Harald Tveit Alvestrand <harald@alvestrand.no> wrote:
> 
>> http://www.ietf.org/internet-drafts/draft-alvestrand-ietf-mission-01.txt
> 
> I haven't been all that involved in the IETF to have a strong
> opinion on the draft. That being said, it sounds good.

   Harald (et al) should be commended for this work.

> Regarding deleting the appendix, I'd suggest not doing so, as I
> think it fits the "Relevant" clause, namely :
> 
> "Note that it does not mean "correct" or "positive" - a
> report of an experiment that failed, or a specification that
> clearly says why you should not use it in a given situation,
> can be highly relevant - for deciding what NOT to do."
> 
> I think including the possible mission statements that weren't
> adequate will help further clarify the one that is.

   I must disagree with Mark and agree with Harald. Inclusion of
Appendix A in _this_ document would detract from the sense of closure,
and give the impresssion that the issues it mentions are still open.

> If the appendix is retained, and it isn't too much effort,
> expanded explanations of why the other mission statement
> candidates weren't satisfactory or adequate may be of some value.
 
  I'd be happy to see a separate document describing the process of
reaching this statement of mission.

====
A Few Nits:

4.1
" 
" We embrace technical concepts such as decentralized control, edge-user
" empowerment and sharing of resources, because those concepts resonate
" with the core values of the IETF community. These concepts have little
" to do with the technology that's possible, and much to do with the
" technology that we choose to create.

   The language here is very good -- in fact, commendable.

   But the aim is a trifle off.

   Whether we "embrace" "decentralized control" is orthogonal to our
mission. We have designed protocols which work well in the presence of
decentralized control, not because we "embrace" anything, but because
we believed it to be impossible to reach the global scope of today's
Internet _without_ decentralized control. I quite agree that it belongs
in our mission statement.

   On the other hand, "edge-user empowerment" is a different animal.
It is _not_ necessary to the existence of the Internet. And it invites
misinterpretation. There's limited consensus today what the "edge"
means. And "empowerment", though it _means_ delegation towards the
edge, is used in so many different ways today that it's semantically
empty.

   I suggest eliminating "edge-user empowerment". What I believe
Harald (et al) meant by this is to extend the "decentralized control"
out to the very edge, enabling users at the (loosely-defined) edge
to have sufficient control of their communications to explore new
uses for the Internet. I think we can trust users to work in that
direction without needing a statement here.

   With this in mind, a possible wording would be:

+ The concept of decentralized control, initially necessary in order
+ to grow the Internet to global scale, has become a core value to
+ the IETF community. Similarly, the concept of sharing resources
+ without letting ourselves get bogged down in accounting for them
+ has become a core value. We will continue to choose to create
+ technologies that resonate with our core values.

" In attempting to resolve this question, perhaps the fairest balance
" is struck by this formulation: "protocols and practices for which
" secure and scalable implementations are expected to have wide
" deployment and interoperation on the Internet, or to form part of the
" infrastructure of the Internet."

   It's not clear what "question" is being discussed. I'm pretty sure
Harald means the question of whether particular work is included
within the scope of the IETF mission; but this has gotten lost in
context.

   Thus I suggest rewording, perhaps something like:

+ In deciding whether particular work is "in-scope" for the IETF, we
+ try to concentrate on "protocols and practices for which secure and
+ scalable implementations are expected to have wide deployment and
+ interoperation on the Internet, or to form part of the infrastructure
+ of the Internet."

4.2
" 
" The IETF has traditionally been a community for both experimentation
" with things that are not fully understood, standardization of
" protocols for which some understanding has been reached, and
" publication of (and refinement of) protocols originally specified
" outside the IETF process.

   Alas, "both" can only connect _two_ choices, and we have at least
three here. I suggest eliminating the word "both".

" In deciding whether or not these activities should be done within the
" IETF, one should not chiefly look at the type of activity, but the
" potential benefit to the Internet - an experiment that yields
" information about the fact that an approach is not viable might be as
" worthy of publication as a standard that is technically competent,
" but only useful in a few special cases.

   "As worthy of publication as a standard" leads the reader to stumble
over _why_ the failed experiment should be published "as a standard".
(Hey, I warned you I'm picking nits!)

   I suggest some shuffling, perhaps like:

+ The type of activity shouldn't drive the decision of whether an
+ activity belongs within the IETF - an Informational RFC describing
+ a failed experiment, showing why that approach is not viable, might
+ be of greater benefit to the Internet than a Standards-track RFC
+ useful in only a few special cases.

====
6. Acknowledgments

   Harald asks:
" 
" Given how incomplete this section necessarily is, should it just say
" "None mentioned, none forgotten"?

   No, it shouldn't (though the temptation is strong). An apology to
those you forgot to mention is appropriate, but you must try to come
up with a list of the most important contributors.

   The list in the draft looks good to me.

--
John Leslie <john@jlc.net>

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



From exim@www1.ietf.org  Mon May  3 10:12:36 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 KAA02573
	for <ietf-archive@odin.ietf.org>; Mon, 3 May 2004 10:12: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 1BKe9n-0003Qb-IV
	for ietf-archive@odin.ietf.org; Mon, 03 May 2004 10:10:55 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i43EAtHG013178
	for ietf-archive@odin.ietf.org; Mon, 3 May 2004 10:10:55 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKdrc-0002Jc-OT; Mon, 03 May 2004 09:52:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKdiw-00076A-DR
	for ietf@optimus.ietf.org; Mon, 03 May 2004 09:43: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 JAA28994
	for <ietf@ietf.org>; Mon, 3 May 2004 09:43: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 1BKdiu-0006S6-EF
	for ietf@ietf.org; Mon, 03 May 2004 09:43:08 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKdeQ-0005ar-00
	for ietf@ietf.org; Mon, 03 May 2004 09:38:31 -0400
Received: from 251.cust42.nsw.dsl.ozemail.com.au ([203.103.121.251] helo=nosense.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKdZT-0004o0-00
	for ietf@ietf.org; Mon, 03 May 2004 09:33:24 -0400
Received: from Dupy2.nosense.org (localhost.localdomain [127.0.0.1])
	by nosense.org (Postfix) with SMTP
	id E07163F02A; Mon,  3 May 2004 23:05:26 +0930 (CST)
Date: Mon, 3 May 2004 23:05:26 +0930
From: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
To: John Leslie <john@jlc.net>
Cc: harald@alvestrand.no, ietf@ietf.org
Subject: Re: Please note this update: IETF mission statement
Message-Id: <20040503230526.362dcf73.ietf@130c04165a5b40404e4440445758487a.nosense.org>
In-Reply-To: <20040503125303.GA12377@verdi>
References: <364559378.1083538207@[192.168.1.63]>
	<20040503185407.72b79956.ietf@130c04165a5b40404e4440445758487a.nosense.org>
	<20040503125303.GA12377@verdi>
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 John, Harald,

On Mon, 3 May 2004 08:53:03 -0400
John Leslie <john@jlc.net> wrote:

> Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
> wrote:
> > Harald Tveit Alvestrand <harald@alvestrand.no> wrote:
> > 
> >>
> >http://www.ietf.org/internet-drafts/draft-alvestrand-ietf-mis
> >sion-01.txt
> > 
> > I haven't been all that involved in the IETF to have a strong
> > opinion on the draft. That being said, it sounds good.
> 
>    Harald (et al) should be commended for this work.

Completely agree.

> 
> > Regarding deleting the appendix, I'd suggest not doing so, as
> > I think it fits the "Relevant" clause, namely :
> > 
> > "Note that it does not mean "correct" or "positive" - a
> > report of an experiment that failed, or a specification that
> > clearly says why you should not use it in a given situation,
> > can be highly relevant - for deciding what NOT to do."
> > 
> > I think including the possible mission statements that
> > weren't adequate will help further clarify the one that is.
> 
>    I must disagree with Mark and agree with Harald. Inclusion
>    of
> Appendix A in _this_ document would detract from the sense of
> closure, and give the impresssion that the issues it mentions
> are still open.
> 
> > If the appendix is retained, and it isn't too much effort,
> > expanded explanations of why the other mission statement
> > candidates weren't satisfactory or adequate may be of some
> > value.
>  
>   I'd be happy to see a separate document describing the
>   process of
> reaching this statement of mission.
> 

I'd be happy with this approach. I think sometimes preserving the
"whys" can be as useful as the "whats". ("Why ?" is one of my
favourite questions :-) )

Regards,
Mark.

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



From ietf-admin@ietf.org  Mon May  3 10:12: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 KAA02637
	for <ietf-archive@ietf.org>; Mon, 3 May 2004 10:12: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 1BKeBj-00034T-Sx
	for ietf-archive@ietf.org; Mon, 03 May 2004 10:12:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKe49-0001ry-00
	for ietf-archive@ietf.org; Mon, 03 May 2004 10:05:08 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKdsX-0000FG-00
	for ietf-archive@ietf.org; Mon, 03 May 2004 09:53:05 -0400
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BKdsV-0003ql-CR
	for ietf-archive@ietf.org; Mon, 03 May 2004 09:53:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKdjn-0007z5-0O; Mon, 03 May 2004 09:44:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKd6S-0007Uq-Sr
	for ietf@optimus.ietf.org; Mon, 03 May 2004 09:03: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 JAA26635
	for <ietf@ietf.org>; Mon, 3 May 2004 09:03: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 1BKd6R-0000MZ-7E
	for ietf@ietf.org; Mon, 03 May 2004 09:03:23 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKd1z-0007UE-00
	for ietf@ietf.org; Mon, 03 May 2004 08:58:48 -0400
Received: from mailhost.jlc.net ([199.201.159.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKcwZ-0006eg-00
	for ietf@ietf.org; Mon, 03 May 2004 08:53:12 -0400
Received: by mailhost.jlc.net (Postfix, from userid 104)
	id 7AD91E0718; Mon,  3 May 2004 08:53:03 -0400 (EDT)
Date: Mon, 3 May 2004 08:53:03 -0400
From: John Leslie <john@jlc.net>
To: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
Cc: Harald Tveit Alvestrand <harald@alvestrand.no>, ietf@ietf.org
Subject: Re: Please note this update: IETF mission statement
Message-ID: <20040503125303.GA12377@verdi>
References: <364559378.1083538207@[192.168.1.63]> <20040503185407.72b79956.ietf@130c04165a5b40404e4440445758487a.nosense.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040503185407.72b79956.ietf@130c04165a5b40404e4440445758487a.nosense.org>
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=AWL autolearn=no version=2.60

Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org> wrote:
> Harald Tveit Alvestrand <harald@alvestrand.no> wrote:
> 
>> http://www.ietf.org/internet-drafts/draft-alvestrand-ietf-mission-01.txt
> 
> I haven't been all that involved in the IETF to have a strong
> opinion on the draft. That being said, it sounds good.

   Harald (et al) should be commended for this work.

> Regarding deleting the appendix, I'd suggest not doing so, as I
> think it fits the "Relevant" clause, namely :
> 
> "Note that it does not mean "correct" or "positive" - a
> report of an experiment that failed, or a specification that
> clearly says why you should not use it in a given situation,
> can be highly relevant - for deciding what NOT to do."
> 
> I think including the possible mission statements that weren't
> adequate will help further clarify the one that is.

   I must disagree with Mark and agree with Harald. Inclusion of
Appendix A in _this_ document would detract from the sense of closure,
and give the impresssion that the issues it mentions are still open.

> If the appendix is retained, and it isn't too much effort,
> expanded explanations of why the other mission statement
> candidates weren't satisfactory or adequate may be of some value.
 
  I'd be happy to see a separate document describing the process of
reaching this statement of mission.

====
A Few Nits:

4.1
" 
" We embrace technical concepts such as decentralized control, edge-user
" empowerment and sharing of resources, because those concepts resonate
" with the core values of the IETF community. These concepts have little
" to do with the technology that's possible, and much to do with the
" technology that we choose to create.

   The language here is very good -- in fact, commendable.

   But the aim is a trifle off.

   Whether we "embrace" "decentralized control" is orthogonal to our
mission. We have designed protocols which work well in the presence of
decentralized control, not because we "embrace" anything, but because
we believed it to be impossible to reach the global scope of today's
Internet _without_ decentralized control. I quite agree that it belongs
in our mission statement.

   On the other hand, "edge-user empowerment" is a different animal.
It is _not_ necessary to the existence of the Internet. And it invites
misinterpretation. There's limited consensus today what the "edge"
means. And "empowerment", though it _means_ delegation towards the
edge, is used in so many different ways today that it's semantically
empty.

   I suggest eliminating "edge-user empowerment". What I believe
Harald (et al) meant by this is to extend the "decentralized control"
out to the very edge, enabling users at the (loosely-defined) edge
to have sufficient control of their communications to explore new
uses for the Internet. I think we can trust users to work in that
direction without needing a statement here.

   With this in mind, a possible wording would be:

+ The concept of decentralized control, initially necessary in order
+ to grow the Internet to global scale, has become a core value to
+ the IETF community. Similarly, the concept of sharing resources
+ without letting ourselves get bogged down in accounting for them
+ has become a core value. We will continue to choose to create
+ technologies that resonate with our core values.

" In attempting to resolve this question, perhaps the fairest balance
" is struck by this formulation: "protocols and practices for which
" secure and scalable implementations are expected to have wide
" deployment and interoperation on the Internet, or to form part of the
" infrastructure of the Internet."

   It's not clear what "question" is being discussed. I'm pretty sure
Harald means the question of whether particular work is included
within the scope of the IETF mission; but this has gotten lost in
context.

   Thus I suggest rewording, perhaps something like:

+ In deciding whether particular work is "in-scope" for the IETF, we
+ try to concentrate on "protocols and practices for which secure and
+ scalable implementations are expected to have wide deployment and
+ interoperation on the Internet, or to form part of the infrastructure
+ of the Internet."

4.2
" 
" The IETF has traditionally been a community for both experimentation
" with things that are not fully understood, standardization of
" protocols for which some understanding has been reached, and
" publication of (and refinement of) protocols originally specified
" outside the IETF process.

   Alas, "both" can only connect _two_ choices, and we have at least
three here. I suggest eliminating the word "both".

" In deciding whether or not these activities should be done within the
" IETF, one should not chiefly look at the type of activity, but the
" potential benefit to the Internet - an experiment that yields
" information about the fact that an approach is not viable might be as
" worthy of publication as a standard that is technically competent,
" but only useful in a few special cases.

   "As worthy of publication as a standard" leads the reader to stumble
over _why_ the failed experiment should be published "as a standard".
(Hey, I warned you I'm picking nits!)

   I suggest some shuffling, perhaps like:

+ The type of activity shouldn't drive the decision of whether an
+ activity belongs within the IETF - an Informational RFC describing
+ a failed experiment, showing why that approach is not viable, might
+ be of greater benefit to the Internet than a Standards-track RFC
+ useful in only a few special cases.

====
6. Acknowledgments

   Harald asks:
" 
" Given how incomplete this section necessarily is, should it just say
" "None mentioned, none forgotten"?

   No, it shouldn't (though the temptation is strong). An apology to
those you forgot to mention is appropriate, but you must try to come
up with a list of the most important contributors.

   The list in the draft looks good to me.

--
John Leslie <john@jlc.net>

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


From ietf-admin@ietf.org  Mon May  3 10:21: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 KAA04190
	for <ietf-archive@ietf.org>; Mon, 3 May 2004 10:21: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 1BKeJy-0004T0-Lf
	for ietf-archive@ietf.org; Mon, 03 May 2004 10:21:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKeGo-0003vE-00
	for ietf-archive@ietf.org; Mon, 03 May 2004 10:18:11 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKe9w-0002ir-00
	for ietf-archive@ietf.org; Mon, 03 May 2004 10:11:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKdrc-0002Jc-OT; Mon, 03 May 2004 09:52:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKdiw-00076A-DR
	for ietf@optimus.ietf.org; Mon, 03 May 2004 09:43: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 JAA28994
	for <ietf@ietf.org>; Mon, 3 May 2004 09:43: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 1BKdiu-0006S6-EF
	for ietf@ietf.org; Mon, 03 May 2004 09:43:08 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKdeQ-0005ar-00
	for ietf@ietf.org; Mon, 03 May 2004 09:38:31 -0400
Received: from 251.cust42.nsw.dsl.ozemail.com.au ([203.103.121.251] helo=nosense.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKdZT-0004o0-00
	for ietf@ietf.org; Mon, 03 May 2004 09:33:24 -0400
Received: from Dupy2.nosense.org (localhost.localdomain [127.0.0.1])
	by nosense.org (Postfix) with SMTP
	id E07163F02A; Mon,  3 May 2004 23:05:26 +0930 (CST)
Date: Mon, 3 May 2004 23:05:26 +0930
From: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
To: John Leslie <john@jlc.net>
Cc: harald@alvestrand.no, ietf@ietf.org
Subject: Re: Please note this update: IETF mission statement
Message-Id: <20040503230526.362dcf73.ietf@130c04165a5b40404e4440445758487a.nosense.org>
In-Reply-To: <20040503125303.GA12377@verdi>
References: <364559378.1083538207@[192.168.1.63]>
	<20040503185407.72b79956.ietf@130c04165a5b40404e4440445758487a.nosense.org>
	<20040503125303.GA12377@verdi>
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 John, Harald,

On Mon, 3 May 2004 08:53:03 -0400
John Leslie <john@jlc.net> wrote:

> Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
> wrote:
> > Harald Tveit Alvestrand <harald@alvestrand.no> wrote:
> > 
> >>
> >http://www.ietf.org/internet-drafts/draft-alvestrand-ietf-mis
> >sion-01.txt
> > 
> > I haven't been all that involved in the IETF to have a strong
> > opinion on the draft. That being said, it sounds good.
> 
>    Harald (et al) should be commended for this work.

Completely agree.

> 
> > Regarding deleting the appendix, I'd suggest not doing so, as
> > I think it fits the "Relevant" clause, namely :
> > 
> > "Note that it does not mean "correct" or "positive" - a
> > report of an experiment that failed, or a specification that
> > clearly says why you should not use it in a given situation,
> > can be highly relevant - for deciding what NOT to do."
> > 
> > I think including the possible mission statements that
> > weren't adequate will help further clarify the one that is.
> 
>    I must disagree with Mark and agree with Harald. Inclusion
>    of
> Appendix A in _this_ document would detract from the sense of
> closure, and give the impresssion that the issues it mentions
> are still open.
> 
> > If the appendix is retained, and it isn't too much effort,
> > expanded explanations of why the other mission statement
> > candidates weren't satisfactory or adequate may be of some
> > value.
>  
>   I'd be happy to see a separate document describing the
>   process of
> reaching this statement of mission.
> 

I'd be happy with this approach. I think sometimes preserving the
"whys" can be as useful as the "whats". ("Why ?" is one of my
favourite questions :-) )

Regards,
Mark.

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


From ietf-admin@ietf.org  Mon May  3 12: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 MAA10003
	for <ietf-archive@ietf.org>; Mon, 3 May 2004 12: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 1BKfxA-0003UJ-Ss
	for ietf-archive@ietf.org; Mon, 03 May 2004 12:06:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKfwF-0003PF-00
	for ietf-archive@ietf.org; Mon, 03 May 2004 12:05:04 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKfvn-0003KF-00
	for ietf-archive@ietf.org; Mon, 03 May 2004 12:04:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKflb-00046H-5h; Mon, 03 May 2004 11:54:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKfhQ-0003Ba-80
	for ietf@optimus.ietf.org; Mon, 03 May 2004 11:49:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09121
	for <ietf@ietf.org>; Mon, 3 May 2004 11:49: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 1BKfhP-0002Ja-1K
	for ietf@ietf.org; Mon, 03 May 2004 11:49:43 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKfgT-0002G0-00
	for ietf@ietf.org; Mon, 03 May 2004 11:48:46 -0400
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKffX-0002By-00
	for ietf@ietf.org; Mon, 03 May 2004 11:47:47 -0400
Received: from f01v-36-235.d0.club-internet.fr ([212.195.247.235] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.24)
	id 1BKffQ-0002vZ-5j; Mon, 03 May 2004 08:47:40 -0700
Message-Id: <6.0.1.1.2.20040503161058.04ad0b80@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Mon, 03 May 2004 17:57:30 +0200
To: Harald Tveit Alvestrand <harald@alvestrand.no>, ietf@ietf.org
From: jfcm <info@utel.net>
Subject: Re: Please note this update: IETF mission statement
In-Reply-To: <364559378.1083538207@[192.168.1.63]>
References: <364559378.1083538207@[192.168.1.63]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - utel.net
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

Dear Harald,
1. Very good work. Extremely clear and useful.

At 07:50 03/05/04, Harald Tveit Alvestrand wrote:
>I have tried to incorporate the extremely useful feedback I got on this 
>list and from the Korea plenary.
>
>I hope this is ready to send to IETF-wide Last Call.
>This is your chance to get at it early :-)
>Take care,

2. But I am very embarrassed to understand how "a large, heterogeneous 
collection of interconnected systems that can be used for communication of 
many different types between any interested parties connected to it", can 
be anything else than value-neutral.

This alights the constant disagreement I have with many here. Until now I 
considered there were only two visions of the Internet.
1. the very clear 47 USC 230 (f)(1) definition: "The term 'Internet' means 
the international computer network of both Federal and non-Federal 
interoperable packet switched data networks." This means a network of 
machines for the entire globality of the world.
2. a consensual metastructure of names, addresses and protocols to support 
numeric relations between its participating users and user agents. This 
means a network of users/usages, matching the all the needs the globe over.

In both cases I fully understand what "making the Internet work better" may 
mean.
1. to better match the state of the art, to better resist to hackers and to 
better grow in size or in technology support
2. to better fulfill the user needs, to permit be surer datacoms, to strive 
to support everyone for everything they need.
Timely, safe and scalable. I can live with both understandings as they say 
the same thing to a technology oriented body: "the technology must perform 
better". In this I agree with Fred Baker's, Dean Anderson's ... 
propositions or even with the one proposed if what follows was removed.

In the proposed draft, there is an in between dogmatic vision of the 
internet which is _not_ technically rooted (you underline it):
<quote>
We want the Internet to be useful for communities that share our commitment 
to openness and fairness.  We embrace technical concepts such as 
decentralized control, edge-user empowerment and sharing of resources, 
because those concepts resonate with the core values of
the IETF community. These concepts have little to do with the technology 
that's possible, and much to do with the technology that we choose to create.
</quote>

This means:
- there is an IETF community
- it has core values
- best supporting these values has priority to best supporting the 
technology efficiency (first understanding) or the best possible usage 
(second understanding).
This makes IETF a Church.

- it dedicates itself to a subset of the internet system it makes the 
"Internet" (boarders unclear).
This makes the IETF a sect (I certainly do not want to sound outrageous 
here, but calling a cat a baby cat, helps to more clearly identify the 
implied meaning).

I have no objection to the principle of such an approach, once it is 
clearly published as you do it now. To the contrary, to some extent I 
welcome it because it clarifies a lot of issues. In particular why IAB 
never published an architectural model of the internet: this model is 
actually made of the core values of the IETF community. This explains why 
IETF does not need market studies, why users have not their say. Why USG 
develops its own internet elsewhere. Why RFC cannot be updated: one does 
not update a catechism. It is not technical engineering but applied 
evangelization.

I would not even have objections to all this, if my long, reviewable and 
reality based analysis matched the (by nature) non negotiable IETF core 
values and their resonating technical consequences. But I technically 
disagree with them, for a deeper personal core value: to make a good job 
out of my own life.

- I understand what is an open protocol and I do not see much of them in 
here. I do not know what a fair electron or an honest byte can be. You know 
my formula on this: "I do not expect my telephone to be democratic, I 
expect it to work". Sorry to be IETF agnostic. This lead me to the Coliseum 
several times already.

- from my humble analysis, and accepting many graduated exceptions, I 
consider decentralized control, edge-user empowerment and resource sharing 
as outdated concepts of the 60s (I entered network operations in 69 and 
never used them before meeting the Internet four years ago). I am used and 
I made my life dedicated to R&D of distributed global control, user's full 
concerted granular empowerment, subsidiarity, numeric continuity relations 
and interaction, hybrid networks, etc.

Obviously I may be wrong, but this creed regidity (integrism?),
- makes the IETF technically unreliable when the life of millions and the 
world's economy depend on the internet solutions (with small "i")
- should make the proposed goal to be corrected as "The goal of the IETF is 
to make the Internet work better along the IETF core values".

Now, a general comment: all this seems inconsistent or even opposed the 
rest of the texts of this excellent draft of yours.
Thank you for the clarification about the IETF Church I had not fully 
understood yet. But I am low IQ.
jfc 


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


From exim@www1.ietf.org  Mon May  3 12:20: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 MAA10645
	for <ietf-archive@odin.ietf.org>; Mon, 3 May 2004 12:20: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 1BKfvo-0006Ta-6E
	for ietf-archive@odin.ietf.org; Mon, 03 May 2004 12:04:37 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i43G4aU0024891
	for ietf-archive@odin.ietf.org; Mon, 3 May 2004 12:04:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKflb-00046H-5h; Mon, 03 May 2004 11:54:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKfhQ-0003Ba-80
	for ietf@optimus.ietf.org; Mon, 03 May 2004 11:49:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09121
	for <ietf@ietf.org>; Mon, 3 May 2004 11:49: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 1BKfhP-0002Ja-1K
	for ietf@ietf.org; Mon, 03 May 2004 11:49:43 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKfgT-0002G0-00
	for ietf@ietf.org; Mon, 03 May 2004 11:48:46 -0400
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKffX-0002By-00
	for ietf@ietf.org; Mon, 03 May 2004 11:47:47 -0400
Received: from f01v-36-235.d0.club-internet.fr ([212.195.247.235] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.24)
	id 1BKffQ-0002vZ-5j; Mon, 03 May 2004 08:47:40 -0700
Message-Id: <6.0.1.1.2.20040503161058.04ad0b80@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Mon, 03 May 2004 17:57:30 +0200
To: Harald Tveit Alvestrand <harald@alvestrand.no>, ietf@ietf.org
From: jfcm <info@utel.net>
Subject: Re: Please note this update: IETF mission statement
In-Reply-To: <364559378.1083538207@[192.168.1.63]>
References: <364559378.1083538207@[192.168.1.63]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - utel.net
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.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>

Dear Harald,
1. Very good work. Extremely clear and useful.

At 07:50 03/05/04, Harald Tveit Alvestrand wrote:
>I have tried to incorporate the extremely useful feedback I got on this 
>list and from the Korea plenary.
>
>I hope this is ready to send to IETF-wide Last Call.
>This is your chance to get at it early :-)
>Take care,

2. But I am very embarrassed to understand how "a large, heterogeneous 
collection of interconnected systems that can be used for communication of 
many different types between any interested parties connected to it", can 
be anything else than value-neutral.

This alights the constant disagreement I have with many here. Until now I 
considered there were only two visions of the Internet.
1. the very clear 47 USC 230 (f)(1) definition: "The term 'Internet' means 
the international computer network of both Federal and non-Federal 
interoperable packet switched data networks." This means a network of 
machines for the entire globality of the world.
2. a consensual metastructure of names, addresses and protocols to support 
numeric relations between its participating users and user agents. This 
means a network of users/usages, matching the all the needs the globe over.

In both cases I fully understand what "making the Internet work better" may 
mean.
1. to better match the state of the art, to better resist to hackers and to 
better grow in size or in technology support
2. to better fulfill the user needs, to permit be surer datacoms, to strive 
to support everyone for everything they need.
Timely, safe and scalable. I can live with both understandings as they say 
the same thing to a technology oriented body: "the technology must perform 
better". In this I agree with Fred Baker's, Dean Anderson's ... 
propositions or even with the one proposed if what follows was removed.

In the proposed draft, there is an in between dogmatic vision of the 
internet which is _not_ technically rooted (you underline it):
<quote>
We want the Internet to be useful for communities that share our commitment 
to openness and fairness.  We embrace technical concepts such as 
decentralized control, edge-user empowerment and sharing of resources, 
because those concepts resonate with the core values of
the IETF community. These concepts have little to do with the technology 
that's possible, and much to do with the technology that we choose to create.
</quote>

This means:
- there is an IETF community
- it has core values
- best supporting these values has priority to best supporting the 
technology efficiency (first understanding) or the best possible usage 
(second understanding).
This makes IETF a Church.

- it dedicates itself to a subset of the internet system it makes the 
"Internet" (boarders unclear).
This makes the IETF a sect (I certainly do not want to sound outrageous 
here, but calling a cat a baby cat, helps to more clearly identify the 
implied meaning).

I have no objection to the principle of such an approach, once it is 
clearly published as you do it now. To the contrary, to some extent I 
welcome it because it clarifies a lot of issues. In particular why IAB 
never published an architectural model of the internet: this model is 
actually made of the core values of the IETF community. This explains why 
IETF does not need market studies, why users have not their say. Why USG 
develops its own internet elsewhere. Why RFC cannot be updated: one does 
not update a catechism. It is not technical engineering but applied 
evangelization.

I would not even have objections to all this, if my long, reviewable and 
reality based analysis matched the (by nature) non negotiable IETF core 
values and their resonating technical consequences. But I technically 
disagree with them, for a deeper personal core value: to make a good job 
out of my own life.

- I understand what is an open protocol and I do not see much of them in 
here. I do not know what a fair electron or an honest byte can be. You know 
my formula on this: "I do not expect my telephone to be democratic, I 
expect it to work". Sorry to be IETF agnostic. This lead me to the Coliseum 
several times already.

- from my humble analysis, and accepting many graduated exceptions, I 
consider decentralized control, edge-user empowerment and resource sharing 
as outdated concepts of the 60s (I entered network operations in 69 and 
never used them before meeting the Internet four years ago). I am used and 
I made my life dedicated to R&D of distributed global control, user's full 
concerted granular empowerment, subsidiarity, numeric continuity relations 
and interaction, hybrid networks, etc.

Obviously I may be wrong, but this creed regidity (integrism?),
- makes the IETF technically unreliable when the life of millions and the 
world's economy depend on the internet solutions (with small "i")
- should make the proposed goal to be corrected as "The goal of the IETF is 
to make the Internet work better along the IETF core values".

Now, a general comment: all this seems inconsistent or even opposed the 
rest of the texts of this excellent draft of yours.
Thank you for the clarification about the IETF Church I had not fully 
understood yet. But I am low IQ.
jfc 


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



From ietf-admin@ietf.org  Mon May  3 12:39: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 MAA11837
	for <ietf-archive@ietf.org>; Mon, 3 May 2004 12:39: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 1BKgTL-000680-K7
	for ietf-archive@ietf.org; Mon, 03 May 2004 12:39:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKgSC-000602-00
	for ietf-archive@ietf.org; Mon, 03 May 2004 12:38:05 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKgR7-0005tX-00
	for ietf-archive@ietf.org; Mon, 03 May 2004 12:36:57 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKgEg-0004cu-7u; Mon, 03 May 2004 12:24:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKg7b-0002dF-PN
	for ietf@optimus.ietf.org; Mon, 03 May 2004 12:16:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10528
	for <ietf@ietf.org>; Mon, 3 May 2004 12:16: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 1BKg7a-0004DI-AW
	for ietf@ietf.org; Mon, 03 May 2004 12:16:46 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKg6c-0004Ac-00
	for ietf@ietf.org; Mon, 03 May 2004 12:15:47 -0400
Received: from backin5.merit.edu ([198.108.60.28])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKg5m-00045c-00
	for ietf@ietf.org; Mon, 03 May 2004 12:14:54 -0400
Received: by backin5.merit.edu (Postfix, from userid 8935)
	id 848897E543; Mon,  3 May 2004 12:13:14 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
	by backin5.merit.edu (Postfix) with ESMTP
	id 6E29D29ADA; Mon,  3 May 2004 12:13:14 -0400 (EDT)
Date: Mon, 3 May 2004 12:13:14 -0400 (EDT)
From: Susan Harris <srh@merit.edu>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
Cc: ietf@ietf.org
Subject: Re: Please note this update: IETF mission statement
In-Reply-To: <364559378.1083538207@[192.168.1.63]>
Message-ID: <Pine.GSO.4.58.0405031116050.18632@backin5.merit.edu>
References: <364559378.1083538207@[192.168.1.63]>
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

Nothing like jumping in late and editing the first sentence, but here
goes:

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

This is phrased a bit awkwardly, and implies that the Internet isn't
working all that well now. What about:

  "The goal of the IETF is to ensure that the Internet continues to
   work effectively."

And a few paragraphs later, to tighten it up a bit:

>    Open process - that any interested participant can in fact
                    ^^^^                                ^^^^^^^
                    omit                                omit

>       participate in the work, know what is being decided, and make his
>       or her voice heard on the issue. Part of this principle is our
>       commitment to making our documents, our WG mailing lists, our
>       attendance lists and our meeting minutes publicly available on the
>       Net.
>
>
>    Technical competence - that the issues on which the IETF produces its
                            ^^^^
                            omit

>       documents are issues where the IETF has the competence needed to
>       speak to them, and that the IETF is willing to listen to
>       technically competent input from any source.
>       Technical competence also means that we expect IETF output to be
>       designed to sound network engineering principles - this is also
>       often referred to as "engineering quality".
>
>
>    Volunteer Core - that our participants and our leadership are people
                      ^^^^
                      omit

>       who come to the IETF because they want to work for the IETF's
>       purposes.
>
>
>
>    Rough consensus and running code - We make standards based on the
>       combined engineering judgement of our participants and our
>       real-world experience in implementing and deploying our
>       specifications.
>
>
>    Protocol ownership - that when the IETF takes ownership of a protocol
                          ^^^^
                          omit

>       or function, it accepts the responsibility for all aspects of the
>       protocol, even though some aspects may rarely or never be seen on
>       the Internet. Conversely, that when the IETF is not responsible
                                  ^^^^
                                  omit

>       for a protocol or function, it does not attempt to exert control
>       over it, even though it may at times touch or affect the Internet.
>

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


From exim@www1.ietf.org  Mon May  3 12:45:51 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12621
	for <ietf-archive@odin.ietf.org>; Mon, 3 May 2004 12:45:51 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKgR8-0007Z1-1a
	for ietf-archive@odin.ietf.org; Mon, 03 May 2004 12:36:58 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i43Gawtg029071
	for ietf-archive@odin.ietf.org; Mon, 3 May 2004 12:36:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKgEg-0004cu-7u; Mon, 03 May 2004 12:24:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKg7b-0002dF-PN
	for ietf@optimus.ietf.org; Mon, 03 May 2004 12:16:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10528
	for <ietf@ietf.org>; Mon, 3 May 2004 12:16: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 1BKg7a-0004DI-AW
	for ietf@ietf.org; Mon, 03 May 2004 12:16:46 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKg6c-0004Ac-00
	for ietf@ietf.org; Mon, 03 May 2004 12:15:47 -0400
Received: from backin5.merit.edu ([198.108.60.28])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKg5m-00045c-00
	for ietf@ietf.org; Mon, 03 May 2004 12:14:54 -0400
Received: by backin5.merit.edu (Postfix, from userid 8935)
	id 848897E543; Mon,  3 May 2004 12:13:14 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
	by backin5.merit.edu (Postfix) with ESMTP
	id 6E29D29ADA; Mon,  3 May 2004 12:13:14 -0400 (EDT)
Date: Mon, 3 May 2004 12:13:14 -0400 (EDT)
From: Susan Harris <srh@merit.edu>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
Cc: ietf@ietf.org
Subject: Re: Please note this update: IETF mission statement
In-Reply-To: <364559378.1083538207@[192.168.1.63]>
Message-ID: <Pine.GSO.4.58.0405031116050.18632@backin5.merit.edu>
References: <364559378.1083538207@[192.168.1.63]>
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>

Nothing like jumping in late and editing the first sentence, but here
goes:

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

This is phrased a bit awkwardly, and implies that the Internet isn't
working all that well now. What about:

  "The goal of the IETF is to ensure that the Internet continues to
   work effectively."

And a few paragraphs later, to tighten it up a bit:

>    Open process - that any interested participant can in fact
                    ^^^^                                ^^^^^^^
                    omit                                omit

>       participate in the work, know what is being decided, and make his
>       or her voice heard on the issue. Part of this principle is our
>       commitment to making our documents, our WG mailing lists, our
>       attendance lists and our meeting minutes publicly available on the
>       Net.
>
>
>    Technical competence - that the issues on which the IETF produces its
                            ^^^^
                            omit

>       documents are issues where the IETF has the competence needed to
>       speak to them, and that the IETF is willing to listen to
>       technically competent input from any source.
>       Technical competence also means that we expect IETF output to be
>       designed to sound network engineering principles - this is also
>       often referred to as "engineering quality".
>
>
>    Volunteer Core - that our participants and our leadership are people
                      ^^^^
                      omit

>       who come to the IETF because they want to work for the IETF's
>       purposes.
>
>
>
>    Rough consensus and running code - We make standards based on the
>       combined engineering judgement of our participants and our
>       real-world experience in implementing and deploying our
>       specifications.
>
>
>    Protocol ownership - that when the IETF takes ownership of a protocol
                          ^^^^
                          omit

>       or function, it accepts the responsibility for all aspects of the
>       protocol, even though some aspects may rarely or never be seen on
>       the Internet. Conversely, that when the IETF is not responsible
                                  ^^^^
                                  omit

>       for a protocol or function, it does not attempt to exert control
>       over it, even though it may at times touch or affect the Internet.
>

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



From ietf-admin@ietf.org  Mon May  3 14:26:44 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18416
	for <ietf-archive@ietf.org>; Mon, 3 May 2004 14:26: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 1BKi9M-0002eb-W5
	for ietf-archive@ietf.org; Mon, 03 May 2004 14:26:45 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKi8Q-0002XK-00
	for ietf-archive@ietf.org; Mon, 03 May 2004 14:25:46 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKi7S-0002PR-00
	for ietf-archive@ietf.org; Mon, 03 May 2004 14:24:46 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKhx4-0006FA-0c; Mon, 03 May 2004 14:14:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKhiJ-0002lA-AH
	for ietf@optimus.ietf.org; Mon, 03 May 2004 13:58:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16833
	for <ietf@ietf.org>; Mon, 3 May 2004 13:58: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 1BKhiG-0007F7-Tr
	for ietf@ietf.org; Mon, 03 May 2004 13:58:45 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKhhN-0007A8-00
	for ietf@ietf.org; Mon, 03 May 2004 13:57:49 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKhge-0006zK-00
	for ietf@ietf.org; Mon, 03 May 2004 13:57:05 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id BECD6621D5; Mon,  3 May 2004 19:56:33 +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 26959-10; Mon,  3 May 2004 19:56:33 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 7E5F9621D0; Mon,  3 May 2004 19:56:31 +0200 (CEST)
Date: Mon, 03 May 2004 09:36:13 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Susan Harris <srh@merit.edu>
Cc: ietf@ietf.org
Subject: Re: Please note this update: IETF mission statement
Message-ID: <403325911.1083576973@localhost>
In-Reply-To: <Pine.GSO.4.58.0405031116050.18632@backin5.merit.edu>
References: <364559378.1083538207@[192.168.1.63]>
 <Pine.GSO.4.58.0405031116050.18632@backin5.merit.edu>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
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 3. mai 2004 12:13 -0400 Susan Harris <srh@merit.edu> wrote:

> Nothing like jumping in late and editing the first sentence, but here
> goes:
>
>> The goal of the IETF is to make the Internet work better.
>
> This is phrased a bit awkwardly, and implies that the Internet isn't
> working all that well now. What about:
>
>   "The goal of the IETF is to ensure that the Internet continues to
>    work effectively."

actually the previous version had "The goal of the IETF is to make the 
Internet work" - I was chastised for lack of ambition on the IETF's behalf!

I actually think the Internet works quite well, in many aspects, but 
there's lots of room for improvement - or there would be no spam in my 
mailbox, and I would know by the touch of a button whether or not I could 
set up a video call to you to discuss these matters.....

but I like being ambitious enough to expect the IETF to help it improve!






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


From exim@www1.ietf.org  Mon May  3 14:38: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 OAA19317
	for <ietf-archive@odin.ietf.org>; Mon, 3 May 2004 14:38: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 1BKi7U-0000NN-4p
	for ietf-archive@odin.ietf.org; Mon, 03 May 2004 14:24:48 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i43IOmIZ001406
	for ietf-archive@odin.ietf.org; Mon, 3 May 2004 14:24:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKhx4-0006FA-0c; Mon, 03 May 2004 14:14:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKhiJ-0002lA-AH
	for ietf@optimus.ietf.org; Mon, 03 May 2004 13:58:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16833
	for <ietf@ietf.org>; Mon, 3 May 2004 13:58: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 1BKhiG-0007F7-Tr
	for ietf@ietf.org; Mon, 03 May 2004 13:58:45 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKhhN-0007A8-00
	for ietf@ietf.org; Mon, 03 May 2004 13:57:49 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKhge-0006zK-00
	for ietf@ietf.org; Mon, 03 May 2004 13:57:05 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id BECD6621D5; Mon,  3 May 2004 19:56:33 +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 26959-10; Mon,  3 May 2004 19:56:33 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 7E5F9621D0; Mon,  3 May 2004 19:56:31 +0200 (CEST)
Date: Mon, 03 May 2004 09:36:13 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Susan Harris <srh@merit.edu>
Cc: ietf@ietf.org
Subject: Re: Please note this update: IETF mission statement
Message-ID: <403325911.1083576973@localhost>
In-Reply-To: <Pine.GSO.4.58.0405031116050.18632@backin5.merit.edu>
References: <364559378.1083538207@[192.168.1.63]>
 <Pine.GSO.4.58.0405031116050.18632@backin5.merit.edu>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-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: 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 3. mai 2004 12:13 -0400 Susan Harris <srh@merit.edu> wrote:

> Nothing like jumping in late and editing the first sentence, but here
> goes:
>
>> The goal of the IETF is to make the Internet work better.
>
> This is phrased a bit awkwardly, and implies that the Internet isn't
> working all that well now. What about:
>
>   "The goal of the IETF is to ensure that the Internet continues to
>    work effectively."

actually the previous version had "The goal of the IETF is to make the 
Internet work" - I was chastised for lack of ambition on the IETF's behalf!

I actually think the Internet works quite well, in many aspects, but 
there's lots of room for improvement - or there would be no spam in my 
mailbox, and I would know by the touch of a button whether or not I could 
set up a video call to you to discuss these matters.....

but I like being ambitious enough to expect the IETF to help it improve!






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



From ietf-admin@ietf.org  Tue May  4 08:18: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 IAA26749
	for <ietf-archive@ietf.org>; Tue, 4 May 2004 08: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 1BKyso-0001tO-FB
	for ietf-archive@ietf.org; Tue, 04 May 2004 08:18:46 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKys9-0001eS-00
	for ietf-archive@ietf.org; Tue, 04 May 2004 08:18:06 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKyrE-0001NX-00
	for ietf-archive@ietf.org; Tue, 04 May 2004 08:17:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKygU-0000lN-5E; Tue, 04 May 2004 08:06:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKgfz-0003n8-53
	for ietf@optimus.ietf.org; Mon, 03 May 2004 12:52: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 MAA13232
	for <ietf@ietf.org>; Mon, 3 May 2004 12:52: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 1BKgfx-0000Jn-Dd
	for ietf@ietf.org; Mon, 03 May 2004 12:52:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKgf7-0000BE-00
	for ietf@ietf.org; Mon, 03 May 2004 12:51:25 -0400
Received: from mout.perfora.net ([217.160.230.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKge9-00001y-00
	for ietf@ietf.org; Mon, 03 May 2004 12:50:25 -0400
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1BKge9-0008B1-00
	for ietf@ietf.org; Mon, 03 May 2004 12:50:25 -0400
Received: from [68.246.190.141] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1BKge8-0005LY-00
	for ietf@ietf.org; Mon, 03 May 2004 12:50:25 -0400
Message-ID: <40967846.8000701@solidmatrix.com>
Date: Mon, 03 May 2004 12:50:14 -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: IETF Discussion <ietf@ietf.org>
Subject: [Fwd: 0. General - UPDATE on "FCC soliciting comments on mobile spam"]
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: perfora.net abuse@perfora.net auth:7051a7fa85b96745770cd89fa6d27f10
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

FYI. Some of the comments submitted are rather dangerous.

Yakov

-------- Original Message --------
Subject: 0. General - UPDATE on "FCC soliciting comments on mobile spam"
Date: Mon, 03 May 2004 12:44:30 -0400
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
To: ASRG <asrg@ietf.org>

This was sent to me from the FCC.

Yakov

-------- Original Message --------
The initial Comment period for the FCC's wireless spam ruling making
closed on April 30, and the FCC is now accepting Replies to those
comments through May 17. The comments that were submitted can be
reviewed by going to the FCC's Electronic Comment Filing System search
page at http://gullfoss2.fcc.gov/prod/ecfs/comsrch_v2.cgi and searching
on the proceeding "04-53".

General information about the subject of this rulemaking is available at
http://www.fcc.gov/cgb/policy/canspam.html.  This includes a summary of
the questions of interpretation and technical solutions that have been
addressed in the comments received to date.

Individuals or groups interested in filing comments (e.g., in response
to the Comments received to date) can find detailed instructions on how
to file Reply comments in Paragraphs 56-60 on p. 23 of the Notice of
Proposed Rulemaking at
http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-04-52A1.doc.
Comments for this proceeding can also be easily filed using the FCC's
ECFS Express option, at http://gullfoss2.fcc.gov/ecfs/Upload/.


--
Yakov Shafranovich / asrg <at> shaftek.org
SolidMatrix Technologies, Inc. / research <at> solidmatrix.com
"And this too shall come to pass"

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


From exim@www1.ietf.org  Tue May  4 08:24: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 IAA27039
	for <ietf-archive@odin.ietf.org>; Tue, 4 May 2004 08:24: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 1BKyrE-0003zB-Pl
	for ietf-archive@odin.ietf.org; Tue, 04 May 2004 08:17:09 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i44CH8hK015317
	for ietf-archive@odin.ietf.org; Tue, 4 May 2004 08:17:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKygU-0000lN-5E; Tue, 04 May 2004 08:06:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BKgfz-0003n8-53
	for ietf@optimus.ietf.org; Mon, 03 May 2004 12:52: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 MAA13232
	for <ietf@ietf.org>; Mon, 3 May 2004 12:52: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 1BKgfx-0000Jn-Dd
	for ietf@ietf.org; Mon, 03 May 2004 12:52:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BKgf7-0000BE-00
	for ietf@ietf.org; Mon, 03 May 2004 12:51:25 -0400
Received: from mout.perfora.net ([217.160.230.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BKge9-00001y-00
	for ietf@ietf.org; Mon, 03 May 2004 12:50:25 -0400
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1BKge9-0008B1-00
	for ietf@ietf.org; Mon, 03 May 2004 12:50:25 -0400
Received: from [68.246.190.141] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1BKge8-0005LY-00
	for ietf@ietf.org; Mon, 03 May 2004 12:50:25 -0400
Message-ID: <40967846.8000701@solidmatrix.com>
Date: Mon, 03 May 2004 12:50:14 -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: IETF Discussion <ietf@ietf.org>
Subject: [Fwd: 0. General - UPDATE on "FCC soliciting comments on mobile spam"]
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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
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

FYI. Some of the comments submitted are rather dangerous.

Yakov

-------- Original Message --------
Subject: 0. General - UPDATE on "FCC soliciting comments on mobile spam"
Date: Mon, 03 May 2004 12:44:30 -0400
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
To: ASRG <asrg@ietf.org>

This was sent to me from the FCC.

Yakov

-------- Original Message --------
The initial Comment period for the FCC's wireless spam ruling making
closed on April 30, and the FCC is now accepting Replies to those
comments through May 17. The comments that were submitted can be
reviewed by going to the FCC's Electronic Comment Filing System search
page at http://gullfoss2.fcc.gov/prod/ecfs/comsrch_v2.cgi and searching
on the proceeding "04-53".

General information about the subject of this rulemaking is available at
http://www.fcc.gov/cgb/policy/canspam.html.  This includes a summary of
the questions of interpretation and technical solutions that have been
addressed in the comments received to date.

Individuals or groups interested in filing comments (e.g., in response
to the Comments received to date) can find detailed instructions on how
to file Reply comments in Paragraphs 56-60 on p. 23 of the Notice of
Proposed Rulemaking at
http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-04-52A1.doc.
Comments for this proceeding can also be easily filed using the FCC's
ECFS Express option, at http://gullfoss2.fcc.gov/ecfs/Upload/.


--
Yakov Shafranovich / asrg <at> shaftek.org
SolidMatrix Technologies, Inc. / research <at> solidmatrix.com
"And this too shall come to pass"

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



From exim@www1.ietf.org  Fri May  7 01:22: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 BAA12070
	for <ietf-archive@odin.ietf.org>; Fri, 7 May 2004 01:22: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 1BLxn7-000761-SW
	for ietf-archive@odin.ietf.org; Fri, 07 May 2004 01:20:57 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i475KvvI027255
	for ietf-archive@odin.ietf.org; Fri, 7 May 2004 01:20:57 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLxeY-0004oJ-G8; Fri, 07 May 2004 01:12:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLxaA-0002tM-Pu
	for ietf@optimus.ietf.org; Fri, 07 May 2004 01: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 BAA11644
	for <ietf@ietf.org>; Fri, 7 May 2004 01:07: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 1BLxa7-0002eL-R4
	for ietf@ietf.org; Fri, 07 May 2004 01:07:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLxZ7-0002F1-00
	for ietf@ietf.org; Fri, 07 May 2004 01:06:29 -0400
Received: from web8310.mail.in.yahoo.com ([203.199.122.10])
	by ietf-mx with smtp (Exim 4.12)
	id 1BLxYd-0001p1-00
	for ietf@ietf.org; Fri, 07 May 2004 01:06:00 -0400
Message-ID: <20040507050500.611.qmail@web8310.mail.in.yahoo.com>
Received: from [61.95.177.131] by web8310.mail.in.yahoo.com via HTTP; Fri, 07 May 2004 06:05:00 BST
Date: Fri, 7 May 2004 06:05:00 +0100 (BST)
From: =?iso-8859-1?q?Girish=20Kamath?= <girishnk75@yahoo.co.in>
Subject: Scope Issue
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1649506079-1083906300=:341"
Content-Transfer-Encoding: 8bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=1.3 required=5.0 tests=AWL,FROM_ENDS_IN_NUMS,
	HTML_20_30,HTML_MESSAGE 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>

--0-1649506079-1083906300=:341
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Hello,
      For Neighbor Discovery messages, is it mandatory that the scope of the source and destination address should match?
If i have just a link-local unicast address on a node A connected to another node B which has global unicast addresses configured, can i form a ND message with source address as link-local unicast address and destination address as global unicast address when sending a ND packet from A to B.
 
-- Girish



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

<DIV>
<DIV>Hello,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; For Neighbor Discovery messages, is it mandatory that the scope of the source and destination address should match?<BR>If i have just a link-local unicast address on a node A connected to another node B which has global unicast addresses configured, can i form a ND message with source address as link-local unicast address and destination address as global unicast address when sending a ND packet from A to B.</DIV>
<DIV>&nbsp;</DIV>
<DIV>-- Girish<BR></DIV></DIV><p><font face=arial size=-1>
<a href="http://in.rd.yahoo.com/specials/mailtg/*http://yahoo.shaadi.com/india-matrimony/" target="_blank">
<b>Yahoo! India Matrimony</a>:</b> Find your partner 
<a href="http://in.rd.yahoo.com/specials/mailtg2/*http://yahoo.shaadi.com/india-matrimony/community.php" target="_blank">online</a>.</font>
--0-1649506079-1083906300=:341--

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



From ietf-admin@ietf.org  Fri May  7 01:22: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 BAA12093
	for <ietf-archive@ietf.org>; Fri, 7 May 2004 01:22: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 1BLxoj-0000yn-Go
	for ietf-archive@ietf.org; Fri, 07 May 2004 01:22:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLxnl-0000Y6-00
	for ietf-archive@ietf.org; Fri, 07 May 2004 01:21:38 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLxn5-00007U-00
	for ietf-archive@ietf.org; Fri, 07 May 2004 01:20:55 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLxeY-0004oJ-G8; Fri, 07 May 2004 01:12:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLxaA-0002tM-Pu
	for ietf@optimus.ietf.org; Fri, 07 May 2004 01: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 BAA11644
	for <ietf@ietf.org>; Fri, 7 May 2004 01:07: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 1BLxa7-0002eL-R4
	for ietf@ietf.org; Fri, 07 May 2004 01:07:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLxZ7-0002F1-00
	for ietf@ietf.org; Fri, 07 May 2004 01:06:29 -0400
Received: from web8310.mail.in.yahoo.com ([203.199.122.10])
	by ietf-mx with smtp (Exim 4.12)
	id 1BLxYd-0001p1-00
	for ietf@ietf.org; Fri, 07 May 2004 01:06:00 -0400
Message-ID: <20040507050500.611.qmail@web8310.mail.in.yahoo.com>
Received: from [61.95.177.131] by web8310.mail.in.yahoo.com via HTTP; Fri, 07 May 2004 06:05:00 BST
Date: Fri, 7 May 2004 06:05:00 +0100 (BST)
From: =?iso-8859-1?q?Girish=20Kamath?= <girishnk75@yahoo.co.in>
Subject: Scope Issue
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1649506079-1083906300=:341"
Content-Transfer-Encoding: 8bit
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=1.3 required=5.0 tests=AWL,FROM_ENDS_IN_NUMS,
	HTML_20_30,HTML_MESSAGE autolearn=no version=2.60

--0-1649506079-1083906300=:341
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Hello,
      For Neighbor Discovery messages, is it mandatory that the scope of the source and destination address should match?
If i have just a link-local unicast address on a node A connected to another node B which has global unicast addresses configured, can i form a ND message with source address as link-local unicast address and destination address as global unicast address when sending a ND packet from A to B.
 
-- Girish



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

<DIV>
<DIV>Hello,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; For Neighbor Discovery messages, is it mandatory that the scope of the source and destination address should match?<BR>If i have just a link-local unicast address on a node A connected to another node B which has global unicast addresses configured, can i form a ND message with source address as link-local unicast address and destination address as global unicast address when sending a ND packet from A to B.</DIV>
<DIV>&nbsp;</DIV>
<DIV>-- Girish<BR></DIV></DIV><p><font face=arial size=-1>
<a href="http://in.rd.yahoo.com/specials/mailtg/*http://yahoo.shaadi.com/india-matrimony/" target="_blank">
<b>Yahoo! India Matrimony</a>:</b> Find your partner 
<a href="http://in.rd.yahoo.com/specials/mailtg2/*http://yahoo.shaadi.com/india-matrimony/community.php" target="_blank">online</a>.</font>
--0-1649506079-1083906300=:341--

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


From ietf-admin@ietf.org  Fri May  7 01:34:43 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA12684
	for <ietf-archive@ietf.org>; Fri, 7 May 2004 01:34: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 1BLy0Q-00063s-K1
	for ietf-archive@ietf.org; Fri, 07 May 2004 01:34:42 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLxzi-0005dR-00
	for ietf-archive@ietf.org; Fri, 07 May 2004 01:33:58 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLxyr-0005BR-00
	for ietf-archive@ietf.org; Fri, 07 May 2004 01:33:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLxs2-0000Gh-8q; Fri, 07 May 2004 01:26:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLxod-0007XY-T1
	for ietf@optimus.ietf.org; Fri, 07 May 2004 01:22: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 BAA12048
	for <ietf@ietf.org>; Fri, 7 May 2004 01:22:29 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLxoa-0000xS-DC
	for ietf@ietf.org; Fri, 07 May 2004 01:22:28 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLxna-0000WM-00
	for ietf@ietf.org; Fri, 07 May 2004 01:21:27 -0400
Received: from bonn.shuttle.de ([194.95.249.247])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLxme-00005T-00
	for ietf@ietf.org; Fri, 07 May 2004 01:20:28 -0400
Received: from uranus (p45.b.shuttle.de [194.95.246.45])
	by bonn.shuttle.de (Postfix) with ESMTP
	id CF2496C1CB; Fri,  7 May 2004 07:20:21 +0200 (CEST)
Content-Type: text/plain;
  charset="us-ascii"
From: Thomas Ackermann <t.ackermann@cats.mol.shuttle.de>
To: ietf@ietf.org
Subject: [Sip] NOTIFY on call transfer procedure
Date: Fri, 7 May 2004 06:55:45 +0200
User-Agent: KMail/1.4.3
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200405070655.45346.t.ackermann@cats.mol.shuttle.de>
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

Hi all,

can anybody tell me why the transfer procedure needs NOTIFY message
with application/sipfrag message body?

Why not simply keep the REFER transaction open by sending:
 - a provisional response instead of the 202/Accepted and
 - a final 200/OK response instead of NOTIFY(200 OK) ?
Just like the INVITE transaction with all its intermediate responses.

Or even more simple:
The Transferee sends the BYE by itself instead of asking the Transferor
to terminate the call?

Do you know the reason why the NOTIFY transaction has been added to
call transfer procedure?

Thanks for your help,
Thomas

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


From exim@www1.ietf.org  Fri May  7 01:41: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 BAA12989
	for <ietf-archive@odin.ietf.org>; Fri, 7 May 2004 01:41: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 1BLxyt-0002G1-TZ
	for ietf-archive@odin.ietf.org; Fri, 07 May 2004 01:33:08 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i475X7ZF008640
	for ietf-archive@odin.ietf.org; Fri, 7 May 2004 01: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 1BLxs2-0000Gh-8q; Fri, 07 May 2004 01:26:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLxod-0007XY-T1
	for ietf@optimus.ietf.org; Fri, 07 May 2004 01:22: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 BAA12048
	for <ietf@ietf.org>; Fri, 7 May 2004 01:22:29 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLxoa-0000xS-DC
	for ietf@ietf.org; Fri, 07 May 2004 01:22:28 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLxna-0000WM-00
	for ietf@ietf.org; Fri, 07 May 2004 01:21:27 -0400
Received: from bonn.shuttle.de ([194.95.249.247])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLxme-00005T-00
	for ietf@ietf.org; Fri, 07 May 2004 01:20:28 -0400
Received: from uranus (p45.b.shuttle.de [194.95.246.45])
	by bonn.shuttle.de (Postfix) with ESMTP
	id CF2496C1CB; Fri,  7 May 2004 07:20:21 +0200 (CEST)
Content-Type: text/plain;
  charset="us-ascii"
From: Thomas Ackermann <t.ackermann@cats.mol.shuttle.de>
To: ietf@ietf.org
Subject: [Sip] NOTIFY on call transfer procedure
Date: Fri, 7 May 2004 06:55:45 +0200
User-Agent: KMail/1.4.3
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200405070655.45346.t.ackermann@cats.mol.shuttle.de>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-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

Hi all,

can anybody tell me why the transfer procedure needs NOTIFY message
with application/sipfrag message body?

Why not simply keep the REFER transaction open by sending:
 - a provisional response instead of the 202/Accepted and
 - a final 200/OK response instead of NOTIFY(200 OK) ?
Just like the INVITE transaction with all its intermediate responses.

Or even more simple:
The Transferee sends the BYE by itself instead of asking the Transferor
to terminate the call?

Do you know the reason why the NOTIFY transaction has been added to
call transfer procedure?

Thanks for your help,
Thomas

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



From ietf-admin@ietf.org  Fri May  7 10:33:57 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26194
	for <ietf-archive@ietf.org>; Fri, 7 May 2004 10:33: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 1BM6QJ-00007g-Ao
	for ietf-archive@ietf.org; Fri, 07 May 2004 10:33:59 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BM6P8-0007Pc-00
	for ietf-archive@ietf.org; Fri, 07 May 2004 10:32:47 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BM6Nz-0006bP-00
	for ietf-archive@ietf.org; Fri, 07 May 2004 10:31:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BM5vf-0000zD-GF; Fri, 07 May 2004 10:02:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BM3tO-0000jU-LJ
	for ietf@optimus.ietf.org; Fri, 07 May 2004 07:51: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 HAA16928
	for <ietf@ietf.org>; Fri, 7 May 2004 07:51:48 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BM3tN-0007Ku-NR
	for ietf@ietf.org; Fri, 07 May 2004 07:51:49 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BM3sT-0006vO-00
	for ietf@ietf.org; Fri, 07 May 2004 07:50:53 -0400
Received: from web50408.mail.yahoo.com ([206.190.38.73])
	by ietf-mx with smtp (Exim 4.12)
	id 1BM3rz-0006Ux-00
	for ietf@ietf.org; Fri, 07 May 2004 07:50:23 -0400
Message-ID: <20040507114952.9550.qmail@web50408.mail.yahoo.com>
Received: from [61.1.144.70] by web50408.mail.yahoo.com via HTTP; Fri, 07 May 2004 04:49:52 PDT
Date: Fri, 7 May 2004 04:49:52 -0700 (PDT)
From: Rajat <myself_rajat@yahoo.com>
Subject: Problem of blocking ICMP packets
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-540255691-1083930592=:9429"
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=HTML_MESSAGE autolearn=no 
	version=2.60

--0-540255691-1083930592=:9429
Content-Type: text/plain; charset=us-ascii

Dear All,
I am in process of implementing Path MTU detection technique. So for that I have to send ICMP ECHO request packets to destination host, and process the received ICMP ECHO reply packets.
I read that the ICMP server is embedded in the kernel of OS itself, so there is no need to write server code at all. So for sending and receiving of ICMP packets we will use raw sockets without specifying any port number.
But in between the network, some routers have some firewall configuration so that they will simply drop any incomming ICMP packet without sending any response to the sender. Hence originating host will not be aware of the status of destination host.
These firewall settings are due to some attacks like Ping of deth, Denial of request etc.
Can any one provide me any solution to overcome this problem. 
 
Thanks in advance.

		
---------------------------------
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs 
--0-540255691-1083930592=:9429
Content-Type: text/html; charset=us-ascii

<DIV>Dear All,</DIV>
<DIV>I am in process of implementing Path MTU detection technique. So for that I have to send ICMP ECHO request packets to destination host, and process the received ICMP ECHO reply packets.</DIV>
<DIV>I read that the ICMP server is embedded in the kernel of OS itself, so there is no need to write server code at all. So for sending and receiving of ICMP packets we will use raw sockets without specifying any port number.</DIV>
<DIV>But in between the network, some routers have some firewall configuration so that they will simply drop any incomming ICMP packet without sending any response to the sender. Hence originating host will not be aware of the status of destination host.<BR>These firewall settings are due to some attacks like Ping of deth, Denial of request etc.</DIV>
<DIV>Can any one provide me any solution to overcome this problem. </DIV>
<DIV>&nbsp;</DIV>
<DIV>Thanks in advance.</DIV><p>
		<hr size=1><font face=arial size=-1>Do you Yahoo!?<br><a href="http://pa.yahoo.com/*http://us.rd.yahoo.com/hotjobs/hotjobs_mail_signature_footer_textlink/evt=23983/*http://hotjobs.sweepstakes.yahoo.com/careermakeover">Win a $20,000 Career Makeover at Yahoo! HotJobs </a>
--0-540255691-1083930592=:9429--

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


From ietf-admin@ietf.org  Fri May  7 10:40: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 KAA26898
	for <ietf-archive@ietf.org>; Fri, 7 May 2004 10:40: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 1BM6Wq-0002sd-DC
	for ietf-archive@ietf.org; Fri, 07 May 2004 10:40:44 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BM6VD-0001yS-00
	for ietf-archive@ietf.org; Fri, 07 May 2004 10:39:03 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BM6Tg-0001Bp-00
	for ietf-archive@ietf.org; Fri, 07 May 2004 10:37:28 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BM5w1-0001M1-F3; Fri, 07 May 2004 10:02:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BM4gf-00011I-Tk
	for ietf@optimus.ietf.org; Fri, 07 May 2004 08:42:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18733
	for <ietf@ietf.org>; Fri, 7 May 2004 08:42: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 1BM4ge-00059u-H8
	for ietf@ietf.org; Fri, 07 May 2004 08:42:44 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BM4g3-0004YE-00
	for ietf@ietf.org; Fri, 07 May 2004 08:42:08 -0400
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BM4e5-0003xR-00
	for ietf@ietf.org; Fri, 07 May 2004 08:40:05 -0400
Received: from f01v-35-74.d0.club-internet.fr ([212.195.246.74] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.24)
	id 1BM4dy-0000KG-5j; Fri, 07 May 2004 05:39:58 -0700
Message-Id: <6.0.1.1.2.20040507143636.03c5bd40@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Fri, 07 May 2004 14:39:56 +0200
To: Harald Tveit Alvestrand <harald@alvestrand.no>
From: jfcm <info@utel.net>
Subject: Re: Please note this update: IETF mission statement
Cc: ietf@ietf.org
In-Reply-To: <403325911.1083576973@localhost>
References: <364559378.1083538207@[192.168.1.63]>
 <Pine.GSO.4.58.0405031116050.18632@backin5.merit.edu>
 <403325911.1083576973@localhost>
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

I had to quickly explain IETF to political decision makers. I think I did 
not betray it in saying:
"The IETF is a place where technical consensus among coopetition can be 
reached in the areas of Internet legacy IP protocols, system and vision, 
with the participation of anyone motivated".
jfc



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


From exim@www1.ietf.org  Fri May  7 10:45:34 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 KAA27570
	for <ietf-archive@odin.ietf.org>; Fri, 7 May 2004 10:45:34 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BM6Ny-000853-HT
	for ietf-archive@odin.ietf.org; Fri, 07 May 2004 10:31:34 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i47EVYQc031060
	for ietf-archive@odin.ietf.org; Fri, 7 May 2004 10:31:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BM5vf-0000zD-GF; Fri, 07 May 2004 10:02:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BM3tO-0000jU-LJ
	for ietf@optimus.ietf.org; Fri, 07 May 2004 07:51: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 HAA16928
	for <ietf@ietf.org>; Fri, 7 May 2004 07:51:48 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BM3tN-0007Ku-NR
	for ietf@ietf.org; Fri, 07 May 2004 07:51:49 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BM3sT-0006vO-00
	for ietf@ietf.org; Fri, 07 May 2004 07:50:53 -0400
Received: from web50408.mail.yahoo.com ([206.190.38.73])
	by ietf-mx with smtp (Exim 4.12)
	id 1BM3rz-0006Ux-00
	for ietf@ietf.org; Fri, 07 May 2004 07:50:23 -0400
Message-ID: <20040507114952.9550.qmail@web50408.mail.yahoo.com>
Received: from [61.1.144.70] by web50408.mail.yahoo.com via HTTP; Fri, 07 May 2004 04:49:52 PDT
Date: Fri, 7 May 2004 04:49:52 -0700 (PDT)
From: Rajat <myself_rajat@yahoo.com>
Subject: Problem of blocking ICMP packets
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-540255691-1083930592=:9429"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=HTML_MESSAGE 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>

--0-540255691-1083930592=:9429
Content-Type: text/plain; charset=us-ascii

Dear All,
I am in process of implementing Path MTU detection technique. So for that I have to send ICMP ECHO request packets to destination host, and process the received ICMP ECHO reply packets.
I read that the ICMP server is embedded in the kernel of OS itself, so there is no need to write server code at all. So for sending and receiving of ICMP packets we will use raw sockets without specifying any port number.
But in between the network, some routers have some firewall configuration so that they will simply drop any incomming ICMP packet without sending any response to the sender. Hence originating host will not be aware of the status of destination host.
These firewall settings are due to some attacks like Ping of deth, Denial of request etc.
Can any one provide me any solution to overcome this problem. 
 
Thanks in advance.

		
---------------------------------
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs 
--0-540255691-1083930592=:9429
Content-Type: text/html; charset=us-ascii

<DIV>Dear All,</DIV>
<DIV>I am in process of implementing Path MTU detection technique. So for that I have to send ICMP ECHO request packets to destination host, and process the received ICMP ECHO reply packets.</DIV>
<DIV>I read that the ICMP server is embedded in the kernel of OS itself, so there is no need to write server code at all. So for sending and receiving of ICMP packets we will use raw sockets without specifying any port number.</DIV>
<DIV>But in between the network, some routers have some firewall configuration so that they will simply drop any incomming ICMP packet without sending any response to the sender. Hence originating host will not be aware of the status of destination host.<BR>These firewall settings are due to some attacks like Ping of deth, Denial of request etc.</DIV>
<DIV>Can any one provide me any solution to overcome this problem. </DIV>
<DIV>&nbsp;</DIV>
<DIV>Thanks in advance.</DIV><p>
		<hr size=1><font face=arial size=-1>Do you Yahoo!?<br><a href="http://pa.yahoo.com/*http://us.rd.yahoo.com/hotjobs/hotjobs_mail_signature_footer_textlink/evt=23983/*http://hotjobs.sweepstakes.yahoo.com/careermakeover">Win a $20,000 Career Makeover at Yahoo! HotJobs </a>
--0-540255691-1083930592=:9429--

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



From ietf-admin@ietf.org  Fri May  7 11:00:58 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29190
	for <ietf-archive@ietf.org>; Fri, 7 May 2004 11:00: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 1BM6qS-00054o-C3
	for ietf-archive@ietf.org; Fri, 07 May 2004 11:01:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BM6pQ-0004bj-00
	for ietf-archive@ietf.org; Fri, 07 May 2004 10:59:57 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BM6oL-00048R-00
	for ietf-archive@ietf.org; Fri, 07 May 2004 10:58:49 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BM6aF-0004ih-5i; Fri, 07 May 2004 10:44:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BM65q-0007eW-9T
	for ietf@optimus.ietf.org; Fri, 07 May 2004 10:12:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23916
	for <ietf@ietf.org>; Fri, 7 May 2004 10:12: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 1BM65n-0005cR-Rx
	for ietf@ietf.org; Fri, 07 May 2004 10:12:47 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BM64n-000599-00
	for ietf@ietf.org; Fri, 07 May 2004 10:11:45 -0400
Received: from sbcsmtp6.sbc.com ([144.160.20.36])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BM63r-0004Ha-00
	for ietf@ietf.org; Fri, 07 May 2004 10:10:48 -0400
Received: from sbc.com (localhost [127.0.0.1])
	by sbcsmtp6.sbc.com (8.12.10/8.12.10) with ESMTP id i47EAGbQ006085
	for <ietf@ietf.org>; Fri, 7 May 2004 10:10:17 -0400 (EDT)
Received: from MISOUT7MSGHUB02.ITServices.sbc.com (misout7msghub02.itservices.sbc.com [144.155.106.22])
	by sbcsmtp6.sbc.com (8.12.10/8.12.10) with ESMTP id i47EACxr006043
	for <ietf@ietf.org>; Fri, 7 May 2004 10:10:12 -0400 (EDT)
Received: from ilnort1msgusr01.ITServices.sbc.com ([144.158.5.100]) by MISOUT7MSGHUB02.ITServices.sbc.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Fri, 7 May 2004 10:10:11 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4343D.029AD356"
Subject: force to load models
Date: Fri, 7 May 2004 09:10:11 -0500
Message-ID: <81396B513EEFB64E94E96676D5187B7903DB4789@ilnort1msgusr01.itservices.sbc.com>
Thread-Topic: force to load models
Thread-Index: AcQ0PQEyYjH/0NlSTD2VkMsF72L1+Q==
From: "TABAKIS, ELEAS (AIT)" <et7563@sbc.com>
To: <ietf@ietf.org>
X-OriginalArrivalTime: 07 May 2004 14:10:11.0778 (UTC) FILETIME=[02CBDA20:01C4343D]
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=1.1 required=5.0 tests=AWL,FROM_ENDS_IN_NUMS,
	HTML_60_70,HTML_FONTCOLOR_RED,HTML_MESSAGE autolearn=no version=2.60

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4343D.029AD356
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

All,
I am looking to find examples of "Force to Load" models that apply to
professional engineering organizations. If the examples are industry
accepted practices all the better. If you reply, also indicate if you
are willing to spend a few minutes discussing the model.=20

Thank you in advance for any assistance you may offer.=20
=20
Thanks,
ET

"Talk Straight, Follow Through"
"Trust, Character, Commitment, Passion"



------_=_NextPart_001_01C4343D.029AD356
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.6487.1">
<TITLE>force to load models</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">All,</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">I am =
looking to find</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Arial">examples =
of</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT =
SIZE=3D2 FACE=3D"Arial">&#8220;</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Force to Load</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&#8221;</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial"> models that apply to =
professional engineering organizations</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Arial">If the</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">examples</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial"> are industry accepted =
practices all</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Arial">the</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial"> better.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Arial">If you reply, also =
indicate if you are willing to spend a few minutes discussing the model. =
</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Thank =
you in advance for any assistance you may offer. </FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial"></FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us">&nbsp;</SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"></SPAN><A NAME=3D""><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#FF0000" SIZE=3D2 =
FACE=3D"Arial">Thanks,</FONT></SPAN></A></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#FF0000" SIZE=3D2 =
FACE=3D"Arial">ET</FONT></SPAN></P>

<P ALIGN=3DLEFT><B><I><SPAN LANG=3D"en-us"><FONT COLOR=3D"#FF0000" =
SIZE=3D1 FACE=3D"Arial">&quot;Talk Straight, Follow =
Through&quot;</FONT></SPAN></I></B><SPAN =
LANG=3D"en-us"><B><I></I></B></SPAN><SPAN =
LANG=3D"en-us"><B><I></I></B></SPAN><B><I><SPAN =
LANG=3D"en-us"></SPAN></I></B></P>

<P ALIGN=3DLEFT><B><I><SPAN LANG=3D"en-us"><FONT COLOR=3D"#FF0000" =
SIZE=3D1 FACE=3D"Arial">&quot;Trust, Character, Commitment, =
Passion&quot;</FONT></SPAN></I></B></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"></SPAN></P>

</BODY>
</HTML>
------_=_NextPart_001_01C4343D.029AD356--

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


From exim@www1.ietf.org  Fri May  7 11:18:24 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 LAA00428
	for <ietf-archive@odin.ietf.org>; Fri, 7 May 2004 11:18: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 1BM6oN-0001t5-3G
	for ietf-archive@odin.ietf.org; Fri, 07 May 2004 10:58:51 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i47EwpSc007255
	for ietf-archive@odin.ietf.org; Fri, 7 May 2004 10:58:51 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BM6aF-0004ih-5i; Fri, 07 May 2004 10:44:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BM65q-0007eW-9T
	for ietf@optimus.ietf.org; Fri, 07 May 2004 10:12:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23916
	for <ietf@ietf.org>; Fri, 7 May 2004 10:12: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 1BM65n-0005cR-Rx
	for ietf@ietf.org; Fri, 07 May 2004 10:12:47 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BM64n-000599-00
	for ietf@ietf.org; Fri, 07 May 2004 10:11:45 -0400
Received: from sbcsmtp6.sbc.com ([144.160.20.36])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BM63r-0004Ha-00
	for ietf@ietf.org; Fri, 07 May 2004 10:10:48 -0400
Received: from sbc.com (localhost [127.0.0.1])
	by sbcsmtp6.sbc.com (8.12.10/8.12.10) with ESMTP id i47EAGbQ006085
	for <ietf@ietf.org>; Fri, 7 May 2004 10:10:17 -0400 (EDT)
Received: from MISOUT7MSGHUB02.ITServices.sbc.com (misout7msghub02.itservices.sbc.com [144.155.106.22])
	by sbcsmtp6.sbc.com (8.12.10/8.12.10) with ESMTP id i47EACxr006043
	for <ietf@ietf.org>; Fri, 7 May 2004 10:10:12 -0400 (EDT)
Received: from ilnort1msgusr01.ITServices.sbc.com ([144.158.5.100]) by MISOUT7MSGHUB02.ITServices.sbc.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Fri, 7 May 2004 10:10:11 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4343D.029AD356"
Subject: force to load models
Date: Fri, 7 May 2004 09:10:11 -0500
Message-ID: <81396B513EEFB64E94E96676D5187B7903DB4789@ilnort1msgusr01.itservices.sbc.com>
Thread-Topic: force to load models
Thread-Index: AcQ0PQEyYjH/0NlSTD2VkMsF72L1+Q==
From: "TABAKIS, ELEAS (AIT)" <et7563@sbc.com>
To: <ietf@ietf.org>
X-OriginalArrivalTime: 07 May 2004 14:10:11.0778 (UTC) FILETIME=[02CBDA20:01C4343D]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=1.1 required=5.0 tests=FROM_ENDS_IN_NUMS,HTML_70_80,
	HTML_FONTCOLOR_RED,HTML_MESSAGE 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.

------_=_NextPart_001_01C4343D.029AD356
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

All,
I am looking to find examples of "Force to Load" models that apply to
professional engineering organizations. If the examples are industry
accepted practices all the better. If you reply, also indicate if you
are willing to spend a few minutes discussing the model.=20

Thank you in advance for any assistance you may offer.=20
=20
Thanks,
ET

"Talk Straight, Follow Through"
"Trust, Character, Commitment, Passion"



------_=_NextPart_001_01C4343D.029AD356
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.6487.1">
<TITLE>force to load models</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">All,</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">I am =
looking to find</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Arial">examples =
of</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT =
SIZE=3D2 FACE=3D"Arial">&#8220;</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Force to Load</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&#8221;</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial"> models that apply to =
professional engineering organizations</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Arial">If the</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">examples</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial"> are industry accepted =
practices all</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Arial">the</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial"> better.</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"> <FONT SIZE=3D2 FACE=3D"Arial">If you reply, also =
indicate if you are willing to spend a few minutes discussing the model. =
</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Thank =
you in advance for any assistance you may offer. </FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial"></FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us">&nbsp;</SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"></SPAN><A NAME=3D""><SPAN =
LANG=3D"en-us"><FONT COLOR=3D"#FF0000" SIZE=3D2 =
FACE=3D"Arial">Thanks,</FONT></SPAN></A></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#FF0000" SIZE=3D2 =
FACE=3D"Arial">ET</FONT></SPAN></P>

<P ALIGN=3DLEFT><B><I><SPAN LANG=3D"en-us"><FONT COLOR=3D"#FF0000" =
SIZE=3D1 FACE=3D"Arial">&quot;Talk Straight, Follow =
Through&quot;</FONT></SPAN></I></B><SPAN =
LANG=3D"en-us"><B><I></I></B></SPAN><SPAN =
LANG=3D"en-us"><B><I></I></B></SPAN><B><I><SPAN =
LANG=3D"en-us"></SPAN></I></B></P>

<P ALIGN=3DLEFT><B><I><SPAN LANG=3D"en-us"><FONT COLOR=3D"#FF0000" =
SIZE=3D1 FACE=3D"Arial">&quot;Trust, Character, Commitment, =
Passion&quot;</FONT></SPAN></I></B></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"></SPAN></P>

</BODY>
</HTML>
------_=_NextPart_001_01C4343D.029AD356--

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



From ietf-admin@ietf.org  Fri May  7 12:27: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 MAA03834
	for <ietf-archive@ietf.org>; Fri, 7 May 2004 12:27: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 1BM8Bq-00044c-Fl
	for ietf-archive@ietf.org; Fri, 07 May 2004 12:27:10 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BM8Al-0003bi-00
	for ietf-archive@ietf.org; Fri, 07 May 2004 12:26:03 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BM89v-0003Ao-00
	for ietf-archive@ietf.org; Fri, 07 May 2004 12:25:11 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BM7qQ-0007yD-Qs; Fri, 07 May 2004 12:05:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BM7lO-0006L1-VP
	for ietf@optimus.ietf.org; Fri, 07 May 2004 11:59: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 LAA02617
	for <ietf@ietf.org>; Fri, 7 May 2004 11:59:47 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BM7lN-0007ne-Jb
	for ietf@ietf.org; Fri, 07 May 2004 11:59:49 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BM7kP-0007NG-00
	for ietf@ietf.org; Fri, 07 May 2004 11:58:50 -0400
Received: from [63.110.3.64] (helo=dyn-tx-arch-crash.dfw.dynamicsoft.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BM7jH-0006Xv-00
	for ietf@ietf.org; Fri, 07 May 2004 11:57:40 -0400
Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1])
	by dyn-tx-arch-crash.dfw.dynamicsoft.com (8.12.10/8.12.10) with ESMTP id i47Fv6Lp003887;
	Fri, 7 May 2004 10:57:06 -0500
Subject: Re: [Sip] NOTIFY on call transfer procedure
From: Robert Sparks <rsparks@dynamicsoft.com>
To: Thomas Ackermann <t.ackermann@cats.mol.shuttle.de>
Cc: ietf@ietf.org
In-Reply-To: <200405070655.45346.t.ackermann@cats.mol.shuttle.de>
References: <200405070655.45346.t.ackermann@cats.mol.shuttle.de>
Content-Type: text/plain
Message-Id: <1083945369.2161.46.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.5 (1.4.5-7) 
Date: Fri, 07 May 2004 10:56:09 -0500
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

Section 6 of RFC3515 calls out why REFER is constructed this way.

The root cause is the fixed length of any SIP non-INVITE transaction.
The approach you sketch won't work as provisional responses to 
non-INVITE requests do _not_ lengthen the transaction.

If you want a more detailed description, look at
http://www.ietf.org/internet-drafts/draft-sparks-sip-nit-problems-00.txt
and
http://www.ietf.org/internet-drafts/draft-sparks-sip-nit-actions-00.txt

RjS


On Thu, 2004-05-06 at 23:55, Thomas Ackermann wrote:
> Hi all,
> 
> can anybody tell me why the transfer procedure needs NOTIFY message
> with application/sipfrag message body?
> 
> Why not simply keep the REFER transaction open by sending:
>  - a provisional response instead of the 202/Accepted and
>  - a final 200/OK response instead of NOTIFY(200 OK) ?
> Just like the INVITE transaction with all its intermediate responses.
> 
> Or even more simple:
> The Transferee sends the BYE by itself instead of asking the Transferor
> to terminate the call?
> 
> Do you know the reason why the NOTIFY transaction has been added to
> call transfer procedure?
> 
> Thanks for your help,
> Thomas
> 
> _______________________________________________
> 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  Fri May  7 12:38:04 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 MAA04290
	for <ietf-archive@odin.ietf.org>; Fri, 7 May 2004 12:38: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 1BM89w-0007RD-C8
	for ietf-archive@odin.ietf.org; Fri, 07 May 2004 12:25:12 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i47GPCYP028574
	for ietf-archive@odin.ietf.org; Fri, 7 May 2004 12:25:12 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BM7qQ-0007yD-Qs; Fri, 07 May 2004 12:05:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BM7lO-0006L1-VP
	for ietf@optimus.ietf.org; Fri, 07 May 2004 11:59: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 LAA02617
	for <ietf@ietf.org>; Fri, 7 May 2004 11:59:47 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BM7lN-0007ne-Jb
	for ietf@ietf.org; Fri, 07 May 2004 11:59:49 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BM7kP-0007NG-00
	for ietf@ietf.org; Fri, 07 May 2004 11:58:50 -0400
Received: from [63.110.3.64] (helo=dyn-tx-arch-crash.dfw.dynamicsoft.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BM7jH-0006Xv-00
	for ietf@ietf.org; Fri, 07 May 2004 11:57:40 -0400
Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1])
	by dyn-tx-arch-crash.dfw.dynamicsoft.com (8.12.10/8.12.10) with ESMTP id i47Fv6Lp003887;
	Fri, 7 May 2004 10:57:06 -0500
Subject: Re: [Sip] NOTIFY on call transfer procedure
From: Robert Sparks <rsparks@dynamicsoft.com>
To: Thomas Ackermann <t.ackermann@cats.mol.shuttle.de>
Cc: ietf@ietf.org
In-Reply-To: <200405070655.45346.t.ackermann@cats.mol.shuttle.de>
References: <200405070655.45346.t.ackermann@cats.mol.shuttle.de>
Content-Type: text/plain
Message-Id: <1083945369.2161.46.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.5 (1.4.5-7) 
Date: Fri, 07 May 2004 10:56:09 -0500
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

Section 6 of RFC3515 calls out why REFER is constructed this way.

The root cause is the fixed length of any SIP non-INVITE transaction.
The approach you sketch won't work as provisional responses to 
non-INVITE requests do _not_ lengthen the transaction.

If you want a more detailed description, look at
http://www.ietf.org/internet-drafts/draft-sparks-sip-nit-problems-00.txt
and
http://www.ietf.org/internet-drafts/draft-sparks-sip-nit-actions-00.txt

RjS


On Thu, 2004-05-06 at 23:55, Thomas Ackermann wrote:
> Hi all,
> 
> can anybody tell me why the transfer procedure needs NOTIFY message
> with application/sipfrag message body?
> 
> Why not simply keep the REFER transaction open by sending:
>  - a provisional response instead of the 202/Accepted and
>  - a final 200/OK response instead of NOTIFY(200 OK) ?
> Just like the INVITE transaction with all its intermediate responses.
> 
> Or even more simple:
> The Transferee sends the BYE by itself instead of asking the Transferor
> to terminate the call?
> 
> Do you know the reason why the NOTIFY transaction has been added to
> call transfer procedure?
> 
> Thanks for your help,
> Thomas
> 
> _______________________________________________
> 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  Fri May  7 16:08: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 QAA17401
	for <ietf-archive@ietf.org>; Fri, 7 May 2004 16:08: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 1BMBdr-0000pm-SD
	for ietf-archive@ietf.org; Fri, 07 May 2004 16:08:19 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMBct-0000La-00
	for ietf-archive@ietf.org; Fri, 07 May 2004 16:07:20 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMBbu-0007fH-00
	for ietf-archive@ietf.org; Fri, 07 May 2004 16:06:18 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMBWo-0007OH-1V; Fri, 07 May 2004 16:01:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMBQ5-0005Ib-NH
	for ietf@optimus.ietf.org; Fri, 07 May 2004 15:54:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16737
	for <ietf@ietf.org>; Fri, 7 May 2004 15:54: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 1BMBQ4-0002Xn-2w
	for ietf@ietf.org; Fri, 07 May 2004 15:54:04 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMBP8-000288-00
	for ietf@ietf.org; Fri, 07 May 2004 15:53:06 -0400
Received: from mail1.microsoft.com ([131.107.3.125])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMBOS-0001WX-00
	for ietf@ietf.org; Fri, 07 May 2004 15:52:24 -0400
Received: from mail5.microsoft.com ([157.54.6.156]) by mail1.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Fri, 7 May 2004 12:54:18 -0700
Received: from inet-vrs-05.redmond.corp.microsoft.com ([157.54.6.157]) by mail5.microsoft.com with Microsoft SMTPSVC(6.0.3790.1039);
	 Fri, 7 May 2004 12:51:55 -0700
Received: from 157.54.5.25 by inet-vrs-05.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Fri, 07 May 2004 12:51:53 -0700
Received: from red-imc-01.redmond.corp.microsoft.com ([157.54.9.102]) by inet-hub-03.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Fri, 7 May 2004 12:51:36 -0700
Received: from win-imc-02.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.84]) by red-imc-01.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.1069);
	 Fri, 7 May 2004 12:51:52 -0700
Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com ([157.54.12.81]) by win-imc-02.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3790.1069);
	 Fri, 7 May 2004 12:51:51 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Problem of blocking ICMP packets
Date: Fri, 7 May 2004 12:51:56 -0700
Message-ID: <DAC3FCB50E31C54987CD10797DA511BA08EA129A@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: Problem of blocking ICMP packets
Thread-Index: AcQ0QFvdhRrhOc5oTp6Cha7NE7ASsgAK42Ng
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: "Rajat" <myself_rajat@yahoo.com>, <ietf@ietf.org>
X-OriginalArrivalTime: 07 May 2004 19:51:51.0882 (UTC) FILETIME=[BDCF7AA0:01C4346C]
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

> But in between the network, some routers have some firewall=20
> configuration so that they will simply drop any incomming ICMP=20
> packet without sending any response to the sender.=20

Not just routers. Many "host firewalls" will by default drop all
unsolicited ICMP packets. The rational is a variant of security by
obscurity: a host is more secure if its presence cannot be trivially
detected.

The old assumption used to be that if a host has an IP address, it can
receive pretty much any packet sent to that address. The practical
situation we have today is that if two hosts communicate over a given
protocol and port, they can receive packets from the same "five tuple"
but are not guaranteed to receive other packets. This has an important
consequence for many IETF designed protocols, including indeed path MTU
discovery.

-- Christian Huitema

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


From exim@www1.ietf.org  Fri May  7 16:11:57 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17548
	for <ietf-archive@odin.ietf.org>; Fri, 7 May 2004 16:11: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 1BMBbv-0000Tb-37
	for ietf-archive@odin.ietf.org; Fri, 07 May 2004 16:06:19 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i47K6JQ2001826
	for ietf-archive@odin.ietf.org; Fri, 7 May 2004 16:06:19 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMBWo-0007OH-1V; Fri, 07 May 2004 16:01:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMBQ5-0005Ib-NH
	for ietf@optimus.ietf.org; Fri, 07 May 2004 15:54:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16737
	for <ietf@ietf.org>; Fri, 7 May 2004 15:54: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 1BMBQ4-0002Xn-2w
	for ietf@ietf.org; Fri, 07 May 2004 15:54:04 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMBP8-000288-00
	for ietf@ietf.org; Fri, 07 May 2004 15:53:06 -0400
Received: from mail1.microsoft.com ([131.107.3.125])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMBOS-0001WX-00
	for ietf@ietf.org; Fri, 07 May 2004 15:52:24 -0400
Received: from mail5.microsoft.com ([157.54.6.156]) by mail1.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Fri, 7 May 2004 12:54:18 -0700
Received: from inet-vrs-05.redmond.corp.microsoft.com ([157.54.6.157]) by mail5.microsoft.com with Microsoft SMTPSVC(6.0.3790.1039);
	 Fri, 7 May 2004 12:51:55 -0700
Received: from 157.54.5.25 by inet-vrs-05.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Fri, 07 May 2004 12:51:53 -0700
Received: from red-imc-01.redmond.corp.microsoft.com ([157.54.9.102]) by inet-hub-03.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Fri, 7 May 2004 12:51:36 -0700
Received: from win-imc-02.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.84]) by red-imc-01.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.1069);
	 Fri, 7 May 2004 12:51:52 -0700
Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com ([157.54.12.81]) by win-imc-02.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3790.1069);
	 Fri, 7 May 2004 12:51:51 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Problem of blocking ICMP packets
Date: Fri, 7 May 2004 12:51:56 -0700
Message-ID: <DAC3FCB50E31C54987CD10797DA511BA08EA129A@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: Problem of blocking ICMP packets
Thread-Index: AcQ0QFvdhRrhOc5oTp6Cha7NE7ASsgAK42Ng
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: "Rajat" <myself_rajat@yahoo.com>, <ietf@ietf.org>
X-OriginalArrivalTime: 07 May 2004 19:51:51.0882 (UTC) FILETIME=[BDCF7AA0:01C4346C]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-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

> But in between the network, some routers have some firewall=20
> configuration so that they will simply drop any incomming ICMP=20
> packet without sending any response to the sender.=20

Not just routers. Many "host firewalls" will by default drop all
unsolicited ICMP packets. The rational is a variant of security by
obscurity: a host is more secure if its presence cannot be trivially
detected.

The old assumption used to be that if a host has an IP address, it can
receive pretty much any packet sent to that address. The practical
situation we have today is that if two hosts communicate over a given
protocol and port, they can receive packets from the same "five tuple"
but are not guaranteed to receive other packets. This has an important
consequence for many IETF designed protocols, including indeed path MTU
discovery.

-- Christian Huitema

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



From ietf-admin@ietf.org  Fri May  7 16:48: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 QAA19685
	for <ietf-archive@ietf.org>; Fri, 7 May 2004 16:48: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 1BMCGJ-0002sb-At
	for ietf-archive@ietf.org; Fri, 07 May 2004 16:48:03 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMCFI-0002R4-00
	for ietf-archive@ietf.org; Fri, 07 May 2004 16:47:01 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMCED-0001jX-00
	for ietf-archive@ietf.org; Fri, 07 May 2004 16:45:53 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMC8Y-0001kx-Jd; Fri, 07 May 2004 16:40:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMC1n-0008Pc-DA
	for ietf@optimus.ietf.org; Fri, 07 May 2004 16:33: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 QAA18925
	for <ietf@ietf.org>; Fri, 7 May 2004 16:33: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 1BMC1l-00043z-BE
	for ietf@ietf.org; Fri, 07 May 2004 16:33:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMC0o-0003df-00
	for ietf@ietf.org; Fri, 07 May 2004 16:32:03 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with smtp (Exim 4.12)
	id 1BMBzv-0003Dx-00
	for ietf@ietf.org; Fri, 07 May 2004 16:31:08 -0400
Received: (qmail 95251 invoked from network); 7 May 2004 20:32:39 -0000
Received: from yahoobb219178198119.bbtec.net (HELO necom830.hpcl.titech.ac.jp) (219.178.198.119)
  by necom830.hpcl.titech.ac.jp with SMTP; 7 May 2004 20:32:39 -0000
Message-ID: <409BF2F5.2080304@necom830.hpcl.titech.ac.jp>
Date: Sat, 08 May 2004 05:35:01 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: ja, en-us, en
MIME-Version: 1.0
To: Rajat <myself_rajat@yahoo.com>
CC: ietf@ietf.org
Subject: Re: Problem of blocking ICMP packets
References: <20040507114952.9550.qmail@web50408.mail.yahoo.com>
In-Reply-To: <20040507114952.9550.qmail@web50408.mail.yahoo.com>
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

Rajat wrote:

> Can any one provide me any solution to overcome this problem. 

In addition to PMTUD, you should have PMUTD availability
discovery that if it is discovered, say by persistent lack
of responses, that PMTUD is not working, you should turn off
PMTUD and just live with fragmentations.

I recommend that, to avoid long initial delay and intermediate
lack of communication after path changes of, PMTUD should turnd
off by default and should be activated only on extreme
conditions.

Further, it should be noted that PMTUD is so unreliable that
no applications rely on it, which means that even under
extreme conditions rational operators won't turn on PMTUD.

In short, forget PMTUD.
						Masataka Ohta



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


From exim@www1.ietf.org  Fri May  7 16:51:16 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19977
	for <ietf-archive@odin.ietf.org>; Fri, 7 May 2004 16:51: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 1BMCEE-00043I-GO
	for ietf-archive@odin.ietf.org; Fri, 07 May 2004 16:45:57 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i47Kjsd3015536
	for ietf-archive@odin.ietf.org; Fri, 7 May 2004 16:45:54 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMC8Y-0001kx-Jd; Fri, 07 May 2004 16:40:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMC1n-0008Pc-DA
	for ietf@optimus.ietf.org; Fri, 07 May 2004 16:33: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 QAA18925
	for <ietf@ietf.org>; Fri, 7 May 2004 16:33: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 1BMC1l-00043z-BE
	for ietf@ietf.org; Fri, 07 May 2004 16:33:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMC0o-0003df-00
	for ietf@ietf.org; Fri, 07 May 2004 16:32:03 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with smtp (Exim 4.12)
	id 1BMBzv-0003Dx-00
	for ietf@ietf.org; Fri, 07 May 2004 16:31:08 -0400
Received: (qmail 95251 invoked from network); 7 May 2004 20:32:39 -0000
Received: from yahoobb219178198119.bbtec.net (HELO necom830.hpcl.titech.ac.jp) (219.178.198.119)
  by necom830.hpcl.titech.ac.jp with SMTP; 7 May 2004 20:32:39 -0000
Message-ID: <409BF2F5.2080304@necom830.hpcl.titech.ac.jp>
Date: Sat, 08 May 2004 05:35:01 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: ja, en-us, en
MIME-Version: 1.0
To: Rajat <myself_rajat@yahoo.com>
CC: ietf@ietf.org
Subject: Re: Problem of blocking ICMP packets
References: <20040507114952.9550.qmail@web50408.mail.yahoo.com>
In-Reply-To: <20040507114952.9550.qmail@web50408.mail.yahoo.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: 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

Rajat wrote:

> Can any one provide me any solution to overcome this problem. 

In addition to PMTUD, you should have PMUTD availability
discovery that if it is discovered, say by persistent lack
of responses, that PMTUD is not working, you should turn off
PMTUD and just live with fragmentations.

I recommend that, to avoid long initial delay and intermediate
lack of communication after path changes of, PMTUD should turnd
off by default and should be activated only on extreme
conditions.

Further, it should be noted that PMTUD is so unreliable that
no applications rely on it, which means that even under
extreme conditions rational operators won't turn on PMTUD.

In short, forget PMTUD.
						Masataka Ohta



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



From ietf-admin@ietf.org  Fri May  7 17:26: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 RAA21823
	for <ietf-archive@ietf.org>; Fri, 7 May 2004 17:26: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 1BMCrI-0003l0-4K
	for ietf-archive@ietf.org; Fri, 07 May 2004 17:26:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMCqI-0003Ig-00
	for ietf-archive@ietf.org; Fri, 07 May 2004 17:25:15 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMCpI-0002rO-00
	for ietf-archive@ietf.org; Fri, 07 May 2004 17:24:12 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMCeV-0003Mj-Bw; Fri, 07 May 2004 17:13:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMCYL-0001Hu-K2
	for ietf@optimus.ietf.org; Fri, 07 May 2004 17:06: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 RAA20521
	for <ietf@ietf.org>; Fri, 7 May 2004 17:06: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 1BMCYJ-0002bH-5u
	for ietf@ietf.org; Fri, 07 May 2004 17:06:39 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMCVs-00020z-00
	for ietf@ietf.org; Fri, 07 May 2004 17:04:08 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMCUy-0001NQ-00
	for ietf@ietf.org; Fri, 07 May 2004 17:03:12 -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 i47L2p1C027359;
	Fri, 7 May 2004 23:02:52 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <DAC3FCB50E31C54987CD10797DA511BA08EA129A@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
References: <DAC3FCB50E31C54987CD10797DA511BA08EA129A@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <EDCBDFEE-A069-11D8-BE01-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: "'Internet Engineering Task Force'" <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: Problem of blocking ICMP packets
Date: Fri, 7 May 2004 23:03:02 +0200
To: "Christian Huitema" <huitema@windows.microsoft.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 7-mei-04, at 21:51, Christian Huitema wrote:

> The old assumption used to be that if a host has an IP address, it can
> receive pretty much any packet sent to that address. The practical
> situation we have today is that if two hosts communicate over a given
> protocol and port, they can receive packets from the same "five tuple"
> but are not guaranteed to receive other packets. This has an important
> consequence for many IETF designed protocols, including indeed path MTU
> discovery.

So you are saying that when a host sends out an IP packet with the DF 
bit set, it's ok for that host (or any system on the path to that host) 
to filter out ICMP "fragmentation needed but DF bit set" messages?

Filtering on protocol/port numbers is a broken concept. When are we 
going to take the time to come up with a *real* security architecture? 
One that allows hosts to receive wanted packets and reject unwanted 
ones, rather than the current one where any correlation to whether a 
packet is wanted and whether it's rejected seems coincidental at best? 
One that at least entertains the possibility of doing something about 
denial of service attacks? And, last but not least, one that allows 
reasonable protocols, carrying desired communication, to function 
without undue breakage?


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


From exim@www1.ietf.org  Fri May  7 17:30: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 RAA22019
	for <ietf-archive@odin.ietf.org>; Fri, 7 May 2004 17:30: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 1BMCpL-0006Ne-42
	for ietf-archive@odin.ietf.org; Fri, 07 May 2004 17:24:15 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i47LOFc7024269
	for ietf-archive@odin.ietf.org; Fri, 7 May 2004 17:24:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMCeV-0003Mj-Bw; Fri, 07 May 2004 17:13:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMCYL-0001Hu-K2
	for ietf@optimus.ietf.org; Fri, 07 May 2004 17:06: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 RAA20521
	for <ietf@ietf.org>; Fri, 7 May 2004 17:06: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 1BMCYJ-0002bH-5u
	for ietf@ietf.org; Fri, 07 May 2004 17:06:39 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMCVs-00020z-00
	for ietf@ietf.org; Fri, 07 May 2004 17:04:08 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMCUy-0001NQ-00
	for ietf@ietf.org; Fri, 07 May 2004 17:03:12 -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 i47L2p1C027359;
	Fri, 7 May 2004 23:02:52 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <DAC3FCB50E31C54987CD10797DA511BA08EA129A@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
References: <DAC3FCB50E31C54987CD10797DA511BA08EA129A@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <EDCBDFEE-A069-11D8-BE01-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: "'Internet Engineering Task Force'" <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: Problem of blocking ICMP packets
Date: Fri, 7 May 2004 23:03:02 +0200
To: "Christian Huitema" <huitema@windows.microsoft.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 7-mei-04, at 21:51, Christian Huitema wrote:

> The old assumption used to be that if a host has an IP address, it can
> receive pretty much any packet sent to that address. The practical
> situation we have today is that if two hosts communicate over a given
> protocol and port, they can receive packets from the same "five tuple"
> but are not guaranteed to receive other packets. This has an important
> consequence for many IETF designed protocols, including indeed path MTU
> discovery.

So you are saying that when a host sends out an IP packet with the DF 
bit set, it's ok for that host (or any system on the path to that host) 
to filter out ICMP "fragmentation needed but DF bit set" messages?

Filtering on protocol/port numbers is a broken concept. When are we 
going to take the time to come up with a *real* security architecture? 
One that allows hosts to receive wanted packets and reject unwanted 
ones, rather than the current one where any correlation to whether a 
packet is wanted and whether it's rejected seems coincidental at best? 
One that at least entertains the possibility of doing something about 
denial of service attacks? And, last but not least, one that allows 
reasonable protocols, carrying desired communication, to function 
without undue breakage?


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



From ietf-admin@ietf.org  Fri May  7 21:21:20 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02652
	for <ietf-archive@ietf.org>; Fri, 7 May 2004 21:21:20 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BMGWm-0003E1-JT
	for ietf-archive@ietf.org; Fri, 07 May 2004 21:21:20 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMGVq-0002me-00
	for ietf-archive@ietf.org; Fri, 07 May 2004 21:20:23 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMGV2-0002M3-00
	for ietf-archive@ietf.org; Fri, 07 May 2004 21:19:32 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMGQh-0000DA-AX; Fri, 07 May 2004 21: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 1BMGOA-0007tS-6Q
	for ietf@optimus.ietf.org; Fri, 07 May 2004 21:12:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02323
	for <ietf@ietf.org>; Fri, 7 May 2004 21:12: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 1BMGO7-00076L-FQ
	for ietf@ietf.org; Fri, 07 May 2004 21:12:23 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMGN3-0006fD-00
	for ietf@ietf.org; Fri, 07 May 2004 21:11:17 -0400
Received: from 99.cust35.nsw.dsl.ozemail.com.au ([203.103.114.99] helo=nosense.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMGM9-0005ou-00
	for ietf@ietf.org; Fri, 07 May 2004 21:10:22 -0400
Received: from Dupy2.nosense.org (localhost.localdomain [127.0.0.1])
	by nosense.org (Postfix) with SMTP
	id 29E0A3F02A; Sat,  8 May 2004 10:42:31 +0930 (CST)
Date: Sat, 8 May 2004 10:42:30 +0930
From: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Cc: huitema@windows.microsoft.com, ietf@ietf.org
Subject: Re: Problem of blocking ICMP packets
Message-Id: <20040508104230.7a701b2f.ietf@130c04165a5b40404e4440445758487a.nosense.org>
In-Reply-To: <EDCBDFEE-A069-11D8-BE01-000A95CD987A@muada.com>
References: <DAC3FCB50E31C54987CD10797DA511BA08EA129A@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
	<EDCBDFEE-A069-11D8-BE01-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

On Fri, 7 May 2004 23:03:02 +0200
Iljitsch van Beijnum <iljitsch@muada.com> wrote:

> On 7-mei-04, at 21:51, Christian Huitema wrote:
> 
> > The old assumption used to be that if a host has an IP
> > address, it can receive pretty much any packet sent to that
> > address. The practical situation we have today is that if two
> > hosts communicate over a given protocol and port, they can
> > receive packets from the same "five tuple" but are not
> > guaranteed to receive other packets. This has an important
> > consequence for many IETF designed protocols, including
> > indeed path MTU discovery.
> 
> So you are saying that when a host sends out an IP packet with
> the DF bit set, it's ok for that host (or any system on the
> path to that host) to filter out ICMP "fragmentation needed but
> DF bit set" messages?
> 
> Filtering on protocol/port numbers is a broken concept. When
> are we going to take the time to come up with a *real* security
> architecture? One that allows hosts to receive wanted packets
> and reject unwanted ones,

I've only read the abstract, however Steve Bellovin's
"Distributed Firewalls"
(http://www.research.att.com/~smb/papers/distfw.html) seems to
suggest exactly that.

Interestingly, with all the recent attacks on Microsoft software,
they seem to be going down this distributed firewalls path, where
each host has a firewall. I'm not sure if they are aware of
Steve's paper, or whether it is a result of these worms almost
always seeming to be being able to bypass any network based
security in place anyway. I'd suspect the latter.

Linux and other OSs have already have firewalls built in, so
maybe we are seeing an unplanned and evolutionary transition to
this model.

 rather than the current one where any
> correlation to whether a packet is wanted and whether it's
> rejected seems coincidental at best? One that at least
> entertains the possibility of doing something about denial of
> service attacks? And, last but not least, one that allows
> reasonable protocols, carrying desired communication, to
> function without undue breakage?
>

I've understood that what you have described is the end-goal
of end-to-end, opportunistic encryption and authentication ie.
IPsec. Once the network can't tell what type of traffic it is,
ie. the port numbers (or protocol numbers if IPsec is run in
tunnel mode), these network based firewalls will be useless, and
hopefully will be turned off.

That wouldn't necessarily remedy denial of service attacks
though. I think denial of service attacks will always be possible
if entities can issue traffic to the network in an unregulated or
unidentified manner.

An "IPsec" only Internet would provide a disincentive to DoS, as
I'd presume that it implies that end-points are uniquely
identified, which allows responsibility for these attacks to be
attributed. That may not be a world we want to live in though as
anonimity in communications can also be a useful privacy feature.

In a few respects, DoS attacks and Spam are similar - they rely
on or assume near or absolute source anonimity, and very low
costs of transmission. If, or hopefully when, any solutions are
found to the spam problem, the fundamental methods or techniques
may be able to be applied to DoS attacks.

Regards,
Mark.

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


From exim@www1.ietf.org  Fri May  7 21:25: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 VAA02818
	for <ietf-archive@odin.ietf.org>; Fri, 7 May 2004 21:25: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 1BMGV4-0001SH-91
	for ietf-archive@odin.ietf.org; Fri, 07 May 2004 21:19:34 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i481JYIA005533
	for ietf-archive@odin.ietf.org; Fri, 7 May 2004 21:19:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMGQh-0000DA-AX; Fri, 07 May 2004 21: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 1BMGOA-0007tS-6Q
	for ietf@optimus.ietf.org; Fri, 07 May 2004 21:12:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02323
	for <ietf@ietf.org>; Fri, 7 May 2004 21:12: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 1BMGO7-00076L-FQ
	for ietf@ietf.org; Fri, 07 May 2004 21:12:23 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMGN3-0006fD-00
	for ietf@ietf.org; Fri, 07 May 2004 21:11:17 -0400
Received: from 99.cust35.nsw.dsl.ozemail.com.au ([203.103.114.99] helo=nosense.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMGM9-0005ou-00
	for ietf@ietf.org; Fri, 07 May 2004 21:10:22 -0400
Received: from Dupy2.nosense.org (localhost.localdomain [127.0.0.1])
	by nosense.org (Postfix) with SMTP
	id 29E0A3F02A; Sat,  8 May 2004 10:42:31 +0930 (CST)
Date: Sat, 8 May 2004 10:42:30 +0930
From: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Cc: huitema@windows.microsoft.com, ietf@ietf.org
Subject: Re: Problem of blocking ICMP packets
Message-Id: <20040508104230.7a701b2f.ietf@130c04165a5b40404e4440445758487a.nosense.org>
In-Reply-To: <EDCBDFEE-A069-11D8-BE01-000A95CD987A@muada.com>
References: <DAC3FCB50E31C54987CD10797DA511BA08EA129A@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
	<EDCBDFEE-A069-11D8-BE01-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

On Fri, 7 May 2004 23:03:02 +0200
Iljitsch van Beijnum <iljitsch@muada.com> wrote:

> On 7-mei-04, at 21:51, Christian Huitema wrote:
> 
> > The old assumption used to be that if a host has an IP
> > address, it can receive pretty much any packet sent to that
> > address. The practical situation we have today is that if two
> > hosts communicate over a given protocol and port, they can
> > receive packets from the same "five tuple" but are not
> > guaranteed to receive other packets. This has an important
> > consequence for many IETF designed protocols, including
> > indeed path MTU discovery.
> 
> So you are saying that when a host sends out an IP packet with
> the DF bit set, it's ok for that host (or any system on the
> path to that host) to filter out ICMP "fragmentation needed but
> DF bit set" messages?
> 
> Filtering on protocol/port numbers is a broken concept. When
> are we going to take the time to come up with a *real* security
> architecture? One that allows hosts to receive wanted packets
> and reject unwanted ones,

I've only read the abstract, however Steve Bellovin's
"Distributed Firewalls"
(http://www.research.att.com/~smb/papers/distfw.html) seems to
suggest exactly that.

Interestingly, with all the recent attacks on Microsoft software,
they seem to be going down this distributed firewalls path, where
each host has a firewall. I'm not sure if they are aware of
Steve's paper, or whether it is a result of these worms almost
always seeming to be being able to bypass any network based
security in place anyway. I'd suspect the latter.

Linux and other OSs have already have firewalls built in, so
maybe we are seeing an unplanned and evolutionary transition to
this model.

 rather than the current one where any
> correlation to whether a packet is wanted and whether it's
> rejected seems coincidental at best? One that at least
> entertains the possibility of doing something about denial of
> service attacks? And, last but not least, one that allows
> reasonable protocols, carrying desired communication, to
> function without undue breakage?
>

I've understood that what you have described is the end-goal
of end-to-end, opportunistic encryption and authentication ie.
IPsec. Once the network can't tell what type of traffic it is,
ie. the port numbers (or protocol numbers if IPsec is run in
tunnel mode), these network based firewalls will be useless, and
hopefully will be turned off.

That wouldn't necessarily remedy denial of service attacks
though. I think denial of service attacks will always be possible
if entities can issue traffic to the network in an unregulated or
unidentified manner.

An "IPsec" only Internet would provide a disincentive to DoS, as
I'd presume that it implies that end-points are uniquely
identified, which allows responsibility for these attacks to be
attributed. That may not be a world we want to live in though as
anonimity in communications can also be a useful privacy feature.

In a few respects, DoS attacks and Spam are similar - they rely
on or assume near or absolute source anonimity, and very low
costs of transmission. If, or hopefully when, any solutions are
found to the spam problem, the fundamental methods or techniques
may be able to be applied to DoS attacks.

Regards,
Mark.

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



From ietf-admin@ietf.org  Fri May  7 22:17: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 WAA04781
	for <ietf-archive@ietf.org>; Fri, 7 May 2004 22:17:36 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BMHPF-00041M-OA
	for ietf-archive@ietf.org; Fri, 07 May 2004 22:17:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMHOC-0003XH-00
	for ietf-archive@ietf.org; Fri, 07 May 2004 22:16:33 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMHNC-000359-00
	for ietf-archive@ietf.org; Fri, 07 May 2004 22:15:30 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMHF2-0005QS-Fp; Fri, 07 May 2004 22:07:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMHCO-0004sh-Vg
	for ietf@optimus.ietf.org; Fri, 07 May 2004 22:04: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 WAA04278
	for <ietf@ietf.org>; Fri, 7 May 2004 22:04: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 1BMHCL-00068F-OE
	for ietf@ietf.org; Fri, 07 May 2004 22:04:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMHBQ-0005gi-00
	for ietf@ietf.org; Fri, 07 May 2004 22:03:21 -0400
Received: from 99.cust35.nsw.dsl.ozemail.com.au ([203.103.114.99] helo=nosense.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMHAB-0004pM-00
	for ietf@ietf.org; Fri, 07 May 2004 22:02:03 -0400
Received: from Dupy2.nosense.org (localhost.localdomain [127.0.0.1])
	by nosense.org (Postfix) with SMTP
	id 8A2B33F02A; Sat,  8 May 2004 11:34:15 +0930 (CST)
Date: Sat, 8 May 2004 11:34:15 +0930
From: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
To: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
Cc: iljitsch@muada.com, huitema@windows.microsoft.com, ietf@ietf.org
Subject: Oops, quote in the wrong place (Re: Problem of blocking ICMP
 packets)
Message-Id: <20040508113415.5bc10fd3.ietf@130c04165a5b40404e4440445758487a.nosense.org>
In-Reply-To: <20040508104230.7a701b2f.ietf@130c04165a5b40404e4440445758487a.nosense.org>
References: <DAC3FCB50E31C54987CD10797DA511BA08EA129A@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
	<EDCBDFEE-A069-11D8-BE01-000A95CD987A@muada.com>
	<20040508104230.7a701b2f.ietf@130c04165a5b40404e4440445758487a.nosense.org>
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

On Sat, 8 May 2004 10:42:30 +0930
Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
wrote:

> On Fri, 7 May 2004 23:03:02 +0200

> 
> An "IPsec" only Internet would provide a disincentive to DoS,
> as

Should be "IPsec only" Internet.


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


From exim@www1.ietf.org  Fri May  7 22:18: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 WAA04836
	for <ietf-archive@odin.ietf.org>; Fri, 7 May 2004 22:18: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 1BMHNE-0008Qp-S5
	for ietf-archive@odin.ietf.org; Fri, 07 May 2004 22:15:33 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i482FW0d032253
	for ietf-archive@odin.ietf.org; Fri, 7 May 2004 22:15:32 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMHF2-0005QS-Fp; Fri, 07 May 2004 22:07:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMHCO-0004sh-Vg
	for ietf@optimus.ietf.org; Fri, 07 May 2004 22:04: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 WAA04278
	for <ietf@ietf.org>; Fri, 7 May 2004 22:04: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 1BMHCL-00068F-OE
	for ietf@ietf.org; Fri, 07 May 2004 22:04:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMHBQ-0005gi-00
	for ietf@ietf.org; Fri, 07 May 2004 22:03:21 -0400
Received: from 99.cust35.nsw.dsl.ozemail.com.au ([203.103.114.99] helo=nosense.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMHAB-0004pM-00
	for ietf@ietf.org; Fri, 07 May 2004 22:02:03 -0400
Received: from Dupy2.nosense.org (localhost.localdomain [127.0.0.1])
	by nosense.org (Postfix) with SMTP
	id 8A2B33F02A; Sat,  8 May 2004 11:34:15 +0930 (CST)
Date: Sat, 8 May 2004 11:34:15 +0930
From: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
To: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
Cc: iljitsch@muada.com, huitema@windows.microsoft.com, ietf@ietf.org
Subject: Oops, quote in the wrong place (Re: Problem of blocking ICMP
 packets)
Message-Id: <20040508113415.5bc10fd3.ietf@130c04165a5b40404e4440445758487a.nosense.org>
In-Reply-To: <20040508104230.7a701b2f.ietf@130c04165a5b40404e4440445758487a.nosense.org>
References: <DAC3FCB50E31C54987CD10797DA511BA08EA129A@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
	<EDCBDFEE-A069-11D8-BE01-000A95CD987A@muada.com>
	<20040508104230.7a701b2f.ietf@130c04165a5b40404e4440445758487a.nosense.org>
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

On Sat, 8 May 2004 10:42:30 +0930
Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
wrote:

> On Fri, 7 May 2004 23:03:02 +0200

> 
> An "IPsec" only Internet would provide a disincentive to DoS,
> as

Should be "IPsec only" Internet.


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



From ietf-admin@ietf.org  Sat May  8 11:43: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 LAA09619
	for <ietf-archive@ietf.org>; Sat, 8 May 2004 11:43: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 1BMTzR-0003BU-Qj
	for ietf-archive@ietf.org; Sat, 08 May 2004 11:43:49 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMTyS-0002lD-00
	for ietf-archive@ietf.org; Sat, 08 May 2004 11:42:50 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMTxQ-0002Db-00
	for ietf-archive@ietf.org; Sat, 08 May 2004 11:41:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMTrv-00064j-WB; Sat, 08 May 2004 11:36:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMTqA-0005p4-HD
	for ietf@optimus.ietf.org; Sat, 08 May 2004 11:34:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09333
	for <ietf@ietf.org>; Sat, 8 May 2004 11:34: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 1BMTq9-00075P-Az
	for ietf@ietf.org; Sat, 08 May 2004 11:34:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMTp9-0006c2-00
	for ietf@ietf.org; Sat, 08 May 2004 11:33:12 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMTnz-00060w-00
	for ietf@ietf.org; Sat, 08 May 2004 11:31: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 i48FVb1C044418;
	Sat, 8 May 2004 17:31:38 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <20040508104230.7a701b2f.ietf@130c04165a5b40404e4440445758487a.nosense.org>
References: <DAC3FCB50E31C54987CD10797DA511BA08EA129A@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com> <EDCBDFEE-A069-11D8-BE01-000A95CD987A@muada.com> <20040508104230.7a701b2f.ietf@130c04165a5b40404e4440445758487a.nosense.org>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <D1E73004-A104-11D8-BE01-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: "'Internet Engineering Task Force'" <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: Firewalling for the new millennium, was: Problem of blocking ICMP packets
Date: Sat, 8 May 2004 17:31:48 +0200
To: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
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 8-mei-04, at 3:12, Mark Smith wrote:

>> Filtering on protocol/port numbers is a broken concept. When
>> are we going to take the time to come up with a *real* security
>> architecture? One that allows hosts to receive wanted packets
>> and reject unwanted ones,

> I've only read the abstract, however Steve Bellovin's
> "Distributed Firewalls"
> (http://www.research.att.com/~smb/papers/distfw.html) seems to
> suggest exactly that.

Yes, this is good stuff. But I don't think distributed firewalling on  
its own is the full answer.

> Interestingly, with all the recent attacks on Microsoft software,
> they seem to be going down this distributed firewalls path, where
> each host has a firewall. I'm not sure if they are aware of
> Steve's paper, or whether it is a result of these worms almost
> always seeming to be being able to bypass any network based
> security in place anyway. I'd suspect the latter.

You are assuming the existence of network based security (ie, a  
traditional firewall or the by-effects of NAT) in the first place.  
Despite the way it seems some times, not everyone uses NAT. And many of  
those that do drop all incoming sessions on a fixed internal address  
because maintaining a list of specific port mappings is too much work.  
Last but not least, there is physical movement of infected systems.  
(Laptop infected at home brought to work.)

The part that I don't get is why a host is running insecure services in  
the first place and then blocks those services. The only reason for  
doing that I can think of is that those services are for host-local  
use. Now obviously it would make lots more sense to make these services  
available to the loopback address only. This is what MacOS does, for  
instance.

> Linux and other OSs have already have firewalls built in, so
> maybe we are seeing an unplanned and evolutionary transition to
> this model.

There are two issues that aren't dealt with in this model:

- link-local services
- undesired locally initiated communication

The reason why systems like Windows have so many open services is (in  
part) that it's desirable to share files and so on in small work groups  
without having to do much, if any, configuration. Now this is a  
legitimate need, and any security device that gets in the way will  
invariably be disabled in a good percentage of all cases. So what we  
need is a good way to keep local services local. That doesn't fix any  
holes those services may have, but it does mitigate the potential for  
wide-scale abuse. (Those fences on the observation deck at the top of  
the Empire State Building don't cure suicidal tendencies but they do  
make 34rd street safer to walk.) Various approaches come to mind. The  
obvious one is using unroutable address space for these services, but  
that doesn't work because of address translation and the address  
selection problem in the presence of multiple source and/or destination  
addresses. But this can also be done using a TTL hack such as RFC 3682  
uses for BGP, or by setting aside a range of portnumbers for site local  
services and then filter these ports at site edges.

Undesired locally initiated communication can be fixed by Zone Alarm  
like filters, where filtering (also) happens based on which application  
is trying to communicate rather than just the information inside the  
packets themselves. The problem with Zone Alarm is that the local user  
has to decide what applications can and can't do, which is often too  
much to ask from end users. A distributed policy mechanism not unlike  
the one proposed in the paper by Steve Bellovin you cited could help  
here. Especially if the application version is taken into account: as  
soon as a vulnerability is found in an application, it can be blocked  
by changing the policy in a central place. When users upgrade to a  
fixed version of the application they can immediately communicate  
again.

> rather than the current one where any
>> correlation to whether a packet is wanted and whether it's
>> rejected seems coincidental at best? One that at least
>> entertains the possibility of doing something about denial of
>> service attacks? And, last but not least, one that allows
>> reasonable protocols, carrying desired communication, to
>> function without undue breakage?

> I've understood that what you have described is the end-goal
> of end-to-end, opportunistic encryption and authentication ie.
> IPsec. Once the network can't tell what type of traffic it is,
> ie. the port numbers (or protocol numbers if IPsec is run in
> tunnel mode), these network based firewalls will be useless, and
> hopefully will be turned off.

They are of limited use even today, as it's trivial to change port  
numbers if you control both ends of the communication. The only thing  
that's easy to block (or allow) in a current firewall is communication  
towards known services on known ports.

> That wouldn't necessarily remedy denial of service attacks
> though. I think denial of service attacks will always be possible
> if entities can issue traffic to the network in an unregulated or
> unidentified manner.

I think it's possible to remedy denial of service by having service  
providers do proxy IPsec AH verification. I haven't found the time to  
write a draft about this so far, though. One of the open questions is  
whether this can be done if correspondents are running regular ISAKMP  
or changes on both ends are necessary. And obviously this requires  
"you-didn't-think-I-could-do-line-rate-crypto-at-10-Gbps-did-you-ha-ha- 
you-stupid-scriptkiddie" type line cards...

> An "IPsec" only Internet would provide a disincentive to DoS, as
> I'd presume that it implies that end-points are uniquely
> identified, which allows responsibility for these attacks to be
> attributed. That may not be a world we want to live in though as
> anonimity in communications can also be a useful privacy feature.

I certainly don't want an IPsec-only internet as the extra overhead,  
both in CPU cycles and packet size, is significant. But there are large  
classes of applications that would benefit from IPsec. I'm not worried  
about the privacy aspect: with SSL only the server needs a certificate  
in order to protect the communication. I don't see why this model  
wouldn't work for many applications of IPsec.

> In a few respects, DoS attacks and Spam are similar - they rely
> on or assume near or absolute source anonimity, and very low
> costs of transmission. If, or hopefully when, any solutions are
> found to the spam problem, the fundamental methods or techniques
> may be able to be applied to DoS attacks.

There is a very fundamental difference: spam can only come in as fast  
as the mail server is willing to accept it, as spammers must play nice  
at least as far as RFC 793 goes. DoS traffic on the other hand, is sent  
entirely unilaterally, the destination has no way to stop it or slow it  
down.


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


From exim@www1.ietf.org  Sat May  8 11:45:09 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 LAA09720
	for <ietf-archive@odin.ietf.org>; Sat, 8 May 2004 11:45: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 1BMTxQ-000771-GL
	for ietf-archive@odin.ietf.org; Sat, 08 May 2004 11:41:44 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i48FfixV027337
	for ietf-archive@odin.ietf.org; Sat, 8 May 2004 11:41:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMTrv-00064j-WB; Sat, 08 May 2004 11:36:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMTqA-0005p4-HD
	for ietf@optimus.ietf.org; Sat, 08 May 2004 11:34:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09333
	for <ietf@ietf.org>; Sat, 8 May 2004 11:34: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 1BMTq9-00075P-Az
	for ietf@ietf.org; Sat, 08 May 2004 11:34:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMTp9-0006c2-00
	for ietf@ietf.org; Sat, 08 May 2004 11:33:12 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMTnz-00060w-00
	for ietf@ietf.org; Sat, 08 May 2004 11:31: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 i48FVb1C044418;
	Sat, 8 May 2004 17:31:38 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <20040508104230.7a701b2f.ietf@130c04165a5b40404e4440445758487a.nosense.org>
References: <DAC3FCB50E31C54987CD10797DA511BA08EA129A@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com> <EDCBDFEE-A069-11D8-BE01-000A95CD987A@muada.com> <20040508104230.7a701b2f.ietf@130c04165a5b40404e4440445758487a.nosense.org>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <D1E73004-A104-11D8-BE01-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: "'Internet Engineering Task Force'" <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: Firewalling for the new millennium, was: Problem of blocking ICMP packets
Date: Sat, 8 May 2004 17:31:48 +0200
To: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
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 8-mei-04, at 3:12, Mark Smith wrote:

>> Filtering on protocol/port numbers is a broken concept. When
>> are we going to take the time to come up with a *real* security
>> architecture? One that allows hosts to receive wanted packets
>> and reject unwanted ones,

> I've only read the abstract, however Steve Bellovin's
> "Distributed Firewalls"
> (http://www.research.att.com/~smb/papers/distfw.html) seems to
> suggest exactly that.

Yes, this is good stuff. But I don't think distributed firewalling on  
its own is the full answer.

> Interestingly, with all the recent attacks on Microsoft software,
> they seem to be going down this distributed firewalls path, where
> each host has a firewall. I'm not sure if they are aware of
> Steve's paper, or whether it is a result of these worms almost
> always seeming to be being able to bypass any network based
> security in place anyway. I'd suspect the latter.

You are assuming the existence of network based security (ie, a  
traditional firewall or the by-effects of NAT) in the first place.  
Despite the way it seems some times, not everyone uses NAT. And many of  
those that do drop all incoming sessions on a fixed internal address  
because maintaining a list of specific port mappings is too much work.  
Last but not least, there is physical movement of infected systems.  
(Laptop infected at home brought to work.)

The part that I don't get is why a host is running insecure services in  
the first place and then blocks those services. The only reason for  
doing that I can think of is that those services are for host-local  
use. Now obviously it would make lots more sense to make these services  
available to the loopback address only. This is what MacOS does, for  
instance.

> Linux and other OSs have already have firewalls built in, so
> maybe we are seeing an unplanned and evolutionary transition to
> this model.

There are two issues that aren't dealt with in this model:

- link-local services
- undesired locally initiated communication

The reason why systems like Windows have so many open services is (in  
part) that it's desirable to share files and so on in small work groups  
without having to do much, if any, configuration. Now this is a  
legitimate need, and any security device that gets in the way will  
invariably be disabled in a good percentage of all cases. So what we  
need is a good way to keep local services local. That doesn't fix any  
holes those services may have, but it does mitigate the potential for  
wide-scale abuse. (Those fences on the observation deck at the top of  
the Empire State Building don't cure suicidal tendencies but they do  
make 34rd street safer to walk.) Various approaches come to mind. The  
obvious one is using unroutable address space for these services, but  
that doesn't work because of address translation and the address  
selection problem in the presence of multiple source and/or destination  
addresses. But this can also be done using a TTL hack such as RFC 3682  
uses for BGP, or by setting aside a range of portnumbers for site local  
services and then filter these ports at site edges.

Undesired locally initiated communication can be fixed by Zone Alarm  
like filters, where filtering (also) happens based on which application  
is trying to communicate rather than just the information inside the  
packets themselves. The problem with Zone Alarm is that the local user  
has to decide what applications can and can't do, which is often too  
much to ask from end users. A distributed policy mechanism not unlike  
the one proposed in the paper by Steve Bellovin you cited could help  
here. Especially if the application version is taken into account: as  
soon as a vulnerability is found in an application, it can be blocked  
by changing the policy in a central place. When users upgrade to a  
fixed version of the application they can immediately communicate  
again.

> rather than the current one where any
>> correlation to whether a packet is wanted and whether it's
>> rejected seems coincidental at best? One that at least
>> entertains the possibility of doing something about denial of
>> service attacks? And, last but not least, one that allows
>> reasonable protocols, carrying desired communication, to
>> function without undue breakage?

> I've understood that what you have described is the end-goal
> of end-to-end, opportunistic encryption and authentication ie.
> IPsec. Once the network can't tell what type of traffic it is,
> ie. the port numbers (or protocol numbers if IPsec is run in
> tunnel mode), these network based firewalls will be useless, and
> hopefully will be turned off.

They are of limited use even today, as it's trivial to change port  
numbers if you control both ends of the communication. The only thing  
that's easy to block (or allow) in a current firewall is communication  
towards known services on known ports.

> That wouldn't necessarily remedy denial of service attacks
> though. I think denial of service attacks will always be possible
> if entities can issue traffic to the network in an unregulated or
> unidentified manner.

I think it's possible to remedy denial of service by having service  
providers do proxy IPsec AH verification. I haven't found the time to  
write a draft about this so far, though. One of the open questions is  
whether this can be done if correspondents are running regular ISAKMP  
or changes on both ends are necessary. And obviously this requires  
"you-didn't-think-I-could-do-line-rate-crypto-at-10-Gbps-did-you-ha-ha- 
you-stupid-scriptkiddie" type line cards...

> An "IPsec" only Internet would provide a disincentive to DoS, as
> I'd presume that it implies that end-points are uniquely
> identified, which allows responsibility for these attacks to be
> attributed. That may not be a world we want to live in though as
> anonimity in communications can also be a useful privacy feature.

I certainly don't want an IPsec-only internet as the extra overhead,  
both in CPU cycles and packet size, is significant. But there are large  
classes of applications that would benefit from IPsec. I'm not worried  
about the privacy aspect: with SSL only the server needs a certificate  
in order to protect the communication. I don't see why this model  
wouldn't work for many applications of IPsec.

> In a few respects, DoS attacks and Spam are similar - they rely
> on or assume near or absolute source anonimity, and very low
> costs of transmission. If, or hopefully when, any solutions are
> found to the spam problem, the fundamental methods or techniques
> may be able to be applied to DoS attacks.

There is a very fundamental difference: spam can only come in as fast  
as the mail server is willing to accept it, as spammers must play nice  
at least as far as RFC 793 goes. DoS traffic on the other hand, is sent  
entirely unilaterally, the destination has no way to stop it or slow it  
down.


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



From ietf-admin@ietf.org  Sat May  8 17:52: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 RAA27416
	for <ietf-archive@ietf.org>; Sat, 8 May 2004 17:52: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 1BMZk9-0006MH-SY
	for ietf-archive@ietf.org; Sat, 08 May 2004 17:52:25 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMZjV-0005y0-00
	for ietf-archive@ietf.org; Sat, 08 May 2004 17:51:46 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMZib-0005Ww-00
	for ietf-archive@ietf.org; Sat, 08 May 2004 17:50:49 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMZd1-0005HL-9m; Sat, 08 May 2004 17:45:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMZaA-0004xw-PY
	for ietf@optimus.ietf.org; Sat, 08 May 2004 17:42: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 RAA26619
	for <ietf@ietf.org>; Sat, 8 May 2004 17:41: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 1BMZa5-0002IE-La
	for ietf@ietf.org; Sat, 08 May 2004 17:42:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMZZ7-0001vK-00
	for ietf@ietf.org; Sat, 08 May 2004 17:41:01 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with smtp (Exim 4.12)
	id 1BMZXz-0001DL-00
	for ietf@ietf.org; Sat, 08 May 2004 17:39:51 -0400
Received: (qmail 1480 invoked from network); 8 May 2004 21:41:42 -0000
Received: from yahoobb219178198119.bbtec.net (HELO necom830.hpcl.titech.ac.jp) (219.178.198.119)
  by necom830.hpcl.titech.ac.jp with SMTP; 8 May 2004 21:41:42 -0000
Message-ID: <409D5492.1080404@necom830.hpcl.titech.ac.jp>
Date: Sun, 09 May 2004 06:43:46 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: ja, en-us, en
MIME-Version: 1.0
To: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
CC: Iljitsch van Beijnum <iljitsch@muada.com>, huitema@windows.microsoft.com,
        ietf@ietf.org
Subject: Re: Problem of blocking ICMP packets
References: <DAC3FCB50E31C54987CD10797DA511BA08EA129A@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>	<EDCBDFEE-A069-11D8-BE01-000A95CD987A@muada.com> <20040508104230.7a701b2f.ietf@130c04165a5b40404e4440445758487a.nosense.org>
In-Reply-To: <20040508104230.7a701b2f.ietf@130c04165a5b40404e4440445758487a.nosense.org>
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

Mark Smith;

> > Filtering on protocol/port numbers is a broken concept.

Yes, it is.

However, it is merely as broken as PMTUD that we don't need
security discussion to deny PMTUD.

> I've understood that what you have described is the end-goal
> of end-to-end, opportunistic encryption and authentication ie.
> IPsec.

Back to the original problem, PMTUD depends on the capabilities
of intermediate systems on a path to generate certain ICMP,
generation of which is as complex as fragmentation itself,
that it is not very end to end.

That is, PMTUD is a broken concept.

						Masataka Ohta



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


From exim@www1.ietf.org  Sat May  8 17:58: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 RAA27602
	for <ietf-archive@odin.ietf.org>; Sat, 8 May 2004 17:58: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 1BMZie-0006UU-Gs
	for ietf-archive@odin.ietf.org; Sat, 08 May 2004 17:50:58 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i48LoqKX024695
	for ietf-archive@odin.ietf.org; Sat, 8 May 2004 17:50:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMZd1-0005HL-9m; Sat, 08 May 2004 17:45:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMZaA-0004xw-PY
	for ietf@optimus.ietf.org; Sat, 08 May 2004 17:42: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 RAA26619
	for <ietf@ietf.org>; Sat, 8 May 2004 17:41: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 1BMZa5-0002IE-La
	for ietf@ietf.org; Sat, 08 May 2004 17:42:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMZZ7-0001vK-00
	for ietf@ietf.org; Sat, 08 May 2004 17:41:01 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with smtp (Exim 4.12)
	id 1BMZXz-0001DL-00
	for ietf@ietf.org; Sat, 08 May 2004 17:39:51 -0400
Received: (qmail 1480 invoked from network); 8 May 2004 21:41:42 -0000
Received: from yahoobb219178198119.bbtec.net (HELO necom830.hpcl.titech.ac.jp) (219.178.198.119)
  by necom830.hpcl.titech.ac.jp with SMTP; 8 May 2004 21:41:42 -0000
Message-ID: <409D5492.1080404@necom830.hpcl.titech.ac.jp>
Date: Sun, 09 May 2004 06:43:46 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: ja, en-us, en
MIME-Version: 1.0
To: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
CC: Iljitsch van Beijnum <iljitsch@muada.com>, huitema@windows.microsoft.com,
        ietf@ietf.org
Subject: Re: Problem of blocking ICMP packets
References: <DAC3FCB50E31C54987CD10797DA511BA08EA129A@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>	<EDCBDFEE-A069-11D8-BE01-000A95CD987A@muada.com> <20040508104230.7a701b2f.ietf@130c04165a5b40404e4440445758487a.nosense.org>
In-Reply-To: <20040508104230.7a701b2f.ietf@130c04165a5b40404e4440445758487a.nosense.org>
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

Mark Smith;

> > Filtering on protocol/port numbers is a broken concept.

Yes, it is.

However, it is merely as broken as PMTUD that we don't need
security discussion to deny PMTUD.

> I've understood that what you have described is the end-goal
> of end-to-end, opportunistic encryption and authentication ie.
> IPsec.

Back to the original problem, PMTUD depends on the capabilities
of intermediate systems on a path to generate certain ICMP,
generation of which is as complex as fragmentation itself,
that it is not very end to end.

That is, PMTUD is a broken concept.

						Masataka Ohta



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



From exim@www1.ietf.org  Sat May  8 23:54:16 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA13633
	for <ietf-archive@odin.ietf.org>; Sat, 8 May 2004 23:54: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 1BMfMJ-0004sc-Fp
	for ietf-archive@odin.ietf.org; Sat, 08 May 2004 23:52:15 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i493qBGH018635
	for ietf-archive@odin.ietf.org; Sat, 8 May 2004 23:52:11 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMfIH-0004LB-Lb; Sat, 08 May 2004 23:48:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMfGm-0004B0-An
	for ietf@optimus.ietf.org; Sat, 08 May 2004 23:46: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 XAA13253
	for <ietf@ietf.org>; Sat, 8 May 2004 23:46: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 1BMfGj-0000Qd-V4
	for ietf@ietf.org; Sat, 08 May 2004 23:46:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMfFd-00001d-00
	for ietf@ietf.org; Sat, 08 May 2004 23:45:17 -0400
Received: from 99.cust35.nsw.dsl.ozemail.com.au ([203.103.114.99] helo=nosense.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMfEV-00076k-00
	for ietf@ietf.org; Sat, 08 May 2004 23:44:08 -0400
Received: from Dupy2.nosense.org (localhost.localdomain [127.0.0.1])
	by nosense.org (Postfix) with SMTP
	id 564DA3F02A; Sun,  9 May 2004 13:16:16 +0930 (CST)
Date: Sun, 9 May 2004 13:16:15 +0930
From: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Cc: iljitsch@muada.com, huitema@windows.microsoft.com, ietf@ietf.org
Subject: Re: Problem of blocking ICMP packets
Message-Id: <20040509131615.1214d46c.ietf@130c04165a5b40404e4440445758487a.nosense.org>
In-Reply-To: <409D5492.1080404@necom830.hpcl.titech.ac.jp>
References: <DAC3FCB50E31C54987CD10797DA511BA08EA129A@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
	<EDCBDFEE-A069-11D8-BE01-000A95CD987A@muada.com>
	<20040508104230.7a701b2f.ietf@130c04165a5b40404e4440445758487a.nosense.org>
	<409D5492.1080404@necom830.hpcl.titech.ac.jp>
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

On Sun, 09 May 2004 06:43:46 +0900
Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> wrote:

> Mark Smith;
> 
> > > Filtering on protocol/port numbers is a broken concept.
> 
> Yes, it is.
> 
> However, it is merely as broken as PMTUD that we don't need
> security discussion to deny PMTUD.
> 
> > I've understood that what you have described is the end-goal
> > of end-to-end, opportunistic encryption and authentication
> > ie. IPsec.
> 
> Back to the original problem, PMTUD depends on the capabilities
> of intermediate systems on a path to generate certain ICMP,
> generation of which is as complex as fragmentation itself,
> that it is not very end to end.
> 

Radia Perlman, in her book "Interconnections", 2nd edition,
suggests a few alternative methods of performing PMTUD, including
one which wouldn't require feedback from the network, starting at
pg 185.

> That is, PMTUD is a broken concept.
> 

I'm not sure I understand you. Are you saying the idea of PMTUD
is broken, or the way it currently works ?

Regards,
Mark.

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



From ietf-admin@ietf.org  Sat May  8 23:54: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 XAA13651
	for <ietf-archive@ietf.org>; Sat, 8 May 2004 23:54:18 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BMfOO-0003Y3-1v
	for ietf-archive@ietf.org; Sat, 08 May 2004 23:54:20 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMfNN-00037v-00
	for ietf-archive@ietf.org; Sat, 08 May 2004 23:53:17 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMfMH-0002Te-00
	for ietf-archive@ietf.org; Sat, 08 May 2004 23:52:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMfIH-0004LB-Lb; Sat, 08 May 2004 23:48:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMfGm-0004B0-An
	for ietf@optimus.ietf.org; Sat, 08 May 2004 23:46: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 XAA13253
	for <ietf@ietf.org>; Sat, 8 May 2004 23:46: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 1BMfGj-0000Qd-V4
	for ietf@ietf.org; Sat, 08 May 2004 23:46:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMfFd-00001d-00
	for ietf@ietf.org; Sat, 08 May 2004 23:45:17 -0400
Received: from 99.cust35.nsw.dsl.ozemail.com.au ([203.103.114.99] helo=nosense.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMfEV-00076k-00
	for ietf@ietf.org; Sat, 08 May 2004 23:44:08 -0400
Received: from Dupy2.nosense.org (localhost.localdomain [127.0.0.1])
	by nosense.org (Postfix) with SMTP
	id 564DA3F02A; Sun,  9 May 2004 13:16:16 +0930 (CST)
Date: Sun, 9 May 2004 13:16:15 +0930
From: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Cc: iljitsch@muada.com, huitema@windows.microsoft.com, ietf@ietf.org
Subject: Re: Problem of blocking ICMP packets
Message-Id: <20040509131615.1214d46c.ietf@130c04165a5b40404e4440445758487a.nosense.org>
In-Reply-To: <409D5492.1080404@necom830.hpcl.titech.ac.jp>
References: <DAC3FCB50E31C54987CD10797DA511BA08EA129A@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
	<EDCBDFEE-A069-11D8-BE01-000A95CD987A@muada.com>
	<20040508104230.7a701b2f.ietf@130c04165a5b40404e4440445758487a.nosense.org>
	<409D5492.1080404@necom830.hpcl.titech.ac.jp>
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

On Sun, 09 May 2004 06:43:46 +0900
Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> wrote:

> Mark Smith;
> 
> > > Filtering on protocol/port numbers is a broken concept.
> 
> Yes, it is.
> 
> However, it is merely as broken as PMTUD that we don't need
> security discussion to deny PMTUD.
> 
> > I've understood that what you have described is the end-goal
> > of end-to-end, opportunistic encryption and authentication
> > ie. IPsec.
> 
> Back to the original problem, PMTUD depends on the capabilities
> of intermediate systems on a path to generate certain ICMP,
> generation of which is as complex as fragmentation itself,
> that it is not very end to end.
> 

Radia Perlman, in her book "Interconnections", 2nd edition,
suggests a few alternative methods of performing PMTUD, including
one which wouldn't require feedback from the network, starting at
pg 185.

> That is, PMTUD is a broken concept.
> 

I'm not sure I understand you. Are you saying the idea of PMTUD
is broken, or the way it currently works ?

Regards,
Mark.

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


From ietf-admin@ietf.org  Sun May  9 04:53: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 EAA24014
	for <ietf-archive@ietf.org>; Sun, 9 May 2004 04:53:42 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BMk46-0004iY-Dp
	for ietf-archive@ietf.org; Sun, 09 May 2004 04:53:42 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMk39-0004Lm-00
	for ietf-archive@ietf.org; Sun, 09 May 2004 04:52:43 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMk2X-0003z8-00
	for ietf-archive@ietf.org; Sun, 09 May 2004 04:52:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMjyf-0005vG-L7; Sun, 09 May 2004 04:48:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMjxI-0005pW-VD
	for ietf@optimus.ietf.org; Sun, 09 May 2004 04:46: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 EAA23751
	for <ietf@ietf.org>; Sun, 9 May 2004 04:46:38 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BMjxF-0002BO-Hc
	for ietf@ietf.org; Sun, 09 May 2004 04:46:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMjwJ-0001pP-00
	for ietf@ietf.org; Sun, 09 May 2004 04:45:40 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with smtp (Exim 4.12)
	id 1BMjvu-0001T2-00
	for ietf@ietf.org; Sun, 09 May 2004 04:45:15 -0400
Received: (qmail 3937 invoked from network); 9 May 2004 08:47:11 -0000
Received: from yahoobb219178198119.bbtec.net (HELO necom830.hpcl.titech.ac.jp) (219.178.198.119)
  by necom830.hpcl.titech.ac.jp with SMTP; 9 May 2004 08:47:11 -0000
Message-ID: <409DF083.1090302@necom830.hpcl.titech.ac.jp>
Date: Sun, 09 May 2004 17:49:07 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: ja, en-us, en
MIME-Version: 1.0
To: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
CC: iljitsch@muada.com, huitema@windows.microsoft.com, ietf@ietf.org
Subject: Re: Problem of blocking ICMP packets
References: <DAC3FCB50E31C54987CD10797DA511BA08EA129A@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>	<EDCBDFEE-A069-11D8-BE01-000A95CD987A@muada.com>	<20040508104230.7a701b2f.ietf@130c04165a5b40404e4440445758487a.nosense.org>	<409D5492.1080404@necom830.hpcl.titech.ac.jp> <20040509131615.1214d46c.ietf@130c04165a5b40404e4440445758487a.nosense.org>
In-Reply-To: <20040509131615.1214d46c.ietf@130c04165a5b40404e4440445758487a.nosense.org>
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

Mark Smith;

> Radia Perlman, in her book "Interconnections", 2nd edition,
> suggests a few alternative methods of performing PMTUD, including
> one which wouldn't require feedback from the network, starting at
> pg 185.

While I won't bother to read a paper material not available here,
I understand it is a very bad idea for a transport or above layer
to interpret a packet loss as a unreliable hint of congestion and
MTU mismatch, especially because initially and upon path changes,
both path congestion and path MTU properties will change.

It is fine that fragmentation of IPv4 is detected and reacted
against by an upper layer.

It is also fine to just send 1280B or smaller IPv6 packets.

> I'm not sure I understand you. Are you saying the idea of PMTUD
> is broken, or the way it currently works ?

The idea is broken. Note that recent super computers are, as
expected long ago, massively parallel ones to be able to
process a lot of interrupts without much performance loss.

						Masataka Ohta


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


From exim@www1.ietf.org  Sun May  9 04:54:55 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA24076
	for <ietf-archive@odin.ietf.org>; Sun, 9 May 2004 04:54:55 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMk2b-0006WL-4T
	for ietf-archive@odin.ietf.org; Sun, 09 May 2004 04:52:12 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i498q9Cd024809
	for ietf-archive@odin.ietf.org; Sun, 9 May 2004 04:52:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMjyf-0005vG-L7; Sun, 09 May 2004 04:48:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMjxI-0005pW-VD
	for ietf@optimus.ietf.org; Sun, 09 May 2004 04:46: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 EAA23751
	for <ietf@ietf.org>; Sun, 9 May 2004 04:46:38 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BMjxF-0002BO-Hc
	for ietf@ietf.org; Sun, 09 May 2004 04:46:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMjwJ-0001pP-00
	for ietf@ietf.org; Sun, 09 May 2004 04:45:40 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with smtp (Exim 4.12)
	id 1BMjvu-0001T2-00
	for ietf@ietf.org; Sun, 09 May 2004 04:45:15 -0400
Received: (qmail 3937 invoked from network); 9 May 2004 08:47:11 -0000
Received: from yahoobb219178198119.bbtec.net (HELO necom830.hpcl.titech.ac.jp) (219.178.198.119)
  by necom830.hpcl.titech.ac.jp with SMTP; 9 May 2004 08:47:11 -0000
Message-ID: <409DF083.1090302@necom830.hpcl.titech.ac.jp>
Date: Sun, 09 May 2004 17:49:07 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: ja, en-us, en
MIME-Version: 1.0
To: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
CC: iljitsch@muada.com, huitema@windows.microsoft.com, ietf@ietf.org
Subject: Re: Problem of blocking ICMP packets
References: <DAC3FCB50E31C54987CD10797DA511BA08EA129A@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>	<EDCBDFEE-A069-11D8-BE01-000A95CD987A@muada.com>	<20040508104230.7a701b2f.ietf@130c04165a5b40404e4440445758487a.nosense.org>	<409D5492.1080404@necom830.hpcl.titech.ac.jp> <20040509131615.1214d46c.ietf@130c04165a5b40404e4440445758487a.nosense.org>
In-Reply-To: <20040509131615.1214d46c.ietf@130c04165a5b40404e4440445758487a.nosense.org>
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

Mark Smith;

> Radia Perlman, in her book "Interconnections", 2nd edition,
> suggests a few alternative methods of performing PMTUD, including
> one which wouldn't require feedback from the network, starting at
> pg 185.

While I won't bother to read a paper material not available here,
I understand it is a very bad idea for a transport or above layer
to interpret a packet loss as a unreliable hint of congestion and
MTU mismatch, especially because initially and upon path changes,
both path congestion and path MTU properties will change.

It is fine that fragmentation of IPv4 is detected and reacted
against by an upper layer.

It is also fine to just send 1280B or smaller IPv6 packets.

> I'm not sure I understand you. Are you saying the idea of PMTUD
> is broken, or the way it currently works ?

The idea is broken. Note that recent super computers are, as
expected long ago, massively parallel ones to be able to
process a lot of interrupts without much performance loss.

						Masataka Ohta


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



From exim@www1.ietf.org  Sun May  9 12:53: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 MAA11287
	for <ietf-archive@odin.ietf.org>; Sun, 9 May 2004 12:53: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 1BMrX0-0001a5-80
	for ietf-archive@odin.ietf.org; Sun, 09 May 2004 12:52:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i49Gq2qu006048
	for ietf-archive@odin.ietf.org; Sun, 9 May 2004 12:52:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMrLP-0000LF-9r; Sun, 09 May 2004 12:40:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMrKM-0000AR-FM
	for ietf@optimus.ietf.org; Sun, 09 May 2004 12:38: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 MAA10830
	for <ietf@ietf.org>; Sun, 9 May 2004 12:38:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BMrKK-0000P3-SK
	for ietf@ietf.org; Sun, 09 May 2004 12:38:56 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMrJR-00006W-00
	for ietf@ietf.org; Sun, 09 May 2004 12:38:01 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMrIl-0007HZ-00
	for ietf@ietf.org; Sun, 09 May 2004 12:37:19 -0400
Received: from sj-core-5.cisco.com (171.71.177.238)
  by sj-iport-3.cisco.com with ESMTP; 09 May 2004 08:42:10 +0000
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id i49GacW9012636;
	Sun, 9 May 2004 09:36:39 -0700 (PDT)
Received: from cisco.com ([10.25.65.178])
	by mira-sjc5-c.cisco.com (MOS 3.4.5-GR)
	with SMTP id ATW32930;
	Sun, 9 May 2004 09:36:38 -0700 (PDT)
Date: Sun, 9 May 2004 12:36:35 -0400
Subject: Re: Firewalling for the new millennium, was: Problem of blocking ICMP packets
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v553)
Cc: "'Internet Engineering Task Force'" <ietf@ietf.org>
To: Iljitsch van Beijnum <iljitsch@muada.com>
From: Melinda Shore <mshore@cisco.com>
In-Reply-To: <D1E73004-A104-11D8-BE01-000A95CD987A@muada.com>
Message-Id: <0989FCAA-A1D7-11D8-8468-000A95E35274@cisco.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.553)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: 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 Saturday, May 8, 2004, at 11:31 AM, Iljitsch van Beijnum wrote:
> Yes, this is good stuff. But I don't think distributed firewalling on 
> its own is the full answer.

I think it's pretty clear at this point that there is no full
answer, or that if there is it's multi-component and situation-
dependent.  I think that it's pretty clear that we need to make
sure that we're allowing network administrators better control
of their own networks, and distributed firewalling can anchor that
(how security policy is passed around).  Unfortunately I think there
will continue to be a need for firewalls at network borders, at
least towards the edge.  NAT doesn't properly belong in this discussion
but since it's here anyway it should be regarded as part of the
network border packet filtering whatever and probably ought to be
included in participation in enforcing security policy.

Melinda


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



From ietf-admin@ietf.org  Sun May  9 12:53: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 MAA11318
	for <ietf-archive@ietf.org>; Sun, 9 May 2004 12:53: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 1BMrYn-00054b-JS
	for ietf-archive@ietf.org; Sun, 09 May 2004 12:53:53 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMrXt-0004kc-00
	for ietf-archive@ietf.org; Sun, 09 May 2004 12:52:58 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMrWz-0004QX-00
	for ietf-archive@ietf.org; Sun, 09 May 2004 12:52:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMrLP-0000LF-9r; Sun, 09 May 2004 12:40:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMrKM-0000AR-FM
	for ietf@optimus.ietf.org; Sun, 09 May 2004 12:38: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 MAA10830
	for <ietf@ietf.org>; Sun, 9 May 2004 12:38:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BMrKK-0000P3-SK
	for ietf@ietf.org; Sun, 09 May 2004 12:38:56 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMrJR-00006W-00
	for ietf@ietf.org; Sun, 09 May 2004 12:38:01 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMrIl-0007HZ-00
	for ietf@ietf.org; Sun, 09 May 2004 12:37:19 -0400
Received: from sj-core-5.cisco.com (171.71.177.238)
  by sj-iport-3.cisco.com with ESMTP; 09 May 2004 08:42:10 +0000
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id i49GacW9012636;
	Sun, 9 May 2004 09:36:39 -0700 (PDT)
Received: from cisco.com ([10.25.65.178])
	by mira-sjc5-c.cisco.com (MOS 3.4.5-GR)
	with SMTP id ATW32930;
	Sun, 9 May 2004 09:36:38 -0700 (PDT)
Date: Sun, 9 May 2004 12:36:35 -0400
Subject: Re: Firewalling for the new millennium, was: Problem of blocking ICMP packets
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v553)
Cc: "'Internet Engineering Task Force'" <ietf@ietf.org>
To: Iljitsch van Beijnum <iljitsch@muada.com>
From: Melinda Shore <mshore@cisco.com>
In-Reply-To: <D1E73004-A104-11D8-BE01-000A95CD987A@muada.com>
Message-Id: <0989FCAA-A1D7-11D8-8468-000A95E35274@cisco.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.553)
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 Saturday, May 8, 2004, at 11:31 AM, Iljitsch van Beijnum wrote:
> Yes, this is good stuff. But I don't think distributed firewalling on 
> its own is the full answer.

I think it's pretty clear at this point that there is no full
answer, or that if there is it's multi-component and situation-
dependent.  I think that it's pretty clear that we need to make
sure that we're allowing network administrators better control
of their own networks, and distributed firewalling can anchor that
(how security policy is passed around).  Unfortunately I think there
will continue to be a need for firewalls at network borders, at
least towards the edge.  NAT doesn't properly belong in this discussion
but since it's here anyway it should be regarded as part of the
network border packet filtering whatever and probably ought to be
included in participation in enforcing security policy.

Melinda


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


From ietf-admin@ietf.org  Sun May  9 14:48: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 OAA16016
	for <ietf-archive@ietf.org>; Sun, 9 May 2004 14:48: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 1BMtLg-0001B3-B8
	for ietf-archive@ietf.org; Sun, 09 May 2004 14:48:28 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMtKx-0000q8-00
	for ietf-archive@ietf.org; Sun, 09 May 2004 14:47:44 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMtK0-0000Ul-00
	for ietf-archive@ietf.org; Sun, 09 May 2004 14:46:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMtGQ-0005I3-Hf; Sun, 09 May 2004 14:43:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMtCb-0004w8-EU
	for ietf@optimus.ietf.org; Sun, 09 May 2004 14:39:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15674
	for <ietf@ietf.org>; Sun, 9 May 2004 14:39:02 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BMtCY-00067m-Ed
	for ietf@ietf.org; Sun, 09 May 2004 14:39:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMtBf-0005of-00
	for ietf@ietf.org; Sun, 09 May 2004 14:38:08 -0400
Received: from rudd.cc ([64.81.246.247])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMtAq-0005UF-00
	for ietf@ietf.org; Sun, 09 May 2004 14:37:16 -0400
Received: from [10.0.1.220] (arcadia.rudd.cc [10.0.1.220])
	by rudd.cc (8.11.1/8.11.1) with ESMTP id i49Iax988198
	for <ietf@ietf.org>; Sun, 9 May 2004 11:36:59 -0700 (PDT)
	(envelope-from john@rudd.cc)
Mime-Version: 1.0 (Apple Message framework v613)
Content-Transfer-Encoding: 7bit
Message-Id: <DD72EEC3-A1E7-11D8-8626-003065F939FE@rudd.cc>
Content-Type: text/plain; charset=US-ASCII; format=flowed
To: ietf@ietf.org
From: John Rudd <john@rudd.cc>
Subject: Not sure if this is the right place for this
Date: Sun, 9 May 2004 11:37:03 -0700
X-Mailer: Apple Mail (2.613)
X-DOMAIN-ORG-MailScanner: Found to be clean
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


I've noticed a trend with the adoption of SSL/TLS that I'm not sure is 
really in the best long term interests of the community.

It seems that early on an "alternate port" strategy is/was adopted, 
such as having an SSL only version of POP on port 995, IMAP on 993, and 
SMTP on 465.  These ports start p with an SSL session before any data 
is sent, so only SSL enabled clients are able to attach. (I will refer 
to this as the "alternate port strategy")

Then, as time has marched on, and the "STARTTLS" command was 
implimented, SSL/TLS has been integrated into the "primary port".  So, 
now, SSL/TLS is handled on ports 110, 143, and 25 (respectively), with 
SSL/TLS being initiated (by the client sending the "STARTTLS" command) 
after the plain-text session has started.  When this shows up in the 
RFC for extensions to the protocol, the alternate port method is 
usually then mentioned as "deprecated".  (I will refer to this as the 
"STARTTLS strategy").


The problem with the STARTTLS strategy is: you can't guarantee at the 
network level that a client will use SSL/TLS.  The service provider 
might be able to do that (ex: CommuniGate Pro, a mail server from 
stalker.com, has an option to require "secure logins", meaning that 
they must be happening within an SSL/TLS protected session), but the 
network provider cannot.  In large organizations, or situations with 
outsourced services, those two groups may not be the same.  This leads 
to a situation where a networking service may be trying to enforce a 
mandate of "secure protocols only", but cannot do so under the STARTTLS 
strategy.

This is our current issue at UCSC with the deployment of wireless 
access points.  I, the email administrator, can't currently require 
"secure logins" because of some legacy issues.  As dangerous as it may 
be, I can't disallow plain text sessions yet.  Yet, the wireless group 
doesn't trust WEP (for good reasons), and has decided that wireless 
privacy must come from SSL/TLS enabled protocols ... so they're 
blocking the non-SSL/TLS ports.  You can't get to POP via 110, IMAP via 
143, nor SMTP via 25.  If you want to check your email, you have to it 
via the Alternate Port strategy.

Personally, I'm quite happy with their agenda.  But I have a concern: 
clients which are aiming at RFC compliance now see that the RFCs which 
cover them consider the Alternate Port strategy to be deprecated.  So, 
we cannot depend upon current clients to "do the smart thing" and have 
the Alternate Port strategy available.  Yet, the Alternate Port 
strategy is the only way to, at the network level, enforce SSL/TLS*.  
So, the Alternate Port strategy still has some very real, very lasting 
value.  If the Alternate Port strategy were to be considered "current", 
then it might encourage authors to embrace both strategies (the best 
path).


(* Yes, someone could merely start a standard STARTTLS based server on 
ports 993, 995, etc. and circumvent the network agenda, but we're not 
so concerned about that type of blatant action, we're concerned with 
typical software in typical configurations being able to be pigeonholed 
into only having the option of entering in to SSL/TLS sessions.)

So, what I would like to see, as a general agenda for the RFC's is:

1) The Alternate Port strategy should no longer be deprecated for any 
protocol
2) Those services (such as the Message Submission Protocol) that were 
created with an assumed dependance upon STARTTLS should be extented to 
also have an Alternate Port for SSL/TLS only.
3) Standard Compliance (of the software) should depend upon 
implementing both strategies, not one or the other (but it would be 
acceptable if the systems administrator were to not activate both 
strategies, which is why I inserted "of the software").


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


From exim@www1.ietf.org  Sun May  9 14:51:52 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16203
	for <ietf-archive@odin.ietf.org>; Sun, 9 May 2004 14:51:52 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMtK2-0005si-FA
	for ietf-archive@odin.ietf.org; Sun, 09 May 2004 14:46:46 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i49Ikk0t022601
	for ietf-archive@odin.ietf.org; Sun, 9 May 2004 14:46:46 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMtGQ-0005I3-Hf; Sun, 09 May 2004 14:43:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMtCb-0004w8-EU
	for ietf@optimus.ietf.org; Sun, 09 May 2004 14:39:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15674
	for <ietf@ietf.org>; Sun, 9 May 2004 14:39:02 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BMtCY-00067m-Ed
	for ietf@ietf.org; Sun, 09 May 2004 14:39:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMtBf-0005of-00
	for ietf@ietf.org; Sun, 09 May 2004 14:38:08 -0400
Received: from rudd.cc ([64.81.246.247])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMtAq-0005UF-00
	for ietf@ietf.org; Sun, 09 May 2004 14:37:16 -0400
Received: from [10.0.1.220] (arcadia.rudd.cc [10.0.1.220])
	by rudd.cc (8.11.1/8.11.1) with ESMTP id i49Iax988198
	for <ietf@ietf.org>; Sun, 9 May 2004 11:36:59 -0700 (PDT)
	(envelope-from john@rudd.cc)
Mime-Version: 1.0 (Apple Message framework v613)
Content-Transfer-Encoding: 7bit
Message-Id: <DD72EEC3-A1E7-11D8-8626-003065F939FE@rudd.cc>
Content-Type: text/plain; charset=US-ASCII; format=flowed
To: ietf@ietf.org
From: John Rudd <john@rudd.cc>
Subject: Not sure if this is the right place for this
Date: Sun, 9 May 2004 11:37:03 -0700
X-Mailer: Apple Mail (2.613)
X-DOMAIN-ORG-MailScanner: Found to be clean
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
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


I've noticed a trend with the adoption of SSL/TLS that I'm not sure is 
really in the best long term interests of the community.

It seems that early on an "alternate port" strategy is/was adopted, 
such as having an SSL only version of POP on port 995, IMAP on 993, and 
SMTP on 465.  These ports start p with an SSL session before any data 
is sent, so only SSL enabled clients are able to attach. (I will refer 
to this as the "alternate port strategy")

Then, as time has marched on, and the "STARTTLS" command was 
implimented, SSL/TLS has been integrated into the "primary port".  So, 
now, SSL/TLS is handled on ports 110, 143, and 25 (respectively), with 
SSL/TLS being initiated (by the client sending the "STARTTLS" command) 
after the plain-text session has started.  When this shows up in the 
RFC for extensions to the protocol, the alternate port method is 
usually then mentioned as "deprecated".  (I will refer to this as the 
"STARTTLS strategy").


The problem with the STARTTLS strategy is: you can't guarantee at the 
network level that a client will use SSL/TLS.  The service provider 
might be able to do that (ex: CommuniGate Pro, a mail server from 
stalker.com, has an option to require "secure logins", meaning that 
they must be happening within an SSL/TLS protected session), but the 
network provider cannot.  In large organizations, or situations with 
outsourced services, those two groups may not be the same.  This leads 
to a situation where a networking service may be trying to enforce a 
mandate of "secure protocols only", but cannot do so under the STARTTLS 
strategy.

This is our current issue at UCSC with the deployment of wireless 
access points.  I, the email administrator, can't currently require 
"secure logins" because of some legacy issues.  As dangerous as it may 
be, I can't disallow plain text sessions yet.  Yet, the wireless group 
doesn't trust WEP (for good reasons), and has decided that wireless 
privacy must come from SSL/TLS enabled protocols ... so they're 
blocking the non-SSL/TLS ports.  You can't get to POP via 110, IMAP via 
143, nor SMTP via 25.  If you want to check your email, you have to it 
via the Alternate Port strategy.

Personally, I'm quite happy with their agenda.  But I have a concern: 
clients which are aiming at RFC compliance now see that the RFCs which 
cover them consider the Alternate Port strategy to be deprecated.  So, 
we cannot depend upon current clients to "do the smart thing" and have 
the Alternate Port strategy available.  Yet, the Alternate Port 
strategy is the only way to, at the network level, enforce SSL/TLS*.  
So, the Alternate Port strategy still has some very real, very lasting 
value.  If the Alternate Port strategy were to be considered "current", 
then it might encourage authors to embrace both strategies (the best 
path).


(* Yes, someone could merely start a standard STARTTLS based server on 
ports 993, 995, etc. and circumvent the network agenda, but we're not 
so concerned about that type of blatant action, we're concerned with 
typical software in typical configurations being able to be pigeonholed 
into only having the option of entering in to SSL/TLS sessions.)

So, what I would like to see, as a general agenda for the RFC's is:

1) The Alternate Port strategy should no longer be deprecated for any 
protocol
2) Those services (such as the Message Submission Protocol) that were 
created with an assumed dependance upon STARTTLS should be extented to 
also have an Alternate Port for SSL/TLS only.
3) Standard Compliance (of the software) should depend upon 
implementing both strategies, not one or the other (but it would be 
acceptable if the systems administrator were to not activate both 
strategies, which is why I inserted "of the software").


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



From exim@www1.ietf.org  Sun May  9 19:39:59 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 TAA28246
	for <ietf-archive@odin.ietf.org>; Sun, 9 May 2004 19:39: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 1BMxs3-0005WM-QY
	for ietf-archive@odin.ietf.org; Sun, 09 May 2004 19:38:12 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i49NcBfe021189
	for ietf-archive@odin.ietf.org; Sun, 9 May 2004 19:38:11 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMxo2-0004p0-JP; Sun, 09 May 2004 19:34:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMxmJ-0004gH-6q
	for ietf@optimus.ietf.org; Sun, 09 May 2004 19:32: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 TAA28027
	for <ietf@ietf.org>; Sun, 9 May 2004 19:32: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 1BMxmH-0006A5-8U
	for ietf@ietf.org; Sun, 09 May 2004 19:32:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMxlI-0005ry-00
	for ietf@ietf.org; Sun, 09 May 2004 19:31:12 -0400
Received: from cpe-138-217-63-233.vic.bigpond.net.au ([138.217.63.233] helo=7020bsd.)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMxkL-0005Ka-00
	for ietf@ietf.org; Sun, 09 May 2004 19:30:13 -0400
Received: from swin.edu.au (localhost [127.0.0.1])
	by 7020bsd. (8.12.6/8.12.6) with ESMTP id i49NTuhX000304;
	Mon, 10 May 2004 09:29:57 +1000 (EST)
	(envelope-from garmitage@swin.edu.au)
Message-ID: <409EBEF4.79BEA1F5@swin.edu.au>
Date: Mon, 10 May 2004 09:29:56 +1000
From: grenville armitage <garmitage@swin.edu.au>
Organization: Centre for Advanced Internet Architectures, Swinburne University of 
 Technology
X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Not sure if this is the right place for this
References: <DD72EEC3-A1E7-11D8-8626-003065F939FE@rudd.cc>
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


John Rudd wrote:
	[..]
> The problem with the STARTTLS strategy is: you can't guarantee at the
> network level that a client will use SSL/TLS.  The service provider
> might be able to do that [...] but the
> network provider cannot.  In large organizations, or situations with
> outsourced services, those two groups may not be the same.  This leads
> to a situation where a networking service may be trying to enforce a
> mandate of "secure protocols only", but cannot do so under the STARTTLS
> strategy.

Your problem lies within this paragraph. If one _has_ decoupled the network
service and end-user service provision then the network service provider has
no place mandating the behaviours (and port usages) of the end-user service
providers (such as email server administrators).

Or in your particular case, the wireless network group should get out of _your_
space (as the email system administrator) and just let you get on with enforcing
your email access security policy with STARTTLS on regular ports.

There's no need to change the RFCs in the way you've suggested.

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

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



From ietf-admin@ietf.org  Sun May  9 19:40: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 TAA28288
	for <ietf-archive@ietf.org>; Sun, 9 May 2004 19:40:32 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BMxuK-0000mP-Ah
	for ietf-archive@ietf.org; Sun, 09 May 2004 19:40:32 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMxtI-0000P7-00
	for ietf-archive@ietf.org; Sun, 09 May 2004 19:39:29 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMxs3-00005I-00
	for ietf-archive@ietf.org; Sun, 09 May 2004 19:38:11 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMxo2-0004p0-JP; Sun, 09 May 2004 19:34:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMxmJ-0004gH-6q
	for ietf@optimus.ietf.org; Sun, 09 May 2004 19:32: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 TAA28027
	for <ietf@ietf.org>; Sun, 9 May 2004 19:32: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 1BMxmH-0006A5-8U
	for ietf@ietf.org; Sun, 09 May 2004 19:32:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMxlI-0005ry-00
	for ietf@ietf.org; Sun, 09 May 2004 19:31:12 -0400
Received: from cpe-138-217-63-233.vic.bigpond.net.au ([138.217.63.233] helo=7020bsd.)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMxkL-0005Ka-00
	for ietf@ietf.org; Sun, 09 May 2004 19:30:13 -0400
Received: from swin.edu.au (localhost [127.0.0.1])
	by 7020bsd. (8.12.6/8.12.6) with ESMTP id i49NTuhX000304;
	Mon, 10 May 2004 09:29:57 +1000 (EST)
	(envelope-from garmitage@swin.edu.au)
Message-ID: <409EBEF4.79BEA1F5@swin.edu.au>
Date: Mon, 10 May 2004 09:29:56 +1000
From: grenville armitage <garmitage@swin.edu.au>
Organization: Centre for Advanced Internet Architectures, Swinburne University of 
 Technology
X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Not sure if this is the right place for this
References: <DD72EEC3-A1E7-11D8-8626-003065F939FE@rudd.cc>
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


John Rudd wrote:
	[..]
> The problem with the STARTTLS strategy is: you can't guarantee at the
> network level that a client will use SSL/TLS.  The service provider
> might be able to do that [...] but the
> network provider cannot.  In large organizations, or situations with
> outsourced services, those two groups may not be the same.  This leads
> to a situation where a networking service may be trying to enforce a
> mandate of "secure protocols only", but cannot do so under the STARTTLS
> strategy.

Your problem lies within this paragraph. If one _has_ decoupled the network
service and end-user service provision then the network service provider has
no place mandating the behaviours (and port usages) of the end-user service
providers (such as email server administrators).

Or in your particular case, the wireless network group should get out of _your_
space (as the email system administrator) and just let you get on with enforcing
your email access security policy with STARTTLS on regular ports.

There's no need to change the RFCs in the way you've suggested.

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

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


From ietf-admin@ietf.org  Sun May  9 19:46: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 TAA28621
	for <ietf-archive@ietf.org>; Sun, 9 May 2004 19:46: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 1BMy00-0002d9-3R
	for ietf-archive@ietf.org; Sun, 09 May 2004 19:46:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMxz3-0002Jj-00
	for ietf-archive@ietf.org; Sun, 09 May 2004 19:45:26 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMxy7-00020Z-00
	for ietf-archive@ietf.org; Sun, 09 May 2004 19:44:27 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMxtu-0005sm-Qh; Sun, 09 May 2004 19:40:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMxq3-0004yX-Gy
	for ietf@optimus.ietf.org; Sun, 09 May 2004 19:36:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28182
	for <ietf@ietf.org>; Sun, 9 May 2004 19:36: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 1BMxq1-0007Jp-Io
	for ietf@ietf.org; Sun, 09 May 2004 19:36:05 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMxp9-00073G-00
	for ietf@ietf.org; Sun, 09 May 2004 19:35:11 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMxoH-0006UU-00
	for ietf@ietf.org; Sun, 09 May 2004 19:34: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 i49NXdxl005497
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Sun, 9 May 2004 19:33:40 -0400
Date: Sun, 9 May 2004 19:33:39 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
cc: Rajat <myself_rajat@yahoo.com>, <ietf@ietf.org>
Subject: Re: Problem of blocking ICMP packets
In-Reply-To: <409BF2F5.2080304@necom830.hpcl.titech.ac.jp>
Message-ID: <Pine.LNX.4.44.0405091926270.4953-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 Sat, 8 May 2004, Masataka Ohta wrote:
> 
> I recommend that, to avoid long initial delay and intermediate
> lack of communication after path changes of, PMTUD should turnd
> off by default and should be activated only on extreme
> conditions.

Just the opposite, unless you want to lose connectivity with a number of 
web servers that want to send big packets with DF turned on.


> Further, it should be noted that PMTUD is so unreliable that
> no applications rely on it, which means that even under
> extreme conditions rational operators won't turn on PMTUD.

It is not true that no applications rely on PMTU. A number of commercial
products and applications do rely on PMTU to work, and will do an PATH MTU 
discovery, and send the MTU sized packets with DF (don't frag).  If you 
have a smaller MTU somewhere that was not discovered, such DF marked 
packets will be dropped.

This is the first I have heard that path mtu discovery software was
unreliable.  I have only heard that those that block ICMP echo have had
problems.  This doesn't make PMTU unreliable. It makes the concept of
blocking ICMP echo unwise.

I suggest, that if you want to use security by obscurity, that you use 
NAT, and that you permit ICMP echo to the NAT device.

		--Dean


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


From exim@www1.ietf.org  Sun May  9 19:48:56 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 TAA28743
	for <ietf-archive@odin.ietf.org>; Sun, 9 May 2004 19:48: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 1BMxy8-0006Q1-FK
	for ietf-archive@odin.ietf.org; Sun, 09 May 2004 19:44:31 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i49NiSvc024636
	for ietf-archive@odin.ietf.org; Sun, 9 May 2004 19:44:28 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMxtu-0005sm-Qh; Sun, 09 May 2004 19:40:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMxq3-0004yX-Gy
	for ietf@optimus.ietf.org; Sun, 09 May 2004 19:36:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28182
	for <ietf@ietf.org>; Sun, 9 May 2004 19:36: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 1BMxq1-0007Jp-Io
	for ietf@ietf.org; Sun, 09 May 2004 19:36:05 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMxp9-00073G-00
	for ietf@ietf.org; Sun, 09 May 2004 19:35:11 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMxoH-0006UU-00
	for ietf@ietf.org; Sun, 09 May 2004 19:34: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 i49NXdxl005497
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Sun, 9 May 2004 19:33:40 -0400
Date: Sun, 9 May 2004 19:33:39 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
cc: Rajat <myself_rajat@yahoo.com>, <ietf@ietf.org>
Subject: Re: Problem of blocking ICMP packets
In-Reply-To: <409BF2F5.2080304@necom830.hpcl.titech.ac.jp>
Message-ID: <Pine.LNX.4.44.0405091926270.4953-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 Sat, 8 May 2004, Masataka Ohta wrote:
> 
> I recommend that, to avoid long initial delay and intermediate
> lack of communication after path changes of, PMTUD should turnd
> off by default and should be activated only on extreme
> conditions.

Just the opposite, unless you want to lose connectivity with a number of 
web servers that want to send big packets with DF turned on.


> Further, it should be noted that PMTUD is so unreliable that
> no applications rely on it, which means that even under
> extreme conditions rational operators won't turn on PMTUD.

It is not true that no applications rely on PMTU. A number of commercial
products and applications do rely on PMTU to work, and will do an PATH MTU 
discovery, and send the MTU sized packets with DF (don't frag).  If you 
have a smaller MTU somewhere that was not discovered, such DF marked 
packets will be dropped.

This is the first I have heard that path mtu discovery software was
unreliable.  I have only heard that those that block ICMP echo have had
problems.  This doesn't make PMTU unreliable. It makes the concept of
blocking ICMP echo unwise.

I suggest, that if you want to use security by obscurity, that you use 
NAT, and that you permit ICMP echo to the NAT device.

		--Dean


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



From ietf-admin@ietf.org  Sun May  9 19:56:33 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28897
	for <ietf-archive@ietf.org>; Sun, 9 May 2004 19:56: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 1BMy9o-0005Vd-Mg
	for ietf-archive@ietf.org; Sun, 09 May 2004 19:56:32 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMy8Y-00059O-00
	for ietf-archive@ietf.org; Sun, 09 May 2004 19:55:15 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMy7d-0004rN-00
	for ietf-archive@ietf.org; Sun, 09 May 2004 19:54:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMy2b-0006mh-3k; Sun, 09 May 2004 19:49:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMxxt-0006Oq-FU
	for ietf@optimus.ietf.org; Sun, 09 May 2004 19:44:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28566
	for <ietf@ietf.org>; Sun, 9 May 2004 19:44: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 1BMxxp-0001zE-LV
	for ietf@ietf.org; Sun, 09 May 2004 19:44:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMxws-0001iE-00
	for ietf@ietf.org; Sun, 09 May 2004 19:43:11 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMxwX-0001RQ-00
	for ietf@ietf.org; Sun, 09 May 2004 19:42: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 i49NgJDR005679
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Sun, 9 May 2004 19:42:19 -0400
Date: Sun, 9 May 2004 19:42:19 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: John Rudd <john@rudd.cc>
cc: ietf@ietf.org
Subject: Re: Not sure if this is the right place for this
In-Reply-To: <DD72EEC3-A1E7-11D8-8626-003065F939FE@rudd.cc>
Message-ID: <Pine.LNX.4.44.0405091933500.4953-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

This is not an IETF problem, but a general problem with upgrading legacy
services and software. Everyone has this same problem, and has to choose
their own approach to the problem.  You cannot move faster than your
client software base.  It means that you may have to either adjust your
security policy to accomodate those legacy clients, or exclude legacy
clients altogether.  Some people must do the former. Some other people can
do the latter.

Since you are in a limited internal academic environment, you probably
have more lattitude to specify that all of your users use a given set of
software products that meets your security and software protocol goals.  
However, if for some reason this is unsuitable, then you have to adjust
your security policy. Those are your choices.

One thing: You should pay close attention to the fact that some of the
protocols you have mentioned are experimental, and probably should not be
used for production environments.

		--Dean

On Sun, 9 May 2004, John Rudd wrote:

> 
> I've noticed a trend with the adoption of SSL/TLS that I'm not sure is 
> really in the best long term interests of the community.
> 
> It seems that early on an "alternate port" strategy is/was adopted, 
> such as having an SSL only version of POP on port 995, IMAP on 993, and 
> SMTP on 465.  These ports start p with an SSL session before any data 
> is sent, so only SSL enabled clients are able to attach. (I will refer 
> to this as the "alternate port strategy")
> 
> Then, as time has marched on, and the "STARTTLS" command was 
> implimented, SSL/TLS has been integrated into the "primary port".  So, 
> now, SSL/TLS is handled on ports 110, 143, and 25 (respectively), with 
> SSL/TLS being initiated (by the client sending the "STARTTLS" command) 
> after the plain-text session has started.  When this shows up in the 
> RFC for extensions to the protocol, the alternate port method is 
> usually then mentioned as "deprecated".  (I will refer to this as the 
> "STARTTLS strategy").
> 
> 
> The problem with the STARTTLS strategy is: you can't guarantee at the 
> network level that a client will use SSL/TLS.  The service provider 
> might be able to do that (ex: CommuniGate Pro, a mail server from 
> stalker.com, has an option to require "secure logins", meaning that 
> they must be happening within an SSL/TLS protected session), but the 
> network provider cannot.  In large organizations, or situations with 
> outsourced services, those two groups may not be the same.  This leads 
> to a situation where a networking service may be trying to enforce a 
> mandate of "secure protocols only", but cannot do so under the STARTTLS 
> strategy.
> 
> This is our current issue at UCSC with the deployment of wireless 
> access points.  I, the email administrator, can't currently require 
> "secure logins" because of some legacy issues.  As dangerous as it may 
> be, I can't disallow plain text sessions yet.  Yet, the wireless group 
> doesn't trust WEP (for good reasons), and has decided that wireless 
> privacy must come from SSL/TLS enabled protocols ... so they're 
> blocking the non-SSL/TLS ports.  You can't get to POP via 110, IMAP via 
> 143, nor SMTP via 25.  If you want to check your email, you have to it 
> via the Alternate Port strategy.
> 
> Personally, I'm quite happy with their agenda.  But I have a concern: 
> clients which are aiming at RFC compliance now see that the RFCs which 
> cover them consider the Alternate Port strategy to be deprecated.  So, 
> we cannot depend upon current clients to "do the smart thing" and have 
> the Alternate Port strategy available.  Yet, the Alternate Port 
> strategy is the only way to, at the network level, enforce SSL/TLS*.  
> So, the Alternate Port strategy still has some very real, very lasting 
> value.  If the Alternate Port strategy were to be considered "current", 
> then it might encourage authors to embrace both strategies (the best 
> path).
> 
> 
> (* Yes, someone could merely start a standard STARTTLS based server on 
> ports 993, 995, etc. and circumvent the network agenda, but we're not 
> so concerned about that type of blatant action, we're concerned with 
> typical software in typical configurations being able to be pigeonholed 
> into only having the option of entering in to SSL/TLS sessions.)
> 
> So, what I would like to see, as a general agenda for the RFC's is:
> 
> 1) The Alternate Port strategy should no longer be deprecated for any 
> protocol
> 2) Those services (such as the Message Submission Protocol) that were 
> created with an assumed dependance upon STARTTLS should be extented to 
> also have an Alternate Port for SSL/TLS only.
> 3) Standard Compliance (of the software) should depend upon 
> implementing both strategies, not one or the other (but it would be 
> acceptable if the systems administrator were to not activate both 
> strategies, which is why I inserted "of the software").
> 
> 
> _______________________________________________
> 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  Sun May  9 20:04:44 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 UAA29956
	for <ietf-archive@odin.ietf.org>; Sun, 9 May 2004 20:04: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 1BMy7e-0007b7-K1
	for ietf-archive@odin.ietf.org; Sun, 09 May 2004 19:54:18 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i49NsI8b029197
	for ietf-archive@odin.ietf.org; Sun, 9 May 2004 19:54:18 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMy2b-0006mh-3k; Sun, 09 May 2004 19:49:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMxxt-0006Oq-FU
	for ietf@optimus.ietf.org; Sun, 09 May 2004 19:44:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28566
	for <ietf@ietf.org>; Sun, 9 May 2004 19:44: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 1BMxxp-0001zE-LV
	for ietf@ietf.org; Sun, 09 May 2004 19:44:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMxws-0001iE-00
	for ietf@ietf.org; Sun, 09 May 2004 19:43:11 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMxwX-0001RQ-00
	for ietf@ietf.org; Sun, 09 May 2004 19:42: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 i49NgJDR005679
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Sun, 9 May 2004 19:42:19 -0400
Date: Sun, 9 May 2004 19:42:19 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: John Rudd <john@rudd.cc>
cc: ietf@ietf.org
Subject: Re: Not sure if this is the right place for this
In-Reply-To: <DD72EEC3-A1E7-11D8-8626-003065F939FE@rudd.cc>
Message-ID: <Pine.LNX.4.44.0405091933500.4953-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>

This is not an IETF problem, but a general problem with upgrading legacy
services and software. Everyone has this same problem, and has to choose
their own approach to the problem.  You cannot move faster than your
client software base.  It means that you may have to either adjust your
security policy to accomodate those legacy clients, or exclude legacy
clients altogether.  Some people must do the former. Some other people can
do the latter.

Since you are in a limited internal academic environment, you probably
have more lattitude to specify that all of your users use a given set of
software products that meets your security and software protocol goals.  
However, if for some reason this is unsuitable, then you have to adjust
your security policy. Those are your choices.

One thing: You should pay close attention to the fact that some of the
protocols you have mentioned are experimental, and probably should not be
used for production environments.

		--Dean

On Sun, 9 May 2004, John Rudd wrote:

> 
> I've noticed a trend with the adoption of SSL/TLS that I'm not sure is 
> really in the best long term interests of the community.
> 
> It seems that early on an "alternate port" strategy is/was adopted, 
> such as having an SSL only version of POP on port 995, IMAP on 993, and 
> SMTP on 465.  These ports start p with an SSL session before any data 
> is sent, so only SSL enabled clients are able to attach. (I will refer 
> to this as the "alternate port strategy")
> 
> Then, as time has marched on, and the "STARTTLS" command was 
> implimented, SSL/TLS has been integrated into the "primary port".  So, 
> now, SSL/TLS is handled on ports 110, 143, and 25 (respectively), with 
> SSL/TLS being initiated (by the client sending the "STARTTLS" command) 
> after the plain-text session has started.  When this shows up in the 
> RFC for extensions to the protocol, the alternate port method is 
> usually then mentioned as "deprecated".  (I will refer to this as the 
> "STARTTLS strategy").
> 
> 
> The problem with the STARTTLS strategy is: you can't guarantee at the 
> network level that a client will use SSL/TLS.  The service provider 
> might be able to do that (ex: CommuniGate Pro, a mail server from 
> stalker.com, has an option to require "secure logins", meaning that 
> they must be happening within an SSL/TLS protected session), but the 
> network provider cannot.  In large organizations, or situations with 
> outsourced services, those two groups may not be the same.  This leads 
> to a situation where a networking service may be trying to enforce a 
> mandate of "secure protocols only", but cannot do so under the STARTTLS 
> strategy.
> 
> This is our current issue at UCSC with the deployment of wireless 
> access points.  I, the email administrator, can't currently require 
> "secure logins" because of some legacy issues.  As dangerous as it may 
> be, I can't disallow plain text sessions yet.  Yet, the wireless group 
> doesn't trust WEP (for good reasons), and has decided that wireless 
> privacy must come from SSL/TLS enabled protocols ... so they're 
> blocking the non-SSL/TLS ports.  You can't get to POP via 110, IMAP via 
> 143, nor SMTP via 25.  If you want to check your email, you have to it 
> via the Alternate Port strategy.
> 
> Personally, I'm quite happy with their agenda.  But I have a concern: 
> clients which are aiming at RFC compliance now see that the RFCs which 
> cover them consider the Alternate Port strategy to be deprecated.  So, 
> we cannot depend upon current clients to "do the smart thing" and have 
> the Alternate Port strategy available.  Yet, the Alternate Port 
> strategy is the only way to, at the network level, enforce SSL/TLS*.  
> So, the Alternate Port strategy still has some very real, very lasting 
> value.  If the Alternate Port strategy were to be considered "current", 
> then it might encourage authors to embrace both strategies (the best 
> path).
> 
> 
> (* Yes, someone could merely start a standard STARTTLS based server on 
> ports 993, 995, etc. and circumvent the network agenda, but we're not 
> so concerned about that type of blatant action, we're concerned with 
> typical software in typical configurations being able to be pigeonholed 
> into only having the option of entering in to SSL/TLS sessions.)
> 
> So, what I would like to see, as a general agenda for the RFC's is:
> 
> 1) The Alternate Port strategy should no longer be deprecated for any 
> protocol
> 2) Those services (such as the Message Submission Protocol) that were 
> created with an assumed dependance upon STARTTLS should be extented to 
> also have an Alternate Port for SSL/TLS only.
> 3) Standard Compliance (of the software) should depend upon 
> implementing both strategies, not one or the other (but it would be 
> acceptable if the systems administrator were to not activate both 
> strategies, which is why I inserted "of the software").
> 
> 
> _______________________________________________
> 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  Sun May  9 22:01: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 WAA03825
	for <ietf-archive@ietf.org>; Sun, 9 May 2004 22:01: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 1BN06j-0002rr-BH
	for ietf-archive@ietf.org; Sun, 09 May 2004 22:01:29 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BN05m-0002Xu-00
	for ietf-archive@ietf.org; Sun, 09 May 2004 22:00:30 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BN052-0002Ey-00
	for ietf-archive@ietf.org; Sun, 09 May 2004 21:59:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BN00V-0001hm-Iv; Sun, 09 May 2004 21:55:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMzyo-0001bM-Lo
	for ietf@optimus.ietf.org; Sun, 09 May 2004 21:53:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03677
	for <ietf@ietf.org>; Sun, 9 May 2004 21:53: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 1BMzyl-0000XA-Kp
	for ietf@ietf.org; Sun, 09 May 2004 21:53:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMzxs-0000G9-00
	for ietf@ietf.org; Sun, 09 May 2004 21:52:21 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with smtp (Exim 4.12)
	id 1BMzxS-0007lw-00
	for ietf@ietf.org; Sun, 09 May 2004 21:51:54 -0400
Received: (qmail 8544 invoked from network); 10 May 2004 01:53:58 -0000
Received: from vaio.hpcl.titech.ac.jp (HELO necom830.hpcl.titech.ac.jp) (131.112.32.134)
  by necom830.hpcl.titech.ac.jp with SMTP; 10 May 2004 01:53:58 -0000
Message-ID: <409EE11F.9070601@necom830.hpcl.titech.ac.jp>
Date: Mon, 10 May 2004 10:55:43 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: ja, en-us, en
MIME-Version: 1.0
To: Dean Anderson <dean@av8.com>
CC: Rajat <myself_rajat@yahoo.com>, ietf@ietf.org
Subject: Re: Problem of blocking ICMP packets
References: <Pine.LNX.4.44.0405091926270.4953-100000@cirrus.av8.net>
In-Reply-To: <Pine.LNX.4.44.0405091926270.4953-100000@cirrus.av8.net>
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=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Dean Anderson;

>>I recommend that, to avoid long initial delay and intermediate
>>lack of communication after path changes of, PMTUD should turnd
>>off by default and should be activated only on extreme
>>conditions.

> Just the opposite, unless you want to lose connectivity with a number of 
> web servers that want to send big packets with DF turned on.

There were (still are?) number of web servers that wanted to send
big packets with DF turned on, because PMTUD was turned on on the
servers but ICMP errors were filtered.

> A number of commercial
> products and applications do rely on PMTU to work, and will do an PATH MTU 
> discovery, and send the MTU sized packets with DF (don't frag).

and send packets larger than MTU expecting to receive ICMP
errors in vain.

Read the original mail of the thread on the reality.

> This is the first I have heard that path mtu discovery software was
> unreliable.

PMTUD software is unreliable!?

Then, it is anther reason to avoid it.

Can you tell me who said it with an appropriate reference?

						Masataka Ohta




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


From exim@www1.ietf.org  Sun May  9 22:01:40 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 WAA03858
	for <ietf-archive@odin.ietf.org>; Sun, 9 May 2004 22:01:40 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BN055-0002NW-0S
	for ietf-archive@odin.ietf.org; Sun, 09 May 2004 21:59:49 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4A1xkCS008887
	for ietf-archive@odin.ietf.org; Sun, 9 May 2004 21:59:46 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BN00V-0001hm-Iv; Sun, 09 May 2004 21:55:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMzyo-0001bM-Lo
	for ietf@optimus.ietf.org; Sun, 09 May 2004 21:53:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03677
	for <ietf@ietf.org>; Sun, 9 May 2004 21:53: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 1BMzyl-0000XA-Kp
	for ietf@ietf.org; Sun, 09 May 2004 21:53:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMzxs-0000G9-00
	for ietf@ietf.org; Sun, 09 May 2004 21:52:21 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with smtp (Exim 4.12)
	id 1BMzxS-0007lw-00
	for ietf@ietf.org; Sun, 09 May 2004 21:51:54 -0400
Received: (qmail 8544 invoked from network); 10 May 2004 01:53:58 -0000
Received: from vaio.hpcl.titech.ac.jp (HELO necom830.hpcl.titech.ac.jp) (131.112.32.134)
  by necom830.hpcl.titech.ac.jp with SMTP; 10 May 2004 01:53:58 -0000
Message-ID: <409EE11F.9070601@necom830.hpcl.titech.ac.jp>
Date: Mon, 10 May 2004 10:55:43 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: ja, en-us, en
MIME-Version: 1.0
To: Dean Anderson <dean@av8.com>
CC: Rajat <myself_rajat@yahoo.com>, ietf@ietf.org
Subject: Re: Problem of blocking ICMP packets
References: <Pine.LNX.4.44.0405091926270.4953-100000@cirrus.av8.net>
In-Reply-To: <Pine.LNX.4.44.0405091926270.4953-100000@cirrus.av8.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: 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;

>>I recommend that, to avoid long initial delay and intermediate
>>lack of communication after path changes of, PMTUD should turnd
>>off by default and should be activated only on extreme
>>conditions.

> Just the opposite, unless you want to lose connectivity with a number of 
> web servers that want to send big packets with DF turned on.

There were (still are?) number of web servers that wanted to send
big packets with DF turned on, because PMTUD was turned on on the
servers but ICMP errors were filtered.

> A number of commercial
> products and applications do rely on PMTU to work, and will do an PATH MTU 
> discovery, and send the MTU sized packets with DF (don't frag).

and send packets larger than MTU expecting to receive ICMP
errors in vain.

Read the original mail of the thread on the reality.

> This is the first I have heard that path mtu discovery software was
> unreliable.

PMTUD software is unreliable!?

Then, it is anther reason to avoid it.

Can you tell me who said it with an appropriate reference?

						Masataka Ohta




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



From ietf-admin@ietf.org  Sun May  9 23:24: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 XAA06104
	for <ietf-archive@ietf.org>; Sun, 9 May 2004 23:24: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 1BN1PA-0003CE-1Q
	for ietf-archive@ietf.org; Sun, 09 May 2004 23:24:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BN1O0-0002sk-00
	for ietf-archive@ietf.org; Sun, 09 May 2004 23:23:25 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BN1NT-0002ad-00
	for ietf-archive@ietf.org; Sun, 09 May 2004 23:22:51 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BN1Dx-0000HN-12; Sun, 09 May 2004 23:13:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BN1CV-0000AW-An
	for ietf@optimus.ietf.org; Sun, 09 May 2004 23:11: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 XAA05737
	for <ietf@ietf.org>; Sun, 9 May 2004 23:11: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 1BN1CQ-0007Cn-O1
	for ietf@ietf.org; Sun, 09 May 2004 23:11:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BN1BN-0006u8-00
	for ietf@ietf.org; Sun, 09 May 2004 23:10:23 -0400
Received: from rudd.cc ([64.81.246.247])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BN19r-0006LR-00
	for ietf@ietf.org; Sun, 09 May 2004 23:08:47 -0400
Received: from [10.0.1.220] (arcadia.rudd.cc [10.0.1.220])
	by rudd.cc (8.11.1/8.11.1) with ESMTP id i4A38e990183;
	Sun, 9 May 2004 20:08:40 -0700 (PDT)
	(envelope-from john@rudd.cc)
In-Reply-To: <01L9WHXTN6820062TI@mauve.mrochek.com>
References: <DD72EEC3-A1E7-11D8-8626-003065F939FE@rudd.cc> <01L9WHXTN6820062TI@mauve.mrochek.com>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <573634C6-A22F-11D8-8626-003065F939FE@rudd.cc>
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
From: John Rudd <john@rudd.cc>
Subject: Re: Not sure if this is the right place for this
Date: Sun, 9 May 2004 20:08:41 -0700
To: ned.freed@mrochek.com
X-Mailer: Apple Mail (2.613)
X-DOMAIN-ORG-MailScanner: Found to be clean
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 May 9, 2004, at 7:33 PM, ned.freed@mrochek.com wrote:

>> I've noticed a trend with the adoption of SSL/TLS that I'm not sure is
>> really in the best long term interests of the community.
>
> I believe there's a strong consensus that this trend _is_ in the best 
> long
> interests of the community.

[snip]
>> (I will refer
>> to this as the "alternate port strategy")
>
> This strategy suffers from several serious flaws, especially in 
> situations
> where SSL/TLS is only used some of the time.

[snip]
> Offering alternate port support is no longer a "smart thing" to do.

So, you given this conclusion 3 times (that it's not in the best long 
term interest, that it's flawed, and that it's not the smart thing to 
do).  Would you care to elaborate at all on that?

What are the flaws?  How is it not good for the community?


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


From exim@www1.ietf.org  Sun May  9 23:27:38 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 XAA06203
	for <ietf-archive@odin.ietf.org>; Sun, 9 May 2004 23:27:38 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BN1NU-00019v-JX
	for ietf-archive@odin.ietf.org; Sun, 09 May 2004 23:22:52 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4A3MqYb004378
	for ietf-archive@odin.ietf.org; Sun, 9 May 2004 23:22:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BN1Dx-0000HN-12; Sun, 09 May 2004 23:13:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BN1CV-0000AW-An
	for ietf@optimus.ietf.org; Sun, 09 May 2004 23:11: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 XAA05737
	for <ietf@ietf.org>; Sun, 9 May 2004 23:11: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 1BN1CQ-0007Cn-O1
	for ietf@ietf.org; Sun, 09 May 2004 23:11:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BN1BN-0006u8-00
	for ietf@ietf.org; Sun, 09 May 2004 23:10:23 -0400
Received: from rudd.cc ([64.81.246.247])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BN19r-0006LR-00
	for ietf@ietf.org; Sun, 09 May 2004 23:08:47 -0400
Received: from [10.0.1.220] (arcadia.rudd.cc [10.0.1.220])
	by rudd.cc (8.11.1/8.11.1) with ESMTP id i4A38e990183;
	Sun, 9 May 2004 20:08:40 -0700 (PDT)
	(envelope-from john@rudd.cc)
In-Reply-To: <01L9WHXTN6820062TI@mauve.mrochek.com>
References: <DD72EEC3-A1E7-11D8-8626-003065F939FE@rudd.cc> <01L9WHXTN6820062TI@mauve.mrochek.com>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <573634C6-A22F-11D8-8626-003065F939FE@rudd.cc>
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
From: John Rudd <john@rudd.cc>
Subject: Re: Not sure if this is the right place for this
Date: Sun, 9 May 2004 20:08:41 -0700
To: ned.freed@mrochek.com
X-Mailer: Apple Mail (2.613)
X-DOMAIN-ORG-MailScanner: Found to be clean
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
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 May 9, 2004, at 7:33 PM, ned.freed@mrochek.com wrote:

>> I've noticed a trend with the adoption of SSL/TLS that I'm not sure is
>> really in the best long term interests of the community.
>
> I believe there's a strong consensus that this trend _is_ in the best 
> long
> interests of the community.

[snip]
>> (I will refer
>> to this as the "alternate port strategy")
>
> This strategy suffers from several serious flaws, especially in 
> situations
> where SSL/TLS is only used some of the time.

[snip]
> Offering alternate port support is no longer a "smart thing" to do.

So, you given this conclusion 3 times (that it's not in the best long 
term interest, that it's flawed, and that it's not the smart thing to 
do).  Would you care to elaborate at all on that?

What are the flaws?  How is it not good for the community?


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



From ietf-admin@ietf.org  Sun May  9 23: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 XAA06959
	for <ietf-archive@ietf.org>; Sun, 9 May 2004 23: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 1BN1hR-00012K-P5
	for ietf-archive@ietf.org; Sun, 09 May 2004 23:43:29 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BN1gU-0000jy-00
	for ietf-archive@ietf.org; Sun, 09 May 2004 23:42:31 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BN1fu-0000RZ-00
	for ietf-archive@ietf.org; Sun, 09 May 2004 23:41:54 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BN1YL-0002P0-FW; Sun, 09 May 2004 23:34:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BN1Vi-00027m-GV
	for ietf@optimus.ietf.org; Sun, 09 May 2004 23:31: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 XAA06368
	for <ietf@ietf.org>; Sun, 9 May 2004 23:31: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 1BN1Vg-0005C0-7F
	for ietf@ietf.org; Sun, 09 May 2004 23:31:20 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BN1Uk-0004us-00
	for ietf@ietf.org; Sun, 09 May 2004 23:30:23 -0400
Received: from 250.cust46.nsw.dsl.ozemail.com.au ([203.103.125.250] helo=nosense.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BN1UN-0004dC-00
	for ietf@ietf.org; Sun, 09 May 2004 23:29:59 -0400
Received: from Dupy2.nosense.org (localhost.localdomain [127.0.0.1])
	by nosense.org (Postfix) with SMTP
	id A6D043F02A; Mon, 10 May 2004 13:02:10 +0930 (CST)
Date: Mon, 10 May 2004 13:02:10 +0930
From: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Cc: dean@av8.com, myself_rajat@yahoo.com, ietf@ietf.org
Subject: Re: Problem of blocking ICMP packets
Message-Id: <20040510130210.09ac9313.ietf@130c04165a5b40404e4440445758487a.nosense.org>
In-Reply-To: <409EE11F.9070601@necom830.hpcl.titech.ac.jp>
References: <Pine.LNX.4.44.0405091926270.4953-100000@cirrus.av8.net>
	<409EE11F.9070601@necom830.hpcl.titech.ac.jp>
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

On Mon, 10 May 2004 10:55:43 +0900
Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> wrote:

> Dean Anderson;
> 

> > A number of commercial
> > products and applications do rely on PMTU to work, and will
> > do an PATH MTU discovery, and send the MTU sized packets with
> > DF (don't frag).
> 
> and send packets larger than MTU expecting to receive ICMP
> errors in vain.
> 
> Read the original mail of the thread on the reality.
> 

The problem identified has nothing to do with the concept or
typical implementations of PMTUD being broken.

RFC1192 (http://www.rfc-editor.org/rfc/rfc1191.txt) is the spec
for PMTUD. 

The issue that PMTUD is addressing is :

"1. Introduction

   When one IP host has a large amount of data to send to another
host, the data is transmitted as a series of IP datagrams.  It
is usually preferable that these datagrams be of the largest
size that does not require fragmentation anywhere along the path
from the source to the  destination.  (For the case against
fragmentation, see [5].)  This datagram size is referred to as
the Path MTU (PMTU), and it is equal to the minimum of the MTUs
of each hop in the path. A shortcoming of the current Internet
protocol suite is the lack of a standard mechanism for a host
to discover the PMTU of an arbitrary path."

PMTUD is a performance optimisation, specifically a throughput
optimisation. 

The problem being discussed is directly caused by broken
firewall/NAT devices or configurations, blocking network
management traffic (ie. ICMP Destination Unreachable,
Fragmentation Needed and Don't Fragment was Set) that they
should be permitting.

Regards,
Mark.


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


From exim@www1.ietf.org  Sun May  9 23:46: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 XAA07109
	for <ietf-archive@odin.ietf.org>; Sun, 9 May 2004 23:46: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 1BN1fv-0003ZZ-Jo
	for ietf-archive@odin.ietf.org; Sun, 09 May 2004 23:42:01 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4A3ftLj013714
	for ietf-archive@odin.ietf.org; Sun, 9 May 2004 23:41:55 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BN1YL-0002P0-FW; Sun, 09 May 2004 23:34:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BN1Vi-00027m-GV
	for ietf@optimus.ietf.org; Sun, 09 May 2004 23:31: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 XAA06368
	for <ietf@ietf.org>; Sun, 9 May 2004 23:31: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 1BN1Vg-0005C0-7F
	for ietf@ietf.org; Sun, 09 May 2004 23:31:20 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BN1Uk-0004us-00
	for ietf@ietf.org; Sun, 09 May 2004 23:30:23 -0400
Received: from 250.cust46.nsw.dsl.ozemail.com.au ([203.103.125.250] helo=nosense.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BN1UN-0004dC-00
	for ietf@ietf.org; Sun, 09 May 2004 23:29:59 -0400
Received: from Dupy2.nosense.org (localhost.localdomain [127.0.0.1])
	by nosense.org (Postfix) with SMTP
	id A6D043F02A; Mon, 10 May 2004 13:02:10 +0930 (CST)
Date: Mon, 10 May 2004 13:02:10 +0930
From: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Cc: dean@av8.com, myself_rajat@yahoo.com, ietf@ietf.org
Subject: Re: Problem of blocking ICMP packets
Message-Id: <20040510130210.09ac9313.ietf@130c04165a5b40404e4440445758487a.nosense.org>
In-Reply-To: <409EE11F.9070601@necom830.hpcl.titech.ac.jp>
References: <Pine.LNX.4.44.0405091926270.4953-100000@cirrus.av8.net>
	<409EE11F.9070601@necom830.hpcl.titech.ac.jp>
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

On Mon, 10 May 2004 10:55:43 +0900
Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> wrote:

> Dean Anderson;
> 

> > A number of commercial
> > products and applications do rely on PMTU to work, and will
> > do an PATH MTU discovery, and send the MTU sized packets with
> > DF (don't frag).
> 
> and send packets larger than MTU expecting to receive ICMP
> errors in vain.
> 
> Read the original mail of the thread on the reality.
> 

The problem identified has nothing to do with the concept or
typical implementations of PMTUD being broken.

RFC1192 (http://www.rfc-editor.org/rfc/rfc1191.txt) is the spec
for PMTUD. 

The issue that PMTUD is addressing is :

"1. Introduction

   When one IP host has a large amount of data to send to another
host, the data is transmitted as a series of IP datagrams.  It
is usually preferable that these datagrams be of the largest
size that does not require fragmentation anywhere along the path
from the source to the  destination.  (For the case against
fragmentation, see [5].)  This datagram size is referred to as
the Path MTU (PMTU), and it is equal to the minimum of the MTUs
of each hop in the path. A shortcoming of the current Internet
protocol suite is the lack of a standard mechanism for a host
to discover the PMTU of an arbitrary path."

PMTUD is a performance optimisation, specifically a throughput
optimisation. 

The problem being discussed is directly caused by broken
firewall/NAT devices or configurations, blocking network
management traffic (ie. ICMP Destination Unreachable,
Fragmentation Needed and Don't Fragment was Set) that they
should be permitting.

Regards,
Mark.


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



From ietf-admin@ietf.org  Mon May 10 08:44: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 IAA29976
	for <ietf-archive@ietf.org>; Mon, 10 May 2004 08:44: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 1BNA9B-0002X0-Mv
	for ietf-archive@ietf.org; Mon, 10 May 2004 08:44:41 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNA8C-0002Bf-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 08:43:41 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNA78-0001eF-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 08:42:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BN9s5-0005fn-6q; Mon, 10 May 2004 08:27:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMa6B-0007DD-ER
	for ietf@optimus.ietf.org; Sat, 08 May 2004 18:15: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 SAA29384
	for <ietf@ietf.org>; Sat, 8 May 2004 18:15: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 1BMa68-0007FP-Ja
	for ietf@ietf.org; Sat, 08 May 2004 18:15:08 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMa5E-0006tL-00
	for ietf@ietf.org; Sat, 08 May 2004 18:14:13 -0400
Received: from mailer2.psc.edu ([128.182.66.106])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMa4j-0006Wx-00
	for ietf@ietf.org; Sat, 08 May 2004 18:13:41 -0400
Received: from tesla.psc.edu (tesla.psc.edu [128.182.61.233])
	by mailer2.psc.edu (8.12.10/8.12.5) with ESMTP id i48MDUKa019269
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <ietf@ietf.org>; Sat, 8 May 2004 18:13:31 -0400 (EDT)
Received: from localhost.psc.edu (localhost.psc.edu [127.0.0.1])
	by tesla.psc.edu (8.12.10/8.12.5) with ESMTP id i48MDU5u022018
	for <ietf@ietf.org>; Sat, 8 May 2004 18:13:30 -0400 (EDT)
Date: Sat, 8 May 2004 18:13:30 -0400 (EDT)
From: Matt Mathis <mathis@psc.edu>
To: ietf@ietf.org
Subject: Re: Problem of blocking ICMP packets
In-Reply-To: <409D5492.1080404@necom830.hpcl.titech.ac.jp>
Message-ID: <Pine.LNX.4.44.0405081756470.25624-100000@zippy.psc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanned: ClamAV version 'clamd / ClamAV version 0.66', clamav-milter version '0.60p'
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 Sun, 9 May 2004, Masataka Ohta wrote:
> Back to the original problem, PMTUD depends on the capabilities
> of intermediate systems on a path to generate certain ICMP,
> generation of which is as complex as fragmentation itself,
> that it is not very end to end.
> 
> That is, PMTUD is a broken concept.

This is the whole point of reopening the original pmtud working group.
http://www.ietf.org/html.charters/pmtud-charter.html

See draft-ietf-pmtud-method-01.txt   I quote:

   This document describes a robust new method for Path MTU Discovery
   that relies on TCP or other Packetization Layer to probe an Internet
   path with progressively larger packets.  This method is described as
   an extension to RFC 1191 and RFC 1981.
   ...
   The general strategy of the new algorithm is to start with a small
   MTU and probe upward, testing successively larger MTUs by probing
   with single packets.  If the probe is successfully delivered, then
   the MTU is raised.  If the probe is lost, it is treated as an MTU
   limitation and not as a congestion signal.


This does not require any messages from the network, and works just fine with 
arbitrary middleboxes that either toss over-sized frames or ICMP 
messages.

Comments, suggestions and additions to the text are welcome.  The document is 
not well baked, but there is running code.   There is some (slightly out of 
date) background info at http://www.psc.edu/~mathis/MTU/#pmtud

Thanks,
--MM--
-------------------------------------------
Matt Mathis      http://www.psc.edu/~mathis
Work:412.268.3319    Home/Cell:412.654.7529
-------------------------------------------


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


From ietf-admin@ietf.org  Mon May 10 08:46: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 IAA00098
	for <ietf-archive@ietf.org>; Mon, 10 May 2004 08:46: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 1BNAAZ-0002wF-0G
	for ietf-archive@ietf.org; Mon, 10 May 2004 08:46:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNA9a-0002aQ-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 08:45:07 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNA8e-0002FN-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 08:44:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BN9s6-0005fz-F6; Mon, 10 May 2004 08:27:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BN5m2-00053N-TI
	for ietf@optimus.ietf.org; Mon, 10 May 2004 04:04: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 EAA15916
	for <ietf@ietf.org>; Mon, 10 May 2004 04:04: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 1BN5lz-0000BH-Sf
	for ietf@ietf.org; Mon, 10 May 2004 04:04:27 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BN5l0-0007dY-00
	for ietf@ietf.org; Mon, 10 May 2004 04:03:27 -0400
Received: from mxout3.cac.washington.edu ([140.142.32.166])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BN5k3-0007KW-00
	for ietf@ietf.org; Mon, 10 May 2004 04:02:27 -0400
Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139])
	by mxout3.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4A82RuY031160;
	Mon, 10 May 2004 01:02:27 -0700
Received: from [192.168.1.109] (c-67-170-59-55.client.comcast.net [67.170.59.55])
	(authenticated bits=0)
	by smtp.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4A82PHo029891
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT);
	Mon, 10 May 2004 01:02:27 -0700
Date: Mon, 10 May 2004 01:02:21 -0700 (PDT)
From: "RL 'Bob' Morgan" <rlmorgan@washington.edu>
X-X-Sender: rlmorgan@perp.cac.washington.edu
To: John Rudd <john@rudd.cc>
cc: IETF <ietf@ietf.org>
Subject: Re: Not sure if this is the right place for this
In-Reply-To: <DD72EEC3-A1E7-11D8-8626-003065F939FE@rudd.cc>
Message-ID: <Pine.LNX.4.58.0405100019050.1405@perp.cac.washington.edu>
References: <DD72EEC3-A1E7-11D8-8626-003065F939FE@rudd.cc>
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

John:

There is actually a list for discussion of this topic,
ietf-apps-tls@imc.org, though it hasn't seen much traffic for quite a
while.

Your note is a reminder that this issue, while much-debated on the various
apps-protocol lists a few years ago when the decisions to invent and
promote STARTTLS were made, is not well-described (so far as I know) in
any RFC.  An informational (or maybe BCP) RFC presenting the reasons why
the separate-port approach is a poor choice, and promoting some good
practices for clients and servers using STARTTLS, would be a good thing
(he said, not quite volunteering).

In a nutshell, the reason STARTTLS is a better approach is that, rather
than treating the use of SSL/TLS as entirely different than other session
characteristics, it permits the use of TLS to be negotiated by client and
server, just as other protocol features are negotiated.  The most
important practical benefit of this is that clients can be designed with
their default behavior to try STARTTLS (perhaps based on a server's
announcing it as a capability), thus giving the generic user the benefits
of TLS-protected connections without having to configure anything.  With
the separate-port approach, the user (in any client I have ever seen) has
to configure the use of the separate port, which in many deployment
scenarios means it doesn't get used at all (since every required obscure
user config step is another $NN of support cost).  (There are lots of
other reasons I won't go into now since I'm up too late already.)

Promoting long-term the use of both STARTTLS and separate ports is also a
bad thing, since having two ways to do the same thing is guaranteed to be
confusing, and security stuff is already confusing enough.
Unfortunately, the separate-port meme has been drilled into people's heads
very effectively by http/https, so it's likely that clients will support
it for a long time to come, but there is no way that this will be anything
other than legacy-compatibility behavior (ie, it won't be specified in
standards RFCs).

Your network administrators are well-meaning, I'm sure, but their policy
is just foolish.  They might reflect on the fact that there are lots of
non-TLS ways to avoid reusable-passwords-in-the-clear with common app
implementations (on the plain old port), including Kerberos, CRAM-MD5,
DIGEST, SRP, and others.  They might reflect on the fact that filtering
out ports just makes people send their traffic over the ports that remain
open, which almost universally includes port 80.  So a "secure ports only"
policy has very little to do with security and very much to do with
organizational power relationships, and making your computing environment
dysfunctional.  Try a "secure servers only" initiative.  It worked much
better for us at my university.

 - RL "Bob"


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


From exim@www1.ietf.org  Mon May 10 08:47:47 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 IAA00336
	for <ietf-archive@odin.ietf.org>; Mon, 10 May 2004 08: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 1BNA78-00013u-TE
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 08:42:35 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4ACgY0l004079
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 08:42:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BN9s5-0005fn-6q; Mon, 10 May 2004 08:27:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMa6B-0007DD-ER
	for ietf@optimus.ietf.org; Sat, 08 May 2004 18:15: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 SAA29384
	for <ietf@ietf.org>; Sat, 8 May 2004 18:15: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 1BMa68-0007FP-Ja
	for ietf@ietf.org; Sat, 08 May 2004 18:15:08 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMa5E-0006tL-00
	for ietf@ietf.org; Sat, 08 May 2004 18:14:13 -0400
Received: from mailer2.psc.edu ([128.182.66.106])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMa4j-0006Wx-00
	for ietf@ietf.org; Sat, 08 May 2004 18:13:41 -0400
Received: from tesla.psc.edu (tesla.psc.edu [128.182.61.233])
	by mailer2.psc.edu (8.12.10/8.12.5) with ESMTP id i48MDUKa019269
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <ietf@ietf.org>; Sat, 8 May 2004 18:13:31 -0400 (EDT)
Received: from localhost.psc.edu (localhost.psc.edu [127.0.0.1])
	by tesla.psc.edu (8.12.10/8.12.5) with ESMTP id i48MDU5u022018
	for <ietf@ietf.org>; Sat, 8 May 2004 18:13:30 -0400 (EDT)
Date: Sat, 8 May 2004 18:13:30 -0400 (EDT)
From: Matt Mathis <mathis@psc.edu>
To: ietf@ietf.org
Subject: Re: Problem of blocking ICMP packets
In-Reply-To: <409D5492.1080404@necom830.hpcl.titech.ac.jp>
Message-ID: <Pine.LNX.4.44.0405081756470.25624-100000@zippy.psc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanned: ClamAV version 'clamd / ClamAV version 0.66', clamav-milter version '0.60p'
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-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 Sun, 9 May 2004, Masataka Ohta wrote:
> Back to the original problem, PMTUD depends on the capabilities
> of intermediate systems on a path to generate certain ICMP,
> generation of which is as complex as fragmentation itself,
> that it is not very end to end.
> 
> That is, PMTUD is a broken concept.

This is the whole point of reopening the original pmtud working group.
http://www.ietf.org/html.charters/pmtud-charter.html

See draft-ietf-pmtud-method-01.txt   I quote:

   This document describes a robust new method for Path MTU Discovery
   that relies on TCP or other Packetization Layer to probe an Internet
   path with progressively larger packets.  This method is described as
   an extension to RFC 1191 and RFC 1981.
   ...
   The general strategy of the new algorithm is to start with a small
   MTU and probe upward, testing successively larger MTUs by probing
   with single packets.  If the probe is successfully delivered, then
   the MTU is raised.  If the probe is lost, it is treated as an MTU
   limitation and not as a congestion signal.


This does not require any messages from the network, and works just fine with 
arbitrary middleboxes that either toss over-sized frames or ICMP 
messages.

Comments, suggestions and additions to the text are welcome.  The document is 
not well baked, but there is running code.   There is some (slightly out of 
date) background info at http://www.psc.edu/~mathis/MTU/#pmtud

Thanks,
--MM--
-------------------------------------------
Matt Mathis      http://www.psc.edu/~mathis
Work:412.268.3319    Home/Cell:412.654.7529
-------------------------------------------


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



From ietf-admin@ietf.org  Mon May 10 09:52: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 JAA04090
	for <ietf-archive@ietf.org>; Mon, 10 May 2004 09:52: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 1BNBD5-00027J-Bu
	for ietf-archive@ietf.org; Mon, 10 May 2004 09:52:47 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNBCD-0001li-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 09:51:54 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNBB6-00019u-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 09:50:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNB5a-0005EE-I4; Mon, 10 May 2004 09:45:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNAwy-0004CL-M2
	for ietf@optimus.ietf.org; Mon, 10 May 2004 09:36: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 JAA03090
	for <ietf@ietf.org>; Mon, 10 May 2004 09:36: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 1BNAww-0003oB-SO
	for ietf@ietf.org; Mon, 10 May 2004 09:36:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNAw8-0003V7-00
	for ietf@ietf.org; Mon, 10 May 2004 09:35: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 1BNAvK-00037L-00; Mon, 10 May 2004 09:34:26 -0400
Received: by newdev.harvard.edu (Postfix, from userid 501)
	id 507B51E6E7C; Mon, 10 May 2004 09:33:51 -0400 (EDT)
To: iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: 'The IESG and RFC Editor documents: Procedures' to BCP
Message-Id: <20040510133351.507B51E6E7C@newdev.harvard.edu>
Date: Mon, 10 May 2004 09:33:51 -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


looks good to me - one suggestion of clearer language and a potential
addition

>   o  Documents for which special rules exist, including IAB documents
>      and April 1st RFCs, and republication of documents from other SDOs
>      - the IESG and the RFC Editor keep a running dialogue on which
>      documents these are

awkward wording - maybe you want to say

   o  The IESG and the RFC Editor keep a running dialogue on which
        documents require special rules (for example, IAB documents,
        April 1st RFCs, and republication of documents from other SDOs)

section 3
>    The IESG may return five different responses

this misses one of the outcomes listed in RFC 2026 - specifically (quoting
from 2026):
	"the IESG recommends that the document be brought within the
	IETF and progressed within the IETF context"

this path has been used from time to time and I think it is a valuable
option - I'd suggest that it be added as a 6th response

Scott

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


From exim@www1.ietf.org  Mon May 10 09:54:59 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 JAA04200
	for <ietf-archive@odin.ietf.org>; Mon, 10 May 2004 09:54: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 1BNBB8-0006QC-Vt
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 09:50:47 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4ADok0T024429
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 09:50:46 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNB5a-0005EE-I4; Mon, 10 May 2004 09:45:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNAwy-0004CL-M2
	for ietf@optimus.ietf.org; Mon, 10 May 2004 09:36: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 JAA03090
	for <ietf@ietf.org>; Mon, 10 May 2004 09:36: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 1BNAww-0003oB-SO
	for ietf@ietf.org; Mon, 10 May 2004 09:36:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNAw8-0003V7-00
	for ietf@ietf.org; Mon, 10 May 2004 09:35: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 1BNAvK-00037L-00; Mon, 10 May 2004 09:34:26 -0400
Received: by newdev.harvard.edu (Postfix, from userid 501)
	id 507B51E6E7C; Mon, 10 May 2004 09:33:51 -0400 (EDT)
To: iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: 'The IESG and RFC Editor documents: Procedures' to BCP
Message-Id: <20040510133351.507B51E6E7C@newdev.harvard.edu>
Date: Mon, 10 May 2004 09:33:51 -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>


looks good to me - one suggestion of clearer language and a potential
addition

>   o  Documents for which special rules exist, including IAB documents
>      and April 1st RFCs, and republication of documents from other SDOs
>      - the IESG and the RFC Editor keep a running dialogue on which
>      documents these are

awkward wording - maybe you want to say

   o  The IESG and the RFC Editor keep a running dialogue on which
        documents require special rules (for example, IAB documents,
        April 1st RFCs, and republication of documents from other SDOs)

section 3
>    The IESG may return five different responses

this misses one of the outcomes listed in RFC 2026 - specifically (quoting
from 2026):
	"the IESG recommends that the document be brought within the
	IETF and progressed within the IETF context"

this path has been used from time to time and I think it is a valuable
option - I'd suggest that it be added as a 6th response

Scott

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



From ietf-admin@ietf.org  Mon May 10 10:59: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 KAA09495
	for <ietf-archive@ietf.org>; Mon, 10 May 2004 10:59: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 1BNCFI-0001fJ-2a
	for ietf-archive@ietf.org; Mon, 10 May 2004 10:59:08 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNCEI-0001Gi-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 10:58:06 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNCDA-0000r3-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 10:56:56 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNC1e-0004WZ-Go; Mon, 10 May 2004 10:45:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNBxf-0003xn-8z
	for ietf@optimus.ietf.org; Mon, 10 May 2004 10:40: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 KAA08686
	for <ietf@ietf.org>; Mon, 10 May 2004 10:40: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 1BNBxc-0003Jz-CV
	for ietf@ietf.org; Mon, 10 May 2004 10:40:52 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNBwo-00030G-00
	for ietf@ietf.org; Mon, 10 May 2004 10:40:02 -0400
Received: from weasel.corp.ntrg.com ([207.65.71.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNBw1-0002Yu-00
	for ietf@ietf.org; Mon, 10 May 2004 10:39:13 -0400
Received: from [207.65.71.20] (account ehall HELO ehsco.com)
  by weasel.corp.ntrg.com (CommuniGate Pro SMTP 4.1.8)
  with ESMTP-TLS id 80007; Mon, 10 May 2004 09:38:42 -0500
Message-ID: <409F93F0.5060300@ehsco.com>
Date: Mon, 10 May 2004 09:38:40 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "RL 'Bob' Morgan" <rlmorgan@washington.edu>
CC: John Rudd <john@rudd.cc>, IETF <ietf@ietf.org>
Subject: Re: Not sure if this is the right place for this
References: <DD72EEC3-A1E7-11D8-8626-003065F939FE@rudd.cc> <Pine.LNX.4.58.0405100019050.1405@perp.cac.washington.edu>
In-Reply-To: <Pine.LNX.4.58.0405100019050.1405@perp.cac.washington.edu>
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


On 5/10/2004 3:02 AM, RL 'Bob' Morgan wrote:

> So a "secure ports only" policy has very little to do with security and
> very much to do with organizational power relationships, and making
> your computing environment dysfunctional.

Somebody check my math on this please, but it seems to me that the whole
STARTTLS approach is succeptible to a specific attack which the secure
socket model is not.

Specifically, a man-in-the-middle can "blank out" the STARTTLS feature
advertisement, and thus make the client believe that TLS is not available.
For example:

      server-A                MitM                  client-C
         |      250-DSN         |     250-DSN
         +-->   250-AUTH        +->   250-AUTH
                250-STARTTLS          250 ok [...pad...]
                250 ok

The client, seeing that TLS is not available, dumbs down to cleartext.
Most clients would probably do that invisibly without even barking at the
user, or not doing so in a way that most of them would appreciate.

Using an encrypted port just means an attack can only produce failure,
rather than inducing fallback.

Unless that's wrong for some reason, I'd say that a "secure ports policy"
actually is more secure.


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


From exim@www1.ietf.org  Mon May 10 11:02:19 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09706
	for <ietf-archive@odin.ietf.org>; Mon, 10 May 2004 11:02: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 1BNCDD-0006Cx-9Z
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 10:57:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4AEuxTc023609
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 10:56:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNC1e-0004WZ-Go; Mon, 10 May 2004 10:45:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNBxf-0003xn-8z
	for ietf@optimus.ietf.org; Mon, 10 May 2004 10:40: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 KAA08686
	for <ietf@ietf.org>; Mon, 10 May 2004 10:40: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 1BNBxc-0003Jz-CV
	for ietf@ietf.org; Mon, 10 May 2004 10:40:52 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNBwo-00030G-00
	for ietf@ietf.org; Mon, 10 May 2004 10:40:02 -0400
Received: from weasel.corp.ntrg.com ([207.65.71.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNBw1-0002Yu-00
	for ietf@ietf.org; Mon, 10 May 2004 10:39:13 -0400
Received: from [207.65.71.20] (account ehall HELO ehsco.com)
  by weasel.corp.ntrg.com (CommuniGate Pro SMTP 4.1.8)
  with ESMTP-TLS id 80007; Mon, 10 May 2004 09:38:42 -0500
Message-ID: <409F93F0.5060300@ehsco.com>
Date: Mon, 10 May 2004 09:38:40 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "RL 'Bob' Morgan" <rlmorgan@washington.edu>
CC: John Rudd <john@rudd.cc>, IETF <ietf@ietf.org>
Subject: Re: Not sure if this is the right place for this
References: <DD72EEC3-A1E7-11D8-8626-003065F939FE@rudd.cc> <Pine.LNX.4.58.0405100019050.1405@perp.cac.washington.edu>
In-Reply-To: <Pine.LNX.4.58.0405100019050.1405@perp.cac.washington.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: 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 5/10/2004 3:02 AM, RL 'Bob' Morgan wrote:

> So a "secure ports only" policy has very little to do with security and
> very much to do with organizational power relationships, and making
> your computing environment dysfunctional.

Somebody check my math on this please, but it seems to me that the whole
STARTTLS approach is succeptible to a specific attack which the secure
socket model is not.

Specifically, a man-in-the-middle can "blank out" the STARTTLS feature
advertisement, and thus make the client believe that TLS is not available.
For example:

      server-A                MitM                  client-C
         |      250-DSN         |     250-DSN
         +-->   250-AUTH        +->   250-AUTH
                250-STARTTLS          250 ok [...pad...]
                250 ok

The client, seeing that TLS is not available, dumbs down to cleartext.
Most clients would probably do that invisibly without even barking at the
user, or not doing so in a way that most of them would appreciate.

Using an encrypted port just means an attack can only produce failure,
rather than inducing fallback.

Unless that's wrong for some reason, I'd say that a "secure ports policy"
actually is more secure.


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



From ietf-admin@ietf.org  Mon May 10 11:12: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 LAA10274
	for <ietf-archive@ietf.org>; Mon, 10 May 2004 11:12: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 1BNCRv-0006Gf-T3
	for ietf-archive@ietf.org; Mon, 10 May 2004 11:12:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNCR4-0005u1-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 11:11:18 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNCQD-0005WU-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 11:10:25 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNCI7-0007MO-0c; Mon, 10 May 2004 11:02:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNCCI-0005lv-Nc
	for ietf@optimus.ietf.org; Mon, 10 May 2004 10:56:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09226
	for <ietf@ietf.org>; Mon, 10 May 2004 10:55: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 1BNCCG-0000VE-55
	for ietf@ietf.org; Mon, 10 May 2004 10:56:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNCBC-0000AM-00
	for ietf@ietf.org; Mon, 10 May 2004 10:54:55 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNCAe-0007da-00; Mon, 10 May 2004 10:54:20 -0400
Received: from [127.0.0.1] (helo=localhost)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1BNCAd-000EIN-00; Mon, 10 May 2004 09:54:19 -0500
Date: Mon, 10 May 2004 10:54:16 -0400
From: John C Klensin <john-ietf@jck.com>
To: Scott Bradner <sob@harvard.edu>, iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: 'The IESG and RFC Editor documents:
 Procedures' to BCP
Message-ID: <98F68B8BD0BF769925C874EE@localhost>
In-Reply-To: <20040510133351.507B51E6E7C@newdev.harvard.edu>
References: <20040510133351.507B51E6E7C@newdev.harvard.edu>
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

--On Monday, May 10, 2004 9:33 AM -0400 Scott Bradner 
<sob@harvard.edu> wrote:

>
> looks good to me - one suggestion of clearer language and a
> potential addition
>
>>   o  Documents for which special rules exist, including IAB
>>   documents and April 1st RFCs, and republication of
>>      documents from other SDOs - the IESG and the RFC Editor
>>      keep a running dialogue on which documents these are
>
> awkward wording - maybe you want to say
>
>    o  The IESG and the RFC Editor keep a running dialogue on
> which         documents require special rules (for example,
> IAB documents,         April 1st RFCs, and republication of
> documents from other SDOs)

Scott, while I agree that the current language is not optimal, I 
don't think the above is the right fix.   The whole point of the 
agreements about publication of IAB documents is that the RFC 
Editor reports, from an overall policy and strategy standpoint, 
with the IAB.  Turning that situation into "the IESG and the RFC 
Editor keep a running dialogue" rather dramatically revises (or 
confuses) that situation.

    john

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


From exim@www1.ietf.org  Mon May 10 11:18:57 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10714
	for <ietf-archive@odin.ietf.org>; Mon, 10 May 2004 11:18: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 1BNCQF-0000sq-FF
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 11:10:31 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4AFAROh003361
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 11:10:27 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNCI7-0007MO-0c; Mon, 10 May 2004 11:02:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNCCI-0005lv-Nc
	for ietf@optimus.ietf.org; Mon, 10 May 2004 10:56:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09226
	for <ietf@ietf.org>; Mon, 10 May 2004 10:55: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 1BNCCG-0000VE-55
	for ietf@ietf.org; Mon, 10 May 2004 10:56:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNCBC-0000AM-00
	for ietf@ietf.org; Mon, 10 May 2004 10:54:55 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNCAe-0007da-00; Mon, 10 May 2004 10:54:20 -0400
Received: from [127.0.0.1] (helo=localhost)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1BNCAd-000EIN-00; Mon, 10 May 2004 09:54:19 -0500
Date: Mon, 10 May 2004 10:54:16 -0400
From: John C Klensin <john-ietf@jck.com>
To: Scott Bradner <sob@harvard.edu>, iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: 'The IESG and RFC Editor documents:
 Procedures' to BCP
Message-ID: <98F68B8BD0BF769925C874EE@localhost>
In-Reply-To: <20040510133351.507B51E6E7C@newdev.harvard.edu>
References: <20040510133351.507B51E6E7C@newdev.harvard.edu>
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

--On Monday, May 10, 2004 9:33 AM -0400 Scott Bradner 
<sob@harvard.edu> wrote:

>
> looks good to me - one suggestion of clearer language and a
> potential addition
>
>>   o  Documents for which special rules exist, including IAB
>>   documents and April 1st RFCs, and republication of
>>      documents from other SDOs - the IESG and the RFC Editor
>>      keep a running dialogue on which documents these are
>
> awkward wording - maybe you want to say
>
>    o  The IESG and the RFC Editor keep a running dialogue on
> which         documents require special rules (for example,
> IAB documents,         April 1st RFCs, and republication of
> documents from other SDOs)

Scott, while I agree that the current language is not optimal, I 
don't think the above is the right fix.   The whole point of the 
agreements about publication of IAB documents is that the RFC 
Editor reports, from an overall policy and strategy standpoint, 
with the IAB.  Turning that situation into "the IESG and the RFC 
Editor keep a running dialogue" rather dramatically revises (or 
confuses) that situation.

    john

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



From ietf-admin@ietf.org  Mon May 10 11: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 LAA11685
	for <ietf-archive@ietf.org>; Mon, 10 May 2004 11:36: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 1BNCpj-000716-Ol
	for ietf-archive@ietf.org; Mon, 10 May 2004 11:36:47 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNCom-0006hC-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 11:35:49 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNCnf-00066a-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 11:34:39 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNCgL-000405-Bw; Mon, 10 May 2004 11:27:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNCWb-0001pn-0i
	for ietf@optimus.ietf.org; Mon, 10 May 2004 11:17:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10564
	for <ietf@ietf.org>; Mon, 10 May 2004 11: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 1BNCWa-0000Bm-57
	for ietf@ietf.org; Mon, 10 May 2004 11:17:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNCVa-0007dl-00
	for ietf@ietf.org; Mon, 10 May 2004 11:15:59 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNCUm-0007Ix-00; Mon, 10 May 2004 11:15:08 -0400
Received: from [127.0.0.1] (helo=localhost)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1BNCUl-000F5T-00; Mon, 10 May 2004 10:15:08 -0500
Date: Mon, 10 May 2004 11:15:04 -0400
From: John C Klensin <john-ietf@jck.com>
To: Scott Bradner <sob@harvard.edu>
cc: iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: 'The IESG and RFC Editor documents:
 Procedures' to BCP
Message-ID: <BF2B12C1D4CD31C19AFB69C9@localhost>
In-Reply-To: <20040510145755.A8B251E71F4@newdev.harvard.edu>
References: <20040510145755.A8B251E71F4@newdev.harvard.edu>
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



--On Monday, May 10, 2004 10:57 AM -0400 Scott Bradner 
<sob@harvard.edu> wrote:

> note that I just used the words that were there - do you
> suggest  leaving teh words as they are?  if not, maybe you can
> suggest something better

I guess that, before, the text was sufficiently muddy that I 
didn't catch the real problem, so thanks for trying to clarify 
it :-(.

Perhaps it should say something like...

	  o  Special rules exist for some documents, including
	IAB
	documents and April 1st RFCs, and republication of
	documents from other SDOs.  In some cases, these rules
	exist because the RFC Editor reports to the IAB on
	policy and strategy matters.  The IESG and the RFC
	Editor keep a running dialogue, in consultation with the
	IAB, on other documents and classification of them.

I think that represents the current situation and agreements, 
and assume that the other text was just confusing.   As you 
know, quite a lot of anguish has gone into this topic area in 
the past. It would be, IMO, a mistake to even reopen the issue 
unless there is compelling need to do so.

     john


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


From ietf-admin@ietf.org  Mon May 10 11:40: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 LAA11893
	for <ietf-archive@ietf.org>; Mon, 10 May 2004 11:40: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 1BNCtg-0000YZ-9O
	for ietf-archive@ietf.org; Mon, 10 May 2004 11:40:52 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNCsh-0000DV-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 11:39:52 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNCrh-0007fd-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 11:38:49 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNChI-0004Lq-NH; Mon, 10 May 2004 11:28:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNCZR-0002RK-Lo
	for ietf@optimus.ietf.org; Mon, 10 May 2004 11:19:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10807
	for <ietf@ietf.org>; Mon, 10 May 2004 11:19: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 1BNCZQ-0001FV-PE
	for ietf@ietf.org; Mon, 10 May 2004 11:19:56 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNCYY-0000uX-00
	for ietf@ietf.org; Mon, 10 May 2004 11:19:02 -0400
Received: from newdev.eecs.harvard.edu ([140.247.60.212] helo=newdev.harvard.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNCXd-0000Dd-00; Mon, 10 May 2004 11:18:05 -0400
Received: by newdev.harvard.edu (Postfix, from userid 501)
	id 5CF621E72C5; Mon, 10 May 2004 11:17:30 -0400 (EDT)
To: john-ietf@jck.com, sob@harvard.edu
Subject: Re: Last Call: 'The IESG and RFC Editor documents: Procedures' to BCP
Cc: iesg@ietf.org, ietf@ietf.org
In-Reply-To: <BF2B12C1D4CD31C19AFB69C9@localhost>
Message-Id: <20040510151730.5CF621E72C5@newdev.harvard.edu>
Date: Mon, 10 May 2004 11:17:30 -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

fwiw - this works for me

---
From: John C Klensin <john-ietf@jck.com>
To: Scott Bradner <sob@harvard.edu>
Cc: iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: 'The IESG and RFC Editor documents:
 Procedures' to BCP

--On Monday, May 10, 2004 10:57 AM -0400 Scott Bradner 
<sob@harvard.edu> wrote:

> note that I just used the words that were there - do you
> suggest  leaving teh words as they are?  if not, maybe you can
> suggest something better

I guess that, before, the text was sufficiently muddy that I 
didn't catch the real problem, so thanks for trying to clarify 
it :-(.

Perhaps it should say something like...

	  o  Special rules exist for some documents, including
	IAB
	documents and April 1st RFCs, and republication of
	documents from other SDOs.  In some cases, these rules
	exist because the RFC Editor reports to the IAB on
	policy and strategy matters.  The IESG and the RFC
	Editor keep a running dialogue, in consultation with the
	IAB, on other documents and classification of them.

I think that represents the current situation and agreements, 
and assume that the other text was just confusing.   As you 
know, quite a lot of anguish has gone into this topic area in 
the past. It would be, IMO, a mistake to even reopen the issue 
unless there is compelling need to do so.

     john


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


From exim@www1.ietf.org  Mon May 10 11:47:17 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12224
	for <ietf-archive@odin.ietf.org>; Mon, 10 May 2004 11:47: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 1BNCnh-0005bo-1I
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 11:34:41 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4AFYeLP021305
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 11:34:40 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNCgL-000405-Bw; Mon, 10 May 2004 11:27:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNCWb-0001pn-0i
	for ietf@optimus.ietf.org; Mon, 10 May 2004 11:17:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10564
	for <ietf@ietf.org>; Mon, 10 May 2004 11: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 1BNCWa-0000Bm-57
	for ietf@ietf.org; Mon, 10 May 2004 11:17:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNCVa-0007dl-00
	for ietf@ietf.org; Mon, 10 May 2004 11:15:59 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNCUm-0007Ix-00; Mon, 10 May 2004 11:15:08 -0400
Received: from [127.0.0.1] (helo=localhost)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1BNCUl-000F5T-00; Mon, 10 May 2004 10:15:08 -0500
Date: Mon, 10 May 2004 11:15:04 -0400
From: John C Klensin <john-ietf@jck.com>
To: Scott Bradner <sob@harvard.edu>
cc: iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: 'The IESG and RFC Editor documents:
 Procedures' to BCP
Message-ID: <BF2B12C1D4CD31C19AFB69C9@localhost>
In-Reply-To: <20040510145755.A8B251E71F4@newdev.harvard.edu>
References: <20040510145755.A8B251E71F4@newdev.harvard.edu>
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



--On Monday, May 10, 2004 10:57 AM -0400 Scott Bradner 
<sob@harvard.edu> wrote:

> note that I just used the words that were there - do you
> suggest  leaving teh words as they are?  if not, maybe you can
> suggest something better

I guess that, before, the text was sufficiently muddy that I 
didn't catch the real problem, so thanks for trying to clarify 
it :-(.

Perhaps it should say something like...

	  o  Special rules exist for some documents, including
	IAB
	documents and April 1st RFCs, and republication of
	documents from other SDOs.  In some cases, these rules
	exist because the RFC Editor reports to the IAB on
	policy and strategy matters.  The IESG and the RFC
	Editor keep a running dialogue, in consultation with the
	IAB, on other documents and classification of them.

I think that represents the current situation and agreements, 
and assume that the other text was just confusing.   As you 
know, quite a lot of anguish has gone into this topic area in 
the past. It would be, IMO, a mistake to even reopen the issue 
unless there is compelling need to do so.

     john


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



From exim@www1.ietf.org  Mon May 10 11:53:38 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 LAA12461
	for <ietf-archive@odin.ietf.org>; Mon, 10 May 2004 11:53:38 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNCri-0006n1-4J
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 11:38:50 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4AFcojl025994
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 11:38:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNChI-0004Lq-NH; Mon, 10 May 2004 11:28:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNCZR-0002RK-Lo
	for ietf@optimus.ietf.org; Mon, 10 May 2004 11:19:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10807
	for <ietf@ietf.org>; Mon, 10 May 2004 11:19: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 1BNCZQ-0001FV-PE
	for ietf@ietf.org; Mon, 10 May 2004 11:19:56 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNCYY-0000uX-00
	for ietf@ietf.org; Mon, 10 May 2004 11:19:02 -0400
Received: from newdev.eecs.harvard.edu ([140.247.60.212] helo=newdev.harvard.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNCXd-0000Dd-00; Mon, 10 May 2004 11:18:05 -0400
Received: by newdev.harvard.edu (Postfix, from userid 501)
	id 5CF621E72C5; Mon, 10 May 2004 11:17:30 -0400 (EDT)
To: john-ietf@jck.com, sob@harvard.edu
Subject: Re: Last Call: 'The IESG and RFC Editor documents: Procedures' to BCP
Cc: iesg@ietf.org, ietf@ietf.org
In-Reply-To: <BF2B12C1D4CD31C19AFB69C9@localhost>
Message-Id: <20040510151730.5CF621E72C5@newdev.harvard.edu>
Date: Mon, 10 May 2004 11:17:30 -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>

fwiw - this works for me

---
From: John C Klensin <john-ietf@jck.com>
To: Scott Bradner <sob@harvard.edu>
Cc: iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: 'The IESG and RFC Editor documents:
 Procedures' to BCP

--On Monday, May 10, 2004 10:57 AM -0400 Scott Bradner 
<sob@harvard.edu> wrote:

> note that I just used the words that were there - do you
> suggest  leaving teh words as they are?  if not, maybe you can
> suggest something better

I guess that, before, the text was sufficiently muddy that I 
didn't catch the real problem, so thanks for trying to clarify 
it :-(.

Perhaps it should say something like...

	  o  Special rules exist for some documents, including
	IAB
	documents and April 1st RFCs, and republication of
	documents from other SDOs.  In some cases, these rules
	exist because the RFC Editor reports to the IAB on
	policy and strategy matters.  The IESG and the RFC
	Editor keep a running dialogue, in consultation with the
	IAB, on other documents and classification of them.

I think that represents the current situation and agreements, 
and assume that the other text was just confusing.   As you 
know, quite a lot of anguish has gone into this topic area in 
the past. It would be, IMO, a mistake to even reopen the issue 
unless there is compelling need to do so.

     john


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



From ietf-admin@ietf.org  Mon May 10 11:58: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 LAA12739
	for <ietf-archive@ietf.org>; Mon, 10 May 2004 11:58: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 1BNDAS-00064Z-RI
	for ietf-archive@ietf.org; Mon, 10 May 2004 11:58:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BND9Z-0005ib-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 11:57:17 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BND8e-0005Ne-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 11:56:20 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNCze-0008Nb-Fc; Mon, 10 May 2004 11: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 1BNCiP-0004ds-FE
	for ietf@optimus.ietf.org; Mon, 10 May 2004 11:29:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11250
	for <ietf@ietf.org>; Mon, 10 May 2004 11:29: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 1BNCiO-0004JI-G0
	for ietf@ietf.org; Mon, 10 May 2004 11:29:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNChH-0003wk-00
	for ietf@ietf.org; Mon, 10 May 2004 11:28:04 -0400
Received: from 216-43-25-66.ip.mcleodusa.net ([216.43.25.66] helo=episteme-software.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNCgn-0003ax-00; Mon, 10 May 2004 11:27:33 -0400
Received: from [216.43.25.67] (216.43.25.67) by episteme-software.com with
 ESMTP (Eudora Internet Mail Server X 3.2.4);
 Mon, 10 May 2004 10:27:02 -0500
Mime-Version: 1.0
X-Sender: resnick@resnick1.qualcomm.com (Unverified)
Message-Id: <p0610110dbcc54d6b507d@[216.43.25.67]>
In-Reply-To: <98F68B8BD0BF769925C874EE@localhost>
References: <20040510133351.507B51E6E7C@newdev.harvard.edu>
 <98F68B8BD0BF769925C874EE@localhost>
X-Mailer: Eudora [Macintosh version 6.1a16]
Date: Mon, 10 May 2004 10:27:00 -0500
To: John C Klensin <john-ietf@jck.com>
From: Pete Resnick <presnick@qualcomm.com>
Subject: Re: Last Call: 'The IESG and RFC Editor documents:  Procedures'
 to BCP
Cc: Scott Bradner <sob@harvard.edu>, iesg@ietf.org, ietf@ietf.org
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=1.9 required=5.0 tests=AWL,FORGED_MUA_EUDORA 
	autolearn=no version=2.60

On 5/10/04 at 10:54 AM -0400, John C Klensin wrote:

>--On Monday, May 10, 2004 9:33 AM -0400 Scott Bradner <sob@harvard.edu> wrote:
>
>>looks good to me - one suggestion of clearer language and a
>>potential addition
>>
>>>   o  Documents for which special rules exist, including IAB 
>>>documents and April 1st RFCs, and republication of documents from 
>>>other SDOs - the IESG and the RFC Editor keep a running dialogue 
>>>on which documents these are
>>
>>awkward wording - maybe you want to say
>>
>>    o  The IESG and the RFC Editor keep a running dialogue on which 
>>documents require special rules (for example, IAB documents, April 
>>1st RFCs, and republication of documents from other SDOs)
>
>Scott, while I agree that the current language is not optimal, I 
>don't think the above is the right fix.   The whole point of the 
>agreements about publication of IAB documents is that the RFC Editor 
>reports, from an overall policy and strategy standpoint, with the 
>IAB.  Turning that situation into "the IESG and the RFC Editor keep 
>a running dialogue" rather dramatically revises (or confuses) that 
>situation.

John, the paragraph which Scott aims to fix is in the section which 
describes "what is currently happening". And, indeed, I believe it is 
true that the current state of affairs is that the IESG and the RFC 
Editor *do* keep a running dialogue about out-of-the-ordinary 
documents which may or may not need IESG review (where republication 
of certain SDO documents do -- because of liaison agreements -- and 
April 1st RFCs do not, as far as I know).

Perhaps this would be better stated as:

o  The IESG and the RFC Editor keep a running dialogue on which 
documents require special rules (for example, IAB informational 
documents and April 1st RFCs never require IESG review, whereas 
certain republication of documents from other SDOs do because of 
liaison agreements)

(assuming that captures what Harald, and Scott, intended in their attempts).
-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
QUALCOMM Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102

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


From ietf-admin@ietf.org  Mon May 10 12:00: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 MAA12932
	for <ietf-archive@ietf.org>; Mon, 10 May 2004 12: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 1BNDCX-0006ot-Do
	for ietf-archive@ietf.org; Mon, 10 May 2004 12:00:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNDBi-0006Sj-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 11:59:31 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNDAT-00064g-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 11:58:13 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNCzm-0008R6-B7; Mon, 10 May 2004 11:47:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNCmJ-0005IU-MO
	for ietf@optimus.ietf.org; Mon, 10 May 2004 11:33:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11522
	for <ietf@ietf.org>; Mon, 10 May 2004 11:33: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 1BNCmI-0005lW-De
	for ietf@ietf.org; Mon, 10 May 2004 11:33:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNClO-0005QB-00
	for ietf@ietf.org; Mon, 10 May 2004 11:32:19 -0400
Received: from above.proper.com ([208.184.76.39])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNCkh-00053z-00
	for ietf@ietf.org; Mon, 10 May 2004 11:31:35 -0400
Received: from [10.20.30.249] (dsl2-63-249-109-252.cruzio.com [63.249.109.252])
	(authenticated bits=0)
	by above.proper.com (8.12.11/8.12.9) with ESMTP id i4AFVSqP089299;
	Mon, 10 May 2004 08:31:28 -0700 (PDT)
	(envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
X-Sender: phoffvpnc@mail.vpnc.org
Message-Id: <p06100532bcc54f129dec@[10.20.30.249]>
In-Reply-To: <409F93F0.5060300@ehsco.com>
References: <DD72EEC3-A1E7-11D8-8626-003065F939FE@rudd.cc>
 <Pine.LNX.4.58.0405100019050.1405@perp.cac.washington.edu>
 <409F93F0.5060300@ehsco.com>
Date: Mon, 10 May 2004 08:31:29 -0700
To: "Eric A. Hall" <ehall@ehsco.com>,
        "RL 'Bob' Morgan" <rlmorgan@washington.edu>
From: Paul Hoffman / VPNC <paul.hoffman@vpnc.org>
Subject: Re: Not sure if this is the right place for this
Cc: John Rudd <john@rudd.cc>, IETF <ietf@ietf.org>
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.1 required=5.0 tests=AWL autolearn=no version=2.60

At 9:38 AM -0500 5/10/04, Eric A. Hall wrote:
>On 5/10/2004 3:02 AM, RL 'Bob' Morgan wrote:
>
>>  So a "secure ports only" policy has very little to do with security and
>>  very much to do with organizational power relationships, and making
>>  your computing environment dysfunctional.
>
>Somebody check my math on this please, but it seems to me that the whole
>STARTTLS approach is succeptible to a specific attack which the secure
>socket model is not.
>
>Specifically, a man-in-the-middle can "blank out" the STARTTLS feature
>advertisement, and thus make the client believe that TLS is not available.
>For example:
>
>       server-A                MitM                  client-C
>          |      250-DSN         |     250-DSN
>          +-->   250-AUTH        +->   250-AUTH
>                 250-STARTTLS          250 ok [...pad...]
>                 250 ok
>
>The client, seeing that TLS is not available, dumbs down to cleartext.
>Most clients would probably do that invisibly without even barking at the
>user, or not doing so in a way that most of them would appreciate.
>
>Using an encrypted port just means an attack can only produce failure,
>rather than inducing fallback.
>
>Unless that's wrong for some reason, I'd say that a "secure ports policy"
>actually is more secure.

In many cases, a client for a "secure ports policy" protocol will 
fall back to the insecure port instead of telling the user "you can't 
communicate". That's not true for HTTPS, but it is true for secure 
POP, secure SMTP, and so on.

A man-in-the-middle can more easily block the secure port than he/she 
can elide the STARTTLS messing in the client's start-up. STARTTLS is 
harder to mount than blocking a "secure port". Thus, the "secure 
ports policy" makes the MITM's job easier.

BTW, sometimes the MITM in the "secure ports only" scenario is a 
clueless firewall admin at any point in the transit. The STARTTLS 
method is not susceptible to this unintentional-but-still-deadly 
downgrade attack.

Any client that is willing to back down to non-secure mode is 
susceptible to a MITM attack, regardless of the protocol.

--Paul Hoffman, Director
--VPN Consortium

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


From exim@www1.ietf.org  Mon May 10 12:11:27 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 MAA13903
	for <ietf-archive@odin.ietf.org>; Mon, 10 May 2004 12:11:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BND8f-0001Wl-8W
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 11:56:21 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4AFuLna005872
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 11:56:21 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNCze-0008Nb-Fc; Mon, 10 May 2004 11: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 1BNCiP-0004ds-FE
	for ietf@optimus.ietf.org; Mon, 10 May 2004 11:29:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11250
	for <ietf@ietf.org>; Mon, 10 May 2004 11:29: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 1BNCiO-0004JI-G0
	for ietf@ietf.org; Mon, 10 May 2004 11:29:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNChH-0003wk-00
	for ietf@ietf.org; Mon, 10 May 2004 11:28:04 -0400
Received: from 216-43-25-66.ip.mcleodusa.net ([216.43.25.66] helo=episteme-software.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNCgn-0003ax-00; Mon, 10 May 2004 11:27:33 -0400
Received: from [216.43.25.67] (216.43.25.67) by episteme-software.com with
 ESMTP (Eudora Internet Mail Server X 3.2.4);
 Mon, 10 May 2004 10:27:02 -0500
Mime-Version: 1.0
X-Sender: resnick@resnick1.qualcomm.com (Unverified)
Message-Id: <p0610110dbcc54d6b507d@[216.43.25.67]>
In-Reply-To: <98F68B8BD0BF769925C874EE@localhost>
References: <20040510133351.507B51E6E7C@newdev.harvard.edu>
 <98F68B8BD0BF769925C874EE@localhost>
X-Mailer: Eudora [Macintosh version 6.1a16]
Date: Mon, 10 May 2004 10:27:00 -0500
To: John C Klensin <john-ietf@jck.com>
From: Pete Resnick <presnick@qualcomm.com>
Subject: Re: Last Call: 'The IESG and RFC Editor documents:  Procedures'
 to BCP
Cc: Scott Bradner <sob@harvard.edu>, iesg@ietf.org, ietf@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=1.9 required=5.0 tests=AWL,FORGED_MUA_EUDORA 
	autolearn=no version=2.60
Sender: 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 5/10/04 at 10:54 AM -0400, John C Klensin wrote:

>--On Monday, May 10, 2004 9:33 AM -0400 Scott Bradner <sob@harvard.edu> wrote:
>
>>looks good to me - one suggestion of clearer language and a
>>potential addition
>>
>>>   o  Documents for which special rules exist, including IAB 
>>>documents and April 1st RFCs, and republication of documents from 
>>>other SDOs - the IESG and the RFC Editor keep a running dialogue 
>>>on which documents these are
>>
>>awkward wording - maybe you want to say
>>
>>    o  The IESG and the RFC Editor keep a running dialogue on which 
>>documents require special rules (for example, IAB documents, April 
>>1st RFCs, and republication of documents from other SDOs)
>
>Scott, while I agree that the current language is not optimal, I 
>don't think the above is the right fix.   The whole point of the 
>agreements about publication of IAB documents is that the RFC Editor 
>reports, from an overall policy and strategy standpoint, with the 
>IAB.  Turning that situation into "the IESG and the RFC Editor keep 
>a running dialogue" rather dramatically revises (or confuses) that 
>situation.

John, the paragraph which Scott aims to fix is in the section which 
describes "what is currently happening". And, indeed, I believe it is 
true that the current state of affairs is that the IESG and the RFC 
Editor *do* keep a running dialogue about out-of-the-ordinary 
documents which may or may not need IESG review (where republication 
of certain SDO documents do -- because of liaison agreements -- and 
April 1st RFCs do not, as far as I know).

Perhaps this would be better stated as:

o  The IESG and the RFC Editor keep a running dialogue on which 
documents require special rules (for example, IAB informational 
documents and April 1st RFCs never require IESG review, whereas 
certain republication of documents from other SDOs do because of 
liaison agreements)

(assuming that captures what Harald, and Scott, intended in their attempts).
-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
QUALCOMM Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102

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



From exim@www1.ietf.org  Mon May 10 12:11: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 MAA13921
	for <ietf-archive@odin.ietf.org>; Mon, 10 May 2004 12:11:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNDAT-0002Rs-Dq
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 11:58:14 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4AFwDPC009406
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 11:58:13 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNCzm-0008R6-B7; Mon, 10 May 2004 11:47:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNCmJ-0005IU-MO
	for ietf@optimus.ietf.org; Mon, 10 May 2004 11:33:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11522
	for <ietf@ietf.org>; Mon, 10 May 2004 11:33: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 1BNCmI-0005lW-De
	for ietf@ietf.org; Mon, 10 May 2004 11:33:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNClO-0005QB-00
	for ietf@ietf.org; Mon, 10 May 2004 11:32:19 -0400
Received: from above.proper.com ([208.184.76.39])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNCkh-00053z-00
	for ietf@ietf.org; Mon, 10 May 2004 11:31:35 -0400
Received: from [10.20.30.249] (dsl2-63-249-109-252.cruzio.com [63.249.109.252])
	(authenticated bits=0)
	by above.proper.com (8.12.11/8.12.9) with ESMTP id i4AFVSqP089299;
	Mon, 10 May 2004 08:31:28 -0700 (PDT)
	(envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
X-Sender: phoffvpnc@mail.vpnc.org
Message-Id: <p06100532bcc54f129dec@[10.20.30.249]>
In-Reply-To: <409F93F0.5060300@ehsco.com>
References: <DD72EEC3-A1E7-11D8-8626-003065F939FE@rudd.cc>
 <Pine.LNX.4.58.0405100019050.1405@perp.cac.washington.edu>
 <409F93F0.5060300@ehsco.com>
Date: Mon, 10 May 2004 08:31:29 -0700
To: "Eric A. Hall" <ehall@ehsco.com>,
        "RL 'Bob' Morgan" <rlmorgan@washington.edu>
From: Paul Hoffman / VPNC <paul.hoffman@vpnc.org>
Subject: Re: Not sure if this is the right place for this
Cc: John Rudd <john@rudd.cc>, IETF <ietf@ietf.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 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 9:38 AM -0500 5/10/04, Eric A. Hall wrote:
>On 5/10/2004 3:02 AM, RL 'Bob' Morgan wrote:
>
>>  So a "secure ports only" policy has very little to do with security and
>>  very much to do with organizational power relationships, and making
>>  your computing environment dysfunctional.
>
>Somebody check my math on this please, but it seems to me that the whole
>STARTTLS approach is succeptible to a specific attack which the secure
>socket model is not.
>
>Specifically, a man-in-the-middle can "blank out" the STARTTLS feature
>advertisement, and thus make the client believe that TLS is not available.
>For example:
>
>       server-A                MitM                  client-C
>          |      250-DSN         |     250-DSN
>          +-->   250-AUTH        +->   250-AUTH
>                 250-STARTTLS          250 ok [...pad...]
>                 250 ok
>
>The client, seeing that TLS is not available, dumbs down to cleartext.
>Most clients would probably do that invisibly without even barking at the
>user, or not doing so in a way that most of them would appreciate.
>
>Using an encrypted port just means an attack can only produce failure,
>rather than inducing fallback.
>
>Unless that's wrong for some reason, I'd say that a "secure ports policy"
>actually is more secure.

In many cases, a client for a "secure ports policy" protocol will 
fall back to the insecure port instead of telling the user "you can't 
communicate". That's not true for HTTPS, but it is true for secure 
POP, secure SMTP, and so on.

A man-in-the-middle can more easily block the secure port than he/she 
can elide the STARTTLS messing in the client's start-up. STARTTLS is 
harder to mount than blocking a "secure port". Thus, the "secure 
ports policy" makes the MITM's job easier.

BTW, sometimes the MITM in the "secure ports only" scenario is a 
clueless firewall admin at any point in the transit. The STARTTLS 
method is not susceptible to this unintentional-but-still-deadly 
downgrade attack.

Any client that is willing to back down to non-secure mode is 
susceptible to a MITM attack, regardless of the protocol.

--Paul Hoffman, Director
--VPN Consortium

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



From ietf-admin@ietf.org  Mon May 10 12:43: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 MAA16245
	for <ietf-archive@ietf.org>; Mon, 10 May 2004 12:43: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 1BNDrv-0006t1-7p
	for ietf-archive@ietf.org; Mon, 10 May 2004 12:43:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNDr2-0006Yn-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 12:42:13 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNDqS-0006DK-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 12:41:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNDkA-0001SY-E9; Mon, 10 May 2004 12:35:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNDbm-0000GI-FL
	for ietf@optimus.ietf.org; Mon, 10 May 2004 12:26:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14932
	for <ietf@ietf.org>; Mon, 10 May 2004 12:26: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 1BNDbk-0000fJ-So
	for ietf@ietf.org; Mon, 10 May 2004 12:26:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNDap-0000Gy-00
	for ietf@ietf.org; Mon, 10 May 2004 12:25:28 -0400
Received: from carwash.centive.com ([65.220.90.249])
	by ietf-mx with smtp (Exim 4.12)
	id 1BNDZw-0007bQ-00
	for ietf@ietf.org; Mon, 10 May 2004 12:24:32 -0400
Received: from minglewood.incentivesystems.com ([10.10.30.25])
 by carwash.centive.com (SAVSMTP 3.1.3.37) with SMTP id M2004051012243503349
 ; Mon, 10 May 2004 12:24:35 -0400
Received: from [10.10.48.119] ([10.10.48.119]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Mon, 10 May 2004 12:19:39 -0400
Message-ID: <409FAB9B.20000@centive.com>
Date: Mon, 10 May 2004 12:19:39 -0400
From: John Stracke <jstracke@centive.com>
User-Agent: Mozilla Thunderbird 0.6 (Windows/20040502)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: John Rudd <john@rudd.cc>
CC: ietf@ietf.org
Subject: Re: Not sure if this is the right place for this
References: <DD72EEC3-A1E7-11D8-8626-003065F939FE@rudd.cc>
In-Reply-To: <DD72EEC3-A1E7-11D8-8626-003065F939FE@rudd.cc>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 10 May 2004 16:19:39.0706 (UTC) FILETIME=[9814D9A0:01C436AA]
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

John Rudd wrote:

> The problem with the STARTTLS strategy is: you can't guarantee at the 
> network level that a client will use SSL/TLS.

Guaranteeing that the client will use TLS is worthless anyway, since TLS 
includes the "None" encryption option.

-- 
/==========================================\
|John Stracke      |jstracke@centive.com   |
|Principal Engineer|http://www.centive.com |
|Centive           |My opinions are my own.|
|==========================================|
|Guide us, oh holy Lemming Herder!         |
\==========================================/


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


From exim@www1.ietf.org  Mon May 10 12:52: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 MAA16733
	for <ietf-archive@odin.ietf.org>; Mon, 10 May 2004 12:52: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 1BNDqU-00035e-IH
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 12:41:41 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4AGfcA0011621
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 12:41:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNDkA-0001SY-E9; Mon, 10 May 2004 12:35:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNDbm-0000GI-FL
	for ietf@optimus.ietf.org; Mon, 10 May 2004 12:26:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14932
	for <ietf@ietf.org>; Mon, 10 May 2004 12:26: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 1BNDbk-0000fJ-So
	for ietf@ietf.org; Mon, 10 May 2004 12:26:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNDap-0000Gy-00
	for ietf@ietf.org; Mon, 10 May 2004 12:25:28 -0400
Received: from carwash.centive.com ([65.220.90.249])
	by ietf-mx with smtp (Exim 4.12)
	id 1BNDZw-0007bQ-00
	for ietf@ietf.org; Mon, 10 May 2004 12:24:32 -0400
Received: from minglewood.incentivesystems.com ([10.10.30.25])
 by carwash.centive.com (SAVSMTP 3.1.3.37) with SMTP id M2004051012243503349
 ; Mon, 10 May 2004 12:24:35 -0400
Received: from [10.10.48.119] ([10.10.48.119]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Mon, 10 May 2004 12:19:39 -0400
Message-ID: <409FAB9B.20000@centive.com>
Date: Mon, 10 May 2004 12:19:39 -0400
From: John Stracke <jstracke@centive.com>
User-Agent: Mozilla Thunderbird 0.6 (Windows/20040502)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: John Rudd <john@rudd.cc>
CC: ietf@ietf.org
Subject: Re: Not sure if this is the right place for this
References: <DD72EEC3-A1E7-11D8-8626-003065F939FE@rudd.cc>
In-Reply-To: <DD72EEC3-A1E7-11D8-8626-003065F939FE@rudd.cc>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 10 May 2004 16:19:39.0706 (UTC) FILETIME=[9814D9A0:01C436AA]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-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

John Rudd wrote:

> The problem with the STARTTLS strategy is: you can't guarantee at the 
> network level that a client will use SSL/TLS.

Guaranteeing that the client will use TLS is worthless anyway, since TLS 
includes the "None" encryption option.

-- 
/==========================================\
|John Stracke      |jstracke@centive.com   |
|Principal Engineer|http://www.centive.com |
|Centive           |My opinions are my own.|
|==========================================|
|Guide us, oh holy Lemming Herder!         |
\==========================================/


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



From ietf-admin@ietf.org  Mon May 10 14:08: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 OAA20716
	for <ietf-archive@ietf.org>; Mon, 10 May 2004 14:08: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 1BNFCz-0004tD-7i
	for ietf-archive@ietf.org; Mon, 10 May 2004 14:08:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNFBy-0004X1-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 14:07:55 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNFB5-0004Cd-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 14:06:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNF3Q-0007kz-9g; Mon, 10 May 2004 13:59:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNF0l-0006jg-RH
	for ietf@optimus.ietf.org; Mon, 10 May 2004 13:56:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20083
	for <ietf@ietf.org>; Mon, 10 May 2004 13:56: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 1BNF0j-0000aA-5i
	for ietf@ietf.org; Mon, 10 May 2004 13:56:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNEzp-0000Ei-00
	for ietf@ietf.org; Mon, 10 May 2004 13:55:22 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNEyt-0007Tm-00
	for ietf@ietf.org; Mon, 10 May 2004 13:54:23 -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 i4AHrgXe025751
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 10 May 2004 13:53:46 -0400
Date: Mon, 10 May 2004 13:53:42 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
cc: Rajat <myself_rajat@yahoo.com>, <ietf@ietf.org>
Subject: Re: Problem of blocking ICMP packets
In-Reply-To: <409EE11F.9070601@necom830.hpcl.titech.ac.jp>
Message-ID: <Pine.LNX.4.44.0405101318260.25030-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, 10 May 2004, Masataka Ohta wrote:

> Dean Anderson;
> 
> >>I recommend that, to avoid long initial delay and intermediate
> >>lack of communication after path changes of, PMTUD should turnd
> >>off by default and should be activated only on extreme
> >>conditions.
> 
> > Just the opposite, unless you want to lose connectivity with a number of 
> > web servers that want to send big packets with DF turned on.
> 
> There were (still are?) number of web servers that wanted to send
> big packets with DF turned on, because PMTUD was turned on on the
> servers but ICMP errors were filtered.

There still are such apps.  I ran into this recently, last winter.

I'd suggest those complaining should get a few more clues about what ICMP
does, and stop filtering ICMP packets that aren't threatening.  The
network can't possibly work if people are going to turn critical parts of
it off, parts that they don't fully understand.  There is no surprise that
they have problems. This isn't a reason to change the network. There are
other things that they don't understand, and could turn off.  One can't
remove all switches and levers.

> > A number of commercial
> > products and applications do rely on PMTU to work, and will do an PATH MTU 
> > discovery, and send the MTU sized packets with DF (don't frag).
> 
> and send packets larger than MTU expecting to receive ICMP
> errors in vain.
> 
> Read the original mail of the thread on the reality.

I think we disagree on the "reality". The reality is that most sensible
people and ISPs don't block harmless ICMP messages. Of course, not _all_
ICMP messages from anywhere are harmless, but that doesn't mean that all
such messages are all harmful.  Blocking everything is a club-footed
method of security, if you'll pardon the pun.

Those that pick such an approach cannot be accomodated, because they're
clubfooted, as it were---if it isn't this, its something else.  
Cluelessly turning things off will have a bad effect on any system. Case
in point: It seems that something similar (in principle anyway) was what
caused the Three Mile Island Nuclear Plant to melt down: The operators
turned off the emergency cooling system pumps wrongly. It took an engineer
to tell them to turn them back on, but by then it was too late to prevent
damage.  People have suggested that the switch to turn off the pumps
should be removed from all nuclear plants. This is also wrong. There might
be a need to do that someday.

The solution is to better train the operators, so that they don't mess
with things they don't fully understand.  This is just as true of
networks, as it is of nuclear power plants. Probably more so of networks,
since these sorts of things happen more frequently, and even the network
engineers aren't nearly as uniformly trained, much less so the operators.

> > This is the first I have heard that path mtu discovery software was
> > unreliable.
> 
> PMTUD software is unreliable!?
> 
> Then, it is anther reason to avoid it.
> 
> Can you tell me who said it with an appropriate reference?

Err, _you_ said it:

On Sat, 8 May 2004, Masataka Ohta wrote:
> Further, it should be noted that PMTUD is so unreliable that
> no applications rely on it, which means that even under
> extreme conditions rational operators won't turn on PMTUD.
>
> In short, forget PMTUD.
>                                               Masataka Ohta
>
>




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


From exim@www1.ietf.org  Mon May 10 14:12: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 OAA20966
	for <ietf-archive@odin.ietf.org>; Mon, 10 May 2004 14:12: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 1BNFB7-0001AM-5S
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 14:07:01 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4AI71FY004468
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 14:07:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNF3Q-0007kz-9g; Mon, 10 May 2004 13:59:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNF0l-0006jg-RH
	for ietf@optimus.ietf.org; Mon, 10 May 2004 13:56:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20083
	for <ietf@ietf.org>; Mon, 10 May 2004 13:56: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 1BNF0j-0000aA-5i
	for ietf@ietf.org; Mon, 10 May 2004 13:56:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNEzp-0000Ei-00
	for ietf@ietf.org; Mon, 10 May 2004 13:55:22 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNEyt-0007Tm-00
	for ietf@ietf.org; Mon, 10 May 2004 13:54:23 -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 i4AHrgXe025751
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 10 May 2004 13:53:46 -0400
Date: Mon, 10 May 2004 13:53:42 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
cc: Rajat <myself_rajat@yahoo.com>, <ietf@ietf.org>
Subject: Re: Problem of blocking ICMP packets
In-Reply-To: <409EE11F.9070601@necom830.hpcl.titech.ac.jp>
Message-ID: <Pine.LNX.4.44.0405101318260.25030-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, 10 May 2004, Masataka Ohta wrote:

> Dean Anderson;
> 
> >>I recommend that, to avoid long initial delay and intermediate
> >>lack of communication after path changes of, PMTUD should turnd
> >>off by default and should be activated only on extreme
> >>conditions.
> 
> > Just the opposite, unless you want to lose connectivity with a number of 
> > web servers that want to send big packets with DF turned on.
> 
> There were (still are?) number of web servers that wanted to send
> big packets with DF turned on, because PMTUD was turned on on the
> servers but ICMP errors were filtered.

There still are such apps.  I ran into this recently, last winter.

I'd suggest those complaining should get a few more clues about what ICMP
does, and stop filtering ICMP packets that aren't threatening.  The
network can't possibly work if people are going to turn critical parts of
it off, parts that they don't fully understand.  There is no surprise that
they have problems. This isn't a reason to change the network. There are
other things that they don't understand, and could turn off.  One can't
remove all switches and levers.

> > A number of commercial
> > products and applications do rely on PMTU to work, and will do an PATH MTU 
> > discovery, and send the MTU sized packets with DF (don't frag).
> 
> and send packets larger than MTU expecting to receive ICMP
> errors in vain.
> 
> Read the original mail of the thread on the reality.

I think we disagree on the "reality". The reality is that most sensible
people and ISPs don't block harmless ICMP messages. Of course, not _all_
ICMP messages from anywhere are harmless, but that doesn't mean that all
such messages are all harmful.  Blocking everything is a club-footed
method of security, if you'll pardon the pun.

Those that pick such an approach cannot be accomodated, because they're
clubfooted, as it were---if it isn't this, its something else.  
Cluelessly turning things off will have a bad effect on any system. Case
in point: It seems that something similar (in principle anyway) was what
caused the Three Mile Island Nuclear Plant to melt down: The operators
turned off the emergency cooling system pumps wrongly. It took an engineer
to tell them to turn them back on, but by then it was too late to prevent
damage.  People have suggested that the switch to turn off the pumps
should be removed from all nuclear plants. This is also wrong. There might
be a need to do that someday.

The solution is to better train the operators, so that they don't mess
with things they don't fully understand.  This is just as true of
networks, as it is of nuclear power plants. Probably more so of networks,
since these sorts of things happen more frequently, and even the network
engineers aren't nearly as uniformly trained, much less so the operators.

> > This is the first I have heard that path mtu discovery software was
> > unreliable.
> 
> PMTUD software is unreliable!?
> 
> Then, it is anther reason to avoid it.
> 
> Can you tell me who said it with an appropriate reference?

Err, _you_ said it:

On Sat, 8 May 2004, Masataka Ohta wrote:
> Further, it should be noted that PMTUD is so unreliable that
> no applications rely on it, which means that even under
> extreme conditions rational operators won't turn on PMTUD.
>
> In short, forget PMTUD.
>                                               Masataka Ohta
>
>




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



From ietf-admin@ietf.org  Mon May 10 14:16: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 OAA21360
	for <ietf-archive@ietf.org>; Mon, 10 May 2004 14:16: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 1BNFK5-0007TI-NW
	for ietf-archive@ietf.org; Mon, 10 May 2004 14:16:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNFJ8-00076t-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 14:15:19 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNFIU-0006l8-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 14:14:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNFE2-00027J-7P; Mon, 10 May 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 1BNF89-0000Sz-W9
	for ietf@optimus.ietf.org; Mon, 10 May 2004 14:03: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 OAA20512
	for <ietf@ietf.org>; Mon, 10 May 2004 14:03: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 1BNF87-0003EB-7p
	for ietf@ietf.org; Mon, 10 May 2004 14:03:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNF6z-0002b6-00
	for ietf@ietf.org; Mon, 10 May 2004 14:02:46 -0400
Received: from maxwell.derobert.net ([207.188.193.82])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNF5z-0002G2-00
	for ietf@ietf.org; Mon, 10 May 2004 14:01:43 -0400
Received: from fermi.vpn.home ([192.168.67.6])
	by Maxwell.derobert.net with esmtp (Exim 3.35 #1 (Debian))
	id 1BNF5n-0003HN-00; Mon, 10 May 2004 14:01:31 -0400
In-Reply-To: <Pine.LNX.4.44.0405091926270.4953-100000@cirrus.av8.net>
References: <Pine.LNX.4.44.0405091926270.4953-100000@cirrus.av8.net>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <1021DB6A-A2AC-11D8-A69B-00039317863E@suespammers.org>
Content-Transfer-Encoding: 7bit
Cc: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>,
        Rajat <myself_rajat@yahoo.com>, <ietf@ietf.org>
From: Anthony DeRobertis <asd@suespammers.org>
Subject: Re: Problem of blocking ICMP packets
Date: Mon, 10 May 2004 14:01:29 -0400
To: Dean Anderson <dean@av8.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 May 9, 2004, at 19:33, Dean Anderson wrote:
> I have only heard that those that block ICMP echo have had
> problems.

Nothing to do with ICMP echo. It's blocking ICMP unreachable, 
fragmentation needed that causes problems.

ICMP unreachables related to known connections should be allowed 
through the firewall.


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


From exim@www1.ietf.org  Mon May 10 14:17:55 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 OAA21462
	for <ietf-archive@odin.ietf.org>; Mon, 10 May 2004 14:17:55 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNFIW-0002s7-3n
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 14:14:40 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4AIEeDZ010929
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 14:14:40 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNFE2-00027J-7P; Mon, 10 May 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 1BNF89-0000Sz-W9
	for ietf@optimus.ietf.org; Mon, 10 May 2004 14:03: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 OAA20512
	for <ietf@ietf.org>; Mon, 10 May 2004 14:03: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 1BNF87-0003EB-7p
	for ietf@ietf.org; Mon, 10 May 2004 14:03:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNF6z-0002b6-00
	for ietf@ietf.org; Mon, 10 May 2004 14:02:46 -0400
Received: from maxwell.derobert.net ([207.188.193.82])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNF5z-0002G2-00
	for ietf@ietf.org; Mon, 10 May 2004 14:01:43 -0400
Received: from fermi.vpn.home ([192.168.67.6])
	by Maxwell.derobert.net with esmtp (Exim 3.35 #1 (Debian))
	id 1BNF5n-0003HN-00; Mon, 10 May 2004 14:01:31 -0400
In-Reply-To: <Pine.LNX.4.44.0405091926270.4953-100000@cirrus.av8.net>
References: <Pine.LNX.4.44.0405091926270.4953-100000@cirrus.av8.net>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <1021DB6A-A2AC-11D8-A69B-00039317863E@suespammers.org>
Content-Transfer-Encoding: 7bit
Cc: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>,
        Rajat <myself_rajat@yahoo.com>, <ietf@ietf.org>
From: Anthony DeRobertis <asd@suespammers.org>
Subject: Re: Problem of blocking ICMP packets
Date: Mon, 10 May 2004 14:01:29 -0400
To: Dean Anderson <dean@av8.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 May 9, 2004, at 19:33, Dean Anderson wrote:
> I have only heard that those that block ICMP echo have had
> problems.

Nothing to do with ICMP echo. It's blocking ICMP unreachable, 
fragmentation needed that causes problems.

ICMP unreachables related to known connections should be allowed 
through the firewall.


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



From ietf-admin@ietf.org  Mon May 10 14:38:43 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23127
	for <ietf-archive@ietf.org>; Mon, 10 May 2004 14:38: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 1BNFfo-0007j6-D0
	for ietf-archive@ietf.org; Mon, 10 May 2004 14:38:44 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNFem-0007Jw-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 14:37:41 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNFds-0006tt-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 14:36:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNFUX-0005SI-4E; Mon, 10 May 2004 14:27:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNFNw-0004De-Kz
	for ietf@optimus.ietf.org; Mon, 10 May 2004 14:20: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 OAA21677
	for <ietf@ietf.org>; Mon, 10 May 2004 14:20: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 1BNFNt-00019M-St
	for ietf@ietf.org; Mon, 10 May 2004 14:20:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNFMw-0000nW-00
	for ietf@ietf.org; Mon, 10 May 2004 14:19:15 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNFLy-00004W-00
	for ietf@ietf.org; Mon, 10 May 2004 14:18:14 -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 i4AIHfhU026206
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 10 May 2004 14:17:42 -0400
Date: Mon, 10 May 2004 14:17:41 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Harald Tveit Alvestrand <harald@alvestrand.no>
cc: ietf@ietf.org, <dnsop@lists.uoregon.edu>
Subject: Complaint on abuse of DNSOP lists
Message-ID: <Pine.LNX.4.44.0405101412540.25030-120000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; REPORT-TYPE=delivery-status; BOUNDARY="i4A0HNVe006325.1084148243/cirrus.av8.net"
Content-ID: <Pine.LNX.4.44.0405101415540.25030@cirrus.av8.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.6 required=5.0 tests=AWL,MAILTO_TO_SPAM_ADDR 
	autolearn=no version=2.60

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--i4A0HNVe006325.1084148243/cirrus.av8.net
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.LNX.4.44.0405101412542.25030@cirrus.av8.net>

Point of order, please

It seems that WG co-chair has begun to use an email address that is 
defaming Av8 Internet, Inc by returning business email to users of Av8 
Internet claiming that Av8 Internet has hijacked some address space.

Av8 Internet hereby demands that the IETF immediately end this behavior
and halt the defamation of Av8 Internet, Inc by IETF representatives.  
IETF representatives must use email addresses that are not configured for
defamation of Av8 Internet, Inc.

Dean Anderson
Av8 Internet, Inc



---------- Forwarded message ----------
Date: Sun, 9 May 2004 20:17:23 -0400
From: Mail Delivery Subsystem <MAILER-DAEMON@cirrus.av8.net>
To: dean@av8.com
Subject: Returned mail: see transcript for details

The original message was received at Sun, 9 May 2004 20:17:14 -0400
from cirrus.av8.net [130.105.36.66]

   ----- The following addresses had permanent fatal errors -----
<sra@isc.org>
    (reason: 553 Service unavailable; Client host [130.105.36.66] blocked using dnsbl.sorbs.net; Hijacked/Disused Netblock See: http://www.dnsbl.sorbs.net/cgi-bin/lookup?IP=130.105.36.66)

   ----- Transcript of session follows -----
... while talking to mx-1.isc.org.:
>>> DATA
<<< 553 Service unavailable; Client host [130.105.36.66] blocked using dnsbl.sorbs.net; Hijacked/Disused Netblock See: http://www.dnsbl.sorbs.net/cgi-bin/lookup?IP=130.105.36.66
550 5.1.1 <sra@isc.org>... User unknown
<<< 554 Error: no valid recipients

--i4A0HNVe006325.1084148243/cirrus.av8.net
Content-Type: MESSAGE/DELIVERY-STATUS; CHARSET=US-ASCII
Content-ID: <Pine.LNX.4.44.0405101412543.25030@cirrus.av8.net>
Content-Description: 

Reporting-MTA: dns; cirrus.av8.net
Received-From-MTA: DNS; cirrus.av8.net
Arrival-Date: Sun, 9 May 2004 20:17:14 -0400

Final-Recipient: RFC822; sra@isc.org
Action: failed
Status: 5.1.3
Remote-MTA: DNS; mx-1.isc.org
Diagnostic-Code: SMTP; 553 Service unavailable; Client host [130.105.36.66] blocked using dnsbl.sorbs.net; Hijacked/Disused Netblock See: http://www.dnsbl.sorbs.net/cgi-bin/lookup?IP=130.105.36.66
Last-Attempt-Date: Sun, 9 May 2004 20:17:20 -0400

--i4A0HNVe006325.1084148243/cirrus.av8.net
Content-Type: MESSAGE/RFC822; CHARSET=US-ASCII
Content-ID: <Pine.LNX.4.44.0405101412544.25030@cirrus.av8.net>
Content-Description: 

Return-Path: <dean@av8.com>
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 i4A0HEVg006323
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Sun, 9 May 2004 20:17:14 -0400
Date: Sun, 9 May 2004 20:17:14 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Rob Austein <sra@isc.org>
cc: dnsop@lists.uoregon.edu, <ph10@cam.ac.uk>
Subject: Re: [dnsop] draft-ietf-dnsop-dontpublish-unreachable-03.txt
In-Reply-To: <20040508025923.ECFDD42B2@thrintun.hactrn.net>
Message-ID: <Pine.LNX.4.44.0405092009280.4953-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I think it is a good idea too, but I don't see why it needs an RFC.  It is
purely administrative function in a nameserver to configure it not go give
out certain data to requests from, say, certain IP ranges. The issues of
'how it works' and what features, administrative syntax, etc seem to me to
be as proprietary as the server configuration file.

Indeed, it should be easy for some nameservers (powerDNS comes to mind)  
to do this now.  But it doesn't change the protocol, it just changes the
administration and operation of the server.


		--Dean

On Fri, 7 May 2004, Rob Austein wrote:

> At Thu, 06 May 2004 17:26:34 +0900, Jun-ichiro itojun Hagino wrote:
> > 
> > 	could you tell me what happened to
> > 	draft-ietf-dnsop-dontpublish-unreachable-03.txt?  it has been expired
> > 	for some time now.  i think it is a good document...
> 
> I thought it was useful too.  If I recall the history of this one
> correctly, it was a WG document which a number of people liked, but
> the WG ratholed discussing how many angels can dance on the word
> "unreachable", why firewalls are an offense before God, Man, and Small
> Furry Creature From Alpha Centauri, and other nonterminating topics.
> The author, not being totally out of his mind, eventually found
> something more productive to do with his time.
> 
> This document is not on the WG's current charter, because the last
> time we asked for a volunteer, the silence was deafening.  Absent
> somebody willing to work on it, there is no point in asking our ADs to
> let us put it back on the charter.
> 
> So: who cares about bringing this one back enough to work on it?
> 
> Given what happened the last time that I foolishly asserted from
> memory that an author had given up on a DNSOP WG doc, let me phrase
> this as a two part question:
> 
> a) Is the author interested in bringing back this document?  If so, he
>    of course has dibs.
> 
> b) Otherwise, is there somebody else who would be interested in
>    picking up the pen?
> .
> dnsop resources:_____________________________________________________
> web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
> mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html
> 


--i4A0HNVe006325.1084148243/cirrus.av8.net--

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


From ietf-admin@ietf.org  Mon May 10 14:40:57 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23268
	for <ietf-archive@ietf.org>; Mon, 10 May 2004 14:40: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 1BNFhy-0000zU-Ps
	for ietf-archive@ietf.org; Mon, 10 May 2004 14:40:58 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNFh0-0000bb-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 14:39:58 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNFfu-00004E-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 14:38:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNFUc-0005Wq-4T; Mon, 10 May 2004 14:27:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNFPo-0004Ma-M4
	for ietf@optimus.ietf.org; Mon, 10 May 2004 14:22:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21776
	for <ietf@ietf.org>; Mon, 10 May 2004 14:22: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 1BNFPl-0001pZ-Gx
	for ietf@ietf.org; Mon, 10 May 2004 14:22:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNFOo-0001VN-00
	for ietf@ietf.org; Mon, 10 May 2004 14:21:10 -0400
Received: from maxwell.derobert.net ([207.188.193.82])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNFOL-0001Aj-00
	for ietf@ietf.org; Mon, 10 May 2004 14:20:41 -0400
Received: from fermi.vpn.home ([192.168.67.6])
	by Maxwell.derobert.net with esmtp (Exim 3.35 #1 (Debian))
	id 1BNFNj-0003RH-00; Mon, 10 May 2004 14:20:03 -0400
In-Reply-To: <409F93F0.5060300@ehsco.com>
References: <DD72EEC3-A1E7-11D8-8626-003065F939FE@rudd.cc> <Pine.LNX.4.58.0405100019050.1405@perp.cac.washington.edu> <409F93F0.5060300@ehsco.com>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <A7BB27FB-A2AE-11D8-A69B-00039317863E@suespammers.org>
Content-Transfer-Encoding: 7bit
Cc: John Rudd <john@rudd.cc>, "RL 'Bob' Morgan" <rlmorgan@washington.edu>,
        IETF <ietf@ietf.org>
From: Anthony DeRobertis <asd@suespammers.org>
Subject: Re: Not sure if this is the right place for this
Date: Mon, 10 May 2004 14:20:02 -0400
To: "Eric A. Hall" <ehall@ehsco.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 May 10, 2004, at 10:38, Eric A. Hall wrote:

> Using an encrypted port just means an attack can only produce failure,
> rather than inducing fallback.

Clients generally default to using the unencrypted port.

Clients generally default to accepting non-STARTTLS connections.

Both require configuration changes to be fully secure. At least with 
starttls you are secure against a passive attacker (because clients use 
starttls if they can).


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


From exim@www1.ietf.org  Mon May 10 14:43:21 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 OAA23551
	for <ietf-archive@odin.ietf.org>; Mon, 10 May 2004 14:43:21 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNFdu-00077S-Ju
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 14:36:49 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4AIakCo027367
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 14:36:46 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNFUX-0005SI-4E; Mon, 10 May 2004 14:27:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNFNw-0004De-Kz
	for ietf@optimus.ietf.org; Mon, 10 May 2004 14:20: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 OAA21677
	for <ietf@ietf.org>; Mon, 10 May 2004 14:20: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 1BNFNt-00019M-St
	for ietf@ietf.org; Mon, 10 May 2004 14:20:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNFMw-0000nW-00
	for ietf@ietf.org; Mon, 10 May 2004 14:19:15 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNFLy-00004W-00
	for ietf@ietf.org; Mon, 10 May 2004 14:18:14 -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 i4AIHfhU026206
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 10 May 2004 14:17:42 -0400
Date: Mon, 10 May 2004 14:17:41 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Harald Tveit Alvestrand <harald@alvestrand.no>
cc: ietf@ietf.org, <dnsop@lists.uoregon.edu>
Subject: Complaint on abuse of DNSOP lists
Message-ID: <Pine.LNX.4.44.0405101412540.25030-120000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; REPORT-TYPE=delivery-status; BOUNDARY="i4A0HNVe006325.1084148243/cirrus.av8.net"
Content-ID: <Pine.LNX.4.44.0405101415540.25030@cirrus.av8.net>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,MAILTO_TO_SPAM_ADDR 
	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 message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--i4A0HNVe006325.1084148243/cirrus.av8.net
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.LNX.4.44.0405101412542.25030@cirrus.av8.net>

Point of order, please

It seems that WG co-chair has begun to use an email address that is 
defaming Av8 Internet, Inc by returning business email to users of Av8 
Internet claiming that Av8 Internet has hijacked some address space.

Av8 Internet hereby demands that the IETF immediately end this behavior
and halt the defamation of Av8 Internet, Inc by IETF representatives.  
IETF representatives must use email addresses that are not configured for
defamation of Av8 Internet, Inc.

Dean Anderson
Av8 Internet, Inc



---------- Forwarded message ----------
Date: Sun, 9 May 2004 20:17:23 -0400
From: Mail Delivery Subsystem <MAILER-DAEMON@cirrus.av8.net>
To: dean@av8.com
Subject: Returned mail: see transcript for details

The original message was received at Sun, 9 May 2004 20:17:14 -0400
from cirrus.av8.net [130.105.36.66]

   ----- The following addresses had permanent fatal errors -----
<sra@isc.org>
    (reason: 553 Service unavailable; Client host [130.105.36.66] blocked using dnsbl.sorbs.net; Hijacked/Disused Netblock See: http://www.dnsbl.sorbs.net/cgi-bin/lookup?IP=130.105.36.66)

   ----- Transcript of session follows -----
... while talking to mx-1.isc.org.:
>>> DATA
<<< 553 Service unavailable; Client host [130.105.36.66] blocked using dnsbl.sorbs.net; Hijacked/Disused Netblock See: http://www.dnsbl.sorbs.net/cgi-bin/lookup?IP=130.105.36.66
550 5.1.1 <sra@isc.org>... User unknown
<<< 554 Error: no valid recipients

--i4A0HNVe006325.1084148243/cirrus.av8.net
Content-Type: MESSAGE/DELIVERY-STATUS; CHARSET=US-ASCII
Content-ID: <Pine.LNX.4.44.0405101412543.25030@cirrus.av8.net>
Content-Description: 

Reporting-MTA: dns; cirrus.av8.net
Received-From-MTA: DNS; cirrus.av8.net
Arrival-Date: Sun, 9 May 2004 20:17:14 -0400

Final-Recipient: RFC822; sra@isc.org
Action: failed
Status: 5.1.3
Remote-MTA: DNS; mx-1.isc.org
Diagnostic-Code: SMTP; 553 Service unavailable; Client host [130.105.36.66] blocked using dnsbl.sorbs.net; Hijacked/Disused Netblock See: http://www.dnsbl.sorbs.net/cgi-bin/lookup?IP=130.105.36.66
Last-Attempt-Date: Sun, 9 May 2004 20:17:20 -0400

--i4A0HNVe006325.1084148243/cirrus.av8.net
Content-Type: MESSAGE/RFC822; CHARSET=US-ASCII
Content-ID: <Pine.LNX.4.44.0405101412544.25030@cirrus.av8.net>
Content-Description: 

Return-Path: <dean@av8.com>
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 i4A0HEVg006323
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Sun, 9 May 2004 20:17:14 -0400
Date: Sun, 9 May 2004 20:17:14 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Rob Austein <sra@isc.org>
cc: dnsop@lists.uoregon.edu, <ph10@cam.ac.uk>
Subject: Re: [dnsop] draft-ietf-dnsop-dontpublish-unreachable-03.txt
In-Reply-To: <20040508025923.ECFDD42B2@thrintun.hactrn.net>
Message-ID: <Pine.LNX.4.44.0405092009280.4953-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

I think it is a good idea too, but I don't see why it needs an RFC.  It is
purely administrative function in a nameserver to configure it not go give
out certain data to requests from, say, certain IP ranges. The issues of
'how it works' and what features, administrative syntax, etc seem to me to
be as proprietary as the server configuration file.

Indeed, it should be easy for some nameservers (powerDNS comes to mind)  
to do this now.  But it doesn't change the protocol, it just changes the
administration and operation of the server.


		--Dean

On Fri, 7 May 2004, Rob Austein wrote:

> At Thu, 06 May 2004 17:26:34 +0900, Jun-ichiro itojun Hagino wrote:
> > 
> > 	could you tell me what happened to
> > 	draft-ietf-dnsop-dontpublish-unreachable-03.txt?  it has been expired
> > 	for some time now.  i think it is a good document...
> 
> I thought it was useful too.  If I recall the history of this one
> correctly, it was a WG document which a number of people liked, but
> the WG ratholed discussing how many angels can dance on the word
> "unreachable", why firewalls are an offense before God, Man, and Small
> Furry Creature From Alpha Centauri, and other nonterminating topics.
> The author, not being totally out of his mind, eventually found
> something more productive to do with his time.
> 
> This document is not on the WG's current charter, because the last
> time we asked for a volunteer, the silence was deafening.  Absent
> somebody willing to work on it, there is no point in asking our ADs to
> let us put it back on the charter.
> 
> So: who cares about bringing this one back enough to work on it?
> 
> Given what happened the last time that I foolishly asserted from
> memory that an author had given up on a DNSOP WG doc, let me phrase
> this as a two part question:
> 
> a) Is the author interested in bringing back this document?  If so, he
>    of course has dibs.
> 
> b) Otherwise, is there somebody else who would be interested in
>    picking up the pen?
> .
> dnsop resources:_____________________________________________________
> web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
> mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html
> 


--i4A0HNVe006325.1084148243/cirrus.av8.net--

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



From exim@www1.ietf.org  Mon May 10 14:43:25 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 OAA23568
	for <ietf-archive@odin.ietf.org>; Mon, 10 May 2004 14:43: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 1BNFfw-000850-Uj
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 14:38:55 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4AIcqj5030980
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 14:38:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNFUc-0005Wq-4T; Mon, 10 May 2004 14:27:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNFPo-0004Ma-M4
	for ietf@optimus.ietf.org; Mon, 10 May 2004 14:22:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21776
	for <ietf@ietf.org>; Mon, 10 May 2004 14:22: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 1BNFPl-0001pZ-Gx
	for ietf@ietf.org; Mon, 10 May 2004 14:22:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNFOo-0001VN-00
	for ietf@ietf.org; Mon, 10 May 2004 14:21:10 -0400
Received: from maxwell.derobert.net ([207.188.193.82])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNFOL-0001Aj-00
	for ietf@ietf.org; Mon, 10 May 2004 14:20:41 -0400
Received: from fermi.vpn.home ([192.168.67.6])
	by Maxwell.derobert.net with esmtp (Exim 3.35 #1 (Debian))
	id 1BNFNj-0003RH-00; Mon, 10 May 2004 14:20:03 -0400
In-Reply-To: <409F93F0.5060300@ehsco.com>
References: <DD72EEC3-A1E7-11D8-8626-003065F939FE@rudd.cc> <Pine.LNX.4.58.0405100019050.1405@perp.cac.washington.edu> <409F93F0.5060300@ehsco.com>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <A7BB27FB-A2AE-11D8-A69B-00039317863E@suespammers.org>
Content-Transfer-Encoding: 7bit
Cc: John Rudd <john@rudd.cc>, "RL 'Bob' Morgan" <rlmorgan@washington.edu>,
        IETF <ietf@ietf.org>
From: Anthony DeRobertis <asd@suespammers.org>
Subject: Re: Not sure if this is the right place for this
Date: Mon, 10 May 2004 14:20:02 -0400
To: "Eric A. Hall" <ehall@ehsco.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 May 10, 2004, at 10:38, Eric A. Hall wrote:

> Using an encrypted port just means an attack can only produce failure,
> rather than inducing fallback.

Clients generally default to using the unencrypted port.

Clients generally default to accepting non-STARTTLS connections.

Both require configuration changes to be fully secure. At least with 
starttls you are secure against a passive attacker (because clients use 
starttls if they can).


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



From ietf-admin@ietf.org  Mon May 10 15:04: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 PAA25025
	for <ietf-archive@ietf.org>; Mon, 10 May 2004 15:04: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 1BNG4Z-0001Dq-7Y
	for ietf-archive@ietf.org; Mon, 10 May 2004 15:04:19 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNG3V-0000sF-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 15:03:13 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNG2w-0000X4-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 15:02:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNFxW-0002Ux-6s; Mon, 10 May 2004 14:57:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNFnn-00018A-59
	for ietf@optimus.ietf.org; Mon, 10 May 2004 14:46:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23911
	for <ietf@ietf.org>; Mon, 10 May 2004 14:46:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNFnk-00038U-9a
	for ietf@ietf.org; Mon, 10 May 2004 14:46:56 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNFml-0002nF-00
	for ietf@ietf.org; Mon, 10 May 2004 14:45:56 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with smtp (Exim 4.12)
	id 1BNFlr-0002RK-00
	for ietf@ietf.org; Mon, 10 May 2004 14:44:59 -0400
Received: (qmail 13416 invoked from network); 10 May 2004 18:47:24 -0000
Received: from yahoobb219178198119.bbtec.net (HELO necom830.hpcl.titech.ac.jp) (219.178.198.119)
  by necom830.hpcl.titech.ac.jp with SMTP; 10 May 2004 18:47:24 -0000
Message-ID: <409FCE99.5050301@necom830.hpcl.titech.ac.jp>
Date: Tue, 11 May 2004 03:48:57 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: ja, en-us, en
MIME-Version: 1.0
To: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
CC: dean@av8.com, myself_rajat@yahoo.com, ietf@ietf.org
Subject: Re: Problem of blocking ICMP packets
References: <Pine.LNX.4.44.0405091926270.4953-100000@cirrus.av8.net>	<409EE11F.9070601@necom830.hpcl.titech.ac.jp> <20040510130210.09ac9313.ietf@130c04165a5b40404e4440445758487a.nosense.org>
In-Reply-To: <20040510130210.09ac9313.ietf@130c04165a5b40404e4440445758487a.nosense.org>
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

Mark Smith;

>>>A number of commercial
>>>products and applications do rely on PMTU to work, and will
>>>do an PATH MTU discovery, and send the MTU sized packets with
>>>DF (don't frag).
>>
>>and send packets larger than MTU expecting to receive ICMP
>>errors in vain.
>>
>>Read the original mail of the thread on the reality.

> The problem identified has nothing to do with the concept or
> typical implementations of PMTUD being broken.

Wrong.

> RFC1192 (http://www.rfc-editor.org/rfc/rfc1191.txt) is the spec
> for PMTUD. 

Read the RFC.

It says "To detect increases in a path's PMTU, a host periodically
increases its assumed PMTU".

							Masataka Ohta



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


From ietf-admin@ietf.org  Mon May 10 15:10: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 PAA25732
	for <ietf-archive@ietf.org>; Mon, 10 May 2004 15:10: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 1BNGAI-0003GO-FP
	for ietf-archive@ietf.org; Mon, 10 May 2004 15:10:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNG9M-0002vD-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 15:09:17 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNG8i-0002Zi-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 15:08:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNFxZ-0002XJ-OE; Mon, 10 May 2004 14:57:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNFp8-0001Kj-V9
	for ietf@optimus.ietf.org; Mon, 10 May 2004 14:48:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24009
	for <ietf@ietf.org>; Mon, 10 May 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 1BNFp5-0003Wr-S8
	for ietf@ietf.org; Mon, 10 May 2004 14:48:19 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNFo4-0003Bf-00
	for ietf@ietf.org; Mon, 10 May 2004 14:47:17 -0400
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNFnT-0002p1-00
	for ietf@ietf.org; Mon, 10 May 2004 14:46:40 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i4AIjXg04719;
	Mon, 10 May 2004 21:45:33 +0300
Date: Mon, 10 May 2004 21:45:33 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Dean Anderson <dean@av8.com>
cc: Harald Tveit Alvestrand <harald@alvestrand.no>, <ietf@ietf.org>,
        <dnsop@lists.uoregon.edu>
Subject: Re: Complaint on abuse of DNSOP lists
In-Reply-To: <Pine.LNX.4.44.0405101412540.25030-120000@cirrus.av8.net>
Message-ID: <Pine.LNX.4.44.0405102142391.4414-100000@netcore.fi>
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, 10 May 2004, Dean Anderson wrote:
> Point of order, please
> 
> It seems that WG co-chair has begun to use an email address that is 
> defaming Av8 Internet, Inc by returning business email to users of Av8 
> Internet claiming that Av8 Internet has hijacked some address space.
> 
> Av8 Internet hereby demands that the IETF immediately end this behavior
> and halt the defamation of Av8 Internet, Inc by IETF representatives.  
> IETF representatives must use email addresses that are not configured for
> defamation of Av8 Internet, Inc.

If you look at the message, you will note that it is a bounce from the
WG co-chair's _personal_ email address, directly to your email
address.

I'd say that everyone has the right to choose what mail to accept (or
not to accept).

You might or might not have a point if this behaviour happened on an 
IETF list, but that is not the case..

> ---------- Forwarded message ----------
> Date: Sun, 9 May 2004 20:17:23 -0400
> From: Mail Delivery Subsystem <MAILER-DAEMON@cirrus.av8.net>
> To: dean@av8.com
> Subject: Returned mail: see transcript for details
> 
> The original message was received at Sun, 9 May 2004 20:17:14 -0400
> from cirrus.av8.net [130.105.36.66]
> 
>    ----- The following addresses had permanent fatal errors -----
> <sra@isc.org>
>     (reason: 553 Service unavailable; Client host [130.105.36.66] blocked using dnsbl.sorbs.net; Hijacked/Disused Netblock See: http://www.dnsbl.sorbs.net/cgi-bin/lookup?IP=130.105.36.66)
> 
>    ----- Transcript of session follows -----
> ... while talking to mx-1.isc.org.:
> >>> DATA
> <<< 553 Service unavailable; Client host [130.105.36.66] blocked using dnsbl.sorbs.net; Hijacked/Disused Netblock See: http://www.dnsbl.sorbs.net/cgi-bin/lookup?IP=130.105.36.66
> 550 5.1.1 <sra@isc.org>... User unknown
> <<< 554 Error: no valid recipients
> 

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


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


From exim@www1.ietf.org  Mon May 10 15:14:39 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 PAA26215
	for <ietf-archive@odin.ietf.org>; Mon, 10 May 2004 15:14: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 1BNG2z-0007HD-16
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 15:02:41 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4AJ2exQ027926
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 15:02:40 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNFxW-0002Ux-6s; Mon, 10 May 2004 14:57:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNFnn-00018A-59
	for ietf@optimus.ietf.org; Mon, 10 May 2004 14:46:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23911
	for <ietf@ietf.org>; Mon, 10 May 2004 14:46:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNFnk-00038U-9a
	for ietf@ietf.org; Mon, 10 May 2004 14:46:56 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNFml-0002nF-00
	for ietf@ietf.org; Mon, 10 May 2004 14:45:56 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with smtp (Exim 4.12)
	id 1BNFlr-0002RK-00
	for ietf@ietf.org; Mon, 10 May 2004 14:44:59 -0400
Received: (qmail 13416 invoked from network); 10 May 2004 18:47:24 -0000
Received: from yahoobb219178198119.bbtec.net (HELO necom830.hpcl.titech.ac.jp) (219.178.198.119)
  by necom830.hpcl.titech.ac.jp with SMTP; 10 May 2004 18:47:24 -0000
Message-ID: <409FCE99.5050301@necom830.hpcl.titech.ac.jp>
Date: Tue, 11 May 2004 03:48:57 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: ja, en-us, en
MIME-Version: 1.0
To: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
CC: dean@av8.com, myself_rajat@yahoo.com, ietf@ietf.org
Subject: Re: Problem of blocking ICMP packets
References: <Pine.LNX.4.44.0405091926270.4953-100000@cirrus.av8.net>	<409EE11F.9070601@necom830.hpcl.titech.ac.jp> <20040510130210.09ac9313.ietf@130c04165a5b40404e4440445758487a.nosense.org>
In-Reply-To: <20040510130210.09ac9313.ietf@130c04165a5b40404e4440445758487a.nosense.org>
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

Mark Smith;

>>>A number of commercial
>>>products and applications do rely on PMTU to work, and will
>>>do an PATH MTU discovery, and send the MTU sized packets with
>>>DF (don't frag).
>>
>>and send packets larger than MTU expecting to receive ICMP
>>errors in vain.
>>
>>Read the original mail of the thread on the reality.

> The problem identified has nothing to do with the concept or
> typical implementations of PMTUD being broken.

Wrong.

> RFC1192 (http://www.rfc-editor.org/rfc/rfc1191.txt) is the spec
> for PMTUD. 

Read the RFC.

It says "To detect increases in a path's PMTU, a host periodically
increases its assumed PMTU".

							Masataka Ohta



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



From exim@www1.ietf.org  Mon May 10 15:14:55 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 PAA26253
	for <ietf-archive@odin.ietf.org>; Mon, 10 May 2004 15:14:55 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNG8k-00031g-GN
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 15:08:40 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4AJ8cst011623
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 15:08:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNFxZ-0002XJ-OE; Mon, 10 May 2004 14:57:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNFp8-0001Kj-V9
	for ietf@optimus.ietf.org; Mon, 10 May 2004 14:48:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24009
	for <ietf@ietf.org>; Mon, 10 May 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 1BNFp5-0003Wr-S8
	for ietf@ietf.org; Mon, 10 May 2004 14:48:19 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNFo4-0003Bf-00
	for ietf@ietf.org; Mon, 10 May 2004 14:47:17 -0400
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNFnT-0002p1-00
	for ietf@ietf.org; Mon, 10 May 2004 14:46:40 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i4AIjXg04719;
	Mon, 10 May 2004 21:45:33 +0300
Date: Mon, 10 May 2004 21:45:33 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Dean Anderson <dean@av8.com>
cc: Harald Tveit Alvestrand <harald@alvestrand.no>, <ietf@ietf.org>,
        <dnsop@lists.uoregon.edu>
Subject: Re: Complaint on abuse of DNSOP lists
In-Reply-To: <Pine.LNX.4.44.0405101412540.25030-120000@cirrus.av8.net>
Message-ID: <Pine.LNX.4.44.0405102142391.4414-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: 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, 10 May 2004, Dean Anderson wrote:
> Point of order, please
> 
> It seems that WG co-chair has begun to use an email address that is 
> defaming Av8 Internet, Inc by returning business email to users of Av8 
> Internet claiming that Av8 Internet has hijacked some address space.
> 
> Av8 Internet hereby demands that the IETF immediately end this behavior
> and halt the defamation of Av8 Internet, Inc by IETF representatives.  
> IETF representatives must use email addresses that are not configured for
> defamation of Av8 Internet, Inc.

If you look at the message, you will note that it is a bounce from the
WG co-chair's _personal_ email address, directly to your email
address.

I'd say that everyone has the right to choose what mail to accept (or
not to accept).

You might or might not have a point if this behaviour happened on an 
IETF list, but that is not the case..

> ---------- Forwarded message ----------
> Date: Sun, 9 May 2004 20:17:23 -0400
> From: Mail Delivery Subsystem <MAILER-DAEMON@cirrus.av8.net>
> To: dean@av8.com
> Subject: Returned mail: see transcript for details
> 
> The original message was received at Sun, 9 May 2004 20:17:14 -0400
> from cirrus.av8.net [130.105.36.66]
> 
>    ----- The following addresses had permanent fatal errors -----
> <sra@isc.org>
>     (reason: 553 Service unavailable; Client host [130.105.36.66] blocked using dnsbl.sorbs.net; Hijacked/Disused Netblock See: http://www.dnsbl.sorbs.net/cgi-bin/lookup?IP=130.105.36.66)
> 
>    ----- Transcript of session follows -----
> ... while talking to mx-1.isc.org.:
> >>> DATA
> <<< 553 Service unavailable; Client host [130.105.36.66] blocked using dnsbl.sorbs.net; Hijacked/Disused Netblock See: http://www.dnsbl.sorbs.net/cgi-bin/lookup?IP=130.105.36.66
> 550 5.1.1 <sra@isc.org>... User unknown
> <<< 554 Error: no valid recipients
> 

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


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



From ietf-admin@ietf.org  Mon May 10 15:36: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 PAA28146
	for <ietf-archive@ietf.org>; Mon, 10 May 2004 15:36: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 1BNGZW-0004Wk-U4
	for ietf-archive@ietf.org; Mon, 10 May 2004 15:36:18 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNGYX-0004BE-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 15:35:18 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNGY3-0003pl-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 15:34:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNGRh-0001UT-8o; Mon, 10 May 2004 15:28:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNGLi-0000Nm-2c
	for ietf@optimus.ietf.org; Mon, 10 May 2004 15:22: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 PAA27091
	for <ietf@ietf.org>; Mon, 10 May 2004 15:21: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 1BNGLg-0007Ns-HF
	for ietf@ietf.org; Mon, 10 May 2004 15:22:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNGKq-00071R-00
	for ietf@ietf.org; Mon, 10 May 2004 15:21:09 -0400
Received: from biscayne-one-station.mit.edu ([18.7.7.80])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNGJf-0006bF-00
	for ietf@ietf.org; Mon, 10 May 2004 15:19:55 -0400
Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86])
	by biscayne-one-station.mit.edu (8.12.4/8.9.2) with ESMTP id i4AJJrjs020761;
	Mon, 10 May 2004 15:19:53 -0400 (EDT)
Received: from [18.18.1.76] (KEN-WIRELESS.MIT.EDU [18.18.1.76])
	(authenticated bits=0)
        (User authenticated as raeburn@ATHENA.MIT.EDU)
	by melbourne-city-street.mit.edu (8.12.4/8.12.4) with ESMTP id i4AJJoAf012274
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT);
	Mon, 10 May 2004 15:19:51 -0400 (EDT)
In-Reply-To: <Pine.LNX.4.44.0405101412540.25030-120000@cirrus.av8.net>
References: <Pine.LNX.4.44.0405101412540.25030-120000@cirrus.av8.net>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <FFF45958-A2B6-11D8-B627-000A95909EE2@mit.edu>
Cc: Harald Tveit Alvestrand <harald@alvestrand.no>, ietf@ietf.org,
        "<dnsop@lists.uoregon.edu>" <dnsop@lists.uoregon.edu>
From: Ken Raeburn <raeburn@MIT.EDU>
Subject: Re: Complaint on abuse of DNSOP lists
Date: Mon, 10 May 2004 15:19:46 -0400
To: Dean Anderson <dean@av8.com>
X-Mailer: Apple Mail (2.613)
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

On May 10, 2004, at 14:17, Dean Anderson wrote:

> It seems that WG co-chair has begun to use an email address that is
> defaming Av8 Internet, Inc by returning business email to users of Av8
> Internet claiming that Av8 Internet has hijacked some address space.

That may or may not be, but since you didn't show any bounce from 
uoregon, your claim of "abuse of DNSOP lists" in the subject line 
appears to be unsupported.

And I'd read the error message to suggest that perhaps Av8's net block 
had *been* hijacked (in someone's experience, not necessarily 
world-wide, which would be an interesting problem for globally 
distributed block lists), not that Av8 necessarily had done it.

> Av8 Internet hereby demands that the IETF immediately end this behavior
> and halt the defamation of Av8 Internet, Inc by IETF representatives.
> IETF representatives must use email addresses that are not configured 
> for
> defamation of Av8 Internet, Inc.

Yes, I'm sure that SRA was the one who submitted Av8's netblock to 
SORBS, and set up ISC to use SORBS, as part of a secret plot to ruin 
your reputation. </sarcasm>

How about suggesting a more positive solution, instead of throwing 
around language like "defamation"?  Maybe, "IETF WG chairs should 
have/use addresses that don't reject mail based on unreliable block 
lists (for some definition of 'unreliable'), and the IETF should 
provide a forwarding service for those chairs who cannot otherwise get 
such an address."

I would also suggest you try to resolve the issue with SORBS, except 
that when I tried the URL suggested, I got "ERROR: Couldn't prepare 
statement: $dbh is (undef)".  So I guess you could question the 
reliability of this particular service....

Ken


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


From ietf-admin@ietf.org  Mon May 10 15:40: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 PAA28452
	for <ietf-archive@ietf.org>; Mon, 10 May 2004 15:40:16 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNGdN-0005ys-8N
	for ietf-archive@ietf.org; Mon, 10 May 2004 15:40:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNGcN-0005d6-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 15:39:16 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNGbl-0005Hl-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 15:38:37 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNGRm-0001V1-3o; Mon, 10 May 2004 15:28:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNGMk-0000bD-Sx
	for ietf@optimus.ietf.org; Mon, 10 May 2004 15:23: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 PAA27214
	for <ietf@ietf.org>; Mon, 10 May 2004 15:23: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 1BNGMj-0007jn-Eu
	for ietf@ietf.org; Mon, 10 May 2004 15:23:05 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNGLj-0007OB-00
	for ietf@ietf.org; Mon, 10 May 2004 15:22:03 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with smtp (Exim 4.12)
	id 1BNGKy-00072F-00
	for ietf@ietf.org; Mon, 10 May 2004 15:21:16 -0400
Received: (qmail 13608 invoked from network); 10 May 2004 19:23:43 -0000
Received: from yahoobb219178198119.bbtec.net (HELO necom830.hpcl.titech.ac.jp) (219.178.198.119)
  by necom830.hpcl.titech.ac.jp with SMTP; 10 May 2004 19:23:43 -0000
Message-ID: <409FD71C.9020209@necom830.hpcl.titech.ac.jp>
Date: Tue, 11 May 2004 04:25:16 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: ja, en-us, en
MIME-Version: 1.0
To: Dean Anderson <dean@av8.com>
CC: Rajat <myself_rajat@yahoo.com>, ietf@ietf.org
Subject: Re: Problem of blocking ICMP packets
References: <Pine.LNX.4.44.0405101318260.25030-100000@cirrus.av8.net>
In-Reply-To: <Pine.LNX.4.44.0405101318260.25030-100000@cirrus.av8.net>
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

Dean Anderson;

>>There were (still are?) number of web servers that wanted to send
>>big packets with DF turned on, because PMTUD was turned on on the
>>servers but ICMP errors were filtered.

> There still are such apps.  I ran into this recently, last winter.

So, that is the reality. Note that we run into this only if
there are both such servers and such filters.

> The
> network can't possibly work if people are going to turn
> critical parts of it off, parts that they don't fully understand.

The most critical ICMP generated by intermediate routers is
TTL exceeded, I think, though it is not critical for real
applications.

We can do without others. However, there are people who want to
invent inappropriate use of inessential features. For example,
TCP should not be disconnected upon network unreachable ICMP but
some TCP did. PMTUD is, IMHO, another example.

> I think we disagree on the "reality". The reality is that most sensible
> people and ISPs don't block harmless ICMP messages.

Sensible people should block PMTUD, too.

>>>This is the first I have heard that path mtu discovery software was
>>>unreliable.

>>Can you tell me who said it with an appropriate reference?

> Err, _you_ said it:

I never said software unreliable.

Note that an example of unreliable software is Windows.

						Masataka Ohta


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


From exim@www1.ietf.org  Mon May 10 15:40:45 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 PAA28475
	for <ietf-archive@odin.ietf.org>; Mon, 10 May 2004 15:40: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 1BNGY3-0002bm-Pn
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 15:34:50 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4AJYldJ010024
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 15:34:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNGRh-0001UT-8o; Mon, 10 May 2004 15:28:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNGLi-0000Nm-2c
	for ietf@optimus.ietf.org; Mon, 10 May 2004 15:22: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 PAA27091
	for <ietf@ietf.org>; Mon, 10 May 2004 15:21: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 1BNGLg-0007Ns-HF
	for ietf@ietf.org; Mon, 10 May 2004 15:22:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNGKq-00071R-00
	for ietf@ietf.org; Mon, 10 May 2004 15:21:09 -0400
Received: from biscayne-one-station.mit.edu ([18.7.7.80])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNGJf-0006bF-00
	for ietf@ietf.org; Mon, 10 May 2004 15:19:55 -0400
Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86])
	by biscayne-one-station.mit.edu (8.12.4/8.9.2) with ESMTP id i4AJJrjs020761;
	Mon, 10 May 2004 15:19:53 -0400 (EDT)
Received: from [18.18.1.76] (KEN-WIRELESS.MIT.EDU [18.18.1.76])
	(authenticated bits=0)
        (User authenticated as raeburn@ATHENA.MIT.EDU)
	by melbourne-city-street.mit.edu (8.12.4/8.12.4) with ESMTP id i4AJJoAf012274
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT);
	Mon, 10 May 2004 15:19:51 -0400 (EDT)
In-Reply-To: <Pine.LNX.4.44.0405101412540.25030-120000@cirrus.av8.net>
References: <Pine.LNX.4.44.0405101412540.25030-120000@cirrus.av8.net>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <FFF45958-A2B6-11D8-B627-000A95909EE2@mit.edu>
Cc: Harald Tveit Alvestrand <harald@alvestrand.no>, ietf@ietf.org,
        "<dnsop@lists.uoregon.edu>" <dnsop@lists.uoregon.edu>
From: Ken Raeburn <raeburn@MIT.EDU>
Subject: Re: Complaint on abuse of DNSOP lists
Date: Mon, 10 May 2004 15:19:46 -0400
To: Dean Anderson <dean@av8.com>
X-Mailer: Apple Mail (2.613)
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

On May 10, 2004, at 14:17, Dean Anderson wrote:

> It seems that WG co-chair has begun to use an email address that is
> defaming Av8 Internet, Inc by returning business email to users of Av8
> Internet claiming that Av8 Internet has hijacked some address space.

That may or may not be, but since you didn't show any bounce from 
uoregon, your claim of "abuse of DNSOP lists" in the subject line 
appears to be unsupported.

And I'd read the error message to suggest that perhaps Av8's net block 
had *been* hijacked (in someone's experience, not necessarily 
world-wide, which would be an interesting problem for globally 
distributed block lists), not that Av8 necessarily had done it.

> Av8 Internet hereby demands that the IETF immediately end this behavior
> and halt the defamation of Av8 Internet, Inc by IETF representatives.
> IETF representatives must use email addresses that are not configured 
> for
> defamation of Av8 Internet, Inc.

Yes, I'm sure that SRA was the one who submitted Av8's netblock to 
SORBS, and set up ISC to use SORBS, as part of a secret plot to ruin 
your reputation. </sarcasm>

How about suggesting a more positive solution, instead of throwing 
around language like "defamation"?  Maybe, "IETF WG chairs should 
have/use addresses that don't reject mail based on unreliable block 
lists (for some definition of 'unreliable'), and the IETF should 
provide a forwarding service for those chairs who cannot otherwise get 
such an address."

I would also suggest you try to resolve the issue with SORBS, except 
that when I tried the URL suggested, I got "ERROR: Couldn't prepare 
statement: $dbh is (undef)".  So I guess you could question the 
reliability of this particular service....

Ken


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



From exim@www1.ietf.org  Mon May 10 15:41: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 PAA28504
	for <ietf-archive@odin.ietf.org>; Mon, 10 May 2004 15:41: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 1BNGbl-0003b1-96
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 15:38:37 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4AJcbsi013803
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 15:38:37 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNGRm-0001V1-3o; Mon, 10 May 2004 15:28:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNGMk-0000bD-Sx
	for ietf@optimus.ietf.org; Mon, 10 May 2004 15:23: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 PAA27214
	for <ietf@ietf.org>; Mon, 10 May 2004 15:23: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 1BNGMj-0007jn-Eu
	for ietf@ietf.org; Mon, 10 May 2004 15:23:05 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNGLj-0007OB-00
	for ietf@ietf.org; Mon, 10 May 2004 15:22:03 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with smtp (Exim 4.12)
	id 1BNGKy-00072F-00
	for ietf@ietf.org; Mon, 10 May 2004 15:21:16 -0400
Received: (qmail 13608 invoked from network); 10 May 2004 19:23:43 -0000
Received: from yahoobb219178198119.bbtec.net (HELO necom830.hpcl.titech.ac.jp) (219.178.198.119)
  by necom830.hpcl.titech.ac.jp with SMTP; 10 May 2004 19:23:43 -0000
Message-ID: <409FD71C.9020209@necom830.hpcl.titech.ac.jp>
Date: Tue, 11 May 2004 04:25:16 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: ja, en-us, en
MIME-Version: 1.0
To: Dean Anderson <dean@av8.com>
CC: Rajat <myself_rajat@yahoo.com>, ietf@ietf.org
Subject: Re: Problem of blocking ICMP packets
References: <Pine.LNX.4.44.0405101318260.25030-100000@cirrus.av8.net>
In-Reply-To: <Pine.LNX.4.44.0405101318260.25030-100000@cirrus.av8.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: 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;

>>There were (still are?) number of web servers that wanted to send
>>big packets with DF turned on, because PMTUD was turned on on the
>>servers but ICMP errors were filtered.

> There still are such apps.  I ran into this recently, last winter.

So, that is the reality. Note that we run into this only if
there are both such servers and such filters.

> The
> network can't possibly work if people are going to turn
> critical parts of it off, parts that they don't fully understand.

The most critical ICMP generated by intermediate routers is
TTL exceeded, I think, though it is not critical for real
applications.

We can do without others. However, there are people who want to
invent inappropriate use of inessential features. For example,
TCP should not be disconnected upon network unreachable ICMP but
some TCP did. PMTUD is, IMHO, another example.

> I think we disagree on the "reality". The reality is that most sensible
> people and ISPs don't block harmless ICMP messages.

Sensible people should block PMTUD, too.

>>>This is the first I have heard that path mtu discovery software was
>>>unreliable.

>>Can you tell me who said it with an appropriate reference?

> Err, _you_ said it:

I never said software unreliable.

Note that an example of unreliable software is Windows.

						Masataka Ohta


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



From ietf-admin@ietf.org  Mon May 10 16:01: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 QAA29985
	for <ietf-archive@ietf.org>; Mon, 10 May 2004 16:01: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 1BNGxg-0005kK-Ip
	for ietf-archive@ietf.org; Mon, 10 May 2004 16:01:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNGwn-0005OH-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 16:00:22 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNGvl-00051j-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 15:59:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNGnm-0005rk-RW; Mon, 10 May 2004 15:51:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNGeS-0004Kr-Qy
	for ietf@optimus.ietf.org; Mon, 10 May 2004 15:41: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 PAA28548
	for <ietf@ietf.org>; Mon, 10 May 2004 15:41: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 1BNGeR-0006MI-7U
	for ietf@ietf.org; Mon, 10 May 2004 15:41:23 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNGdO-0005z7-00
	for ietf@ietf.org; Mon, 10 May 2004 15:40:18 -0400
Received: from carwash.centive.com ([65.220.90.249])
	by ietf-mx with smtp (Exim 4.12)
	id 1BNGcQ-0005Hu-00
	for ietf@ietf.org; Mon, 10 May 2004 15:39:19 -0400
Received: from minglewood.incentivesystems.com ([10.10.30.25])
 by carwash.centive.com (SAVSMTP 3.1.3.37) with SMTP id M2004051015390903763
 ; Mon, 10 May 2004 15:39:09 -0400
Received: from [10.10.48.119] ([10.10.48.119]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Mon, 10 May 2004 15:34:13 -0400
Message-ID: <409FD935.8020308@centive.com>
Date: Mon, 10 May 2004 15:34:13 -0400
From: John Stracke <jstracke@centive.com>
User-Agent: Mozilla Thunderbird 0.6 (Windows/20040502)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Dean Anderson <dean@av8.com>
CC: ietf@ietf.org, dnsop@lists.uoregon.edu
Subject: Re: Complaint on abuse of DNSOP lists
References: <Pine.LNX.4.44.0405101412540.25030-120000@cirrus.av8.net>
In-Reply-To: <Pine.LNX.4.44.0405101412540.25030-120000@cirrus.av8.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 10 May 2004 19:34:13.0920 (UTC) FILETIME=[C6748A00:01C436C5]
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

Dean Anderson wrote:

>It seems that WG co-chair has begun to use an email address that is 
>defaming Av8 Internet, Inc
>
How is it defamation if the only one that gets the message is Av8?

-- 
/=======================================================\
|John Stracke      |jstracke@centive.com                |
|Principal Engineer|http://www.centive.com              |
|Centive           |My opinions are my own.             |
|=======================================================|
|I'm not a bibliophile, I'm a bibliophiliac. Put me in a|
|bookstore, & my wallet bleeds.                         |
\=======================================================/


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


From exim@www1.ietf.org  Mon May 10 16:06:01 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 QAA00267
	for <ietf-archive@odin.ietf.org>; Mon, 10 May 2004 16:06: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 1BNGvl-0007Q3-MX
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 15:59:17 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4AJxHAq028498
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 15:59:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNGnm-0005rk-RW; Mon, 10 May 2004 15:51:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNGeS-0004Kr-Qy
	for ietf@optimus.ietf.org; Mon, 10 May 2004 15:41: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 PAA28548
	for <ietf@ietf.org>; Mon, 10 May 2004 15:41: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 1BNGeR-0006MI-7U
	for ietf@ietf.org; Mon, 10 May 2004 15:41:23 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNGdO-0005z7-00
	for ietf@ietf.org; Mon, 10 May 2004 15:40:18 -0400
Received: from carwash.centive.com ([65.220.90.249])
	by ietf-mx with smtp (Exim 4.12)
	id 1BNGcQ-0005Hu-00
	for ietf@ietf.org; Mon, 10 May 2004 15:39:19 -0400
Received: from minglewood.incentivesystems.com ([10.10.30.25])
 by carwash.centive.com (SAVSMTP 3.1.3.37) with SMTP id M2004051015390903763
 ; Mon, 10 May 2004 15:39:09 -0400
Received: from [10.10.48.119] ([10.10.48.119]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Mon, 10 May 2004 15:34:13 -0400
Message-ID: <409FD935.8020308@centive.com>
Date: Mon, 10 May 2004 15:34:13 -0400
From: John Stracke <jstracke@centive.com>
User-Agent: Mozilla Thunderbird 0.6 (Windows/20040502)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Dean Anderson <dean@av8.com>
CC: ietf@ietf.org, dnsop@lists.uoregon.edu
Subject: Re: Complaint on abuse of DNSOP lists
References: <Pine.LNX.4.44.0405101412540.25030-120000@cirrus.av8.net>
In-Reply-To: <Pine.LNX.4.44.0405101412540.25030-120000@cirrus.av8.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 10 May 2004 19:34:13.0920 (UTC) FILETIME=[C6748A00:01C436C5]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-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

Dean Anderson wrote:

>It seems that WG co-chair has begun to use an email address that is 
>defaming Av8 Internet, Inc
>
How is it defamation if the only one that gets the message is Av8?

-- 
/=======================================================\
|John Stracke      |jstracke@centive.com                |
|Principal Engineer|http://www.centive.com              |
|Centive           |My opinions are my own.             |
|=======================================================|
|I'm not a bibliophile, I'm a bibliophiliac. Put me in a|
|bookstore, & my wallet bleeds.                         |
\=======================================================/


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



From ietf-admin@ietf.org  Mon May 10 16:27: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 QAA01426
	for <ietf-archive@ietf.org>; Mon, 10 May 2004 16:27:15 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNHMq-0006wK-RI
	for ietf-archive@ietf.org; Mon, 10 May 2004 16:27:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNHLr-0006Y3-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 16:26:16 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNHKy-0006Ai-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 16:25:20 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNH94-0001VS-Jk; Mon, 10 May 2004 16:13:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNH1O-0000LC-9O
	for ietf@optimus.ietf.org; Mon, 10 May 2004 16:05:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00218
	for <ietf@ietf.org>; Mon, 10 May 2004 16:05:03 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNH1M-00075a-GJ
	for ietf@ietf.org; Mon, 10 May 2004 16:05:04 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNH0U-0006lM-00
	for ietf@ietf.org; Mon, 10 May 2004 16:04:11 -0400
Received: from maxwell.derobert.net ([207.188.193.82])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNGzo-0006R4-00
	for ietf@ietf.org; Mon, 10 May 2004 16:03:28 -0400
Received: from fermi.vpn.home ([192.168.67.6])
	by Maxwell.derobert.net with esmtp (Exim 3.35 #1 (Debian))
	id 1BNGzn-0004NS-00; Mon, 10 May 2004 16:03:27 -0400
In-Reply-To: <409FD71C.9020209@necom830.hpcl.titech.ac.jp>
References: <Pine.LNX.4.44.0405101318260.25030-100000@cirrus.av8.net> <409FD71C.9020209@necom830.hpcl.titech.ac.jp>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <180CB344-A2BD-11D8-A69B-00039317863E@suespammers.org>
Content-Transfer-Encoding: 7bit
Cc: Dean Anderson <dean@av8.com>, Rajat <myself_rajat@yahoo.com>,
        ietf@ietf.org
From: Anthony DeRobertis <asd@suespammers.org>
Subject: Re: Problem of blocking ICMP packets
Date: Mon, 10 May 2004 16:03:24 -0400
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
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 May 10, 2004, at 15:25, Masataka Ohta wrote:

> Sensible people should block PMTUD, too.

Why? Do you just enjoy breaking random things?



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


From ietf-admin@ietf.org  Mon May 10 16:28: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 QAA01534
	for <ietf-archive@ietf.org>; Mon, 10 May 2004 16:28: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 1BNHNy-0007ME-8v
	for ietf-archive@ietf.org; Mon, 10 May 2004 16:28:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNHND-0006zD-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 16:27:40 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNHM8-0006ay-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 16:26:32 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNHDu-0002Pc-CD; Mon, 10 May 2004 16: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 1BNH93-0001VJ-PK
	for ietf@optimus.ietf.org; Mon, 10 May 2004 16:13: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 QAA00529
	for <ietf@ietf.org>; Mon, 10 May 2004 16:12:58 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNH91-0001wj-Vc
	for ietf@ietf.org; Mon, 10 May 2004 16:13:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNH84-0001br-00
	for ietf@ietf.org; Mon, 10 May 2004 16:12:01 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNH77-0000z0-00
	for ietf@ietf.org; Mon, 10 May 2004 16:11:01 -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 i4AKAT5m028298
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 10 May 2004 16:10:30 -0400
Date: Mon, 10 May 2004 16:10:29 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Pekka Savola <pekkas@netcore.fi>
cc: Harald Tveit Alvestrand <harald@alvestrand.no>, <ietf@ietf.org>,
        <dnsop@lists.uoregon.edu>
Subject: Re: Complaint on abuse of DNSOP lists
In-Reply-To: <Pine.LNX.4.44.0405102142391.4414-100000@netcore.fi>
Message-ID: <Pine.LNX.4.44.0405101516140.25030-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, 10 May 2004, Pekka Savola wrote:

> On Mon, 10 May 2004, Dean Anderson wrote:
> > Point of order, please
> > 
> > It seems that WG co-chair has begun to use an email address that is 
> > defaming Av8 Internet, Inc by returning business email to users of Av8 
> > Internet claiming that Av8 Internet has hijacked some address space.
> > 
> > Av8 Internet hereby demands that the IETF immediately end this behavior
> > and halt the defamation of Av8 Internet, Inc by IETF representatives.  
> > IETF representatives must use email addresses that are not configured for
> > defamation of Av8 Internet, Inc.
> 
> If you look at the message, you will note that it is a bounce from the
> WG co-chair's _personal_ email address, directly to your email
> address.

Actually, it bounces this way to all Av8 Internet Customers, not just to
me.  But it was a bounce to a message Mr. Austein posted on DNSOP. It was
not private business. It was IETF business.

Further, by reviewing the archives of DNSOP, I have found that Mr.  
Austein's home address is <sra+dnsop@hactrn.net>, which he has used
exclusively for some time until March 1st of this year. He first started
using the ISC.ORG address on a message involving
draft-ietf-dnsop-inadr-required. Perhaps coincidentally, this draft is a
pet project of Mr. Austeins, and one to which I (and many others) have
raised serious objections regarding both misleading and incorrect content
and procedural irregularities.  The archives show that since March 1st,
2004, Mr.  Austein has made all his DNSOP posts from sra@isc.org.  

> I'd say that everyone has the right to choose what mail to accept (or
> not to accept).

They don't when they are conducting IETF business. IETF rules require that
participants not be excluded from IETF activities. WG chairs and others
cannot refuse email from participants.

As Joe Abley revealed previously, this configuration from ISC.ORG isn't
meant to actually block spam. The idea is to make Av8 Internet users have
to seek other email addresses by which to contact them, and to obtain
opportunities to defame Av8 Internet and perhaps others and convince users
to seek other services. This is unlawful.  Besides the defamation, it
would is an illegal group boycott, and an unfair business practice.

Refusing email is one thing, though that is still not permitted for IETF
business.  Defamation by claiming addresses are hijacked is quite another
thing. This abuse of email addresses is unacceptable, and illegal, and I
can engage legal action if necessary to prevent an organization like the
IETF from permitting this abuse to continue.

Mr. Austein cannot be allowed to use the ISC.ORG address for IETF
business.

> You might or might not have a point if this behaviour happened on an 
> IETF list, but that is not the case..

Actually, it is the case. This involves two IETF lists, and the conduct of
an IETF representative on the DNSOP list. My republishing of Mr. Austein's
defamation to the DNSOP and IETF list to make a complaint is a
republishment for which Mr.  Austein and the IETF are legally responsible
under US defamation tort law.

Mr Austein as a representative of the IETF defamed Av8 Internet to me, to
the customers of Av8 Internet, and to the readership of both the IETF and
DNSOP lists.  Mr. Austein is a co-chair of the IETF working group.  This
defamation came about through IETF working group business.

The IETF is responsible for the conduct of its representatives on its
lists.  It is unlawful to permit its representatives to use addresses
which are configured to defame IETF participants, and it is against the
IETF rules to refuse email from IETF participants.

Dean Anderson
President
Av8 Internet, Inc













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


From exim@www1.ietf.org  Mon May 10 16:29: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 QAA01676
	for <ietf-archive@odin.ietf.org>; Mon, 10 May 2004 16:29: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 1BNHFZ-00030r-Ai
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 16:19:48 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4AKJjQf011325
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 16:19:45 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNH94-0001VS-Jk; Mon, 10 May 2004 16:13:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNH1O-0000LC-9O
	for ietf@optimus.ietf.org; Mon, 10 May 2004 16:05:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00218
	for <ietf@ietf.org>; Mon, 10 May 2004 16:05:03 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNH1M-00075a-GJ
	for ietf@ietf.org; Mon, 10 May 2004 16:05:04 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNH0U-0006lM-00
	for ietf@ietf.org; Mon, 10 May 2004 16:04:11 -0400
Received: from maxwell.derobert.net ([207.188.193.82])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNGzo-0006R4-00
	for ietf@ietf.org; Mon, 10 May 2004 16:03:28 -0400
Received: from fermi.vpn.home ([192.168.67.6])
	by Maxwell.derobert.net with esmtp (Exim 3.35 #1 (Debian))
	id 1BNGzn-0004NS-00; Mon, 10 May 2004 16:03:27 -0400
In-Reply-To: <409FD71C.9020209@necom830.hpcl.titech.ac.jp>
References: <Pine.LNX.4.44.0405101318260.25030-100000@cirrus.av8.net> <409FD71C.9020209@necom830.hpcl.titech.ac.jp>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <180CB344-A2BD-11D8-A69B-00039317863E@suespammers.org>
Content-Transfer-Encoding: 7bit
Cc: Dean Anderson <dean@av8.com>, Rajat <myself_rajat@yahoo.com>,
        ietf@ietf.org
From: Anthony DeRobertis <asd@suespammers.org>
Subject: Re: Problem of blocking ICMP packets
Date: Mon, 10 May 2004 16:03:24 -0400
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
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 May 10, 2004, at 15:25, Masataka Ohta wrote:

> Sensible people should block PMTUD, too.

Why? Do you just enjoy breaking random things?



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



From exim@www1.ietf.org  Mon May 10 16:30:46 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 QAA01787
	for <ietf-archive@odin.ietf.org>; Mon, 10 May 2004 16:30: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 1BNHM9-0004Ml-Gf
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 16:26:33 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4AKQX1x016784
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 16:26:33 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNHDu-0002Pc-CD; Mon, 10 May 2004 16: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 1BNH93-0001VJ-PK
	for ietf@optimus.ietf.org; Mon, 10 May 2004 16:13: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 QAA00529
	for <ietf@ietf.org>; Mon, 10 May 2004 16:12:58 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNH91-0001wj-Vc
	for ietf@ietf.org; Mon, 10 May 2004 16:13:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNH84-0001br-00
	for ietf@ietf.org; Mon, 10 May 2004 16:12:01 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNH77-0000z0-00
	for ietf@ietf.org; Mon, 10 May 2004 16:11:01 -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 i4AKAT5m028298
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 10 May 2004 16:10:30 -0400
Date: Mon, 10 May 2004 16:10:29 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Pekka Savola <pekkas@netcore.fi>
cc: Harald Tveit Alvestrand <harald@alvestrand.no>, <ietf@ietf.org>,
        <dnsop@lists.uoregon.edu>
Subject: Re: Complaint on abuse of DNSOP lists
In-Reply-To: <Pine.LNX.4.44.0405102142391.4414-100000@netcore.fi>
Message-ID: <Pine.LNX.4.44.0405101516140.25030-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, 10 May 2004, Pekka Savola wrote:

> On Mon, 10 May 2004, Dean Anderson wrote:
> > Point of order, please
> > 
> > It seems that WG co-chair has begun to use an email address that is 
> > defaming Av8 Internet, Inc by returning business email to users of Av8 
> > Internet claiming that Av8 Internet has hijacked some address space.
> > 
> > Av8 Internet hereby demands that the IETF immediately end this behavior
> > and halt the defamation of Av8 Internet, Inc by IETF representatives.  
> > IETF representatives must use email addresses that are not configured for
> > defamation of Av8 Internet, Inc.
> 
> If you look at the message, you will note that it is a bounce from the
> WG co-chair's _personal_ email address, directly to your email
> address.

Actually, it bounces this way to all Av8 Internet Customers, not just to
me.  But it was a bounce to a message Mr. Austein posted on DNSOP. It was
not private business. It was IETF business.

Further, by reviewing the archives of DNSOP, I have found that Mr.  
Austein's home address is <sra+dnsop@hactrn.net>, which he has used
exclusively for some time until March 1st of this year. He first started
using the ISC.ORG address on a message involving
draft-ietf-dnsop-inadr-required. Perhaps coincidentally, this draft is a
pet project of Mr. Austeins, and one to which I (and many others) have
raised serious objections regarding both misleading and incorrect content
and procedural irregularities.  The archives show that since March 1st,
2004, Mr.  Austein has made all his DNSOP posts from sra@isc.org.  

> I'd say that everyone has the right to choose what mail to accept (or
> not to accept).

They don't when they are conducting IETF business. IETF rules require that
participants not be excluded from IETF activities. WG chairs and others
cannot refuse email from participants.

As Joe Abley revealed previously, this configuration from ISC.ORG isn't
meant to actually block spam. The idea is to make Av8 Internet users have
to seek other email addresses by which to contact them, and to obtain
opportunities to defame Av8 Internet and perhaps others and convince users
to seek other services. This is unlawful.  Besides the defamation, it
would is an illegal group boycott, and an unfair business practice.

Refusing email is one thing, though that is still not permitted for IETF
business.  Defamation by claiming addresses are hijacked is quite another
thing. This abuse of email addresses is unacceptable, and illegal, and I
can engage legal action if necessary to prevent an organization like the
IETF from permitting this abuse to continue.

Mr. Austein cannot be allowed to use the ISC.ORG address for IETF
business.

> You might or might not have a point if this behaviour happened on an 
> IETF list, but that is not the case..

Actually, it is the case. This involves two IETF lists, and the conduct of
an IETF representative on the DNSOP list. My republishing of Mr. Austein's
defamation to the DNSOP and IETF list to make a complaint is a
republishment for which Mr.  Austein and the IETF are legally responsible
under US defamation tort law.

Mr Austein as a representative of the IETF defamed Av8 Internet to me, to
the customers of Av8 Internet, and to the readership of both the IETF and
DNSOP lists.  Mr. Austein is a co-chair of the IETF working group.  This
defamation came about through IETF working group business.

The IETF is responsible for the conduct of its representatives on its
lists.  It is unlawful to permit its representatives to use addresses
which are configured to defame IETF participants, and it is against the
IETF rules to refuse email from IETF participants.

Dean Anderson
President
Av8 Internet, Inc













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



From ietf-admin@ietf.org  Mon May 10 17:10:49 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05357
	for <ietf-archive@ietf.org>; Mon, 10 May 2004 17:10: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 1BNI30-0007i7-Mz
	for ietf-archive@ietf.org; Mon, 10 May 2004 17:10:50 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNI1v-0007Go-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 17:09:43 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNI0X-0006f6-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 17:08:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNHQ0-0005Dl-Gk; Mon, 10 May 2004 16:30:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNHIx-0003Rp-7m
	for ietf@optimus.ietf.org; Mon, 10 May 2004 16:23: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 QAA01069
	for <ietf@ietf.org>; Mon, 10 May 2004 16:23: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 1BNHIv-0005PT-AF
	for ietf@ietf.org; Mon, 10 May 2004 16:23:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNHI5-00053D-00
	for ietf@ietf.org; Mon, 10 May 2004 16:22:22 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNHHX-0004gc-00
	for ietf@ietf.org; Mon, 10 May 2004 16:21:47 -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 i4AKLG4O028481
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 10 May 2004 16:21:16 -0400
Date: Mon, 10 May 2004 16:21:16 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Ken Raeburn <raeburn@MIT.EDU>
cc: Harald Tveit Alvestrand <harald@alvestrand.no>, <ietf@ietf.org>,
        "<dnsop@lists.uoregon.edu>" <dnsop@lists.uoregon.edu>
Subject: Re: Complaint on abuse of DNSOP lists
In-Reply-To: <FFF45958-A2B6-11D8-B627-000A95909EE2@mit.edu>
Message-ID: <Pine.LNX.4.44.0405101610410.25030-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, 10 May 2004, Ken Raeburn wrote:

> On May 10, 2004, at 14:17, Dean Anderson wrote:
> 
> > It seems that WG co-chair has begun to use an email address that is
> > defaming Av8 Internet, Inc by returning business email to users of Av8
> > Internet claiming that Av8 Internet has hijacked some address space.
> 
> That may or may not be, but since you didn't show any bounce from 
> uoregon, your claim of "abuse of DNSOP lists" in the subject line 
> appears to be unsupported.

Bounces don't have to come from Uoregon.  Mr. Austein is the WG chair.  He 
has to abide by the IETF rules, just like Uoregon (host of DNSOP)

> And I'd read the error message to suggest that perhaps Av8's net block 
> had *been* hijacked (in someone's experience, not necessarily 
> world-wide, which would be an interesting problem for globally 
> distributed block lists), not that Av8 necessarily had done it.

This isn't the case. And if it were, Av8 would make that claim, no one 
else would.

> > Av8 Internet hereby demands that the IETF immediately end this behavior
> > and halt the defamation of Av8 Internet, Inc by IETF representatives.
> > IETF representatives must use email addresses that are not configured 
> > for
> > defamation of Av8 Internet, Inc.
> 
> Yes, I'm sure that SRA was the one who submitted Av8's netblock to 
> SORBS, and set up ISC to use SORBS, as part of a secret plot to ruin 
> your reputation. </sarcasm>

This has no legal relevance. Repetition of defamation is still defamation. 

> How about suggesting a more positive solution, instead of throwing 
> around language like "defamation"?  Maybe, "IETF WG chairs should 
> have/use addresses that don't reject mail based on unreliable block 
> lists (for some definition of 'unreliable'), and the IETF should 
> provide a forwarding service for those chairs who cannot otherwise get 
> such an address."
> 
> I would also suggest you try to resolve the issue with SORBS, except 
> that when I tried the URL suggested, I got "ERROR: Couldn't prepare 
> statement: $dbh is (undef)".  So I guess you could question the 
> reliability of this particular service....

I have been in contact with SORBS, and with ISC.ORG. SORBS Australian
operator Matthew Sullivan says "sue me, I have no assets".  I did engage
an attorney in Australia, to review the possibility of a suit, and who
confirmed that Sullivan had no visible assets. It would cost about $50k
(US) to sue, and while Australian law provides that we can recover that,
it cannot be recovered from someone who has no assets.

ISC.ORG is the US promoter of SORBS (we got it booted from other US ISPs),
but ISC.ORG doesn't want to take a complaint. Bill Manning, of EP.NET
(ISC.ORG upstream) says he has no contract with me to accept complaints
about ISC.ORG.

Fortunately, almost no one is using SORBS, or has Av8 whitelisted.  Those 
few that have used SORBS (outside of ISC.ORG) have stopped using SORBS 
when the 130.105 listing is pointed out to them.

		--Dean



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


From ietf-admin@ietf.org  Mon May 10 17:14: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 RAA05678
	for <ietf-archive@ietf.org>; Mon, 10 May 2004 17:14: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 1BNI6C-0001Mj-6Z
	for ietf-archive@ietf.org; Mon, 10 May 2004 17:14:08 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNI5B-0000yM-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 17:13:05 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNI4C-0000bf-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 17:12:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNHQV-0005Hs-KT; Mon, 10 May 2004 16:31:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNHMr-0004Z2-9d
	for ietf@optimus.ietf.org; Mon, 10 May 2004 16:27: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 QAA01420
	for <ietf@ietf.org>; Mon, 10 May 2004 16:27:13 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNHMp-0006wB-BY
	for ietf@ietf.org; Mon, 10 May 2004 16:27:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNHLq-0006Xn-00
	for ietf@ietf.org; Mon, 10 May 2004 16:26:14 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNHKs-0005pQ-00
	for ietf@ietf.org; Mon, 10 May 2004 16:25:14 -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 i4AKNjRp028484
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 10 May 2004 16:23:46 -0400
Date: Mon, 10 May 2004 16:23:45 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: John Stracke <jstracke@centive.com>
cc: ietf@ietf.org, <dnsop@lists.uoregon.edu>
Subject: Re: Complaint on abuse of DNSOP lists
In-Reply-To: <409FD935.8020308@centive.com>
Message-ID: <Pine.LNX.4.44.0405101621260.25030-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, 10 May 2004, John Stracke wrote:

> Dean Anderson wrote:
> 
> >It seems that WG co-chair has begun to use an email address that is 
> >defaming Av8 Internet, Inc
> >
> How is it defamation if the only one that gets the message is Av8?

Av8 customers get it.  DNSOP and IETF list members have gotten it. When I
have to republish something to make a complaint then legally it is just
like Mr. Austein published it himself. Defamation Tort Law.

		--Dean


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


From exim@www1.ietf.org  Mon May 10 17:21: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 RAA06588
	for <ietf-archive@odin.ietf.org>; Mon, 10 May 2004 17:21: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 1BNI0U-0000yN-EV
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 17:08:46 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4AL8E3I003709
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 17:08:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNHQ0-0005Dl-Gk; Mon, 10 May 2004 16:30:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNHIx-0003Rp-7m
	for ietf@optimus.ietf.org; Mon, 10 May 2004 16:23: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 QAA01069
	for <ietf@ietf.org>; Mon, 10 May 2004 16:23: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 1BNHIv-0005PT-AF
	for ietf@ietf.org; Mon, 10 May 2004 16:23:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNHI5-00053D-00
	for ietf@ietf.org; Mon, 10 May 2004 16:22:22 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNHHX-0004gc-00
	for ietf@ietf.org; Mon, 10 May 2004 16:21:47 -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 i4AKLG4O028481
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 10 May 2004 16:21:16 -0400
Date: Mon, 10 May 2004 16:21:16 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Ken Raeburn <raeburn@MIT.EDU>
cc: Harald Tveit Alvestrand <harald@alvestrand.no>, <ietf@ietf.org>,
        "<dnsop@lists.uoregon.edu>" <dnsop@lists.uoregon.edu>
Subject: Re: Complaint on abuse of DNSOP lists
In-Reply-To: <FFF45958-A2B6-11D8-B627-000A95909EE2@mit.edu>
Message-ID: <Pine.LNX.4.44.0405101610410.25030-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, 10 May 2004, Ken Raeburn wrote:

> On May 10, 2004, at 14:17, Dean Anderson wrote:
> 
> > It seems that WG co-chair has begun to use an email address that is
> > defaming Av8 Internet, Inc by returning business email to users of Av8
> > Internet claiming that Av8 Internet has hijacked some address space.
> 
> That may or may not be, but since you didn't show any bounce from 
> uoregon, your claim of "abuse of DNSOP lists" in the subject line 
> appears to be unsupported.

Bounces don't have to come from Uoregon.  Mr. Austein is the WG chair.  He 
has to abide by the IETF rules, just like Uoregon (host of DNSOP)

> And I'd read the error message to suggest that perhaps Av8's net block 
> had *been* hijacked (in someone's experience, not necessarily 
> world-wide, which would be an interesting problem for globally 
> distributed block lists), not that Av8 necessarily had done it.

This isn't the case. And if it were, Av8 would make that claim, no one 
else would.

> > Av8 Internet hereby demands that the IETF immediately end this behavior
> > and halt the defamation of Av8 Internet, Inc by IETF representatives.
> > IETF representatives must use email addresses that are not configured 
> > for
> > defamation of Av8 Internet, Inc.
> 
> Yes, I'm sure that SRA was the one who submitted Av8's netblock to 
> SORBS, and set up ISC to use SORBS, as part of a secret plot to ruin 
> your reputation. </sarcasm>

This has no legal relevance. Repetition of defamation is still defamation. 

> How about suggesting a more positive solution, instead of throwing 
> around language like "defamation"?  Maybe, "IETF WG chairs should 
> have/use addresses that don't reject mail based on unreliable block 
> lists (for some definition of 'unreliable'), and the IETF should 
> provide a forwarding service for those chairs who cannot otherwise get 
> such an address."
> 
> I would also suggest you try to resolve the issue with SORBS, except 
> that when I tried the URL suggested, I got "ERROR: Couldn't prepare 
> statement: $dbh is (undef)".  So I guess you could question the 
> reliability of this particular service....

I have been in contact with SORBS, and with ISC.ORG. SORBS Australian
operator Matthew Sullivan says "sue me, I have no assets".  I did engage
an attorney in Australia, to review the possibility of a suit, and who
confirmed that Sullivan had no visible assets. It would cost about $50k
(US) to sue, and while Australian law provides that we can recover that,
it cannot be recovered from someone who has no assets.

ISC.ORG is the US promoter of SORBS (we got it booted from other US ISPs),
but ISC.ORG doesn't want to take a complaint. Bill Manning, of EP.NET
(ISC.ORG upstream) says he has no contract with me to accept complaints
about ISC.ORG.

Fortunately, almost no one is using SORBS, or has Av8 whitelisted.  Those 
few that have used SORBS (outside of ISC.ORG) have stopped using SORBS 
when the 130.105 listing is pointed out to them.

		--Dean



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



From exim@www1.ietf.org  Mon May 10 17:22: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 RAA06620
	for <ietf-archive@odin.ietf.org>; Mon, 10 May 2004 17:22: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 1BNI4H-0002T6-Gv
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 17:12:09 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4ALC9sr009222
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 17:12:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNHQV-0005Hs-KT; Mon, 10 May 2004 16:31:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNHMr-0004Z2-9d
	for ietf@optimus.ietf.org; Mon, 10 May 2004 16:27: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 QAA01420
	for <ietf@ietf.org>; Mon, 10 May 2004 16:27:13 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNHMp-0006wB-BY
	for ietf@ietf.org; Mon, 10 May 2004 16:27:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNHLq-0006Xn-00
	for ietf@ietf.org; Mon, 10 May 2004 16:26:14 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNHKs-0005pQ-00
	for ietf@ietf.org; Mon, 10 May 2004 16:25:14 -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 i4AKNjRp028484
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 10 May 2004 16:23:46 -0400
Date: Mon, 10 May 2004 16:23:45 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: John Stracke <jstracke@centive.com>
cc: ietf@ietf.org, <dnsop@lists.uoregon.edu>
Subject: Re: Complaint on abuse of DNSOP lists
In-Reply-To: <409FD935.8020308@centive.com>
Message-ID: <Pine.LNX.4.44.0405101621260.25030-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, 10 May 2004, John Stracke wrote:

> Dean Anderson wrote:
> 
> >It seems that WG co-chair has begun to use an email address that is 
> >defaming Av8 Internet, Inc
> >
> How is it defamation if the only one that gets the message is Av8?

Av8 customers get it.  DNSOP and IETF list members have gotten it. When I
have to republish something to make a complaint then legally it is just
like Mr. Austein published it himself. Defamation Tort Law.

		--Dean


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



From ietf-admin@ietf.org  Mon May 10 19:59: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 TAA17317
	for <ietf-archive@ietf.org>; Mon, 10 May 2004 19:59: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 1BNKg0-0004T0-KE
	for ietf-archive@ietf.org; Mon, 10 May 2004 19:59:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNKf0-00045z-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 19:58:15 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNKe0-0003j9-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 19:57:12 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNKSG-0003bZ-SK; Mon, 10 May 2004 19:45:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNKJn-0001py-9U
	for ietf@optimus.ietf.org; Mon, 10 May 2004 19:36:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16498
	for <ietf@ietf.org>; Mon, 10 May 2004 19:36: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 1BNKJl-0004Q8-GH
	for ietf@ietf.org; Mon, 10 May 2004 19:36:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNKIk-00045R-00
	for ietf@ietf.org; Mon, 10 May 2004 19:35:15 -0400
Received: from mercury.lcs.mit.edu ([18.26.0.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNKID-0003kx-00
	for ietf@ietf.org; Mon, 10 May 2004 19:34:41 -0400
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178)
	id DB05B86AE2; Mon, 10 May 2004 19:34:11 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: Complaint on abuse of DNSOP lists
Cc: jnc@mercury.lcs.mit.edu
Message-Id: <20040510233411.DB05B86AE2@mercury.lcs.mit.edu>
Date: Mon, 10 May 2004 19:34:11 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
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

    > From: Dean Anderson <dean@av8.com>

    >> If you look at the message, you will note that it is a bounce from the
    >> WG co-chair's _personal_ email address, directly to your email address.

    > it was a bounce to a message Mr. Austein posted on DNSOP.

I assume you mean "it was a bounce to [a reply to] a message Mr. Austein
posted on DNSOP", right? (No need to confirm, just checking.)

    > It was not private business. It was IETF business.

So? Rob's not refusing to accept *any* email *at all* from you as a person
(just from a range of addresses which are generating email he doesn't like);
and you're more than savvy enough technically to get email to him via some
other path.

He's not under any more obligation to accept email from you via whatever
channel you feel like using, no matter how onerous for him, than he is to
accept messages written on 12' long oak logs of 3' diameter.


Get a life, will you? Your constant whining and flaming is really getting
old. You're getting really close to the line at which I'd ask the Chair to
ban you from posting. Oh wait, I know what your response would be - you'd sue
us. And you seem to think the rest of the world is doing things which is
making you look bad. Here's another free clue: you're doing a far better job
of that than the rest of us could do with a decade of free time.

	Noel

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


From exim@www1.ietf.org  Mon May 10 20:00: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 UAA17463
	for <ietf-archive@odin.ietf.org>; Mon, 10 May 2004 20: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 1BNKe1-0006DY-BI
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 19:57:13 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4ANvD00023850
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 19:57:13 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNKSG-0003bZ-SK; Mon, 10 May 2004 19:45:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNKJn-0001py-9U
	for ietf@optimus.ietf.org; Mon, 10 May 2004 19:36:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16498
	for <ietf@ietf.org>; Mon, 10 May 2004 19:36: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 1BNKJl-0004Q8-GH
	for ietf@ietf.org; Mon, 10 May 2004 19:36:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNKIk-00045R-00
	for ietf@ietf.org; Mon, 10 May 2004 19:35:15 -0400
Received: from mercury.lcs.mit.edu ([18.26.0.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNKID-0003kx-00
	for ietf@ietf.org; Mon, 10 May 2004 19:34:41 -0400
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178)
	id DB05B86AE2; Mon, 10 May 2004 19:34:11 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: Complaint on abuse of DNSOP lists
Cc: jnc@mercury.lcs.mit.edu
Message-Id: <20040510233411.DB05B86AE2@mercury.lcs.mit.edu>
Date: Mon, 10 May 2004 19:34:11 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: 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>

    > From: Dean Anderson <dean@av8.com>

    >> If you look at the message, you will note that it is a bounce from the
    >> WG co-chair's _personal_ email address, directly to your email address.

    > it was a bounce to a message Mr. Austein posted on DNSOP.

I assume you mean "it was a bounce to [a reply to] a message Mr. Austein
posted on DNSOP", right? (No need to confirm, just checking.)

    > It was not private business. It was IETF business.

So? Rob's not refusing to accept *any* email *at all* from you as a person
(just from a range of addresses which are generating email he doesn't like);
and you're more than savvy enough technically to get email to him via some
other path.

He's not under any more obligation to accept email from you via whatever
channel you feel like using, no matter how onerous for him, than he is to
accept messages written on 12' long oak logs of 3' diameter.


Get a life, will you? Your constant whining and flaming is really getting
old. You're getting really close to the line at which I'd ask the Chair to
ban you from posting. Oh wait, I know what your response would be - you'd sue
us. And you seem to think the rest of the world is doing things which is
making you look bad. Here's another free clue: you're doing a far better job
of that than the rest of us could do with a decade of free time.

	Noel

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



From ietf-admin@ietf.org  Mon May 10 23:58: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 XAA29173
	for <ietf-archive@ietf.org>; Mon, 10 May 2004 23:58: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 1BNOPU-0001Po-Ou
	for ietf-archive@ietf.org; Mon, 10 May 2004 23:58:28 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNOOY-00014M-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 23:57:30 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNOO4-0000j7-00
	for ietf-archive@ietf.org; Mon, 10 May 2004 23:57:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNOCU-0001KA-Ro; Mon, 10 May 2004 23:45:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNO85-0000bJ-04
	for ietf@optimus.ietf.org; Mon, 10 May 2004 23:40:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA28504
	for <ietf@ietf.org>; Mon, 10 May 2004 23:40: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 1BNO82-0002v9-OA
	for ietf@ietf.org; Mon, 10 May 2004 23:40:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNO78-0002ZT-00
	for ietf@ietf.org; Mon, 10 May 2004 23:39:30 -0400
Received: from 151.cust40.nsw.dsl.ozemail.com.au ([203.103.119.151] helo=nosense.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNO6E-0001rK-00
	for ietf@ietf.org; Mon, 10 May 2004 23:38:35 -0400
Received: from Dupy2.nosense.org (localhost.localdomain [127.0.0.1])
	by nosense.org (Postfix) with SMTP
	id CA3A23F02A; Tue, 11 May 2004 13:08:02 +0930 (CST)
Date: Tue, 11 May 2004 13:08:02 +0930
From: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Cc: dean@av8.com, myself_rajat@yahoo.com, ietf@ietf.org
Subject: Re: Problem of blocking ICMP packets
Message-Id: <20040511130802.740c0773.ietf@130c04165a5b40404e4440445758487a.nosense.org>
In-Reply-To: <409FCE99.5050301@necom830.hpcl.titech.ac.jp>
References: <Pine.LNX.4.44.0405091926270.4953-100000@cirrus.av8.net>
	<409EE11F.9070601@necom830.hpcl.titech.ac.jp>
	<20040510130210.09ac9313.ietf@130c04165a5b40404e4440445758487a.nosense.org>
	<409FCE99.5050301@necom830.hpcl.titech.ac.jp>
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

On Tue, 11 May 2004 03:48:57 +0900
Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> wrote:

> Mark Smith;
> 
> >>>A number of commercial
> >>>products and applications do rely on PMTU to work, and will
> >>>do an PATH MTU discovery, and send the MTU sized packets
> >with>>DF (don't frag).
> >>
> >>and send packets larger than MTU expecting to receive ICMP
> >>errors in vain.
> >>
> >>Read the original mail of the thread on the reality.
> 
> > The problem identified has nothing to do with the concept or
> > typical implementations of PMTUD being broken.
> 
> Wrong.

Ok, if you think I'm wrong, what is it that is preventing PMTUD
working, as per the RFC method of operation, in this discussion ?


> 
> > RFC1192 (http://www.rfc-editor.org/rfc/rfc1191.txt) is the
> > spec for PMTUD. 
> 
> Read the RFC.

> 
> It says "To detect increases in a path's PMTU, a host
> periodically increases its assumed PMTU".

And how does the host know that it has increased the PMTU too far
? 

I'm really interested in some references to documentation or
information that has helped you form your opinion. I'm keen to
find out if my understanding of PMTUD purpose and operation is
incorrect.

Here is a summary of the references I've cited, including an
additonal one, for further information :

(a) The RFC of course. This is the reference for PMTUD operation.

(b) Radia Perlman's book, "Interconnections", 2nd Edition. Pg
185, section 8.7. There is also some discussion of fragmentation
- related to PMTUD - on page 233, section 10.4.7

and an additional one

(c) W. Richard Stevens' book, "TCP/IP Illustrated, Volume 1".
Page 340, Section 24.2


Regards,
Mark.

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


From exim@www1.ietf.org  Tue May 11 00:00:55 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 AAA29291
	for <ietf-archive@odin.ietf.org>; Tue, 11 May 2004 00:00:55 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNOO6-00039Q-1h
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 23:57:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4B3v2ct012113
	for ietf-archive@odin.ietf.org; Mon, 10 May 2004 23:57:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNOCU-0001KA-Ro; Mon, 10 May 2004 23:45:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNO85-0000bJ-04
	for ietf@optimus.ietf.org; Mon, 10 May 2004 23:40:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA28504
	for <ietf@ietf.org>; Mon, 10 May 2004 23:40: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 1BNO82-0002v9-OA
	for ietf@ietf.org; Mon, 10 May 2004 23:40:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNO78-0002ZT-00
	for ietf@ietf.org; Mon, 10 May 2004 23:39:30 -0400
Received: from 151.cust40.nsw.dsl.ozemail.com.au ([203.103.119.151] helo=nosense.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNO6E-0001rK-00
	for ietf@ietf.org; Mon, 10 May 2004 23:38:35 -0400
Received: from Dupy2.nosense.org (localhost.localdomain [127.0.0.1])
	by nosense.org (Postfix) with SMTP
	id CA3A23F02A; Tue, 11 May 2004 13:08:02 +0930 (CST)
Date: Tue, 11 May 2004 13:08:02 +0930
From: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Cc: dean@av8.com, myself_rajat@yahoo.com, ietf@ietf.org
Subject: Re: Problem of blocking ICMP packets
Message-Id: <20040511130802.740c0773.ietf@130c04165a5b40404e4440445758487a.nosense.org>
In-Reply-To: <409FCE99.5050301@necom830.hpcl.titech.ac.jp>
References: <Pine.LNX.4.44.0405091926270.4953-100000@cirrus.av8.net>
	<409EE11F.9070601@necom830.hpcl.titech.ac.jp>
	<20040510130210.09ac9313.ietf@130c04165a5b40404e4440445758487a.nosense.org>
	<409FCE99.5050301@necom830.hpcl.titech.ac.jp>
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

On Tue, 11 May 2004 03:48:57 +0900
Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> wrote:

> Mark Smith;
> 
> >>>A number of commercial
> >>>products and applications do rely on PMTU to work, and will
> >>>do an PATH MTU discovery, and send the MTU sized packets
> >with>>DF (don't frag).
> >>
> >>and send packets larger than MTU expecting to receive ICMP
> >>errors in vain.
> >>
> >>Read the original mail of the thread on the reality.
> 
> > The problem identified has nothing to do with the concept or
> > typical implementations of PMTUD being broken.
> 
> Wrong.

Ok, if you think I'm wrong, what is it that is preventing PMTUD
working, as per the RFC method of operation, in this discussion ?


> 
> > RFC1192 (http://www.rfc-editor.org/rfc/rfc1191.txt) is the
> > spec for PMTUD. 
> 
> Read the RFC.

> 
> It says "To detect increases in a path's PMTU, a host
> periodically increases its assumed PMTU".

And how does the host know that it has increased the PMTU too far
? 

I'm really interested in some references to documentation or
information that has helped you form your opinion. I'm keen to
find out if my understanding of PMTUD purpose and operation is
incorrect.

Here is a summary of the references I've cited, including an
additonal one, for further information :

(a) The RFC of course. This is the reference for PMTUD operation.

(b) Radia Perlman's book, "Interconnections", 2nd Edition. Pg
185, section 8.7. There is also some discussion of fragmentation
- related to PMTUD - on page 233, section 10.4.7

and an additional one

(c) W. Richard Stevens' book, "TCP/IP Illustrated, Volume 1".
Page 340, Section 24.2


Regards,
Mark.

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



From ietf-admin@ietf.org  Tue May 11 00:58: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 AAA01551
	for <ietf-archive@ietf.org>; Tue, 11 May 2004 00:58: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 1BNPLa-00074M-6J
	for ietf-archive@ietf.org; Tue, 11 May 2004 00:58:30 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNPKi-0006i8-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 00:57:37 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNPJp-0006M3-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 00:56:41 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNPAU-0005AY-DZ; Tue, 11 May 2004 00: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 1BNP63-0004LY-Eu
	for ietf@optimus.ietf.org; Tue, 11 May 2004 00:42:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA01047
	for <ietf@ietf.org>; Tue, 11 May 2004 00:42: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 1BNP60-0001O5-Fh
	for ietf@ietf.org; Tue, 11 May 2004 00:42:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNP52-00010v-00
	for ietf@ietf.org; Tue, 11 May 2004 00:41:24 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with smtp (Exim 4.12)
	id 1BNP3z-0000PO-00
	for ietf@ietf.org; Tue, 11 May 2004 00:40:20 -0400
Received: (qmail 15997 invoked from network); 11 May 2004 04:42:49 -0000
Received: from vaio.hpcl.titech.ac.jp (HELO necom830.hpcl.titech.ac.jp) (131.112.32.134)
  by necom830.hpcl.titech.ac.jp with SMTP; 11 May 2004 04:42:49 -0000
Message-ID: <40A05A20.3090103@necom830.hpcl.titech.ac.jp>
Date: Tue, 11 May 2004 13:44:16 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: ja, en-us, en
MIME-Version: 1.0
To: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
CC: dean@av8.com, myself_rajat@yahoo.com, ietf@ietf.org
Subject: Re: Problem of blocking ICMP packets
References: <Pine.LNX.4.44.0405091926270.4953-100000@cirrus.av8.net>	<409EE11F.9070601@necom830.hpcl.titech.ac.jp>	<20040510130210.09ac9313.ietf@130c04165a5b40404e4440445758487a.nosense.org>	<409FCE99.5050301@necom830.hpcl.titech.ac.jp> <20040511130802.740c0773.ietf@130c04165a5b40404e4440445758487a.nosense.org>
In-Reply-To: <20040511130802.740c0773.ietf@130c04165a5b40404e4440445758487a.nosense.org>
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=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Mark Smith;

> I'm keen to
> find out if my understanding of PMTUD purpose and operation is
> incorrect.

Read the RFC or my quotation of it.

						Masataka Ohta



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


From exim@www1.ietf.org  Tue May 11 00:59: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 AAA01650
	for <ietf-archive@odin.ietf.org>; Tue, 11 May 2004 00:59:52 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNPJr-0006jk-Ia
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 00:56:43 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4B4uhAs025877
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 00:56:43 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNPAU-0005AY-DZ; Tue, 11 May 2004 00: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 1BNP63-0004LY-Eu
	for ietf@optimus.ietf.org; Tue, 11 May 2004 00:42:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA01047
	for <ietf@ietf.org>; Tue, 11 May 2004 00:42: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 1BNP60-0001O5-Fh
	for ietf@ietf.org; Tue, 11 May 2004 00:42:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNP52-00010v-00
	for ietf@ietf.org; Tue, 11 May 2004 00:41:24 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with smtp (Exim 4.12)
	id 1BNP3z-0000PO-00
	for ietf@ietf.org; Tue, 11 May 2004 00:40:20 -0400
Received: (qmail 15997 invoked from network); 11 May 2004 04:42:49 -0000
Received: from vaio.hpcl.titech.ac.jp (HELO necom830.hpcl.titech.ac.jp) (131.112.32.134)
  by necom830.hpcl.titech.ac.jp with SMTP; 11 May 2004 04:42:49 -0000
Message-ID: <40A05A20.3090103@necom830.hpcl.titech.ac.jp>
Date: Tue, 11 May 2004 13:44:16 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: ja, en-us, en
MIME-Version: 1.0
To: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
CC: dean@av8.com, myself_rajat@yahoo.com, ietf@ietf.org
Subject: Re: Problem of blocking ICMP packets
References: <Pine.LNX.4.44.0405091926270.4953-100000@cirrus.av8.net>	<409EE11F.9070601@necom830.hpcl.titech.ac.jp>	<20040510130210.09ac9313.ietf@130c04165a5b40404e4440445758487a.nosense.org>	<409FCE99.5050301@necom830.hpcl.titech.ac.jp> <20040511130802.740c0773.ietf@130c04165a5b40404e4440445758487a.nosense.org>
In-Reply-To: <20040511130802.740c0773.ietf@130c04165a5b40404e4440445758487a.nosense.org>
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=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

Mark Smith;

> I'm keen to
> find out if my understanding of PMTUD purpose and operation is
> incorrect.

Read the RFC or my quotation of it.

						Masataka Ohta



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



From ietf-admin@ietf.org  Tue May 11 01:09: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 BAA02015
	for <ietf-archive@ietf.org>; Tue, 11 May 2004 01:09: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 1BNPWK-0003E7-MP
	for ietf-archive@ietf.org; Tue, 11 May 2004 01:09:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNPVL-0002pz-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 01:08:36 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNPUL-0002Sn-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 01:07:33 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNPN6-0007M7-Pn; Tue, 11 May 2004 01: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 1BNPCv-0005a4-4A
	for ietf@optimus.ietf.org; Tue, 11 May 2004 00:49: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 AAA01276
	for <ietf@ietf.org>; Tue, 11 May 2004 00:49: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 1BNPCs-0003r5-BC
	for ietf@ietf.org; Tue, 11 May 2004 00:49:30 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNPBz-0003W2-00
	for ietf@ietf.org; Tue, 11 May 2004 00:48:36 -0400
Received: from 151.cust40.nsw.dsl.ozemail.com.au ([203.103.119.151] helo=nosense.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNPBF-00031z-00
	for ietf@ietf.org; Tue, 11 May 2004 00:47:50 -0400
Received: from Dupy2.nosense.org (localhost.localdomain [127.0.0.1])
	by nosense.org (Postfix) with SMTP
	id 053AE3F02A; Tue, 11 May 2004 14:17:17 +0930 (CST)
Date: Tue, 11 May 2004 14:17:17 +0930
From: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Cc: dean@av8.com, myself_rajat@yahoo.com, ietf@ietf.org
Subject: Re: Problem of blocking ICMP packets
Message-Id: <20040511141717.3dadf2ef.ietf@130c04165a5b40404e4440445758487a.nosense.org>
In-Reply-To: <40A05A20.3090103@necom830.hpcl.titech.ac.jp>
References: <Pine.LNX.4.44.0405091926270.4953-100000@cirrus.av8.net>
	<409EE11F.9070601@necom830.hpcl.titech.ac.jp>
	<20040510130210.09ac9313.ietf@130c04165a5b40404e4440445758487a.nosense.org>
	<409FCE99.5050301@necom830.hpcl.titech.ac.jp>
	<20040511130802.740c0773.ietf@130c04165a5b40404e4440445758487a.nosense.org>
	<40A05A20.3090103@necom830.hpcl.titech.ac.jp>
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

On Tue, 11 May 2004 13:44:16 +0900
Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> wrote:

> Mark Smith;
> 
> > I'm keen to
> > find out if my understanding of PMTUD purpose and operation
> > is incorrect.
> 
> Read the RFC or my quotation of it.
> 

Ok, well, I haven't got far into it, and it seems to correspond
to what I've understood :

"2. Protocol overview

   In this memo, we describe a technique for using the Don't
Fragment   (DF) bit in the IP header to dynamically discover the
PMTU of a path.   The basic idea is that a source host initially
assumes that the PMTU   of a path is the (known) MTU of its first
hop, and sends all   datagrams on that path with the DF bit set. 
If any of the datagrams   are too large to be forwarded without
fragmentation by some router   along the path, that router will
discard them and return ICMP   Destination Unreachable messages
with a code meaning "fragmentation   needed and DF set" [7]. 
Upon receipt of such a message (henceforth   called a "Datagram
Too Big" message), the source host reduces its   assumed PMTU for
the path."

I'll continue reading, although I'm happy enough that my original
understanding was correct.


Regards,
Mark.

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


From exim@www1.ietf.org  Tue May 11 01:18: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 BAA02249
	for <ietf-archive@odin.ietf.org>; Tue, 11 May 2004 01:18: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 1BNPUO-0000et-4s
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 01:07:36 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4B57a0G002514
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 01:07:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNPN6-0007M7-Pn; Tue, 11 May 2004 01: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 1BNPCv-0005a4-4A
	for ietf@optimus.ietf.org; Tue, 11 May 2004 00:49: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 AAA01276
	for <ietf@ietf.org>; Tue, 11 May 2004 00:49: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 1BNPCs-0003r5-BC
	for ietf@ietf.org; Tue, 11 May 2004 00:49:30 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNPBz-0003W2-00
	for ietf@ietf.org; Tue, 11 May 2004 00:48:36 -0400
Received: from 151.cust40.nsw.dsl.ozemail.com.au ([203.103.119.151] helo=nosense.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNPBF-00031z-00
	for ietf@ietf.org; Tue, 11 May 2004 00:47:50 -0400
Received: from Dupy2.nosense.org (localhost.localdomain [127.0.0.1])
	by nosense.org (Postfix) with SMTP
	id 053AE3F02A; Tue, 11 May 2004 14:17:17 +0930 (CST)
Date: Tue, 11 May 2004 14:17:17 +0930
From: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Cc: dean@av8.com, myself_rajat@yahoo.com, ietf@ietf.org
Subject: Re: Problem of blocking ICMP packets
Message-Id: <20040511141717.3dadf2ef.ietf@130c04165a5b40404e4440445758487a.nosense.org>
In-Reply-To: <40A05A20.3090103@necom830.hpcl.titech.ac.jp>
References: <Pine.LNX.4.44.0405091926270.4953-100000@cirrus.av8.net>
	<409EE11F.9070601@necom830.hpcl.titech.ac.jp>
	<20040510130210.09ac9313.ietf@130c04165a5b40404e4440445758487a.nosense.org>
	<409FCE99.5050301@necom830.hpcl.titech.ac.jp>
	<20040511130802.740c0773.ietf@130c04165a5b40404e4440445758487a.nosense.org>
	<40A05A20.3090103@necom830.hpcl.titech.ac.jp>
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

On Tue, 11 May 2004 13:44:16 +0900
Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> wrote:

> Mark Smith;
> 
> > I'm keen to
> > find out if my understanding of PMTUD purpose and operation
> > is incorrect.
> 
> Read the RFC or my quotation of it.
> 

Ok, well, I haven't got far into it, and it seems to correspond
to what I've understood :

"2. Protocol overview

   In this memo, we describe a technique for using the Don't
Fragment   (DF) bit in the IP header to dynamically discover the
PMTU of a path.   The basic idea is that a source host initially
assumes that the PMTU   of a path is the (known) MTU of its first
hop, and sends all   datagrams on that path with the DF bit set. 
If any of the datagrams   are too large to be forwarded without
fragmentation by some router   along the path, that router will
discard them and return ICMP   Destination Unreachable messages
with a code meaning "fragmentation   needed and DF set" [7]. 
Upon receipt of such a message (henceforth   called a "Datagram
Too Big" message), the source host reduces its   assumed PMTU for
the path."

I'll continue reading, although I'm happy enough that my original
understanding was correct.


Regards,
Mark.

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



From ietf-admin@ietf.org  Tue May 11 01:53: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 BAA03685
	for <ietf-archive@ietf.org>; Tue, 11 May 2004 01:53: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 1BNQCr-0003MD-M3
	for ietf-archive@ietf.org; Tue, 11 May 2004 01:53:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNQC1-00030F-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 01:52:42 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNQBC-0002db-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 01:51:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNQ0m-0007dv-TV; Tue, 11 May 2004 01:41:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNPwM-0006RU-46
	for ietf@optimus.ietf.org; Tue, 11 May 2004 01:36: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 BAA03216
	for <ietf@ietf.org>; Tue, 11 May 2004 01:36: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 1BNPwG-0005Ah-Og
	for ietf@ietf.org; Tue, 11 May 2004 01:36:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNPvI-0004oZ-00
	for ietf@ietf.org; Tue, 11 May 2004 01:35:25 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with smtp (Exim 4.12)
	id 1BNPuO-0004Ta-00
	for ietf@ietf.org; Tue, 11 May 2004 01:34:29 -0400
Received: (qmail 16265 invoked from network); 11 May 2004 05:37:00 -0000
Received: from vaio.hpcl.titech.ac.jp (HELO necom830.hpcl.titech.ac.jp) (131.112.32.134)
  by necom830.hpcl.titech.ac.jp with SMTP; 11 May 2004 05:37:00 -0000
Message-ID: <40A066D2.2070100@necom830.hpcl.titech.ac.jp>
Date: Tue, 11 May 2004 14:38:26 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: ja, en-us, en
MIME-Version: 1.0
To: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
CC: dean@av8.com, myself_rajat@yahoo.com, ietf@ietf.org
Subject: Re: Problem of blocking ICMP packets
References: <Pine.LNX.4.44.0405091926270.4953-100000@cirrus.av8.net>	<409EE11F.9070601@necom830.hpcl.titech.ac.jp>	<20040510130210.09ac9313.ietf@130c04165a5b40404e4440445758487a.nosense.org>	<409FCE99.5050301@necom830.hpcl.titech.ac.jp>	<20040511130802.740c0773.ietf@130c04165a5b40404e4440445758487a.nosense.org>	<40A05A20.3090103@necom830.hpcl.titech.ac.jp> <20040511141717.3dadf2ef.ietf@130c04165a5b40404e4440445758487a.nosense.org>
In-Reply-To: <20040511141717.3dadf2ef.ietf@130c04165a5b40404e4440445758487a.nosense.org>
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=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Mark Smith;

> I'll continue reading, although I'm happy enough that my original
> understanding was correct.

Let's agree that you are as correct as PMTUD.

If you have further comments, do so offline.

					Masataka Ohta



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


From exim@www1.ietf.org  Tue May 11 01:55: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 BAA03797
	for <ietf-archive@odin.ietf.org>; Tue, 11 May 2004 01:55: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 1BNQBF-0001B6-7J
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 01:51:58 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4B5prAN004350
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 01:51:53 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNQ0m-0007dv-TV; Tue, 11 May 2004 01:41:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNPwM-0006RU-46
	for ietf@optimus.ietf.org; Tue, 11 May 2004 01:36: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 BAA03216
	for <ietf@ietf.org>; Tue, 11 May 2004 01:36: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 1BNPwG-0005Ah-Og
	for ietf@ietf.org; Tue, 11 May 2004 01:36:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNPvI-0004oZ-00
	for ietf@ietf.org; Tue, 11 May 2004 01:35:25 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx with smtp (Exim 4.12)
	id 1BNPuO-0004Ta-00
	for ietf@ietf.org; Tue, 11 May 2004 01:34:29 -0400
Received: (qmail 16265 invoked from network); 11 May 2004 05:37:00 -0000
Received: from vaio.hpcl.titech.ac.jp (HELO necom830.hpcl.titech.ac.jp) (131.112.32.134)
  by necom830.hpcl.titech.ac.jp with SMTP; 11 May 2004 05:37:00 -0000
Message-ID: <40A066D2.2070100@necom830.hpcl.titech.ac.jp>
Date: Tue, 11 May 2004 14:38:26 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: ja, en-us, en
MIME-Version: 1.0
To: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
CC: dean@av8.com, myself_rajat@yahoo.com, ietf@ietf.org
Subject: Re: Problem of blocking ICMP packets
References: <Pine.LNX.4.44.0405091926270.4953-100000@cirrus.av8.net>	<409EE11F.9070601@necom830.hpcl.titech.ac.jp>	<20040510130210.09ac9313.ietf@130c04165a5b40404e4440445758487a.nosense.org>	<409FCE99.5050301@necom830.hpcl.titech.ac.jp>	<20040511130802.740c0773.ietf@130c04165a5b40404e4440445758487a.nosense.org>	<40A05A20.3090103@necom830.hpcl.titech.ac.jp> <20040511141717.3dadf2ef.ietf@130c04165a5b40404e4440445758487a.nosense.org>
In-Reply-To: <20040511141717.3dadf2ef.ietf@130c04165a5b40404e4440445758487a.nosense.org>
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=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

Mark Smith;

> I'll continue reading, although I'm happy enough that my original
> understanding was correct.

Let's agree that you are as correct as PMTUD.

If you have further comments, do so offline.

					Masataka Ohta



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



From ietf-admin@ietf.org  Tue May 11 03:31: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 DAA08356
	for <ietf-archive@ietf.org>; Tue, 11 May 2004 03:31: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 1BNRjK-00006V-9J
	for ietf-archive@ietf.org; Tue, 11 May 2004 03:31:10 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNRiD-0007UY-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 03:30:02 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNRhV-00074x-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 03:29:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNRQu-0000Y6-8E; Tue, 11 May 2004 03:12:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNRHi-0006dz-MQ
	for ietf@optimus.ietf.org; Tue, 11 May 2004 03:02: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 DAA07243
	for <ietf@ietf.org>; Tue, 11 May 2004 03:02:34 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNRHe-0005S5-GY
	for ietf@ietf.org; Tue, 11 May 2004 03:02:34 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNRGk-00056f-00
	for ietf@ietf.org; Tue, 11 May 2004 03:01:39 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNRGK-0004kx-00
	for ietf@ietf.org; Tue, 11 May 2004 03:01:12 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 194F961C0F; Tue, 11 May 2004 09:00:43 +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 10427-06; Tue, 11 May 2004 09:00:42 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 0010D61B89; Tue, 11 May 2004 09:00:25 +0200 (CEST)
Date: Mon, 10 May 2004 13:53:25 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Dean Anderson <dean@av8.com>
Cc: ietf@ietf.org, dnsop@lists.uoregon.edu
Subject: Re: Complaint on abuse of DNSOP lists
Message-ID: <10224401.1084197205@localhost>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
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.3 required=5.0 tests=AWL,DATE_IN_PAST_06_12 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Dean,

third time same complaint, third time same answer.

No.

A WG chair is expected to read mail coming from the working group list. 
What he does with copies that go directly to him is his own business.

And as I have told you on the previous two instances of this complaint: 
Personal mail to you, including bounce messages, is not someone defaming 
you in the IETF, even when you choose to make it public.

                    Harald

--On 10. mai 2004 14:17 -0400 Dean Anderson <dean@av8.com> wrote:

> Point of order, please
>
> It seems that WG co-chair has begun to use an email address that is
> defaming Av8 Internet, Inc by returning business email to users of Av8
> Internet claiming that Av8 Internet has hijacked some address space.
>
> Av8 Internet hereby demands that the IETF immediately end this behavior
> and halt the defamation of Av8 Internet, Inc by IETF representatives.
> IETF representatives must use email addresses that are not configured for
> defamation of Av8 Internet, Inc.
>
> Dean Anderson
> Av8 Internet, Inc
>
>
>
> ---------- Forwarded message ----------
> Date: Sun, 9 May 2004 20:17:23 -0400
> From: Mail Delivery Subsystem <MAILER-DAEMON@cirrus.av8.net>
> To: dean@av8.com
> Subject: Returned mail: see transcript for details
>
> The original message was received at Sun, 9 May 2004 20:17:14 -0400
> from cirrus.av8.net [130.105.36.66]
>
>    ----- The following addresses had permanent fatal errors -----
> <sra@isc.org>
>     (reason: 553 Service unavailable; Client host [130.105.36.66] blocked
> using dnsbl.sorbs.net; Hijacked/Disused Netblock See:
> http://www.dnsbl.sorbs.net/cgi-bin/lookup?IP=130.105.36.66)
>
>    ----- Transcript of session follows -----
> ... while talking to mx-1.isc.org.:
>>>> DATA
> <<< 553 Service unavailable; Client host [130.105.36.66] blocked using
> dnsbl.sorbs.net; Hijacked/Disused Netblock See:
> http://www.dnsbl.sorbs.net/cgi-bin/lookup?IP=130.105.36.66 550 5.1.1
> <sra@isc.org>... User unknown
> <<< 554 Error: no valid recipients
>



 

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


From ietf-admin@ietf.org  Tue May 11 03:32:49 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA08553
	for <ietf-archive@ietf.org>; Tue, 11 May 2004 03:32:49 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNRku-0000ty-QK
	for ietf-archive@ietf.org; Tue, 11 May 2004 03:32:48 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNRk1-0000V7-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 03:31:54 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNRjD-00005Z-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 03:31:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNRQy-0000Yo-7K; Tue, 11 May 2004 03:12:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNRIs-0006p6-Qi
	for ietf@optimus.ietf.org; Tue, 11 May 2004 03:03: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 DAA07294
	for <ietf@ietf.org>; Tue, 11 May 2004 03:03: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 1BNRIo-0005qK-SY
	for ietf@ietf.org; Tue, 11 May 2004 03:03:46 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNRHq-0005Th-00
	for ietf@ietf.org; Tue, 11 May 2004 03:02:46 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNRH9-00055t-00; Tue, 11 May 2004 03:02:03 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id E095161C0F; Tue, 11 May 2004 09:01:34 +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 10427-09; Tue, 11 May 2004 09:01:34 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id A2B3961B89; Tue, 11 May 2004 09:01:19 +0200 (CEST)
Date: Mon, 10 May 2004 15:28:18 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Scott Bradner <sob@harvard.edu>, iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: 'The IESG and RFC Editor documents: Procedures' to
 BCP
Message-ID: <15917027.1084202898@localhost>
In-Reply-To: <20040510133351.507B51E6E7C@newdev.harvard.edu>
References: <20040510133351.507B51E6E7C@newdev.harvard.edu>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
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.3 required=5.0 tests=AWL,DATE_IN_PAST_06_12 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit



--On 10. mai 2004 09:33 -0400 Scott Bradner <sob@harvard.edu> wrote:

> this misses one of the outcomes listed in RFC 2026 - specifically (quoting
> from 2026):
> 	"the IESG recommends that the document be brought within the
> 	IETF and progressed within the IETF context"
>
> this path has been used from time to time and I think it is a valuable
> option - I'd suggest that it be added as a 6th response

actually it was more-or-less intentionally left out.
There are 3 scenarios to consider, I think:

- There is a valid reason why it's impossible to do this work outside of 
the IETF. Response 4 or 5 should be returned, explaining why.

- The work can be done in the IETF, and the author agrees. The author 
should (IMHO) be the one to inform the RFC Editor that he/she is dropping 
the request to publish outside IETF review.

- The work can be done in the IETF (or rather, this draft could be the 
basis for further work in the IETF), but the author wants it published 
independently anyway. In this case, I think it is good for the health of 
the RFC series AND for the time budget of the IESG that the IESG does NOT 
say "should be brought in" to the RFC Editor; the IESG, having failed to 
convince the author, should just live with the RFC Editor's judgment on 
publication.

My opinion only.....

                      Harald





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


From exim@www1.ietf.org  Tue May 11 03:36: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 DAA08723
	for <ietf-archive@odin.ietf.org>; Tue, 11 May 2004 03:36: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 1BNRhV-0003zz-K1
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 03:29:17 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4B7THwM015354
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 03:29:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNRQu-0000Y6-8E; Tue, 11 May 2004 03:12:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNRHi-0006dz-MQ
	for ietf@optimus.ietf.org; Tue, 11 May 2004 03:02: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 DAA07243
	for <ietf@ietf.org>; Tue, 11 May 2004 03:02:34 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNRHe-0005S5-GY
	for ietf@ietf.org; Tue, 11 May 2004 03:02:34 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNRGk-00056f-00
	for ietf@ietf.org; Tue, 11 May 2004 03:01:39 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNRGK-0004kx-00
	for ietf@ietf.org; Tue, 11 May 2004 03:01:12 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 194F961C0F; Tue, 11 May 2004 09:00:43 +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 10427-06; Tue, 11 May 2004 09:00:42 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 0010D61B89; Tue, 11 May 2004 09:00:25 +0200 (CEST)
Date: Mon, 10 May 2004 13:53:25 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Dean Anderson <dean@av8.com>
Cc: ietf@ietf.org, dnsop@lists.uoregon.edu
Subject: Re: Complaint on abuse of DNSOP lists
Message-ID: <10224401.1084197205@localhost>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-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.3 required=5.0 tests=AWL,DATE_IN_PAST_06_12 
	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,

third time same complaint, third time same answer.

No.

A WG chair is expected to read mail coming from the working group list. 
What he does with copies that go directly to him is his own business.

And as I have told you on the previous two instances of this complaint: 
Personal mail to you, including bounce messages, is not someone defaming 
you in the IETF, even when you choose to make it public.

                    Harald

--On 10. mai 2004 14:17 -0400 Dean Anderson <dean@av8.com> wrote:

> Point of order, please
>
> It seems that WG co-chair has begun to use an email address that is
> defaming Av8 Internet, Inc by returning business email to users of Av8
> Internet claiming that Av8 Internet has hijacked some address space.
>
> Av8 Internet hereby demands that the IETF immediately end this behavior
> and halt the defamation of Av8 Internet, Inc by IETF representatives.
> IETF representatives must use email addresses that are not configured for
> defamation of Av8 Internet, Inc.
>
> Dean Anderson
> Av8 Internet, Inc
>
>
>
> ---------- Forwarded message ----------
> Date: Sun, 9 May 2004 20:17:23 -0400
> From: Mail Delivery Subsystem <MAILER-DAEMON@cirrus.av8.net>
> To: dean@av8.com
> Subject: Returned mail: see transcript for details
>
> The original message was received at Sun, 9 May 2004 20:17:14 -0400
> from cirrus.av8.net [130.105.36.66]
>
>    ----- The following addresses had permanent fatal errors -----
> <sra@isc.org>
>     (reason: 553 Service unavailable; Client host [130.105.36.66] blocked
> using dnsbl.sorbs.net; Hijacked/Disused Netblock See:
> http://www.dnsbl.sorbs.net/cgi-bin/lookup?IP=130.105.36.66)
>
>    ----- Transcript of session follows -----
> ... while talking to mx-1.isc.org.:
>>>> DATA
> <<< 553 Service unavailable; Client host [130.105.36.66] blocked using
> dnsbl.sorbs.net; Hijacked/Disused Netblock See:
> http://www.dnsbl.sorbs.net/cgi-bin/lookup?IP=130.105.36.66 550 5.1.1
> <sra@isc.org>... User unknown
> <<< 554 Error: no valid recipients
>



 

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



From ietf-admin@ietf.org  Tue May 11 03:49: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 DAA09241
	for <ietf-archive@ietf.org>; Tue, 11 May 2004 03:49: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 1BNS1D-0007Gb-9U
	for ietf-archive@ietf.org; Tue, 11 May 2004 03:49:39 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNS09-0006qX-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 03:48:34 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNRzC-0006Sa-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 03:47:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNRlM-0005Hc-60; Tue, 11 May 2004 03:33:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNRZD-00020x-R7
	for ietf@optimus.ietf.org; Tue, 11 May 2004 03:20: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 DAA07853
	for <ietf@ietf.org>; Tue, 11 May 2004 03:20: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 1BNRZB-00046g-Al
	for ietf@ietf.org; Tue, 11 May 2004 03:20:41 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNRYA-0003kd-00
	for ietf@ietf.org; Tue, 11 May 2004 03:19:39 -0400
Received: from weasel.corp.ntrg.com ([207.65.71.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNRXZ-0003N9-00
	for ietf@ietf.org; Tue, 11 May 2004 03:19:01 -0400
Received: from [207.65.71.20] (account ehall HELO ehsco.com)
  by weasel.corp.ntrg.com (CommuniGate Pro SMTP 4.1.8)
  with ESMTP-TLS id 80138; Tue, 11 May 2004 02:18:31 -0500
Message-ID: <40A07E47.4060906@ehsco.com>
Date: Tue, 11 May 2004 02:18:31 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Paul Hoffman / VPNC <paul.hoffman@vpnc.org>
CC: IETF <ietf@ietf.org>
Subject: Re: Not sure if this is the right place for this
References: <DD72EEC3-A1E7-11D8-8626-003065F939FE@rudd.cc> <Pine.LNX.4.58.0405100019050.1405@perp.cac.washington.edu> <409F93F0.5060300@ehsco.com> <p06100532bcc54f129dec@[10.20.30.249]>
In-Reply-To: <p06100532bcc54f129dec@[10.20.30.249]>
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


On 5/10/2004 10:31 AM, Paul Hoffman / VPNC wrote:

> At 9:38 AM -0500 5/10/04, Eric A. Hall wrote:

>> Using an encrypted port just means an attack can only produce 
>> failure, rather than inducing fallback.
>> 
>> Unless that's wrong for some reason, I'd say that a "secure ports 
>> policy" actually is more secure.
> 
> In many cases, a client for a "secure ports policy" protocol will fall 
> back to the insecure port instead of telling the user "you can't 
> communicate". That's not true for HTTPS, but it is true for secure POP,
>  secure SMTP, and so on.

This is a fair enough point, and I should have accounted for it, but I
don't think its absence weakens the merits of the first point any.

I'm not even sure they are similar arguments. I mean, the argument against
SSL is that *if* an SSL connection is blocked, and *if* an alternative
clear channel exists, and *if* that channel accepts clear-text logins, and
*if* the client fallsback through all of that, then the session will be
exposed. I'll grant that it's easy enough to interfere with somebody
establishing a session, and that there's a measurable percentage of
services that maintain clear channel alternatives, and that PLAIN/LOGIN
are still the only things that work everywhere, and that there are
probably clients which fallback invisibly. I can also argue some of those
points to some degree -- that people who have setup SSL versions are
likely to have eliminated access to the clear channel, for example -- so
instead of any of those things being certainties, we should agree that
this is a question of overlapping probabilities.

On the other hand, STARTTLS *requires* a clear channel that the client
MUST *already* be using. So whereas the attack on SSL *might* succeed in
putting the client in touch with an unencrypted service, TLS is
*guaranteed* to be using such a service already anyway. The only question
is whether or not a decipherable login can be used, which is a probability
mask that also applies to the SSL scenario.

Given the collection of probabilities, therefore, starting with an SSL
channel and refusing connections to a backup clear channel eliminates most
of the probability from the MitM attack model. Conversely, those
attributes are prerequisites to the very existence of TLS. Ergo, TLS is
weaker against this particular vector, by design.

I don't think it really matters given the other problems (see below).

> A man-in-the-middle can more easily block the secure port than he/she 
> can elide the STARTTLS messing in the client's start-up.

That's true.

On the other hand, channeling clients through a proxy is easy, especially
if they are on a foreign network. The client can be tricked into using a
different host via DNS attacks, or can simply be routed through proxies,
NATs, firewalls, or any number of 'transparent' proxies that can be easily
deployed. STARTTLS can be disabled by any of these, using a two-bit attack
(literally: borrow one bit from the T and hand it to the S, causing the
service to be advertised as "TSARTTLS" -- I've seen worse than that from
unintentional bugs and intentional features alike).

> Any client that is willing to back down to non-secure mode is 
> susceptible to a MITM attack, regardless of the protocol.

agreed on that


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

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


From exim@www1.ietf.org  Tue May 11 04:00: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 EAA09699
	for <ietf-archive@odin.ietf.org>; Tue, 11 May 2004 04:00: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 1BNRzD-0000aw-4k
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 03:47:35 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4B7lZT7002287
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 03:47:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNRlM-0005Hc-60; Tue, 11 May 2004 03:33:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNRZD-00020x-R7
	for ietf@optimus.ietf.org; Tue, 11 May 2004 03:20: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 DAA07853
	for <ietf@ietf.org>; Tue, 11 May 2004 03:20: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 1BNRZB-00046g-Al
	for ietf@ietf.org; Tue, 11 May 2004 03:20:41 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNRYA-0003kd-00
	for ietf@ietf.org; Tue, 11 May 2004 03:19:39 -0400
Received: from weasel.corp.ntrg.com ([207.65.71.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNRXZ-0003N9-00
	for ietf@ietf.org; Tue, 11 May 2004 03:19:01 -0400
Received: from [207.65.71.20] (account ehall HELO ehsco.com)
  by weasel.corp.ntrg.com (CommuniGate Pro SMTP 4.1.8)
  with ESMTP-TLS id 80138; Tue, 11 May 2004 02:18:31 -0500
Message-ID: <40A07E47.4060906@ehsco.com>
Date: Tue, 11 May 2004 02:18:31 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Paul Hoffman / VPNC <paul.hoffman@vpnc.org>
CC: IETF <ietf@ietf.org>
Subject: Re: Not sure if this is the right place for this
References: <DD72EEC3-A1E7-11D8-8626-003065F939FE@rudd.cc> <Pine.LNX.4.58.0405100019050.1405@perp.cac.washington.edu> <409F93F0.5060300@ehsco.com> <p06100532bcc54f129dec@[10.20.30.249]>
In-Reply-To: <p06100532bcc54f129dec@[10.20.30.249]>
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


On 5/10/2004 10:31 AM, Paul Hoffman / VPNC wrote:

> At 9:38 AM -0500 5/10/04, Eric A. Hall wrote:

>> Using an encrypted port just means an attack can only produce 
>> failure, rather than inducing fallback.
>> 
>> Unless that's wrong for some reason, I'd say that a "secure ports 
>> policy" actually is more secure.
> 
> In many cases, a client for a "secure ports policy" protocol will fall 
> back to the insecure port instead of telling the user "you can't 
> communicate". That's not true for HTTPS, but it is true for secure POP,
>  secure SMTP, and so on.

This is a fair enough point, and I should have accounted for it, but I
don't think its absence weakens the merits of the first point any.

I'm not even sure they are similar arguments. I mean, the argument against
SSL is that *if* an SSL connection is blocked, and *if* an alternative
clear channel exists, and *if* that channel accepts clear-text logins, and
*if* the client fallsback through all of that, then the session will be
exposed. I'll grant that it's easy enough to interfere with somebody
establishing a session, and that there's a measurable percentage of
services that maintain clear channel alternatives, and that PLAIN/LOGIN
are still the only things that work everywhere, and that there are
probably clients which fallback invisibly. I can also argue some of those
points to some degree -- that people who have setup SSL versions are
likely to have eliminated access to the clear channel, for example -- so
instead of any of those things being certainties, we should agree that
this is a question of overlapping probabilities.

On the other hand, STARTTLS *requires* a clear channel that the client
MUST *already* be using. So whereas the attack on SSL *might* succeed in
putting the client in touch with an unencrypted service, TLS is
*guaranteed* to be using such a service already anyway. The only question
is whether or not a decipherable login can be used, which is a probability
mask that also applies to the SSL scenario.

Given the collection of probabilities, therefore, starting with an SSL
channel and refusing connections to a backup clear channel eliminates most
of the probability from the MitM attack model. Conversely, those
attributes are prerequisites to the very existence of TLS. Ergo, TLS is
weaker against this particular vector, by design.

I don't think it really matters given the other problems (see below).

> A man-in-the-middle can more easily block the secure port than he/she 
> can elide the STARTTLS messing in the client's start-up.

That's true.

On the other hand, channeling clients through a proxy is easy, especially
if they are on a foreign network. The client can be tricked into using a
different host via DNS attacks, or can simply be routed through proxies,
NATs, firewalls, or any number of 'transparent' proxies that can be easily
deployed. STARTTLS can be disabled by any of these, using a two-bit attack
(literally: borrow one bit from the T and hand it to the S, causing the
service to be advertised as "TSARTTLS" -- I've seen worse than that from
unintentional bugs and intentional features alike).

> Any client that is willing to back down to non-secure mode is 
> susceptible to a MITM attack, regardless of the protocol.

agreed on that


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

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



From ietf-admin@ietf.org  Tue May 11 04:24: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 EAA11437
	for <ietf-archive@ietf.org>; Tue, 11 May 2004 04:24: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 1BNSZ2-0005H7-Pk
	for ietf-archive@ietf.org; Tue, 11 May 2004 04:24:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNSY6-0004uk-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 04:23:39 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNSXL-0004Yy-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 04:22:51 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNSM6-0006sH-2Z; Tue, 11 May 2004 04:11:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNSA6-0002p4-Dn
	for ietf@optimus.ietf.org; Tue, 11 May 2004 03:58: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 DAA09633
	for <ietf@ietf.org>; Tue, 11 May 2004 03:58:48 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNSA3-0002pY-QF
	for ietf@ietf.org; Tue, 11 May 2004 03:58:47 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNS93-0002TK-00
	for ietf@ietf.org; Tue, 11 May 2004 03:57:46 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNS8W-00026d-00
	for ietf@ietf.org; Tue, 11 May 2004 03:57:12 -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 i4B7uo1C005418;
	Tue, 11 May 2004 09:56:50 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <20040511141717.3dadf2ef.ietf@130c04165a5b40404e4440445758487a.nosense.org>
References: <Pine.LNX.4.44.0405091926270.4953-100000@cirrus.av8.net> <409EE11F.9070601@necom830.hpcl.titech.ac.jp> <20040510130210.09ac9313.ietf@130c04165a5b40404e4440445758487a.nosense.org> <409FCE99.5050301@necom830.hpcl.titech.ac.jp> <20040511130802.740c0773.ietf@130c04165a5b40404e4440445758487a.nosense.org> <40A05A20.3090103@necom830.hpcl.titech.ac.jp> <20040511141717.3dadf2ef.ietf@130c04165a5b40404e4440445758487a.nosense.org>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <C8A67D48-A320-11D8-B6DD-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: "'Internet Engineering Task Force'" <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: Problem of blocking ICMP packets
Date: Tue, 11 May 2004 09:57:00 +0200
To: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
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 11-mei-04, at 6:47, Mark Smith wrote:

> The basic idea is that a source host initially
> assumes that the PMTU   of a path is the (known) MTU of its first
> hop, and sends all   datagrams on that path with the DF bit set.
                ^^^^^
And this is where all the problems start. This flies directly in the 
face of the the robustness principle. If the host would just set the DF 
bit in one in 1000, one in 100 or one in 10 packets, we wouldn't be in 
this mess.

Note that the RFC doesn't say the DF bit must be set on ALL packets. 
But then, it also doesn't say this shouldn't be done either.


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


From exim@www1.ietf.org  Tue May 11 04:38: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 EAA11951
	for <ietf-archive@odin.ietf.org>; Tue, 11 May 2004 04:38: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 1BNSXR-00024g-7g
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 04:22:58 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4B8Mvk5007718
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 04:22:57 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNSM6-0006sH-2Z; Tue, 11 May 2004 04:11:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNSA6-0002p4-Dn
	for ietf@optimus.ietf.org; Tue, 11 May 2004 03:58: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 DAA09633
	for <ietf@ietf.org>; Tue, 11 May 2004 03:58:48 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNSA3-0002pY-QF
	for ietf@ietf.org; Tue, 11 May 2004 03:58:47 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNS93-0002TK-00
	for ietf@ietf.org; Tue, 11 May 2004 03:57:46 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNS8W-00026d-00
	for ietf@ietf.org; Tue, 11 May 2004 03:57:12 -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 i4B7uo1C005418;
	Tue, 11 May 2004 09:56:50 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <20040511141717.3dadf2ef.ietf@130c04165a5b40404e4440445758487a.nosense.org>
References: <Pine.LNX.4.44.0405091926270.4953-100000@cirrus.av8.net> <409EE11F.9070601@necom830.hpcl.titech.ac.jp> <20040510130210.09ac9313.ietf@130c04165a5b40404e4440445758487a.nosense.org> <409FCE99.5050301@necom830.hpcl.titech.ac.jp> <20040511130802.740c0773.ietf@130c04165a5b40404e4440445758487a.nosense.org> <40A05A20.3090103@necom830.hpcl.titech.ac.jp> <20040511141717.3dadf2ef.ietf@130c04165a5b40404e4440445758487a.nosense.org>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <C8A67D48-A320-11D8-B6DD-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: "'Internet Engineering Task Force'" <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: Problem of blocking ICMP packets
Date: Tue, 11 May 2004 09:57:00 +0200
To: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
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 11-mei-04, at 6:47, Mark Smith wrote:

> The basic idea is that a source host initially
> assumes that the PMTU   of a path is the (known) MTU of its first
> hop, and sends all   datagrams on that path with the DF bit set.
                ^^^^^
And this is where all the problems start. This flies directly in the 
face of the the robustness principle. If the host would just set the DF 
bit in one in 1000, one in 100 or one in 10 packets, we wouldn't be in 
this mess.

Note that the RFC doesn't say the DF bit must be set on ALL packets. 
But then, it also doesn't say this shouldn't be done either.


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



From ietf-admin@ietf.org  Tue May 11 04:53: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 EAA12873
	for <ietf-archive@ietf.org>; Tue, 11 May 2004 04:53: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 1BNT1N-0000Nu-4M
	for ietf-archive@ietf.org; Tue, 11 May 2004 04:53:53 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNT0Q-0007mW-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 04:52:55 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNSzn-0007Oe-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 04:52:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNSm4-00052y-8x; Tue, 11 May 2004 04:38:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNSSL-00017G-1X
	for ietf@optimus.ietf.org; Tue, 11 May 2004 04:17:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA10806
	for <ietf@ietf.org>; Tue, 11 May 2004 04:17: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 1BNSSH-0002RT-7J
	for ietf@ietf.org; Tue, 11 May 2004 04:17:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNSRO-00025J-00
	for ietf@ietf.org; Tue, 11 May 2004 04:16:43 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNSQe-0001ik-00; Tue, 11 May 2004 04:15:56 -0400
Received: from [127.0.0.1] (helo=localhost)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1BNSQb-000KMD-00; Tue, 11 May 2004 03:15:53 -0500
Date: Tue, 11 May 2004 04:15:50 -0400
From: John C Klensin <john-ietf@jck.com>
To: Pete Resnick <presnick@qualcomm.com>
cc: Scott Bradner <sob@harvard.edu>, iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: 'The IESG and RFC Editor documents: 
 Procedures' to BCP
Message-ID: <88B65B68142F602B00CFA81C@[10.0.0.77]>
In-Reply-To: <p0610110dbcc54d6b507d@[216.43.25.67]>
References: <20040510133351.507B51E6E7C@newdev.harvard.edu>
 <98F68B8BD0BF769925C874EE@localhost>
 <p0610110dbcc54d6b507d@[216.43.25.67]>
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

Pete,

I thought I was describing the status quo and what is currently 
happening.   Unless the IAB has handed off that responsibility 
to the IESG in the last two years (in which case the community 
wasn't told), the IESG's having any discussion at all with the 
RFC Editor about an IAB document -- what is in that category, 
how they are handled, etc.-- is because the IAB asks for that 
discussion.  It presumably also occurs in a three-way 
environment, even if the IAB decides to be silent about 
particular aspects of the conversation.

     john

--On Monday, May 10, 2004 10:27 AM -0500 Pete Resnick 
<presnick@qualcomm.com> wrote:

> On 5/10/04 at 10:54 AM -0400, John C Klensin wrote:
>
>> --On Monday, May 10, 2004 9:33 AM -0400 Scott Bradner
>> <sob@harvard.edu> wrote:
>>
>>> looks good to me - one suggestion of clearer language and a
>>> potential addition
>>>
>>>>   o  Documents for which special rules exist, including IAB
>>>> documents and April 1st RFCs, and republication of
>>>> documents from  other SDOs - the IESG and the RFC Editor
>>>> keep a running dialogue  on which documents these are
>>>
>>> awkward wording - maybe you want to say
>>>
>>>    o  The IESG and the RFC Editor keep a running dialogue on
>>>    which  documents require special rules (for example, IAB
>>> documents, April  1st RFCs, and republication of documents
>>> from other SDOs)
>>
>> Scott, while I agree that the current language is not
>> optimal, I  don't think the above is the right fix.   The
>> whole point of the  agreements about publication of IAB
>> documents is that the RFC Editor  reports, from an overall
>> policy and strategy standpoint, with the  IAB.  Turning that
>> situation into "the IESG and the RFC Editor keep  a running
>> dialogue" rather dramatically revises (or confuses) that
>> situation.
>
> John, the paragraph which Scott aims to fix is in the section
> which describes "what is currently happening". And, indeed, I
> believe it is true that the current state of affairs is that
> the IESG and the RFC Editor *do* keep a running dialogue about
> out-of-the-ordinary documents which may or may not need IESG
> review (where republication of certain SDO documents do --
> because of liaison agreements -- and April 1st RFCs do not, as
> far as I know).
>
> Perhaps this would be better stated as:
>
> o  The IESG and the RFC Editor keep a running dialogue on
> which documents require special rules (for example, IAB
> informational documents and April 1st RFCs never require IESG
> review, whereas certain republication of documents from other
> SDOs do because of liaison agreements)
>
> (assuming that captures what Harald, and Scott, intended in
> their attempts).





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


From exim@www1.ietf.org  Tue May 11 05:08:00 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 FAA13602
	for <ietf-archive@odin.ietf.org>; Tue, 11 May 2004 05:08: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 1BNSzp-00007H-Eu
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 04:52:18 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4B8qHxp000414
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 04:52:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNSm4-00052y-8x; Tue, 11 May 2004 04:38:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNSSL-00017G-1X
	for ietf@optimus.ietf.org; Tue, 11 May 2004 04:17:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA10806
	for <ietf@ietf.org>; Tue, 11 May 2004 04:17: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 1BNSSH-0002RT-7J
	for ietf@ietf.org; Tue, 11 May 2004 04:17:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNSRO-00025J-00
	for ietf@ietf.org; Tue, 11 May 2004 04:16:43 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNSQe-0001ik-00; Tue, 11 May 2004 04:15:56 -0400
Received: from [127.0.0.1] (helo=localhost)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1BNSQb-000KMD-00; Tue, 11 May 2004 03:15:53 -0500
Date: Tue, 11 May 2004 04:15:50 -0400
From: John C Klensin <john-ietf@jck.com>
To: Pete Resnick <presnick@qualcomm.com>
cc: Scott Bradner <sob@harvard.edu>, iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: 'The IESG and RFC Editor documents: 
 Procedures' to BCP
Message-ID: <88B65B68142F602B00CFA81C@[10.0.0.77]>
In-Reply-To: <p0610110dbcc54d6b507d@[216.43.25.67]>
References: <20040510133351.507B51E6E7C@newdev.harvard.edu>
 <98F68B8BD0BF769925C874EE@localhost>
 <p0610110dbcc54d6b507d@[216.43.25.67]>
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

Pete,

I thought I was describing the status quo and what is currently 
happening.   Unless the IAB has handed off that responsibility 
to the IESG in the last two years (in which case the community 
wasn't told), the IESG's having any discussion at all with the 
RFC Editor about an IAB document -- what is in that category, 
how they are handled, etc.-- is because the IAB asks for that 
discussion.  It presumably also occurs in a three-way 
environment, even if the IAB decides to be silent about 
particular aspects of the conversation.

     john

--On Monday, May 10, 2004 10:27 AM -0500 Pete Resnick 
<presnick@qualcomm.com> wrote:

> On 5/10/04 at 10:54 AM -0400, John C Klensin wrote:
>
>> --On Monday, May 10, 2004 9:33 AM -0400 Scott Bradner
>> <sob@harvard.edu> wrote:
>>
>>> looks good to me - one suggestion of clearer language and a
>>> potential addition
>>>
>>>>   o  Documents for which special rules exist, including IAB
>>>> documents and April 1st RFCs, and republication of
>>>> documents from  other SDOs - the IESG and the RFC Editor
>>>> keep a running dialogue  on which documents these are
>>>
>>> awkward wording - maybe you want to say
>>>
>>>    o  The IESG and the RFC Editor keep a running dialogue on
>>>    which  documents require special rules (for example, IAB
>>> documents, April  1st RFCs, and republication of documents
>>> from other SDOs)
>>
>> Scott, while I agree that the current language is not
>> optimal, I  don't think the above is the right fix.   The
>> whole point of the  agreements about publication of IAB
>> documents is that the RFC Editor  reports, from an overall
>> policy and strategy standpoint, with the  IAB.  Turning that
>> situation into "the IESG and the RFC Editor keep  a running
>> dialogue" rather dramatically revises (or confuses) that
>> situation.
>
> John, the paragraph which Scott aims to fix is in the section
> which describes "what is currently happening". And, indeed, I
> believe it is true that the current state of affairs is that
> the IESG and the RFC Editor *do* keep a running dialogue about
> out-of-the-ordinary documents which may or may not need IESG
> review (where republication of certain SDO documents do --
> because of liaison agreements -- and April 1st RFCs do not, as
> far as I know).
>
> Perhaps this would be better stated as:
>
> o  The IESG and the RFC Editor keep a running dialogue on
> which documents require special rules (for example, IAB
> informational documents and April 1st RFCs never require IESG
> review, whereas certain republication of documents from other
> SDOs do because of liaison agreements)
>
> (assuming that captures what Harald, and Scott, intended in
> their attempts).





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



From exim@www1.ietf.org  Tue May 11 09:05:45 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA24102
	for <ietf-archive@odin.ietf.org>; Tue, 11 May 2004 09:05: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 1BNWv3-0007XY-CM
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 09:03:45 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4BD3bPJ028982
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 09:03:37 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNWit-0005V1-2f; Tue, 11 May 2004 08: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 1BNWgk-0004x6-8H
	for ietf@optimus.ietf.org; Tue, 11 May 2004 08:48: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 IAA23259
	for <ietf@ietf.org>; Tue, 11 May 2004 08:48: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 1BNWgi-0003sC-P6
	for ietf@ietf.org; Tue, 11 May 2004 08:48:48 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNWfj-0003VH-00
	for ietf@ietf.org; Tue, 11 May 2004 08:47:48 -0400
Received: from newdev.eecs.harvard.edu ([140.247.60.212] helo=newdev.harvard.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNWez-0002mO-00; Tue, 11 May 2004 08:47:01 -0400
Received: by newdev.harvard.edu (Postfix, from userid 501)
	id CB7E51E9556; Tue, 11 May 2004 08:46:25 -0400 (EDT)
To: harald@alvestrand.no, iesg@ietf.org, ietf@ietf.org, sob@harvard.edu
Subject: Re: Last Call: 'The IESG and RFC Editor documents: Procedures' to BCP
In-Reply-To: <15917027.1084202898@localhost>
Message-Id: <20040511124625.CB7E51E9556@newdev.harvard.edu>
Date: Tue, 11 May 2004 08:46:25 -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>

> --On 10. mai 2004 09:33 -0400 Scott Bradner <sob@harvard.edu> wrote:
> 
> > this misses one of the outcomes listed in RFC 2026 - specifically (quoting
> > from 2026):
> > 	"the IESG recommends that the document be brought within the
> > 	IETF and progressed within the IETF context"
> >
> > this path has been used from time to time and I think it is a valuable
> > option - I'd suggest that it be added as a 6th response
> 
> actually it was more-or-less intentionally left out.
> There are 3 scenarios to consider, I think:
> 
> - There is a valid reason why it's impossible to do this work outside of 
> the IETF. Response 4 or 5 should be returned, explaining why.

not the case I'm speaking of - I'm speaking of new work that the IESG 
feels would be a good new IETF topic or that it fits within the charter of
an existing WG (and maybe the author did not know that) and the IESG feels
that it would be good to have the WG work on the document.

> - The work can be done in the IETF, and the author agrees. The author 
> should (IMHO) be the one to inform the RFC Editor that he/she is dropping 
> the request to publish outside IETF review.

but that seems to drop a ball - the RFC Editor asks the IESG a question
imo the IESG should answer - maybe just say 'we are talking with the
author about doing this work in the IETF' but at least say something
to close the loop

I also think that just leaving out these possibilities makes this 
document an incomplete  picture of the processing that goes on
and I fail to see a reason to not mention that bringing the work into
the IETF is an option (even if you think the author should tell the
RFC Editor that is being done)

> - The work can be done in the IETF (or rather, this draft could be the 
> basis for further work in the IETF), but the author wants it published 
> independently anyway. In this case, I think it is good for the health of 
> the RFC series AND for the time budget of the IESG that the IESG does NOT 
> say "should be brought in" to the RFC Editor; the IESG, having failed to 
> convince the author, should just live with the RFC Editor's judgment on 
> publication.

agree (and 2026 specifically calls this case out)

Scott

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



From ietf-admin@ietf.org  Tue May 11 09:05: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 JAA24127
	for <ietf-archive@ietf.org>; Tue, 11 May 2004 09:05: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 1BNWxB-0002yQ-0Z
	for ietf-archive@ietf.org; Tue, 11 May 2004 09:05:49 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNWwA-0002YD-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 09:04:47 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNWv5-0001wk-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 09:03:39 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNWit-0005V1-2f; Tue, 11 May 2004 08: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 1BNWgk-0004x6-8H
	for ietf@optimus.ietf.org; Tue, 11 May 2004 08:48: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 IAA23259
	for <ietf@ietf.org>; Tue, 11 May 2004 08:48: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 1BNWgi-0003sC-P6
	for ietf@ietf.org; Tue, 11 May 2004 08:48:48 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNWfj-0003VH-00
	for ietf@ietf.org; Tue, 11 May 2004 08:47:48 -0400
Received: from newdev.eecs.harvard.edu ([140.247.60.212] helo=newdev.harvard.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNWez-0002mO-00; Tue, 11 May 2004 08:47:01 -0400
Received: by newdev.harvard.edu (Postfix, from userid 501)
	id CB7E51E9556; Tue, 11 May 2004 08:46:25 -0400 (EDT)
To: harald@alvestrand.no, iesg@ietf.org, ietf@ietf.org, sob@harvard.edu
Subject: Re: Last Call: 'The IESG and RFC Editor documents: Procedures' to BCP
In-Reply-To: <15917027.1084202898@localhost>
Message-Id: <20040511124625.CB7E51E9556@newdev.harvard.edu>
Date: Tue, 11 May 2004 08:46:25 -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

> --On 10. mai 2004 09:33 -0400 Scott Bradner <sob@harvard.edu> wrote:
> 
> > this misses one of the outcomes listed in RFC 2026 - specifically (quoting
> > from 2026):
> > 	"the IESG recommends that the document be brought within the
> > 	IETF and progressed within the IETF context"
> >
> > this path has been used from time to time and I think it is a valuable
> > option - I'd suggest that it be added as a 6th response
> 
> actually it was more-or-less intentionally left out.
> There are 3 scenarios to consider, I think:
> 
> - There is a valid reason why it's impossible to do this work outside of 
> the IETF. Response 4 or 5 should be returned, explaining why.

not the case I'm speaking of - I'm speaking of new work that the IESG 
feels would be a good new IETF topic or that it fits within the charter of
an existing WG (and maybe the author did not know that) and the IESG feels
that it would be good to have the WG work on the document.

> - The work can be done in the IETF, and the author agrees. The author 
> should (IMHO) be the one to inform the RFC Editor that he/she is dropping 
> the request to publish outside IETF review.

but that seems to drop a ball - the RFC Editor asks the IESG a question
imo the IESG should answer - maybe just say 'we are talking with the
author about doing this work in the IETF' but at least say something
to close the loop

I also think that just leaving out these possibilities makes this 
document an incomplete  picture of the processing that goes on
and I fail to see a reason to not mention that bringing the work into
the IETF is an option (even if you think the author should tell the
RFC Editor that is being done)

> - The work can be done in the IETF (or rather, this draft could be the 
> basis for further work in the IETF), but the author wants it published 
> independently anyway. In this case, I think it is good for the health of 
> the RFC series AND for the time budget of the IESG that the IESG does NOT 
> say "should be brought in" to the RFC Editor; the IESG, having failed to 
> convince the author, should just live with the RFC Editor's judgment on 
> publication.

agree (and 2026 specifically calls this case out)

Scott

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


From ietf-admin@ietf.org  Tue May 11 10:18: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 KAA28584
	for <ietf-archive@ietf.org>; Tue, 11 May 2004 10:18:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNY5x-0000oD-Dx
	for ietf-archive@ietf.org; Tue, 11 May 2004 10:18:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNY4v-0000Mr-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 10:17:53 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNY3s-0007jn-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 10:16:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNXrV-0004gE-O6; Tue, 11 May 2004 10:04:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNXgs-0000Ps-Dm
	for ietf@optimus.ietf.org; Tue, 11 May 2004 09:53: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 JAA26317
	for <ietf@ietf.org>; Tue, 11 May 2004 09:52: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 1BNXgn-00066y-M5
	for ietf@ietf.org; Tue, 11 May 2004 09:52:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNXfr-0005j2-00
	for ietf@ietf.org; Tue, 11 May 2004 09:52:00 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNXfB-0005ID-00; Tue, 11 May 2004 09:51:17 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 5EE44621F5; Tue, 11 May 2004 15:50:47 +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 19393-06; Tue, 11 May 2004 15:50:46 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 50E1961AA5; Tue, 11 May 2004 15:50:45 +0200 (CEST)
Date: Tue, 11 May 2004 14:34:50 +0100
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Scott Bradner <sob@harvard.edu>, iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: 'The IESG and RFC Editor documents: Procedures' to
 BCP
Message-ID: <70310080.1084286090@localhost>
In-Reply-To: <20040511124625.CB7E51E9556@newdev.harvard.edu>
References: <20040511124625.CB7E51E9556@newdev.harvard.edu>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
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 11. mai 2004 08:46 -0400 Scott Bradner <sob@harvard.edu> wrote:

>> - The work can be done in the IETF, and the author agrees. The author
>> should (IMHO) be the one to inform the RFC Editor that he/she is
>> dropping  the request to publish outside IETF review.
>
> but that seems to drop a ball - the RFC Editor asks the IESG a question
> imo the IESG should answer - maybe just say 'we are talking with the
> author about doing this work in the IETF' but at least say something
> to close the loop

Yes - the IESG should answer.
But I believe the question being asked is "is there a reason, based on 
conflict with existing IETF work, that this document should not be 
published?"

And the IESG should answer yes or no to that question.

Anything else should (IMHO) be advice to the RFC Editor and the author, and 
not be part of the formal position-taking the IESG makes.

Because in the past, we've seriously bogged down independent publications 
because we were debating (with or without the author) whether or not they 
should be IETF work.
And we need to stop doing that.

                    Harald






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


From ietf-admin@ietf.org  Tue May 11 10:21: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 KAA28802
	for <ietf-archive@ietf.org>; Tue, 11 May 2004 10:21: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 1BNY8G-0001ht-SE
	for ietf-archive@ietf.org; Tue, 11 May 2004 10:21:20 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNY7E-0001Gt-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 10:20:17 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNY6P-0000qX-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 10:19:25 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNXra-0004jq-SI; Tue, 11 May 2004 10:04:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNXnT-0001ZG-Vf
	for ietf@optimus.ietf.org; Tue, 11 May 2004 09:59:52 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26577
	for <ietf@ietf.org>; Tue, 11 May 2004 09:59:48 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNXnR-00014C-W3
	for ietf@ietf.org; Tue, 11 May 2004 09:59:50 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNXmT-0000f8-00
	for ietf@ietf.org; Tue, 11 May 2004 09:58:49 -0400
Received: from newdev.eecs.harvard.edu ([140.247.60.212] helo=newdev.harvard.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNXlL-0007g5-00; Tue, 11 May 2004 09:57:39 -0400
Received: by newdev.harvard.edu (Postfix, from userid 501)
	id 3E2D51E97E8; Tue, 11 May 2004 09:57:04 -0400 (EDT)
To: harald@alvestrand.no, iesg@ietf.org, ietf@ietf.org, sob@harvard.edu
Subject: Re: Last Call: 'The IESG and RFC Editor documents: Procedures' to BCP
In-Reply-To: <70310080.1084286090@localhost>
Message-Id: <20040511135704.3E2D51E97E8@newdev.harvard.edu>
Date: Tue, 11 May 2004 09:57: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

> Anything else should (IMHO) be advice to the RFC Editor and the author, and 
> not be part of the formal position-taking the IESG makes.

we may be debating termonology

your ID says "The IESG may return five different responses"

that seems to eliminate the possibility of communicating any
such advice

> Because in the past, we've seriously bogged down independent publications 
> because we were debating (with or without the author) whether or not they 
> should be IETF work.
> And we need to stop doing that.

beware of tossing too much away just to "stop doing that"

I still fail to see why this document cannot say that one of the
outcomes could be that the author could agree with the IESG to bring
the work into the IETF -  it seems a bit dogmatic to refuse to say that
(and counter to the intent of 2026)

Scott

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


From exim@www1.ietf.org  Tue May 11 10:22:43 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 KAA28948
	for <ietf-archive@odin.ietf.org>; Tue, 11 May 2004 10:22: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 1BNY3u-0001Ze-4I
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 10:16:55 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4BEGoRD006007
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 10:16:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNXrV-0004gE-O6; Tue, 11 May 2004 10:04:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNXgs-0000Ps-Dm
	for ietf@optimus.ietf.org; Tue, 11 May 2004 09:53: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 JAA26317
	for <ietf@ietf.org>; Tue, 11 May 2004 09:52: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 1BNXgn-00066y-M5
	for ietf@ietf.org; Tue, 11 May 2004 09:52:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNXfr-0005j2-00
	for ietf@ietf.org; Tue, 11 May 2004 09:52:00 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNXfB-0005ID-00; Tue, 11 May 2004 09:51:17 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 5EE44621F5; Tue, 11 May 2004 15:50:47 +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 19393-06; Tue, 11 May 2004 15:50:46 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 50E1961AA5; Tue, 11 May 2004 15:50:45 +0200 (CEST)
Date: Tue, 11 May 2004 14:34:50 +0100
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Scott Bradner <sob@harvard.edu>, iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: 'The IESG and RFC Editor documents: Procedures' to
 BCP
Message-ID: <70310080.1084286090@localhost>
In-Reply-To: <20040511124625.CB7E51E9556@newdev.harvard.edu>
References: <20040511124625.CB7E51E9556@newdev.harvard.edu>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-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: 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 11. mai 2004 08:46 -0400 Scott Bradner <sob@harvard.edu> wrote:

>> - The work can be done in the IETF, and the author agrees. The author
>> should (IMHO) be the one to inform the RFC Editor that he/she is
>> dropping  the request to publish outside IETF review.
>
> but that seems to drop a ball - the RFC Editor asks the IESG a question
> imo the IESG should answer - maybe just say 'we are talking with the
> author about doing this work in the IETF' but at least say something
> to close the loop

Yes - the IESG should answer.
But I believe the question being asked is "is there a reason, based on 
conflict with existing IETF work, that this document should not be 
published?"

And the IESG should answer yes or no to that question.

Anything else should (IMHO) be advice to the RFC Editor and the author, and 
not be part of the formal position-taking the IESG makes.

Because in the past, we've seriously bogged down independent publications 
because we were debating (with or without the author) whether or not they 
should be IETF work.
And we need to stop doing that.

                    Harald






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



From exim@www1.ietf.org  Tue May 11 10:23:19 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 KAA29028
	for <ietf-archive@odin.ietf.org>; Tue, 11 May 2004 10:23: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 1BNY6R-00042c-1w
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 10:19:27 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4BEJRel015477
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 10:19:27 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNXra-0004jq-SI; Tue, 11 May 2004 10:04:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNXnT-0001ZG-Vf
	for ietf@optimus.ietf.org; Tue, 11 May 2004 09:59:52 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26577
	for <ietf@ietf.org>; Tue, 11 May 2004 09:59:48 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNXnR-00014C-W3
	for ietf@ietf.org; Tue, 11 May 2004 09:59:50 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNXmT-0000f8-00
	for ietf@ietf.org; Tue, 11 May 2004 09:58:49 -0400
Received: from newdev.eecs.harvard.edu ([140.247.60.212] helo=newdev.harvard.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNXlL-0007g5-00; Tue, 11 May 2004 09:57:39 -0400
Received: by newdev.harvard.edu (Postfix, from userid 501)
	id 3E2D51E97E8; Tue, 11 May 2004 09:57:04 -0400 (EDT)
To: harald@alvestrand.no, iesg@ietf.org, ietf@ietf.org, sob@harvard.edu
Subject: Re: Last Call: 'The IESG and RFC Editor documents: Procedures' to BCP
In-Reply-To: <70310080.1084286090@localhost>
Message-Id: <20040511135704.3E2D51E97E8@newdev.harvard.edu>
Date: Tue, 11 May 2004 09:57: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>

> Anything else should (IMHO) be advice to the RFC Editor and the author, and 
> not be part of the formal position-taking the IESG makes.

we may be debating termonology

your ID says "The IESG may return five different responses"

that seems to eliminate the possibility of communicating any
such advice

> Because in the past, we've seriously bogged down independent publications 
> because we were debating (with or without the author) whether or not they 
> should be IETF work.
> And we need to stop doing that.

beware of tossing too much away just to "stop doing that"

I still fail to see why this document cannot say that one of the
outcomes could be that the author could agree with the IESG to bring
the work into the IETF -  it seems a bit dogmatic to refuse to say that
(and counter to the intent of 2026)

Scott

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



From ietf-admin@ietf.org  Tue May 11 11:15: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 LAA02744
	for <ietf-archive@ietf.org>; Tue, 11 May 2004 11:15: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 1BNYz3-0001Wj-Oz
	for ietf-archive@ietf.org; Tue, 11 May 2004 11:15:53 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNYy3-000155-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 11:14:51 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNYx8-0000ft-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 11:13:54 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNYkg-0005iU-Mg; Tue, 11 May 2004 11:01:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNYfr-0004gq-G0
	for ietf@optimus.ietf.org; Tue, 11 May 2004 10:56: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 KAA01360
	for <ietf@ietf.org>; Tue, 11 May 2004 10:55: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 1BNYfo-0000PA-Ry
	for ietf@ietf.org; Tue, 11 May 2004 10:56:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNYeQ-0007Xq-00
	for ietf@ietf.org; Tue, 11 May 2004 10:54:35 -0400
Received: from above.proper.com ([208.184.76.39])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNYdI-000740-00
	for ietf@ietf.org; Tue, 11 May 2004 10:53:24 -0400
Received: from [10.20.30.249] (dsl2-63-249-109-252.cruzio.com [63.249.109.252])
	(authenticated bits=0)
	by above.proper.com (8.12.11/8.12.9) with ESMTP id i4BErGN1021192;
	Tue, 11 May 2004 07:53:17 -0700 (PDT)
	(envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
X-Sender: phoffvpnc@mail.vpnc.org
Message-Id: <p0610050ebcc6979bb9ca@[10.20.30.249]>
In-Reply-To: <40A07E47.4060906@ehsco.com>
References: <DD72EEC3-A1E7-11D8-8626-003065F939FE@rudd.cc>
 <Pine.LNX.4.58.0405100019050.1405@perp.cac.washington.edu>
 <409F93F0.5060300@ehsco.com> <p06100532bcc54f129dec@[10.20.30.249]>
 <40A07E47.4060906@ehsco.com>
Date: Tue, 11 May 2004 07:53:16 -0700
To: "Eric A. Hall" <ehall@ehsco.com>
From: Paul Hoffman / VPNC <paul.hoffman@vpnc.org>
Subject: Re: Not sure if this is the right place for this
Cc: IETF <ietf@ietf.org>
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.1 required=5.0 tests=AWL autolearn=no version=2.60

At 2:18 AM -0500 5/11/04, Eric A. Hall wrote:
>I'm not even sure they are similar arguments. I mean, the argument against
>SSL is that *if* an SSL connection is blocked, and *if* an alternative
>clear channel exists, and *if* that channel accepts clear-text logins, and
>*if* the client fallsback through all of that, then the session will be
>exposed. I'll grant that it's easy enough to interfere with somebody
>establishing a session, and that there's a measurable percentage of
>services that maintain clear channel alternatives, and that PLAIN/LOGIN
>are still the only things that work everywhere, and that there are
>probably clients which fallback invisibly. I can also argue some of those
>points to some degree -- that people who have setup SSL versions are
>likely to have eliminated access to the clear channel, for example -- so
>instead of any of those things being certainties, we should agree that
>this is a question of overlapping probabilities.

Not only can you argue that, it is the default setting for most 
SSL-using applications today (other than web browsers). As we were 
discussing this years ago, most application developers thought that 
this arrangement is exactly what the users wanted.

>On the other hand, STARTTLS *requires* a clear channel that the client
>MUST *already* be using. So whereas the attack on SSL *might* succeed in
>putting the client in touch with an unencrypted service, TLS is
>*guaranteed* to be using such a service already anyway. The only question
>is whether or not a decipherable login can be used, which is a probability
>mask that also applies to the SSL scenario.

Exactly right. This is the strongest argument in favor of protected 
ports over STARTTLS.

>Given the collection of probabilities, therefore, starting with an SSL
>channel and refusing connections to a backup clear channel eliminates most
>of the probability from the MitM attack model.

Right. And this is rejected by most people as unreasonable for the 
application users, unfortunately. What we are battling here is not 
how to do the protocols securely, but how to get the users to use the 
applications securely. If they say "if I can't get a secure 
connection I still want to communicate", all our lovely design is 
lost.

>I don't think it really matters given the other problems (see below).

Fully agree.

--Paul Hoffman, Director
--VPN Consortium

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


From exim@www1.ietf.org  Tue May 11 11:21:47 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03179
	for <ietf-archive@odin.ietf.org>; Tue, 11 May 2004 11:21: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 1BNYx6-0008Ir-Qz
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 11:13:55 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4BFDq8G031918
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 11:13:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNYkg-0005iU-Mg; Tue, 11 May 2004 11:01:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNYfr-0004gq-G0
	for ietf@optimus.ietf.org; Tue, 11 May 2004 10:56: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 KAA01360
	for <ietf@ietf.org>; Tue, 11 May 2004 10:55: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 1BNYfo-0000PA-Ry
	for ietf@ietf.org; Tue, 11 May 2004 10:56:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNYeQ-0007Xq-00
	for ietf@ietf.org; Tue, 11 May 2004 10:54:35 -0400
Received: from above.proper.com ([208.184.76.39])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNYdI-000740-00
	for ietf@ietf.org; Tue, 11 May 2004 10:53:24 -0400
Received: from [10.20.30.249] (dsl2-63-249-109-252.cruzio.com [63.249.109.252])
	(authenticated bits=0)
	by above.proper.com (8.12.11/8.12.9) with ESMTP id i4BErGN1021192;
	Tue, 11 May 2004 07:53:17 -0700 (PDT)
	(envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
X-Sender: phoffvpnc@mail.vpnc.org
Message-Id: <p0610050ebcc6979bb9ca@[10.20.30.249]>
In-Reply-To: <40A07E47.4060906@ehsco.com>
References: <DD72EEC3-A1E7-11D8-8626-003065F939FE@rudd.cc>
 <Pine.LNX.4.58.0405100019050.1405@perp.cac.washington.edu>
 <409F93F0.5060300@ehsco.com> <p06100532bcc54f129dec@[10.20.30.249]>
 <40A07E47.4060906@ehsco.com>
Date: Tue, 11 May 2004 07:53:16 -0700
To: "Eric A. Hall" <ehall@ehsco.com>
From: Paul Hoffman / VPNC <paul.hoffman@vpnc.org>
Subject: Re: Not sure if this is the right place for this
Cc: IETF <ietf@ietf.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.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 2:18 AM -0500 5/11/04, Eric A. Hall wrote:
>I'm not even sure they are similar arguments. I mean, the argument against
>SSL is that *if* an SSL connection is blocked, and *if* an alternative
>clear channel exists, and *if* that channel accepts clear-text logins, and
>*if* the client fallsback through all of that, then the session will be
>exposed. I'll grant that it's easy enough to interfere with somebody
>establishing a session, and that there's a measurable percentage of
>services that maintain clear channel alternatives, and that PLAIN/LOGIN
>are still the only things that work everywhere, and that there are
>probably clients which fallback invisibly. I can also argue some of those
>points to some degree -- that people who have setup SSL versions are
>likely to have eliminated access to the clear channel, for example -- so
>instead of any of those things being certainties, we should agree that
>this is a question of overlapping probabilities.

Not only can you argue that, it is the default setting for most 
SSL-using applications today (other than web browsers). As we were 
discussing this years ago, most application developers thought that 
this arrangement is exactly what the users wanted.

>On the other hand, STARTTLS *requires* a clear channel that the client
>MUST *already* be using. So whereas the attack on SSL *might* succeed in
>putting the client in touch with an unencrypted service, TLS is
>*guaranteed* to be using such a service already anyway. The only question
>is whether or not a decipherable login can be used, which is a probability
>mask that also applies to the SSL scenario.

Exactly right. This is the strongest argument in favor of protected 
ports over STARTTLS.

>Given the collection of probabilities, therefore, starting with an SSL
>channel and refusing connections to a backup clear channel eliminates most
>of the probability from the MitM attack model.

Right. And this is rejected by most people as unreasonable for the 
application users, unfortunately. What we are battling here is not 
how to do the protocols securely, but how to get the users to use the 
applications securely. If they say "if I can't get a secure 
connection I still want to communicate", all our lovely design is 
lost.

>I don't think it really matters given the other problems (see below).

Fully agree.

--Paul Hoffman, Director
--VPN Consortium

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



From ietf-admin@ietf.org  Tue May 11 12:47: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 MAA07761
	for <ietf-archive@ietf.org>; Tue, 11 May 2004 12:47: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 1BNaPQ-0001FJ-FT
	for ietf-archive@ietf.org; Tue, 11 May 2004 12:47:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNaOP-0000ny-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 12:46:10 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNaNb-0000Ns-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 12:45:19 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNa7v-0007CM-VK; Tue, 11 May 2004 12:29:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNZzM-0004ti-BP
	for ietf@optimus.ietf.org; Tue, 11 May 2004 12:20: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 MAA06093
	for <ietf@ietf.org>; Tue, 11 May 2004 12:20: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 1BNZzK-00058N-QF
	for ietf@ietf.org; Tue, 11 May 2004 12:20:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNZyN-0004iU-00
	for ietf@ietf.org; Tue, 11 May 2004 12:19:16 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNZxn-0004IQ-00; Tue, 11 May 2004 12:18:39 -0400
Received: from [127.0.0.1] (helo=localhost)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1BNZxY-0009Co-00; Tue, 11 May 2004 11:18:24 -0500
Date: Tue, 11 May 2004 12:18:20 -0400
From: John C Klensin <john-ietf@jck.com>
To: Scott Bradner <sob@harvard.edu>, harald@alvestrand.no, iesg@ietf.org,
        ietf@ietf.org
Subject: Re: Last Call: 'The IESG and RFC Editor documents:
 Procedures' to BCP
Message-ID: <09ADC4D72F555E7E1CEC63F9@localhost>
In-Reply-To: <20040511135704.3E2D51E97E8@newdev.harvard.edu>
References: <20040511135704.3E2D51E97E8@newdev.harvard.edu>
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

Scott, Harald,

It seems to me that this problem/ disagreement could be easily 
solved while preserving the (IMO, valid) points both of you are 
making, by including a sentence somewhere to the effect of...

	Of course, the IESG or individual ADs may have
	discussions with the author during this period about
	other possible ways to handle the document.  Should that
	discussion result in a voluntary action by the author to
	drop the request to the RFC Editor to publist, the
	document moves immediately outside the scope of this
	specification.

Now, that may not be the right phrasing in context, and can 
certainly be improved.   But I think it covers the full range of 
from "we really think this should be standardized, why not let 
us process it that way" to "if you insist on publishing that 
thing, I'm going to break both of your legs".   The question of 
whether those actions are appropriate is a separate issue, but 
the IESG has never been able to insist on either standardization 
or withdrawal.  And, as far as I know, both actions are 
identical as far as the RFC Editor is concerned: the document is 
spontaneously withdrawn as an individual submission.

       john


--On Tuesday, May 11, 2004 9:57 AM -0400 Scott Bradner 
<sob@harvard.edu> wrote:

>> Anything else should (IMHO) be advice to the RFC Editor and
>> the author, and  not be part of the formal position-taking
>> the IESG makes.
>
> we may be debating termonology
>
> your ID says "The IESG may return five different responses"
>
> that seems to eliminate the possibility of communicating any
> such advice
>
>> Because in the past, we've seriously bogged down independent
>> publications  because we were debating (with or without the
>> author) whether or not they  should be IETF work.
>> And we need to stop doing that.
>
> beware of tossing too much away just to "stop doing that"
>
> I still fail to see why this document cannot say that one of
> the outcomes could be that the author could agree with the
> IESG to bring the work into the IETF -  it seems a bit
> dogmatic to refuse to say that (and counter to the intent of
> 2026)
>
> Scott
>
> _______________________________________________
> 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 May 11 12:57:40 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 MAA08334
	for <ietf-archive@odin.ietf.org>; Tue, 11 May 2004 12:57:40 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNaNc-0001xI-NJ
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 12:45:36 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4BGjKPc007508
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 12:45:20 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNa7v-0007CM-VK; Tue, 11 May 2004 12:29:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNZzM-0004ti-BP
	for ietf@optimus.ietf.org; Tue, 11 May 2004 12:20: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 MAA06093
	for <ietf@ietf.org>; Tue, 11 May 2004 12:20: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 1BNZzK-00058N-QF
	for ietf@ietf.org; Tue, 11 May 2004 12:20:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNZyN-0004iU-00
	for ietf@ietf.org; Tue, 11 May 2004 12:19:16 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNZxn-0004IQ-00; Tue, 11 May 2004 12:18:39 -0400
Received: from [127.0.0.1] (helo=localhost)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1BNZxY-0009Co-00; Tue, 11 May 2004 11:18:24 -0500
Date: Tue, 11 May 2004 12:18:20 -0400
From: John C Klensin <john-ietf@jck.com>
To: Scott Bradner <sob@harvard.edu>, harald@alvestrand.no, iesg@ietf.org,
        ietf@ietf.org
Subject: Re: Last Call: 'The IESG and RFC Editor documents:
 Procedures' to BCP
Message-ID: <09ADC4D72F555E7E1CEC63F9@localhost>
In-Reply-To: <20040511135704.3E2D51E97E8@newdev.harvard.edu>
References: <20040511135704.3E2D51E97E8@newdev.harvard.edu>
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

Scott, Harald,

It seems to me that this problem/ disagreement could be easily 
solved while preserving the (IMO, valid) points both of you are 
making, by including a sentence somewhere to the effect of...

	Of course, the IESG or individual ADs may have
	discussions with the author during this period about
	other possible ways to handle the document.  Should that
	discussion result in a voluntary action by the author to
	drop the request to the RFC Editor to publist, the
	document moves immediately outside the scope of this
	specification.

Now, that may not be the right phrasing in context, and can 
certainly be improved.   But I think it covers the full range of 
from "we really think this should be standardized, why not let 
us process it that way" to "if you insist on publishing that 
thing, I'm going to break both of your legs".   The question of 
whether those actions are appropriate is a separate issue, but 
the IESG has never been able to insist on either standardization 
or withdrawal.  And, as far as I know, both actions are 
identical as far as the RFC Editor is concerned: the document is 
spontaneously withdrawn as an individual submission.

       john


--On Tuesday, May 11, 2004 9:57 AM -0400 Scott Bradner 
<sob@harvard.edu> wrote:

>> Anything else should (IMHO) be advice to the RFC Editor and
>> the author, and  not be part of the formal position-taking
>> the IESG makes.
>
> we may be debating termonology
>
> your ID says "The IESG may return five different responses"
>
> that seems to eliminate the possibility of communicating any
> such advice
>
>> Because in the past, we've seriously bogged down independent
>> publications  because we were debating (with or without the
>> author) whether or not they  should be IETF work.
>> And we need to stop doing that.
>
> beware of tossing too much away just to "stop doing that"
>
> I still fail to see why this document cannot say that one of
> the outcomes could be that the author could agree with the
> IESG to bring the work into the IETF -  it seems a bit
> dogmatic to refuse to say that (and counter to the intent of
> 2026)
>
> Scott
>
> _______________________________________________
> 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 May 11 13:14: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 NAA09452
	for <ietf-archive@ietf.org>; Tue, 11 May 2004 13:14: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 1BNaqJ-0005bK-CB
	for ietf-archive@ietf.org; Tue, 11 May 2004 13:14:59 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNapK-00058X-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 13:13:58 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNao9-0004K7-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 13:12:45 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNaZu-0004tE-8g; Tue, 11 May 2004 12:58:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNaJc-0001AG-76
	for ietf@optimus.ietf.org; Tue, 11 May 2004 12:41:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07516
	for <ietf@ietf.org>; Tue, 11 May 2004 12:41: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 1BNaJa-0006SO-GR
	for ietf@ietf.org; Tue, 11 May 2004 12:41:10 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNaIk-00062P-00
	for ietf@ietf.org; Tue, 11 May 2004 12:40:19 -0400
Received: from newdev.eecs.harvard.edu ([140.247.60.212] helo=newdev.harvard.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNaI6-0005Y6-00; Tue, 11 May 2004 12:39:38 -0400
Received: by newdev.harvard.edu (Postfix, from userid 501)
	id 0EF011E9EDF; Tue, 11 May 2004 12:39:02 -0400 (EDT)
To: harald@alvestrand.no, iesg@ietf.org, ietf@ietf.org, john-ietf@jck.com,
        sob@harvard.edu
Subject: Re: Last Call: 'The IESG and RFC Editor documents: Procedures' to BCP
In-Reply-To: <09ADC4D72F555E7E1CEC63F9@localhost>
Message-Id: <20040511163902.0EF011E9EDF@newdev.harvard.edu>
Date: Tue, 11 May 2004 12:39:02 -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

in general that seems OK though I'd like to see "including the possibility
of the author pursuing the work within the IETF" added

----

From exim@www1.ietf.org  Tue May 11 13:26:35 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 NAA10223
	for <ietf-archive@odin.ietf.org>; Tue, 11 May 2004 13:26:35 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNaoA-0008Ji-Di
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 13:12:46 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4BHCkN0031970
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 13:12:46 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNaZu-0004tE-8g; Tue, 11 May 2004 12:58:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNaJc-0001AG-76
	for ietf@optimus.ietf.org; Tue, 11 May 2004 12:41:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07516
	for <ietf@ietf.org>; Tue, 11 May 2004 12:41: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 1BNaJa-0006SO-GR
	for ietf@ietf.org; Tue, 11 May 2004 12:41:10 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNaIk-00062P-00
	for ietf@ietf.org; Tue, 11 May 2004 12:40:19 -0400
Received: from newdev.eecs.harvard.edu ([140.247.60.212] helo=newdev.harvard.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNaI6-0005Y6-00; Tue, 11 May 2004 12:39:38 -0400
Received: by newdev.harvard.edu (Postfix, from userid 501)
	id 0EF011E9EDF; Tue, 11 May 2004 12:39:02 -0400 (EDT)
To: harald@alvestrand.no, iesg@ietf.org, ietf@ietf.org, john-ietf@jck.com,
        sob@harvard.edu
Subject: Re: Last Call: 'The IESG and RFC Editor documents: Procedures' to BCP
In-Reply-To: <09ADC4D72F555E7E1CEC63F9@localhost>
Message-Id: <20040511163902.0EF011E9EDF@newdev.harvard.edu>
Date: Tue, 11 May 2004 12:39:02 -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>

in general that seems OK though I'd like to see "including the possibility
of the author pursuing the work within the IETF" added

----

From ietf-admin@ietf.org  Tue May 11 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 OAA13810
	for <ietf-archive@ietf.org>; Tue, 11 May 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 1BNbuR-0003vS-AZ
	for ietf-archive@ietf.org; Tue, 11 May 2004 14:23:19 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNbtV-0003TK-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 14:22:22 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNbsT-00031E-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 14:21:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNbff-00045Z-UJ; Tue, 11 May 2004 14:08:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNbbn-00031V-U7
	for ietf@optimus.ietf.org; Tue, 11 May 2004 14:04: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 OAA12866
	for <ietf@ietf.org>; Tue, 11 May 2004 14:04: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 1BNbbl-0003dR-0A
	for ietf@ietf.org; Tue, 11 May 2004 14:04:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNbam-0003Cg-00
	for ietf@ietf.org; Tue, 11 May 2004 14:03:01 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNbZt-0002NE-00
	for ietf@ietf.org; Tue, 11 May 2004 14:02:05 -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 i4BI1Jpw019904
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 11 May 2004 14:01:23 -0400
Date: Tue, 11 May 2004 14:01:19 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Harald Tveit Alvestrand <harald@alvestrand.no>
cc: ietf@ietf.org, <dnsop@lists.uoregon.edu>
Subject: Re: Complaint on abuse of DNSOP lists
In-Reply-To: <10224401.1084197205@localhost>
Message-ID: <Pine.LNX.4.44.0405111357560.19722-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, 10 May 2004, Harald Tveit Alvestrand wrote:

> Dean,
> 
> third time same complaint, third time same answer.
> 
> No.
> 
> A WG chair is expected to read mail coming from the working group list. 
> What he does with copies that go directly to him is his own business.

I disagree. A WG chair has to read email from participants, including 
off-list email.  Certain complaints and business needs to be handled 
off-list.  

> And as I have told you on the previous two instances of this complaint: 
> Personal mail to you, including bounce messages, is not someone defaming 
> you in the IETF, even when you choose to make it public.

I disagree, and I believe the IETF attorney has advised you otherwise.  
The previous complaints involving Paul Vixie and Joe Abley regarded their 
roles as participants, not as representatives of the IETF.

Dean Anderson
Av8 Internet, Inc


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


From ietf-admin@ietf.org  Tue May 11 14:26: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 OAA13979
	for <ietf-archive@ietf.org>; Tue, 11 May 2004 14:26: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 1BNbxO-0005Gi-TI
	for ietf-archive@ietf.org; Tue, 11 May 2004 14:26:23 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNbwM-0004ok-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 14:25:19 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNbvi-0004NQ-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 14:24:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNbgc-0004Fe-Or; Tue, 11 May 2004 14:09:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNbcv-0003D1-Uh
	for ietf@optimus.ietf.org; Tue, 11 May 2004 14:05:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12951
	for <ietf@ietf.org>; Tue, 11 May 2004 14:05:10 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNbct-00045b-Fw
	for ietf@ietf.org; Tue, 11 May 2004 14:05:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNbbv-0003fG-00
	for ietf@ietf.org; Tue, 11 May 2004 14:04:12 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNbb2-0002oM-00
	for ietf@ietf.org; Tue, 11 May 2004 14:03:16 -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 i4BI2jLQ019907
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 11 May 2004 14:02:45 -0400
Date: Tue, 11 May 2004 14:02:45 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: bmanning@vacation.karoshi.com
cc: Ken Raeburn <raeburn@MIT.EDU>,
        Harald Tveit Alvestrand <harald@alvestrand.no>, <ietf@ietf.org>,
        "<dnsop@lists.uoregon.edu>" <dnsop@lists.uoregon.edu>
Subject: Re: [dnsop] Re: Complaint on abuse of DNSOP lists
In-Reply-To: <20040510224859.GA17723@vacation.karoshi.com.>
Message-ID: <Pine.LNX.4.44.0405111401380.19722-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

The following message indicates that EP.NET has assigned an IP address to 
ISC.ORG.  You are quite well aware of this.  Dissembling will not help 
you.

		--Dean 


Date: Thu, 15 Jan 2004 10:26:42 -0500 (EST)
From: Dean Anderson <dean@av8.com>
To: bill <bmanning@karoshi.com>
Subject: Re: Complaint regarding www.sorbs.net (204.152.186.189) (fwd)


On Wed, 14 Jan 2004, bill wrote:

>       I have no reason to act as your relay agent.  We have no
>       agreement in place for me to act in this manner.

The traceroute I forwarded shows that your IP addresses 198.32.176.4 is
assigned to ISC.ORG, which typically indicates a relationship.

>  8  paix-gw4.isc.org (198.32.176.4)  92.828 ms  91.036 ms  91.415 ms



On Mon, 10 May 2004 bmanning@vacation.karoshi.com wrote:

> > but ISC.ORG doesn't want to take a complaint. Bill Manning, of EP.NET
> > (ISC.ORG upstream) says he has no contract with me to accept complaints
> > about ISC.ORG.
> > 
> > 		--Dean
> 
> 	Dean... you are asserting a relationship that you have no 
> 	way to prove exists.  Unless or until you can prove that
> 	ep.net is an upstream for isc.org, please refrain from 
> 	making such statements.  Traceroute is not your friend in
> 	this case.  Defamation works many ways.
> 
> --bill
> 


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


From exim@www1.ietf.org  Tue May 11 14:31:40 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14551
	for <ietf-archive@odin.ietf.org>; Tue, 11 May 2004 14:31:40 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNbsW-0006UW-Qr
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 14:21:22 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4BILKK2024650
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 14:21:20 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNbff-00045Z-UJ; Tue, 11 May 2004 14:08:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNbbn-00031V-U7
	for ietf@optimus.ietf.org; Tue, 11 May 2004 14:04: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 OAA12866
	for <ietf@ietf.org>; Tue, 11 May 2004 14:04: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 1BNbbl-0003dR-0A
	for ietf@ietf.org; Tue, 11 May 2004 14:04:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNbam-0003Cg-00
	for ietf@ietf.org; Tue, 11 May 2004 14:03:01 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNbZt-0002NE-00
	for ietf@ietf.org; Tue, 11 May 2004 14:02:05 -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 i4BI1Jpw019904
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 11 May 2004 14:01:23 -0400
Date: Tue, 11 May 2004 14:01:19 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Harald Tveit Alvestrand <harald@alvestrand.no>
cc: ietf@ietf.org, <dnsop@lists.uoregon.edu>
Subject: Re: Complaint on abuse of DNSOP lists
In-Reply-To: <10224401.1084197205@localhost>
Message-ID: <Pine.LNX.4.44.0405111357560.19722-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, 10 May 2004, Harald Tveit Alvestrand wrote:

> Dean,
> 
> third time same complaint, third time same answer.
> 
> No.
> 
> A WG chair is expected to read mail coming from the working group list. 
> What he does with copies that go directly to him is his own business.

I disagree. A WG chair has to read email from participants, including 
off-list email.  Certain complaints and business needs to be handled 
off-list.  

> And as I have told you on the previous two instances of this complaint: 
> Personal mail to you, including bounce messages, is not someone defaming 
> you in the IETF, even when you choose to make it public.

I disagree, and I believe the IETF attorney has advised you otherwise.  
The previous complaints involving Paul Vixie and Joe Abley regarded their 
roles as participants, not as representatives of the IETF.

Dean Anderson
Av8 Internet, Inc


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



From exim@www1.ietf.org  Tue May 11 14:31: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 OAA14581
	for <ietf-archive@odin.ietf.org>; Tue, 11 May 2004 14:31: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 1BNbvk-0007Q3-3K
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 14:24:41 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4BIOeEg028468
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 14:24:40 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNbgc-0004Fe-Or; Tue, 11 May 2004 14:09:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNbcv-0003D1-Uh
	for ietf@optimus.ietf.org; Tue, 11 May 2004 14:05:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12951
	for <ietf@ietf.org>; Tue, 11 May 2004 14:05:10 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNbct-00045b-Fw
	for ietf@ietf.org; Tue, 11 May 2004 14:05:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNbbv-0003fG-00
	for ietf@ietf.org; Tue, 11 May 2004 14:04:12 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNbb2-0002oM-00
	for ietf@ietf.org; Tue, 11 May 2004 14:03:16 -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 i4BI2jLQ019907
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 11 May 2004 14:02:45 -0400
Date: Tue, 11 May 2004 14:02:45 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: bmanning@vacation.karoshi.com
cc: Ken Raeburn <raeburn@MIT.EDU>,
        Harald Tveit Alvestrand <harald@alvestrand.no>, <ietf@ietf.org>,
        "<dnsop@lists.uoregon.edu>" <dnsop@lists.uoregon.edu>
Subject: Re: [dnsop] Re: Complaint on abuse of DNSOP lists
In-Reply-To: <20040510224859.GA17723@vacation.karoshi.com.>
Message-ID: <Pine.LNX.4.44.0405111401380.19722-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>

The following message indicates that EP.NET has assigned an IP address to 
ISC.ORG.  You are quite well aware of this.  Dissembling will not help 
you.

		--Dean 


Date: Thu, 15 Jan 2004 10:26:42 -0500 (EST)
From: Dean Anderson <dean@av8.com>
To: bill <bmanning@karoshi.com>
Subject: Re: Complaint regarding www.sorbs.net (204.152.186.189) (fwd)


On Wed, 14 Jan 2004, bill wrote:

>       I have no reason to act as your relay agent.  We have no
>       agreement in place for me to act in this manner.

The traceroute I forwarded shows that your IP addresses 198.32.176.4 is
assigned to ISC.ORG, which typically indicates a relationship.

>  8  paix-gw4.isc.org (198.32.176.4)  92.828 ms  91.036 ms  91.415 ms



On Mon, 10 May 2004 bmanning@vacation.karoshi.com wrote:

> > but ISC.ORG doesn't want to take a complaint. Bill Manning, of EP.NET
> > (ISC.ORG upstream) says he has no contract with me to accept complaints
> > about ISC.ORG.
> > 
> > 		--Dean
> 
> 	Dean... you are asserting a relationship that you have no 
> 	way to prove exists.  Unless or until you can prove that
> 	ep.net is an upstream for isc.org, please refrain from 
> 	making such statements.  Traceroute is not your friend in
> 	this case.  Defamation works many ways.
> 
> --bill
> 


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



From ietf-admin@ietf.org  Tue May 11 14:48: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 OAA15689
	for <ietf-archive@ietf.org>; Tue, 11 May 2004 14:48: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 1BNcIa-00077n-GU
	for ietf-archive@ietf.org; Tue, 11 May 2004 14:48:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNcHW-0006f1-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 14:47:11 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNcGf-0006EC-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 14:46:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNc32-000125-So; Tue, 11 May 2004 14:32:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNc0L-0008S7-UF
	for ietf@optimus.ietf.org; Tue, 11 May 2004 14:29: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 OAA14233
	for <ietf@ietf.org>; Tue, 11 May 2004 14:29: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 1BNc0J-0006fB-9x
	for ietf@ietf.org; Tue, 11 May 2004 14:29:23 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNbyy-00068i-00
	for ietf@ietf.org; Tue, 11 May 2004 14:28:01 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNbxs-0005Ge-00
	for ietf@ietf.org; Tue, 11 May 2004 14:26:52 -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 i4BIQMad020357
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 11 May 2004 14:26:22 -0400
Date: Tue, 11 May 2004 14:26:22 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
cc: ietf@ietf.org
Subject: Re: Complaint on abuse of DNSOP lists
In-Reply-To: <20040510233411.DB05B86AE2@mercury.lcs.mit.edu>
Message-ID: <Pine.LNX.4.44.0405111419230.19722-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, 10 May 2004, Noel Chiappa wrote:

> So? Rob's not refusing to accept *any* email *at all* from you as a person
> (just from a range of addresses which are generating email he doesn't like);
> and you're more than savvy enough technically to get email to him via some
> other path.

As an IETF WG chair, he's obligated to follow the IETF rules on public
participation.  He can't block anything that the IETF mail server can't
block: Public Participants.

> He's not under any more obligation to accept email from you via whatever
> channel you feel like using, no matter how onerous for him, than he is to
> accept messages written on 12' long oak logs of 3' diameter.
> 
> 
> Get a life, will you? Your constant whining and flaming is really getting
> old. You're getting really close to the line at which I'd ask the Chair to
> ban you from posting. Oh wait, I know what your response would be - you'd sue
> us. And you seem to think the rest of the world is doing things which is
> making you look bad. Here's another free clue: you're doing a far better job
> of that than the rest of us could do with a decade of free time.

I'm entitled to particpate, and I'm entitled to send email to the WG 
chairs as a participant.

One thing I've noticed is that of none of the people criticizing me has
thought to address the fact that OUR ADDRESS SPACE IS NOT HIJACKED, and
that these people associated with the IETF: Paul Vixie, Joe Abley, Bill
Manning, and Rob Austein as WG Co-chair in his role for IETF business, all
claim that it is.  But anyone can plainly see they are lying.

Dean Anderson
Av8 Internet, Inc




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


From exim@www1.ietf.org  Tue May 11 14:48:34 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15727
	for <ietf-archive@odin.ietf.org>; Tue, 11 May 2004 14:48: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 1BNcGi-0004Xr-0Z
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 14:46:20 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4BIkJX2017406
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 14:46:19 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNc32-000125-So; Tue, 11 May 2004 14:32:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNc0L-0008S7-UF
	for ietf@optimus.ietf.org; Tue, 11 May 2004 14:29: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 OAA14233
	for <ietf@ietf.org>; Tue, 11 May 2004 14:29: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 1BNc0J-0006fB-9x
	for ietf@ietf.org; Tue, 11 May 2004 14:29:23 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNbyy-00068i-00
	for ietf@ietf.org; Tue, 11 May 2004 14:28:01 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNbxs-0005Ge-00
	for ietf@ietf.org; Tue, 11 May 2004 14:26:52 -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 i4BIQMad020357
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 11 May 2004 14:26:22 -0400
Date: Tue, 11 May 2004 14:26:22 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
cc: ietf@ietf.org
Subject: Re: Complaint on abuse of DNSOP lists
In-Reply-To: <20040510233411.DB05B86AE2@mercury.lcs.mit.edu>
Message-ID: <Pine.LNX.4.44.0405111419230.19722-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, 10 May 2004, Noel Chiappa wrote:

> So? Rob's not refusing to accept *any* email *at all* from you as a person
> (just from a range of addresses which are generating email he doesn't like);
> and you're more than savvy enough technically to get email to him via some
> other path.

As an IETF WG chair, he's obligated to follow the IETF rules on public
participation.  He can't block anything that the IETF mail server can't
block: Public Participants.

> He's not under any more obligation to accept email from you via whatever
> channel you feel like using, no matter how onerous for him, than he is to
> accept messages written on 12' long oak logs of 3' diameter.
> 
> 
> Get a life, will you? Your constant whining and flaming is really getting
> old. You're getting really close to the line at which I'd ask the Chair to
> ban you from posting. Oh wait, I know what your response would be - you'd sue
> us. And you seem to think the rest of the world is doing things which is
> making you look bad. Here's another free clue: you're doing a far better job
> of that than the rest of us could do with a decade of free time.

I'm entitled to particpate, and I'm entitled to send email to the WG 
chairs as a participant.

One thing I've noticed is that of none of the people criticizing me has
thought to address the fact that OUR ADDRESS SPACE IS NOT HIJACKED, and
that these people associated with the IETF: Paul Vixie, Joe Abley, Bill
Manning, and Rob Austein as WG Co-chair in his role for IETF business, all
claim that it is.  But anyone can plainly see they are lying.

Dean Anderson
Av8 Internet, Inc




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



From ietf-admin@ietf.org  Tue May 11 15:21: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 PAA18965
	for <ietf-archive@ietf.org>; Tue, 11 May 2004 15:21: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 1BNcon-00068e-K3
	for ietf-archive@ietf.org; Tue, 11 May 2004 15:21:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNcnn-0005fz-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 15:20:32 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNcmx-0005DR-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 15:19:39 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNcXu-0003Pk-Iy; Tue, 11 May 2004 15:04:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNcTA-0006oO-5m
	for ietf@optimus.ietf.org; Tue, 11 May 2004 14:59:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16448
	for <ietf@ietf.org>; Tue, 11 May 2004 14:59: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 1BNcT7-0004Cb-8S
	for ietf@ietf.org; Tue, 11 May 2004 14:59:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNcSA-0003mi-00
	for ietf@ietf.org; Tue, 11 May 2004 14:58:11 -0400
Received: from carwash.centive.com ([65.220.90.249])
	by ietf-mx with smtp (Exim 4.12)
	id 1BNcRS-0003Bb-00
	for ietf@ietf.org; Tue, 11 May 2004 14:57:26 -0400
Received: from minglewood.incentivesystems.com ([10.10.30.25])
 by carwash.centive.com (SAVSMTP 3.1.3.37) with SMTP id M2004051114555606205
 ; Tue, 11 May 2004 14:55:56 -0400
Received: from [10.10.48.119] ([10.10.48.119]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Tue, 11 May 2004 14:51:00 -0400
Message-ID: <40A12093.7010100@centive.com>
Date: Tue, 11 May 2004 14:50:59 -0400
From: John Stracke <jstracke@centive.com>
User-Agent: Mozilla Thunderbird 0.6 (Windows/20040502)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Dean Anderson <dean@av8.com>
CC: Noel Chiappa <jnc@mercury.lcs.mit.edu>, ietf@ietf.org
Subject: Re: Complaint on abuse of DNSOP lists
References: <Pine.LNX.4.44.0405111419230.19722-100000@cirrus.av8.net>
In-Reply-To: <Pine.LNX.4.44.0405111419230.19722-100000@cirrus.av8.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 11 May 2004 18:51:00.0142 (UTC) FILETIME=[E6DB2CE0:01C43788]
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

Dean Anderson wrote:

>One thing I've noticed is that of none of the people criticizing me has
>thought to address the fact that OUR ADDRESS SPACE IS NOT HIJACKED, and
>that these people associated with the IETF: Paul Vixie, Joe Abley, Bill
>Manning, and Rob Austein as WG Co-chair in his role for IETF business, all
>claim that it is.  But anyone can plainly see they are lying.
>  
>
No, actually, that's very difficult for anyone to see.  First off 
there's the simple matter that "hijacked" doesn't mean you hijacked it; 
as has already been pointed out, it could mean that someone else 
hijacked part of it from you.

Second there's the fact that ARIN lists your netblock as being assigned 
to the Open Software Foundation (with yourself as the contact).  It is 
impossible for an outsider to know whether or not the OSF transferred 
the block to av8.com legitimately.  I don't suspect it, you 
understand--nor do I much care--I'm just pointing out that it's not 
plain whether anybody here is lying.

-- 
/===============================================================\
|John Stracke      |jstracke@centive.com                        |
|Principal Engineer|http://www.centive.com                      |
|Centive           |My opinions are my own.                     |
|===============================================================|
|"Baldric, how did you manage to find a turnip that cost 400,000|
|pounds?" "Well, I had to haggle." --Blackadder III             |
\===============================================================/


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


From exim@www1.ietf.org  Tue May 11 15:25:37 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19458
	for <ietf-archive@odin.ietf.org>; Tue, 11 May 2004 15:25: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 1BNcmy-00043P-0b
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 15:19:46 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4BJJdmK015584
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 15:19:39 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNcXu-0003Pk-Iy; Tue, 11 May 2004 15:04:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNcTA-0006oO-5m
	for ietf@optimus.ietf.org; Tue, 11 May 2004 14:59:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16448
	for <ietf@ietf.org>; Tue, 11 May 2004 14:59: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 1BNcT7-0004Cb-8S
	for ietf@ietf.org; Tue, 11 May 2004 14:59:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNcSA-0003mi-00
	for ietf@ietf.org; Tue, 11 May 2004 14:58:11 -0400
Received: from carwash.centive.com ([65.220.90.249])
	by ietf-mx with smtp (Exim 4.12)
	id 1BNcRS-0003Bb-00
	for ietf@ietf.org; Tue, 11 May 2004 14:57:26 -0400
Received: from minglewood.incentivesystems.com ([10.10.30.25])
 by carwash.centive.com (SAVSMTP 3.1.3.37) with SMTP id M2004051114555606205
 ; Tue, 11 May 2004 14:55:56 -0400
Received: from [10.10.48.119] ([10.10.48.119]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Tue, 11 May 2004 14:51:00 -0400
Message-ID: <40A12093.7010100@centive.com>
Date: Tue, 11 May 2004 14:50:59 -0400
From: John Stracke <jstracke@centive.com>
User-Agent: Mozilla Thunderbird 0.6 (Windows/20040502)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Dean Anderson <dean@av8.com>
CC: Noel Chiappa <jnc@mercury.lcs.mit.edu>, ietf@ietf.org
Subject: Re: Complaint on abuse of DNSOP lists
References: <Pine.LNX.4.44.0405111419230.19722-100000@cirrus.av8.net>
In-Reply-To: <Pine.LNX.4.44.0405111419230.19722-100000@cirrus.av8.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 11 May 2004 18:51:00.0142 (UTC) FILETIME=[E6DB2CE0:01C43788]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-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

Dean Anderson wrote:

>One thing I've noticed is that of none of the people criticizing me has
>thought to address the fact that OUR ADDRESS SPACE IS NOT HIJACKED, and
>that these people associated with the IETF: Paul Vixie, Joe Abley, Bill
>Manning, and Rob Austein as WG Co-chair in his role for IETF business, all
>claim that it is.  But anyone can plainly see they are lying.
>  
>
No, actually, that's very difficult for anyone to see.  First off 
there's the simple matter that "hijacked" doesn't mean you hijacked it; 
as has already been pointed out, it could mean that someone else 
hijacked part of it from you.

Second there's the fact that ARIN lists your netblock as being assigned 
to the Open Software Foundation (with yourself as the contact).  It is 
impossible for an outsider to know whether or not the OSF transferred 
the block to av8.com legitimately.  I don't suspect it, you 
understand--nor do I much care--I'm just pointing out that it's not 
plain whether anybody here is lying.

-- 
/===============================================================\
|John Stracke      |jstracke@centive.com                        |
|Principal Engineer|http://www.centive.com                      |
|Centive           |My opinions are my own.                     |
|===============================================================|
|"Baldric, how did you manage to find a turnip that cost 400,000|
|pounds?" "Well, I had to haggle." --Blackadder III             |
\===============================================================/


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



From ietf-admin@ietf.org  Tue May 11 15:42:31 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20545
	for <ietf-archive@ietf.org>; Tue, 11 May 2004 15:42: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 1BNd96-0007lE-9T
	for ietf-archive@ietf.org; Tue, 11 May 2004 15:42:32 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNd8B-0007Gg-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 15:41:36 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNd6v-0006iZ-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 15:40:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNctA-0005UU-3Z; Tue, 11 May 2004 15:26:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNcmT-0003Y1-17
	for ietf@optimus.ietf.org; Tue, 11 May 2004 15:19: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 PAA18785
	for <ietf@ietf.org>; Tue, 11 May 2004 15:19: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 1BNcmR-00059q-6J
	for ietf@ietf.org; Tue, 11 May 2004 15:19:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNclY-0004js-00
	for ietf@ietf.org; Tue, 11 May 2004 15:18:13 -0400
Received: from [69.59.189.34] (helo=mail.ar.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNcks-000479-00
	for ietf@ietf.org; Tue, 11 May 2004 15:17:30 -0400
Received: by mail.ar.com (Postfix, from userid 1012)
	id 0DD8A14804B; Tue, 11 May 2004 12:58:40 -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 3A4AE14804A; Tue, 11 May 2004 12:58:36 -0700 (PDT)
Date: Tue, 11 May 2004 12:16:54 -0700 (PDT)
From: Rick Wesson <wessorh@ar.com>
To: Dean Anderson <dean@av8.com>
Cc: ietf@ietf.org
Subject: Re: Complaint on abuse of DNSOP lists
In-Reply-To: <Pine.LNX.4.44.0405111419230.19722-100000@cirrus.av8.net>
Message-ID: <Pine.LNX.4.58.0405111215520.1570@king.ar.com>
References: <Pine.LNX.4.44.0405111419230.19722-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=none autolearn=no version=2.60


Dean,

ok, i asked nicely and privately several times.
PLEASE! take this thread some place else.

-rick

On Tue, 11 May 2004, Dean Anderson wrote:

> On Mon, 10 May 2004, Noel Chiappa wrote:
>
> > So? Rob's not refusing to accept *any* email *at all* from you as a person
> > (just from a range of addresses which are generating email he doesn't like);
> > and you're more than savvy enough technically to get email to him via some
> > other path.
>
> As an IETF WG chair, he's obligated to follow the IETF rules on public
> participation.  He can't block anything that the IETF mail server can't
> block: Public Participants.
>
> > He's not under any more obligation to accept email from you via whatever
> > channel you feel like using, no matter how onerous for him, than he is to
> > accept messages written on 12' long oak logs of 3' diameter.
> >
> >
> > Get a life, will you? Your constant whining and flaming is really getting
> > old. You're getting really close to the line at which I'd ask the Chair to
> > ban you from posting. Oh wait, I know what your response would be - you'd sue
> > us. And you seem to think the rest of the world is doing things which is
> > making you look bad. Here's another free clue: you're doing a far better job
> > of that than the rest of us could do with a decade of free time.
>
> I'm entitled to particpate, and I'm entitled to send email to the WG
> chairs as a participant.
>
> One thing I've noticed is that of none of the people criticizing me has
> thought to address the fact that OUR ADDRESS SPACE IS NOT HIJACKED, and
> that these people associated with the IETF: Paul Vixie, Joe Abley, Bill
> Manning, and Rob Austein as WG Co-chair in his role for IETF business, all
> claim that it is.  But anyone can plainly see they are lying.
>
> Dean Anderson
> Av8 Internet, Inc
>
>
>
>
> _______________________________________________
> 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 May 11 15:51: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 PAA20981
	for <ietf-archive@odin.ietf.org>; Tue, 11 May 2004 15:51: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 1BNd6v-0000jB-IC
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 15:40:23 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4BJeHs2002786
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 15:40:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNctA-0005UU-3Z; Tue, 11 May 2004 15:26:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNcmT-0003Y1-17
	for ietf@optimus.ietf.org; Tue, 11 May 2004 15:19: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 PAA18785
	for <ietf@ietf.org>; Tue, 11 May 2004 15:19: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 1BNcmR-00059q-6J
	for ietf@ietf.org; Tue, 11 May 2004 15:19:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNclY-0004js-00
	for ietf@ietf.org; Tue, 11 May 2004 15:18:13 -0400
Received: from [69.59.189.34] (helo=mail.ar.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNcks-000479-00
	for ietf@ietf.org; Tue, 11 May 2004 15:17:30 -0400
Received: by mail.ar.com (Postfix, from userid 1012)
	id 0DD8A14804B; Tue, 11 May 2004 12:58:40 -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 3A4AE14804A; Tue, 11 May 2004 12:58:36 -0700 (PDT)
Date: Tue, 11 May 2004 12:16:54 -0700 (PDT)
From: Rick Wesson <wessorh@ar.com>
To: Dean Anderson <dean@av8.com>
Cc: ietf@ietf.org
Subject: Re: Complaint on abuse of DNSOP lists
In-Reply-To: <Pine.LNX.4.44.0405111419230.19722-100000@cirrus.av8.net>
Message-ID: <Pine.LNX.4.58.0405111215520.1570@king.ar.com>
References: <Pine.LNX.4.44.0405111419230.19722-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: 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>


Dean,

ok, i asked nicely and privately several times.
PLEASE! take this thread some place else.

-rick

On Tue, 11 May 2004, Dean Anderson wrote:

> On Mon, 10 May 2004, Noel Chiappa wrote:
>
> > So? Rob's not refusing to accept *any* email *at all* from you as a person
> > (just from a range of addresses which are generating email he doesn't like);
> > and you're more than savvy enough technically to get email to him via some
> > other path.
>
> As an IETF WG chair, he's obligated to follow the IETF rules on public
> participation.  He can't block anything that the IETF mail server can't
> block: Public Participants.
>
> > He's not under any more obligation to accept email from you via whatever
> > channel you feel like using, no matter how onerous for him, than he is to
> > accept messages written on 12' long oak logs of 3' diameter.
> >
> >
> > Get a life, will you? Your constant whining and flaming is really getting
> > old. You're getting really close to the line at which I'd ask the Chair to
> > ban you from posting. Oh wait, I know what your response would be - you'd sue
> > us. And you seem to think the rest of the world is doing things which is
> > making you look bad. Here's another free clue: you're doing a far better job
> > of that than the rest of us could do with a decade of free time.
>
> I'm entitled to particpate, and I'm entitled to send email to the WG
> chairs as a participant.
>
> One thing I've noticed is that of none of the people criticizing me has
> thought to address the fact that OUR ADDRESS SPACE IS NOT HIJACKED, and
> that these people associated with the IETF: Paul Vixie, Joe Abley, Bill
> Manning, and Rob Austein as WG Co-chair in his role for IETF business, all
> claim that it is.  But anyone can plainly see they are lying.
>
> Dean Anderson
> Av8 Internet, Inc
>
>
>
>
> _______________________________________________
> 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 May 11 15:55: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 PAA21201
	for <ietf-archive@ietf.org>; Tue, 11 May 2004 15:55: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 1BNdLf-0005Zc-7s
	for ietf-archive@ietf.org; Tue, 11 May 2004 15:55:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNdKi-000572-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 15:54:33 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNdJv-0004eU-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 15:53:43 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNd6x-0000nd-FW; Tue, 11 May 2004 15:40:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNd1v-0007KO-TH
	for ietf@optimus.ietf.org; Tue, 11 May 2004 15:35:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19962
	for <ietf@ietf.org>; Tue, 11 May 2004 15:35: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 1BNd1u-0004U0-4X
	for ietf@ietf.org; Tue, 11 May 2004 15:35:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNd0w-00043k-00
	for ietf@ietf.org; Tue, 11 May 2004 15:34:07 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNczu-0003Dx-00
	for ietf@ietf.org; Tue, 11 May 2004 15:33:02 -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 i4BJWRdl021531
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 11 May 2004 15:32:28 -0400
Date: Tue, 11 May 2004 15:32:27 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: bmanning@vacation.karoshi.com
cc: Ken Raeburn <raeburn@MIT.EDU>,
        Harald Tveit Alvestrand <harald@alvestrand.no>, <ietf@ietf.org>,
        "<dnsop@lists.uoregon.edu>" <dnsop@lists.uoregon.edu>
Subject: Re: [dnsop] Re: Complaint on abuse of DNSOP lists
In-Reply-To: <20040511181641.GA19823@vacation.karoshi.com.>
Message-ID: <Pine.LNX.4.44.0405111513370.19722-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 can't parse your statement.  I didn't say "assignment of IP space
__impunes__ a service". Perhaps you meant to say that your assignment of
IP address space to abusers doesn't impune the rest of your services. This
was the claim made by Media3 in Media3 v. MAPS.  Media3 lost.

But assignment of IP address space does indicate a relationship.  Your
denials of that relationship are frivolous.  Now, as in January, a close
read of your message reveals that you didn't actually _deny_ the
relationship, you tried to convince me that there was no _proof_ of any
relationship.  With regard to spam, we call such "deniable" relationships
"pink contracts".  The spam-hoster tries to deny that anyone has any proof
there is a relationship with the spammer.

I'd love to be able to say you were violating you AUP, but you don't have
one published.  Indeed, it is rather interesting that neither EP.NET (Bill
Manning), nor ISC.ORG (Paul Vixie) had published AUPs.

But as Media3 V. MAPS demonstrated, we can call a spade a spade.  You host
abusers, we can call you abuse-friendly.  

I suspect this is off-topic from the subject of abuse on DNSOP lists.  I
would like to redirect anyone who would like to continue this offlist. I
will shortly put all of your January emails and you current emails
regarding EP.NET and ISC.ORG on the web under IADL.ORG (Internet
Anti-Defamation League).

		--Dean




On Tue, 11 May 2004 bmanning@vacation.karoshi.com wrote:

> 
> 
> 	assignment of IP space does not impune any other
> 	service. Asserting otherwise is foolish.  Pressing
> 	the point, esp. in public fora, appears to be 
> 	willful ignorance.  Please enjoy your blissful state.
> 
> --bill
> 
> 
> On Tue, May 11, 2004 at 02:02:45PM -0400, Dean Anderson wrote:
> > The following message indicates that EP.NET has assigned an IP address to 
> > ISC.ORG.  You are quite well aware of this.  Dissembling will not help 
> > you.
> > 
> > 		--Dean 
> > 
> > 
> > Date: Thu, 15 Jan 2004 10:26:42 -0500 (EST)
> > From: Dean Anderson <dean@av8.com>
> > To: bill <bmanning@karoshi.com>
> > Subject: Re: Complaint regarding www.sorbs.net (204.152.186.189) (fwd)
> > 
> > 
> > On Wed, 14 Jan 2004, bill wrote:
> > 
> > >       I have no reason to act as your relay agent.  We have no
> > >       agreement in place for me to act in this manner.
> > 
> > The traceroute I forwarded shows that your IP addresses 198.32.176.4 is
> > assigned to ISC.ORG, which typically indicates a relationship.
> > 
> > >  8  paix-gw4.isc.org (198.32.176.4)  92.828 ms  91.036 ms  91.415 ms
> > 
> > On Mon, 10 May 2004 bmanning@vacation.karoshi.com wrote:
> > 
> > > > but ISC.ORG doesn't want to take a complaint. Bill Manning, of EP.NET
> > > > (ISC.ORG upstream) says he has no contract with me to accept complaints
> > > > about ISC.ORG.
> > > > 
> > > > 		--Dean
> > > 
> > > 	Dean... you are asserting a relationship that you have no 
> > > 	way to prove exists.  Unless or until you can prove that
> > > 	ep.net is an upstream for isc.org, please refrain from 
> > > 	making such statements.  Traceroute is not your friend in
> > > 	this case.  Defamation works many ways.
> > > 
> > > --bill
> > > 
> 


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


From exim@www1.ietf.org  Tue May 11 16:02:50 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 QAA21534
	for <ietf-archive@odin.ietf.org>; Tue, 11 May 2004 16:02: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 1BNdJw-0003UA-C6
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 15:53:50 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4BJriWv013394
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 15:53:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNd6x-0000nd-FW; Tue, 11 May 2004 15:40:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNd1v-0007KO-TH
	for ietf@optimus.ietf.org; Tue, 11 May 2004 15:35:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19962
	for <ietf@ietf.org>; Tue, 11 May 2004 15:35: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 1BNd1u-0004U0-4X
	for ietf@ietf.org; Tue, 11 May 2004 15:35:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNd0w-00043k-00
	for ietf@ietf.org; Tue, 11 May 2004 15:34:07 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNczu-0003Dx-00
	for ietf@ietf.org; Tue, 11 May 2004 15:33:02 -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 i4BJWRdl021531
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 11 May 2004 15:32:28 -0400
Date: Tue, 11 May 2004 15:32:27 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: bmanning@vacation.karoshi.com
cc: Ken Raeburn <raeburn@MIT.EDU>,
        Harald Tveit Alvestrand <harald@alvestrand.no>, <ietf@ietf.org>,
        "<dnsop@lists.uoregon.edu>" <dnsop@lists.uoregon.edu>
Subject: Re: [dnsop] Re: Complaint on abuse of DNSOP lists
In-Reply-To: <20040511181641.GA19823@vacation.karoshi.com.>
Message-ID: <Pine.LNX.4.44.0405111513370.19722-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 can't parse your statement.  I didn't say "assignment of IP space
__impunes__ a service". Perhaps you meant to say that your assignment of
IP address space to abusers doesn't impune the rest of your services. This
was the claim made by Media3 in Media3 v. MAPS.  Media3 lost.

But assignment of IP address space does indicate a relationship.  Your
denials of that relationship are frivolous.  Now, as in January, a close
read of your message reveals that you didn't actually _deny_ the
relationship, you tried to convince me that there was no _proof_ of any
relationship.  With regard to spam, we call such "deniable" relationships
"pink contracts".  The spam-hoster tries to deny that anyone has any proof
there is a relationship with the spammer.

I'd love to be able to say you were violating you AUP, but you don't have
one published.  Indeed, it is rather interesting that neither EP.NET (Bill
Manning), nor ISC.ORG (Paul Vixie) had published AUPs.

But as Media3 V. MAPS demonstrated, we can call a spade a spade.  You host
abusers, we can call you abuse-friendly.  

I suspect this is off-topic from the subject of abuse on DNSOP lists.  I
would like to redirect anyone who would like to continue this offlist. I
will shortly put all of your January emails and you current emails
regarding EP.NET and ISC.ORG on the web under IADL.ORG (Internet
Anti-Defamation League).

		--Dean




On Tue, 11 May 2004 bmanning@vacation.karoshi.com wrote:

> 
> 
> 	assignment of IP space does not impune any other
> 	service. Asserting otherwise is foolish.  Pressing
> 	the point, esp. in public fora, appears to be 
> 	willful ignorance.  Please enjoy your blissful state.
> 
> --bill
> 
> 
> On Tue, May 11, 2004 at 02:02:45PM -0400, Dean Anderson wrote:
> > The following message indicates that EP.NET has assigned an IP address to 
> > ISC.ORG.  You are quite well aware of this.  Dissembling will not help 
> > you.
> > 
> > 		--Dean 
> > 
> > 
> > Date: Thu, 15 Jan 2004 10:26:42 -0500 (EST)
> > From: Dean Anderson <dean@av8.com>
> > To: bill <bmanning@karoshi.com>
> > Subject: Re: Complaint regarding www.sorbs.net (204.152.186.189) (fwd)
> > 
> > 
> > On Wed, 14 Jan 2004, bill wrote:
> > 
> > >       I have no reason to act as your relay agent.  We have no
> > >       agreement in place for me to act in this manner.
> > 
> > The traceroute I forwarded shows that your IP addresses 198.32.176.4 is
> > assigned to ISC.ORG, which typically indicates a relationship.
> > 
> > >  8  paix-gw4.isc.org (198.32.176.4)  92.828 ms  91.036 ms  91.415 ms
> > 
> > On Mon, 10 May 2004 bmanning@vacation.karoshi.com wrote:
> > 
> > > > but ISC.ORG doesn't want to take a complaint. Bill Manning, of EP.NET
> > > > (ISC.ORG upstream) says he has no contract with me to accept complaints
> > > > about ISC.ORG.
> > > > 
> > > > 		--Dean
> > > 
> > > 	Dean... you are asserting a relationship that you have no 
> > > 	way to prove exists.  Unless or until you can prove that
> > > 	ep.net is an upstream for isc.org, please refrain from 
> > > 	making such statements.  Traceroute is not your friend in
> > > 	this case.  Defamation works many ways.
> > > 
> > > --bill
> > > 
> 


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



From ietf-admin@ietf.org  Tue May 11 17:13: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 RAA26109
	for <ietf-archive@ietf.org>; Tue, 11 May 2004 17:13: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 1BNeYh-0000Hr-P5
	for ietf-archive@ietf.org; Tue, 11 May 2004 17:13:03 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNeXK-0007QC-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 17:11:38 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNeVD-0006W2-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 17:09:27 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNeN4-000347-Tb; Tue, 11 May 2004 17:01:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNCiM-0004df-0d
	for ietf@optimus.ietf.org; Mon, 10 May 2004 11:29: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 LAA11228
	for <ietf@ietf.org>; Mon, 10 May 2004 11:29:06 -0400 (EDT)
From: ned.freed@mrochek.com
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNCiK-0004It-QU
	for ietf@ietf.org; Mon, 10 May 2004 11:29:08 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNChD-0003w6-00
	for ietf@ietf.org; Mon, 10 May 2004 11:28:00 -0400
Received: from mauve.mrochek.com ([209.55.107.55])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNCgg-0003bU-00
	for ietf@ietf.org; Mon, 10 May 2004 11:27:26 -0400
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243)
 id <01L9VM4DMHOW0062TI@mauve.mrochek.com> for ietf@ietf.org; Mon,
 10 May 2004 08:27:20 -0700 (PDT)
Date: Mon, 10 May 2004 08:20:44 -0700 (PDT)
Subject: Re: Not sure if this is the right place for this
In-reply-to: "Your message dated Mon, 10 May 2004 09:38:40 -0500"
 <409F93F0.5060300@ehsco.com>
To: "Eric A. Hall" <ehall@ehsco.com>
Cc: "RL 'Bob' Morgan" <rlmorgan@washington.edu>, John Rudd <john@rudd.cc>,
        IETF <ietf@ietf.org>
Message-id: <01L9X89J73W40062TI@mauve.mrochek.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=us-ascii
Content-transfer-encoding: 7BIT
Virus-test: FALSE
References: <DD72EEC3-A1E7-11D8-8626-003065F939FE@rudd.cc>
 <Pine.LNX.4.58.0405100019050.1405@perp.cac.washington.edu>
 <409F93F0.5060300@ehsco.com>
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.4 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7BIT


> On 5/10/2004 3:02 AM, RL 'Bob' Morgan wrote:

> > So a "secure ports only" policy has very little to do with security and
> > very much to do with organizational power relationships, and making
> > your computing environment dysfunctional.

> Somebody check my math on this please, but it seems to me that the whole
> STARTTLS approach is succeptible to a specific attack which the secure
> socket model is not.

Your "math" is incorrect in that both STARTTLS and the separate port approach
are vulnerable to this attack. In the separate port case an attacker has only
to block the separate port completely, forcing a fallback to the regular port.
(Not providing fallback in such cases is rarely a viable option.) It is also
possible to interfere with the TLS negotiation itself, causing negotiation of
unacceptably weak security.

All of these attacks can be twarted by requiring (on either the client or
server or both) a certain level of security. We've been providing the necessary
knobs to enforce this for quite a few years now; I'm fairly sure other vendors
have similar knobs.

> Unless that's wrong for some reason, I'd say that a "secure ports policy"
> actually is more secure.

It isn't. See above.

				Ned

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


From ietf-admin@ietf.org  Tue May 11 17:19: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 RAA26484
	for <ietf-archive@ietf.org>; Tue, 11 May 2004 17:19: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 1BNeef-0003EX-L0
	for ietf-archive@ietf.org; Tue, 11 May 2004 17:19:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNedg-0002nl-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 17:18:13 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNecW-000291-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 17:17:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNeN6-00036t-SQ; Tue, 11 May 2004 17:01:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BND4P-0000PX-Ga
	for ietf@optimus.ietf.org; Mon, 10 May 2004 11:51: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 LAA12400
	for <ietf@ietf.org>; Mon, 10 May 2004 11:51: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 1BND4O-00044y-5a
	for ietf@ietf.org; Mon, 10 May 2004 11:51:56 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BND3P-0003mN-00
	for ietf@ietf.org; Mon, 10 May 2004 11:50:56 -0400
Received: from mxout5.cac.washington.edu ([140.142.32.135])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BND2o-0003Tj-00
	for ietf@ietf.org; Mon, 10 May 2004 11:50:18 -0400
Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9])
	by mxout5.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4AFoEw4007301;
	Mon, 10 May 2004 08:50:14 -0700
Received: from [192.168.1.109] (c-67-170-59-55.client.comcast.net [67.170.59.55])
	(authenticated bits=0)
	by smtp.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4AFoCIN011877
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT);
	Mon, 10 May 2004 08:50:13 -0700
Date: Mon, 10 May 2004 08:50:08 -0700 (PDT)
From: "RL 'Bob' Morgan" <rlmorgan@washington.edu>
X-X-Sender: rlmorgan@perp.cac.washington.edu
To: "Eric A. Hall" <ehall@ehsco.com>
cc: IETF <ietf@ietf.org>
Subject: Re: Not sure if this is the right place for this
In-Reply-To: <409F93F0.5060300@ehsco.com>
Message-ID: <Pine.LNX.4.58.0405100810490.1405@perp.cac.washington.edu>
References: <DD72EEC3-A1E7-11D8-8626-003065F939FE@rudd.cc>
 <Pine.LNX.4.58.0405100019050.1405@perp.cac.washington.edu> <409F93F0.5060300@ehsco.com>
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


> > So a "secure ports only" policy has very little to do with security and
> > very much to do with organizational power relationships, and making
> > your computing environment dysfunctional.
>
> Somebody check my math on this please, but it seems to me that the whole
> STARTTLS approach is succeptible to a specific attack which the secure
> socket model is not.

A man-in-the-middle can just as easily (more easily, in fact, since it
doesn't require datastream modification) send back a port-unreachable to
the client's attempt to contact the foo-over-ssl port.  It is true, as you
imply, that if either the client or the server has a SSL/TLS-required
policy, then a non-SSL/TLS connection won't get made.  This policy can be
configured into endpoints using STARTTLS if that's desired.  If clients
and servers both permit the use of cleartext reusable passwords to be
negotiated, then a MITM will be able to force them into it in either case.

At a theoretical level there isn't much difference between the two
security-wise.  Arguments about which is better in practice depend on
assumptions about what implementors and deployers and users might or might
not do.  The underlying reason why the separate-port approach loses,
though, is that it makes simplistic assumptions about the relationships
between services on different ports.  Do imap://example.com/ and
imaps://example.com/ provide access to the same resource?  There's no
reason to believe that they do in the general case.  The separate-port
approach wires-in assumptions about "what's on a port" that are easily
circumvented later, both by bad guys and good guys (as we tend toward a
world where everything runs over port 80).

 - RL "Bob"


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


From ietf-admin@ietf.org  Tue May 11 17:23: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 RAA26672
	for <ietf-archive@ietf.org>; Tue, 11 May 2004 17:23: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 1BNeiW-00051b-85
	for ietf-archive@ietf.org; Tue, 11 May 2004 17:23:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNehT-0004X7-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 17:22:08 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNegK-0003hu-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 17:20:56 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNeN8-00038v-Sh; Tue, 11 May 2004 17:01:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNHpk-00057x-Jo
	for ietf@optimus.ietf.org; Mon, 10 May 2004 16:57: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 QAA03369
	for <ietf@ietf.org>; Mon, 10 May 2004 16:57: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 1BNHpi-0002GU-D3
	for ietf@ietf.org; Mon, 10 May 2004 16:57:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNHnj-0001eg-00
	for ietf@ietf.org; Mon, 10 May 2004 16:55:03 -0400
Received: from ihemail2.lucent.com ([192.11.222.163] helo=ihemail2.firewall.lucent.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNHma-0000sq-00
	for ietf@ietf.org; Mon, 10 May 2004 16:53:52 -0400
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by ihemail2.firewall.lucent.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i4AKrJB20599
	for <ietf@ietf.org>; Mon, 10 May 2004 15:53:19 -0500 (CDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72)
	id <JB9T20VL>; Mon, 10 May 2004 22:53:17 +0200
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550445E721@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Dean Anderson <dean@av8.com>, Pekka Savola <pekkas@netcore.fi>
Cc: Harald Tveit Alvestrand <harald@alvestrand.no>, ietf@ietf.org,
        dnsop@lists.uoregon.edu
Subject: RE: Complaint on abuse of DNSOP lists
Date: Mon, 10 May 2004 22:53:13 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
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

Speaking as OPS AD who is currently on-line.
The other OPS AD (David Kessens) is in the air and so is Harald.

Please refrain from this discussion on the DNSOP mailing list.

I have seen the complaint and will investigate and come with an
answer. The issue was between Dean and one of Rob Austein's email
addresses, so I do not see a need to discuss this on this mailing
list. So I declare this subject as a topic that is NOT a DNSOP
mailing list topic. Pls refrain from posting to this list on
this topic.

Thanks,
Bert (OPS AD)

> -----Original Message-----
> From: Dean Anderson [mailto:dean@av8.com]
> Sent: maandag 10 mei 2004 22:10
> To: Pekka Savola
> Cc: Harald Tveit Alvestrand; ietf@ietf.org; dnsop@lists.uoregon.edu
> Subject: Re: Complaint on abuse of DNSOP lists
> 
> 
> On Mon, 10 May 2004, Pekka Savola wrote:
> 
> > On Mon, 10 May 2004, Dean Anderson wrote:
> > > Point of order, please
> > > 
> > > It seems that WG co-chair has begun to use an email 
> address that is 
> > > defaming Av8 Internet, Inc by returning business email to 
> users of Av8 
> > > Internet claiming that Av8 Internet has hijacked some 
> address space.
> > > 
> > > Av8 Internet hereby demands that the IETF immediately end 
> this behavior
> > > and halt the defamation of Av8 Internet, Inc by IETF 
> representatives.  
> > > IETF representatives must use email addresses that are 
> not configured for
> > > defamation of Av8 Internet, Inc.
> > 
> > If you look at the message, you will note that it is a 
> bounce from the
> > WG co-chair's _personal_ email address, directly to your email
> > address.
> 
> Actually, it bounces this way to all Av8 Internet Customers, 
> not just to
> me.  But it was a bounce to a message Mr. Austein posted on 
> DNSOP. It was
> not private business. It was IETF business.
> 
> Further, by reviewing the archives of DNSOP, I have found that Mr.  
> Austein's home address is <sra+dnsop@hactrn.net>, which he has used
> exclusively for some time until March 1st of this year. He 
> first started
> using the ISC.ORG address on a message involving
> draft-ietf-dnsop-inadr-required. Perhaps coincidentally, this 
> draft is a
> pet project of Mr. Austeins, and one to which I (and many others) have
> raised serious objections regarding both misleading and 
> incorrect content
> and procedural irregularities.  The archives show that since 
> March 1st,
> 2004, Mr.  Austein has made all his DNSOP posts from sra@isc.org.  
> 
> > I'd say that everyone has the right to choose what mail to 
> accept (or
> > not to accept).
> 
> They don't when they are conducting IETF business. IETF rules 
> require that
> participants not be excluded from IETF activities. WG chairs 
> and others
> cannot refuse email from participants.
> 
> As Joe Abley revealed previously, this configuration from 
> ISC.ORG isn't
> meant to actually block spam. The idea is to make Av8 
> Internet users have
> to seek other email addresses by which to contact them, and to obtain
> opportunities to defame Av8 Internet and perhaps others and 
> convince users
> to seek other services. This is unlawful.  Besides the defamation, it
> would is an illegal group boycott, and an unfair business practice.
> 
> Refusing email is one thing, though that is still not 
> permitted for IETF
> business.  Defamation by claiming addresses are hijacked is 
> quite another
> thing. This abuse of email addresses is unacceptable, and 
> illegal, and I
> can engage legal action if necessary to prevent an 
> organization like the
> IETF from permitting this abuse to continue.
> 
> Mr. Austein cannot be allowed to use the ISC.ORG address for IETF
> business.
> 
> > You might or might not have a point if this behaviour 
> happened on an 
> > IETF list, but that is not the case..
> 
> Actually, it is the case. This involves two IETF lists, and 
> the conduct of
> an IETF representative on the DNSOP list. My republishing of 
> Mr. Austein's
> defamation to the DNSOP and IETF list to make a complaint is a
> republishment for which Mr.  Austein and the IETF are legally 
> responsible
> under US defamation tort law.
> 
> Mr Austein as a representative of the IETF defamed Av8 
> Internet to me, to
> the customers of Av8 Internet, and to the readership of both 
> the IETF and
> DNSOP lists.  Mr. Austein is a co-chair of the IETF working 
> group.  This
> defamation came about through IETF working group business.
> 
> The IETF is responsible for the conduct of its representatives on its
> lists.  It is unlawful to permit its representatives to use addresses
> which are configured to defame IETF participants, and it is 
> against the
> IETF rules to refuse email from IETF participants.
> 
> Dean Anderson
> President
> Av8 Internet, Inc
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
> _______________________________________________
> 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).
> 

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


From ietf-admin@ietf.org  Tue May 11 17:23: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 RAA26706
	for <ietf-archive@ietf.org>; Tue, 11 May 2004 17:23: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 1BNeil-00053O-TZ
	for ietf-archive@ietf.org; Tue, 11 May 2004 17:23:28 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNehg-0004Z1-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 17:22:21 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNege-000460-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 17: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 1BNeNA-0003BP-9S; Tue, 11 May 2004 17:01:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNJc8-0000Rt-LL
	for ietf@optimus.ietf.org; Mon, 10 May 2004 18:51:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14277
	for <ietf@ietf.org>; Mon, 10 May 2004 18:51: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 1BNJc5-0004Gu-CO
	for ietf@ietf.org; Mon, 10 May 2004 18:51:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNJb3-0003vs-00
	for ietf@ietf.org; Mon, 10 May 2004 18:50:06 -0400
Received: from vacation.karoshi.com ([198.32.6.68] helo=karoshi.com.)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNJa4-0003TI-00
	for ietf@ietf.org; Mon, 10 May 2004 18:49:04 -0400
Received: from karoshi.com (localhost.localdomain [127.0.0.1])
	by karoshi.com. (8.12.8/8.12.8) with ESMTP id i4AMmxNw017791;
	Mon, 10 May 2004 22:48:59 GMT
Received: (from bmanning@localhost)
	by karoshi.com (8.12.8/8.12.8/Submit) id i4AMmxPD017788;
	Mon, 10 May 2004 22:48:59 GMT
Date: Mon, 10 May 2004 22:48:59 +0000
From: bmanning@vacation.karoshi.com
To: Dean Anderson <dean@av8.com>
Cc: Ken Raeburn <raeburn@MIT.EDU>,
        Harald Tveit Alvestrand <harald@alvestrand.no>, ietf@ietf.org,
        "<dnsop@lists.uoregon.edu>" <dnsop@lists.uoregon.edu>
Subject: Re: [dnsop] Re: Complaint on abuse of DNSOP lists
Message-ID: <20040510224859.GA17723@vacation.karoshi.com.>
References: <FFF45958-A2B6-11D8-B627-000A95909EE2@mit.edu> <Pine.LNX.4.44.0405101610410.25030-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.0405101610410.25030-100000@cirrus.av8.net>
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.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60

> but ISC.ORG doesn't want to take a complaint. Bill Manning, of EP.NET
> (ISC.ORG upstream) says he has no contract with me to accept complaints
> about ISC.ORG.
> 
> 		--Dean

	Dean... you are asserting a relationship that you have no 
	way to prove exists.  Unless or until you can prove that
	ep.net is an upstream for isc.org, please refrain from 
	making such statements.  Traceroute is not your friend in
	this case.  Defamation works many ways.

--bill

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


From ietf-admin@ietf.org  Tue May 11 17:26: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 RAA26912
	for <ietf-archive@ietf.org>; Tue, 11 May 2004 17:26: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 1BNelT-0006U5-Im
	for ietf-archive@ietf.org; Tue, 11 May 2004 17:26:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNekQ-0005zo-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 17:25:11 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNejH-0005Ax-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 17:23:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNeNB-0003CL-NV; Tue, 11 May 2004 17:01:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNaZx-0004uc-7z
	for ietf@optimus.ietf.org; Tue, 11 May 2004 12:58:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08395
	for <ietf@ietf.org>; Tue, 11 May 2004 12:58:00 -0400 (EDT)
From: ned.freed@mrochek.com
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNaZu-00062O-GZ
	for ietf@ietf.org; Tue, 11 May 2004 12:58:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNaZ1-0005cM-00
	for ietf@ietf.org; Tue, 11 May 2004 12:57:07 -0400
Received: from mauve.mrochek.com ([209.55.107.55])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNaY7-0005CL-00
	for ietf@ietf.org; Tue, 11 May 2004 12:56:11 -0400
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243)
 id <01L9XYTYVR0G0062TI@mauve.mrochek.com> for ietf@ietf.org; Tue,
 11 May 2004 09:56:03 -0700 (PDT)
Date: Tue, 11 May 2004 09:37:34 -0700 (PDT)
Subject: Re: Not sure if this is the right place for this
In-reply-to: "Your message dated Tue, 11 May 2004 07:53:16 -0700"
 <p0610050ebcc6979bb9ca@[10.20.30.249]>
To: Paul Hoffman / VPNC <paul.hoffman@vpnc.org>
Cc: "Eric A. Hall" <ehall@ehsco.com>, IETF <ietf@ietf.org>
Message-id: <01L9YPMWCQMG0062TI@mauve.mrochek.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
Virus-test: FALSE
References: <DD72EEC3-A1E7-11D8-8626-003065F939FE@rudd.cc>
 <Pine.LNX.4.58.0405100019050.1405@perp.cac.washington.edu>
 <409F93F0.5060300@ehsco.com> <p06100532bcc54f129dec@[10.20.30.249]>
 <40A07E47.4060906@ehsco.com> <p0610050ebcc6979bb9ca@[10.20.30.249]>
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.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7BIT

> > On the other hand, STARTTLS *requires* a clear channel that the client
> > MUST *already* be using. So whereas the attack on SSL *might* succeed in
> > putting the client in touch with an unencrypted service, TLS is
> > *guaranteed* to be using such a service already anyway. The only question
> > is whether or not a decipherable login can be used, which is a probability
> > mask that also applies to the SSL scenario.

> Exactly right. This is the strongest argument in favor of protected
> ports over STARTTLS.

Another argument in favor of separate ports is an implementation issue: It is
fairly common in large scale deployments to have specialized hardware to
perform SSL/TLS stuff, and that hardware often is not resident on the same
machines that offer POP/SMTP/IMAP services. This means that proxy that delves a
bit into the underlying protocol is needed to do STARTTLS. Unfortunately
proxies are in practice responsible for far more bugs you'd expect and the
proxy has to dig into the protocol the worse things get. Separate ports, on the
other hand, are much easier to implement on a front end.

The counter argument to this is the separation of the SSL/TLS layer from the
protocol layer is actually a bad thing security-wise. More specifically, when
it is done as a separate layer information about the SSL/TLS negotiation tends
to remain at that layer. Not making this information available to the
application protocol makes implementation of some security schemes, including
but not limited to SASL external, problematic.

So, while STARTTLS is in some senses more complex, it is useful complexity.

IMO this counterargument is fairly compelling. Add in the other issues that
come up with separate ports (RL Bob" Morgan has already summarized them nicely
so I see no reason to repeat them here) leads me to conclude that STARTTLS is
the way to go.

				Ned

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


From ietf-admin@ietf.org  Tue May 11 17:26: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 RAA26966
	for <ietf-archive@ietf.org>; Tue, 11 May 2004 17:26: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 1BNels-0006X1-3a
	for ietf-archive@ietf.org; Tue, 11 May 2004 17:26:40 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNeks-00063w-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 17:25:39 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNejz-0005aP-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 17:24:43 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNeND-0003DR-5N; Tue, 11 May 2004 17:01:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNbpO-0005lS-B0
	for ietf@optimus.ietf.org; Tue, 11 May 2004 14:18: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 OAA13621
	for <ietf@ietf.org>; Tue, 11 May 2004 14:18: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 1BNbpL-0001l6-HN
	for ietf@ietf.org; Tue, 11 May 2004 14:18:03 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNboQ-0001MG-00
	for ietf@ietf.org; Tue, 11 May 2004 14:17:07 -0400
Received: from vacation.karoshi.com ([198.32.6.68] helo=karoshi.com.)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNbo6-0000x3-00
	for ietf@ietf.org; Tue, 11 May 2004 14:16:46 -0400
Received: from karoshi.com (localhost.localdomain [127.0.0.1])
	by karoshi.com. (8.12.8/8.12.8) with ESMTP id i4BIGfNw019850;
	Tue, 11 May 2004 18:16:41 GMT
Received: (from bmanning@localhost)
	by karoshi.com (8.12.8/8.12.8/Submit) id i4BIGfxx019847;
	Tue, 11 May 2004 18:16:41 GMT
Date: Tue, 11 May 2004 18:16:41 +0000
From: bmanning@vacation.karoshi.com
To: Dean Anderson <dean@av8.com>
Cc: bmanning@vacation.karoshi.com, Ken Raeburn <raeburn@MIT.EDU>,
        Harald Tveit Alvestrand <harald@alvestrand.no>, ietf@ietf.org,
        "<dnsop@lists.uoregon.edu>" <dnsop@lists.uoregon.edu>
Subject: Re: [dnsop] Re: Complaint on abuse of DNSOP lists
Message-ID: <20040511181641.GA19823@vacation.karoshi.com.>
References: <20040510224859.GA17723@vacation.karoshi.com.> <Pine.LNX.4.44.0405111401380.19722-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.0405111401380.19722-100000@cirrus.av8.net>
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.3 required=5.0 tests=NO_REAL_NAME autolearn=no 
	version=2.60



	assignment of IP space does not impune any other
	service. Asserting otherwise is foolish.  Pressing
	the point, esp. in public fora, appears to be 
	willful ignorance.  Please enjoy your blissful state.

--bill


On Tue, May 11, 2004 at 02:02:45PM -0400, Dean Anderson wrote:
> The following message indicates that EP.NET has assigned an IP address to 
> ISC.ORG.  You are quite well aware of this.  Dissembling will not help 
> you.
> 
> 		--Dean 
> 
> 
> Date: Thu, 15 Jan 2004 10:26:42 -0500 (EST)
> From: Dean Anderson <dean@av8.com>
> To: bill <bmanning@karoshi.com>
> Subject: Re: Complaint regarding www.sorbs.net (204.152.186.189) (fwd)
> 
> 
> On Wed, 14 Jan 2004, bill wrote:
> 
> >       I have no reason to act as your relay agent.  We have no
> >       agreement in place for me to act in this manner.
> 
> The traceroute I forwarded shows that your IP addresses 198.32.176.4 is
> assigned to ISC.ORG, which typically indicates a relationship.
> 
> >  8  paix-gw4.isc.org (198.32.176.4)  92.828 ms  91.036 ms  91.415 ms
> 
> On Mon, 10 May 2004 bmanning@vacation.karoshi.com wrote:
> 
> > > but ISC.ORG doesn't want to take a complaint. Bill Manning, of EP.NET
> > > (ISC.ORG upstream) says he has no contract with me to accept complaints
> > > about ISC.ORG.
> > > 
> > > 		--Dean
> > 
> > 	Dean... you are asserting a relationship that you have no 
> > 	way to prove exists.  Unless or until you can prove that
> > 	ep.net is an upstream for isc.org, please refrain from 
> > 	making such statements.  Traceroute is not your friend in
> > 	this case.  Defamation works many ways.
> > 
> > --bill
> > 

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


From exim@www1.ietf.org  Tue May 11 17:36: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 RAA27557
	for <ietf-archive@odin.ietf.org>; Tue, 11 May 2004 17:36: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 1BNeVF-0005kQ-Eo
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 17:09:39 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4BL9Tsa022066
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 17:09:29 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNeN4-000347-Tb; Tue, 11 May 2004 17:01:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNCiM-0004df-0d
	for ietf@optimus.ietf.org; Mon, 10 May 2004 11:29: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 LAA11228
	for <ietf@ietf.org>; Mon, 10 May 2004 11:29:06 -0400 (EDT)
From: ned.freed@mrochek.com
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNCiK-0004It-QU
	for ietf@ietf.org; Mon, 10 May 2004 11:29:08 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNChD-0003w6-00
	for ietf@ietf.org; Mon, 10 May 2004 11:28:00 -0400
Received: from mauve.mrochek.com ([209.55.107.55])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNCgg-0003bU-00
	for ietf@ietf.org; Mon, 10 May 2004 11:27:26 -0400
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243)
 id <01L9VM4DMHOW0062TI@mauve.mrochek.com> for ietf@ietf.org; Mon,
 10 May 2004 08:27:20 -0700 (PDT)
Date: Mon, 10 May 2004 08:20:44 -0700 (PDT)
Subject: Re: Not sure if this is the right place for this
In-reply-to: "Your message dated Mon, 10 May 2004 09:38:40 -0500"
 <409F93F0.5060300@ehsco.com>
To: "Eric A. Hall" <ehall@ehsco.com>
Cc: "RL 'Bob' Morgan" <rlmorgan@washington.edu>, John Rudd <john@rudd.cc>,
        IETF <ietf@ietf.org>
Message-id: <01L9X89J73W40062TI@mauve.mrochek.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=us-ascii
Content-transfer-encoding: 7BIT
Virus-test: FALSE
References: <DD72EEC3-A1E7-11D8-8626-003065F939FE@rudd.cc>
 <Pine.LNX.4.58.0405100019050.1405@perp.cac.washington.edu>
 <409F93F0.5060300@ehsco.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,NO_REAL_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


> On 5/10/2004 3:02 AM, RL 'Bob' Morgan wrote:

> > So a "secure ports only" policy has very little to do with security and
> > very much to do with organizational power relationships, and making
> > your computing environment dysfunctional.

> Somebody check my math on this please, but it seems to me that the whole
> STARTTLS approach is succeptible to a specific attack which the secure
> socket model is not.

Your "math" is incorrect in that both STARTTLS and the separate port approach
are vulnerable to this attack. In the separate port case an attacker has only
to block the separate port completely, forcing a fallback to the regular port.
(Not providing fallback in such cases is rarely a viable option.) It is also
possible to interfere with the TLS negotiation itself, causing negotiation of
unacceptably weak security.

All of these attacks can be twarted by requiring (on either the client or
server or both) a certain level of security. We've been providing the necessary
knobs to enforce this for quite a few years now; I'm fairly sure other vendors
have similar knobs.

> Unless that's wrong for some reason, I'd say that a "secure ports policy"
> actually is more secure.

It isn't. See above.

				Ned

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



From exim@www1.ietf.org  Tue May 11 17:37:04 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 RAA27641
	for <ietf-archive@odin.ietf.org>; Tue, 11 May 2004 17:37: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 1BNecY-0007OY-39
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 17:17:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4BLH26J028411
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 17:17:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNeN6-00036t-SQ; Tue, 11 May 2004 17:01:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BND4P-0000PX-Ga
	for ietf@optimus.ietf.org; Mon, 10 May 2004 11:51: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 LAA12400
	for <ietf@ietf.org>; Mon, 10 May 2004 11:51: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 1BND4O-00044y-5a
	for ietf@ietf.org; Mon, 10 May 2004 11:51:56 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BND3P-0003mN-00
	for ietf@ietf.org; Mon, 10 May 2004 11:50:56 -0400
Received: from mxout5.cac.washington.edu ([140.142.32.135])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BND2o-0003Tj-00
	for ietf@ietf.org; Mon, 10 May 2004 11:50:18 -0400
Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9])
	by mxout5.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4AFoEw4007301;
	Mon, 10 May 2004 08:50:14 -0700
Received: from [192.168.1.109] (c-67-170-59-55.client.comcast.net [67.170.59.55])
	(authenticated bits=0)
	by smtp.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4AFoCIN011877
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT);
	Mon, 10 May 2004 08:50:13 -0700
Date: Mon, 10 May 2004 08:50:08 -0700 (PDT)
From: "RL 'Bob' Morgan" <rlmorgan@washington.edu>
X-X-Sender: rlmorgan@perp.cac.washington.edu
To: "Eric A. Hall" <ehall@ehsco.com>
cc: IETF <ietf@ietf.org>
Subject: Re: Not sure if this is the right place for this
In-Reply-To: <409F93F0.5060300@ehsco.com>
Message-ID: <Pine.LNX.4.58.0405100810490.1405@perp.cac.washington.edu>
References: <DD72EEC3-A1E7-11D8-8626-003065F939FE@rudd.cc>
 <Pine.LNX.4.58.0405100019050.1405@perp.cac.washington.edu> <409F93F0.5060300@ehsco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: 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 a "secure ports only" policy has very little to do with security and
> > very much to do with organizational power relationships, and making
> > your computing environment dysfunctional.
>
> Somebody check my math on this please, but it seems to me that the whole
> STARTTLS approach is succeptible to a specific attack which the secure
> socket model is not.

A man-in-the-middle can just as easily (more easily, in fact, since it
doesn't require datastream modification) send back a port-unreachable to
the client's attempt to contact the foo-over-ssl port.  It is true, as you
imply, that if either the client or the server has a SSL/TLS-required
policy, then a non-SSL/TLS connection won't get made.  This policy can be
configured into endpoints using STARTTLS if that's desired.  If clients
and servers both permit the use of cleartext reusable passwords to be
negotiated, then a MITM will be able to force them into it in either case.

At a theoretical level there isn't much difference between the two
security-wise.  Arguments about which is better in practice depend on
assumptions about what implementors and deployers and users might or might
not do.  The underlying reason why the separate-port approach loses,
though, is that it makes simplistic assumptions about the relationships
between services on different ports.  Do imap://example.com/ and
imaps://example.com/ provide access to the same resource?  There's no
reason to believe that they do in the general case.  The separate-port
approach wires-in assumptions about "what's on a port" that are easily
circumvented later, both by bad guys and good guys (as we tend toward a
world where everything runs over port 80).

 - RL "Bob"


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



From exim@www1.ietf.org  Tue May 11 17:37:27 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 RAA27675
	for <ietf-archive@odin.ietf.org>; Tue, 11 May 2004 17:37:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNek0-00028u-Uv
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 17:24:51 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4BLOiiX008232
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 17:24:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNeND-0003DR-5N; Tue, 11 May 2004 17:01:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNbpO-0005lS-B0
	for ietf@optimus.ietf.org; Tue, 11 May 2004 14:18: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 OAA13621
	for <ietf@ietf.org>; Tue, 11 May 2004 14:18: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 1BNbpL-0001l6-HN
	for ietf@ietf.org; Tue, 11 May 2004 14:18:03 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNboQ-0001MG-00
	for ietf@ietf.org; Tue, 11 May 2004 14:17:07 -0400
Received: from vacation.karoshi.com ([198.32.6.68] helo=karoshi.com.)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNbo6-0000x3-00
	for ietf@ietf.org; Tue, 11 May 2004 14:16:46 -0400
Received: from karoshi.com (localhost.localdomain [127.0.0.1])
	by karoshi.com. (8.12.8/8.12.8) with ESMTP id i4BIGfNw019850;
	Tue, 11 May 2004 18:16:41 GMT
Received: (from bmanning@localhost)
	by karoshi.com (8.12.8/8.12.8/Submit) id i4BIGfxx019847;
	Tue, 11 May 2004 18:16:41 GMT
Date: Tue, 11 May 2004 18:16:41 +0000
From: bmanning@vacation.karoshi.com
To: Dean Anderson <dean@av8.com>
Cc: bmanning@vacation.karoshi.com, Ken Raeburn <raeburn@MIT.EDU>,
        Harald Tveit Alvestrand <harald@alvestrand.no>, ietf@ietf.org,
        "<dnsop@lists.uoregon.edu>" <dnsop@lists.uoregon.edu>
Subject: Re: [dnsop] Re: Complaint on abuse of DNSOP lists
Message-ID: <20040511181641.GA19823@vacation.karoshi.com.>
References: <20040510224859.GA17723@vacation.karoshi.com.> <Pine.LNX.4.44.0405111401380.19722-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.0405111401380.19722-100000@cirrus.av8.net>
User-Agent: Mutt/1.4.1i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME 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>



	assignment of IP space does not impune any other
	service. Asserting otherwise is foolish.  Pressing
	the point, esp. in public fora, appears to be 
	willful ignorance.  Please enjoy your blissful state.

--bill


On Tue, May 11, 2004 at 02:02:45PM -0400, Dean Anderson wrote:
> The following message indicates that EP.NET has assigned an IP address to 
> ISC.ORG.  You are quite well aware of this.  Dissembling will not help 
> you.
> 
> 		--Dean 
> 
> 
> Date: Thu, 15 Jan 2004 10:26:42 -0500 (EST)
> From: Dean Anderson <dean@av8.com>
> To: bill <bmanning@karoshi.com>
> Subject: Re: Complaint regarding www.sorbs.net (204.152.186.189) (fwd)
> 
> 
> On Wed, 14 Jan 2004, bill wrote:
> 
> >       I have no reason to act as your relay agent.  We have no
> >       agreement in place for me to act in this manner.
> 
> The traceroute I forwarded shows that your IP addresses 198.32.176.4 is
> assigned to ISC.ORG, which typically indicates a relationship.
> 
> >  8  paix-gw4.isc.org (198.32.176.4)  92.828 ms  91.036 ms  91.415 ms
> 
> On Mon, 10 May 2004 bmanning@vacation.karoshi.com wrote:
> 
> > > but ISC.ORG doesn't want to take a complaint. Bill Manning, of EP.NET
> > > (ISC.ORG upstream) says he has no contract with me to accept complaints
> > > about ISC.ORG.
> > > 
> > > 		--Dean
> > 
> > 	Dean... you are asserting a relationship that you have no 
> > 	way to prove exists.  Unless or until you can prove that
> > 	ep.net is an upstream for isc.org, please refrain from 
> > 	making such statements.  Traceroute is not your friend in
> > 	this case.  Defamation works many ways.
> > 
> > --bill
> > 

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



From ietf-admin@ietf.org  Tue May 11 17:38:58 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27784
	for <ietf-archive@ietf.org>; Tue, 11 May 2004 17:38: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 1BNexn-0004FW-Hf
	for ietf-archive@ietf.org; Tue, 11 May 2004 17:38:59 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNewK-0003dl-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 17:37:28 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNevV-0003Bp-01
	for ietf-archive@ietf.org; Tue, 11 May 2004 17:36:37 -0400
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BNes3-0005nR-CD
	for ietf-archive@ietf.org; Tue, 11 May 2004 17: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 1BNeQ0-00044J-3p; Tue, 11 May 2004 17:04:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNeEg-0001B7-Az
	for ietf@optimus.ietf.org; Tue, 11 May 2004 16:52: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 QAA24528
	for <ietf@ietf.org>; Tue, 11 May 2004 16:52: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 1BNeEb-0007GJ-S7
	for ietf@ietf.org; Tue, 11 May 2004 16:52:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNeDW-0006qi-00
	for ietf@ietf.org; Tue, 11 May 2004 16:51:10 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNeCr-0006FX-00
	for ietf@ietf.org; Tue, 11 May 2004 16:50:30 -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 i4BKnp8J022895
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 11 May 2004 16:49:53 -0400
Date: Tue, 11 May 2004 16:49:51 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Rick Wesson <wessorh@ar.com>
cc: ietf@ietf.org
Subject: Re: Complaint on abuse of DNSOP lists
In-Reply-To: <Pine.LNX.4.58.0405111215520.1570@king.ar.com>
Message-ID: <Pine.LNX.4.44.0405111646070.19722-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

Where would you suggest I take it?  

It says in the IETF mission statement:

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


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

How can one have an open process if WG chairs don't receive email?

How can it be taken off-list if IETF staff don't receive email?

Your request seems to be contradictory.

		--Dean



On Tue, 11 May 2004, Rick Wesson wrote:

> 
> Dean,
> 
> ok, i asked nicely and privately several times.
> PLEASE! take this thread some place else.
> 
> -rick
> 
> On Tue, 11 May 2004, Dean Anderson wrote:
> 
> > On Mon, 10 May 2004, Noel Chiappa wrote:
> >
> > > So? Rob's not refusing to accept *any* email *at all* from you as a person
> > > (just from a range of addresses which are generating email he doesn't like);
> > > and you're more than savvy enough technically to get email to him via some
> > > other path.
> >
> > As an IETF WG chair, he's obligated to follow the IETF rules on public
> > participation.  He can't block anything that the IETF mail server can't
> > block: Public Participants.
> >
> > > He's not under any more obligation to accept email from you via whatever
> > > channel you feel like using, no matter how onerous for him, than he is to
> > > accept messages written on 12' long oak logs of 3' diameter.
> > >
> > >
> > > Get a life, will you? Your constant whining and flaming is really getting
> > > old. You're getting really close to the line at which I'd ask the Chair to
> > > ban you from posting. Oh wait, I know what your response would be - you'd sue
> > > us. And you seem to think the rest of the world is doing things which is
> > > making you look bad. Here's another free clue: you're doing a far better job
> > > of that than the rest of us could do with a decade of free time.
> >
> > I'm entitled to particpate, and I'm entitled to send email to the WG
> > chairs as a participant.
> >
> > One thing I've noticed is that of none of the people criticizing me has
> > thought to address the fact that OUR ADDRESS SPACE IS NOT HIJACKED, and
> > that these people associated with the IETF: Paul Vixie, Joe Abley, Bill
> > Manning, and Rob Austein as WG Co-chair in his role for IETF business, all
> > claim that it is.  But anyone can plainly see they are lying.
> >
> > Dean Anderson
> > Av8 Internet, Inc
> >
> >
> >
> >
> > _______________________________________________
> > 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 May 11 17:38:58 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 RAA27797
	for <ietf-archive@odin.ietf.org>; Tue, 11 May 2004 17:38:58 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNeno-0003L8-BA
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 17:28:40 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4BLSebm012829
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 17:28:40 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNeNE-0003Dk-Gl; Tue, 11 May 2004 17:01:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNd1x-0007KQ-A7
	for ietf@optimus.ietf.org; Tue, 11 May 2004 15:35: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 PAA19968
	for <ietf@ietf.org>; Tue, 11 May 2004 15:35: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 1BNd1v-0004UD-Nb
	for ietf@ietf.org; Tue, 11 May 2004 15:35:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNd10-00044E-00
	for ietf@ietf.org; Tue, 11 May 2004 15:34:10 -0400
Received: from darkwing.uoregon.edu ([128.223.142.13] ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNd00-0003ct-00
	for ietf@ietf.org; Tue, 11 May 2004 15:33:08 -0400
Received: from darkwing.uoregon.edu (llynch@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i4BJX4Wb016390;
	Tue, 11 May 2004 12:33:04 -0700 (PDT)
Received: from localhost (llynch@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) with ESMTP id i4BJX4Ff016385;
	Tue, 11 May 2004 12:33:04 -0700 (PDT)
Date: Tue, 11 May 2004 12:33:04 -0700 (PDT)
From: "Lucy E. Lynch" <llynch@darkwing.uoregon.edu>
To: Dean Anderson <dean@av8.com>
cc: Harald Tveit Alvestrand <harald@alvestrand.no>, ietf@ietf.org,
        dnsop@lists.uoregon.edu
Subject: Re: [dnsop] Re: Complaint on abuse of DNSOP lists
In-Reply-To: <Pine.LNX.4.44.0405111357560.19722-100000@cirrus.av8.net>
Message-ID: <Pine.GSO.4.58.0405111231060.28408@darkwing.uoregon.edu>
References: <Pine.LNX.4.44.0405111357560.19722-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: 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>

DNSOP list members -

A friendly reminder about the list setup:

DNSOP, the Domain Name System Operations WG list.

Questions about the administration of this list should be addressed to
owner-dnsop@lists.uoregon.edu

Posts intended for the entire list should be addressed to
dnsop@lists.uoregon.edu

If you plan to post from more than one email address, please send a
list of secondary posting addresses to: owner-dnsop@lists.uoregon.edu
with a subjecy line that reads: dnsop secondary posting request

To unsubscribe yourself from this list send a message to
'majordomo@lists.uoregon.edu' with the contents:

unsubscribe dnsop
end

or go to the web based user interface:
http://darkwing.uoregon.edu/~llynch/dnsop.html

The Mhonarc web archive can be found here:
http://darkwing.uoregon.edu/~llynch/dnsop/index.html

A list of the  text archive files (month by month) can be found by
sending an index request (index dnsop) to majordomo@lists.uoregon.edu
and files can be retrived using the majordomo get command:

get dnsop dnsop.archive.xxx
-------------------------------------------------------------------
Note that the list is archived is several ways and in several places,
so anyone can read the WG list at their pleasure.

Lucy E. Lynch 				Academic User Services
Computing Center			University of Oregon
llynch  @darkwing.uoregon.edu		(541) 346-1774/Cell: 912-7998

On Tue, 11 May 2004, Dean Anderson wrote:

> On Mon, 10 May 2004, Harald Tveit Alvestrand wrote:
>
> > Dean,
> >
> > third time same complaint, third time same answer.
> >
> > No.
> >
> > A WG chair is expected to read mail coming from the working group list.
> > What he does with copies that go directly to him is his own business.
>
> I disagree. A WG chair has to read email from participants, including
> off-list email.  Certain complaints and business needs to be handled
> off-list.
>
> > And as I have told you on the previous two instances of this complaint:
> > Personal mail to you, including bounce messages, is not someone defaming
> > you in the IETF, even when you choose to make it public.
>
> I disagree, and I believe the IETF attorney has advised you otherwise.
> The previous complaints involving Paul Vixie and Joe Abley regarded their
> roles as participants, not as representatives of the IETF.
>
> Dean Anderson
> Av8 Internet, Inc
>
> .
> dnsop resources:_____________________________________________________
> web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
> mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html
>

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



From exim@www1.ietf.org  Tue May 11 17:39:06 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 RAA27840
	for <ietf-archive@odin.ietf.org>; Tue, 11 May 2004 17:39: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 1BNeor-0003oO-11
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 17:29:45 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4BLTikk014646
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 17:29:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNeNG-0003ES-2u; Tue, 11 May 2004 17:01:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNdpJ-00024T-VX
	for ietf@optimus.ietf.org; Tue, 11 May 2004 16:26: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 QAA22739
	for <ietf@ietf.org>; Tue, 11 May 2004 16:26:06 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNdpH-0003JJ-ND
	for ietf@ietf.org; Tue, 11 May 2004 16:26:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNdoI-0002qw-00
	for ietf@ietf.org; Tue, 11 May 2004 16:25:07 -0400
Received: from vacation.karoshi.com ([198.32.6.68] helo=karoshi.com.)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNdnK-0002O9-00
	for ietf@ietf.org; Tue, 11 May 2004 16:24:06 -0400
Received: from karoshi.com (localhost.localdomain [127.0.0.1])
	by karoshi.com. (8.12.8/8.12.8) with ESMTP id i4BKO1Nw020099;
	Tue, 11 May 2004 20:24:01 GMT
Received: (from bmanning@localhost)
	by karoshi.com (8.12.8/8.12.8/Submit) id i4BKNwPg020096;
	Tue, 11 May 2004 20:23:58 GMT
Date: Tue, 11 May 2004 20:23:58 +0000
From: bmanning@vacation.karoshi.com
To: Dean Anderson <dean@av8.com>
Cc: bmanning@vacation.karoshi.com, Ken Raeburn <raeburn@MIT.EDU>,
        Harald Tveit Alvestrand <harald@alvestrand.no>, ietf@ietf.org,
        "<dnsop@lists.uoregon.edu>" <dnsop@lists.uoregon.edu>
Subject: Re: [dnsop] Re: Complaint on abuse of DNSOP lists
Message-ID: <20040511202358.GA19883@vacation.karoshi.com.>
References: <20040511181641.GA19823@vacation.karoshi.com.> <Pine.LNX.4.44.0405111513370.19722-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.0405111513370.19722-100000@cirrus.av8.net>
User-Agent: Mutt/1.4.1i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=NO_REAL_NAME 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>

 if you are serious, please feel free to contact your legal council
 to persue remedies.  


On Tue, May 11, 2004 at 03:32:27PM -0400, Dean Anderson wrote:
> I can't parse your statement.  I didn't say "assignment of IP space
> __impunes__ a service". Perhaps you meant to say that your assignment of
> IP address space to abusers doesn't impune the rest of your services. This
> was the claim made by Media3 in Media3 v. MAPS.  Media3 lost.
> 
> But assignment of IP address space does indicate a relationship.  Your
> denials of that relationship are frivolous.  Now, as in January, a close
> read of your message reveals that you didn't actually _deny_ the
> relationship, you tried to convince me that there was no _proof_ of any
> relationship.  With regard to spam, we call such "deniable" relationships
> "pink contracts".  The spam-hoster tries to deny that anyone has any proof
> there is a relationship with the spammer.
> 
> I'd love to be able to say you were violating you AUP, but you don't have
> one published.  Indeed, it is rather interesting that neither EP.NET (Bill
> Manning), nor ISC.ORG (Paul Vixie) had published AUPs.
> 
> But as Media3 V. MAPS demonstrated, we can call a spade a spade.  You host
> abusers, we can call you abuse-friendly.  
> 
> I suspect this is off-topic from the subject of abuse on DNSOP lists.  I
> would like to redirect anyone who would like to continue this offlist. I
> will shortly put all of your January emails and you current emails
> regarding EP.NET and ISC.ORG on the web under IADL.ORG (Internet
> Anti-Defamation League).
> 
> 		--Dean
> 
> 
> 
> 
> On Tue, 11 May 2004 bmanning@vacation.karoshi.com wrote:
> 
> > 
> > 
> > 	assignment of IP space does not impune any other
> > 	service. Asserting otherwise is foolish.  Pressing
> > 	the point, esp. in public fora, appears to be 
> > 	willful ignorance.  Please enjoy your blissful state.
> > 
> > --bill
> > 
> > 
> > On Tue, May 11, 2004 at 02:02:45PM -0400, Dean Anderson wrote:
> > > The following message indicates that EP.NET has assigned an IP address to 
> > > ISC.ORG.  You are quite well aware of this.  Dissembling will not help 
> > > you.
> > > 
> > > 		--Dean 
> > > 
> > > 
> > > Date: Thu, 15 Jan 2004 10:26:42 -0500 (EST)
> > > From: Dean Anderson <dean@av8.com>
> > > To: bill <bmanning@karoshi.com>
> > > Subject: Re: Complaint regarding www.sorbs.net (204.152.186.189) (fwd)
> > > 
> > > 
> > > On Wed, 14 Jan 2004, bill wrote:
> > > 
> > > >       I have no reason to act as your relay agent.  We have no
> > > >       agreement in place for me to act in this manner.
> > > 
> > > The traceroute I forwarded shows that your IP addresses 198.32.176.4 is
> > > assigned to ISC.ORG, which typically indicates a relationship.
> > > 
> > > >  8  paix-gw4.isc.org (198.32.176.4)  92.828 ms  91.036 ms  91.415 ms
> > > 
> > > On Mon, 10 May 2004 bmanning@vacation.karoshi.com wrote:
> > > 
> > > > > but ISC.ORG doesn't want to take a complaint. Bill Manning, of EP.NET
> > > > > (ISC.ORG upstream) says he has no contract with me to accept complaints
> > > > > about ISC.ORG.
> > > > > 
> > > > > 		--Dean
> > > > 
> > > > 	Dean... you are asserting a relationship that you have no 
> > > > 	way to prove exists.  Unless or until you can prove that
> > > > 	ep.net is an upstream for isc.org, please refrain from 
> > > > 	making such statements.  Traceroute is not your friend in
> > > > 	this case.  Defamation works many ways.
> > > > 
> > > > --bill
> > > > 
> > 

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



From ietf-admin@ietf.org  Tue May 11 17:39: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 RAA27871
	for <ietf-archive@ietf.org>; Tue, 11 May 2004 17:39: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 1BNey6-0004VC-LD
	for ietf-archive@ietf.org; Tue, 11 May 2004 17:39:18 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNewd-0003gZ-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 17:37:48 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNevZ-0003Bt-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 17:36:41 -0400
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BNeot-0005iD-J1
	for ietf-archive@ietf.org; Tue, 11 May 2004 17:29:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNeNG-0003ES-2u; Tue, 11 May 2004 17:01:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNdpJ-00024T-VX
	for ietf@optimus.ietf.org; Tue, 11 May 2004 16:26: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 QAA22739
	for <ietf@ietf.org>; Tue, 11 May 2004 16:26:06 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNdpH-0003JJ-ND
	for ietf@ietf.org; Tue, 11 May 2004 16:26:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNdoI-0002qw-00
	for ietf@ietf.org; Tue, 11 May 2004 16:25:07 -0400
Received: from vacation.karoshi.com ([198.32.6.68] helo=karoshi.com.)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNdnK-0002O9-00
	for ietf@ietf.org; Tue, 11 May 2004 16:24:06 -0400
Received: from karoshi.com (localhost.localdomain [127.0.0.1])
	by karoshi.com. (8.12.8/8.12.8) with ESMTP id i4BKO1Nw020099;
	Tue, 11 May 2004 20:24:01 GMT
Received: (from bmanning@localhost)
	by karoshi.com (8.12.8/8.12.8/Submit) id i4BKNwPg020096;
	Tue, 11 May 2004 20:23:58 GMT
Date: Tue, 11 May 2004 20:23:58 +0000
From: bmanning@vacation.karoshi.com
To: Dean Anderson <dean@av8.com>
Cc: bmanning@vacation.karoshi.com, Ken Raeburn <raeburn@MIT.EDU>,
        Harald Tveit Alvestrand <harald@alvestrand.no>, ietf@ietf.org,
        "<dnsop@lists.uoregon.edu>" <dnsop@lists.uoregon.edu>
Subject: Re: [dnsop] Re: Complaint on abuse of DNSOP lists
Message-ID: <20040511202358.GA19883@vacation.karoshi.com.>
References: <20040511181641.GA19823@vacation.karoshi.com.> <Pine.LNX.4.44.0405111513370.19722-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.0405111513370.19722-100000@cirrus.av8.net>
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.3 required=5.0 tests=NO_REAL_NAME autolearn=no 
	version=2.60

 if you are serious, please feel free to contact your legal council
 to persue remedies.  


On Tue, May 11, 2004 at 03:32:27PM -0400, Dean Anderson wrote:
> I can't parse your statement.  I didn't say "assignment of IP space
> __impunes__ a service". Perhaps you meant to say that your assignment of
> IP address space to abusers doesn't impune the rest of your services. This
> was the claim made by Media3 in Media3 v. MAPS.  Media3 lost.
> 
> But assignment of IP address space does indicate a relationship.  Your
> denials of that relationship are frivolous.  Now, as in January, a close
> read of your message reveals that you didn't actually _deny_ the
> relationship, you tried to convince me that there was no _proof_ of any
> relationship.  With regard to spam, we call such "deniable" relationships
> "pink contracts".  The spam-hoster tries to deny that anyone has any proof
> there is a relationship with the spammer.
> 
> I'd love to be able to say you were violating you AUP, but you don't have
> one published.  Indeed, it is rather interesting that neither EP.NET (Bill
> Manning), nor ISC.ORG (Paul Vixie) had published AUPs.
> 
> But as Media3 V. MAPS demonstrated, we can call a spade a spade.  You host
> abusers, we can call you abuse-friendly.  
> 
> I suspect this is off-topic from the subject of abuse on DNSOP lists.  I
> would like to redirect anyone who would like to continue this offlist. I
> will shortly put all of your January emails and you current emails
> regarding EP.NET and ISC.ORG on the web under IADL.ORG (Internet
> Anti-Defamation League).
> 
> 		--Dean
> 
> 
> 
> 
> On Tue, 11 May 2004 bmanning@vacation.karoshi.com wrote:
> 
> > 
> > 
> > 	assignment of IP space does not impune any other
> > 	service. Asserting otherwise is foolish.  Pressing
> > 	the point, esp. in public fora, appears to be 
> > 	willful ignorance.  Please enjoy your blissful state.
> > 
> > --bill
> > 
> > 
> > On Tue, May 11, 2004 at 02:02:45PM -0400, Dean Anderson wrote:
> > > The following message indicates that EP.NET has assigned an IP address to 
> > > ISC.ORG.  You are quite well aware of this.  Dissembling will not help 
> > > you.
> > > 
> > > 		--Dean 
> > > 
> > > 
> > > Date: Thu, 15 Jan 2004 10:26:42 -0500 (EST)
> > > From: Dean Anderson <dean@av8.com>
> > > To: bill <bmanning@karoshi.com>
> > > Subject: Re: Complaint regarding www.sorbs.net (204.152.186.189) (fwd)
> > > 
> > > 
> > > On Wed, 14 Jan 2004, bill wrote:
> > > 
> > > >       I have no reason to act as your relay agent.  We have no
> > > >       agreement in place for me to act in this manner.
> > > 
> > > The traceroute I forwarded shows that your IP addresses 198.32.176.4 is
> > > assigned to ISC.ORG, which typically indicates a relationship.
> > > 
> > > >  8  paix-gw4.isc.org (198.32.176.4)  92.828 ms  91.036 ms  91.415 ms
> > > 
> > > On Mon, 10 May 2004 bmanning@vacation.karoshi.com wrote:
> > > 
> > > > > but ISC.ORG doesn't want to take a complaint. Bill Manning, of EP.NET
> > > > > (ISC.ORG upstream) says he has no contract with me to accept complaints
> > > > > about ISC.ORG.
> > > > > 
> > > > > 		--Dean
> > > > 
> > > > 	Dean... you are asserting a relationship that you have no 
> > > > 	way to prove exists.  Unless or until you can prove that
> > > > 	ep.net is an upstream for isc.org, please refrain from 
> > > > 	making such statements.  Traceroute is not your friend in
> > > > 	this case.  Defamation works many ways.
> > > > 
> > > > --bill
> > > > 
> > 

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


From ietf-admin@ietf.org  Tue May 11 17:39: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 RAA27892
	for <ietf-archive@ietf.org>; Tue, 11 May 2004 17:39: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 1BNey7-0004WR-VD
	for ietf-archive@ietf.org; Tue, 11 May 2004 17:39:19 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNewf-0003gq-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 17:37:50 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNevb-0003Bg-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 17:36:43 -0400
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BNent-0005hR-Fi
	for ietf-archive@ietf.org; Tue, 11 May 2004 17:28:45 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNeNE-0003Dk-Gl; Tue, 11 May 2004 17:01:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNd1x-0007KQ-A7
	for ietf@optimus.ietf.org; Tue, 11 May 2004 15:35: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 PAA19968
	for <ietf@ietf.org>; Tue, 11 May 2004 15:35: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 1BNd1v-0004UD-Nb
	for ietf@ietf.org; Tue, 11 May 2004 15:35:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNd10-00044E-00
	for ietf@ietf.org; Tue, 11 May 2004 15:34:10 -0400
Received: from darkwing.uoregon.edu ([128.223.142.13] ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNd00-0003ct-00
	for ietf@ietf.org; Tue, 11 May 2004 15:33:08 -0400
Received: from darkwing.uoregon.edu (llynch@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i4BJX4Wb016390;
	Tue, 11 May 2004 12:33:04 -0700 (PDT)
Received: from localhost (llynch@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) with ESMTP id i4BJX4Ff016385;
	Tue, 11 May 2004 12:33:04 -0700 (PDT)
Date: Tue, 11 May 2004 12:33:04 -0700 (PDT)
From: "Lucy E. Lynch" <llynch@darkwing.uoregon.edu>
To: Dean Anderson <dean@av8.com>
cc: Harald Tveit Alvestrand <harald@alvestrand.no>, ietf@ietf.org,
        dnsop@lists.uoregon.edu
Subject: Re: [dnsop] Re: Complaint on abuse of DNSOP lists
In-Reply-To: <Pine.LNX.4.44.0405111357560.19722-100000@cirrus.av8.net>
Message-ID: <Pine.GSO.4.58.0405111231060.28408@darkwing.uoregon.edu>
References: <Pine.LNX.4.44.0405111357560.19722-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=none autolearn=no version=2.60

DNSOP list members -

A friendly reminder about the list setup:

DNSOP, the Domain Name System Operations WG list.

Questions about the administration of this list should be addressed to
owner-dnsop@lists.uoregon.edu

Posts intended for the entire list should be addressed to
dnsop@lists.uoregon.edu

If you plan to post from more than one email address, please send a
list of secondary posting addresses to: owner-dnsop@lists.uoregon.edu
with a subjecy line that reads: dnsop secondary posting request

To unsubscribe yourself from this list send a message to
'majordomo@lists.uoregon.edu' with the contents:

unsubscribe dnsop
end

or go to the web based user interface:
http://darkwing.uoregon.edu/~llynch/dnsop.html

The Mhonarc web archive can be found here:
http://darkwing.uoregon.edu/~llynch/dnsop/index.html

A list of the  text archive files (month by month) can be found by
sending an index request (index dnsop) to majordomo@lists.uoregon.edu
and files can be retrived using the majordomo get command:

get dnsop dnsop.archive.xxx
-------------------------------------------------------------------
Note that the list is archived is several ways and in several places,
so anyone can read the WG list at their pleasure.

Lucy E. Lynch 				Academic User Services
Computing Center			University of Oregon
llynch  @darkwing.uoregon.edu		(541) 346-1774/Cell: 912-7998

On Tue, 11 May 2004, Dean Anderson wrote:

> On Mon, 10 May 2004, Harald Tveit Alvestrand wrote:
>
> > Dean,
> >
> > third time same complaint, third time same answer.
> >
> > No.
> >
> > A WG chair is expected to read mail coming from the working group list.
> > What he does with copies that go directly to him is his own business.
>
> I disagree. A WG chair has to read email from participants, including
> off-list email.  Certain complaints and business needs to be handled
> off-list.
>
> > And as I have told you on the previous two instances of this complaint:
> > Personal mail to you, including bounce messages, is not someone defaming
> > you in the IETF, even when you choose to make it public.
>
> I disagree, and I believe the IETF attorney has advised you otherwise.
> The previous complaints involving Paul Vixie and Joe Abley regarded their
> roles as participants, not as representatives of the IETF.
>
> Dean Anderson
> Av8 Internet, Inc
>
> .
> dnsop resources:_____________________________________________________
> web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
> mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html
>

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


From exim@www1.ietf.org  Tue May 11 17:41: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 RAA28165
	for <ietf-archive@odin.ietf.org>; Tue, 11 May 2004 17:41: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 1BNerk-0004jj-UR
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 17:32:44 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4BLWi7H018199
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 17:32:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNeQ0-00044J-3p; Tue, 11 May 2004 17:04:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNeEg-0001B7-Az
	for ietf@optimus.ietf.org; Tue, 11 May 2004 16:52: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 QAA24528
	for <ietf@ietf.org>; Tue, 11 May 2004 16:52: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 1BNeEb-0007GJ-S7
	for ietf@ietf.org; Tue, 11 May 2004 16:52:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNeDW-0006qi-00
	for ietf@ietf.org; Tue, 11 May 2004 16:51:10 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNeCr-0006FX-00
	for ietf@ietf.org; Tue, 11 May 2004 16:50:30 -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 i4BKnp8J022895
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 11 May 2004 16:49:53 -0400
Date: Tue, 11 May 2004 16:49:51 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Rick Wesson <wessorh@ar.com>
cc: ietf@ietf.org
Subject: Re: Complaint on abuse of DNSOP lists
In-Reply-To: <Pine.LNX.4.58.0405111215520.1570@king.ar.com>
Message-ID: <Pine.LNX.4.44.0405111646070.19722-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>

Where would you suggest I take it?  

It says in the IETF mission statement:

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


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

How can one have an open process if WG chairs don't receive email?

How can it be taken off-list if IETF staff don't receive email?

Your request seems to be contradictory.

		--Dean



On Tue, 11 May 2004, Rick Wesson wrote:

> 
> Dean,
> 
> ok, i asked nicely and privately several times.
> PLEASE! take this thread some place else.
> 
> -rick
> 
> On Tue, 11 May 2004, Dean Anderson wrote:
> 
> > On Mon, 10 May 2004, Noel Chiappa wrote:
> >
> > > So? Rob's not refusing to accept *any* email *at all* from you as a person
> > > (just from a range of addresses which are generating email he doesn't like);
> > > and you're more than savvy enough technically to get email to him via some
> > > other path.
> >
> > As an IETF WG chair, he's obligated to follow the IETF rules on public
> > participation.  He can't block anything that the IETF mail server can't
> > block: Public Participants.
> >
> > > He's not under any more obligation to accept email from you via whatever
> > > channel you feel like using, no matter how onerous for him, than he is to
> > > accept messages written on 12' long oak logs of 3' diameter.
> > >
> > >
> > > Get a life, will you? Your constant whining and flaming is really getting
> > > old. You're getting really close to the line at which I'd ask the Chair to
> > > ban you from posting. Oh wait, I know what your response would be - you'd sue
> > > us. And you seem to think the rest of the world is doing things which is
> > > making you look bad. Here's another free clue: you're doing a far better job
> > > of that than the rest of us could do with a decade of free time.
> >
> > I'm entitled to particpate, and I'm entitled to send email to the WG
> > chairs as a participant.
> >
> > One thing I've noticed is that of none of the people criticizing me has
> > thought to address the fact that OUR ADDRESS SPACE IS NOT HIJACKED, and
> > that these people associated with the IETF: Paul Vixie, Joe Abley, Bill
> > Manning, and Rob Austein as WG Co-chair in his role for IETF business, all
> > claim that it is.  But anyone can plainly see they are lying.
> >
> > Dean Anderson
> > Av8 Internet, Inc
> >
> >
> >
> >
> > _______________________________________________
> > 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 May 11 17:45: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 RAA28406
	for <ietf-archive@ietf.org>; Tue, 11 May 2004 17:45: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 1BNf43-0007Qg-NR
	for ietf-archive@ietf.org; Tue, 11 May 2004 17:45:27 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNf36-0006yK-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 17:44:28 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNf2L-0006Wg-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 17:43:41 -0400
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BNf2G-00063q-Jn
	for ietf-archive@ietf.org; Tue, 11 May 2004 17:43:37 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNev6-0005hs-VZ; Tue, 11 May 2004 17:36:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNeSR-0004kW-OF
	for ietf@optimus.ietf.org; Tue, 11 May 2004 17:06: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 RAA25539
	for <ietf@ietf.org>; Tue, 11 May 2004 17:06: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 1BNeSO-0005n5-UL
	for ietf@ietf.org; Tue, 11 May 2004 17:06:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNeRP-0005Iy-00
	for ietf@ietf.org; Tue, 11 May 2004 17:05:32 -0400
Received: from felix.automagic.org ([204.152.186.101])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNeQh-0004r6-00
	for ietf@ietf.org; Tue, 11 May 2004 17:04:47 -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 1BNeQU-0006j6-ES; Tue, 11 May 2004 21:04:34 +0000
In-Reply-To: <Pine.LNX.4.44.0405101516140.25030-100000@cirrus.av8.net>
References: <Pine.LNX.4.44.0405101516140.25030-100000@cirrus.av8.net>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <CC27502C-A38E-11D8-8085-000A95E7E6B4@isc.org>
Content-Transfer-Encoding: 7bit
Cc: Pekka Savola <pekkas@netcore.fi>,
        Harald Tveit Alvestrand <harald@alvestrand.no>,
        <dnsop@lists.uoregon.edu>, <ietf@ietf.org>
From: Joe Abley <jabley@isc.org>
Subject: Re: Complaint on abuse of DNSOP lists
Date: Tue, 11 May 2004 17:04:31 -0400
To: Dean Anderson <dean@av8.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 10 May 2004, at 16:10, Dean Anderson wrote:

> As Joe Abley revealed previously, this configuration from ISC.ORG isn't
> meant to actually block spam.

What?


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


From ietf-admin@ietf.org  Tue May 11 17:55:33 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29405
	for <ietf-archive@ietf.org>; Tue, 11 May 2004 17:55: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 1BNfDq-0004L1-No
	for ietf-archive@ietf.org; Tue, 11 May 2004 17:55:34 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNfCp-0003qC-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 17:54:32 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNfBe-0003Ms-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 17:53:18 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNewS-0006Ng-2u; Tue, 11 May 2004 17:37:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNeY3-0006Xl-J7
	for ietf@optimus.ietf.org; Tue, 11 May 2004 17:12:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26046
	for <ietf@ietf.org>; Tue, 11 May 2004 17:12: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 1BNeY1-00004C-AI
	for ietf@ietf.org; Tue, 11 May 2004 17:12:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNeW9-0006t8-00
	for ietf@ietf.org; Tue, 11 May 2004 17:10:25 -0400
Received: from felix.automagic.org ([204.152.186.101])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNeSv-0005rX-00
	for ietf@ietf.org; Tue, 11 May 2004 17:07:05 -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 1BNeSv-0006jx-4b; Tue, 11 May 2004 21:07:05 +0000
In-Reply-To: <Pine.LNX.4.44.0405111419230.19722-100000@cirrus.av8.net>
References: <Pine.LNX.4.44.0405111419230.19722-100000@cirrus.av8.net>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <26D104AE-A38F-11D8-8085-000A95E7E6B4@isc.org>
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, Noel Chiappa <jnc@mercury.lcs.mit.edu>
From: Joe Abley <jabley@isc.org>
Subject: Re: Complaint on abuse of DNSOP lists
Date: Tue, 11 May 2004 17:07:03 -0400
To: Dean Anderson <dean@av8.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 11 May 2004, at 14:26, Dean Anderson wrote:

> One thing I've noticed is that of none of the people criticizing me has
> thought to address the fact that OUR ADDRESS SPACE IS NOT HIJACKED, and
> that these people associated with the IETF: Paul Vixie, Joe Abley, Bill
> Manning, and Rob Austein as WG Co-chair in his role for IETF business, 
> all
> claim that it is.

What?


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


From ietf-admin@ietf.org  Tue May 11 17:58: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 RAA29614
	for <ietf-archive@ietf.org>; Tue, 11 May 2004 17:58: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 1BNfGQ-0005jp-Lm
	for ietf-archive@ietf.org; Tue, 11 May 2004 17:58:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNfFP-0005GP-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 17:57:12 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNfEJ-0004cQ-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 17:56:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNewc-0006R4-SW; Tue, 11 May 2004 17:37:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNeZH-0006n6-QI
	for ietf@optimus.ietf.org; Tue, 11 May 2004 17:13:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26196
	for <ietf@ietf.org>; Tue, 11 May 2004 17:13: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 1BNeZF-0000eL-HD
	for ietf@ietf.org; Tue, 11 May 2004 17:13:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNeYH-00009J-00
	for ietf@ietf.org; Tue, 11 May 2004 17:12:37 -0400
Received: from felix.automagic.org ([204.152.186.101])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNeWg-0006zg-00
	for ietf@ietf.org; Tue, 11 May 2004 17:10:58 -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 1BNeWf-0006k6-1j; Tue, 11 May 2004 21:10:57 +0000
In-Reply-To: <Pine.LNX.4.44.0405111401380.19722-100000@cirrus.av8.net>
References: <Pine.LNX.4.44.0405111401380.19722-100000@cirrus.av8.net>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <B0D6533C-A38F-11D8-8085-000A95E7E6B4@isc.org>
Content-Transfer-Encoding: 7bit
Cc: Harald Tveit Alvestrand <harald@alvestrand.no>,
        "<dnsop@lists.uoregon.edu>" <dnsop@lists.uoregon.edu>, <ietf@ietf.org>,
        bmanning@vacation.karoshi.com, Ken Raeburn <raeburn@MIT.EDU>
From: Joe Abley <jabley@isc.org>
Subject: Re: [dnsop] Re: Complaint on abuse of DNSOP lists
Date: Tue, 11 May 2004 17:10:54 -0400
To: Dean Anderson <dean@av8.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 11 May 2004, at 14:02, Dean Anderson wrote:

> The following message indicates that EP.NET has assigned an IP address 
> to
> ISC.ORG.  You are quite well aware of this.  Dissembling will not help
> you.

For the benefit of less-operational people here who don't see humour in 
this, 198.32.176.0/24 is the PAIX IPv4 peering fabric in the Bay Area.

Some of Dean's mail servers are listed on SORBS. ISC's MXes use SORBS. 
Perhaps we should move on.


Joe


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


From exim@www1.ietf.org  Tue May 11 18:02:01 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 SAA29978
	for <ietf-archive@odin.ietf.org>; Tue, 11 May 2004 18:02: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 1BNf2M-0000S4-1j
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 17:43:43 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4BLhb0D001472
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 17:43:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNev6-0005hs-VZ; Tue, 11 May 2004 17:36:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNeSR-0004kW-OF
	for ietf@optimus.ietf.org; Tue, 11 May 2004 17:06: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 RAA25539
	for <ietf@ietf.org>; Tue, 11 May 2004 17:06: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 1BNeSO-0005n5-UL
	for ietf@ietf.org; Tue, 11 May 2004 17:06:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNeRP-0005Iy-00
	for ietf@ietf.org; Tue, 11 May 2004 17:05:32 -0400
Received: from felix.automagic.org ([204.152.186.101])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNeQh-0004r6-00
	for ietf@ietf.org; Tue, 11 May 2004 17:04:47 -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 1BNeQU-0006j6-ES; Tue, 11 May 2004 21:04:34 +0000
In-Reply-To: <Pine.LNX.4.44.0405101516140.25030-100000@cirrus.av8.net>
References: <Pine.LNX.4.44.0405101516140.25030-100000@cirrus.av8.net>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <CC27502C-A38E-11D8-8085-000A95E7E6B4@isc.org>
Content-Transfer-Encoding: 7bit
Cc: Pekka Savola <pekkas@netcore.fi>,
        Harald Tveit Alvestrand <harald@alvestrand.no>,
        <dnsop@lists.uoregon.edu>, <ietf@ietf.org>
From: Joe Abley <jabley@isc.org>
Subject: Re: Complaint on abuse of DNSOP lists
Date: Tue, 11 May 2004 17:04:31 -0400
To: Dean Anderson <dean@av8.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 10 May 2004, at 16:10, Dean Anderson wrote:

> As Joe Abley revealed previously, this configuration from ISC.ORG isn't
> meant to actually block spam.

What?


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



From exim@www1.ietf.org  Tue May 11 18:06: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 SAA00406
	for <ietf-archive@odin.ietf.org>; Tue, 11 May 2004 18:06: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 1BNfBf-0002wZ-VO
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 17:53:20 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4BLrJri011246
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 17:53:19 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNewS-0006Ng-2u; Tue, 11 May 2004 17:37:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNeY3-0006Xl-J7
	for ietf@optimus.ietf.org; Tue, 11 May 2004 17:12:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26046
	for <ietf@ietf.org>; Tue, 11 May 2004 17:12: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 1BNeY1-00004C-AI
	for ietf@ietf.org; Tue, 11 May 2004 17:12:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNeW9-0006t8-00
	for ietf@ietf.org; Tue, 11 May 2004 17:10:25 -0400
Received: from felix.automagic.org ([204.152.186.101])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNeSv-0005rX-00
	for ietf@ietf.org; Tue, 11 May 2004 17:07:05 -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 1BNeSv-0006jx-4b; Tue, 11 May 2004 21:07:05 +0000
In-Reply-To: <Pine.LNX.4.44.0405111419230.19722-100000@cirrus.av8.net>
References: <Pine.LNX.4.44.0405111419230.19722-100000@cirrus.av8.net>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <26D104AE-A38F-11D8-8085-000A95E7E6B4@isc.org>
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, Noel Chiappa <jnc@mercury.lcs.mit.edu>
From: Joe Abley <jabley@isc.org>
Subject: Re: Complaint on abuse of DNSOP lists
Date: Tue, 11 May 2004 17:07:03 -0400
To: Dean Anderson <dean@av8.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 11 May 2004, at 14:26, Dean Anderson wrote:

> One thing I've noticed is that of none of the people criticizing me has
> thought to address the fact that OUR ADDRESS SPACE IS NOT HIJACKED, and
> that these people associated with the IETF: Paul Vixie, Joe Abley, Bill
> Manning, and Rob Austein as WG Co-chair in his role for IETF business, 
> all
> claim that it is.

What?


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



From exim@www1.ietf.org  Tue May 11 18:06: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 SAA00483
	for <ietf-archive@odin.ietf.org>; Tue, 11 May 2004 18:06: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 1BNfEM-0003xx-9I
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 17:56:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4BLu6VK015084
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 17:56:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNewc-0006R4-SW; Tue, 11 May 2004 17:37:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNeZH-0006n6-QI
	for ietf@optimus.ietf.org; Tue, 11 May 2004 17:13:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26196
	for <ietf@ietf.org>; Tue, 11 May 2004 17:13: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 1BNeZF-0000eL-HD
	for ietf@ietf.org; Tue, 11 May 2004 17:13:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNeYH-00009J-00
	for ietf@ietf.org; Tue, 11 May 2004 17:12:37 -0400
Received: from felix.automagic.org ([204.152.186.101])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNeWg-0006zg-00
	for ietf@ietf.org; Tue, 11 May 2004 17:10:58 -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 1BNeWf-0006k6-1j; Tue, 11 May 2004 21:10:57 +0000
In-Reply-To: <Pine.LNX.4.44.0405111401380.19722-100000@cirrus.av8.net>
References: <Pine.LNX.4.44.0405111401380.19722-100000@cirrus.av8.net>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <B0D6533C-A38F-11D8-8085-000A95E7E6B4@isc.org>
Content-Transfer-Encoding: 7bit
Cc: Harald Tveit Alvestrand <harald@alvestrand.no>,
        "<dnsop@lists.uoregon.edu>" <dnsop@lists.uoregon.edu>, <ietf@ietf.org>,
        bmanning@vacation.karoshi.com, Ken Raeburn <raeburn@MIT.EDU>
From: Joe Abley <jabley@isc.org>
Subject: Re: [dnsop] Re: Complaint on abuse of DNSOP lists
Date: Tue, 11 May 2004 17:10:54 -0400
To: Dean Anderson <dean@av8.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 11 May 2004, at 14:02, Dean Anderson wrote:

> The following message indicates that EP.NET has assigned an IP address 
> to
> ISC.ORG.  You are quite well aware of this.  Dissembling will not help
> you.

For the benefit of less-operational people here who don't see humour in 
this, 198.32.176.0/24 is the PAIX IPv4 peering fabric in the Bay Area.

Some of Dean's mail servers are listed on SORBS. ISC's MXes use SORBS. 
Perhaps we should move on.


Joe


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



From ietf-admin@ietf.org  Tue May 11 18:24: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 SAA02238
	for <ietf-archive@ietf.org>; Tue, 11 May 2004 18:24: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 1BNffj-0001eC-UE
	for ietf-archive@ietf.org; Tue, 11 May 2004 18:24:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNfei-0001B6-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 18:23:21 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNfdy-0000kG-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 18: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 1BNfPB-0001lN-Uo; Tue, 11 May 2004 18:07:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNfGS-0004Pd-4Y
	for ietf@optimus.ietf.org; Tue, 11 May 2004 17:58: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 RAA29607
	for <ietf@ietf.org>; Tue, 11 May 2004 17:58: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 1BNfGP-0005jf-Eg
	for ietf@ietf.org; Tue, 11 May 2004 17:58:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNfFN-0005G7-00
	for ietf@ietf.org; Tue, 11 May 2004 17:57:10 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNfEI-0004KI-00
	for ietf@ietf.org; Tue, 11 May 2004 17:56:02 -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 i4BLtPXb024178
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 11 May 2004 17:55:26 -0400
Date: Tue, 11 May 2004 17:55:25 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Joe Abley <jabley@isc.org>
cc: Harald Tveit Alvestrand <harald@alvestrand.no>,
        "<dnsop@lists.uoregon.edu>" <dnsop@lists.uoregon.edu>, <ietf@ietf.org>,
        <bmanning@vacation.karoshi.com>, Ken Raeburn <raeburn@MIT.EDU>
Subject: Re: [dnsop] Re: Complaint on abuse of DNSOP lists
In-Reply-To: <B0D6533C-A38F-11D8-8085-000A95E7E6B4@isc.org>
Message-ID: <Pine.LNX.4.44.0405111748480.19722-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 would ignore this, but it materially mis-states ISC.ORGS involvement in 
SORBS.   ISC.ORG __HOSTS__ www.sorbs.net on 204.152.186.189:

On Tue, 11 May 2004, Joe Abley wrote:

> For the benefit of less-operational people here who don't see humour in 
> this, 198.32.176.0/24 is the PAIX IPv4 peering fabric in the Bay Area.

This block is assigned to EP.NET.

> Some of Dean's mail servers are listed on SORBS. ISC's MXes use SORBS. 
> Perhaps we should move on.

ISC does more than just __USE__ SORBS. It hosts and promotes SORBS.  Host
abuse, you are abuse-friendly.


/usr/sbin/traceroute 204.152.186.189
traceroute to 204.152.186.189 (204.152.186.189), 30 hops max, 38 byte packets
 1  av8-camb-gw1 (198.3.136.1)  1.548 ms  0.869 ms  1.758 ms
 2  av8-qncy-gw1 (130.105.32.14)  4.338 ms  4.197 ms  4.125 ms
 3  qcy1-ar2-f2-0-314.gnaps.net (199.232.42.53)  4.105 ms  3.812 ms  4.504 ms
 4  qcy-m20-ge2-3-0-625.gnaps.net (199.232.44.45)  6.874 ms  4.224 ms  7.064 ms
 5  ash-m20-at-0-2-0.gnaps.net (199.232.44.53)  16.136 ms  16.263 ms  16.145 ms
 6  nyc-m20-ge2-1-0.gnaps.net (199.232.131.16)  24.379 ms  27.903 ms  22.061 ms
 7  los1-m20-at1-3-0.gnaps.net (199.232.44.10)  99.734 ms  94.698 ms  101.074 ms
 8  paix-gw4.isc.org (198.32.176.4)  103.482 ms  103.255 ms  103.596 ms
 9  r2-sfo2.r5.sql1.isc.org (192.5.4.248)  106.342 ms  110.758 ms  115.882 ms
10  www.dnsbl.us.sorbs.net (204.152.186.189)  106.122 ms  110.523 ms  105.857 ms

As you can see, traffic to 204.152.186.189 transits EP.NET's 198.32.176.4
address block.

		--Dean



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


From exim@www1.ietf.org  Tue May 11 18:28: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 SAA02506
	for <ietf-archive@odin.ietf.org>; Tue, 11 May 2004 18:28: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 1BNfe0-0001F7-Tu
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 18:22:37 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4BMMaiV004774
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 18:22:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNfPB-0001lN-Uo; Tue, 11 May 2004 18:07:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNfGS-0004Pd-4Y
	for ietf@optimus.ietf.org; Tue, 11 May 2004 17:58: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 RAA29607
	for <ietf@ietf.org>; Tue, 11 May 2004 17:58: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 1BNfGP-0005jf-Eg
	for ietf@ietf.org; Tue, 11 May 2004 17:58:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNfFN-0005G7-00
	for ietf@ietf.org; Tue, 11 May 2004 17:57:10 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNfEI-0004KI-00
	for ietf@ietf.org; Tue, 11 May 2004 17:56:02 -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 i4BLtPXb024178
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 11 May 2004 17:55:26 -0400
Date: Tue, 11 May 2004 17:55:25 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Joe Abley <jabley@isc.org>
cc: Harald Tveit Alvestrand <harald@alvestrand.no>,
        "<dnsop@lists.uoregon.edu>" <dnsop@lists.uoregon.edu>, <ietf@ietf.org>,
        <bmanning@vacation.karoshi.com>, Ken Raeburn <raeburn@MIT.EDU>
Subject: Re: [dnsop] Re: Complaint on abuse of DNSOP lists
In-Reply-To: <B0D6533C-A38F-11D8-8085-000A95E7E6B4@isc.org>
Message-ID: <Pine.LNX.4.44.0405111748480.19722-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 would ignore this, but it materially mis-states ISC.ORGS involvement in 
SORBS.   ISC.ORG __HOSTS__ www.sorbs.net on 204.152.186.189:

On Tue, 11 May 2004, Joe Abley wrote:

> For the benefit of less-operational people here who don't see humour in 
> this, 198.32.176.0/24 is the PAIX IPv4 peering fabric in the Bay Area.

This block is assigned to EP.NET.

> Some of Dean's mail servers are listed on SORBS. ISC's MXes use SORBS. 
> Perhaps we should move on.

ISC does more than just __USE__ SORBS. It hosts and promotes SORBS.  Host
abuse, you are abuse-friendly.


/usr/sbin/traceroute 204.152.186.189
traceroute to 204.152.186.189 (204.152.186.189), 30 hops max, 38 byte packets
 1  av8-camb-gw1 (198.3.136.1)  1.548 ms  0.869 ms  1.758 ms
 2  av8-qncy-gw1 (130.105.32.14)  4.338 ms  4.197 ms  4.125 ms
 3  qcy1-ar2-f2-0-314.gnaps.net (199.232.42.53)  4.105 ms  3.812 ms  4.504 ms
 4  qcy-m20-ge2-3-0-625.gnaps.net (199.232.44.45)  6.874 ms  4.224 ms  7.064 ms
 5  ash-m20-at-0-2-0.gnaps.net (199.232.44.53)  16.136 ms  16.263 ms  16.145 ms
 6  nyc-m20-ge2-1-0.gnaps.net (199.232.131.16)  24.379 ms  27.903 ms  22.061 ms
 7  los1-m20-at1-3-0.gnaps.net (199.232.44.10)  99.734 ms  94.698 ms  101.074 ms
 8  paix-gw4.isc.org (198.32.176.4)  103.482 ms  103.255 ms  103.596 ms
 9  r2-sfo2.r5.sql1.isc.org (192.5.4.248)  106.342 ms  110.758 ms  115.882 ms
10  www.dnsbl.us.sorbs.net (204.152.186.189)  106.122 ms  110.523 ms  105.857 ms

As you can see, traffic to 204.152.186.189 transits EP.NET's 198.32.176.4
address block.

		--Dean



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



From ietf-admin@ietf.org  Tue May 11 20:09:20 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08437
	for <ietf-archive@ietf.org>; Tue, 11 May 2004 20:09:20 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNhJI-0001m2-Pl
	for ietf-archive@ietf.org; Tue, 11 May 2004 20:09:20 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNhIN-0001Ks-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 20:08:23 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNhHf-0000ua-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 20:07:39 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNh1h-0003Bl-L0; Tue, 11 May 2004 19:51:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNgyv-0002KG-HB
	for ietf@optimus.ietf.org; Tue, 11 May 2004 19:48:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07059
	for <ietf@ietf.org>; Tue, 11 May 2004 19:48: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 1BNgyt-00005t-04
	for ietf@ietf.org; Tue, 11 May 2004 19:48:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNgxw-0007TI-00
	for ietf@ietf.org; Tue, 11 May 2004 19:47:17 -0400
Received: from felix.automagic.org ([204.152.186.101])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNgx2-000738-00
	for ietf@ietf.org; Tue, 11 May 2004 19:46:20 -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 1BNgx0-00077P-Sm; Tue, 11 May 2004 23:46:19 +0000
In-Reply-To: <Pine.LNX.4.44.0405111748480.19722-100000@cirrus.av8.net>
References: <Pine.LNX.4.44.0405111748480.19722-100000@cirrus.av8.net>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <65230E37-A3A5-11D8-8085-000A95E7E6B4@isc.org>
Content-Transfer-Encoding: 7bit
Cc: Harald Tveit Alvestrand <harald@alvestrand.no>,
        Bill Manning <bmanning@vacation.karoshi.com>,
        "<dnsop@lists.uoregon.edu>" <dnsop@lists.uoregon.edu>,
        "<ietf@ietf.org>" <ietf@ietf.org>, Ken Raeburn <raeburn@MIT.EDU>
From: Joe Abley <jabley@isc.org>
Subject: Re: [dnsop] Re: Complaint on abuse of DNSOP lists
Date: Tue, 11 May 2004 19:46:16 -0400
To: Dean Anderson <dean@av8.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 11 May 2004, at 17:55, Dean Anderson wrote:

> I would ignore this, but it materially mis-states ISC.ORGS involvement 
> in
> SORBS.   ISC.ORG __HOSTS__ www.sorbs.net on 204.152.186.189:

For a more complete list of resources hosted at ISC, you might try:

   http://www.isc.org/ops/hosting

> On Tue, 11 May 2004, Joe Abley wrote:
>
>> For the benefit of less-operational people here who don't see humour 
>> in
>> this, 198.32.176.0/24 is the PAIX IPv4 peering fabric in the Bay Area.
>
> This block is assigned to EP.NET.

[...]

> As you can see, traffic to 204.152.186.189 transits EP.NET's 
> 198.32.176.4
> address block.

If you are interested in learning about exchange points, peering, 
transit and interconnection in general, I'd can give you some pointers: 
you're missing some basic information which is leading you to jump to 
the wrong conclusions wrt 198.32.176.0/24.

I do lots of community education, and I'm more than willing to help 
out. But let's do it in private mail rather than this list.


Joe


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


From exim@www1.ietf.org  Tue May 11 20:21: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 UAA08968
	for <ietf-archive@odin.ietf.org>; Tue, 11 May 2004 20:21:52 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNhHg-0006m9-U7
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 20:07:53 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4C07ew5026020
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 20:07:40 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNh1h-0003Bl-L0; Tue, 11 May 2004 19:51:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNgyv-0002KG-HB
	for ietf@optimus.ietf.org; Tue, 11 May 2004 19:48:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07059
	for <ietf@ietf.org>; Tue, 11 May 2004 19:48: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 1BNgyt-00005t-04
	for ietf@ietf.org; Tue, 11 May 2004 19:48:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNgxw-0007TI-00
	for ietf@ietf.org; Tue, 11 May 2004 19:47:17 -0400
Received: from felix.automagic.org ([204.152.186.101])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNgx2-000738-00
	for ietf@ietf.org; Tue, 11 May 2004 19:46:20 -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 1BNgx0-00077P-Sm; Tue, 11 May 2004 23:46:19 +0000
In-Reply-To: <Pine.LNX.4.44.0405111748480.19722-100000@cirrus.av8.net>
References: <Pine.LNX.4.44.0405111748480.19722-100000@cirrus.av8.net>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <65230E37-A3A5-11D8-8085-000A95E7E6B4@isc.org>
Content-Transfer-Encoding: 7bit
Cc: Harald Tveit Alvestrand <harald@alvestrand.no>,
        Bill Manning <bmanning@vacation.karoshi.com>,
        "<dnsop@lists.uoregon.edu>" <dnsop@lists.uoregon.edu>,
        "<ietf@ietf.org>" <ietf@ietf.org>, Ken Raeburn <raeburn@MIT.EDU>
From: Joe Abley <jabley@isc.org>
Subject: Re: [dnsop] Re: Complaint on abuse of DNSOP lists
Date: Tue, 11 May 2004 19:46:16 -0400
To: Dean Anderson <dean@av8.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 11 May 2004, at 17:55, Dean Anderson wrote:

> I would ignore this, but it materially mis-states ISC.ORGS involvement 
> in
> SORBS.   ISC.ORG __HOSTS__ www.sorbs.net on 204.152.186.189:

For a more complete list of resources hosted at ISC, you might try:

   http://www.isc.org/ops/hosting

> On Tue, 11 May 2004, Joe Abley wrote:
>
>> For the benefit of less-operational people here who don't see humour 
>> in
>> this, 198.32.176.0/24 is the PAIX IPv4 peering fabric in the Bay Area.
>
> This block is assigned to EP.NET.

[...]

> As you can see, traffic to 204.152.186.189 transits EP.NET's 
> 198.32.176.4
> address block.

If you are interested in learning about exchange points, peering, 
transit and interconnection in general, I'd can give you some pointers: 
you're missing some basic information which is leading you to jump to 
the wrong conclusions wrt 198.32.176.0/24.

I do lots of community education, and I'm more than willing to help 
out. But let's do it in private mail rather than this list.


Joe


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



From ietf-admin@ietf.org  Tue May 11 20:38: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 UAA09818
	for <ietf-archive@ietf.org>; Tue, 11 May 2004 20:38: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 1BNhlM-0006fp-Tw
	for ietf-archive@ietf.org; Tue, 11 May 2004 20:38:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNhkP-0006Bw-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 20:37:21 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNhjD-0005R2-00
	for ietf-archive@ietf.org; Tue, 11 May 2004 20:36:07 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNhWa-00029y-4P; Tue, 11 May 2004 20:23:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNhOI-0008Vy-NL
	for ietf@optimus.ietf.org; Tue, 11 May 2004 20:14: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 UAA08695
	for <ietf@ietf.org>; Tue, 11 May 2004 20:14: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 1BNhOG-00040n-LG
	for ietf@ietf.org; Tue, 11 May 2004 20:14:28 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNhNO-0003ZZ-00
	for ietf@ietf.org; Tue, 11 May 2004 20:13:35 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNhMe-00034h-00
	for ietf@ietf.org; Tue, 11 May 2004 20:12:48 -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 i4C0C6SE026623
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 11 May 2004 20:12:06 -0400
Date: Tue, 11 May 2004 20:12:06 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Richard Barr Hibbs <rbhibbs@pacbell.net>
cc: John Stracke <jstracke@centive.com>, <ietf@ietf.org>,
        <dnsop@lists.uoregon.edu>
Subject: RE: [dnsop] Re: Complaint on abuse of DNSOP lists
In-Reply-To: <EJEFKKCLDBINLKODAFMDCEEDDEAA.rbhibbs@pacbell.net>
Message-ID: <Pine.LNX.4.44.0405112011100.19722-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 sent a response to Rob in regard to a post he made on DNSOP, and he
responded that my IP addresses were hijacked. 

		--Dean

On Tue, 11 May 2004, Richard Barr Hibbs wrote:

> 
> while Rob and I have had serious disagreements about
> technical matters in the past, I've never known him to make
> disparaging remarks about anyone, and a scan of the last 30
> days' messages on the DNSOP list authored by Rob (and
> delivered to my inbox) show NONE that mention AV8, it's
> products, customers, or business practices.
> 
> So, what's the fuss about?  Doesn't seem to involve IETF at
> all....
> 
> --Barr Hibbs
> 
> 
> > -----Original Message-----
> > From: owner-dnsop@lists.uoregon.edu
> > [mailto:owner-dnsop@lists.uoregon.edu]On Behalf
> > Of Dean Anderson
> > Sent: Monday, 10 May 2004 13:24
> > To: John Stracke
> > Cc: ietf@ietf.org; dnsop@lists.uoregon.edu
> > Subject: [dnsop] Re: Complaint on abuse of DNSOP lists
> >
> >
> > On Mon, 10 May 2004, John Stracke wrote:
> >
> > > Dean Anderson wrote:
> > >
> > > >It seems that WG co-chair has begun to use an
> > email address that is
> > > >defaming Av8 Internet, Inc
> > > >
> > > How is it defamation if the only one that gets
> > the message is Av8?
> >
> > Av8 customers get it.  DNSOP and IETF list
> > members have gotten it. When I
> > have to republish something to make a complaint
> > then legally it is just
> > like Mr. Austein published it himself. Defamation
> > Tort Law.
> >
> > 		--Dean
> >
> > .
> > dnsop
> > resources:________________________________________
> > _____________
> > web user interface:
> > http://darkwing.uoregon.edu/~llynch/dnsop.html
> > mhonarc archive:
> > http://darkwing.uoregon.edu/~llynch/dnsop/index.html
> >
> 
> 


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


From exim@www1.ietf.org  Tue May 11 20:45: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 UAA10076
	for <ietf-archive@odin.ietf.org>; Tue, 11 May 2004 20:45: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 1BNhjF-0004Zu-9E
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 20:36:16 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4C0a9lk017598
	for ietf-archive@odin.ietf.org; Tue, 11 May 2004 20:36:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNhWa-00029y-4P; Tue, 11 May 2004 20:23:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNhOI-0008Vy-NL
	for ietf@optimus.ietf.org; Tue, 11 May 2004 20:14: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 UAA08695
	for <ietf@ietf.org>; Tue, 11 May 2004 20:14: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 1BNhOG-00040n-LG
	for ietf@ietf.org; Tue, 11 May 2004 20:14:28 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNhNO-0003ZZ-00
	for ietf@ietf.org; Tue, 11 May 2004 20:13:35 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNhMe-00034h-00
	for ietf@ietf.org; Tue, 11 May 2004 20:12:48 -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 i4C0C6SE026623
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 11 May 2004 20:12:06 -0400
Date: Tue, 11 May 2004 20:12:06 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Richard Barr Hibbs <rbhibbs@pacbell.net>
cc: John Stracke <jstracke@centive.com>, <ietf@ietf.org>,
        <dnsop@lists.uoregon.edu>
Subject: RE: [dnsop] Re: Complaint on abuse of DNSOP lists
In-Reply-To: <EJEFKKCLDBINLKODAFMDCEEDDEAA.rbhibbs@pacbell.net>
Message-ID: <Pine.LNX.4.44.0405112011100.19722-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 sent a response to Rob in regard to a post he made on DNSOP, and he
responded that my IP addresses were hijacked. 

		--Dean

On Tue, 11 May 2004, Richard Barr Hibbs wrote:

> 
> while Rob and I have had serious disagreements about
> technical matters in the past, I've never known him to make
> disparaging remarks about anyone, and a scan of the last 30
> days' messages on the DNSOP list authored by Rob (and
> delivered to my inbox) show NONE that mention AV8, it's
> products, customers, or business practices.
> 
> So, what's the fuss about?  Doesn't seem to involve IETF at
> all....
> 
> --Barr Hibbs
> 
> 
> > -----Original Message-----
> > From: owner-dnsop@lists.uoregon.edu
> > [mailto:owner-dnsop@lists.uoregon.edu]On Behalf
> > Of Dean Anderson
> > Sent: Monday, 10 May 2004 13:24
> > To: John Stracke
> > Cc: ietf@ietf.org; dnsop@lists.uoregon.edu
> > Subject: [dnsop] Re: Complaint on abuse of DNSOP lists
> >
> >
> > On Mon, 10 May 2004, John Stracke wrote:
> >
> > > Dean Anderson wrote:
> > >
> > > >It seems that WG co-chair has begun to use an
> > email address that is
> > > >defaming Av8 Internet, Inc
> > > >
> > > How is it defamation if the only one that gets
> > the message is Av8?
> >
> > Av8 customers get it.  DNSOP and IETF list
> > members have gotten it. When I
> > have to republish something to make a complaint
> > then legally it is just
> > like Mr. Austein published it himself. Defamation
> > Tort Law.
> >
> > 		--Dean
> >
> > .
> > dnsop
> > resources:________________________________________
> > _____________
> > web user interface:
> > http://darkwing.uoregon.edu/~llynch/dnsop.html
> > mhonarc archive:
> > http://darkwing.uoregon.edu/~llynch/dnsop/index.html
> >
> 
> 


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



From ietf-admin@ietf.org  Wed May 12 01:13: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 BAA21179
	for <ietf-archive@ietf.org>; Wed, 12 May 2004 01:13: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 1BNm3n-0001b0-Rc
	for ietf-archive@ietf.org; Wed, 12 May 2004 01:13:39 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNm2v-00019L-00
	for ietf-archive@ietf.org; Wed, 12 May 2004 01:12:45 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNm26-0000hx-00
	for ietf-archive@ietf.org; Wed, 12 May 2004 01:11:54 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNloh-0002EN-J7; Wed, 12 May 2004 00:58:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNlgY-0000Y9-7f
	for ietf@optimus.ietf.org; Wed, 12 May 2004 00:49:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20255
	for <ietf@ietf.org>; Wed, 12 May 2004 00:49: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 1BNlgV-0006iU-2O
	for ietf@ietf.org; Wed, 12 May 2004 00:49:35 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNlfd-0006Hs-00
	for ietf@ietf.org; Wed, 12 May 2004 00:48:41 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNleb-0005QJ-00
	for ietf@ietf.org; Wed, 12 May 2004 00:47:37 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 1C20461BD7; Wed, 12 May 2004 06:47:08 +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 11586-03; Wed, 12 May 2004 06:47:07 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 2A21861AA5; Wed, 12 May 2004 06:47:05 +0200 (CEST)
Date: Wed, 12 May 2004 06:13:46 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Joe Abley <jabley@isc.org>, Dean Anderson <dean@av8.com>
Cc: "<dnsop@lists.uoregon.edu>" <dnsop@lists.uoregon.edu>, ietf@ietf.org,
        bmanning@vacation.karoshi.com, Ken Raeburn <raeburn@MIT.EDU>
Subject: Re: [dnsop] Re: Complaint on abuse of DNSOP lists
Message-ID: <778178.1084342426@localhost>
In-Reply-To: <B0D6533C-A38F-11D8-8085-000A95E7E6B4@isc.org>
References: <Pine.LNX.4.44.0405111401380.19722-100000@cirrus.av8.net>
 <B0D6533C-A38F-11D8-8085-000A95E7E6B4@isc.org>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
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 11. mai 2004 17:10 -0400 Joe Abley <jabley@isc.org> wrote:

> For the benefit of less-operational people here who don't see humour in
> this, 198.32.176.0/24 is the PAIX IPv4 peering fabric in the Bay Area.
>
> Some of Dean's mail servers are listed on SORBS. ISC's MXes use SORBS.
> Perhaps we should move on.

Yes, please. The topic has lost all information value relevant to the IETF 
list.

                Harald


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


From exim@www1.ietf.org  Wed May 12 01:20: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 BAA21611
	for <ietf-archive@odin.ietf.org>; Wed, 12 May 2004 01: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 1BNm28-0005AG-2B
	for ietf-archive@odin.ietf.org; Wed, 12 May 2004 01:12:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4C5BtfT019808
	for ietf-archive@odin.ietf.org; Wed, 12 May 2004 01:11:55 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNloh-0002EN-J7; Wed, 12 May 2004 00:58:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNlgY-0000Y9-7f
	for ietf@optimus.ietf.org; Wed, 12 May 2004 00:49:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20255
	for <ietf@ietf.org>; Wed, 12 May 2004 00:49: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 1BNlgV-0006iU-2O
	for ietf@ietf.org; Wed, 12 May 2004 00:49:35 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNlfd-0006Hs-00
	for ietf@ietf.org; Wed, 12 May 2004 00:48:41 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNleb-0005QJ-00
	for ietf@ietf.org; Wed, 12 May 2004 00:47:37 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 1C20461BD7; Wed, 12 May 2004 06:47:08 +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 11586-03; Wed, 12 May 2004 06:47:07 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 2A21861AA5; Wed, 12 May 2004 06:47:05 +0200 (CEST)
Date: Wed, 12 May 2004 06:13:46 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Joe Abley <jabley@isc.org>, Dean Anderson <dean@av8.com>
Cc: "<dnsop@lists.uoregon.edu>" <dnsop@lists.uoregon.edu>, ietf@ietf.org,
        bmanning@vacation.karoshi.com, Ken Raeburn <raeburn@MIT.EDU>
Subject: Re: [dnsop] Re: Complaint on abuse of DNSOP lists
Message-ID: <778178.1084342426@localhost>
In-Reply-To: <B0D6533C-A38F-11D8-8085-000A95E7E6B4@isc.org>
References: <Pine.LNX.4.44.0405111401380.19722-100000@cirrus.av8.net>
 <B0D6533C-A38F-11D8-8085-000A95E7E6B4@isc.org>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-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: 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 11. mai 2004 17:10 -0400 Joe Abley <jabley@isc.org> wrote:

> For the benefit of less-operational people here who don't see humour in
> this, 198.32.176.0/24 is the PAIX IPv4 peering fabric in the Bay Area.
>
> Some of Dean's mail servers are listed on SORBS. ISC's MXes use SORBS.
> Perhaps we should move on.

Yes, please. The topic has lost all information value relevant to the IETF 
list.

                Harald


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



From ietf-admin@ietf.org  Wed May 12 04:14: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 EAA15766
	for <ietf-archive@ietf.org>; Wed, 12 May 2004 04:14: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 1BNoss-0000rF-1C
	for ietf-archive@ietf.org; Wed, 12 May 2004 04:14:34 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNorL-00009F-00
	for ietf-archive@ietf.org; Wed, 12 May 2004 04:13:00 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNoqE-0007Lz-00
	for ietf-archive@ietf.org; Wed, 12 May 2004 04:11:51 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNohm-0001Wm-MX; Wed, 12 May 2004 04:03:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNobp-0008GJ-QB
	for ietf@optimus.ietf.org; Wed, 12 May 2004 03:56:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA14723
	for <ietf@ietf.org>; Wed, 12 May 2004 03:56: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 1BNobn-0007d8-70
	for ietf@ietf.org; Wed, 12 May 2004 03:56:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNoag-00076G-00
	for ietf@ietf.org; Wed, 12 May 2004 03:55:47 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNoZe-0006aH-00; Wed, 12 May 2004 03:54:42 -0400
Received: from [127.0.0.1] (helo=localhost)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1BNoZc-000COM-00; Wed, 12 May 2004 02:54:41 -0500
Date: Tue, 11 May 2004 21:04:14 -0400
From: John C Klensin <john-ietf@jck.com>
To: Scott Bradner <sob@harvard.edu>, harald@alvestrand.no, iesg@ietf.org,
        ietf@ietf.org
Subject: Re: Last Call: 'The IESG and RFC Editor documents:
 Procedures' to BCP
Message-ID: <834B7C1227D9FBC665D91F09@7AD4D3FB4841A5E367CCF211>
In-Reply-To: <20040511163902.0EF011E9EDF@newdev.harvard.edu>
References: <20040511163902.0EF011E9EDF@newdev.harvard.edu>
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.3 required=5.0 tests=AWL,DATE_IN_PAST_06_12 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit



--On Tuesday, May 11, 2004 12:39 PM -0400 Scott Bradner 
<sob@harvard.edu> wrote:

> in general that seems OK though I'd like to see "including the
> possibility of the author pursuing the work within the IETF"
> added

Clearly I intended that option to be included.  I didn't state 
it for two reasons.  First, I thought it was obvious.  Second, 
it felt like it was looking for trouble to identify one example 
("pursue the work within the IETF" while not identifying any 
others.  And, bluntly, the obvious other example is "the IESG 
beats the author (I hope only intellectually and metaphorically) 
to a  pulp and convinces him that the document is really stupid 
and will cause him embarrassment for the rest of his life".  I 
don't want to go anywhere near that in this sort of document, 
but avoiding doing anything that would permit someone to 
complain that AD administration of a clue-by-four (even 
aggressively) is inappropriate.

Much more broadly and IMO, if the IETF is going to be worth 
anything a few years from now, the ADs have to be enabled to 
educate, and encouraged and expected to do so, even when the 
subject of such education is unwilling.   As long as "education" 
doesn't shift into "intimidation", if the side effect of such 
education is withdrawal of a dumb document, then I think it is 
wonderful.  This isn't the critical mainstream for this 
document, with or without the suggested modifications, but, 
based on the experience of the last few years, I get really 
worried about text -- especially new text-- in these procedural 
documents that enables or encourages potential protocol 
lawyers... whether they are inside the IESG or outside the core 
IETF community.

    john


  --On Tuesday, May 11, 2004 12:39 PM -0400 Scott Bradner 
<sob@harvard.edu> wrote:

> in general that seems OK though I'd like to see "including the
> possibility of the author pursuing the work within the IETF"
> added
>
> ----
>
>> From john-ietf@jck.com  Tue May 11 12:18:30 2004
> X-Original-To: sob@newdev.harvard.edu
> Delivered-To: sob@newdev.harvard.edu
> Date: Tue, 11 May 2004 12:18:20 -0400
> From: John C Klensin <john-ietf@jck.com>
> To: Scott Bradner <sob@harvard.edu>, harald@alvestrand.no,
> 	iesg@ietf.org, ietf@ietf.org
> Subject: Re: Last Call: 'The IESG and RFC Editor documents:
>  Procedures' to BCP
> In-Reply-To: <20040511135704.3E2D51E97E8@newdev.harvard.edu>
> References:  <20040511135704.3E2D51E97E8@newdev.harvard.edu>
> 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
>
> Scott, Harald,
>
> It seems to me that this problem/ disagreement could be easily
> solved while preserving the (IMO, valid) points both of you
> are  making, by including a sentence somewhere to the effect
> of...
>
> 	Of course, the IESG or individual ADs may have
> 	discussions with the author during this period about
> 	other possible ways to handle the document.  Should that
> 	discussion result in a voluntary action by the author to
> 	drop the request to the RFC Editor to publist, the
> 	document moves immediately outside the scope of this
> 	specification.
>
> Now, that may not be the right phrasing in context, and can
> certainly be improved.   But I think it covers the full range
> of  from "we really think this should be standardized, why not
> let  us process it that way" to "if you insist on publishing
> that  thing, I'm going to break both of your legs".   The
> question of  whether those actions are appropriate is a
> separate issue, but  the IESG has never been able to insist on
> either standardization  or withdrawal.  And, as far as I know,
> both actions are  identical as far as the RFC Editor is
> concerned: the document is  spontaneously withdrawn as an
> individual submission.
>
>        john
>
>
> --On Tuesday, May 11, 2004 9:57 AM -0400 Scott Bradner
> <sob@harvard.edu> wrote:
>
>>> Anything else should (IMHO) be advice to the RFC Editor and
>>> the author, and  not be part of the formal position-taking
>>> the IESG makes.
>>
>> we may be debating termonology
>>
>> your ID says "The IESG may return five different responses"
>>
>> that seems to eliminate the possibility of communicating any
>> such advice
>>
>>> Because in the past, we've seriously bogged down independent
>>> publications  because we were debating (with or without the
>>> author) whether or not they  should be IETF work.
>>> And we need to stop doing that.
>>
>> beware of tossing too much away just to "stop doing that"
>>
>> I still fail to see why this document cannot say that one of
>> the outcomes could be that the author could agree with the
>> IESG to bring the work into the IETF -  it seems a bit
>> dogmatic to refuse to say that (and counter to the intent of
>> 2026)
>>
>> Scott
>>
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www1.ietf.org/mailman/listinfo/ietf
>
>
>
>
>


>
> ----
>
>> From john-ietf@jck.com  Tue May 11 12:18:30 2004
> X-Original-To: sob@newdev.harvard.edu
> Delivered-To: sob@newdev.harvard.edu
> Date: Tue, 11 May 2004 12:18:20 -0400
> From: John C Klensin <john-ietf@jck.com>
> To: Scott Bradner <sob@harvard.edu>, harald@alvestrand.no,
> 	iesg@ietf.org, ietf@ietf.org
> Subject: Re: Last Call: 'The IESG and RFC Editor documents:
>  Procedures' to BCP
> In-Reply-To: <20040511135704.3E2D51E97E8@newdev.harvard.edu>
> References:  <20040511135704.3E2D51E97E8@newdev.harvard.edu>
> 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
>
> Scott, Harald,
>
> It seems to me that this problem/ disagreement could be easily
> solved while preserving the (IMO, valid) points both of you
> are  making, by including a sentence somewhere to the effect
> of...
>
> 	Of course, the IESG or individual ADs may have
> 	discussions with the author during this period about
> 	other possible ways to handle the document.  Should that
> 	discussion result in a voluntary action by the author to
> 	drop the request to the RFC Editor to publist, the
> 	document moves immediately outside the scope of this
> 	specification.
>
> Now, that may not be the right phrasing in context, and can
> certainly be improved.   But I think it covers the full range
> of  from "we really think this should be standardized, why not
> let  us process it that way" to "if you insist on publishing
> that  thing, I'm going to break both of your legs".   The
> question of  whether those actions are appropriate is a
> separate issue, but  the IESG has never been able to insist on
> either standardization  or withdrawal.  And, as far as I know,
> both actions are  identical as far as the RFC Editor is
> concerned: the document is  spontaneously withdrawn as an
> individual submission.
>
>        john
>
>
> --On Tuesday, May 11, 2004 9:57 AM -0400 Scott Bradner
> <sob@harvard.edu> wrote:
>
>>> Anything else should (IMHO) be advice to the RFC Editor and
>>> the author, and  not be part of the formal position-taking
>>> the IESG makes.
>>
>> we may be debating termonology
>>
>> your ID says "The IESG may return five different responses"
>>
>> that seems to eliminate the possibility of communicating any
>> such advice
>>
>>> Because in the past, we've seriously bogged down independent
>>> publications  because we were debating (with or without the
>>> author) whether or not they  should be IETF work.
>>> And we need to stop doing that.
>>
>> beware of tossing too much away just to "stop doing that"
>>
>> I still fail to see why this document cannot say that one of
>> the outcomes could be that the author could agree with the
>> IESG to bring the work into the IETF -  it seems a bit
>> dogmatic to refuse to say that (and counter to the intent of
>> 2026)
>>
>> Scott
>>
>> _______________________________________________
>> 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 May 12 04:17:10 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA15963
	for <ietf-archive@odin.ietf.org>; Wed, 12 May 2004 04:17: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 1BNoqG-0003Ky-7b
	for ietf-archive@odin.ietf.org; Wed, 12 May 2004 04:12:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4C8BqVo012829
	for ietf-archive@odin.ietf.org; Wed, 12 May 2004 04:11:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNohm-0001Wm-MX; Wed, 12 May 2004 04:03:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNobp-0008GJ-QB
	for ietf@optimus.ietf.org; Wed, 12 May 2004 03:56:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA14723
	for <ietf@ietf.org>; Wed, 12 May 2004 03:56: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 1BNobn-0007d8-70
	for ietf@ietf.org; Wed, 12 May 2004 03:56:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNoag-00076G-00
	for ietf@ietf.org; Wed, 12 May 2004 03:55:47 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNoZe-0006aH-00; Wed, 12 May 2004 03:54:42 -0400
Received: from [127.0.0.1] (helo=localhost)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1BNoZc-000COM-00; Wed, 12 May 2004 02:54:41 -0500
Date: Tue, 11 May 2004 21:04:14 -0400
From: John C Klensin <john-ietf@jck.com>
To: Scott Bradner <sob@harvard.edu>, harald@alvestrand.no, iesg@ietf.org,
        ietf@ietf.org
Subject: Re: Last Call: 'The IESG and RFC Editor documents:
 Procedures' to BCP
Message-ID: <834B7C1227D9FBC665D91F09@7AD4D3FB4841A5E367CCF211>
In-Reply-To: <20040511163902.0EF011E9EDF@newdev.harvard.edu>
References: <20040511163902.0EF011E9EDF@newdev.harvard.edu>
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.3 required=5.0 tests=AWL,DATE_IN_PAST_06_12 
	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 Tuesday, May 11, 2004 12:39 PM -0400 Scott Bradner 
<sob@harvard.edu> wrote:

> in general that seems OK though I'd like to see "including the
> possibility of the author pursuing the work within the IETF"
> added

Clearly I intended that option to be included.  I didn't state 
it for two reasons.  First, I thought it was obvious.  Second, 
it felt like it was looking for trouble to identify one example 
("pursue the work within the IETF" while not identifying any 
others.  And, bluntly, the obvious other example is "the IESG 
beats the author (I hope only intellectually and metaphorically) 
to a  pulp and convinces him that the document is really stupid 
and will cause him embarrassment for the rest of his life".  I 
don't want to go anywhere near that in this sort of document, 
but avoiding doing anything that would permit someone to 
complain that AD administration of a clue-by-four (even 
aggressively) is inappropriate.

Much more broadly and IMO, if the IETF is going to be worth 
anything a few years from now, the ADs have to be enabled to 
educate, and encouraged and expected to do so, even when the 
subject of such education is unwilling.   As long as "education" 
doesn't shift into "intimidation", if the side effect of such 
education is withdrawal of a dumb document, then I think it is 
wonderful.  This isn't the critical mainstream for this 
document, with or without the suggested modifications, but, 
based on the experience of the last few years, I get really 
worried about text -- especially new text-- in these procedural 
documents that enables or encourages potential protocol 
lawyers... whether they are inside the IESG or outside the core 
IETF community.

    john


  --On Tuesday, May 11, 2004 12:39 PM -0400 Scott Bradner 
<sob@harvard.edu> wrote:

> in general that seems OK though I'd like to see "including the
> possibility of the author pursuing the work within the IETF"
> added
>
> ----
>
>> From john-ietf@jck.com  Tue May 11 12:18:30 2004
> X-Original-To: sob@newdev.harvard.edu
> Delivered-To: sob@newdev.harvard.edu
> Date: Tue, 11 May 2004 12:18:20 -0400
> From: John C Klensin <john-ietf@jck.com>
> To: Scott Bradner <sob@harvard.edu>, harald@alvestrand.no,
> 	iesg@ietf.org, ietf@ietf.org
> Subject: Re: Last Call: 'The IESG and RFC Editor documents:
>  Procedures' to BCP
> In-Reply-To: <20040511135704.3E2D51E97E8@newdev.harvard.edu>
> References:  <20040511135704.3E2D51E97E8@newdev.harvard.edu>
> 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
>
> Scott, Harald,
>
> It seems to me that this problem/ disagreement could be easily
> solved while preserving the (IMO, valid) points both of you
> are  making, by including a sentence somewhere to the effect
> of...
>
> 	Of course, the IESG or individual ADs may have
> 	discussions with the author during this period about
> 	other possible ways to handle the document.  Should that
> 	discussion result in a voluntary action by the author to
> 	drop the request to the RFC Editor to publist, the
> 	document moves immediately outside the scope of this
> 	specification.
>
> Now, that may not be the right phrasing in context, and can
> certainly be improved.   But I think it covers the full range
> of  from "we really think this should be standardized, why not
> let  us process it that way" to "if you insist on publishing
> that  thing, I'm going to break both of your legs".   The
> question of  whether those actions are appropriate is a
> separate issue, but  the IESG has never been able to insist on
> either standardization  or withdrawal.  And, as far as I know,
> both actions are  identical as far as the RFC Editor is
> concerned: the document is  spontaneously withdrawn as an
> individual submission.
>
>        john
>
>
> --On Tuesday, May 11, 2004 9:57 AM -0400 Scott Bradner
> <sob@harvard.edu> wrote:
>
>>> Anything else should (IMHO) be advice to the RFC Editor and
>>> the author, and  not be part of the formal position-taking
>>> the IESG makes.
>>
>> we may be debating termonology
>>
>> your ID says "The IESG may return five different responses"
>>
>> that seems to eliminate the possibility of communicating any
>> such advice
>>
>>> Because in the past, we've seriously bogged down independent
>>> publications  because we were debating (with or without the
>>> author) whether or not they  should be IETF work.
>>> And we need to stop doing that.
>>
>> beware of tossing too much away just to "stop doing that"
>>
>> I still fail to see why this document cannot say that one of
>> the outcomes could be that the author could agree with the
>> IESG to bring the work into the IETF -  it seems a bit
>> dogmatic to refuse to say that (and counter to the intent of
>> 2026)
>>
>> Scott
>>
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www1.ietf.org/mailman/listinfo/ietf
>
>
>
>
>


>
> ----
>
>> From john-ietf@jck.com  Tue May 11 12:18:30 2004
> X-Original-To: sob@newdev.harvard.edu
> Delivered-To: sob@newdev.harvard.edu
> Date: Tue, 11 May 2004 12:18:20 -0400
> From: John C Klensin <john-ietf@jck.com>
> To: Scott Bradner <sob@harvard.edu>, harald@alvestrand.no,
> 	iesg@ietf.org, ietf@ietf.org
> Subject: Re: Last Call: 'The IESG and RFC Editor documents:
>  Procedures' to BCP
> In-Reply-To: <20040511135704.3E2D51E97E8@newdev.harvard.edu>
> References:  <20040511135704.3E2D51E97E8@newdev.harvard.edu>
> 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
>
> Scott, Harald,
>
> It seems to me that this problem/ disagreement could be easily
> solved while preserving the (IMO, valid) points both of you
> are  making, by including a sentence somewhere to the effect
> of...
>
> 	Of course, the IESG or individual ADs may have
> 	discussions with the author during this period about
> 	other possible ways to handle the document.  Should that
> 	discussion result in a voluntary action by the author to
> 	drop the request to the RFC Editor to publist, the
> 	document moves immediately outside the scope of this
> 	specification.
>
> Now, that may not be the right phrasing in context, and can
> certainly be improved.   But I think it covers the full range
> of  from "we really think this should be standardized, why not
> let  us process it that way" to "if you insist on publishing
> that  thing, I'm going to break both of your legs".   The
> question of  whether those actions are appropriate is a
> separate issue, but  the IESG has never been able to insist on
> either standardization  or withdrawal.  And, as far as I know,
> both actions are  identical as far as the RFC Editor is
> concerned: the document is  spontaneously withdrawn as an
> individual submission.
>
>        john
>
>
> --On Tuesday, May 11, 2004 9:57 AM -0400 Scott Bradner
> <sob@harvard.edu> wrote:
>
>>> Anything else should (IMHO) be advice to the RFC Editor and
>>> the author, and  not be part of the formal position-taking
>>> the IESG makes.
>>
>> we may be debating termonology
>>
>> your ID says "The IESG may return five different responses"
>>
>> that seems to eliminate the possibility of communicating any
>> such advice
>>
>>> Because in the past, we've seriously bogged down independent
>>> publications  because we were debating (with or without the
>>> author) whether or not they  should be IETF work.
>>> And we need to stop doing that.
>>
>> beware of tossing too much away just to "stop doing that"
>>
>> I still fail to see why this document cannot say that one of
>> the outcomes could be that the author could agree with the
>> IESG to bring the work into the IETF -  it seems a bit
>> dogmatic to refuse to say that (and counter to the intent of
>> 2026)
>>
>> Scott
>>
>> _______________________________________________
>> 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 May 12 07:29:26 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 HAA25024
	for <ietf-archive@odin.ietf.org>; Wed, 12 May 2004 07:29: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 1BNrtg-0003Ah-PJ
	for ietf-archive@odin.ietf.org; Wed, 12 May 2004 07:27:40 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4CBRaRJ011932
	for ietf-archive@odin.ietf.org; Wed, 12 May 2004 07:27:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNrkQ-0001ny-Fc; Wed, 12 May 2004 07: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 1BNrhm-0001KQ-V9
	for ietf@optimus.ietf.org; Wed, 12 May 2004 07:15: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 HAA24593
	for <ietf@ietf.org>; Wed, 12 May 2004 07:15: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 1BNrhm-0007T8-Az
	for ietf@ietf.org; Wed, 12 May 2004 07:15:18 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNrgl-0006vb-00
	for ietf@ietf.org; Wed, 12 May 2004 07:14: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 1BNrfc-0005r0-00; Wed, 12 May 2004 07:13:04 -0400
Received: by newdev.harvard.edu (Postfix, from userid 501)
	id 810C71EBD4C; Wed, 12 May 2004 07:12:28 -0400 (EDT)
To: harald@alvestrand.no, iesg@ietf.org, ietf@ietf.org, john-ietf@jck.com,
        sob@harvard.edu
Subject: Re: Last Call: 'The IESG and RFC Editor documents: Procedures' to BCP
In-Reply-To: <834B7C1227D9FBC665D91F09@7AD4D3FB4841A5E367CCF211>
Message-Id: <20040512111228.810C71EBD4C@newdev.harvard.edu>
Date: Wed, 12 May 2004 07:12:28 -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>

> I get really
> worried about text -- especially new text-- in these procedural 
> documents that enables or encourages potential protocol 
> lawyers... whether they are inside the IESG or outside the core 
> IETF community.


a reasonable worry (sorry to say) - note though that the text I'm suggesting 
is already in RFC 2026 so unless this new ID specifically obsoletes 
the section of RFC 2026 (right now the ID says its compatable with that 
section) - the old text still could be used by those protocol lawyers

Scott

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



From ietf-admin@ietf.org  Wed May 12 07:29: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 HAA25055
	for <ietf-archive@ietf.org>; Wed, 12 May 2004 07:29: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 1BNrvq-0007Pa-ME
	for ietf-archive@ietf.org; Wed, 12 May 2004 07:29:50 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNrur-0006qg-00
	for ietf-archive@ietf.org; Wed, 12 May 2004 07:28:50 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNrtg-0005uN-00
	for ietf-archive@ietf.org; Wed, 12 May 2004 07:27:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNrkQ-0001ny-Fc; Wed, 12 May 2004 07: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 1BNrhm-0001KQ-V9
	for ietf@optimus.ietf.org; Wed, 12 May 2004 07:15: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 HAA24593
	for <ietf@ietf.org>; Wed, 12 May 2004 07:15: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 1BNrhm-0007T8-Az
	for ietf@ietf.org; Wed, 12 May 2004 07:15:18 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNrgl-0006vb-00
	for ietf@ietf.org; Wed, 12 May 2004 07:14: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 1BNrfc-0005r0-00; Wed, 12 May 2004 07:13:04 -0400
Received: by newdev.harvard.edu (Postfix, from userid 501)
	id 810C71EBD4C; Wed, 12 May 2004 07:12:28 -0400 (EDT)
To: harald@alvestrand.no, iesg@ietf.org, ietf@ietf.org, john-ietf@jck.com,
        sob@harvard.edu
Subject: Re: Last Call: 'The IESG and RFC Editor documents: Procedures' to BCP
In-Reply-To: <834B7C1227D9FBC665D91F09@7AD4D3FB4841A5E367CCF211>
Message-Id: <20040512111228.810C71EBD4C@newdev.harvard.edu>
Date: Wed, 12 May 2004 07:12:28 -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

> I get really
> worried about text -- especially new text-- in these procedural 
> documents that enables or encourages potential protocol 
> lawyers... whether they are inside the IESG or outside the core 
> IETF community.


a reasonable worry (sorry to say) - note though that the text I'm suggesting 
is already in RFC 2026 so unless this new ID specifically obsoletes 
the section of RFC 2026 (right now the ID says its compatable with that 
section) - the old text still could be used by those protocol lawyers

Scott

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


From ietf-admin@ietf.org  Wed May 12 09:20: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 JAA00927
	for <ietf-archive@ietf.org>; Wed, 12 May 2004 09:20: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 1BNteZ-00036Q-HM
	for ietf-archive@ietf.org; Wed, 12 May 2004 09:20:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNtdf-0002aa-00
	for ietf-archive@ietf.org; Wed, 12 May 2004 09:19:12 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNtce-000231-00
	for ietf-archive@ietf.org; Wed, 12 May 2004 09:18:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNtRv-0004tR-Ey; Wed, 12 May 2004 09:07:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNgu4-0001Tg-53
	for ietf@optimus.ietf.org; Tue, 11 May 2004 19:43:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06858
	for <ietf@ietf.org>; Tue, 11 May 2004 19:43: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 1BNgu1-0005lZ-UY
	for ietf@ietf.org; Tue, 11 May 2004 19:43:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNgt3-0005Ka-00
	for ietf@ietf.org; Tue, 11 May 2004 19:42:13 -0400
Received: from smtp807.mail.sc5.yahoo.com ([66.163.168.186])
	by ietf-mx with smtp (Exim 4.12)
	id 1BNgrz-0004g7-00
	for ietf@ietf.org; Tue, 11 May 2004 19:41:07 -0400
Received: from unknown (HELO BarrH63p601) (rbhibbs@pacbell.net@63.193.193.52 with login)
  by smtp807.mail.sc5.yahoo.com with SMTP; 11 May 2004 23:41:07 -0000
Reply-To: <rbhibbs@pacbell.net>
From: "Richard Barr Hibbs" <rbhibbs@pacbell.net>
To: "Dean Anderson" <dean@av8.com>, "John Stracke" <jstracke@centive.com>
Cc: <ietf@ietf.org>, <dnsop@lists.uoregon.edu>
Subject: RE: [dnsop] Re: Complaint on abuse of DNSOP lists
Date: Tue, 11 May 2004 16:50:29 -0700
Message-ID: <EJEFKKCLDBINLKODAFMDCEEDDEAA.rbhibbs@pacbell.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
In-Reply-To: <Pine.LNX.4.44.0405101621260.25030-100000@cirrus.av8.net>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Importance: Normal
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


while Rob and I have had serious disagreements about
technical matters in the past, I've never known him to make
disparaging remarks about anyone, and a scan of the last 30
days' messages on the DNSOP list authored by Rob (and
delivered to my inbox) show NONE that mention AV8, it's
products, customers, or business practices.

So, what's the fuss about?  Doesn't seem to involve IETF at
all....

--Barr Hibbs


> -----Original Message-----
> From: owner-dnsop@lists.uoregon.edu
> [mailto:owner-dnsop@lists.uoregon.edu]On Behalf
> Of Dean Anderson
> Sent: Monday, 10 May 2004 13:24
> To: John Stracke
> Cc: ietf@ietf.org; dnsop@lists.uoregon.edu
> Subject: [dnsop] Re: Complaint on abuse of DNSOP lists
>
>
> On Mon, 10 May 2004, John Stracke wrote:
>
> > Dean Anderson wrote:
> >
> > >It seems that WG co-chair has begun to use an
> email address that is
> > >defaming Av8 Internet, Inc
> > >
> > How is it defamation if the only one that gets
> the message is Av8?
>
> Av8 customers get it.  DNSOP and IETF list
> members have gotten it. When I
> have to republish something to make a complaint
> then legally it is just
> like Mr. Austein published it himself. Defamation
> Tort Law.
>
> 		--Dean
>
> .
> dnsop
> resources:________________________________________
> _____________
> web user interface:
> http://darkwing.uoregon.edu/~llynch/dnsop.html
> mhonarc archive:
> http://darkwing.uoregon.edu/~llynch/dnsop/index.html
>


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


From exim@www1.ietf.org  Wed May 12 09:27:14 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01473
	for <ietf-archive@odin.ietf.org>; Wed, 12 May 2004 09:27: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 1BNtcf-0007Lo-5Z
	for ietf-archive@odin.ietf.org; Wed, 12 May 2004 09:18:09 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4CDI9bG028256
	for ietf-archive@odin.ietf.org; Wed, 12 May 2004 09:18:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNtRv-0004tR-Ey; Wed, 12 May 2004 09:07:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNgu4-0001Tg-53
	for ietf@optimus.ietf.org; Tue, 11 May 2004 19:43:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06858
	for <ietf@ietf.org>; Tue, 11 May 2004 19:43: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 1BNgu1-0005lZ-UY
	for ietf@ietf.org; Tue, 11 May 2004 19:43:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNgt3-0005Ka-00
	for ietf@ietf.org; Tue, 11 May 2004 19:42:13 -0400
Received: from smtp807.mail.sc5.yahoo.com ([66.163.168.186])
	by ietf-mx with smtp (Exim 4.12)
	id 1BNgrz-0004g7-00
	for ietf@ietf.org; Tue, 11 May 2004 19:41:07 -0400
Received: from unknown (HELO BarrH63p601) (rbhibbs@pacbell.net@63.193.193.52 with login)
  by smtp807.mail.sc5.yahoo.com with SMTP; 11 May 2004 23:41:07 -0000
Reply-To: <rbhibbs@pacbell.net>
From: "Richard Barr Hibbs" <rbhibbs@pacbell.net>
To: "Dean Anderson" <dean@av8.com>, "John Stracke" <jstracke@centive.com>
Cc: <ietf@ietf.org>, <dnsop@lists.uoregon.edu>
Subject: RE: [dnsop] Re: Complaint on abuse of DNSOP lists
Date: Tue, 11 May 2004 16:50:29 -0700
Message-ID: <EJEFKKCLDBINLKODAFMDCEEDDEAA.rbhibbs@pacbell.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
In-Reply-To: <Pine.LNX.4.44.0405101621260.25030-100000@cirrus.av8.net>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Importance: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: 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


while Rob and I have had serious disagreements about
technical matters in the past, I've never known him to make
disparaging remarks about anyone, and a scan of the last 30
days' messages on the DNSOP list authored by Rob (and
delivered to my inbox) show NONE that mention AV8, it's
products, customers, or business practices.

So, what's the fuss about?  Doesn't seem to involve IETF at
all....

--Barr Hibbs


> -----Original Message-----
> From: owner-dnsop@lists.uoregon.edu
> [mailto:owner-dnsop@lists.uoregon.edu]On Behalf
> Of Dean Anderson
> Sent: Monday, 10 May 2004 13:24
> To: John Stracke
> Cc: ietf@ietf.org; dnsop@lists.uoregon.edu
> Subject: [dnsop] Re: Complaint on abuse of DNSOP lists
>
>
> On Mon, 10 May 2004, John Stracke wrote:
>
> > Dean Anderson wrote:
> >
> > >It seems that WG co-chair has begun to use an
> email address that is
> > >defaming Av8 Internet, Inc
> > >
> > How is it defamation if the only one that gets
> the message is Av8?
>
> Av8 customers get it.  DNSOP and IETF list
> members have gotten it. When I
> have to republish something to make a complaint
> then legally it is just
> like Mr. Austein published it himself. Defamation
> Tort Law.
>
> 		--Dean
>
> .
> dnsop
> resources:________________________________________
> _____________
> web user interface:
> http://darkwing.uoregon.edu/~llynch/dnsop.html
> mhonarc archive:
> http://darkwing.uoregon.edu/~llynch/dnsop/index.html
>


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



From ietf-admin@ietf.org  Thu May 13 01:47: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 BAA06149
	for <ietf-archive@ietf.org>; Thu, 13 May 2004 01:47: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 1BO94Q-0000pI-71
	for ietf-archive@ietf.org; Thu, 13 May 2004 01:47:50 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BO93X-0000IS-00
	for ietf-archive@ietf.org; Thu, 13 May 2004 01:46:56 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BO92R-0007ZF-00
	for ietf-archive@ietf.org; Thu, 13 May 2004 01: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 1BO8ux-0005hW-8d; Thu, 13 May 2004 01:38:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BO8rg-00054t-8i
	for ietf@optimus.ietf.org; Thu, 13 May 2004 01:34:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA05429
	for <ietf@ietf.org>; Thu, 13 May 2004 01:34: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 1BO8rc-0001j3-Pv
	for ietf@ietf.org; Thu, 13 May 2004 01:34:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BO8qd-0001D6-00
	for ietf@ietf.org; Thu, 13 May 2004 01:33:36 -0400
Received: from letters.cs.ucsb.edu ([128.111.41.13])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BO8pc-0000Su-00
	for ietf@ietf.org; Thu, 13 May 2004 01:32:32 -0400
Received: from jackson.cs.ucsb.edu (jackson [128.111.52.10])
	by letters.cs.ucsb.edu (8.11.7+Sun/8.11.7) with ESMTP id i4D5WRx11796;
	Wed, 12 May 2004 22:32:27 -0700 (PDT)
Received: from jackson.cs.ucsb.edu (localhost [127.0.0.1])
	by jackson.cs.ucsb.edu (8.12.8/8.12.8) with ESMTP id i4D5WRSn016140;
	Wed, 12 May 2004 22:32:27 -0700
Received: (from almeroth@localhost)
	by jackson.cs.ucsb.edu (8.12.8/8.12.8/Submit) id i4D5WQWg016138;
	Wed, 12 May 2004 22:32:26 -0700
Date: Wed, 12 May 2004 22:32:26 -0700
From: "Kevin C. Almeroth" <almeroth@cs.ucsb.edu>
Message-Id: <200405130532.i4D5WQWg016138@jackson.cs.ucsb.edu>
To: dean@av8.com, jnc@mercury.lcs.mit.edu
Subject: Re: Complaint on abuse of DNSOP lists
Cc: 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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-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 pretty much does it for me:  anyone who says they are entitled
to participate in the IETF immediately goes into my spam bucket.

As others have pointed out, you've done yourself more harm than good.

>>I'm entitled to particpate, and I'm entitled to send email to the WG 
>>chairs as a participant.
>>
>>One thing I've noticed is that of none of the people criticizing me has
>>thought to address the fact that OUR ADDRESS SPACE IS NOT HIJACKED, and
>>that these people associated with the IETF: Paul Vixie, Joe Abley, Bill
>>Manning, and Rob Austein as WG Co-chair in his role for IETF business, all
>>claim that it is.  But anyone can plainly see they are lying.
>>
>>Dean Anderson
>>Av8 Internet, Inc
>>
>>
>>
>>
>>_______________________________________________
>>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 May 13 01:49:05 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 BAA06279
	for <ietf-archive@odin.ietf.org>; Thu, 13 May 2004 01:49: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 1BO92T-0007oC-HB
	for ietf-archive@odin.ietf.org; Thu, 13 May 2004 01:45:50 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4D5jn3I029960
	for ietf-archive@odin.ietf.org; Thu, 13 May 2004 01:45:49 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BO8ux-0005hW-8d; Thu, 13 May 2004 01:38:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BO8rg-00054t-8i
	for ietf@optimus.ietf.org; Thu, 13 May 2004 01:34:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA05429
	for <ietf@ietf.org>; Thu, 13 May 2004 01:34: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 1BO8rc-0001j3-Pv
	for ietf@ietf.org; Thu, 13 May 2004 01:34:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BO8qd-0001D6-00
	for ietf@ietf.org; Thu, 13 May 2004 01:33:36 -0400
Received: from letters.cs.ucsb.edu ([128.111.41.13])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BO8pc-0000Su-00
	for ietf@ietf.org; Thu, 13 May 2004 01:32:32 -0400
Received: from jackson.cs.ucsb.edu (jackson [128.111.52.10])
	by letters.cs.ucsb.edu (8.11.7+Sun/8.11.7) with ESMTP id i4D5WRx11796;
	Wed, 12 May 2004 22:32:27 -0700 (PDT)
Received: from jackson.cs.ucsb.edu (localhost [127.0.0.1])
	by jackson.cs.ucsb.edu (8.12.8/8.12.8) with ESMTP id i4D5WRSn016140;
	Wed, 12 May 2004 22:32:27 -0700
Received: (from almeroth@localhost)
	by jackson.cs.ucsb.edu (8.12.8/8.12.8/Submit) id i4D5WQWg016138;
	Wed, 12 May 2004 22:32:26 -0700
Date: Wed, 12 May 2004 22:32:26 -0700
From: "Kevin C. Almeroth" <almeroth@cs.ucsb.edu>
Message-Id: <200405130532.i4D5WQWg016138@jackson.cs.ucsb.edu>
To: dean@av8.com, jnc@mercury.lcs.mit.edu
Subject: Re: Complaint on abuse of DNSOP lists
Cc: ietf@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
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 pretty much does it for me:  anyone who says they are entitled
to participate in the IETF immediately goes into my spam bucket.

As others have pointed out, you've done yourself more harm than good.

>>I'm entitled to particpate, and I'm entitled to send email to the WG 
>>chairs as a participant.
>>
>>One thing I've noticed is that of none of the people criticizing me has
>>thought to address the fact that OUR ADDRESS SPACE IS NOT HIJACKED, and
>>that these people associated with the IETF: Paul Vixie, Joe Abley, Bill
>>Manning, and Rob Austein as WG Co-chair in his role for IETF business, all
>>claim that it is.  But anyone can plainly see they are lying.
>>
>>Dean Anderson
>>Av8 Internet, Inc
>>
>>
>>
>>
>>_______________________________________________
>>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 May 13 12:48: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 MAA22426
	for <ietf-archive@ietf.org>; Thu, 13 May 2004 12:48: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 1BOJO3-0007lJ-1Y
	for ietf-archive@ietf.org; Thu, 13 May 2004 12:48:47 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BOJMa-00075o-00
	for ietf-archive@ietf.org; Thu, 13 May 2004 12:47:16 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BOJLX-0006Xz-00
	for ietf-archive@ietf.org; Thu, 13 May 2004 12:46:11 -0400
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BOJLW-0005md-Ar
	for ietf-archive@ietf.org; Thu, 13 May 2004 12:46:11 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOJFf-0000bC-0N; Thu, 13 May 2004 12:40:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOJBq-0007vq-J9
	for ietf@optimus.ietf.org; Thu, 13 May 2004 12:36:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21827
	for <ietf@ietf.org>; Thu, 13 May 2004 12:36: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 1BOJBo-0001Jy-TH
	for ietf@ietf.org; Thu, 13 May 2004 12:36:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BOJAm-0000oD-00
	for ietf@ietf.org; Thu, 13 May 2004 12:35:05 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BOJ9n-0007aU-00
	for ietf@ietf.org; Thu, 13 May 2004 12:34:03 -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 i4DGXUtk006154
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <ietf@ietf.org>; Thu, 13 May 2004 12:33:33 -0400
Date: Thu, 13 May 2004 12:33:30 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: ietf@ietf.org
Subject: Re: Complaint on abuse of DNSOP lists (fwd)
Message-ID: <Pine.LNX.4.44.0405131231580.5972-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

This wasn't a rhetorical question.  Does the IETF plan to pay more than 
just lip service to having an open process?  

Seems to make a good argument for putting the IETF under the ITU.


		--Dean

---------- Forwarded message ----------
Date: Tue, 11 May 2004 16:49:51 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
To: Rick Wesson <wessorh@ar.com>
Cc: ietf@ietf.org
Subject: Re: Complaint on abuse of DNSOP lists

Where would you suggest I take it?  

It says in the IETF mission statement:

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


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

How can one have an open process if WG chairs don't receive email?

How can it be taken off-list if IETF staff don't receive email?

Your request seems to be contradictory.

		--Dean



On Tue, 11 May 2004, Rick Wesson wrote:

> 
> Dean,
> 
> ok, i asked nicely and privately several times.
> PLEASE! take this thread some place else.
> 
> -rick
> 
> On Tue, 11 May 2004, Dean Anderson wrote:
> 
> > On Mon, 10 May 2004, Noel Chiappa wrote:
> >
> > > So? Rob's not refusing to accept *any* email *at all* from you as a person
> > > (just from a range of addresses which are generating email he doesn't like);
> > > and you're more than savvy enough technically to get email to him via some
> > > other path.
> >
> > As an IETF WG chair, he's obligated to follow the IETF rules on public
> > participation.  He can't block anything that the IETF mail server can't
> > block: Public Participants.
> >
> > > He's not under any more obligation to accept email from you via whatever
> > > channel you feel like using, no matter how onerous for him, than he is to
> > > accept messages written on 12' long oak logs of 3' diameter.
> > >
> > >
> > > Get a life, will you? Your constant whining and flaming is really getting
> > > old. You're getting really close to the line at which I'd ask the Chair to
> > > ban you from posting. Oh wait, I know what your response would be - you'd sue
> > > us. And you seem to think the rest of the world is doing things which is
> > > making you look bad. Here's another free clue: you're doing a far better job
> > > of that than the rest of us could do with a decade of free time.
> >
> > I'm entitled to particpate, and I'm entitled to send email to the WG
> > chairs as a participant.
> >
> > One thing I've noticed is that of none of the people criticizing me has
> > thought to address the fact that OUR ADDRESS SPACE IS NOT HIJACKED, and
> > that these people associated with the IETF: Paul Vixie, Joe Abley, Bill
> > Manning, and Rob Austein as WG Co-chair in his role for IETF business, all
> > claim that it is.  But anyone can plainly see they are lying.
> >
> > Dean Anderson
> > Av8 Internet, Inc
> >
> >
> >
> >
> > _______________________________________________
> > 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


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


From exim@www1.ietf.org  Thu May 13 12:53: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 MAA22870
	for <ietf-archive@odin.ietf.org>; Thu, 13 May 2004 12:53: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 1BOJLU-0001m0-Rv
	for ietf-archive@odin.ietf.org; Thu, 13 May 2004 12:46:08 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4DGk8N1006814
	for ietf-archive@odin.ietf.org; Thu, 13 May 2004 12:46:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOJFf-0000bC-0N; Thu, 13 May 2004 12:40:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOJBq-0007vq-J9
	for ietf@optimus.ietf.org; Thu, 13 May 2004 12:36:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21827
	for <ietf@ietf.org>; Thu, 13 May 2004 12:36: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 1BOJBo-0001Jy-TH
	for ietf@ietf.org; Thu, 13 May 2004 12:36:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BOJAm-0000oD-00
	for ietf@ietf.org; Thu, 13 May 2004 12:35:05 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BOJ9n-0007aU-00
	for ietf@ietf.org; Thu, 13 May 2004 12:34:03 -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 i4DGXUtk006154
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <ietf@ietf.org>; Thu, 13 May 2004 12:33:33 -0400
Date: Thu, 13 May 2004 12:33:30 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: ietf@ietf.org
Subject: Re: Complaint on abuse of DNSOP lists (fwd)
Message-ID: <Pine.LNX.4.44.0405131231580.5972-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>

This wasn't a rhetorical question.  Does the IETF plan to pay more than 
just lip service to having an open process?  

Seems to make a good argument for putting the IETF under the ITU.


		--Dean

---------- Forwarded message ----------
Date: Tue, 11 May 2004 16:49:51 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
To: Rick Wesson <wessorh@ar.com>
Cc: ietf@ietf.org
Subject: Re: Complaint on abuse of DNSOP lists

Where would you suggest I take it?  

It says in the IETF mission statement:

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


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

How can one have an open process if WG chairs don't receive email?

How can it be taken off-list if IETF staff don't receive email?

Your request seems to be contradictory.

		--Dean



On Tue, 11 May 2004, Rick Wesson wrote:

> 
> Dean,
> 
> ok, i asked nicely and privately several times.
> PLEASE! take this thread some place else.
> 
> -rick
> 
> On Tue, 11 May 2004, Dean Anderson wrote:
> 
> > On Mon, 10 May 2004, Noel Chiappa wrote:
> >
> > > So? Rob's not refusing to accept *any* email *at all* from you as a person
> > > (just from a range of addresses which are generating email he doesn't like);
> > > and you're more than savvy enough technically to get email to him via some
> > > other path.
> >
> > As an IETF WG chair, he's obligated to follow the IETF rules on public
> > participation.  He can't block anything that the IETF mail server can't
> > block: Public Participants.
> >
> > > He's not under any more obligation to accept email from you via whatever
> > > channel you feel like using, no matter how onerous for him, than he is to
> > > accept messages written on 12' long oak logs of 3' diameter.
> > >
> > >
> > > Get a life, will you? Your constant whining and flaming is really getting
> > > old. You're getting really close to the line at which I'd ask the Chair to
> > > ban you from posting. Oh wait, I know what your response would be - you'd sue
> > > us. And you seem to think the rest of the world is doing things which is
> > > making you look bad. Here's another free clue: you're doing a far better job
> > > of that than the rest of us could do with a decade of free time.
> >
> > I'm entitled to particpate, and I'm entitled to send email to the WG
> > chairs as a participant.
> >
> > One thing I've noticed is that of none of the people criticizing me has
> > thought to address the fact that OUR ADDRESS SPACE IS NOT HIJACKED, and
> > that these people associated with the IETF: Paul Vixie, Joe Abley, Bill
> > Manning, and Rob Austein as WG Co-chair in his role for IETF business, all
> > claim that it is.  But anyone can plainly see they are lying.
> >
> > Dean Anderson
> > Av8 Internet, Inc
> >
> >
> >
> >
> > _______________________________________________
> > 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


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



From ietf-admin@ietf.org  Thu May 13 12:53: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 MAA22963
	for <ietf-archive@ietf.org>; Thu, 13 May 2004 12:53: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 1BOJSi-0002p7-Ly
	for ietf-archive@ietf.org; Thu, 13 May 2004 12:53:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BOJRb-0002F2-00
	for ietf-archive@ietf.org; Thu, 13 May 2004 12:52:28 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BOJQl-0001gN-00
	for ietf-archive@ietf.org; Thu, 13 May 2004 12:51:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOJFg-0000bQ-H9; Thu, 13 May 2004 12:40:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOJCl-00086U-7z
	for ietf@optimus.ietf.org; Thu, 13 May 2004 12:37:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21877
	for <ietf@ietf.org>; Thu, 13 May 2004 12:37: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 1BOJCj-0001px-EN
	for ietf@ietf.org; Thu, 13 May 2004 12:37:05 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BOJBu-0001Kd-00
	for ietf@ietf.org; Thu, 13 May 2004 12:36:15 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BOJBB-0000hb-00
	for ietf@ietf.org; Thu, 13 May 2004 12:35:29 -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 i4DGYuL1006157
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 13 May 2004 12:34:57 -0400
Date: Thu, 13 May 2004 12:34:56 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: "Kevin C. Almeroth" <almeroth@cs.ucsb.edu>
cc: ietf@ietf.org
Subject: Re: Complaint on abuse of DNSOP lists
In-Reply-To: <200405130532.i4D5WQWg016138@jackson.cs.ucsb.edu>
Message-ID: <Pine.LNX.4.44.0405131233520.5972-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

Of course, this is exactly why the third world doesn't want to have the
IETF in charge in its present form.

Professional and standards organizations aren't private clubs.

		--Dean

On Wed, 12 May 2004, Kevin C. Almeroth wrote:

> This pretty much does it for me:  anyone who says they are entitled
> to participate in the IETF immediately goes into my spam bucket.
> 
> As others have pointed out, you've done yourself more harm than good.
> 
> >>I'm entitled to particpate, and I'm entitled to send email to the WG 
> >>chairs as a participant.
> >>
> >>One thing I've noticed is that of none of the people criticizing me has
> >>thought to address the fact that OUR ADDRESS SPACE IS NOT HIJACKED, and
> >>that these people associated with the IETF: Paul Vixie, Joe Abley, Bill
> >>Manning, and Rob Austein as WG Co-chair in his role for IETF business, all
> >>claim that it is.  But anyone can plainly see they are lying.
> >>
> >>Dean Anderson
> >>Av8 Internet, Inc
> >>
> >>
> >>
> >>
> >>_______________________________________________
> >>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 May 13 13:47:08 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 MAA22964
	for <ietf-archive@odin.ietf.org>; Thu, 13 May 2004 12:53:34 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOJQm-0002w8-Sj
	for ietf-archive@odin.ietf.org; Thu, 13 May 2004 12:51:37 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4DGpasc011219
	for ietf-archive@odin.ietf.org; Thu, 13 May 2004 12:51:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOJFg-0000bQ-H9; Thu, 13 May 2004 12:40:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOJCl-00086U-7z
	for ietf@optimus.ietf.org; Thu, 13 May 2004 12:37:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21877
	for <ietf@ietf.org>; Thu, 13 May 2004 12:37: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 1BOJCj-0001px-EN
	for ietf@ietf.org; Thu, 13 May 2004 12:37:05 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BOJBu-0001Kd-00
	for ietf@ietf.org; Thu, 13 May 2004 12:36:15 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BOJBB-0000hb-00
	for ietf@ietf.org; Thu, 13 May 2004 12:35:29 -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 i4DGYuL1006157
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 13 May 2004 12:34:57 -0400
Date: Thu, 13 May 2004 12:34:56 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: "Kevin C. Almeroth" <almeroth@cs.ucsb.edu>
cc: ietf@ietf.org
Subject: Re: Complaint on abuse of DNSOP lists
In-Reply-To: <200405130532.i4D5WQWg016138@jackson.cs.ucsb.edu>
Message-ID: <Pine.LNX.4.44.0405131233520.5972-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>

Of course, this is exactly why the third world doesn't want to have the
IETF in charge in its present form.

Professional and standards organizations aren't private clubs.

		--Dean

On Wed, 12 May 2004, Kevin C. Almeroth wrote:

> This pretty much does it for me:  anyone who says they are entitled
> to participate in the IETF immediately goes into my spam bucket.
> 
> As others have pointed out, you've done yourself more harm than good.
> 
> >>I'm entitled to particpate, and I'm entitled to send email to the WG 
> >>chairs as a participant.
> >>
> >>One thing I've noticed is that of none of the people criticizing me has
> >>thought to address the fact that OUR ADDRESS SPACE IS NOT HIJACKED, and
> >>that these people associated with the IETF: Paul Vixie, Joe Abley, Bill
> >>Manning, and Rob Austein as WG Co-chair in his role for IETF business, all
> >>claim that it is.  But anyone can plainly see they are lying.
> >>
> >>Dean Anderson
> >>Av8 Internet, Inc
> >>
> >>
> >>
> >>
> >>_______________________________________________
> >>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  Fri May 14 16:52:23 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25584
	for <ietf-archive@odin.ietf.org>; Fri, 14 May 2004 16:52: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 1BOjZ9-0003QD-La
	for ietf-archive@odin.ietf.org; Fri, 14 May 2004 16:45:59 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4EKjxIL013093
	for ietf-archive@odin.ietf.org; Fri, 14 May 2004 16:45:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOitb-00011x-0x; Fri, 14 May 2004 16:03:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BO4K8-0006YO-9l
	for ietf@optimus.ietf.org; Wed, 12 May 2004 20:43:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22165
	for <ietf@ietf.org>; Wed, 12 May 2004 20:43: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 1BO4K6-0006Eg-07
	for ietf@ietf.org; Wed, 12 May 2004 20:43:42 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BO4IV-0005HS-00
	for ietf@ietf.org; Wed, 12 May 2004 20:42:04 -0400
Received: from mout.perfora.net ([217.160.230.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BO4HV-0004h4-00
	for ietf@ietf.org; Wed, 12 May 2004 20:41:01 -0400
Received: from 000-137-713.area3.spcsdns.net[68.246.23.219] (helo=solidmatrix.com)
	by mrelay.perfora.net with ESMTP (Nemesis),
	id 1BO4HS-3T59-0MKz5u-0007z3; Wed, 12 May 2004 20:40:58 -0400
Message-ID: <40A2C413.4050201@solidmatrix.com>
Date: Wed, 12 May 2004 20:40:51 -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: ietf@ietf.org
Subject: [Fwd: [Asrg] ITU WSIS meeting]
X-Enigmail-Version: 0.83.2.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: 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

Forwarded from the ASRG list.

-------- Original Message --------
Subject: [Asrg] ITU WSIS meeting
Date: Thu, 13 May 2004 07:51:24 +1000
From: Ian Peter <ian.peter@ianpeter.com>
To: <asrg@ietf.org>

Has anyone been approached about this? Should we seek to get
someone in attendance as a subject matter expert?

(For those not following the governance debates this is part of ITU's
lead up to the World Summit on Information Society Internet governance
discussions)



ITU WSIS Thematic Meeting on Countering Spam, Geneva, 7-9 July 2004

Information about the meeting says the discussion will be structured
around five main themes:

- Scope of the problem
- Technical solutions
- Consumer and small business education and awareness
- Legislation and Enforcement
- International cooperation


See <http://www.itu.int/osg/spu/spam/> (general information)

and

<http://www.itu.int/osg/spu/spam/meeting7-9-04/index.html> (more
specific)


Ian Peter
Senior Partner
Ian Peter and Associates Pty Ltd
P.O. Box 10670 Adelaide St
Brisbane 4000 Australia
Tel (617) 3870 1181
Mobile (614) 1966 7772

--
Yakov Shafranovich / asrg <at> shaftek.org
SolidMatrix Technologies, Inc. / research <at> solidmatrix.com
"And this too shall come to pass"

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



From ietf-admin@ietf.org  Fri May 14 17:05: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 RAA26866
	for <ietf-archive@ietf.org>; Fri, 14 May 2004 17: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 1BOjs0-0000kh-W5
	for ietf-archive@ietf.org; Fri, 14 May 2004 17:05:29 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BOjpH-0007E8-00
	for ietf-archive@ietf.org; Fri, 14 May 2004 17:02:39 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BOjln-0005s0-00
	for ietf-archive@ietf.org; Fri, 14 May 2004 16:59:03 -0400
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BOjZD-0002CM-09
	for ietf-archive@ietf.org; Fri, 14 May 2004 16:46:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BOitb-00011x-0x; Fri, 14 May 2004 16:03:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BO4K8-0006YO-9l
	for ietf@optimus.ietf.org; Wed, 12 May 2004 20:43:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22165
	for <ietf@ietf.org>; Wed, 12 May 2004 20:43: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 1BO4K6-0006Eg-07
	for ietf@ietf.org; Wed, 12 May 2004 20:43:42 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BO4IV-0005HS-00
	for ietf@ietf.org; Wed, 12 May 2004 20:42:04 -0400
Received: from mout.perfora.net ([217.160.230.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BO4HV-0004h4-00
	for ietf@ietf.org; Wed, 12 May 2004 20:41:01 -0400
Received: from 000-137-713.area3.spcsdns.net[68.246.23.219] (helo=solidmatrix.com)
	by mrelay.perfora.net with ESMTP (Nemesis),
	id 1BO4HS-3T59-0MKz5u-0007z3; Wed, 12 May 2004 20:40:58 -0400
Message-ID: <40A2C413.4050201@solidmatrix.com>
Date: Wed, 12 May 2004 20:40:51 -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: ietf@ietf.org
Subject: [Fwd: [Asrg] ITU WSIS meeting]
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: 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

Forwarded from the ASRG list.

-------- Original Message --------
Subject: [Asrg] ITU WSIS meeting
Date: Thu, 13 May 2004 07:51:24 +1000
From: Ian Peter <ian.peter@ianpeter.com>
To: <asrg@ietf.org>

Has anyone been approached about this? Should we seek to get
someone in attendance as a subject matter expert?

(For those not following the governance debates this is part of ITU's
lead up to the World Summit on Information Society Internet governance
discussions)



ITU WSIS Thematic Meeting on Countering Spam, Geneva, 7-9 July 2004

Information about the meeting says the discussion will be structured
around five main themes:

- Scope of the problem
- Technical solutions
- Consumer and small business education and awareness
- Legislation and Enforcement
- International cooperation


See <http://www.itu.int/osg/spu/spam/> (general information)

and

<http://www.itu.int/osg/spu/spam/meeting7-9-04/index.html> (more
specific)


Ian Peter
Senior Partner
Ian Peter and Associates Pty Ltd
P.O. Box 10670 Adelaide St
Brisbane 4000 Australia
Tel (617) 3870 1181
Mobile (614) 1966 7772

--
Yakov Shafranovich / asrg <at> shaftek.org
SolidMatrix Technologies, Inc. / research <at> solidmatrix.com
"And this too shall come to pass"

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


From ietf-admin@ietf.org  Sun May 16 15:25:31 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17219
	for <ietf-archive@ietf.org>; Sun, 16 May 2004 15:25: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 1BPRGO-00046x-Bq
	for ietf-archive@ietf.org; Sun, 16 May 2004 15:25:32 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPRFR-0003mZ-00
	for ietf-archive@ietf.org; Sun, 16 May 2004 15:24:33 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPREs-0003Rt-00
	for ietf-archive@ietf.org; Sun, 16 May 2004 15:23:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPR98-00032W-1Z; Sun, 16 May 2004 15: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 1BPR6Q-00020p-Pe
	for ietf@optimus.ietf.org; Sun, 16 May 2004 15:15:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16511
	for <ietf@ietf.org>; Sun, 16 May 2004 15:15: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 1BPR6P-00010V-66
	for ietf@ietf.org; Sun, 16 May 2004 15:15:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPR5U-0000go-00
	for ietf@ietf.org; Sun, 16 May 2004 15:14:17 -0400
Received: from line-zh-102-119.adsl.econophone.ch ([212.53.102.119] helo=moreandmore.nope.ch)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPR5D-0000Mf-00
	for ietf@ietf.org; Sun, 16 May 2004 15:13:59 -0400
Received: by moreandmore.nope.ch (Postfix, from userid 33)
	id 327D459C11B; Sun, 16 May 2004 21:13:25 +0200 (CEST)
Received: from adsl-62-167-35-253.adslplus.ch (adsl-62-167-35-253.adslplus.ch [62.167.35.253]) 
	by www.bocek.ch (IMP) with HTTP 
	for <draft@localhost>; Sun, 16 May 2004 21:13:24 +0200
Message-ID: <1084734804.40a7bd54f3d8f@www.bocek.ch>
Date: Sun, 16 May 2004 21:13:24 +0200
From: Thomas Bocek <draft@icu.unizh.ch>
To: ietf@ietf.org
Subject: 13 Root Server Limitation
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
User-Agent: Internet Messaging Program (IMP) 3.2.2
X-Originating-IP: 62.167.35.253
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id PAA16511
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

Hi

I=92m confused with the fact than the number of root servers is limited t=
o 13.
>From RFC 3226:

"The current number of root servers is limited to 13 as that is the maxim=
um
number of name servers and their address records that fit in one 512-octe=
t
answer for a SOA record.  If root servers start advertising A6 or KEY rec=
ords
then the answer for the root NS records will not fit in a single 512-octe=
t DNS
message, resulting in a large number of TCP query connections to the root
servers."

A query send to one of the root servers with a long name (length 255) sho=
ws
that
the answer is 511 bytes, returning one A and 13 NS records. My question i=
s: Why
are all 13 NS returned?

Thanks in advance

T. Bocek



----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

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


From exim@www1.ietf.org  Sun May 16 15:25:35 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 PAA17236
	for <ietf-archive@odin.ietf.org>; Sun, 16 May 2004 15:25:35 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPREv-0004na-9v
	for ietf-archive@odin.ietf.org; Sun, 16 May 2004 15:24:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4GJO18x018165
	for ietf-archive@odin.ietf.org; Sun, 16 May 2004 15:24:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPR98-00032W-1Z; Sun, 16 May 2004 15: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 1BPR6Q-00020p-Pe
	for ietf@optimus.ietf.org; Sun, 16 May 2004 15:15:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16511
	for <ietf@ietf.org>; Sun, 16 May 2004 15:15: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 1BPR6P-00010V-66
	for ietf@ietf.org; Sun, 16 May 2004 15:15:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPR5U-0000go-00
	for ietf@ietf.org; Sun, 16 May 2004 15:14:17 -0400
Received: from line-zh-102-119.adsl.econophone.ch ([212.53.102.119] helo=moreandmore.nope.ch)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPR5D-0000Mf-00
	for ietf@ietf.org; Sun, 16 May 2004 15:13:59 -0400
Received: by moreandmore.nope.ch (Postfix, from userid 33)
	id 327D459C11B; Sun, 16 May 2004 21:13:25 +0200 (CEST)
Received: from adsl-62-167-35-253.adslplus.ch (adsl-62-167-35-253.adslplus.ch [62.167.35.253]) 
	by www.bocek.ch (IMP) with HTTP 
	for <draft@localhost>; Sun, 16 May 2004 21:13:24 +0200
Message-ID: <1084734804.40a7bd54f3d8f@www.bocek.ch>
Date: Sun, 16 May 2004 21:13:24 +0200
From: Thomas Bocek <draft@icu.unizh.ch>
To: ietf@ietf.org
Subject: 13 Root Server Limitation
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
User-Agent: Internet Messaging Program (IMP) 3.2.2
X-Originating-IP: 62.167.35.253
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-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
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id PAA16511
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

Hi

I=92m confused with the fact than the number of root servers is limited t=
o 13.
>From RFC 3226:

"The current number of root servers is limited to 13 as that is the maxim=
um
number of name servers and their address records that fit in one 512-octe=
t
answer for a SOA record.  If root servers start advertising A6 or KEY rec=
ords
then the answer for the root NS records will not fit in a single 512-octe=
t DNS
message, resulting in a large number of TCP query connections to the root
servers."

A query send to one of the root servers with a long name (length 255) sho=
ws
that
the answer is 511 bytes, returning one A and 13 NS records. My question i=
s: Why
are all 13 NS returned?

Thanks in advance

T. Bocek



----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

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



From ietf-admin@ietf.org  Sun May 16 18:23: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 SAA25572
	for <ietf-archive@ietf.org>; Sun, 16 May 2004 18:23: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 1BPU2T-0003WR-IB
	for ietf-archive@ietf.org; Sun, 16 May 2004 18:23:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPU1e-0003Cx-00
	for ietf-archive@ietf.org; Sun, 16 May 2004 18:22:30 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPU0f-0002tZ-00
	for ietf-archive@ietf.org; Sun, 16 May 2004 18:21:29 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPTvN-0005kv-6K; Sun, 16 May 2004 18:16:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPRyh-000233-CW
	for ietf@optimus.ietf.org; Sun, 16 May 2004 16:11: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 QAA19237
	for <ietf@ietf.org>; Sun, 16 May 2004 16:11: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 1BPRyf-0002jH-Fw
	for ietf@ietf.org; Sun, 16 May 2004 16:11:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPRxx-0002QW-00
	for ietf@ietf.org; Sun, 16 May 2004 16:10:34 -0400
Received: from mailout.techfak.uni-bielefeld.de ([129.70.136.245])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPRx8-00027J-00
	for ietf@ietf.org; Sun, 16 May 2004 16:09:42 -0400
Received: from grimsvotn.TechFak.Uni-Bielefeld.DE (grimsvotn.TechFak.Uni-Bielefeld.DE [129.70.137.40])
	by momotombo.TechFak.Uni-Bielefeld.DE (8.12.11/8.12.11/TechFak/2004/05/05/sjaenick) with ESMTP id i4GK9RRi016500;
	Sun, 16 May 2004 22:09:27 +0200 (MEST)
Received: from localhost (pk@localhost)
	by grimsvotn.TechFak.Uni-Bielefeld.DE (8.11.7+Sun/8.9.1) with SMTP id i4GK9R823251;
	Sun, 16 May 2004 22:09:27 +0200 (MEST)
Message-Id: <200405162009.i4GK9R823251@grimsvotn.TechFak.Uni-Bielefeld.DE>
X-Authentication-Warning: grimsvotn.TechFak.Uni-Bielefeld.DE: pk owned process doing -bs
X-Authentication-Warning: grimsvotn.TechFak.Uni-Bielefeld.DE: pk@localhost didn't use HELO protocol
To: Thomas Bocek <draft@icu.unizh.ch>
Cc: ietf@ietf.org
Subject: Re: 13 Root Server Limitation 
In-reply-to: Your message of "Sun, 16 May 2004 21:13:24 +0200."
             <1084734804.40a7bd54f3d8f@www.bocek.ch> 
X-Organization: Uni Bielefeld, Technische Fakultaet
X-Phone: +49 521 106 2902
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <23245.1084738162.1@grimsvotn.TechFak.Uni-Bielefeld.DE>
Date: Sun, 16 May 2004 22:09:27 +0200
From: Peter Koch <pk@TechFak.Uni-Bielefeld.DE>
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

Hello Thomas,

{calculation of DNS response sizes is a topic for the IETF DNSOP WG
 <http://www.ietf.org/html.charters/dnsop-charter.html>. For the basic
 issues, the archives of the DNSOP mailinglist may help, or even more so
 (apart from direct replies) one of the DNS related Usenet newsgroups.}

> A query send to one of the root servers with a long name (length 255) shows
> that
> the answer is 511 bytes, returning one A and 13 NS records. My question is: W
>hy
> are all 13 NS returned?

The protocol requires (RFC 2181, 5.2) that RRSets be handed out completely.
Everything else would sooner or later result in "funny" effects and severe
operational problems. It is, however, arguable, whether or not the "A" RR
is really needed. Currently deployed software may lead to a "yes" here.

-Peter

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


From exim@www1.ietf.org  Sun May 16 18:23:45 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25615
	for <ietf-archive@odin.ietf.org>; Sun, 16 May 2004 18:23: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 1BPU0k-0007ma-DQ
	for ietf-archive@odin.ietf.org; Sun, 16 May 2004 18:21:37 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4GMLUqm029653
	for ietf-archive@odin.ietf.org; Sun, 16 May 2004 18:21:30 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPTvN-0005kv-6K; Sun, 16 May 2004 18:16:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPRyh-000233-CW
	for ietf@optimus.ietf.org; Sun, 16 May 2004 16:11: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 QAA19237
	for <ietf@ietf.org>; Sun, 16 May 2004 16:11: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 1BPRyf-0002jH-Fw
	for ietf@ietf.org; Sun, 16 May 2004 16:11:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPRxx-0002QW-00
	for ietf@ietf.org; Sun, 16 May 2004 16:10:34 -0400
Received: from mailout.techfak.uni-bielefeld.de ([129.70.136.245])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPRx8-00027J-00
	for ietf@ietf.org; Sun, 16 May 2004 16:09:42 -0400
Received: from grimsvotn.TechFak.Uni-Bielefeld.DE (grimsvotn.TechFak.Uni-Bielefeld.DE [129.70.137.40])
	by momotombo.TechFak.Uni-Bielefeld.DE (8.12.11/8.12.11/TechFak/2004/05/05/sjaenick) with ESMTP id i4GK9RRi016500;
	Sun, 16 May 2004 22:09:27 +0200 (MEST)
Received: from localhost (pk@localhost)
	by grimsvotn.TechFak.Uni-Bielefeld.DE (8.11.7+Sun/8.9.1) with SMTP id i4GK9R823251;
	Sun, 16 May 2004 22:09:27 +0200 (MEST)
Message-Id: <200405162009.i4GK9R823251@grimsvotn.TechFak.Uni-Bielefeld.DE>
X-Authentication-Warning: grimsvotn.TechFak.Uni-Bielefeld.DE: pk owned process doing -bs
X-Authentication-Warning: grimsvotn.TechFak.Uni-Bielefeld.DE: pk@localhost didn't use HELO protocol
To: Thomas Bocek <draft@icu.unizh.ch>
Cc: ietf@ietf.org
Subject: Re: 13 Root Server Limitation 
In-reply-to: Your message of "Sun, 16 May 2004 21:13:24 +0200."
             <1084734804.40a7bd54f3d8f@www.bocek.ch> 
X-Organization: Uni Bielefeld, Technische Fakultaet
X-Phone: +49 521 106 2902
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <23245.1084738162.1@grimsvotn.TechFak.Uni-Bielefeld.DE>
Date: Sun, 16 May 2004 22:09:27 +0200
From: Peter Koch <pk@TechFak.Uni-Bielefeld.DE>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-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>

Hello Thomas,

{calculation of DNS response sizes is a topic for the IETF DNSOP WG
 <http://www.ietf.org/html.charters/dnsop-charter.html>. For the basic
 issues, the archives of the DNSOP mailinglist may help, or even more so
 (apart from direct replies) one of the DNS related Usenet newsgroups.}

> A query send to one of the root servers with a long name (length 255) shows
> that
> the answer is 511 bytes, returning one A and 13 NS records. My question is: W
>hy
> are all 13 NS returned?

The protocol requires (RFC 2181, 5.2) that RRSets be handed out completely.
Everything else would sooner or later result in "funny" effects and severe
operational problems. It is, however, arguable, whether or not the "A" RR
is really needed. Currently deployed software may lead to a "yes" here.

-Peter

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



From ietf-admin@ietf.org  Sun May 16 18:32:31 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26102
	for <ietf-archive@ietf.org>; Sun, 16 May 2004 18:32: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 1BPUBN-0006Eq-5W
	for ietf-archive@ietf.org; Sun, 16 May 2004 18:32:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPUAP-0005wV-00
	for ietf-archive@ietf.org; Sun, 16 May 2004 18:31:34 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPU9u-0005eN-00
	for ietf-archive@ietf.org; Sun, 16 May 2004 18:31:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPU54-0008M3-77; Sun, 16 May 2004 18:26:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPU3i-00087e-NT
	for ietf@optimus.ietf.org; Sun, 16 May 2004 18:24: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 SAA25693
	for <ietf@ietf.org>; Sun, 16 May 2004 18:24:31 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPU3d-0003sa-95
	for ietf@ietf.org; Sun, 16 May 2004 18:24:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPU2g-0003YG-00
	for ietf@ietf.org; Sun, 16 May 2004 18:23:35 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPU1z-0003Be-00
	for ietf@ietf.org; Sun, 16 May 2004 18:22:51 -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 i4GMMDKE002235
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Sun, 16 May 2004 18:22:14 -0400
Date: Sun, 16 May 2004 18:22:13 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Thomas Bocek <draft@icu.unizh.ch>
cc: ietf@ietf.org
Subject: Re: 13 Root Server Limitation
In-Reply-To: <1084734804.40a7bd54f3d8f@www.bocek.ch>
Message-ID: <Pine.LNX.4.44.0405161706080.678-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by cirrus.av8.net id i4GMMDKE002235
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.1 required=5.0 tests=AWL,OFFERS_ETC autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable

On Sun, 16 May 2004, Thomas Bocek wrote:

> Hi
>=20
> I=92m confused with the fact than the number of root servers is limited=
 to 13.
> From RFC 3226:
>=20
> "The current number of root servers is limited to 13 as that is the max=
imum
> number of name servers and their address records that fit in one 512-oc=
tet
> answer for a SOA record.  If root servers start advertising A6 or KEY r=
ecords
> then the answer for the root NS records will not fit in a single 512-oc=
tet DNS
> message, resulting in a large number of TCP query connections to the ro=
ot
> servers."
>=20
> A query send to one of the root servers with a long name (length 255)
> shows that the answer is 511 bytes, returning one A and 13 NS records.
> My question is: Why are all 13 NS returned?

BIND adds an additional section that is optional. If this section weren't
provided, then more root servers could be added.  It has been pointed out
that this additional section information is ignored by most resolvers, an=
d
so it useless, except to persons manually interpreting the output of DNS
query details. Some nameservers do not provide this additional data.  It
would be operationally advantageous to use a nameserver software on the
Root servers that did not provide the additional section.

However, I think your interest is in regard to DNSSEC deployment. There
are other problems with DNSSEC deployment, that limit or preclude
widespread utility. I can't cover them all in one message.  But suffice i=
t
to say that DNSSEC isn't really secure, and that further, the root server=
s
operators have widely adopted a dubious anycast replication model that
won't work well with TCP and load-balancing BGP configurations that are
gaining the interest of ISPs. Such load balancing configurations will sen=
d
packets over different paths to the same IP address. This is significant
because an Anycast server is two (or more) physical servers with the same
IP address, but with different paths to each server to distribute load. =20
Anycast will not cause problems with single packet UDP DNS queries, but
will have problems with load balanced, TCP connections, especially where
BGP load balancing configurations would be likely to send packets over
different paths (and thus to different anycast servers) within a very
short period of time, perhaps even sequential packets could sent over
different paths.

This dubious anycast configuration was discussed and "approved" by the
NAMEDROPPERS Working Group in late November, 2002. Unfortunately for the
anycast discussion, the list then became distracted by discussions
concerning procedural irregularities involving the AXFR-clarify Draft,
which would have altered the DNS AXFR and IXFR protocol to conform to the
non-standard ISC/BIND implementation, despite a number of other
implementations being able to follow the AXFR and IXFR specifications. =20
This quickly developed into a discussion regarding abuse by the list
administrator (Randy Bush) with respect to Dan Bernstein, and so the
anycast discussion was abandoned.

As the IETF list members are perhaps unaware, the charges of abuse by ISC
and ISC-promoters is hardly new.  It is very hard to get real work done i=
n
the DNS working groups as a result.  ISC/BIND promoters have the working
group tied up with gratuitous alterations to widely implemented protocols
(eg AXFR-clarify) and irrational and misleading changes (eg IN-ADDR
required) that have been demonstrated to either be security risks or
dangerously misleading security placebo's, and have tried to suppress
dissent on these issues by refusing to accept email, and in the past,
silently discarding email, and otherwise harrassing people who offer
reasoned and detailed objections.=20

I and others would probably be more involved in issues like DNSSEC, and n=
o
doubt more progress would be made, if it weren't for the distractions of
the mismanagement of the IETF and its working groups.

Dean Anderson
Av8 Internet, Inc


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


From exim@www1.ietf.org  Sun May 16 18:33: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 SAA26125
	for <ietf-archive@odin.ietf.org>; Sun, 16 May 2004 18:33: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 1BPU9w-0000e8-UB
	for ietf-archive@odin.ietf.org; Sun, 16 May 2004 18:31:13 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4GMV4u7002457
	for ietf-archive@odin.ietf.org; Sun, 16 May 2004 18:31:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPU54-0008M3-77; Sun, 16 May 2004 18:26:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPU3i-00087e-NT
	for ietf@optimus.ietf.org; Sun, 16 May 2004 18:24: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 SAA25693
	for <ietf@ietf.org>; Sun, 16 May 2004 18:24:31 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPU3d-0003sa-95
	for ietf@ietf.org; Sun, 16 May 2004 18:24:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPU2g-0003YG-00
	for ietf@ietf.org; Sun, 16 May 2004 18:23:35 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPU1z-0003Be-00
	for ietf@ietf.org; Sun, 16 May 2004 18:22:51 -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 i4GMMDKE002235
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Sun, 16 May 2004 18:22:14 -0400
Date: Sun, 16 May 2004 18:22:13 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Thomas Bocek <draft@icu.unizh.ch>
cc: ietf@ietf.org
Subject: Re: 13 Root Server Limitation
In-Reply-To: <1084734804.40a7bd54f3d8f@www.bocek.ch>
Message-ID: <Pine.LNX.4.44.0405161706080.678-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by cirrus.av8.net id i4GMMDKE002235
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,OFFERS_ETC 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

On Sun, 16 May 2004, Thomas Bocek wrote:

> Hi
>=20
> I=92m confused with the fact than the number of root servers is limited=
 to 13.
> From RFC 3226:
>=20
> "The current number of root servers is limited to 13 as that is the max=
imum
> number of name servers and their address records that fit in one 512-oc=
tet
> answer for a SOA record.  If root servers start advertising A6 or KEY r=
ecords
> then the answer for the root NS records will not fit in a single 512-oc=
tet DNS
> message, resulting in a large number of TCP query connections to the ro=
ot
> servers."
>=20
> A query send to one of the root servers with a long name (length 255)
> shows that the answer is 511 bytes, returning one A and 13 NS records.
> My question is: Why are all 13 NS returned?

BIND adds an additional section that is optional. If this section weren't
provided, then more root servers could be added.  It has been pointed out
that this additional section information is ignored by most resolvers, an=
d
so it useless, except to persons manually interpreting the output of DNS
query details. Some nameservers do not provide this additional data.  It
would be operationally advantageous to use a nameserver software on the
Root servers that did not provide the additional section.

However, I think your interest is in regard to DNSSEC deployment. There
are other problems with DNSSEC deployment, that limit or preclude
widespread utility. I can't cover them all in one message.  But suffice i=
t
to say that DNSSEC isn't really secure, and that further, the root server=
s
operators have widely adopted a dubious anycast replication model that
won't work well with TCP and load-balancing BGP configurations that are
gaining the interest of ISPs. Such load balancing configurations will sen=
d
packets over different paths to the same IP address. This is significant
because an Anycast server is two (or more) physical servers with the same
IP address, but with different paths to each server to distribute load. =20
Anycast will not cause problems with single packet UDP DNS queries, but
will have problems with load balanced, TCP connections, especially where
BGP load balancing configurations would be likely to send packets over
different paths (and thus to different anycast servers) within a very
short period of time, perhaps even sequential packets could sent over
different paths.

This dubious anycast configuration was discussed and "approved" by the
NAMEDROPPERS Working Group in late November, 2002. Unfortunately for the
anycast discussion, the list then became distracted by discussions
concerning procedural irregularities involving the AXFR-clarify Draft,
which would have altered the DNS AXFR and IXFR protocol to conform to the
non-standard ISC/BIND implementation, despite a number of other
implementations being able to follow the AXFR and IXFR specifications. =20
This quickly developed into a discussion regarding abuse by the list
administrator (Randy Bush) with respect to Dan Bernstein, and so the
anycast discussion was abandoned.

As the IETF list members are perhaps unaware, the charges of abuse by ISC
and ISC-promoters is hardly new.  It is very hard to get real work done i=
n
the DNS working groups as a result.  ISC/BIND promoters have the working
group tied up with gratuitous alterations to widely implemented protocols
(eg AXFR-clarify) and irrational and misleading changes (eg IN-ADDR
required) that have been demonstrated to either be security risks or
dangerously misleading security placebo's, and have tried to suppress
dissent on these issues by refusing to accept email, and in the past,
silently discarding email, and otherwise harrassing people who offer
reasoned and detailed objections.=20

I and others would probably be more involved in issues like DNSSEC, and n=
o
doubt more progress would be made, if it weren't for the distractions of
the mismanagement of the IETF and its working groups.

Dean Anderson
Av8 Internet, Inc


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



From ietf-admin@ietf.org  Sun May 16 19:04: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 TAA27457
	for <ietf-archive@ietf.org>; Sun, 16 May 2004 19:04: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 1BPUgB-00008E-E9
	for ietf-archive@ietf.org; Sun, 16 May 2004 19:04:23 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPUfE-0007Tj-00
	for ietf-archive@ietf.org; Sun, 16 May 2004 19:03:25 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPUe0-000718-00
	for ietf-archive@ietf.org; Sun, 16 May 2004 19:02:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPUZ4-0003TP-Fh; Sun, 16 May 2004 18:57:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPUYl-0003O1-Ct
	for ietf@optimus.ietf.org; Sun, 16 May 2004 18:56: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 SAA27029
	for <ietf@ietf.org>; Sun, 16 May 2004 18:56: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 1BPUYi-0005SJ-56
	for ietf@ietf.org; Sun, 16 May 2004 18:56:40 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPUXc-000585-00
	for ietf@ietf.org; Sun, 16 May 2004 18:55:32 -0400
Received: from weasel.corp.ntrg.com ([207.65.71.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPUWs-0004dg-00
	for ietf@ietf.org; Sun, 16 May 2004 18:54:46 -0400
Received: from [207.65.71.20] (account ehall HELO ehsco.com)
  by weasel.corp.ntrg.com (CommuniGate Pro SMTP 4.1.8)
  with ESMTP-TLS id 80685 for ietf@ietf.org; Sun, 16 May 2004 17:54:11 -0500
Message-ID: <40A7F112.4060305@ehsco.com>
Date: Sun, 16 May 2004 17:54:10 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: ftp license
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


ftp://www1.ietf.org/

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

  NOTICE:  The archive maintainer is running an expired
           evaluation copy of the FTP server software.
           Please encourage the maintainer to license the
           software now at http://www.ncftp.com/order/ !

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

Please wait 23 seconds.
Wasn't that annoying?  Tell your site administrators that the delay
goes away when they license the software.



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


From exim@www1.ietf.org  Sun May 16 19:04: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 TAA27514
	for <ietf-archive@odin.ietf.org>; Sun, 16 May 2004 19:04: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 1BPUe3-0004CB-1F
	for ietf-archive@odin.ietf.org; Sun, 16 May 2004 19:02:11 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4GN2A9h016075
	for ietf-archive@odin.ietf.org; Sun, 16 May 2004 19:02:11 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPUZ4-0003TP-Fh; Sun, 16 May 2004 18:57:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPUYl-0003O1-Ct
	for ietf@optimus.ietf.org; Sun, 16 May 2004 18:56: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 SAA27029
	for <ietf@ietf.org>; Sun, 16 May 2004 18:56: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 1BPUYi-0005SJ-56
	for ietf@ietf.org; Sun, 16 May 2004 18:56:40 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPUXc-000585-00
	for ietf@ietf.org; Sun, 16 May 2004 18:55:32 -0400
Received: from weasel.corp.ntrg.com ([207.65.71.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPUWs-0004dg-00
	for ietf@ietf.org; Sun, 16 May 2004 18:54:46 -0400
Received: from [207.65.71.20] (account ehall HELO ehsco.com)
  by weasel.corp.ntrg.com (CommuniGate Pro SMTP 4.1.8)
  with ESMTP-TLS id 80685 for ietf@ietf.org; Sun, 16 May 2004 17:54:11 -0500
Message-ID: <40A7F112.4060305@ehsco.com>
Date: Sun, 16 May 2004 17:54:10 -0500
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: ftp license
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


ftp://www1.ietf.org/

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

  NOTICE:  The archive maintainer is running an expired
           evaluation copy of the FTP server software.
           Please encourage the maintainer to license the
           software now at http://www.ncftp.com/order/ !

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

Please wait 23 seconds.
Wasn't that annoying?  Tell your site administrators that the delay
goes away when they license the software.



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



From ietf-admin@ietf.org  Sun May 16 19:13:44 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27792
	for <ietf-archive@ietf.org>; Sun, 16 May 2004 19:13: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 1BPUpG-0002hH-2d
	for ietf-archive@ietf.org; Sun, 16 May 2004 19:13:46 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPUoE-0002OL-00
	for ietf-archive@ietf.org; Sun, 16 May 2004 19:12:42 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPUnY-00025d-00
	for ietf-archive@ietf.org; Sun, 16 May 2004 19:12:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPUgp-0004YL-1E; Sun, 16 May 2004 19:05:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPUfH-0004Mz-8S
	for ietf@optimus.ietf.org; Sun, 16 May 2004 19:03: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 TAA27387
	for <ietf@ietf.org>; Sun, 16 May 2004 19:03: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 1BPUfB-0007Qs-O8
	for ietf@ietf.org; Sun, 16 May 2004 19:03:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPUdu-00070i-00
	for ietf@ietf.org; Sun, 16 May 2004 19:02:03 -0400
Received: from felix.automagic.org ([204.152.186.101])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPUco-0006dh-00
	for ietf@ietf.org; Sun, 16 May 2004 19:00:54 -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 1BPUcm-000N55-6a; Sun, 16 May 2004 23:00:52 +0000
In-Reply-To: <Pine.LNX.4.44.0405161706080.678-100000@cirrus.av8.net>
References: <Pine.LNX.4.44.0405161706080.678-100000@cirrus.av8.net>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <F05AE9AF-A78C-11D8-BE47-000A95E7E6B4@isc.org>
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, Thomas Bocek <draft@icu.unizh.ch>
From: Joe Abley <jabley@isc.org>
Subject: Re: 13 Root Server Limitation
Date: Sun, 16 May 2004 19:01:17 -0400
To: Dean Anderson <dean@av8.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 16 May 2004, at 18:22, Dean Anderson wrote:

> ... and that further, the root servers
> operators have widely adopted a dubious anycast replication model that
> won't work well with TCP and load-balancing BGP configurations that are
> gaining the interest of ISPs. Such load balancing configurations will 
> send
> packets over different paths to the same IP address. This is 
> significant
> because an Anycast server is two (or more) physical servers with the 
> same
> IP address, but with different paths to each server to distribute load.

This is not the case with F (I can't speak for other operators 
deploying Internet-scope anycast services). The different paths are 
made available in order to provide redundancy and diversity, and 
absolutely not to share load.

If you have an example of someone enabling multi-path BGP hacks in 
order to allow selection of more than one path, and specifically one 
who has ever selected two or more paths to different nodes of F (that 
is, paths to 192.5.5.0/24) I would be very interested to hear about it.

Feedback and measurement data we have seen has not yet revealed an 
occurrence of this, and conversations so far with operators does not 
suggest there is much risk that we will. Your data will be interesting 
to hear, however, if you can pass it on.

> Anycast will not cause problems with single packet UDP DNS queries, but
> will have problems with load balanced, TCP connections, especially 
> where
> BGP load balancing configurations would be likely to send packets over
> different paths (and thus to different anycast servers) within a very
> short period of time, perhaps even sequential packets could sent over
> different paths.

There is a risk that during a routing transition, when one path to 
192.5.5.0/24 is promoted over another due to a link failure or some 
other policy or topology change, a TCP transaction to an anycast node 
will fail. This is documented in both ISC technical notes written to 
describe what we are doing with F.

Our experience is that such route churn is of such a low frequency that 
the effect on extremely transient TCP DNS transactions is statistically 
negligible (and quite possibly indistinguishable from timeouts during 
reconvergence events to non-anycast servers). In addition, before the 
frequency of the route churn became sufficiently high to cause a 
problem, it would be well and truly damped to death by anybody running 
with common BGP damping parameters and the inability to talk to the few 
root servers which have anycast instances would be the last of your 
problems.

There's a specific section in ISC-TN-2004-1 which describes the 
applicability of cluster-scope anycast to protocols with longer-lived 
transaction times than DNS, and which warns implementers to test 
thoroughly since the opportunities for flows switching between hosts is 
greater there than in the global/BGP case. This is not the case you 
were talking about, but I mention it anyway for completeness.

Just thought I'd add some operational perspective to this particular 
point. I have no useful comments to make on the rest of your message, 
since I am neither a BIND developer nor a DNS/DNSSEC architect.


Joe


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


From exim@www1.ietf.org  Sun May 16 19:14:21 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 TAA27828
	for <ietf-archive@odin.ietf.org>; Sun, 16 May 2004 19:14:21 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPUnZ-0005f4-Ov
	for ietf-archive@odin.ietf.org; Sun, 16 May 2004 19:12:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4GNC1mv021755
	for ietf-archive@odin.ietf.org; Sun, 16 May 2004 19:12:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPUgp-0004YL-1E; Sun, 16 May 2004 19:05:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPUfH-0004Mz-8S
	for ietf@optimus.ietf.org; Sun, 16 May 2004 19:03: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 TAA27387
	for <ietf@ietf.org>; Sun, 16 May 2004 19:03: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 1BPUfB-0007Qs-O8
	for ietf@ietf.org; Sun, 16 May 2004 19:03:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPUdu-00070i-00
	for ietf@ietf.org; Sun, 16 May 2004 19:02:03 -0400
Received: from felix.automagic.org ([204.152.186.101])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPUco-0006dh-00
	for ietf@ietf.org; Sun, 16 May 2004 19:00:54 -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 1BPUcm-000N55-6a; Sun, 16 May 2004 23:00:52 +0000
In-Reply-To: <Pine.LNX.4.44.0405161706080.678-100000@cirrus.av8.net>
References: <Pine.LNX.4.44.0405161706080.678-100000@cirrus.av8.net>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <F05AE9AF-A78C-11D8-BE47-000A95E7E6B4@isc.org>
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, Thomas Bocek <draft@icu.unizh.ch>
From: Joe Abley <jabley@isc.org>
Subject: Re: 13 Root Server Limitation
Date: Sun, 16 May 2004 19:01:17 -0400
To: Dean Anderson <dean@av8.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 16 May 2004, at 18:22, Dean Anderson wrote:

> ... and that further, the root servers
> operators have widely adopted a dubious anycast replication model that
> won't work well with TCP and load-balancing BGP configurations that are
> gaining the interest of ISPs. Such load balancing configurations will 
> send
> packets over different paths to the same IP address. This is 
> significant
> because an Anycast server is two (or more) physical servers with the 
> same
> IP address, but with different paths to each server to distribute load.

This is not the case with F (I can't speak for other operators 
deploying Internet-scope anycast services). The different paths are 
made available in order to provide redundancy and diversity, and 
absolutely not to share load.

If you have an example of someone enabling multi-path BGP hacks in 
order to allow selection of more than one path, and specifically one 
who has ever selected two or more paths to different nodes of F (that 
is, paths to 192.5.5.0/24) I would be very interested to hear about it.

Feedback and measurement data we have seen has not yet revealed an 
occurrence of this, and conversations so far with operators does not 
suggest there is much risk that we will. Your data will be interesting 
to hear, however, if you can pass it on.

> Anycast will not cause problems with single packet UDP DNS queries, but
> will have problems with load balanced, TCP connections, especially 
> where
> BGP load balancing configurations would be likely to send packets over
> different paths (and thus to different anycast servers) within a very
> short period of time, perhaps even sequential packets could sent over
> different paths.

There is a risk that during a routing transition, when one path to 
192.5.5.0/24 is promoted over another due to a link failure or some 
other policy or topology change, a TCP transaction to an anycast node 
will fail. This is documented in both ISC technical notes written to 
describe what we are doing with F.

Our experience is that such route churn is of such a low frequency that 
the effect on extremely transient TCP DNS transactions is statistically 
negligible (and quite possibly indistinguishable from timeouts during 
reconvergence events to non-anycast servers). In addition, before the 
frequency of the route churn became sufficiently high to cause a 
problem, it would be well and truly damped to death by anybody running 
with common BGP damping parameters and the inability to talk to the few 
root servers which have anycast instances would be the last of your 
problems.

There's a specific section in ISC-TN-2004-1 which describes the 
applicability of cluster-scope anycast to protocols with longer-lived 
transaction times than DNS, and which warns implementers to test 
thoroughly since the opportunities for flows switching between hosts is 
greater there than in the global/BGP case. This is not the case you 
were talking about, but I mention it anyway for completeness.

Just thought I'd add some operational perspective to this particular 
point. I have no useful comments to make on the rest of your message, 
since I am neither a BIND developer nor a DNS/DNSSEC architect.


Joe


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



From ietf-admin@ietf.org  Sun May 16 21:20: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 VAA02410
	for <ietf-archive@ietf.org>; Sun, 16 May 2004 21:20: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 1BPWnn-0000cj-5N
	for ietf-archive@ietf.org; Sun, 16 May 2004 21:20:23 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPWmo-0000KG-00
	for ietf-archive@ietf.org; Sun, 16 May 2004 21:19:23 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPWlj-0007ZE-00
	for ietf-archive@ietf.org; Sun, 16 May 2004 21:18:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPWdo-0001mV-94; Sun, 16 May 2004 21:10:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPWdL-0001fe-HE
	for ietf@optimus.ietf.org; Sun, 16 May 2004 21:09: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 VAA01965
	for <ietf@ietf.org>; Sun, 16 May 2004 21:09: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 1BPWdH-00056M-Lv
	for ietf@ietf.org; Sun, 16 May 2004 21:09:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPWcN-0004mu-00
	for ietf@ietf.org; Sun, 16 May 2004 21:08:36 -0400
Received: from mx01.plaxo.com ([66.54.249.34] helo=mx.plaxo.com)
	by ietf-mx with smtp (Exim 4.12)
	id 1BPWbK-0004TZ-00
	for ietf@ietf.org; Sun, 16 May 2004 21:07:30 -0400
Received: (qmail 6759 invoked from network); 17 May 2004 01:07:30 -0000
Received: from unknown (10.1.0.5)
  by mx2.plaxo.com with QMQP; 17 May 2004 01:07:30 -0000
Received: from 152.226.6.205 by pas02.plaxo.com; 17 May 2004 01:06:39 -0000
Message-ID: <1084756050.21355.196113.sendUpdate@mx.plaxo.com>
Date: 17 May 2004 01:07:30 -0000
From: "Hung Peng Chua" <hungpeng@tp.edu.sg>
To: "IETF" <ietf@ietf.org>
Reply-to: "Plaxo Contact Update for Hung Peng Chua" <addrupdate-25770196726-11977359-129946132-1SH@mx.plaxo.com>
Precedence: bulk
Subject: Your Contact Info
MIME-Version: 1.0
Content-Type: multipart/mixed;
 boundary="_-------==3400467814"
Sender: ietf-admin@ietf.org
Errors-To: ietf-admin@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.0.12
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.5 required=5.0 tests=CLICK_BELOW,EXCUSE_14,
	HTML_70_80,HTML_LINK_CLICK_HERE,HTML_MESSAGE,HTML_TAG_EXISTS_TBODY 
	autolearn=no version=2.60

This is a multi-part message in MIME format.

--_-------==3400467814
Content-Type: multipart/alternative;
	boundary="_--=======792966920"

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

IETF,

I'm updating my address book. Please take a moment to update
your latest contact information. Your information is stored in
my personal address book and will not be shared with anyone
else. 

Thanks,


Click the following link to correct or confirm your information: https://www.plaxo.com/edit_contact_info?r=25770196726-11977359-129946132

Name: IETF
Job Title: 
Company: 
Work E-mail: ietf@ietf.org
Work Phone: 
Work Fax: 
Work Address Line 1: 
Work Address Line 2: 
Work City, State, Zip: 
Mobile Phone: 

Home E-mail: 
Home Phone: 
Home Fax: 
Home Address Line 1: 
Home Address Line 2: 
Home City, State, Zip: 
Birthday: 
My current contact information:




P.S. I've included my Plaxo card below so that you have my current information.  I've also attached a copy as a vCard.

 +-----------------
 | Hung Peng Chua
 | hungpeng@tp.edu.sg
 | Educator
 | 
 | Temasek Polytechnic
 | 21 Tampines Avenue 1
 | Singapore 529757
 | work: 65-67805434
 | fax: 65-67874247
 +-------------------------------------

____________________________________________________________
This message was sent to you by hungpeng@tp.edu.sg
via Plaxo.  

To opt out: https://www.plaxo.com/opt_out?r=25770196726-11977359-129946132

Plaxo's Privacy Policy: http://www.plaxo.com/support/privacy

--_--=======792966920
Content-Type: text/html;
	charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit



<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<HEAD>
<TITLE>Your Contact Info</TITLE>
<META http-equiv=Content-Type content="text/html; charset=ISO-8859-1">

<style type=text/css rel=stylesheet>
<!-- 
/* base styles */

table { font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 9pt; color: #333333; }
body,p { line-height: 135%; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 9pt; color: #333333; }
th { background-color: #d7e6ff; font-size: 10pt;  font-weight: bold; }
h1,.h1 { font-family: "Arial Narrow",Arial,Helvetica,sans-serif; font-size: 20pt; font-weight: bold; color: #3d69ad; margin-bottom: 6px; }
h2,.h2 { font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 12pt; font-weight: bold; color: #3d69ad; margin-bottom: 0px; }
h3,.h3 { font-size: 10pt; font-weight: bold; color: #555555; }
a { color: #000099; }
a.on_dark { color: #94c6ff; }

/* template styles */

.welcome { color: #333333; }
.nav_unselect { color: #CCCCCC; }
.body_black { line-height: 135%; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 9pt; color: #000000; }
.body_small, .body_small_black { line-height: 135%; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 8pt; color: #777777; }
.body_small_black { color: #000000; }
.body_very_small, .body_very_small_black { line-height: 135%; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 7pt; color: #777777; }
.body_very_small_black { color: #000000; }
.body_small_fixed { font-size: 10pt; color: #333333; font-family: Courier New, Courier, monospace; }
.update_msg_body { font-size: 10pt; color: #333333; font-family: Verdana, Arial, Helvetica, sans-serif; line-height: 135%; }
.icon_menu { font-size: 10pt; color: #FFFFFF; }
.error_msg { font-size: 12pt; color: #FF0000; font-weight: bold; }
.column_title { font-weight: bold; }
.column_text { font-size: 8pt; }
.feature_text { font-family: Arial, Helvetica, sans-serif; font-size: 14pt; color: #FFAA00; font-weight: bold; }
.feature_body { font-family: Arial, Helvetica, sans-serif; font-size: 11pt; color: #555555; font-weight: normal; }
.bottom_bar { font-family: Arial, Helvetica, sans-serif; font-size: 8pt; color: #dddddd; }
.reg_label { line-height: 135%; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 7pt; color: #000000; }
.update_link { color: #0033cc; font-weight: bold; text-decoration: none }
.update_link:hover { text-decoration: underline }

/* table styles */

.table_title { color: 3d69a6; font-size: 10pt; font-weight: bold; background-color: #e6e6e6; }
.table_subtitle { font-size: 8pt; font-weight: bold; background-color: #dbdfe3; }
.table_text { font-size: 8pt; }
.table_text_large_bold { font-weight: bold; }
.even_row { color: #333333; font-size: 8pt; background-color: #f3f3f3; }
.odd_row { color: #333333; font-size: 8pt; background-color: #ffffff; }
.table_rule { background-color: #333333; padding-top: 0px; padding-bottom: 0px; }
.tiny { font-size: 1pt; }
.no_entries { border: 1px solid black; padding: 8px; background-color: #d7e6ff; }

/* misc styles */

.copyright { font-size: 8pt; color: 84A3C7; }
.fieldLabel { font-weight: bold; }
.fieldValue { font-family: monospace; }
.nav_footer { font-size: 8pt; color: #A6A6A6; }
.preview { font-size: 7.5pt; background-color: #CFD4DD; }
.previewHeader { font-size: 10pt; color: #ffffff; background-color: #4E81C4; }
.previewAddress { margin-left: 3px; }
.subnav { font-size: 7pt; color: white; text-decoration: none; }
.subheader { font-size: 11pt; padding: 2px; font-weight: bold; background-color: #d7e6ff; }

/* new styles */

.section_title { font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 12px; font-weight: bold; color: #4e81c4; }
.table_small, .table_small_label {  font-family: Verdana, Arial, Helvetica, sans-serif; font-size: xx-small; color: #888888; }
.table_small_label { color: #000000; font-weight: normal; }
.invite { font: normal 22px Verdana, Arial, Helvetica, sans-serif; letter-spacing: -0.02em; }
.formText1 { font: 9px/15px Verdana, Arial, Helvetica, sans-serif; }
.formText2 { font: 11px/16px Verdana, Arial, Helvetica, sans-serif; }

/* busines card styles */

.card_comapny_large, .card_name, .card_name_changed { font-family: Arial, Helvetica, sans-serif; color: #000000; font-size: 12px; font-weight: bold; }
.card_company_large { font-size: 14px; }
.card_name_changed { color: red; }

.card_field, .card_field_none, .card_field_changed { font-family: Verdana, Arial, Helvetica, sans-serif; font-size: xx-small; }
.card_field { color: #888888; }
.card_field_none { color: #bb5555; }
.card_field_changed { color: red; }

/* anchor styles */

A.contactlink {text-decoration:none; color: #666666; }
A.cardlink {text-decoration:none; color: #888888; }
A.cardlink:hover, A.cardlink_changed:hover, A.contactlink:hover {text-decoration:none; color: #0066CC; }
A.cardlink_changed {text-decoration:none; color: red; }

// -->
</style>

</HEAD>
<BODY bgColor=white topMargin=20 marginwidth="0" marginheight="0">
<TABLE cellSpacing=0 cellPadding=0 border=0>
<TBODY>
 <TR>
  <TD>
   <TABLE border=0 cellSpacing=0 cellPadding=0>
   <TBODY> 

      
  <TR>
   <TD colspan=2 valign=top>



</TD>
  </TR>
  

    <TR> 
     <TD vAlign=top width="330">

	    <P class=update_msg_body>IETF,</P>
	    <P class=update_msg_body>I'm updating my address book. Please take a moment to update your latest contact information. Your information is stored in my personal address book and will not be shared with anyone else. <br><br>Thanks,<br></P>
        <P class=update_msg_body>Hung Peng Chua
  
  <BR>hungpeng@tp.edu.sg
  <BR>Temasek Polytechnic
  
  </P>


	    <P class=update_msg_body>&nbsp;</P>
     </TD>

     <TD align=left vAlign=top style="padding-left: 5px;"> 
        <!-- begin of card meta table -->
  <TABLE align=left cellSpacing=0 cellPadding=0 border=0>
  <TBODY> 
   <TR>
    <TD align="center" style="padding-bottom: 2px"><a class="update_link" href="https://www.plaxo.com/edit_contact_info?r=25770196726-11977359-129946132&t=web">Click the buttons below to change or confirm your info</a></TD>
   </TR>
   <TR> 
    <TD valign=top>
     <!-- INSERT CARD HERE -->
     
  <table cellpadding=0 cellspacing=0 border=0 align=center width=320><tr><td>

        <table border=0 width="100%" cellpadding=0 cellspacing=0 align="center">
          <tr> 
	    

            <td valign=top> 
              <table cellpadding="0" cellspacing="0" class="body_small" align="center" height=100 width="100%"
              style="border-top: 1px solid #cccccc; border-left: 1px solid #cccccc;
                      border-right: 1px solid #888888; border-bottom: 1px solid #888888;">

                <tr>
                  <!-- padding for business card body -->
                  <td valign="top" style="padding: 10px 11px 10px 11px;">
		    <!-- start card contents -->

  <table border=0 cellspacing=0 cellpadding=0 id="PlaxoCard.Biz" width="100%">
    
    <tr>
      <td colspan=1 valign="top" nowrap >
	<span class="card_name">
	
	<span id="START.PlaxoField.Biz.FullName"></span>IETF<span id="END.PlaxoField.Biz.FullName"></span>
        
	</span><br>
	<span class="table_small"><span id="START.PlaxoField.Biz.Title"></span><span class="card_field_none">no title</span><span id="END.PlaxoField.Biz.Title"></span></span><br>
      </td>
      
      <td class="table_small" style="padding-left: 18px" height=8></td>
      
      <td colspan=1 align="right" valign=top nowrap style="padding-bottom: 6px;" width="1%">
	<span class="card_name">
	<span id="START.PlaxoField.Biz.Company"></span><span class="card_field_none">no company</span><span id="END.PlaxoField.Biz.Company"></span><br>
	</span>
	<span class="table_small">
	
	<span id="START.PlaxoField.Biz.Address"></span>
	<span class="card_field_none">
  

        no work address
	<br>&nbsp;
	


	</span>
	<span id="END.PlaxoField.Biz.Address"></span>
	
	</span>
      </td>
    </tr>
    <tr>
      <td colspan=3 class="table_small" width="100%" height=20></td>
    </tr>
    <tr>
        <td class="table_small" width="100%" nowrap align=left valign="bottom">
	  <br><br>
	             <a target=_blank href="mailto:ietf@ietf.org" class=cardlink>
<span id="START.PlaxoField.Biz.Email1"></span>ietf@ietf.org           </a>
<span id="END.PlaxoField.Biz.Email1"></span><br>
  	  
	  
	  <span id="START.PlaxoField.Biz.WebPage"></span><span class="card_field_none">no web page</span><span id="END.PlaxoField.Biz.WebPage"></span><br>
	  <span class="table_small_label">IM:&nbsp;</span><span id="START.PlaxoField.Biz.IM"></span><span class="card_field_none">none</span><span id="END.PlaxoField.Biz.IM"></span><br>
        </td>

      <td class="table_small" align="right" width="1%" height=8></td>

      <td class="table_small" width="1%" valign="bottom" align="right">
        <br>

        <table cellspacing=0 cellpadding=0>
	 <tr><td class="table_small_label" align="right">work:&nbsp;</td><td class="table_small" nowrap align=right><span id="START.PlaxoField.Biz.Phone1"></span><span class="card_field_none">none</span><span id="END.PlaxoField.Biz.Phone1"></span></td></tr>
	 
	 <tr><td class="table_small_label" align="right">fax:&nbsp;</td><td class="table_small" nowrap align=right><span id="START.PlaxoField.Biz.Fax"></span><span class="card_field_none">none</span><span id="END.PlaxoField.Biz.Fax"></span></td></tr>
	 <tr><td class="table_small_label" align="right">mobile:&nbsp;</td><td class="table_small" nowrap align=right><span id="START.PlaxoField.Biz.Mobile"></span><span class="card_field_none">none</span><span id="END.PlaxoField.Biz.Mobile"></span></td></tr>
	 <tr><td class="table_small_label" align="right">pager:&nbsp;</td><td class="table_small" nowrap align=right><span id="START.PlaxoField.Biz.Pager"></span><span class="card_field_none">none</span><span id="END.PlaxoField.Biz.Pager"></span></td></tr>
         
	</table>
      </td>
    </tr>
  </table>

                  </td>
                </tr>
                <!-- begin separator line between business and personal info -->
		<tr>
  		  <td height="1" width="100%">
                    <table class="tiny" align="center" cellpadding=0 cellspacing=0 width="90%"><tr><td height="9" style="border-top: 1px solid #cccccc">&nbsp;</td></tr></table>
                  </td>
                </td>
		</tr>
                <!-- end separator line between business and personal info -->
		<tr>
                  <!-- padding for personal card body -->
		  <td valign="top" style="padding: 0 11 10 11;">


     <!-- START BUTTONS -->
    
     <table cellspacing=0 cellpadding=0>
       <tr>
    
       <td class=body_small_black nowrap>Is this information correct?&nbsp;</td>
    
       <td>
        <form name="form2" method="get" action="https://www.plaxo.com/edit_contact_info" style="padding: 1px; margin: 0px;">
         <input type="submit" style="background-color: #0099ff; border: 1px solid #888888; color: white; font-weight: bold" value="Change">
         <input type="hidden" name="t" value="web">
         <input type="hidden" name="r" value="25770196726-11977359-129946132">


        </form>
       </td>
    
       <td style="padding-left: 10px;">
        <form name="form1" method="get" action="https://www.plaxo.com/edit_contact_info" style="padding: 1px; margin: 0px;">
         <input type="submit" style="background-color: #33cccc; border: 1px solid #888888; color: white; font-weight: bold" value="Confirm">
         <input type="hidden" name="t" value="web">
         <input type="hidden" name="r" value="25770196726-11977359-129946132">


         <input type="hidden" name="update" value="0">
        </form>
       </td>
    
      </tr>
     </table>
     <!-- END BUTTON -->
    
     
		    <!-- end card contents -->
                  </td>
                </tr>
              </table>
            </td>
	    

  <td></td>


          </tr>
          <tr> 
	  
	    <td colspan=2>
	  
          </tr>
        </table>

     
  </td></tr></table>

     <!-- END OF CARD -->
    
     
    </TD>
   </TR>
  </TBODY>
  </TABLE> 
  <!-- end of card meta table -->

     </TD>
	  </TR>
	    <TR>
   <TD colspan=2>
    <P class="update_msg_body">P.S. I've attached my current information in a vcard. If you <a href="http://www.plaxo.com/downloads">get Plaxo</a> too, we'll stay in touch automatically.<BR></P>
   </TD>
  </TR>

   </TBODY>
   </TABLE>
  </TD>
 </TR>
</TBODY>
</TABLE>
<p style="font: 10px Verdana, Arial, Helvetica, sans-serif;">If you do not wish to receive update request emails from Hung Peng Chua, <a href="https://www.plaxo.com/opt_out?r=25770196726-11977359-129946132">click here</a> to opt-out.<br></p>
<!-- end master table -->
</BODY>

</HTML>

--_--=======792966920--


--_-------==3400467814
Content-Type: text/x-vcard; charset=ISO-8859-1; name="Hung Peng Chua.vcf"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment; filename="Hung Peng Chua.vcf"
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

BEGIN:VCARD 
VERSION:2.1
X-PLAXO-VERSION:1.0
N:Chua;Hung;Peng;;
FN:Hung Peng Chua
ORG:Temasek Polytechnic
TITLE:Educator
ADR;WORK;ENCODING=QUOTED-PRINTABLE:;;21 Tampines Avenue 1;;;529757;Singapore
TEL;WORK;VOICE:65-67805434
TEL;WORK;FAX:65-67874247
EMAIL;PREF;INTERNET:hungpeng@tp.edu.sg
END:VCARD

--_-------==3400467814--





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


From exim@www1.ietf.org  Sun May 16 21:20:49 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 VAA02453
	for <ietf-archive@odin.ietf.org>; Sun, 16 May 2004 21:20:49 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPWll-0002XR-Ve
	for ietf-archive@odin.ietf.org; Sun, 16 May 2004 21:18:21 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4H1IHvA009757
	for ietf-archive@odin.ietf.org; Sun, 16 May 2004 21:18:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPWdo-0001mV-94; Sun, 16 May 2004 21:10:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPWdL-0001fe-HE
	for ietf@optimus.ietf.org; Sun, 16 May 2004 21:09: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 VAA01965
	for <ietf@ietf.org>; Sun, 16 May 2004 21:09: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 1BPWdH-00056M-Lv
	for ietf@ietf.org; Sun, 16 May 2004 21:09:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPWcN-0004mu-00
	for ietf@ietf.org; Sun, 16 May 2004 21:08:36 -0400
Received: from mx01.plaxo.com ([66.54.249.34] helo=mx.plaxo.com)
	by ietf-mx with smtp (Exim 4.12)
	id 1BPWbK-0004TZ-00
	for ietf@ietf.org; Sun, 16 May 2004 21:07:30 -0400
Received: (qmail 6759 invoked from network); 17 May 2004 01:07:30 -0000
Received: from unknown (10.1.0.5)
  by mx2.plaxo.com with QMQP; 17 May 2004 01:07:30 -0000
Received: from 152.226.6.205 by pas02.plaxo.com; 17 May 2004 01:06:39 -0000
Message-ID: <1084756050.21355.196113.sendUpdate@mx.plaxo.com>
Date: 17 May 2004 01:07:30 -0000
From: "Hung Peng Chua" <hungpeng@tp.edu.sg>
To: "IETF" <ietf@ietf.org>
Reply-to: "Plaxo Contact Update for Hung Peng Chua" <addrupdate-25770196726-11977359-129946132-1SH@mx.plaxo.com>
Precedence: bulk
Subject: Your Contact Info
MIME-Version: 1.0
Content-Type: multipart/mixed;
 boundary="_-------==3400467814"
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=CLICK_BELOW,EXCUSE_14,
	HTML_70_80,HTML_LINK_CLICK_HERE,HTML_MESSAGE,HTML_TAG_EXISTS_TBODY 
	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
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.

--_-------==3400467814
Content-Type: multipart/alternative;
	boundary="_--=======792966920"

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

IETF,

I'm updating my address book. Please take a moment to update
your latest contact information. Your information is stored in
my personal address book and will not be shared with anyone
else. 

Thanks,


Click the following link to correct or confirm your information: https://www.plaxo.com/edit_contact_info?r=25770196726-11977359-129946132

Name: IETF
Job Title: 
Company: 
Work E-mail: ietf@ietf.org
Work Phone: 
Work Fax: 
Work Address Line 1: 
Work Address Line 2: 
Work City, State, Zip: 
Mobile Phone: 

Home E-mail: 
Home Phone: 
Home Fax: 
Home Address Line 1: 
Home Address Line 2: 
Home City, State, Zip: 
Birthday: 
My current contact information:




P.S. I've included my Plaxo card below so that you have my current information.  I've also attached a copy as a vCard.

 +-----------------
 | Hung Peng Chua
 | hungpeng@tp.edu.sg
 | Educator
 | 
 | Temasek Polytechnic
 | 21 Tampines Avenue 1
 | Singapore 529757
 | work: 65-67805434
 | fax: 65-67874247
 +-------------------------------------

____________________________________________________________
This message was sent to you by hungpeng@tp.edu.sg
via Plaxo.  

To opt out: https://www.plaxo.com/opt_out?r=25770196726-11977359-129946132

Plaxo's Privacy Policy: http://www.plaxo.com/support/privacy

--_--=======792966920
Content-Type: text/html;
	charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit



<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<HEAD>
<TITLE>Your Contact Info</TITLE>
<META http-equiv=Content-Type content="text/html; charset=ISO-8859-1">

<style type=text/css rel=stylesheet>
<!-- 
/* base styles */

table { font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 9pt; color: #333333; }
body,p { line-height: 135%; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 9pt; color: #333333; }
th { background-color: #d7e6ff; font-size: 10pt;  font-weight: bold; }
h1,.h1 { font-family: "Arial Narrow",Arial,Helvetica,sans-serif; font-size: 20pt; font-weight: bold; color: #3d69ad; margin-bottom: 6px; }
h2,.h2 { font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 12pt; font-weight: bold; color: #3d69ad; margin-bottom: 0px; }
h3,.h3 { font-size: 10pt; font-weight: bold; color: #555555; }
a { color: #000099; }
a.on_dark { color: #94c6ff; }

/* template styles */

.welcome { color: #333333; }
.nav_unselect { color: #CCCCCC; }
.body_black { line-height: 135%; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 9pt; color: #000000; }
.body_small, .body_small_black { line-height: 135%; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 8pt; color: #777777; }
.body_small_black { color: #000000; }
.body_very_small, .body_very_small_black { line-height: 135%; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 7pt; color: #777777; }
.body_very_small_black { color: #000000; }
.body_small_fixed { font-size: 10pt; color: #333333; font-family: Courier New, Courier, monospace; }
.update_msg_body { font-size: 10pt; color: #333333; font-family: Verdana, Arial, Helvetica, sans-serif; line-height: 135%; }
.icon_menu { font-size: 10pt; color: #FFFFFF; }
.error_msg { font-size: 12pt; color: #FF0000; font-weight: bold; }
.column_title { font-weight: bold; }
.column_text { font-size: 8pt; }
.feature_text { font-family: Arial, Helvetica, sans-serif; font-size: 14pt; color: #FFAA00; font-weight: bold; }
.feature_body { font-family: Arial, Helvetica, sans-serif; font-size: 11pt; color: #555555; font-weight: normal; }
.bottom_bar { font-family: Arial, Helvetica, sans-serif; font-size: 8pt; color: #dddddd; }
.reg_label { line-height: 135%; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 7pt; color: #000000; }
.update_link { color: #0033cc; font-weight: bold; text-decoration: none }
.update_link:hover { text-decoration: underline }

/* table styles */

.table_title { color: 3d69a6; font-size: 10pt; font-weight: bold; background-color: #e6e6e6; }
.table_subtitle { font-size: 8pt; font-weight: bold; background-color: #dbdfe3; }
.table_text { font-size: 8pt; }
.table_text_large_bold { font-weight: bold; }
.even_row { color: #333333; font-size: 8pt; background-color: #f3f3f3; }
.odd_row { color: #333333; font-size: 8pt; background-color: #ffffff; }
.table_rule { background-color: #333333; padding-top: 0px; padding-bottom: 0px; }
.tiny { font-size: 1pt; }
.no_entries { border: 1px solid black; padding: 8px; background-color: #d7e6ff; }

/* misc styles */

.copyright { font-size: 8pt; color: 84A3C7; }
.fieldLabel { font-weight: bold; }
.fieldValue { font-family: monospace; }
.nav_footer { font-size: 8pt; color: #A6A6A6; }
.preview { font-size: 7.5pt; background-color: #CFD4DD; }
.previewHeader { font-size: 10pt; color: #ffffff; background-color: #4E81C4; }
.previewAddress { margin-left: 3px; }
.subnav { font-size: 7pt; color: white; text-decoration: none; }
.subheader { font-size: 11pt; padding: 2px; font-weight: bold; background-color: #d7e6ff; }

/* new styles */

.section_title { font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 12px; font-weight: bold; color: #4e81c4; }
.table_small, .table_small_label {  font-family: Verdana, Arial, Helvetica, sans-serif; font-size: xx-small; color: #888888; }
.table_small_label { color: #000000; font-weight: normal; }
.invite { font: normal 22px Verdana, Arial, Helvetica, sans-serif; letter-spacing: -0.02em; }
.formText1 { font: 9px/15px Verdana, Arial, Helvetica, sans-serif; }
.formText2 { font: 11px/16px Verdana, Arial, Helvetica, sans-serif; }

/* busines card styles */

.card_comapny_large, .card_name, .card_name_changed { font-family: Arial, Helvetica, sans-serif; color: #000000; font-size: 12px; font-weight: bold; }
.card_company_large { font-size: 14px; }
.card_name_changed { color: red; }

.card_field, .card_field_none, .card_field_changed { font-family: Verdana, Arial, Helvetica, sans-serif; font-size: xx-small; }
.card_field { color: #888888; }
.card_field_none { color: #bb5555; }
.card_field_changed { color: red; }

/* anchor styles */

A.contactlink {text-decoration:none; color: #666666; }
A.cardlink {text-decoration:none; color: #888888; }
A.cardlink:hover, A.cardlink_changed:hover, A.contactlink:hover {text-decoration:none; color: #0066CC; }
A.cardlink_changed {text-decoration:none; color: red; }

// -->
</style>

</HEAD>
<BODY bgColor=white topMargin=20 marginwidth="0" marginheight="0">
<TABLE cellSpacing=0 cellPadding=0 border=0>
<TBODY>
 <TR>
  <TD>
   <TABLE border=0 cellSpacing=0 cellPadding=0>
   <TBODY> 

      
  <TR>
   <TD colspan=2 valign=top>



</TD>
  </TR>
  

    <TR> 
     <TD vAlign=top width="330">

	    <P class=update_msg_body>IETF,</P>
	    <P class=update_msg_body>I'm updating my address book. Please take a moment to update your latest contact information. Your information is stored in my personal address book and will not be shared with anyone else. <br><br>Thanks,<br></P>
        <P class=update_msg_body>Hung Peng Chua
  
  <BR>hungpeng@tp.edu.sg
  <BR>Temasek Polytechnic
  
  </P>


	    <P class=update_msg_body>&nbsp;</P>
     </TD>

     <TD align=left vAlign=top style="padding-left: 5px;"> 
        <!-- begin of card meta table -->
  <TABLE align=left cellSpacing=0 cellPadding=0 border=0>
  <TBODY> 
   <TR>
    <TD align="center" style="padding-bottom: 2px"><a class="update_link" href="https://www.plaxo.com/edit_contact_info?r=25770196726-11977359-129946132&t=web">Click the buttons below to change or confirm your info</a></TD>
   </TR>
   <TR> 
    <TD valign=top>
     <!-- INSERT CARD HERE -->
     
  <table cellpadding=0 cellspacing=0 border=0 align=center width=320><tr><td>

        <table border=0 width="100%" cellpadding=0 cellspacing=0 align="center">
          <tr> 
	    

            <td valign=top> 
              <table cellpadding="0" cellspacing="0" class="body_small" align="center" height=100 width="100%"
              style="border-top: 1px solid #cccccc; border-left: 1px solid #cccccc;
                      border-right: 1px solid #888888; border-bottom: 1px solid #888888;">

                <tr>
                  <!-- padding for business card body -->
                  <td valign="top" style="padding: 10px 11px 10px 11px;">
		    <!-- start card contents -->

  <table border=0 cellspacing=0 cellpadding=0 id="PlaxoCard.Biz" width="100%">
    
    <tr>
      <td colspan=1 valign="top" nowrap >
	<span class="card_name">
	
	<span id="START.PlaxoField.Biz.FullName"></span>IETF<span id="END.PlaxoField.Biz.FullName"></span>
        
	</span><br>
	<span class="table_small"><span id="START.PlaxoField.Biz.Title"></span><span class="card_field_none">no title</span><span id="END.PlaxoField.Biz.Title"></span></span><br>
      </td>
      
      <td class="table_small" style="padding-left: 18px" height=8></td>
      
      <td colspan=1 align="right" valign=top nowrap style="padding-bottom: 6px;" width="1%">
	<span class="card_name">
	<span id="START.PlaxoField.Biz.Company"></span><span class="card_field_none">no company</span><span id="END.PlaxoField.Biz.Company"></span><br>
	</span>
	<span class="table_small">
	
	<span id="START.PlaxoField.Biz.Address"></span>
	<span class="card_field_none">
  

        no work address
	<br>&nbsp;
	


	</span>
	<span id="END.PlaxoField.Biz.Address"></span>
	
	</span>
      </td>
    </tr>
    <tr>
      <td colspan=3 class="table_small" width="100%" height=20></td>
    </tr>
    <tr>
        <td class="table_small" width="100%" nowrap align=left valign="bottom">
	  <br><br>
	             <a target=_blank href="mailto:ietf@ietf.org" class=cardlink>
<span id="START.PlaxoField.Biz.Email1"></span>ietf@ietf.org           </a>
<span id="END.PlaxoField.Biz.Email1"></span><br>
  	  
	  
	  <span id="START.PlaxoField.Biz.WebPage"></span><span class="card_field_none">no web page</span><span id="END.PlaxoField.Biz.WebPage"></span><br>
	  <span class="table_small_label">IM:&nbsp;</span><span id="START.PlaxoField.Biz.IM"></span><span class="card_field_none">none</span><span id="END.PlaxoField.Biz.IM"></span><br>
        </td>

      <td class="table_small" align="right" width="1%" height=8></td>

      <td class="table_small" width="1%" valign="bottom" align="right">
        <br>

        <table cellspacing=0 cellpadding=0>
	 <tr><td class="table_small_label" align="right">work:&nbsp;</td><td class="table_small" nowrap align=right><span id="START.PlaxoField.Biz.Phone1"></span><span class="card_field_none">none</span><span id="END.PlaxoField.Biz.Phone1"></span></td></tr>
	 
	 <tr><td class="table_small_label" align="right">fax:&nbsp;</td><td class="table_small" nowrap align=right><span id="START.PlaxoField.Biz.Fax"></span><span class="card_field_none">none</span><span id="END.PlaxoField.Biz.Fax"></span></td></tr>
	 <tr><td class="table_small_label" align="right">mobile:&nbsp;</td><td class="table_small" nowrap align=right><span id="START.PlaxoField.Biz.Mobile"></span><span class="card_field_none">none</span><span id="END.PlaxoField.Biz.Mobile"></span></td></tr>
	 <tr><td class="table_small_label" align="right">pager:&nbsp;</td><td class="table_small" nowrap align=right><span id="START.PlaxoField.Biz.Pager"></span><span class="card_field_none">none</span><span id="END.PlaxoField.Biz.Pager"></span></td></tr>
         
	</table>
      </td>
    </tr>
  </table>

                  </td>
                </tr>
                <!-- begin separator line between business and personal info -->
		<tr>
  		  <td height="1" width="100%">
                    <table class="tiny" align="center" cellpadding=0 cellspacing=0 width="90%"><tr><td height="9" style="border-top: 1px solid #cccccc">&nbsp;</td></tr></table>
                  </td>
                </td>
		</tr>
                <!-- end separator line between business and personal info -->
		<tr>
                  <!-- padding for personal card body -->
		  <td valign="top" style="padding: 0 11 10 11;">


     <!-- START BUTTONS -->
    
     <table cellspacing=0 cellpadding=0>
       <tr>
    
       <td class=body_small_black nowrap>Is this information correct?&nbsp;</td>
    
       <td>
        <form name="form2" method="get" action="https://www.plaxo.com/edit_contact_info" style="padding: 1px; margin: 0px;">
         <input type="submit" style="background-color: #0099ff; border: 1px solid #888888; color: white; font-weight: bold" value="Change">
         <input type="hidden" name="t" value="web">
         <input type="hidden" name="r" value="25770196726-11977359-129946132">


        </form>
       </td>
    
       <td style="padding-left: 10px;">
        <form name="form1" method="get" action="https://www.plaxo.com/edit_contact_info" style="padding: 1px; margin: 0px;">
         <input type="submit" style="background-color: #33cccc; border: 1px solid #888888; color: white; font-weight: bold" value="Confirm">
         <input type="hidden" name="t" value="web">
         <input type="hidden" name="r" value="25770196726-11977359-129946132">


         <input type="hidden" name="update" value="0">
        </form>
       </td>
    
      </tr>
     </table>
     <!-- END BUTTON -->
    
     
		    <!-- end card contents -->
                  </td>
                </tr>
              </table>
            </td>
	    

  <td></td>


          </tr>
          <tr> 
	  
	    <td colspan=2>
	  
          </tr>
        </table>

     
  </td></tr></table>

     <!-- END OF CARD -->
    
     
    </TD>
   </TR>
  </TBODY>
  </TABLE> 
  <!-- end of card meta table -->

     </TD>
	  </TR>
	    <TR>
   <TD colspan=2>
    <P class="update_msg_body">P.S. I've attached my current information in a vcard. If you <a href="http://www.plaxo.com/downloads">get Plaxo</a> too, we'll stay in touch automatically.<BR></P>
   </TD>
  </TR>

   </TBODY>
   </TABLE>
  </TD>
 </TR>
</TBODY>
</TABLE>
<p style="font: 10px Verdana, Arial, Helvetica, sans-serif;">If you do not wish to receive update request emails from Hung Peng Chua, <a href="https://www.plaxo.com/opt_out?r=25770196726-11977359-129946132">click here</a> to opt-out.<br></p>
<!-- end master table -->
</BODY>

</HTML>

--_--=======792966920--


--_-------==3400467814
Content-Type: text/x-vcard; charset=ISO-8859-1; name="Hung Peng Chua.vcf"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment; filename="Hung Peng Chua.vcf"
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

BEGIN:VCARD 
VERSION:2.1
X-PLAXO-VERSION:1.0
N:Chua;Hung;Peng;;
FN:Hung Peng Chua
ORG:Temasek Polytechnic
TITLE:Educator
ADR;WORK;ENCODING=QUOTED-PRINTABLE:;;21 Tampines Avenue 1;;;529757;Singapore
TEL;WORK;VOICE:65-67805434
TEL;WORK;FAX:65-67874247
EMAIL;PREF;INTERNET:hungpeng@tp.edu.sg
END:VCARD

--_-------==3400467814--





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



From exim@www1.ietf.org  Sun May 16 22:25: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 WAA06644
	for <ietf-archive@odin.ietf.org>; Sun, 16 May 2004 22:25: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 1BPXnH-00024u-0t
	for ietf-archive@odin.ietf.org; Sun, 16 May 2004 22:23:55 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4H2NsKt007873
	for ietf-archive@odin.ietf.org; Sun, 16 May 2004 22:23:54 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPXff-0001Ak-6U; Sun, 16 May 2004 22:16:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPXbK-0000hA-Ro
	for ietf@optimus.ietf.org; Sun, 16 May 2004 22:11: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 WAA05554
	for <ietf@ietf.org>; Sun, 16 May 2004 22:11: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 1BPXbH-0000kW-HT
	for ietf@ietf.org; Sun, 16 May 2004 22:11:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPXaY-0000Rw-00
	for ietf@ietf.org; Sun, 16 May 2004 22:10:46 -0400
Received: from aharp.ittns.northwestern.edu ([129.105.153.69])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPXZj-0007b4-00
	for ietf@ietf.org; Sun, 16 May 2004 22:09:55 -0400
Received: from 24-136-20-138.c3-0.drb-ubr1.chi-drb.il.cable.rcn.com (aharp [127.0.0.1])
	by aharp.ittns.northwestern.edu (smtpd) with SMTP id 8B846136C82
	for <ietf@ietf.org>; Sun, 16 May 2004 21:09:16 -0500 (CDT)
Date: Sun, 16 May 2004 21:09:16 -0500
From: John Kristoff <jtk@northwestern.edu>
To: ietf@ietf.org
Subject: Re: 13 Root Server Limitation
Message-Id: <20040516210916.45eb186b.jtk@northwestern.edu>
In-Reply-To: <F05AE9AF-A78C-11D8-BE47-000A95E7E6B4@isc.org>
References: <Pine.LNX.4.44.0405161706080.678-100000@cirrus.av8.net>
	<F05AE9AF-A78C-11D8-BE47-000A95E7E6B4@isc.org>
X-Mailer: Sylpheed version 0.9.6claws (GTK+ 1.2.10; i686-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: 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 Sun, 16 May 2004 19:01:17 -0400
Joe Abley <jabley@isc.org> wrote:

> reconvergence events to non-anycast servers). In addition, before the 
> frequency of the route churn became sufficiently high to cause a 
> problem, it would be well and truly damped to death by anybody running 
> with common BGP damping parameters and the inability to talk to the few 
> root servers which have anycast instances would be the last of your 
> problems.

Not necessarily.  Common dampening parameters exclude some 'golden
networks' such as root name server networks from damping.  RIPE 229 and
Rob Thomas' Secure BGP template being perhaps the two most widely cited
guides that suggest such a practice.

John

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



From ietf-admin@ietf.org  Sun May 16 22:26:55 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA06793
	for <ietf-archive@ietf.org>; Sun, 16 May 2004 22:26:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPXqB-0005bE-RS
	for ietf-archive@ietf.org; Sun, 16 May 2004 22:26:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPXp0-0005Ca-00
	for ietf-archive@ietf.org; Sun, 16 May 2004 22:25:43 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPXnE-0004UQ-00
	for ietf-archive@ietf.org; Sun, 16 May 2004 22:23:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPXff-0001Ak-6U; Sun, 16 May 2004 22:16:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPXbK-0000hA-Ro
	for ietf@optimus.ietf.org; Sun, 16 May 2004 22:11: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 WAA05554
	for <ietf@ietf.org>; Sun, 16 May 2004 22:11: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 1BPXbH-0000kW-HT
	for ietf@ietf.org; Sun, 16 May 2004 22:11:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPXaY-0000Rw-00
	for ietf@ietf.org; Sun, 16 May 2004 22:10:46 -0400
Received: from aharp.ittns.northwestern.edu ([129.105.153.69])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPXZj-0007b4-00
	for ietf@ietf.org; Sun, 16 May 2004 22:09:55 -0400
Received: from 24-136-20-138.c3-0.drb-ubr1.chi-drb.il.cable.rcn.com (aharp [127.0.0.1])
	by aharp.ittns.northwestern.edu (smtpd) with SMTP id 8B846136C82
	for <ietf@ietf.org>; Sun, 16 May 2004 21:09:16 -0500 (CDT)
Date: Sun, 16 May 2004 21:09:16 -0500
From: John Kristoff <jtk@northwestern.edu>
To: ietf@ietf.org
Subject: Re: 13 Root Server Limitation
Message-Id: <20040516210916.45eb186b.jtk@northwestern.edu>
In-Reply-To: <F05AE9AF-A78C-11D8-BE47-000A95E7E6B4@isc.org>
References: <Pine.LNX.4.44.0405161706080.678-100000@cirrus.av8.net>
	<F05AE9AF-A78C-11D8-BE47-000A95E7E6B4@isc.org>
X-Mailer: Sylpheed version 0.9.6claws (GTK+ 1.2.10; i686-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
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 Sun, 16 May 2004 19:01:17 -0400
Joe Abley <jabley@isc.org> wrote:

> reconvergence events to non-anycast servers). In addition, before the 
> frequency of the route churn became sufficiently high to cause a 
> problem, it would be well and truly damped to death by anybody running 
> with common BGP damping parameters and the inability to talk to the few 
> root servers which have anycast instances would be the last of your 
> problems.

Not necessarily.  Common dampening parameters exclude some 'golden
networks' such as root name server networks from damping.  RIPE 229 and
Rob Thomas' Secure BGP template being perhaps the two most widely cited
guides that suggest such a practice.

John

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


From ietf-admin@ietf.org  Sun May 16 23:33: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 XAA10266
	for <ietf-archive@ietf.org>; Sun, 16 May 2004 23:33:29 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPYsc-0001ox-2A
	for ietf-archive@ietf.org; Sun, 16 May 2004 23:33:30 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPYrc-0001WV-00
	for ietf-archive@ietf.org; Sun, 16 May 2004 23:32:29 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPYqa-00016W-00
	for ietf-archive@ietf.org; Sun, 16 May 2004 23:31:24 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPYmN-0001aJ-K5; Sun, 16 May 2004 23:27:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPYky-0001Nm-4f
	for ietf@optimus.ietf.org; Sun, 16 May 2004 23:25:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA09904
	for <ietf@ietf.org>; Sun, 16 May 2004 23:25:33 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPYkw-0007DJ-4c
	for ietf@ietf.org; Sun, 16 May 2004 23:25:34 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPYkA-0006vY-00
	for ietf@ietf.org; Sun, 16 May 2004 23:24:47 -0400
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPYjf-0006dO-00
	for ietf@ietf.org; Sun, 16 May 2004 23:24:15 -0400
Received: from f01v-35-161.d0.club-internet.fr ([212.195.246.161] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.24)
	id 1BPYjS-0000MH-HB
	for ietf@ietf.org; Sun, 16 May 2004 20:24:03 -0700
Message-Id: <6.1.0.6.2.20040517040140.049c8590@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 6.1.0.6
Date: Mon, 17 May 2004 04:32:36 +0200
To: ietf@ietf.org
From: jfcm <info@utel.net>
Subject: Re: 13 Root Server Limitation
In-Reply-To: <Pine.LNX.4.44.0405161706080.678-100000@cirrus.av8.net>
References: <1084734804.40a7bd54f3d8f@www.bocek.ch>
 <Pine.LNX.4.44.0405161706080.678-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 - [47 12] / [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.2 required=5.0 tests=AWL,OFFERS_ETC autolearn=no 
	version=2.60

Dear Dean,
Anycast is of no interest here. The regional disemination of Root Servers 
requested by the WSIS should not to be read as a dissemination of the NTIA 
root file, but as a regional/national redundant generation of the root 
file, with mutual cross verification. Each national/regional identical root 
file can then have 13 servers and enhance the reliablity of the whole 
system, providing root system failure / hacking / attack fall-out / DoS 
containment.

Under the current deployement the DNS reference is not the network reality, 
nor the TLD Managers and Regiistrants decision. This is in blattant 
opposition with the "Internet core values" the IETF draft describes. The 
reference is a single master file on which ICANN/IANA acknowledges having 
no direct power. This is not something the Tunis 2005 meeting will accept 
when you consider the positions in Geneva 2003, so we are better off 
presenting an acceptable solution.

All the more than regional root file compilation addresses the IPv6 
concern: each root sever system may have only a few machines. If only 1/10h 
of the countries run a root compilation/server system, we could have from 
60 to 240 root servers. 20 root servers system would be a good back-up and 
for the users to chose from (RFC 883). The cost would ^probably be lower as 
the load on each machine will be much lower than today. Most of the 97.5% 
illigitimate load on the existing single system will probably only partly 
export to others. This means that we could decrease the load on an aveage 
root server machine down to 0.25% of the today load.

I know that you do not trust DNSSEC, but accessing randomly two or three 
different root server systems to verify a received info is another way 
towards security without taking risk of implementing a new system as 
DNSSEC. Even if this results in 3 times more traffic the load per machine 
would stay around less than 1% of the today load and the load on the 
network would probably be reduced with information travelling more locally.
jfc




At 00:22 17/05/04, Dean Anderson wrote:

>On Sun, 16 May 2004, Thomas Bocek wrote:
>
> > Hi
> >
> > I'm confused with the fact than the number of root servers is limited 
> to 13.
> > From RFC 3226:
> >
> > "The current number of root servers is limited to 13 as that is the maximum
> > number of name servers and their address records that fit in one 512-octet
> > answer for a SOA record.  If root servers start advertising A6 or KEY 
> records
> > then the answer for the root NS records will not fit in a single 
> 512-octet DNS
> > message, resulting in a large number of TCP query connections to the root
> > servers."
> >
> > A query send to one of the root servers with a long name (length 255)
> > shows that the answer is 511 bytes, returning one A and 13 NS records.
> > My question is: Why are all 13 NS returned?
>
>BIND adds an additional section that is optional. If this section weren't
>provided, then more root servers could be added.  It has been pointed out
>that this additional section information is ignored by most resolvers, and
>so it useless, except to persons manually interpreting the output of DNS
>query details. Some nameservers do not provide this additional data.  It
>would be operationally advantageous to use a nameserver software on the
>Root servers that did not provide the additional section.
>
>However, I think your interest is in regard to DNSSEC deployment. There
>are other problems with DNSSEC deployment, that limit or preclude
>widespread utility. I can't cover them all in one message.  But suffice it
>to say that DNSSEC isn't really secure, and that further, the root servers
>operators have widely adopted a dubious anycast replication model that
>won't work well with TCP and load-balancing BGP configurations that are
>gaining the interest of ISPs. Such load balancing configurations will send
>packets over different paths to the same IP address. This is significant
>because an Anycast server is two (or more) physical servers with the same
>IP address, but with different paths to each server to distribute load.
>Anycast will not cause problems with single packet UDP DNS queries, but
>will have problems with load balanced, TCP connections, especially where
>BGP load balancing configurations would be likely to send packets over
>different paths (and thus to different anycast servers) within a very
>short period of time, perhaps even sequential packets could sent over
>different paths.
>
>This dubious anycast configuration was discussed and "approved" by the
>NAMEDROPPERS Working Group in late November, 2002. Unfortunately for the
>anycast discussion, the list then became distracted by discussions
>concerning procedural irregularities involving the AXFR-clarify Draft,
>which would have altered the DNS AXFR and IXFR protocol to conform to the
>non-standard ISC/BIND implementation, despite a number of other
>implementations being able to follow the AXFR and IXFR specifications.
>This quickly developed into a discussion regarding abuse by the list
>administrator (Randy Bush) with respect to Dan Bernstein, and so the
>anycast discussion was abandoned.
>
>As the IETF list members are perhaps unaware, the charges of abuse by ISC
>and ISC-promoters is hardly new.  It is very hard to get real work done in
>the DNS working groups as a result.  ISC/BIND promoters have the working
>group tied up with gratuitous alterations to widely implemented protocols
>(eg AXFR-clarify) and irrational and misleading changes (eg IN-ADDR
>required) that have been demonstrated to either be security risks or
>dangerously misleading security placebo's, and have tried to suppress
>dissent on these issues by refusing to accept email, and in the past,
>silently discarding email, and otherwise harrassing people who offer
>reasoned and detailed objections.
>
>I and others would probably be more involved in issues like DNSSEC, and no
>doubt more progress would be made, if it weren't for the distractions of
>the mismanagement of the IETF and its working groups.
>
>Dean Anderson
>Av8 Internet, Inc
>
>
>_______________________________________________
>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  Sun May 16 23:38:41 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 XAA10493
	for <ietf-archive@odin.ietf.org>; Sun, 16 May 2004 23:38:41 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPYqa-00022O-Eb
	for ietf-archive@odin.ietf.org; Sun, 16 May 2004 23:31:24 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4H3VOmx007822
	for ietf-archive@odin.ietf.org; Sun, 16 May 2004 23:31:24 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPYmN-0001aJ-K5; Sun, 16 May 2004 23:27:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPYky-0001Nm-4f
	for ietf@optimus.ietf.org; Sun, 16 May 2004 23:25:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA09904
	for <ietf@ietf.org>; Sun, 16 May 2004 23:25:33 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPYkw-0007DJ-4c
	for ietf@ietf.org; Sun, 16 May 2004 23:25:34 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPYkA-0006vY-00
	for ietf@ietf.org; Sun, 16 May 2004 23:24:47 -0400
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPYjf-0006dO-00
	for ietf@ietf.org; Sun, 16 May 2004 23:24:15 -0400
Received: from f01v-35-161.d0.club-internet.fr ([212.195.246.161] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.24)
	id 1BPYjS-0000MH-HB
	for ietf@ietf.org; Sun, 16 May 2004 20:24:03 -0700
Message-Id: <6.1.0.6.2.20040517040140.049c8590@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 6.1.0.6
Date: Mon, 17 May 2004 04:32:36 +0200
To: ietf@ietf.org
From: jfcm <info@utel.net>
Subject: Re: 13 Root Server Limitation
In-Reply-To: <Pine.LNX.4.44.0405161706080.678-100000@cirrus.av8.net>
References: <1084734804.40a7bd54f3d8f@www.bocek.ch>
 <Pine.LNX.4.44.0405161706080.678-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 - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - utel.net
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,OFFERS_ETC 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 Dean,
Anycast is of no interest here. The regional disemination of Root Servers 
requested by the WSIS should not to be read as a dissemination of the NTIA 
root file, but as a regional/national redundant generation of the root 
file, with mutual cross verification. Each national/regional identical root 
file can then have 13 servers and enhance the reliablity of the whole 
system, providing root system failure / hacking / attack fall-out / DoS 
containment.

Under the current deployement the DNS reference is not the network reality, 
nor the TLD Managers and Regiistrants decision. This is in blattant 
opposition with the "Internet core values" the IETF draft describes. The 
reference is a single master file on which ICANN/IANA acknowledges having 
no direct power. This is not something the Tunis 2005 meeting will accept 
when you consider the positions in Geneva 2003, so we are better off 
presenting an acceptable solution.

All the more than regional root file compilation addresses the IPv6 
concern: each root sever system may have only a few machines. If only 1/10h 
of the countries run a root compilation/server system, we could have from 
60 to 240 root servers. 20 root servers system would be a good back-up and 
for the users to chose from (RFC 883). The cost would ^probably be lower as 
the load on each machine will be much lower than today. Most of the 97.5% 
illigitimate load on the existing single system will probably only partly 
export to others. This means that we could decrease the load on an aveage 
root server machine down to 0.25% of the today load.

I know that you do not trust DNSSEC, but accessing randomly two or three 
different root server systems to verify a received info is another way 
towards security without taking risk of implementing a new system as 
DNSSEC. Even if this results in 3 times more traffic the load per machine 
would stay around less than 1% of the today load and the load on the 
network would probably be reduced with information travelling more locally.
jfc




At 00:22 17/05/04, Dean Anderson wrote:

>On Sun, 16 May 2004, Thomas Bocek wrote:
>
> > Hi
> >
> > I'm confused with the fact than the number of root servers is limited 
> to 13.
> > From RFC 3226:
> >
> > "The current number of root servers is limited to 13 as that is the maximum
> > number of name servers and their address records that fit in one 512-octet
> > answer for a SOA record.  If root servers start advertising A6 or KEY 
> records
> > then the answer for the root NS records will not fit in a single 
> 512-octet DNS
> > message, resulting in a large number of TCP query connections to the root
> > servers."
> >
> > A query send to one of the root servers with a long name (length 255)
> > shows that the answer is 511 bytes, returning one A and 13 NS records.
> > My question is: Why are all 13 NS returned?
>
>BIND adds an additional section that is optional. If this section weren't
>provided, then more root servers could be added.  It has been pointed out
>that this additional section information is ignored by most resolvers, and
>so it useless, except to persons manually interpreting the output of DNS
>query details. Some nameservers do not provide this additional data.  It
>would be operationally advantageous to use a nameserver software on the
>Root servers that did not provide the additional section.
>
>However, I think your interest is in regard to DNSSEC deployment. There
>are other problems with DNSSEC deployment, that limit or preclude
>widespread utility. I can't cover them all in one message.  But suffice it
>to say that DNSSEC isn't really secure, and that further, the root servers
>operators have widely adopted a dubious anycast replication model that
>won't work well with TCP and load-balancing BGP configurations that are
>gaining the interest of ISPs. Such load balancing configurations will send
>packets over different paths to the same IP address. This is significant
>because an Anycast server is two (or more) physical servers with the same
>IP address, but with different paths to each server to distribute load.
>Anycast will not cause problems with single packet UDP DNS queries, but
>will have problems with load balanced, TCP connections, especially where
>BGP load balancing configurations would be likely to send packets over
>different paths (and thus to different anycast servers) within a very
>short period of time, perhaps even sequential packets could sent over
>different paths.
>
>This dubious anycast configuration was discussed and "approved" by the
>NAMEDROPPERS Working Group in late November, 2002. Unfortunately for the
>anycast discussion, the list then became distracted by discussions
>concerning procedural irregularities involving the AXFR-clarify Draft,
>which would have altered the DNS AXFR and IXFR protocol to conform to the
>non-standard ISC/BIND implementation, despite a number of other
>implementations being able to follow the AXFR and IXFR specifications.
>This quickly developed into a discussion regarding abuse by the list
>administrator (Randy Bush) with respect to Dan Bernstein, and so the
>anycast discussion was abandoned.
>
>As the IETF list members are perhaps unaware, the charges of abuse by ISC
>and ISC-promoters is hardly new.  It is very hard to get real work done in
>the DNS working groups as a result.  ISC/BIND promoters have the working
>group tied up with gratuitous alterations to widely implemented protocols
>(eg AXFR-clarify) and irrational and misleading changes (eg IN-ADDR
>required) that have been demonstrated to either be security risks or
>dangerously misleading security placebo's, and have tried to suppress
>dissent on these issues by refusing to accept email, and in the past,
>silently discarding email, and otherwise harrassing people who offer
>reasoned and detailed objections.
>
>I and others would probably be more involved in issues like DNSSEC, and no
>doubt more progress would be made, if it weren't for the distractions of
>the mismanagement of the IETF and its working groups.
>
>Dean Anderson
>Av8 Internet, Inc
>
>
>_______________________________________________
>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  Mon May 17 01:09: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 BAA14988
	for <ietf-archive@ietf.org>; Mon, 17 May 2004 01:09: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 1BPaNg-0007gh-79
	for ietf-archive@ietf.org; Mon, 17 May 2004 01:09:40 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPaMi-0007PM-00
	for ietf-archive@ietf.org; Mon, 17 May 2004 01:08:41 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPaMR-00077r-00
	for ietf-archive@ietf.org; Mon, 17 May 2004 01:08:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPaDN-0004xV-I0; Mon, 17 May 2004 00:59:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPaA9-0004dM-0v
	for ietf@optimus.ietf.org; Mon, 17 May 2004 00:55: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 AAA14485
	for <ietf@ietf.org>; Mon, 17 May 2004 00:55:36 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPaA6-0003Yp-2S
	for ietf@ietf.org; Mon, 17 May 2004 00:55:38 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPa9B-0003HR-00
	for ietf@ietf.org; Mon, 17 May 2004 00:54:41 -0400
Received: from felix.automagic.org ([204.152.186.101])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPa8K-000307-00
	for ietf@ietf.org; Mon, 17 May 2004 00:53:48 -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 1BPa8K-000Nvm-47; Mon, 17 May 2004 04:53:48 +0000
In-Reply-To: <20040516210916.45eb186b.jtk@northwestern.edu>
References: <Pine.LNX.4.44.0405161706080.678-100000@cirrus.av8.net> <F05AE9AF-A78C-11D8-BE47-000A95E7E6B4@isc.org> <20040516210916.45eb186b.jtk@northwestern.edu>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <3E7F436A-A7BE-11D8-BE47-000A95E7E6B4@isc.org>
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
From: Joe Abley <jabley@isc.org>
Subject: Re: 13 Root Server Limitation
Date: Mon, 17 May 2004 00:54:14 -0400
To: John Kristoff <jtk@northwestern.edu>
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 16 May 2004, at 22:09, John Kristoff wrote:

> On Sun, 16 May 2004 19:01:17 -0400
> Joe Abley <jabley@isc.org> wrote:
>
>> reconvergence events to non-anycast servers). In addition, before the
>> frequency of the route churn became sufficiently high to cause a
>> problem, it would be well and truly damped to death by anybody running
>> with common BGP damping parameters and the inability to talk to the 
>> few
>> root servers which have anycast instances would be the last of your
>> problems.
>
> Not necessarily.  Common dampening parameters exclude some 'golden
> networks' such as root name server networks from damping.  RIPE 229 and
> Rob Thomas' Secure BGP template being perhaps the two most widely cited
> guides that suggest such a practice.

The point I was trying to make was not that the path to the anycast 
roots would be dampened, but that topology oscillations that caused 
path changes with that frequency might well cause everything else to be 
dampened, or cause the prefixes announced from the supposedly-affected 
AS to become dampened in other ASes.

This was intended to be degenerate-case handwaving.


Joe


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


From exim@www1.ietf.org  Mon May 17 01:12:58 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 BAA15056
	for <ietf-archive@odin.ietf.org>; Mon, 17 May 2004 01:12:58 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPaMT-0006GU-J8
	for ietf-archive@odin.ietf.org; Mon, 17 May 2004 01:08:25 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4H58Phl024006
	for ietf-archive@odin.ietf.org; Mon, 17 May 2004 01:08:25 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPaDN-0004xV-I0; Mon, 17 May 2004 00:59:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPaA9-0004dM-0v
	for ietf@optimus.ietf.org; Mon, 17 May 2004 00:55: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 AAA14485
	for <ietf@ietf.org>; Mon, 17 May 2004 00:55:36 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPaA6-0003Yp-2S
	for ietf@ietf.org; Mon, 17 May 2004 00:55:38 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPa9B-0003HR-00
	for ietf@ietf.org; Mon, 17 May 2004 00:54:41 -0400
Received: from felix.automagic.org ([204.152.186.101])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPa8K-000307-00
	for ietf@ietf.org; Mon, 17 May 2004 00:53:48 -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 1BPa8K-000Nvm-47; Mon, 17 May 2004 04:53:48 +0000
In-Reply-To: <20040516210916.45eb186b.jtk@northwestern.edu>
References: <Pine.LNX.4.44.0405161706080.678-100000@cirrus.av8.net> <F05AE9AF-A78C-11D8-BE47-000A95E7E6B4@isc.org> <20040516210916.45eb186b.jtk@northwestern.edu>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <3E7F436A-A7BE-11D8-BE47-000A95E7E6B4@isc.org>
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
From: Joe Abley <jabley@isc.org>
Subject: Re: 13 Root Server Limitation
Date: Mon, 17 May 2004 00:54:14 -0400
To: John Kristoff <jtk@northwestern.edu>
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 16 May 2004, at 22:09, John Kristoff wrote:

> On Sun, 16 May 2004 19:01:17 -0400
> Joe Abley <jabley@isc.org> wrote:
>
>> reconvergence events to non-anycast servers). In addition, before the
>> frequency of the route churn became sufficiently high to cause a
>> problem, it would be well and truly damped to death by anybody running
>> with common BGP damping parameters and the inability to talk to the 
>> few
>> root servers which have anycast instances would be the last of your
>> problems.
>
> Not necessarily.  Common dampening parameters exclude some 'golden
> networks' such as root name server networks from damping.  RIPE 229 and
> Rob Thomas' Secure BGP template being perhaps the two most widely cited
> guides that suggest such a practice.

The point I was trying to make was not that the path to the anycast 
roots would be dampened, but that topology oscillations that caused 
path changes with that frequency might well cause everything else to be 
dampened, or cause the prefixes announced from the supposedly-affected 
AS to become dampened in other ASes.

This was intended to be degenerate-case handwaving.


Joe


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



From ietf-admin@ietf.org  Mon May 17 04:35:57 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07260
	for <ietf-archive@ietf.org>; Mon, 17 May 2004 04:35: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 1BPdbI-0000oL-NF
	for ietf-archive@ietf.org; Mon, 17 May 2004 04:35:56 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPdaR-0000Ub-00
	for ietf-archive@ietf.org; Mon, 17 May 2004 04:35:03 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPdZa-0000Ap-00
	for ietf-archive@ietf.org; Mon, 17 May 2004 04:34:10 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPdJ3-0004jU-Fr; Mon, 17 May 2004 04: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 1BPdF6-0004G3-UC
	for ietf@optimus.ietf.org; Mon, 17 May 2004 04:13:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06443
	for <ietf@ietf.org>; Mon, 17 May 2004 04:12:58 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPdF4-0001fF-1y
	for ietf@ietf.org; Mon, 17 May 2004 04:12:58 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPdEI-0001Lt-00
	for ietf@ietf.org; Mon, 17 May 2004 04:12:11 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPdDc-00011B-00
	for ietf@ietf.org; Mon, 17 May 2004 04:11:28 -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 i4H8B31C041614;
	Mon, 17 May 2004 10:11:03 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <F05AE9AF-A78C-11D8-BE47-000A95E7E6B4@isc.org>
References: <Pine.LNX.4.44.0405161706080.678-100000@cirrus.av8.net> <F05AE9AF-A78C-11D8-BE47-000A95E7E6B4@isc.org>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <C4F3D472-A7D9-11D8-AC18-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: "'Internet Engineering Task Force'" <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: 13 Root Server Limitation
Date: Mon, 17 May 2004 10:11:16 +0200
To: Joe Abley <jabley@isc.org>
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 17-mei-04, at 1:01, Joe Abley wrote:

> If you have an example of someone enabling multi-path BGP hacks in 
> order to allow selection of more than one path, and specifically one 
> who has ever selected two or more paths to different nodes of F (that 
> is, paths to 192.5.5.0/24) I would be very interested to hear about 
> it.

> Feedback and measurement data we have seen has not yet revealed an 
> occurrence of this, and conversations so far with operators does not 
> suggest there is much risk that we will. Your data will be interesting 
> to hear, however, if you can pass it on.

This is pretty much impossible with Cisco equipment, as in order to 
load balance, the different routes must all be learned from the same 
neighboring AS. (So if everyone used Cisco equipment the AS paths would 
have to be identical.) Additionally, the default way to do this is send 
all packets towards the same IP address over the same link. Other 
vendors also bend over backwards to avoid packets from the same session 
being distributed over more than one link. (The idea is that reordering 
packets is bad. However, sometimes the measures to avoid it are worse.)

But as long as we're dissing anycast root DNS servers: how many of the 
root servers are being anycast now or in the future, and how many 
won't? As we've seen a few times with .org, and thought we saw with 
.org many more times, over-enthusiastic anycasting isn't without its 
dangers.


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


From ietf-admin@ietf.org  Mon May 17 11:38: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 LAA28839
	for <ietf-archive@ietf.org>; Mon, 17 May 2004 11:38: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 1BPkBs-0003xc-Si
	for ietf-archive@ietf.org; Mon, 17 May 2004 11:38:08 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPkAr-0003b1-00
	for ietf-archive@ietf.org; Mon, 17 May 2004 11:37:05 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPk9m-00037r-00
	for ietf-archive@ietf.org; Mon, 17 May 2004 11: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 1BPjzO-0003LF-WD; Mon, 17 May 2004 11:25:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPjyf-0003Cj-6u
	for ietf@optimus.ietf.org; Mon, 17 May 2004 11:24: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 LAA28218
	for <ietf@ietf.org>; Mon, 17 May 2004 11:24: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 1BPjyd-0006zQ-Vw
	for ietf@ietf.org; Mon, 17 May 2004 11:24:28 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPjxY-0006eM-00
	for ietf@ietf.org; Mon, 17 May 2004 11:23:21 -0400
Received: from felix.automagic.org ([204.152.186.101])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPjwZ-0006JK-00
	for ietf@ietf.org; Mon, 17 May 2004 11:22:20 -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 1BPjwY-000PGa-Jj; Mon, 17 May 2004 15:22:18 +0000
In-Reply-To: <C4F3D472-A7D9-11D8-AC18-000A95CD987A@muada.com>
References: <Pine.LNX.4.44.0405161706080.678-100000@cirrus.av8.net> <F05AE9AF-A78C-11D8-BE47-000A95E7E6B4@isc.org> <C4F3D472-A7D9-11D8-AC18-000A95CD987A@muada.com>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <0AC20BBE-A816-11D8-BE47-000A95E7E6B4@isc.org>
Content-Transfer-Encoding: 7bit
Cc: "'Internet Engineering Task Force'" <ietf@ietf.org>
From: Joe Abley <jabley@isc.org>
Subject: Re: 13 Root Server Limitation
Date: Mon, 17 May 2004 11:22:43 -0400
To: Iljitsch van Beijnum <iljitsch@muada.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 17 May 2004, at 04:11, Iljitsch van Beijnum wrote:

> This is pretty much impossible with Cisco equipment, as in order to 
> load balance, the different routes must all be learned from the same 
> neighboring AS. (So if everyone used Cisco equipment the AS paths 
> would have to be identical.)

It may be worth noting here that with the style of Internet-scope 
anycast deployment we're doing with F (ISC-TN-2003-1) each anycast node 
operates as a globally-unique AS, so even if a single AS was peering 
with F-root nodes in different places it ought not to be possible for 
traffic from a single TCP transaction to be split between nodes.

> But as long as we're dissing anycast root DNS servers: how many of the 
> root servers are being anycast now or in the future, and how many 
> won't? As we've seen a few times with .org, and thought we saw with 
> .org many more times, over-enthusiastic anycasting isn't without its 
> dangers.

It seems to me that prudence and diversity are best served through a 
mixture of anycast and unicast nameservers in an NS set, the latter to 
provide path diversity and local stability to topologically distant 
regions and the former to accommodate any practical issues that might 
arise with the latter.


Joe


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


From exim@www1.ietf.org  Mon May 17 11:39:21 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>; Mon, 17 May 2004 11:39:21 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPk9m-0004bl-Jl
	for ietf-archive@odin.ietf.org; Mon, 17 May 2004 11:35:59 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4HFZw6G017569
	for ietf-archive@odin.ietf.org; Mon, 17 May 2004 11: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 1BPjzO-0003LF-WD; Mon, 17 May 2004 11:25:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPjyf-0003Cj-6u
	for ietf@optimus.ietf.org; Mon, 17 May 2004 11:24: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 LAA28218
	for <ietf@ietf.org>; Mon, 17 May 2004 11:24: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 1BPjyd-0006zQ-Vw
	for ietf@ietf.org; Mon, 17 May 2004 11:24:28 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPjxY-0006eM-00
	for ietf@ietf.org; Mon, 17 May 2004 11:23:21 -0400
Received: from felix.automagic.org ([204.152.186.101])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPjwZ-0006JK-00
	for ietf@ietf.org; Mon, 17 May 2004 11:22:20 -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 1BPjwY-000PGa-Jj; Mon, 17 May 2004 15:22:18 +0000
In-Reply-To: <C4F3D472-A7D9-11D8-AC18-000A95CD987A@muada.com>
References: <Pine.LNX.4.44.0405161706080.678-100000@cirrus.av8.net> <F05AE9AF-A78C-11D8-BE47-000A95E7E6B4@isc.org> <C4F3D472-A7D9-11D8-AC18-000A95CD987A@muada.com>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <0AC20BBE-A816-11D8-BE47-000A95E7E6B4@isc.org>
Content-Transfer-Encoding: 7bit
Cc: "'Internet Engineering Task Force'" <ietf@ietf.org>
From: Joe Abley <jabley@isc.org>
Subject: Re: 13 Root Server Limitation
Date: Mon, 17 May 2004 11:22:43 -0400
To: Iljitsch van Beijnum <iljitsch@muada.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 17 May 2004, at 04:11, Iljitsch van Beijnum wrote:

> This is pretty much impossible with Cisco equipment, as in order to 
> load balance, the different routes must all be learned from the same 
> neighboring AS. (So if everyone used Cisco equipment the AS paths 
> would have to be identical.)

It may be worth noting here that with the style of Internet-scope 
anycast deployment we're doing with F (ISC-TN-2003-1) each anycast node 
operates as a globally-unique AS, so even if a single AS was peering 
with F-root nodes in different places it ought not to be possible for 
traffic from a single TCP transaction to be split between nodes.

> But as long as we're dissing anycast root DNS servers: how many of the 
> root servers are being anycast now or in the future, and how many 
> won't? As we've seen a few times with .org, and thought we saw with 
> .org many more times, over-enthusiastic anycasting isn't without its 
> dangers.

It seems to me that prudence and diversity are best served through a 
mixture of anycast and unicast nameservers in an NS set, the latter to 
provide path diversity and local stability to topologically distant 
regions and the former to accommodate any practical issues that might 
arise with the latter.


Joe


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



From ietf-admin@ietf.org  Mon May 17 12:09: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 MAA01491
	for <ietf-archive@ietf.org>; Mon, 17 May 2004 12:09: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 1BPkfu-0006sb-66
	for ietf-archive@ietf.org; Mon, 17 May 2004 12:09:10 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPkez-0006YO-00
	for ietf-archive@ietf.org; Mon, 17 May 2004 12:08:13 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPkeV-0006EV-00
	for ietf-archive@ietf.org; Mon, 17 May 2004 12:07:43 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPkTg-0007rW-86; Mon, 17 May 2004 11:56:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPkKd-000693-6B
	for ietf@optimus.ietf.org; Mon, 17 May 2004 11:47: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 LAA29884
	for <ietf@ietf.org>; Mon, 17 May 2004 11:47: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 1BPkKc-00070q-0U
	for ietf@ietf.org; Mon, 17 May 2004 11:47:10 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPkJ6-0006Me-00
	for ietf@ietf.org; Mon, 17 May 2004 11:45:36 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPkH7-0005it-00
	for ietf@ietf.org; Mon, 17 May 2004 11:43:33 -0400
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) id i4HFflE17760;
	Mon, 17 May 2004 08:41:47 -0700 (PDT)
From: Bill Manning <bmanning@ISI.EDU>
Message-Id: <200405171541.i4HFflE17760@boreas.isi.edu>
Subject: Re: Root Anycast
To: iljitsch@muada.com (Iljitsch van Beijnum)
Date: Mon, 17 May 2004 08:41:46 -0700 (PDT)
Cc: ietf@ietf.org ('Internet Engineering Task Force'),
        jabley@isc.org (Joe Abley)
In-Reply-To: <C4F3D472-A7D9-11D8-AC18-000A95CD987A@muada.com> from "Iljitsch van Beijnum" at May 17, 2004 10:11:16 AM
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-ISI-4-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

% But as long as we're dissing anycast root DNS servers: how many of the 
% root servers are being anycast now or in the future, and how many 
% won't? 

	http://www.rssac.org/ 

	check the 17th & 18th meeting minutes.


--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  Mon May 17 12:25: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 MAA02848
	for <ietf-archive@odin.ietf.org>; Mon, 17 May 2004 12:25: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 1BPkeX-0000y5-UN
	for ietf-archive@odin.ietf.org; Mon, 17 May 2004 12:07:48 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4HG7ihE003454
	for ietf-archive@odin.ietf.org; Mon, 17 May 2004 12:07:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPkTg-0007rW-86; Mon, 17 May 2004 11:56:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPkKd-000693-6B
	for ietf@optimus.ietf.org; Mon, 17 May 2004 11:47: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 LAA29884
	for <ietf@ietf.org>; Mon, 17 May 2004 11:47: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 1BPkKc-00070q-0U
	for ietf@ietf.org; Mon, 17 May 2004 11:47:10 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPkJ6-0006Me-00
	for ietf@ietf.org; Mon, 17 May 2004 11:45:36 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPkH7-0005it-00
	for ietf@ietf.org; Mon, 17 May 2004 11:43:33 -0400
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) id i4HFflE17760;
	Mon, 17 May 2004 08:41:47 -0700 (PDT)
From: Bill Manning <bmanning@ISI.EDU>
Message-Id: <200405171541.i4HFflE17760@boreas.isi.edu>
Subject: Re: Root Anycast
To: iljitsch@muada.com (Iljitsch van Beijnum)
Date: Mon, 17 May 2004 08:41:46 -0700 (PDT)
Cc: ietf@ietf.org ('Internet Engineering Task Force'),
        jabley@isc.org (Joe Abley)
In-Reply-To: <C4F3D472-A7D9-11D8-AC18-000A95CD987A@muada.com> from "Iljitsch van Beijnum" at May 17, 2004 10:11:16 AM
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-ISI-4-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

% But as long as we're dissing anycast root DNS servers: how many of the 
% root servers are being anycast now or in the future, and how many 
% won't? 

	http://www.rssac.org/ 

	check the 17th & 18th meeting minutes.


--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  Mon May 17 14:08: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 OAA09265
	for <ietf-archive@ietf.org>; Mon, 17 May 2004 14:08: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 1BPmXW-0001wI-0L
	for ietf-archive@ietf.org; Mon, 17 May 2004 14:08:38 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPmWF-0001TQ-00
	for ietf-archive@ietf.org; Mon, 17 May 2004 14:07:20 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPmVF-00016o-00
	for ietf-archive@ietf.org; Mon, 17 May 2004 14:06:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPmCf-0001jy-2Z; Mon, 17 May 2004 13: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 1BPm53-0000fT-6p
	for ietf@optimus.ietf.org; Mon, 17 May 2004 13:39:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07618
	for <ietf@ietf.org>; Mon, 17 May 2004 13:39: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 1BPm4y-0007Ri-2x
	for ietf@ietf.org; Mon, 17 May 2004 13:39:08 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPm3r-0006mW-00
	for ietf@ietf.org; Mon, 17 May 2004 13:38:00 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPm2o-0006ON-00
	for ietf@ietf.org; Mon, 17 May 2004 13:36:54 -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 i4HHaLX2023423
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 17 May 2004 13:36:21 -0400
Date: Mon, 17 May 2004 13:36:21 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Joe Abley <jabley@isc.org>
cc: ietf@ietf.org, Thomas Bocek <draft@icu.unizh.ch>
Subject: Re: 13 Root Server Limitation
In-Reply-To: <F05AE9AF-A78C-11D8-BE47-000A95E7E6B4@isc.org>
Message-ID: <Pine.LNX.4.44.0405171313140.22879-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 Sun, 16 May 2004, Joe Abley wrote:
> On 16 May 2004, at 18:22, Dean Anderson wrote:
> 
> > ... and that further, the root servers
> > operators have widely adopted a dubious anycast replication model that
> > won't work well with TCP and load-balancing BGP configurations that are
> > gaining the interest of ISPs. Such load balancing configurations will 
> > send
> > packets over different paths to the same IP address. This is 
> > significant
> > because an Anycast server is two (or more) physical servers with the 
> > same
> > IP address, but with different paths to each server to distribute load.
> 
> This is not the case with F (I can't speak for other operators 
> deploying Internet-scope anycast services). The different paths are 
> made available in order to provide redundancy and diversity, and 
> absolutely not to share load.

I don't have the list of roots using anycast handy (I think might have
been published on Namedroppers though), and I don't remember if F was 
amoung them.

> If you have an example of someone enabling multi-path BGP hacks in 
> order to allow selection of more than one path, and specifically one 
> who has ever selected two or more paths to different nodes of F (that 
> is, paths to 192.5.5.0/24) I would be very interested to hear about it.

It is conceptually very simple:  Setup 2 anycast servers (S1 and S2) on
several paths (AS-A and AS-Y, different AS numbers)  Have an ISP connect
to both of those paths, and then have that ISP do fine grained load
balancing to prefixes available over those paths. Packets will go to each
anycast server.  This will not cause a problem with UDP, since the entire
connection transaction is in one packet. But TCP will have a minumim of 3
packets.  2 packets will go to server S1, and one packet will go to server
S2.  Neither S1 nor S2 will have a complete TCP connection, and so both
will fail.

> Feedback and measurement data we have seen has not yet revealed an 
> occurrence of this, and conversations so far with operators does not 
> suggest there is much risk that we will. Your data will be interesting 
> to hear, however, if you can pass it on.

This is because most (vast bulk?) traffic to the root's is UDP. It may
also be the case that no ISPs are doing fine-grained load balancing to the
specific paths which happen to go to the root servers using anycast.  
However, this configuration is just a matter of chance.  One can't make
operational plans based on essentially false assumptions that a) no one
does TCP DNS queries, and b)  no one does fine grained load balancing, or
c) no one does fined grained load balancing on the paths that lead to
anycast root servers.

Anycast only works on UDP, and only one single packet transactions with no
other state.  If your application cannot meet those requirements, it is
unsuitable for anycast.  UDP DNS meets those requirements. TCP DNS does
not.

> > Anycast will not cause problems with single packet UDP DNS queries,
> > but will have problems with load balanced, TCP connections, especially
> > where BGP load balancing configurations would be likely to send
> > packets over different paths (and thus to different anycast servers)
> > within a very short period of time, perhaps even sequential packets
> > could sent over different paths.
> 
> There is a risk that during a routing transition, when one path to 
> 192.5.5.0/24 is promoted over another due to a link failure or some 
> other policy or topology change, a TCP transaction to an anycast node 
> will fail. This is documented in both ISC technical notes written to 
> describe what we are doing with F.

This is a course-grained route switch. There is no way to avoid such
connection failure, because one server containing the TCP state, failed.  
As has been pointed out, such route changes are infrequent.  Route churn
is a minor problem, and unrelated to fine-grained load balancing, in which
packets are simultaneously sent over two different paths.


		--Dean



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


From exim@www1.ietf.org  Mon May 17 14:11:07 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09704
	for <ietf-archive@odin.ietf.org>; Mon, 17 May 2004 14:11: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 1BPmVH-0004IX-Bp
	for ietf-archive@odin.ietf.org; Mon, 17 May 2004 14:06:22 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4HI6JEn016522
	for ietf-archive@odin.ietf.org; Mon, 17 May 2004 14:06:19 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPmCf-0001jy-2Z; Mon, 17 May 2004 13: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 1BPm53-0000fT-6p
	for ietf@optimus.ietf.org; Mon, 17 May 2004 13:39:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07618
	for <ietf@ietf.org>; Mon, 17 May 2004 13:39: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 1BPm4y-0007Ri-2x
	for ietf@ietf.org; Mon, 17 May 2004 13:39:08 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPm3r-0006mW-00
	for ietf@ietf.org; Mon, 17 May 2004 13:38:00 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPm2o-0006ON-00
	for ietf@ietf.org; Mon, 17 May 2004 13:36:54 -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 i4HHaLX2023423
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 17 May 2004 13:36:21 -0400
Date: Mon, 17 May 2004 13:36:21 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Joe Abley <jabley@isc.org>
cc: ietf@ietf.org, Thomas Bocek <draft@icu.unizh.ch>
Subject: Re: 13 Root Server Limitation
In-Reply-To: <F05AE9AF-A78C-11D8-BE47-000A95E7E6B4@isc.org>
Message-ID: <Pine.LNX.4.44.0405171313140.22879-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 Sun, 16 May 2004, Joe Abley wrote:
> On 16 May 2004, at 18:22, Dean Anderson wrote:
> 
> > ... and that further, the root servers
> > operators have widely adopted a dubious anycast replication model that
> > won't work well with TCP and load-balancing BGP configurations that are
> > gaining the interest of ISPs. Such load balancing configurations will 
> > send
> > packets over different paths to the same IP address. This is 
> > significant
> > because an Anycast server is two (or more) physical servers with the 
> > same
> > IP address, but with different paths to each server to distribute load.
> 
> This is not the case with F (I can't speak for other operators 
> deploying Internet-scope anycast services). The different paths are 
> made available in order to provide redundancy and diversity, and 
> absolutely not to share load.

I don't have the list of roots using anycast handy (I think might have
been published on Namedroppers though), and I don't remember if F was 
amoung them.

> If you have an example of someone enabling multi-path BGP hacks in 
> order to allow selection of more than one path, and specifically one 
> who has ever selected two or more paths to different nodes of F (that 
> is, paths to 192.5.5.0/24) I would be very interested to hear about it.

It is conceptually very simple:  Setup 2 anycast servers (S1 and S2) on
several paths (AS-A and AS-Y, different AS numbers)  Have an ISP connect
to both of those paths, and then have that ISP do fine grained load
balancing to prefixes available over those paths. Packets will go to each
anycast server.  This will not cause a problem with UDP, since the entire
connection transaction is in one packet. But TCP will have a minumim of 3
packets.  2 packets will go to server S1, and one packet will go to server
S2.  Neither S1 nor S2 will have a complete TCP connection, and so both
will fail.

> Feedback and measurement data we have seen has not yet revealed an 
> occurrence of this, and conversations so far with operators does not 
> suggest there is much risk that we will. Your data will be interesting 
> to hear, however, if you can pass it on.

This is because most (vast bulk?) traffic to the root's is UDP. It may
also be the case that no ISPs are doing fine-grained load balancing to the
specific paths which happen to go to the root servers using anycast.  
However, this configuration is just a matter of chance.  One can't make
operational plans based on essentially false assumptions that a) no one
does TCP DNS queries, and b)  no one does fine grained load balancing, or
c) no one does fined grained load balancing on the paths that lead to
anycast root servers.

Anycast only works on UDP, and only one single packet transactions with no
other state.  If your application cannot meet those requirements, it is
unsuitable for anycast.  UDP DNS meets those requirements. TCP DNS does
not.

> > Anycast will not cause problems with single packet UDP DNS queries,
> > but will have problems with load balanced, TCP connections, especially
> > where BGP load balancing configurations would be likely to send
> > packets over different paths (and thus to different anycast servers)
> > within a very short period of time, perhaps even sequential packets
> > could sent over different paths.
> 
> There is a risk that during a routing transition, when one path to 
> 192.5.5.0/24 is promoted over another due to a link failure or some 
> other policy or topology change, a TCP transaction to an anycast node 
> will fail. This is documented in both ISC technical notes written to 
> describe what we are doing with F.

This is a course-grained route switch. There is no way to avoid such
connection failure, because one server containing the TCP state, failed.  
As has been pointed out, such route changes are infrequent.  Route churn
is a minor problem, and unrelated to fine-grained load balancing, in which
packets are simultaneously sent over two different paths.


		--Dean



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



From ietf-admin@ietf.org  Mon May 17 15: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 PAA15197
	for <ietf-archive@ietf.org>; Mon, 17 May 2004 15: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 1BPnQW-0007aB-1Z
	for ietf-archive@ietf.org; Mon, 17 May 2004 15:05:28 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPnPU-0007Ec-00
	for ietf-archive@ietf.org; Mon, 17 May 2004 15:04:24 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPnOe-0006te-00
	for ietf-archive@ietf.org; Mon, 17 May 2004 15:03:32 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPnDb-0005Ik-6K; Mon, 17 May 2004 14:52:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPn7n-0003yn-FC
	for ietf@optimus.ietf.org; Mon, 17 May 2004 14:46:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13756
	for <ietf@ietf.org>; Mon, 17 May 2004 14:46: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 1BPn7k-0000V6-FU
	for ietf@ietf.org; Mon, 17 May 2004 14:46:04 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPn6b-00000i-00
	for ietf@ietf.org; Mon, 17 May 2004 14:44:54 -0400
Received: from m018e36d0.tmodns.net ([208.54.142.1] helo=proradius03)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPn5P-00074P-00
	for ietf@ietf.org; Mon, 17 May 2004 14:43:39 -0400
Received: from laptop2.kurtis.pp.se ([10.242.8.212])
	by proradius03 (8.11.6+Sun/8.11.6) with ESMTP id i4HIReo27317
	for <ietf@ietf.org>; Mon, 17 May 2004 11:27:40 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by laptop2.kurtis.pp.se (Postfix) with ESMTP
	id 1C911402165; Mon, 17 May 2004 20:10:01 +0200 (CEST)
In-Reply-To: <Pine.LNX.4.44.0405111748480.19722-100000@cirrus.av8.net>
References: <Pine.LNX.4.44.0405111748480.19722-100000@cirrus.av8.net>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=fixed
Message-Id: <C6111F54-A81D-11D8-8726-000A95928574@kurtis.pp.se>
Content-Transfer-Encoding: 7bit
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
From: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
Subject: Re: [dnsop] Re: Complaint on abuse of DNSOP lists
Date: Mon, 17 May 2004 18:18:03 +0200
To: Dean Anderson <dean@av8.com>
X-Pgp-Rfc2646-Fix: 1
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.4 required=5.0 tests=AWL,UPPERCASE_25_50 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

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


On 2004-05-11, at 23.55, Dean Anderson wrote:

> On Tue, 11 May 2004, Joe Abley wrote:
>
>> For the benefit of less-operational people here who don't see humour
>> in
>> this, 198.32.176.0/24 is the PAIX IPv4 peering fabric in the Bay Area.
>
> This block is assigned to EP.NET.

I work for an IXP. Are you trying to say that that means that all
traffic that passes an IXP means that I am the upstream for that
traffic? It doesn't work this way.

- - kurtis -

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3

iQA/AwUBQKjlvqarNKXTPFCVEQIevwCfQAG+nR7rSNpkmSGvSmtTsjTEKtMAn03c
PTbWNR/gB8VkAwl/P+94/WQZ
=0ViT
-----END PGP SIGNATURE-----


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


From ietf-admin@ietf.org  Mon May 17 15:10: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 PAA15827
	for <ietf-archive@ietf.org>; Mon, 17 May 2004 15:10: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 1BPnV9-0001Y7-9G
	for ietf-archive@ietf.org; Mon, 17 May 2004 15:10:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPnU9-0001BU-00
	for ietf-archive@ietf.org; Mon, 17 May 2004 15:09:13 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPnT8-0000n9-00
	for ietf-archive@ietf.org; Mon, 17 May 2004 15:08:10 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPnDe-0005JA-F6; Mon, 17 May 2004 14:52:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPn7p-0003yx-Vo
	for ietf@optimus.ietf.org; Mon, 17 May 2004 14:46: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 OAA13766
	for <ietf@ietf.org>; Mon, 17 May 2004 14:46: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 1BPn7n-0000XQ-2l
	for ietf@ietf.org; Mon, 17 May 2004 14:46:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPn6e-00001C-00
	for ietf@ietf.org; Mon, 17 May 2004 14:44:57 -0400
Received: from m018e36d0.tmodns.net ([208.54.142.1] helo=proradius03)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPn5R-00075j-00
	for ietf@ietf.org; Mon, 17 May 2004 14:43:41 -0400
Received: from laptop2.kurtis.pp.se ([10.242.8.212])
	by proradius03 (8.11.6+Sun/8.11.6) with ESMTP id i4HIRgo27367
	for <ietf@ietf.org>; Mon, 17 May 2004 11:27:43 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by laptop2.kurtis.pp.se (Postfix) with ESMTP
	id 8FD7240216E; Mon, 17 May 2004 20:10:01 +0200 (CEST)
In-Reply-To: <Pine.LNX.4.44.0405131233520.5972-100000@cirrus.av8.net>
References: <Pine.LNX.4.44.0405131233520.5972-100000@cirrus.av8.net>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=fixed
Message-Id: <A8FADF4C-A7FB-11D8-8726-000A95928574@kurtis.pp.se>
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, "Kevin C. Almeroth" <almeroth@cs.ucsb.edu>
From: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
Subject: Re: Complaint on abuse of DNSOP lists
Date: Mon, 17 May 2004 14:13:52 +0200
To: Dean Anderson <dean@av8.com>
X-Pgp-Rfc2646-Fix: 1
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.7 required=5.0 tests=AWL,DATE_IN_PAST_03_06 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

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



I thought I needed to pay to get to most ITU standards. But I might be 
wrong.

I can't see how personal closed discussions relate to open 
standardization. Are you saying that you want to have an open process, 
as long as you have a direct channel to the chairs in that process? I 
am not following you. I though the standardization for the IETF was 
done in public, not in private emails with the chairs. And that that 
was what made the IETF special.

- - kurtis -

On 2004-05-13, at 18.34, Dean Anderson wrote:

> Of course, this is exactly why the third world doesn't want to have the
> IETF in charge in its present form.
>
> Professional and standards organizations aren't private clubs.
>
> 		--Dean
>
> On Wed, 12 May 2004, Kevin C. Almeroth wrote:
>
>> This pretty much does it for me:  anyone who says they are entitled
>> to participate in the IETF immediately goes into my spam bucket.
>>
>> As others have pointed out, you've done yourself more harm than good.
>>
>>>> I'm entitled to particpate, and I'm entitled to send email to the WG
>>>> chairs as a participant.
>>>>
>>>> One thing I've noticed is that of none of the people criticizing me 
>>>> has
>>>> thought to address the fact that OUR ADDRESS SPACE IS NOT HIJACKED, 
>>>> and
>>>> that these people associated with the IETF: Paul Vixie, Joe Abley, 
>>>> Bill
>>>> Manning, and Rob Austein as WG Co-chair in his role for IETF 
>>>> business, all
>>>> claim that it is.  But anyone can plainly see they are lying.
>>>>
>>>> Dean Anderson
>>>> Av8 Internet, Inc
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3

iQA/AwUBQKisgqarNKXTPFCVEQLJrQCgoc/TPKrlLx7QUTXsjkIkjZ8kVVsAn07g
f8jJEq6KM4+sTZqp01ScKraY
=KuSS
-----END PGP SIGNATURE-----


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


From ietf-admin@ietf.org  Mon May 17 15:13: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 PAA16291
	for <ietf-archive@ietf.org>; Mon, 17 May 2004 15:13: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 1BPnYG-0002hd-1n
	for ietf-archive@ietf.org; Mon, 17 May 2004 15:13:28 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPnXI-0002JD-00
	for ietf-archive@ietf.org; Mon, 17 May 2004 15:12:29 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPnWG-0001w1-00
	for ietf-archive@ietf.org; Mon, 17 May 2004 15:11:24 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPnDf-0005JR-UC; Mon, 17 May 2004 14:52:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPn7q-0003yz-M4
	for ietf@optimus.ietf.org; Mon, 17 May 2004 14:46: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 OAA13770
	for <ietf@ietf.org>; Mon, 17 May 2004 14:46: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 1BPn7n-0000Y7-P6
	for ietf@ietf.org; Mon, 17 May 2004 14:46:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPn6g-00001Q-00
	for ietf@ietf.org; Mon, 17 May 2004 14:44:58 -0400
Received: from m018e36d0.tmodns.net ([208.54.142.1] helo=proradius03)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPn5S-00075m-00
	for ietf@ietf.org; Mon, 17 May 2004 14:43:42 -0400
Received: from laptop2.kurtis.pp.se ([10.242.8.212])
	by proradius03 (8.11.6+Sun/8.11.6) with ESMTP id i4HIRgo27366
	for <ietf@ietf.org>; Mon, 17 May 2004 11:27:43 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by laptop2.kurtis.pp.se (Postfix) with ESMTP
	id 8401540216B; Mon, 17 May 2004 20:10:01 +0200 (CEST)
In-Reply-To: <Pine.LNX.4.44.0405161706080.678-100000@cirrus.av8.net>
References: <Pine.LNX.4.44.0405161706080.678-100000@cirrus.av8.net>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=UTF-8; format=fixed
Message-Id: <3000726A-A7FC-11D8-8726-000A95928574@kurtis.pp.se>
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org, Thomas Bocek <draft@icu.unizh.ch>
From: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
Subject: Re: 13 Root Server Limitation
Date: Mon, 17 May 2004 14:17:38 +0200
To: Dean Anderson <dean@av8.com>
X-Pgp-Rfc2646-Fix: 1
X-Mailer: Apple Mail (2.613)
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.8 required=5.0 tests=AWL,DATE_IN_PAST_03_06,
	OFFERS_ETC autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable

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


On 2004-05-17, at 00.22, Dean Anderson wrote:

> On Sun, 16 May 2004, Thomas Bocek wrote:
>
>> Hi
>>
>> I=E2=80=99m confused with the fact than the number of root servers is =
limited=20
>> to 13.
>> =46rom RFC 3226:
>>
>> "The current number of root servers is limited to 13 as that is the=20=

>> maximum
>> number of name servers and their address records that fit in one=20
>> 512-octet
>> answer for a SOA record.  If root servers start advertising A6 or KEY=20=

>> records
>> then the answer for the root NS records will not fit in a single=20
>> 512-octet DNS
>> message, resulting in a large number of TCP query connections to the=20=

>> root
>> servers."
>>
>> A query send to one of the root servers with a long name (length 255)
>> shows that the answer is 511 bytes, returning one A and 13 NS =
records.
>> My question is: Why are all 13 NS returned?

[snip]

> This dubious anycast configuration was discussed and "approved" by the
> NAMEDROPPERS Working Group in late November, 2002.

To the best of my knowledge there where root-servers anycasted way=20
before this date. And I have no idea why the namedroppers mailinglist=20
(or the IETF for that matter) would have to approve how the=20
root-servers are operated?

> Unfortunately for the
> anycast discussion, the list then became distracted by discussions
> concerning procedural irregularities involving the AXFR-clarify Draft,
> which would have altered the DNS AXFR and IXFR protocol to conform to=20=

> the
> non-standard ISC/BIND implementation, despite a number of other
> implementations being able to follow the AXFR and IXFR specifications.
> This quickly developed into a discussion regarding abuse by the list
> administrator (Randy Bush) with respect to Dan Bernstein, and so the
> anycast discussion was abandoned.
>
> As the IETF list members are perhaps unaware, the charges of abuse by=20=

> ISC
> and ISC-promoters is hardly new.  It is very hard to get real work=20
> done in
> the DNS working groups as a result.  ISC/BIND promoters have the=20
> working
> group tied up with gratuitous alterations to widely implemented=20
> protocols
> (eg AXFR-clarify) and irrational and misleading changes (eg IN-ADDR
> required) that have been demonstrated to either be security risks or
> dangerously misleading security placebo's, and have tried to suppress
> dissent on these issues by refusing to accept email, and in the past,
> silently discarding email, and otherwise harrassing people who offer
> reasoned and detailed objections.
>
> I and others would probably be more involved in issues like DNSSEC,=20
> and no
> doubt more progress would be made, if it weren't for the distractions=20=

> of
> the mismanagement of the IETF and its working groups.

I've got no idea what this has to do with the number of root-servers.

- - kurtis -

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3

iQA/AwUBQKitaKarNKXTPFCVEQJ2egCgs69tH2LXGKZI12ZEzhNJ2LVKaVkAoP0s
zo+h2jIT17WGxiR4Rkd6k/8p
=3DVd76
-----END PGP SIGNATURE-----


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


From exim@www1.ietf.org  Mon May 17 15:16: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 PAA16773
	for <ietf-archive@odin.ietf.org>; Mon, 17 May 2004 15:16: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 1BPnOh-0002hO-Re
	for ietf-archive@odin.ietf.org; Mon, 17 May 2004 15:03:38 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4HJ3ZoW010118
	for ietf-archive@odin.ietf.org; Mon, 17 May 2004 15:03:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPnDb-0005Ik-6K; Mon, 17 May 2004 14:52:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPn7n-0003yn-FC
	for ietf@optimus.ietf.org; Mon, 17 May 2004 14:46:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13756
	for <ietf@ietf.org>; Mon, 17 May 2004 14:46: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 1BPn7k-0000V6-FU
	for ietf@ietf.org; Mon, 17 May 2004 14:46:04 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPn6b-00000i-00
	for ietf@ietf.org; Mon, 17 May 2004 14:44:54 -0400
Received: from m018e36d0.tmodns.net ([208.54.142.1] helo=proradius03)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPn5P-00074P-00
	for ietf@ietf.org; Mon, 17 May 2004 14:43:39 -0400
Received: from laptop2.kurtis.pp.se ([10.242.8.212])
	by proradius03 (8.11.6+Sun/8.11.6) with ESMTP id i4HIReo27317
	for <ietf@ietf.org>; Mon, 17 May 2004 11:27:40 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by laptop2.kurtis.pp.se (Postfix) with ESMTP
	id 1C911402165; Mon, 17 May 2004 20:10:01 +0200 (CEST)
In-Reply-To: <Pine.LNX.4.44.0405111748480.19722-100000@cirrus.av8.net>
References: <Pine.LNX.4.44.0405111748480.19722-100000@cirrus.av8.net>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=fixed
Message-Id: <C6111F54-A81D-11D8-8726-000A95928574@kurtis.pp.se>
Content-Transfer-Encoding: 7bit
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
From: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
Subject: Re: [dnsop] Re: Complaint on abuse of DNSOP lists
Date: Mon, 17 May 2004 18:18:03 +0200
To: Dean Anderson <dean@av8.com>
X-Pgp-Rfc2646-Fix: 1
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.3 required=5.0 tests=UPPERCASE_25_50 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

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


On 2004-05-11, at 23.55, Dean Anderson wrote:

> On Tue, 11 May 2004, Joe Abley wrote:
>
>> For the benefit of less-operational people here who don't see humour
>> in
>> this, 198.32.176.0/24 is the PAIX IPv4 peering fabric in the Bay Area.
>
> This block is assigned to EP.NET.

I work for an IXP. Are you trying to say that that means that all
traffic that passes an IXP means that I am the upstream for that
traffic? It doesn't work this way.

- - kurtis -

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3

iQA/AwUBQKjlvqarNKXTPFCVEQIevwCfQAG+nR7rSNpkmSGvSmtTsjTEKtMAn03c
PTbWNR/gB8VkAwl/P+94/WQZ
=0ViT
-----END PGP SIGNATURE-----


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



From exim@www1.ietf.org  Mon May 17 15:27: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 PAA17759
	for <ietf-archive@odin.ietf.org>; Mon, 17 May 2004 15:27:52 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPnTB-0000IQ-3z
	for ietf-archive@odin.ietf.org; Mon, 17 May 2004 15:08:13 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4HJ8Dt9001108
	for ietf-archive@odin.ietf.org; Mon, 17 May 2004 15:08:13 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPnDe-0005JA-F6; Mon, 17 May 2004 14:52:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPn7p-0003yx-Vo
	for ietf@optimus.ietf.org; Mon, 17 May 2004 14:46: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 OAA13766
	for <ietf@ietf.org>; Mon, 17 May 2004 14:46: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 1BPn7n-0000XQ-2l
	for ietf@ietf.org; Mon, 17 May 2004 14:46:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPn6e-00001C-00
	for ietf@ietf.org; Mon, 17 May 2004 14:44:57 -0400
Received: from m018e36d0.tmodns.net ([208.54.142.1] helo=proradius03)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPn5R-00075j-00
	for ietf@ietf.org; Mon, 17 May 2004 14:43:41 -0400
Received: from laptop2.kurtis.pp.se ([10.242.8.212])
	by proradius03 (8.11.6+Sun/8.11.6) with ESMTP id i4HIRgo27367
	for <ietf@ietf.org>; Mon, 17 May 2004 11:27:43 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by laptop2.kurtis.pp.se (Postfix) with ESMTP
	id 8FD7240216E; Mon, 17 May 2004 20:10:01 +0200 (CEST)
In-Reply-To: <Pine.LNX.4.44.0405131233520.5972-100000@cirrus.av8.net>
References: <Pine.LNX.4.44.0405131233520.5972-100000@cirrus.av8.net>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=fixed
Message-Id: <A8FADF4C-A7FB-11D8-8726-000A95928574@kurtis.pp.se>
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, "Kevin C. Almeroth" <almeroth@cs.ucsb.edu>
From: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
Subject: Re: Complaint on abuse of DNSOP lists
Date: Mon, 17 May 2004 14:13:52 +0200
To: Dean Anderson <dean@av8.com>
X-Pgp-Rfc2646-Fix: 1
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.8 required=5.0 tests=AWL,DATE_IN_PAST_03_06 
	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

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



I thought I needed to pay to get to most ITU standards. But I might be 
wrong.

I can't see how personal closed discussions relate to open 
standardization. Are you saying that you want to have an open process, 
as long as you have a direct channel to the chairs in that process? I 
am not following you. I though the standardization for the IETF was 
done in public, not in private emails with the chairs. And that that 
was what made the IETF special.

- - kurtis -

On 2004-05-13, at 18.34, Dean Anderson wrote:

> Of course, this is exactly why the third world doesn't want to have the
> IETF in charge in its present form.
>
> Professional and standards organizations aren't private clubs.
>
> 		--Dean
>
> On Wed, 12 May 2004, Kevin C. Almeroth wrote:
>
>> This pretty much does it for me:  anyone who says they are entitled
>> to participate in the IETF immediately goes into my spam bucket.
>>
>> As others have pointed out, you've done yourself more harm than good.
>>
>>>> I'm entitled to particpate, and I'm entitled to send email to the WG
>>>> chairs as a participant.
>>>>
>>>> One thing I've noticed is that of none of the people criticizing me 
>>>> has
>>>> thought to address the fact that OUR ADDRESS SPACE IS NOT HIJACKED, 
>>>> and
>>>> that these people associated with the IETF: Paul Vixie, Joe Abley, 
>>>> Bill
>>>> Manning, and Rob Austein as WG Co-chair in his role for IETF 
>>>> business, all
>>>> claim that it is.  But anyone can plainly see they are lying.
>>>>
>>>> Dean Anderson
>>>> Av8 Internet, Inc
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3

iQA/AwUBQKisgqarNKXTPFCVEQLJrQCgoc/TPKrlLx7QUTXsjkIkjZ8kVVsAn07g
f8jJEq6KM4+sTZqp01ScKraY
=KuSS
-----END PGP SIGNATURE-----


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



From exim@www1.ietf.org  Mon May 17 15:32: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 PAA18253
	for <ietf-archive@odin.ietf.org>; Mon, 17 May 2004 15:32: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 1BPnWI-0002us-Ll
	for ietf-archive@odin.ietf.org; Mon, 17 May 2004 15:11:34 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4HJBQ5m011200
	for ietf-archive@odin.ietf.org; Mon, 17 May 2004 15:11:26 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPnDf-0005JR-UC; Mon, 17 May 2004 14:52:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPn7q-0003yz-M4
	for ietf@optimus.ietf.org; Mon, 17 May 2004 14:46: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 OAA13770
	for <ietf@ietf.org>; Mon, 17 May 2004 14:46: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 1BPn7n-0000Y7-P6
	for ietf@ietf.org; Mon, 17 May 2004 14:46:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPn6g-00001Q-00
	for ietf@ietf.org; Mon, 17 May 2004 14:44:58 -0400
Received: from m018e36d0.tmodns.net ([208.54.142.1] helo=proradius03)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPn5S-00075m-00
	for ietf@ietf.org; Mon, 17 May 2004 14:43:42 -0400
Received: from laptop2.kurtis.pp.se ([10.242.8.212])
	by proradius03 (8.11.6+Sun/8.11.6) with ESMTP id i4HIRgo27366
	for <ietf@ietf.org>; Mon, 17 May 2004 11:27:43 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by laptop2.kurtis.pp.se (Postfix) with ESMTP
	id 8401540216B; Mon, 17 May 2004 20:10:01 +0200 (CEST)
In-Reply-To: <Pine.LNX.4.44.0405161706080.678-100000@cirrus.av8.net>
References: <Pine.LNX.4.44.0405161706080.678-100000@cirrus.av8.net>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=UTF-8; format=fixed
Message-Id: <3000726A-A7FC-11D8-8726-000A95928574@kurtis.pp.se>
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org, Thomas Bocek <draft@icu.unizh.ch>
From: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
Subject: Re: 13 Root Server Limitation
Date: Mon, 17 May 2004 14:17:38 +0200
To: Dean Anderson <dean@av8.com>
X-Pgp-Rfc2646-Fix: 1
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.9 required=5.0 tests=AWL,DATE_IN_PAST_03_06,
	OFFERS_ETC 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

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


On 2004-05-17, at 00.22, Dean Anderson wrote:

> On Sun, 16 May 2004, Thomas Bocek wrote:
>
>> Hi
>>
>> I=E2=80=99m confused with the fact than the number of root servers is =
limited=20
>> to 13.
>> =46rom RFC 3226:
>>
>> "The current number of root servers is limited to 13 as that is the=20=

>> maximum
>> number of name servers and their address records that fit in one=20
>> 512-octet
>> answer for a SOA record.  If root servers start advertising A6 or KEY=20=

>> records
>> then the answer for the root NS records will not fit in a single=20
>> 512-octet DNS
>> message, resulting in a large number of TCP query connections to the=20=

>> root
>> servers."
>>
>> A query send to one of the root servers with a long name (length 255)
>> shows that the answer is 511 bytes, returning one A and 13 NS =
records.
>> My question is: Why are all 13 NS returned?

[snip]

> This dubious anycast configuration was discussed and "approved" by the
> NAMEDROPPERS Working Group in late November, 2002.

To the best of my knowledge there where root-servers anycasted way=20
before this date. And I have no idea why the namedroppers mailinglist=20
(or the IETF for that matter) would have to approve how the=20
root-servers are operated?

> Unfortunately for the
> anycast discussion, the list then became distracted by discussions
> concerning procedural irregularities involving the AXFR-clarify Draft,
> which would have altered the DNS AXFR and IXFR protocol to conform to=20=

> the
> non-standard ISC/BIND implementation, despite a number of other
> implementations being able to follow the AXFR and IXFR specifications.
> This quickly developed into a discussion regarding abuse by the list
> administrator (Randy Bush) with respect to Dan Bernstein, and so the
> anycast discussion was abandoned.
>
> As the IETF list members are perhaps unaware, the charges of abuse by=20=

> ISC
> and ISC-promoters is hardly new.  It is very hard to get real work=20
> done in
> the DNS working groups as a result.  ISC/BIND promoters have the=20
> working
> group tied up with gratuitous alterations to widely implemented=20
> protocols
> (eg AXFR-clarify) and irrational and misleading changes (eg IN-ADDR
> required) that have been demonstrated to either be security risks or
> dangerously misleading security placebo's, and have tried to suppress
> dissent on these issues by refusing to accept email, and in the past,
> silently discarding email, and otherwise harrassing people who offer
> reasoned and detailed objections.
>
> I and others would probably be more involved in issues like DNSSEC,=20
> and no
> doubt more progress would be made, if it weren't for the distractions=20=

> of
> the mismanagement of the IETF and its working groups.

I've got no idea what this has to do with the number of root-servers.

- - kurtis -

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3

iQA/AwUBQKitaKarNKXTPFCVEQJ2egCgs69tH2LXGKZI12ZEzhNJ2LVKaVkAoP0s
zo+h2jIT17WGxiR4Rkd6k/8p
=3DVd76
-----END PGP SIGNATURE-----


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



From ietf-admin@ietf.org  Mon May 17 17:51:01 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04569
	for <ietf-archive@ietf.org>; Mon, 17 May 2004 17:51: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 1BPq0k-0000Qa-HZ
	for ietf-archive@ietf.org; Mon, 17 May 2004 17:51:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPpwR-0006wb-00
	for ietf-archive@ietf.org; Mon, 17 May 2004 17:46:36 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPprS-0005Xh-00
	for ietf-archive@ietf.org; Mon, 17 May 2004 17:41:26 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPpVW-0004Yb-Sn; Mon, 17 May 2004 17:18:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPonx-0000y9-93
	for ietf@optimus.ietf.org; Mon, 17 May 2004 16:33:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24010
	for <ietf@ietf.org>; Mon, 17 May 2004 16:33: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 1BPonu-0001nr-KD
	for ietf@ietf.org; Mon, 17 May 2004 16:33:42 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPomn-0001Mj-00
	for ietf@ietf.org; Mon, 17 May 2004 16:32:33 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPolQ-0000Wm-00
	for ietf@ietf.org; Mon, 17 May 2004 16:31:08 -0400
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i4HKUaVn026585
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 17 May 2004 16:30:36 -0400
Date: Mon, 17 May 2004 16:30:36 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
cc: ietf@ietf.org, "Kevin C. Almeroth" <almeroth@cs.ucsb.edu>
Subject: Re: Complaint on abuse of DNSOP lists
In-Reply-To: <A8FADF4C-A7FB-11D8-8726-000A95928574@kurtis.pp.se>
Message-ID: <Pine.LNX.4.44.0405171619150.25950-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, 17 May 2004, Kurt Erik Lindqvist wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 
> 
> I thought I needed to pay to get to most ITU standards. But I might be 
> wrong.

What does that have to do with anything???  The IETF obtains funds, too.  
Nothing is free.

> I can't see how personal closed discussions relate to open 
> standardization. Are you saying that you want to have an open process, 
> as long as you have a direct channel to the chairs in that process? I 
> am not following you. I though the standardization for the IETF was 
> done in public, not in private emails with the chairs. And that that 
> was what made the IETF special.

Some IETF business needs to be conducted off-list.  If the IETF is going
to participate in unlawful group boycotts, then it can't really claim to
have an open process.  You couch your terms as though I expect to have a
'special direct channel' to the chairs.  I only expect to have the _SAME_
access as everyone else, and no less.  If others can send email directly
to the chairs, then I should have that opportunity as well.  Anything less 
is unequal access.

As I've already pointed out, this abuse on the DNS lists isn't new, and it
hasn't only targeted me.  And in fact, in the past, it hasn't been limited
to off-list email, but on-list email as well.  I'm just the _current_
victim.

		--Dean





> > - - kurtis -
> 
> On 2004-05-13, at 18.34, Dean Anderson wrote:
> 
> > Of course, this is exactly why the third world doesn't want to have the
> > IETF in charge in its present form.
> >
> > Professional and standards organizations aren't private clubs.
> >
> > 		--Dean
> >
> > On Wed, 12 May 2004, Kevin C. Almeroth wrote:
> >
> >> This pretty much does it for me:  anyone who says they are entitled
> >> to participate in the IETF immediately goes into my spam bucket.
> >>
> >> As others have pointed out, you've done yourself more harm than good.
> >>
> >>>> I'm entitled to particpate, and I'm entitled to send email to the WG
> >>>> chairs as a participant.
> >>>>
> >>>> One thing I've noticed is that of none of the people criticizing me 
> >>>> has
> >>>> thought to address the fact that OUR ADDRESS SPACE IS NOT HIJACKED, 
> >>>> and
> >>>> that these people associated with the IETF: Paul Vixie, Joe Abley, 
> >>>> Bill
> >>>> Manning, and Rob Austein as WG Co-chair in his role for IETF 
> >>>> business, all
> >>>> claim that it is.  But anyone can plainly see they are lying.
> >>>>
> >>>> Dean Anderson
> >>>> Av8 Internet, Inc
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> 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
> >
> 
> -----BEGIN PGP SIGNATURE-----
> Version: PGP 8.0.3
> 
> iQA/AwUBQKisgqarNKXTPFCVEQLJrQCgoc/TPKrlLx7QUTXsjkIkjZ8kVVsAn07g
> f8jJEq6KM4+sTZqp01ScKraY
> =KuSS
> -----END PGP SIGNATURE-----
> 
> 


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


From ietf-admin@ietf.org  Mon May 17 17:53:33 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05158
	for <ietf-archive@ietf.org>; Mon, 17 May 2004 17:53: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 1BPq3C-0001Jy-Mk
	for ietf-archive@ietf.org; Mon, 17 May 2004 17:53:34 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPq0m-0000RH-00
	for ietf-archive@ietf.org; Mon, 17 May 2004 17:51:06 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPpwX-0006xr-00
	for ietf-archive@ietf.org; Mon, 17 May 2004 17:46:41 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPpjm-0002ex-QX; Mon, 17 May 2004 17:33:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPp5B-0008SE-PM
	for ietf@optimus.ietf.org; Mon, 17 May 2004 16:51: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 QAA25956
	for <ietf@ietf.org>; Mon, 17 May 2004 16:51:31 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPp59-0007gY-M4
	for ietf@ietf.org; Mon, 17 May 2004 16:51:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPp0A-0006Iq-00
	for ietf@ietf.org; Mon, 17 May 2004 16:46:24 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPovx-00053M-00
	for ietf@ietf.org; Mon, 17 May 2004 16:42:01 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BPoZr-0000os-8O
	for ietf@ietf.org; Mon, 17 May 2004 16:19:11 -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 i4HKJ62u026312
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 17 May 2004 16:19:09 -0400
Date: Mon, 17 May 2004 16:19:06 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
cc: "<ietf@ietf.org>" <ietf@ietf.org>
Subject: Re: [dnsop] Re: Complaint on abuse of DNSOP lists
In-Reply-To: <C6111F54-A81D-11D8-8726-000A95928574@kurtis.pp.se>
Message-ID: <Pine.LNX.4.44.0405171600540.25950-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, 17 May 2004, Kurt Erik Lindqvist wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 
> On 2004-05-11, at 23.55, Dean Anderson wrote:
> 
> > On Tue, 11 May 2004, Joe Abley wrote:
> >
> >> For the benefit of less-operational people here who don't see humour
> >> in this, 198.32.176.0/24 is the PAIX IPv4 peering fabric in the Bay
> >> Area.
> >
> > This block is assigned to EP.NET.
> 
> I work for an IXP. Are you trying to say that that means that all
> traffic that passes an IXP means that I am the upstream for that
> traffic? It doesn't work this way.

It certainly does when you've assigned them IP addresses.

But, I do find it rather funny that some (very few) people running
exchange points (which are the simplest of ISPs) don't think they provide
transit services.  For the less technical, an exchange point is a place
that provides rack space and a Local Area Network of some sort (think
ethernet, but ethernet has long been replaced by faster technologies).  
Other people (usually ISPs, but not always)  come in to an exchange point
and establish BGP peering sessions with other exchange point customers.  
Sometimes this is over the LAN provided by the exchange point, sometimes
they pull their own cable between their racks.  The only thing that is
different is that an exchange point doesn't need to have it's own AS
number, nor does it need to run BGP.  The lack of a BGP session doesn't
have any impact on whether there is a relationship with the customers of
the exchange point, nor on whether traffic is transited by an exchange
point.

When customers pull their own cable, one can't necessarilly tell that
those customers connected at an exchange point. That type of connection is
totally private. But LAN connections provided by the exchange point and
assigned IP addresses are just regular network connections, subject to the
rules and AUP of the service provider (exchange point).  An exchange point
is expected to behave just like other ISPs with respect to abuse and AUPs.  
Most exchange points do have AUPs, and most do handle abuse by their
customers.

		--Dean



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


From exim@www1.ietf.org  Mon May 17 17:55:47 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05402
	for <ietf-archive@odin.ietf.org>; Mon, 17 May 2004 17:55: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 1BPprU-0008QZ-F8
	for ietf-archive@odin.ietf.org; Mon, 17 May 2004 17:41:35 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4HLfSOf032389
	for ietf-archive@odin.ietf.org; Mon, 17 May 2004 17:41:28 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPpVW-0004Yb-Sn; Mon, 17 May 2004 17:18:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPonx-0000y9-93
	for ietf@optimus.ietf.org; Mon, 17 May 2004 16:33:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24010
	for <ietf@ietf.org>; Mon, 17 May 2004 16:33: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 1BPonu-0001nr-KD
	for ietf@ietf.org; Mon, 17 May 2004 16:33:42 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPomn-0001Mj-00
	for ietf@ietf.org; Mon, 17 May 2004 16:32:33 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPolQ-0000Wm-00
	for ietf@ietf.org; Mon, 17 May 2004 16:31:08 -0400
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i4HKUaVn026585
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 17 May 2004 16:30:36 -0400
Date: Mon, 17 May 2004 16:30:36 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
cc: ietf@ietf.org, "Kevin C. Almeroth" <almeroth@cs.ucsb.edu>
Subject: Re: Complaint on abuse of DNSOP lists
In-Reply-To: <A8FADF4C-A7FB-11D8-8726-000A95928574@kurtis.pp.se>
Message-ID: <Pine.LNX.4.44.0405171619150.25950-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, 17 May 2004, Kurt Erik Lindqvist wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 
> 
> I thought I needed to pay to get to most ITU standards. But I might be 
> wrong.

What does that have to do with anything???  The IETF obtains funds, too.  
Nothing is free.

> I can't see how personal closed discussions relate to open 
> standardization. Are you saying that you want to have an open process, 
> as long as you have a direct channel to the chairs in that process? I 
> am not following you. I though the standardization for the IETF was 
> done in public, not in private emails with the chairs. And that that 
> was what made the IETF special.

Some IETF business needs to be conducted off-list.  If the IETF is going
to participate in unlawful group boycotts, then it can't really claim to
have an open process.  You couch your terms as though I expect to have a
'special direct channel' to the chairs.  I only expect to have the _SAME_
access as everyone else, and no less.  If others can send email directly
to the chairs, then I should have that opportunity as well.  Anything less 
is unequal access.

As I've already pointed out, this abuse on the DNS lists isn't new, and it
hasn't only targeted me.  And in fact, in the past, it hasn't been limited
to off-list email, but on-list email as well.  I'm just the _current_
victim.

		--Dean





> > - - kurtis -
> 
> On 2004-05-13, at 18.34, Dean Anderson wrote:
> 
> > Of course, this is exactly why the third world doesn't want to have the
> > IETF in charge in its present form.
> >
> > Professional and standards organizations aren't private clubs.
> >
> > 		--Dean
> >
> > On Wed, 12 May 2004, Kevin C. Almeroth wrote:
> >
> >> This pretty much does it for me:  anyone who says they are entitled
> >> to participate in the IETF immediately goes into my spam bucket.
> >>
> >> As others have pointed out, you've done yourself more harm than good.
> >>
> >>>> I'm entitled to particpate, and I'm entitled to send email to the WG
> >>>> chairs as a participant.
> >>>>
> >>>> One thing I've noticed is that of none of the people criticizing me 
> >>>> has
> >>>> thought to address the fact that OUR ADDRESS SPACE IS NOT HIJACKED, 
> >>>> and
> >>>> that these people associated with the IETF: Paul Vixie, Joe Abley, 
> >>>> Bill
> >>>> Manning, and Rob Austein as WG Co-chair in his role for IETF 
> >>>> business, all
> >>>> claim that it is.  But anyone can plainly see they are lying.
> >>>>
> >>>> Dean Anderson
> >>>> Av8 Internet, Inc
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> 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
> >
> 
> -----BEGIN PGP SIGNATURE-----
> Version: PGP 8.0.3
> 
> iQA/AwUBQKisgqarNKXTPFCVEQLJrQCgoc/TPKrlLx7QUTXsjkIkjZ8kVVsAn07g
> f8jJEq6KM4+sTZqp01ScKraY
> =KuSS
> -----END PGP SIGNATURE-----
> 
> 


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



From ietf-admin@ietf.org  Mon May 17 17:57:43 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05636
	for <ietf-archive@ietf.org>; Mon, 17 May 2004 17:57: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 1BPq7E-0002bP-6k
	for ietf-archive@ietf.org; Mon, 17 May 2004 17:57:44 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPq55-0001yn-00
	for ietf-archive@ietf.org; Mon, 17 May 2004 17:55:32 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPq31-0001CK-00
	for ietf-archive@ietf.org; Mon, 17 May 2004 17:53:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPpmK-000570-9S; Mon, 17 May 2004 17:36:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPpE1-0003WP-TF
	for ietf@optimus.ietf.org; Mon, 17 May 2004 17:00: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 RAA27012
	for <ietf@ietf.org>; Mon, 17 May 2004 17:00: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 1BPpDw-0002Of-VU
	for ietf@ietf.org; Mon, 17 May 2004 17:00:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPp9r-0001Aj-00
	for ietf@ietf.org; Mon, 17 May 2004 16:56:24 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPp5C-0007ar-00
	for ietf@ietf.org; Mon, 17 May 2004 16:51:34 -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 i4HKp1ko026949
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 17 May 2004 16:51:01 -0400
Date: Mon, 17 May 2004 16:51:01 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
cc: ietf@ietf.org, Thomas Bocek <draft@icu.unizh.ch>
Subject: Re: 13 Root Server Limitation
In-Reply-To: <3000726A-A7FC-11D8-8726-000A95928574@kurtis.pp.se>
Message-ID: <Pine.LNX.4.44.0405171631140.25950-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, 17 May 2004, Kurt Erik Lindqvist wrote:

> > This dubious anycast configuration was discussed and "approved" by the
> > NAMEDROPPERS Working Group in late November, 2002.
> 
> To the best of my knowledge there where root-servers anycasted way 
> before this date. 

This may be true, but it certainly wasn't widespread.

> And I have no idea why the namedroppers mailinglist (or the IETF for
> that matter) would have to approve how the root-servers are operated?

I have no idea why anyone would bother to ask a group of DNS protocol
experts about a DNS protocol-affecting change to the operation of root
namerservers, either. The insanity. Go figure.  Why not just go do it, and
see what breaks? Screw the possible false assumptions. Besides, if it
doesn't break on my shift, it wasn't my fault.  Who needs engineers when
you have operators?  People worry too much.

Of course, this same line of thought led to the 3 Mile Island meltdown,
when the __operators__ decided on their own to shut off the emergency
cooling pumps. By the time the engineers came in and told them to turn the
pumps back on it was too late. Although, it could have been worse if
delayed longer.  But it wouldn't have happened at all if the operators
hadn't turned off the emergency cooling pumps.  Moral: Just because you
can operate something, and know _how_ to make changes, doesn't mean you
know what changes are safe or wise to make.

		--Dean



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


From exim@www1.ietf.org  Mon May 17 18:00:14 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06133
	for <ietf-archive@odin.ietf.org>; Mon, 17 May 2004 18:00: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 1BPpwZ-0002vo-HL
	for ietf-archive@odin.ietf.org; Mon, 17 May 2004 17:46:43 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4HLkhIu011264
	for ietf-archive@odin.ietf.org; Mon, 17 May 2004 17:46:43 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPpjm-0002ex-QX; Mon, 17 May 2004 17:33:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPp5B-0008SE-PM
	for ietf@optimus.ietf.org; Mon, 17 May 2004 16:51: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 QAA25956
	for <ietf@ietf.org>; Mon, 17 May 2004 16:51:31 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPp59-0007gY-M4
	for ietf@ietf.org; Mon, 17 May 2004 16:51:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPp0A-0006Iq-00
	for ietf@ietf.org; Mon, 17 May 2004 16:46:24 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPovx-00053M-00
	for ietf@ietf.org; Mon, 17 May 2004 16:42:01 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BPoZr-0000os-8O
	for ietf@ietf.org; Mon, 17 May 2004 16:19:11 -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 i4HKJ62u026312
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 17 May 2004 16:19:09 -0400
Date: Mon, 17 May 2004 16:19:06 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
cc: "<ietf@ietf.org>" <ietf@ietf.org>
Subject: Re: [dnsop] Re: Complaint on abuse of DNSOP lists
In-Reply-To: <C6111F54-A81D-11D8-8726-000A95928574@kurtis.pp.se>
Message-ID: <Pine.LNX.4.44.0405171600540.25950-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, 17 May 2004, Kurt Erik Lindqvist wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 
> On 2004-05-11, at 23.55, Dean Anderson wrote:
> 
> > On Tue, 11 May 2004, Joe Abley wrote:
> >
> >> For the benefit of less-operational people here who don't see humour
> >> in this, 198.32.176.0/24 is the PAIX IPv4 peering fabric in the Bay
> >> Area.
> >
> > This block is assigned to EP.NET.
> 
> I work for an IXP. Are you trying to say that that means that all
> traffic that passes an IXP means that I am the upstream for that
> traffic? It doesn't work this way.

It certainly does when you've assigned them IP addresses.

But, I do find it rather funny that some (very few) people running
exchange points (which are the simplest of ISPs) don't think they provide
transit services.  For the less technical, an exchange point is a place
that provides rack space and a Local Area Network of some sort (think
ethernet, but ethernet has long been replaced by faster technologies).  
Other people (usually ISPs, but not always)  come in to an exchange point
and establish BGP peering sessions with other exchange point customers.  
Sometimes this is over the LAN provided by the exchange point, sometimes
they pull their own cable between their racks.  The only thing that is
different is that an exchange point doesn't need to have it's own AS
number, nor does it need to run BGP.  The lack of a BGP session doesn't
have any impact on whether there is a relationship with the customers of
the exchange point, nor on whether traffic is transited by an exchange
point.

When customers pull their own cable, one can't necessarilly tell that
those customers connected at an exchange point. That type of connection is
totally private. But LAN connections provided by the exchange point and
assigned IP addresses are just regular network connections, subject to the
rules and AUP of the service provider (exchange point).  An exchange point
is expected to behave just like other ISPs with respect to abuse and AUPs.  
Most exchange points do have AUPs, and most do handle abuse by their
customers.

		--Dean



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



From exim@www1.ietf.org  Mon May 17 18:01:36 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06353
	for <ietf-archive@odin.ietf.org>; Mon, 17 May 2004 18:01: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 1BPq33-0005UK-Ij
	for ietf-archive@odin.ietf.org; Mon, 17 May 2004 17:53:30 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4HLrP7I021071
	for ietf-archive@odin.ietf.org; Mon, 17 May 2004 17: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 1BPpmK-000570-9S; Mon, 17 May 2004 17:36:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPpE1-0003WP-TF
	for ietf@optimus.ietf.org; Mon, 17 May 2004 17:00: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 RAA27012
	for <ietf@ietf.org>; Mon, 17 May 2004 17:00: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 1BPpDw-0002Of-VU
	for ietf@ietf.org; Mon, 17 May 2004 17:00:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPp9r-0001Aj-00
	for ietf@ietf.org; Mon, 17 May 2004 16:56:24 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPp5C-0007ar-00
	for ietf@ietf.org; Mon, 17 May 2004 16:51:34 -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 i4HKp1ko026949
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 17 May 2004 16:51:01 -0400
Date: Mon, 17 May 2004 16:51:01 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
cc: ietf@ietf.org, Thomas Bocek <draft@icu.unizh.ch>
Subject: Re: 13 Root Server Limitation
In-Reply-To: <3000726A-A7FC-11D8-8726-000A95928574@kurtis.pp.se>
Message-ID: <Pine.LNX.4.44.0405171631140.25950-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, 17 May 2004, Kurt Erik Lindqvist wrote:

> > This dubious anycast configuration was discussed and "approved" by the
> > NAMEDROPPERS Working Group in late November, 2002.
> 
> To the best of my knowledge there where root-servers anycasted way 
> before this date. 

This may be true, but it certainly wasn't widespread.

> And I have no idea why the namedroppers mailinglist (or the IETF for
> that matter) would have to approve how the root-servers are operated?

I have no idea why anyone would bother to ask a group of DNS protocol
experts about a DNS protocol-affecting change to the operation of root
namerservers, either. The insanity. Go figure.  Why not just go do it, and
see what breaks? Screw the possible false assumptions. Besides, if it
doesn't break on my shift, it wasn't my fault.  Who needs engineers when
you have operators?  People worry too much.

Of course, this same line of thought led to the 3 Mile Island meltdown,
when the __operators__ decided on their own to shut off the emergency
cooling pumps. By the time the engineers came in and told them to turn the
pumps back on it was too late. Although, it could have been worse if
delayed longer.  But it wouldn't have happened at all if the operators
hadn't turned off the emergency cooling pumps.  Moral: Just because you
can operate something, and know _how_ to make changes, doesn't mean you
know what changes are safe or wise to make.

		--Dean



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



From ietf-admin@ietf.org  Mon May 17 18:20: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 SAA08557
	for <ietf-archive@ietf.org>; Mon, 17 May 2004 18:20: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 1BPqTJ-0003By-NA
	for ietf-archive@ietf.org; Mon, 17 May 2004 18:20:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPqSN-0002pw-00
	for ietf-archive@ietf.org; Mon, 17 May 2004 18:19:35 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPqRi-0002UP-00
	for ietf-archive@ietf.org; Mon, 17 May 2004 18:18:54 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPqBV-0003HP-Ob; Mon, 17 May 2004 18:02:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPq0c-0003m1-BT
	for ietf@optimus.ietf.org; Mon, 17 May 2004 17:50: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 RAA04483
	for <ietf@ietf.org>; Mon, 17 May 2004 17:50: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 1BPq0Z-0000Ok-ON
	for ietf@ietf.org; Mon, 17 May 2004 17:50:51 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPpw7-0006sn-00
	for ietf@ietf.org; Mon, 17 May 2004 17:46:16 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPpr6-0005SO-00
	for ietf@ietf.org; Mon, 17 May 2004 17:41:04 -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 i4HLed1C056789;
	Mon, 17 May 2004 23:40:39 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <200405171541.i4HFflE17760@boreas.isi.edu>
References: <200405171541.i4HFflE17760@boreas.isi.edu>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <DFC3BD05-A84A-11D8-AC18-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: "'Internet Engineering Task Force'" <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: Root Anycast
Date: Mon, 17 May 2004 23:40:54 +0200
To: Bill Manning <bmanning@ISI.EDU>
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 17-mei-04, at 17:41, Bill Manning wrote:

> % But as long as we're dissing anycast root DNS servers: how many of 
> the
> % root servers are being anycast now or in the future, and how many
> % won't?

> 	http://www.rssac.org/

> 	check the 17th & 18th meeting minutes.

Result:

Unicast: A, E, H, L
Anycast: B, C, D, F, G, I, J, K, M (now or planned)

The thing that worries me is that apparently, there is no policy about 
this whatsoever, the root operators each get to decide what they want 
to do. The fact that .org is run using only two anycast addresses also 
indicates that apparently the ICANN doesn't feel the need to throw 
their weight around in this area.

Now obviously anycasting is a very useful mechanism to reduce latency 
and increase capacity and robustness. However, these properties are 
best served by careful design rather than organic growth. If we 
consider the number of actual servers/server clusters and the number of 
root IP addresses as given, there are still many ways to skin this cat. 
One would be using 12 unicast servers and anycast just one address. 
However, this only creates partial benefits, especially with regard to 
robustness in the presence of denial of service attacks. But at the 
other extreme, 13 unicast addresses, there are problems as well. For 
instance, if a network enjoys good local/regional connectivity, it may 
very well see the anycast instances for all roots behind some common 
infrastructure. When this piece of infrastructure fails, it may take 
considerable time before BGP converges and mean root reachability 
reaches acceptable levels again.

It seems to me that any design that makes the root addresses seem as 
distributed around the net as possible would be optimal, as in this 
case the changes of an outage triggering rerouting of a large number of 
root addresses is as small as possible. In order to do this, the number 
of root addresses that are available within a geographic region (where 
"region" < RIR region) should be limited.

(Just having the roots close is of little value: good recursive servers 
hone in to the one with the lowest RTT anyway, so having one close by 
is enough. However, when this one fails it's important that after the 
timeout, the next root address that the recursive server tries is 
highly likely to be reachable, in order to avoid stacking timeout upon 
timeout. A couple 100 ms extra round trip delay doesn't mean much in 
cases where the recursive server suffers a timeout anyway.)


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


From ietf-admin@ietf.org  Mon May 17 18:24: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 SAA08893
	for <ietf-archive@ietf.org>; Mon, 17 May 2004 18:24: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 1BPqXT-0004kg-1U
	for ietf-archive@ietf.org; Mon, 17 May 2004 18:24:51 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPqWa-0004Mp-00
	for ietf-archive@ietf.org; Mon, 17 May 2004 18:23:56 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPqVX-0003yn-00
	for ietf-archive@ietf.org; Mon, 17 May 2004 18:22:51 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPqBq-0003d5-Lf; Mon, 17 May 2004 18:02:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPq3s-0006dc-Bf
	for ietf@optimus.ietf.org; Mon, 17 May 2004 17:54:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05254
	for <ietf@ietf.org>; Mon, 17 May 2004 17:54: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 1BPq3p-0001Y0-NK
	for ietf@ietf.org; Mon, 17 May 2004 17:54:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPq1o-0000cU-00
	for ietf@ietf.org; Mon, 17 May 2004 17:52:08 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPpyb-0007ZT-00
	for ietf@ietf.org; Mon, 17 May 2004 17:48:49 -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 i4HLmT1C056980;
	Mon, 17 May 2004 23:48:30 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <Pine.LNX.4.44.0405171313140.22879-100000@cirrus.av8.net>
References: <Pine.LNX.4.44.0405171313140.22879-100000@cirrus.av8.net>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <F8350588-A84B-11D8-AC18-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: "'Internet Engineering Task Force'" <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: 13 Root Server Limitation
Date: Mon, 17 May 2004 23:48:44 +0200
To: Dean Anderson <dean@av8.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 17-mei-04, at 19:36, Dean Anderson wrote:

> It is conceptually very simple:  Setup 2 anycast servers (S1 and S2) on
> several paths (AS-A and AS-Y, different AS numbers)  Have an ISP 
> connect
> to both of those paths, and then have that ISP do fine grained load
> balancing to prefixes available over those paths. Packets will go to 
> each
> anycast server.  This will not cause a problem with UDP, since the 
> entire
> connection transaction is in one packet. But TCP will have a minumim 
> of 3
> packets.  2 packets will go to server S1, and one packet will go to 
> server
> S2.  Neither S1 nor S2 will have a complete TCP connection, and so both
> will fail.

As I've said before, this isn't how things work in practice, as actual 
load sharing towards a destination over two different AS paths doesn't 
happen, and when load sharing is done, it's almost always in a way that 
keeps packets belonging to a single TCP session together. (You really 
don't want to see what happens to TCP performance with 100% out of 
order packets.)

And even if this happened it would very likely be non-fatal, as at some 
point retransmissions will make it trough so the TCP session works. As 
most data is going from the server to the client, and ACKs work 
cumulative, the performance hit is probably not too catastrophic.


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


From exim@www1.ietf.org  Mon May 17 18:31:49 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09632
	for <ietf-archive@odin.ietf.org>; Mon, 17 May 2004 18:31:49 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPqRk-00067q-JB
	for ietf-archive@odin.ietf.org; Mon, 17 May 2004 18:18:56 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4HMIueX023547
	for ietf-archive@odin.ietf.org; Mon, 17 May 2004 18:18:56 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPqBV-0003HP-Ob; Mon, 17 May 2004 18:02:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPq0c-0003m1-BT
	for ietf@optimus.ietf.org; Mon, 17 May 2004 17:50: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 RAA04483
	for <ietf@ietf.org>; Mon, 17 May 2004 17:50: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 1BPq0Z-0000Ok-ON
	for ietf@ietf.org; Mon, 17 May 2004 17:50:51 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPpw7-0006sn-00
	for ietf@ietf.org; Mon, 17 May 2004 17:46:16 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPpr6-0005SO-00
	for ietf@ietf.org; Mon, 17 May 2004 17:41:04 -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 i4HLed1C056789;
	Mon, 17 May 2004 23:40:39 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <200405171541.i4HFflE17760@boreas.isi.edu>
References: <200405171541.i4HFflE17760@boreas.isi.edu>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <DFC3BD05-A84A-11D8-AC18-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: "'Internet Engineering Task Force'" <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: Root Anycast
Date: Mon, 17 May 2004 23:40:54 +0200
To: Bill Manning <bmanning@ISI.EDU>
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 17-mei-04, at 17:41, Bill Manning wrote:

> % But as long as we're dissing anycast root DNS servers: how many of 
> the
> % root servers are being anycast now or in the future, and how many
> % won't?

> 	http://www.rssac.org/

> 	check the 17th & 18th meeting minutes.

Result:

Unicast: A, E, H, L
Anycast: B, C, D, F, G, I, J, K, M (now or planned)

The thing that worries me is that apparently, there is no policy about 
this whatsoever, the root operators each get to decide what they want 
to do. The fact that .org is run using only two anycast addresses also 
indicates that apparently the ICANN doesn't feel the need to throw 
their weight around in this area.

Now obviously anycasting is a very useful mechanism to reduce latency 
and increase capacity and robustness. However, these properties are 
best served by careful design rather than organic growth. If we 
consider the number of actual servers/server clusters and the number of 
root IP addresses as given, there are still many ways to skin this cat. 
One would be using 12 unicast servers and anycast just one address. 
However, this only creates partial benefits, especially with regard to 
robustness in the presence of denial of service attacks. But at the 
other extreme, 13 unicast addresses, there are problems as well. For 
instance, if a network enjoys good local/regional connectivity, it may 
very well see the anycast instances for all roots behind some common 
infrastructure. When this piece of infrastructure fails, it may take 
considerable time before BGP converges and mean root reachability 
reaches acceptable levels again.

It seems to me that any design that makes the root addresses seem as 
distributed around the net as possible would be optimal, as in this 
case the changes of an outage triggering rerouting of a large number of 
root addresses is as small as possible. In order to do this, the number 
of root addresses that are available within a geographic region (where 
"region" < RIR region) should be limited.

(Just having the roots close is of little value: good recursive servers 
hone in to the one with the lowest RTT anyway, so having one close by 
is enough. However, when this one fails it's important that after the 
timeout, the next root address that the recursive server tries is 
highly likely to be reachable, in order to avoid stacking timeout upon 
timeout. A couple 100 ms extra round trip delay doesn't mean much in 
cases where the recursive server suffers a timeout anyway.)


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



From ietf-admin@ietf.org  Mon May 17 18:42: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 SAA10613
	for <ietf-archive@ietf.org>; Mon, 17 May 2004 18:42: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 1BPqou-0003tz-Hx
	for ietf-archive@ietf.org; Mon, 17 May 2004 18:42:52 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPqnp-0003ST-00
	for ietf-archive@ietf.org; Mon, 17 May 2004 18:41:46 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPqmj-00035A-00
	for ietf-archive@ietf.org; Mon, 17 May 2004 18:40:37 -0400
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BPqkT-0003wE-Oo
	for ietf-archive@ietf.org; Mon, 17 May 2004 18:38:19 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPqcY-0004Sg-6h; Mon, 17 May 2004 18:30:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPqEk-0006Jn-75
	for ietf@optimus.ietf.org; Mon, 17 May 2004 18:05: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 SAA06814
	for <ietf@ietf.org>; Mon, 17 May 2004 18:05: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 1BPqEh-0005qv-9P
	for ietf@ietf.org; Mon, 17 May 2004 18:05:27 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPqDr-0005WS-00
	for ietf@ietf.org; Mon, 17 May 2004 18:04:35 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPqDG-0005BT-00
	for ietf@ietf.org; Mon, 17 May 2004 18:03:58 -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 i4HM3c1C057288;
	Tue, 18 May 2004 00:03:38 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <Pine.LNX.4.44.0405171631140.25950-100000@cirrus.av8.net>
References: <Pine.LNX.4.44.0405171631140.25950-100000@cirrus.av8.net>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <15ECE4EE-A84E-11D8-AC18-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: "'Internet Engineering Task Force'" <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: 13 Root Server Limitation
Date: Tue, 18 May 2004 00:03:53 +0200
To: Dean Anderson <dean@av8.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 17-mei-04, at 22:51, Dean Anderson wrote:

> Moral: Just because you
> can operate something, and know _how_ to make changes, doesn't mean you
> know what changes are safe or wise to make.

Hm, maybe we should get some of the people who wrote the most popular 
DNS software to run some root servers?


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


From exim@www1.ietf.org  Mon May 17 19:00:08 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11508
	for <ietf-archive@odin.ietf.org>; Mon, 17 May 2004 19:00: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 1BPqkU-0008Lw-SB
	for ietf-archive@odin.ietf.org; Mon, 17 May 2004 18:38:18 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4HMcIa8031884
	for ietf-archive@odin.ietf.org; Mon, 17 May 2004 18:38:18 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPqcY-0004Sg-6h; Mon, 17 May 2004 18:30:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPqEk-0006Jn-75
	for ietf@optimus.ietf.org; Mon, 17 May 2004 18:05: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 SAA06814
	for <ietf@ietf.org>; Mon, 17 May 2004 18:05: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 1BPqEh-0005qv-9P
	for ietf@ietf.org; Mon, 17 May 2004 18:05:27 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPqDr-0005WS-00
	for ietf@ietf.org; Mon, 17 May 2004 18:04:35 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPqDG-0005BT-00
	for ietf@ietf.org; Mon, 17 May 2004 18:03:58 -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 i4HM3c1C057288;
	Tue, 18 May 2004 00:03:38 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <Pine.LNX.4.44.0405171631140.25950-100000@cirrus.av8.net>
References: <Pine.LNX.4.44.0405171631140.25950-100000@cirrus.av8.net>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <15ECE4EE-A84E-11D8-AC18-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: "'Internet Engineering Task Force'" <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: 13 Root Server Limitation
Date: Tue, 18 May 2004 00:03:53 +0200
To: Dean Anderson <dean@av8.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 17-mei-04, at 22:51, Dean Anderson wrote:

> Moral: Just because you
> can operate something, and know _how_ to make changes, doesn't mean you
> know what changes are safe or wise to make.

Hm, maybe we should get some of the people who wrote the most popular 
DNS software to run some root servers?


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



From ietf-admin@ietf.org  Mon May 17 19:37: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 TAA13306
	for <ietf-archive@ietf.org>; Mon, 17 May 2004 19:37: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 1BPrfp-0007T9-Pn
	for ietf-archive@ietf.org; Mon, 17 May 2004 19:37:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPrek-00075A-00
	for ietf-archive@ietf.org; Mon, 17 May 2004 19:36:27 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPrdq-0006jx-00
	for ietf-archive@ietf.org; Mon, 17 May 2004 19:35:30 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPrVd-0006ow-LJ; Mon, 17 May 2004 19:27:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPrNU-0002tr-Qz
	for ietf@optimus.ietf.org; Mon, 17 May 2004 19:18: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 TAA12346
	for <ietf@ietf.org>; Mon, 17 May 2004 19: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 1BPrNT-0000eR-25
	for ietf@ietf.org; Mon, 17 May 2004 19:18:35 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPrMh-0000K0-00
	for ietf@ietf.org; Mon, 17 May 2004 19:17:47 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPrM0-0007mU-00
	for ietf@ietf.org; Mon, 17 May 2004 19:17:04 -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 i4HNGWmE029751
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 17 May 2004 19:16:32 -0400
Date: Mon, 17 May 2004 19:16:32 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Iljitsch van Beijnum <iljitsch@muada.com>
cc: "'Internet Engineering Task Force'" <ietf@ietf.org>
Subject: Re: 13 Root Server Limitation
In-Reply-To: <F8350588-A84B-11D8-AC18-000A95CD987A@muada.com>
Message-ID: <Pine.LNX.4.44.0405171856070.22879-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, 17 May 2004, Iljitsch van Beijnum wrote:

> On 17-mei-04, at 19:36, Dean Anderson wrote:
> 
> > It is conceptually very simple:  Setup 2 anycast servers (S1 and S2)
> > on several paths (AS-A and AS-Y, different AS numbers)  Have an ISP
> > connect to both of those paths, and then have that ISP do fine grained
> > load balancing to prefixes available over those paths. Packets will go
> > to each anycast server.  This will not cause a problem with UDP, since
> > the entire connection transaction is in one packet. But TCP will have
> > a minumim of 3 packets.  2 packets will go to server S1, and one
> > packet will go to server S2.  Neither S1 nor S2 will have a complete
> > TCP connection, and so both will fail.
> 
> As I've said before, this isn't how things work in practice, as actual 
> load sharing towards a destination over two different AS paths doesn't 
> happen, and when load sharing is done, it's almost always in a way that 
> keeps packets belonging to a single TCP session together. (You really 
> don't want to see what happens to TCP performance with 100% out of 
> order packets.)

You are describing Cisco load balancing. The cisco behavior is due to the
effects of its route cache, which uses cache flow data to keep flows
together (but only when cef is turned on). This is not a feature of its
BGP handling, but a "feature" of its packet routing engine. Cisco is not
the only router vendor, and certainly not the only one interested in
fine-grained load balancing.  Most people interested in load balancing
consider this cisco behavior undesirable, and leaving a lot to be desired.

Also, as long as the out-of-sequence packets arrive within the window
frame, there is no degradation in performance (this is one benefit of
segment windows), even if they are 100% non-sequential. I think you are
referring to some pathological out of order cases: If the frame were to
get full before the next-up packet were received (ie complete reverse
order), then there would be a problem. But just because every *pair* or so
of packets arrives out of order doesn't mean there will be any degradation
in performance. That would still be 100% out of order, but not
pathologically so.

> And even if this happened it would very likely be non-fatal, as at some 
> point retransmissions will make it trough so the TCP session works. As 
> most data is going from the server to the client, and ACKs work 
> cumulative, the performance hit is probably not too catastrophic.

Possibly.  Or you might just get a RST from the other server. I think
retransmissions just makes the problem intermittent, and slow, and consume
more connection resources on the nameserver(s). 



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


From exim@www1.ietf.org  Mon May 17 19:39:42 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13601
	for <ietf-archive@odin.ietf.org>; Mon, 17 May 2004 19:39: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 1BPrdr-0001EA-73
	for ietf-archive@odin.ietf.org; Mon, 17 May 2004 19:35:31 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4HNZVEF004708
	for ietf-archive@odin.ietf.org; Mon, 17 May 2004 19:35:31 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPrVd-0006ow-LJ; Mon, 17 May 2004 19:27:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPrNU-0002tr-Qz
	for ietf@optimus.ietf.org; Mon, 17 May 2004 19:18: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 TAA12346
	for <ietf@ietf.org>; Mon, 17 May 2004 19: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 1BPrNT-0000eR-25
	for ietf@ietf.org; Mon, 17 May 2004 19:18:35 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPrMh-0000K0-00
	for ietf@ietf.org; Mon, 17 May 2004 19:17:47 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPrM0-0007mU-00
	for ietf@ietf.org; Mon, 17 May 2004 19:17:04 -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 i4HNGWmE029751
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 17 May 2004 19:16:32 -0400
Date: Mon, 17 May 2004 19:16:32 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Iljitsch van Beijnum <iljitsch@muada.com>
cc: "'Internet Engineering Task Force'" <ietf@ietf.org>
Subject: Re: 13 Root Server Limitation
In-Reply-To: <F8350588-A84B-11D8-AC18-000A95CD987A@muada.com>
Message-ID: <Pine.LNX.4.44.0405171856070.22879-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, 17 May 2004, Iljitsch van Beijnum wrote:

> On 17-mei-04, at 19:36, Dean Anderson wrote:
> 
> > It is conceptually very simple:  Setup 2 anycast servers (S1 and S2)
> > on several paths (AS-A and AS-Y, different AS numbers)  Have an ISP
> > connect to both of those paths, and then have that ISP do fine grained
> > load balancing to prefixes available over those paths. Packets will go
> > to each anycast server.  This will not cause a problem with UDP, since
> > the entire connection transaction is in one packet. But TCP will have
> > a minumim of 3 packets.  2 packets will go to server S1, and one
> > packet will go to server S2.  Neither S1 nor S2 will have a complete
> > TCP connection, and so both will fail.
> 
> As I've said before, this isn't how things work in practice, as actual 
> load sharing towards a destination over two different AS paths doesn't 
> happen, and when load sharing is done, it's almost always in a way that 
> keeps packets belonging to a single TCP session together. (You really 
> don't want to see what happens to TCP performance with 100% out of 
> order packets.)

You are describing Cisco load balancing. The cisco behavior is due to the
effects of its route cache, which uses cache flow data to keep flows
together (but only when cef is turned on). This is not a feature of its
BGP handling, but a "feature" of its packet routing engine. Cisco is not
the only router vendor, and certainly not the only one interested in
fine-grained load balancing.  Most people interested in load balancing
consider this cisco behavior undesirable, and leaving a lot to be desired.

Also, as long as the out-of-sequence packets arrive within the window
frame, there is no degradation in performance (this is one benefit of
segment windows), even if they are 100% non-sequential. I think you are
referring to some pathological out of order cases: If the frame were to
get full before the next-up packet were received (ie complete reverse
order), then there would be a problem. But just because every *pair* or so
of packets arrives out of order doesn't mean there will be any degradation
in performance. That would still be 100% out of order, but not
pathologically so.

> And even if this happened it would very likely be non-fatal, as at some 
> point retransmissions will make it trough so the TCP session works. As 
> most data is going from the server to the client, and ACKs work 
> cumulative, the performance hit is probably not too catastrophic.

Possibly.  Or you might just get a RST from the other server. I think
retransmissions just makes the problem intermittent, and slow, and consume
more connection resources on the nameserver(s). 



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



From ietf-admin@ietf.org  Mon May 17 20:02:33 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15352
	for <ietf-archive@ietf.org>; Mon, 17 May 2004 20:02: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 1BPs40-0000m3-RX
	for ietf-archive@ietf.org; Mon, 17 May 2004 20:02:32 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPs33-0000Nj-00
	for ietf-archive@ietf.org; Mon, 17 May 2004 20:01:33 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPs2D-0007nC-00
	for ietf-archive@ietf.org; Mon, 17 May 2004 20:00:41 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPrts-0007bo-FF; Mon, 17 May 2004 19:52:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPrpS-0005j5-KN
	for ietf@optimus.ietf.org; Mon, 17 May 2004 19:47: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 TAA13956
	for <ietf@ietf.org>; Mon, 17 May 2004 19:47: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 1BPrpQ-0003Fs-Pp
	for ietf@ietf.org; Mon, 17 May 2004 19:47:28 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BProW-0002tE-00
	for ietf@ietf.org; Mon, 17 May 2004 19:46:32 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPrnY-0002Bi-00
	for ietf@ietf.org; Mon, 17 May 2004 19:45:32 -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 i4HNj26e030281
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 17 May 2004 19:45:02 -0400
Date: Mon, 17 May 2004 19:45:02 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Iljitsch van Beijnum <iljitsch@muada.com>
cc: "'Internet Engineering Task Force'" <ietf@ietf.org>
Subject: Re: 13 Root Server Limitation
In-Reply-To: <15ECE4EE-A84E-11D8-AC18-000A95CD987A@muada.com>
Message-ID: <Pine.LNX.4.44.0405171917060.22879-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, 18 May 2004, Iljitsch van Beijnum wrote:

> On 17-mei-04, at 22:51, Dean Anderson wrote:
> 
> > Moral: Just because you can operate something, and know _how_ to make
> > changes, doesn't mean you know what changes are safe or wise to make.
> 
> Hm, maybe we should get some of the people who wrote the most popular 
> DNS software to run some root servers?

Hmm. Good suggestion.  But maybe first we should find some small group of
people that can write software that *complies* with DNS standards, (as
this tends to suggest that they understand the standards) and not go off
implementing rash, unnecessary, and gratuitous variations (ie BIND 9 AXFR,
IXFR non-compliance), and then try to have the protocol documents
gratuitously changed to make their implemenation conformant and make a
number of other implementations non-conformant, but only long after
they've released the non-compliant software into production and written
books describing their non-compliant software as though it were standards
compliant.  Second, while Bind is the most popular nameserver, it has
spurred the most efforts at reimplementation. I can think of very few
other projects that so many people desperately need, but don't want to be
a part of.  I was also part of the namedroppers list back in the late
80's/early 90's, and contributed Bind patches back then, but found it so
difficult to work with that I didn't want to bother for 10 years. Now, I 
can't avoid it.

Also, that group (if we are thinking of the same group) of people didn't
actually _write_ the software, they are just maintaining it, and have made
some modifications to it, and have applied modifications made by others,
and have even made modifications to the protocol after discussing those
modifications with many others.  But along the way they've added a great
deal of security vulnerabilities, too.  It is not that I mean to say they
are stupid, but that their unilateral judgement can't be trusted.

So, how to tell the operators from the engineers, and how to tell the
engineers from the maintenance engineers.  How to keep the bad judgements
of one person or a small group of people from affecting the whole world
internet?? Tough one, I admit.  Could posing questions to a protocol list
at sensible junctures suffice? Say, junctures where proposed operational
modifications affecting the protocols are discussed and vetted first?  
Nah.  That's asking too much.

But seriously, their attitude of "they know better than others" is their
first (but not only) mistake. 

So, I'm also just wondering, where was this operational change discussed
before it was implemented? Anywhere? Because the first I heard of it was
November '02.

		--Dean


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


From exim@www1.ietf.org  Mon May 17 20:18:01 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15892
	for <ietf-archive@odin.ietf.org>; Mon, 17 May 2004 20:18: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 1BPs2E-0000yG-GS
	for ietf-archive@odin.ietf.org; Mon, 17 May 2004 20:00:42 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4I00gFj003730
	for ietf-archive@odin.ietf.org; Mon, 17 May 2004 20:00:42 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPrts-0007bo-FF; Mon, 17 May 2004 19:52:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPrpS-0005j5-KN
	for ietf@optimus.ietf.org; Mon, 17 May 2004 19:47: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 TAA13956
	for <ietf@ietf.org>; Mon, 17 May 2004 19:47: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 1BPrpQ-0003Fs-Pp
	for ietf@ietf.org; Mon, 17 May 2004 19:47:28 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BProW-0002tE-00
	for ietf@ietf.org; Mon, 17 May 2004 19:46:32 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPrnY-0002Bi-00
	for ietf@ietf.org; Mon, 17 May 2004 19:45:32 -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 i4HNj26e030281
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 17 May 2004 19:45:02 -0400
Date: Mon, 17 May 2004 19:45:02 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Iljitsch van Beijnum <iljitsch@muada.com>
cc: "'Internet Engineering Task Force'" <ietf@ietf.org>
Subject: Re: 13 Root Server Limitation
In-Reply-To: <15ECE4EE-A84E-11D8-AC18-000A95CD987A@muada.com>
Message-ID: <Pine.LNX.4.44.0405171917060.22879-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, 18 May 2004, Iljitsch van Beijnum wrote:

> On 17-mei-04, at 22:51, Dean Anderson wrote:
> 
> > Moral: Just because you can operate something, and know _how_ to make
> > changes, doesn't mean you know what changes are safe or wise to make.
> 
> Hm, maybe we should get some of the people who wrote the most popular 
> DNS software to run some root servers?

Hmm. Good suggestion.  But maybe first we should find some small group of
people that can write software that *complies* with DNS standards, (as
this tends to suggest that they understand the standards) and not go off
implementing rash, unnecessary, and gratuitous variations (ie BIND 9 AXFR,
IXFR non-compliance), and then try to have the protocol documents
gratuitously changed to make their implemenation conformant and make a
number of other implementations non-conformant, but only long after
they've released the non-compliant software into production and written
books describing their non-compliant software as though it were standards
compliant.  Second, while Bind is the most popular nameserver, it has
spurred the most efforts at reimplementation. I can think of very few
other projects that so many people desperately need, but don't want to be
a part of.  I was also part of the namedroppers list back in the late
80's/early 90's, and contributed Bind patches back then, but found it so
difficult to work with that I didn't want to bother for 10 years. Now, I 
can't avoid it.

Also, that group (if we are thinking of the same group) of people didn't
actually _write_ the software, they are just maintaining it, and have made
some modifications to it, and have applied modifications made by others,
and have even made modifications to the protocol after discussing those
modifications with many others.  But along the way they've added a great
deal of security vulnerabilities, too.  It is not that I mean to say they
are stupid, but that their unilateral judgement can't be trusted.

So, how to tell the operators from the engineers, and how to tell the
engineers from the maintenance engineers.  How to keep the bad judgements
of one person or a small group of people from affecting the whole world
internet?? Tough one, I admit.  Could posing questions to a protocol list
at sensible junctures suffice? Say, junctures where proposed operational
modifications affecting the protocols are discussed and vetted first?  
Nah.  That's asking too much.

But seriously, their attitude of "they know better than others" is their
first (but not only) mistake. 

So, I'm also just wondering, where was this operational change discussed
before it was implemented? Anywhere? Because the first I heard of it was
November '02.

		--Dean


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



From ietf-admin@ietf.org  Mon May 17 21:37:31 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20159
	for <ietf-archive@ietf.org>; Mon, 17 May 2004 21:37: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 1BPtXv-0004VP-NX
	for ietf-archive@ietf.org; Mon, 17 May 2004 21:37:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPtWy-00046n-00
	for ietf-archive@ietf.org; Mon, 17 May 2004 21:36:33 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPtVz-0003i7-00
	for ietf-archive@ietf.org; Mon, 17 May 2004 21:35:31 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPtRf-0000Rj-KR; Mon, 17 May 2004 21:31:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPt9j-0003bL-NM
	for ietf@optimus.ietf.org; Mon, 17 May 2004 21:12: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 VAA18995
	for <ietf@ietf.org>; Mon, 17 May 2004 21:12:29 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPt9h-0002xH-4V
	for ietf@ietf.org; Mon, 17 May 2004 21:12:29 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPt8i-0002aB-00
	for ietf@ietf.org; Mon, 17 May 2004 21:11:28 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPt7c-0001pN-00
	for ietf@ietf.org; Mon, 17 May 2004 21:10:20 -0400
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) id i4I18tX00714;
	Mon, 17 May 2004 18:08:55 -0700 (PDT)
From: Bill Manning <bmanning@ISI.EDU>
Message-Id: <200405180108.i4I18tX00714@boreas.isi.edu>
Subject: Re: Root Anycast
To: iljitsch@muada.com (Iljitsch van Beijnum)
Date: Mon, 17 May 2004 18:08:55 -0700 (PDT)
Cc: ietf@ietf.org ('Internet Engineering Task Force'),
        bmanning@ISI.EDU (Bill Manning)
In-Reply-To: <DFC3BD05-A84A-11D8-AC18-000A95CD987A@muada.com> from "Iljitsch van Beijnum" at May 17, 2004 11:40:54 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

% 
% On 17-mei-04, at 17:41, Bill Manning wrote:
% 
% > % But as long as we're dissing anycast root DNS servers: how many of 
% > the
% > % root servers are being anycast now or in the future, and how many
% > % won't?
% 
% > 	http://www.rssac.org/
% 
% > 	check the 17th & 18th meeting minutes.
% 
% Result:
% 
% Unicast: A, E, H, L
% Anycast: B, C, D, F, G, I, J, K, M (now or planned)

	And in this brave new world, anycast may not equal anycast... :)
	Consider VRRP.  Is that anycast?  If not, why not?
	Any instance of localised load-balancing. Is it anycast?
	What are the distinctions btwn local/remote loadbalancing?

	None (to my knowledge) of the roots have a consistant view of
	a shared anycast vision, so you should not read too much into
	the summaries found in the RSSAC notes.
	
% The thing that worries me is that apparently, there is no policy about 
% this whatsoever, the root operators each get to decide what they want 
% to do. The fact that .org is run using only two anycast addresses also 
% indicates that apparently the ICANN doesn't feel the need to throw 
% their weight around in this area.

	ICANN has no say in the matter, with the exception of "L".
	There is nothing binding the root operators to a single policy
	with regard to deployment.  But thanks for noticing. :)

% It seems to me that any design that makes the root addresses seem as 
% distributed around the net as possible would be optimal, as in this 
% case the changes of an outage triggering rerouting of a large number of 
% root addresses is as small as possible. In order to do this, the number 
% of root addresses that are available within a geographic region (where 
% "region" < RIR region) should be limited.

	Er... geography != network topology.

--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  Mon May 17 21:41:06 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20418
	for <ietf-archive@odin.ietf.org>; Mon, 17 May 2004 21:41: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 1BPtW0-00024M-QM
	for ietf-archive@odin.ietf.org; Mon, 17 May 2004 21:35:32 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4I1ZWgO007955
	for ietf-archive@odin.ietf.org; Mon, 17 May 2004 21:35:32 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPtRf-0000Rj-KR; Mon, 17 May 2004 21:31:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPt9j-0003bL-NM
	for ietf@optimus.ietf.org; Mon, 17 May 2004 21:12: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 VAA18995
	for <ietf@ietf.org>; Mon, 17 May 2004 21:12:29 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPt9h-0002xH-4V
	for ietf@ietf.org; Mon, 17 May 2004 21:12:29 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPt8i-0002aB-00
	for ietf@ietf.org; Mon, 17 May 2004 21:11:28 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPt7c-0001pN-00
	for ietf@ietf.org; Mon, 17 May 2004 21:10:20 -0400
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) id i4I18tX00714;
	Mon, 17 May 2004 18:08:55 -0700 (PDT)
From: Bill Manning <bmanning@ISI.EDU>
Message-Id: <200405180108.i4I18tX00714@boreas.isi.edu>
Subject: Re: Root Anycast
To: iljitsch@muada.com (Iljitsch van Beijnum)
Date: Mon, 17 May 2004 18:08:55 -0700 (PDT)
Cc: ietf@ietf.org ('Internet Engineering Task Force'),
        bmanning@ISI.EDU (Bill Manning)
In-Reply-To: <DFC3BD05-A84A-11D8-AC18-000A95CD987A@muada.com> from "Iljitsch van Beijnum" at May 17, 2004 11:40:54 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

% 
% On 17-mei-04, at 17:41, Bill Manning wrote:
% 
% > % But as long as we're dissing anycast root DNS servers: how many of 
% > the
% > % root servers are being anycast now or in the future, and how many
% > % won't?
% 
% > 	http://www.rssac.org/
% 
% > 	check the 17th & 18th meeting minutes.
% 
% Result:
% 
% Unicast: A, E, H, L
% Anycast: B, C, D, F, G, I, J, K, M (now or planned)

	And in this brave new world, anycast may not equal anycast... :)
	Consider VRRP.  Is that anycast?  If not, why not?
	Any instance of localised load-balancing. Is it anycast?
	What are the distinctions btwn local/remote loadbalancing?

	None (to my knowledge) of the roots have a consistant view of
	a shared anycast vision, so you should not read too much into
	the summaries found in the RSSAC notes.
	
% The thing that worries me is that apparently, there is no policy about 
% this whatsoever, the root operators each get to decide what they want 
% to do. The fact that .org is run using only two anycast addresses also 
% indicates that apparently the ICANN doesn't feel the need to throw 
% their weight around in this area.

	ICANN has no say in the matter, with the exception of "L".
	There is nothing binding the root operators to a single policy
	with regard to deployment.  But thanks for noticing. :)

% It seems to me that any design that makes the root addresses seem as 
% distributed around the net as possible would be optimal, as in this 
% case the changes of an outage triggering rerouting of a large number of 
% root addresses is as small as possible. In order to do this, the number 
% of root addresses that are available within a geographic region (where 
% "region" < RIR region) should be limited.

	Er... geography != network topology.

--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  Tue May 18 02:21:01 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA16853
	for <ietf-archive@ietf.org>; Tue, 18 May 2004 02:21:01 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPxyF-0001GO-TE
	for ietf-archive@ietf.org; Tue, 18 May 2004 02:21:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPxxE-0000rE-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 02:19:56 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPxwU-0000Sq-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 02:19:10 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPxod-00076z-Gm; Tue, 18 May 2004 02:11:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPxhk-0002vz-Cx
	for ietf@optimus.ietf.org; Tue, 18 May 2004 02:03: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 CAA06850
	for <ietf@ietf.org>; Tue, 18 May 2004 02:03: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 1BPxhf-0002UA-ET
	for ietf@ietf.org; Tue, 18 May 2004 02:03:51 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPxgm-00027G-00
	for ietf@ietf.org; Tue, 18 May 2004 02:02:56 -0400
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPxg2-0001hr-00
	for ietf@ietf.org; Tue, 18 May 2004 02:02:10 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i4I61fJ16920
	for <ietf@ietf.org>; Tue, 18 May 2004 09:01:41 +0300
Date: Tue, 18 May 2004 09:01:41 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: ietf@ietf.org
Subject: Re: 60th IETF - Registration
In-Reply-To: <200405171936.PAA18695@ietf.org>
Message-ID: <Pine.LNX.4.44.0405180900090.16893-100000@netcore.fi>
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

Hi,

The registration says the hotel is already full.  Is this for real --
900 rooms already taken, within 11 hours??

(Or is the reservation system just broken like in many other times..)

On Mon, 17 May 2004 ietf-registrar@ietf.org wrote:
> 60th IETF Meeting
> August 1-6, 2004
> San Diego, CA
> 
> Registration for the 60th IETF Meeting is now open.
> 
> You can register on line at: 
> http://www.ietf.org/meetings/IETF-60.html 
> 
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf-announce
> 

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


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


From exim@www1.ietf.org  Tue May 18 02:24:55 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA17338
	for <ietf-archive@odin.ietf.org>; Tue, 18 May 2004 02:24:55 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPxwd-00031l-7s
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 02:19:19 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4I6JJbw011324
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 02:19:19 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPxod-00076z-Gm; Tue, 18 May 2004 02:11:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPxhk-0002vz-Cx
	for ietf@optimus.ietf.org; Tue, 18 May 2004 02:03: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 CAA06850
	for <ietf@ietf.org>; Tue, 18 May 2004 02:03: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 1BPxhf-0002UA-ET
	for ietf@ietf.org; Tue, 18 May 2004 02:03:51 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPxgm-00027G-00
	for ietf@ietf.org; Tue, 18 May 2004 02:02:56 -0400
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPxg2-0001hr-00
	for ietf@ietf.org; Tue, 18 May 2004 02:02:10 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i4I61fJ16920
	for <ietf@ietf.org>; Tue, 18 May 2004 09:01:41 +0300
Date: Tue, 18 May 2004 09:01:41 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: ietf@ietf.org
Subject: Re: 60th IETF - Registration
In-Reply-To: <200405171936.PAA18695@ietf.org>
Message-ID: <Pine.LNX.4.44.0405180900090.16893-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: 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,

The registration says the hotel is already full.  Is this for real --
900 rooms already taken, within 11 hours??

(Or is the reservation system just broken like in many other times..)

On Mon, 17 May 2004 ietf-registrar@ietf.org wrote:
> 60th IETF Meeting
> August 1-6, 2004
> San Diego, CA
> 
> Registration for the 60th IETF Meeting is now open.
> 
> You can register on line at: 
> http://www.ietf.org/meetings/IETF-60.html 
> 
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf-announce
> 

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


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



From ietf-admin@ietf.org  Tue May 18 03:00: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 DAA19113
	for <ietf-archive@ietf.org>; Tue, 18 May 2004 03:00: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 1BPyat-0001VK-5Z
	for ietf-archive@ietf.org; Tue, 18 May 2004 03:00:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPyZq-00015G-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 02:59:50 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPyYl-0000fd-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 02:58:43 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPyLh-0002sp-Lv; Tue, 18 May 2004 02:45:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPyFS-0000xn-1O
	for ietf@optimus.ietf.org; Tue, 18 May 2004 02:38: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 CAA18212
	for <ietf@ietf.org>; Tue, 18 May 2004 02:38: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 1BPyFO-0000jt-7I
	for ietf@ietf.org; Tue, 18 May 2004 02:38:42 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPyEQ-0000Mv-00
	for ietf@ietf.org; Tue, 18 May 2004 02:37:43 -0400
Received: from gw.dittler.org ([217.160.132.152] helo=linux.dittler.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPyDQ-0007cn-00
	for ietf@ietf.org; Tue, 18 May 2004 02:36:40 -0400
Received: from pcpeter (p54808714.dip.t-dialin.net [84.128.135.20])
	(authenticated bits=0)
	by linux.dittler.org (8.12.6/8.12.6) with ESMTP id i4I6aYY1012680;
	Tue, 18 May 2004 08:36:35 +0200
From: "Hans Peter Dittler" <dittler@braintec-consult.de>
To: "'Pekka Savola'" <pekkas@netcore.fi>, <ietf@ietf.org>
Subject: AW: 60th IETF - Registration
Date: Tue, 18 May 2004 08:32:44 +0200
Organization: BRAINTEC
Message-ID: <DC55E4CF3BF32E46B6F1FA9028E35667626A@w3k.win3k.braintec-consult.de>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
In-Reply-To: <DC55E4CF3BF32E46B6F1FA9028E35667095D5F@w3k.win3k.braintec-consult.de>
Importance: Normal
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=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Hi,

>The registration says the hotel is already full.  Is this for real --
900 rooms already taken, within 11 hours??

no - there are rooms of all three kinds available if you call the
reservation-desk directly.
(Phone: 1-619-291-2900 or 1-877-734-2726)

I just got my confirmation mail back from San Diego (8:23 MEZ = 23:23 in
San Diego)

Peter


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


From ietf-admin@ietf.org  Tue May 18 08:33: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 IAA09701
	for <ietf-archive@ietf.org>; Tue, 18 May 2004 08:33: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 1BQ3mQ-0004Xp-Eb
	for ietf-archive@ietf.org; Tue, 18 May 2004 08:33:10 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ3l4-0003iB-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 08:31:47 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ3jv-0003EI-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 08:30:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ3P3-0007iR-61; Tue, 18 May 2004 08:09:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPrg1-0002aO-UR
	for ietf@optimus.ietf.org; Mon, 17 May 2004 19:37: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 TAA13337
	for <ietf@ietf.org>; Mon, 17 May 2004 19:37: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 1BPrg0-0007U6-47
	for ietf@ietf.org; Mon, 17 May 2004 19:37:44 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPreq-00075w-00
	for ietf@ietf.org; Mon, 17 May 2004 19:36:33 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPre2-0006Pb-00
	for ietf@ietf.org; Mon, 17 May 2004 19:35:42 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id 1CC4013CDE; Mon, 17 May 2004 23:35:08 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: [dnsop] Re: Complaint on abuse of DNSOP lists
References: <C6111F54-A81D-11D8-8726-000A95928574@kurtis.pp.se>
	<Pine.LNX.4.44.0405171600540.25950-100000@cirrus.av8.net>
From: Paul Vixie <vixie@vix.com>
Date: 17 May 2004 23:35:08 +0000
In-Reply-To: <Pine.LNX.4.44.0405171600540.25950-100000@cirrus.av8.net>
Message-ID: <g3pt92eifn.fsf@sa.vix.com>
Lines: 7
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
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

dean@av8.com (Dean Anderson) writes:

> ... For the less technical, an exchange point is ...

I don't think there's anyone on this list less technical than you, Dean.
-- 
Paul Vixie

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


From ietf-admin@ietf.org  Tue May 18 08:35: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 IAA09955
	for <ietf-archive@ietf.org>; Tue, 18 May 2004 08:35:10 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQ3oM-0005SK-Ja
	for ietf-archive@ietf.org; Tue, 18 May 2004 08:35:10 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ3n4-0004dp-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 08:33:51 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ3lr-00048z-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 08:32:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ3P4-0007ig-Mj; Tue, 18 May 2004 08:09:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPsKM-00060L-7P
	for ietf@optimus.ietf.org; Mon, 17 May 2004 20:19:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15969
	for <ietf@ietf.org>; Mon, 17 May 2004 20:19:24 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPsKK-0006cu-4s
	for ietf@ietf.org; Mon, 17 May 2004 20:19:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPsJK-0006Gg-00
	for ietf@ietf.org; Mon, 17 May 2004 20:18:23 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPsIJ-0005bo-00
	for ietf@ietf.org; Mon, 17 May 2004 20:17:20 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id B648713DE5; Tue, 18 May 2004 00:16:49 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: Root Anycast
References: <DFC3BD05-A84A-11D8-AC18-000A95CD987A@muada.com>
From: Paul Vixie <vixie@vix.com>
Date: 18 May 2004 00:16:49 +0000
In-Reply-To: <DFC3BD05-A84A-11D8-AC18-000A95CD987A@muada.com>
Message-ID: <g3lljqegi6.fsf@sa.vix.com>
Lines: 84
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
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

iljitsch@muada.com (Iljitsch van Beijnum) writes:

> Unicast: A, E, H, L
> Anycast: B, C, D, F, G, I, J, K, M (now or planned)
> 
> The thing that worries me is that apparently, there is no policy about 
> this whatsoever, the root operators each get to decide what they want 
> to do.

The table is round.  Policies are discussed as a group but set individually.
The result is a service which has never been "down hard", not ever, not for
any millisecond out of the last 15 years.  This is "strength by diversity."

> The fact that .org is run using only two anycast addresses also indicates
> that apparently the ICANN doesn't feel the need to throw their weight
> around in this area.

Apparently you have your facts wrong about how much sway ICANN had about
the anycasting of .ORG, but those details aren't mine, let others speak.

> Now obviously anycasting is a very useful mechanism to reduce latency 
> and increase capacity and robustness. However, these properties are 
> best served by careful design rather than organic growth.

Careful design by whom?  Organic compared to what?  I assure you that f-root
has grown by careful design.  It's only organic in that we go where we're
invited rather than having a gigantic budget that could be used as a leash.

Check out <http://www.isc.org/ops/f-root/> and the list of mirror sites, and
look for some sponsors you know, and call them, and ask why they sponsored
f-root and whether they're happy about it.  Then find someone in that region
and ask them to do "dig @192.5.5.241 hostname.bind chaos txt" and tell you
whether they're talking to a local f-root.  What could scale better, or
allocate resources more efficiently?  (Central planning didn't help USSR.)

> If we consider the number of actual servers/server clusters and the
> number of root IP addresses as given, there are still many ways to skin
> this cat.  One would be using 12 unicast servers and anycast just one
> address.

Who is "we", though?  That's always the excluded middle of this debate.  I
know who I am -- a root operator.  But who are "we"?  And which of the
million different answers to "who are 'we'?" would you like to see govern
the choice of "who gets to decide how this stuff ought to work?"  E.g., I'm
sure, without even having heard it, that you wouldn't want the choice of
"who decides?" governed by Dean Anderson's answer to "who are 'we'?"

> It seems to me that any design that makes the root addresses seem as 
> distributed around the net as possible would be optimal, as in this 
> case the changes of an outage triggering rerouting of a large number of 
> root addresses is as small as possible. In order to do this, the number 
> of root addresses that are available within a geographic region (where 
> "region" < RIR region) should be limited.

In counterpoint, it seems to me that any unified design will make the system
subject to monoculture attacks or ISO-L9 capture, and that the current 
system which you call "unplanned and organic" (but which is actually just
"diversity by credo") yields a stronger system overall.

> (Just having the roots close is of little value: good recursive servers 
> hone in to the one with the lowest RTT anyway, so having one close by 
> is enough. However, when this one fails it's important that after the 
> timeout, the next root address that the recursive server tries is 
> highly likely to be reachable, in order to avoid stacking timeout upon 
> timeout. A couple 100 ms extra round trip delay doesn't mean much in 
> cases where the recursive server suffers a timeout anyway.)

What would help overall DNS robustness would be if more DNS clients used
recursion, and cached what they heard (both positive and negative).  A
frightfully large (and growing) segment of the client population always
walks from the top down (I guess these are worms or viruses or whatever)
and another growing/frightful segment asks the same question hundreds of
times a minute and doesn't seem to care whether the response is positive or
negative, only that it has to arrive so that the (lockstepped) next (same)
query can be sent.

If you'd like to unify something, perhaps it could be DNS client behaviour
and network-owner recursive caching forwarder design.  And while you're at
it, please outlaw those fiendish DNS-based load balancers.  f-root should
still be a 486DX2-66 like it was in ~1995, rather than fifty 1GHz pentiums,
and the 500X load 10 years later is due to client stupidity, not population
growth or backbone speed increases.
-- 
Paul Vixie

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


From exim@www1.ietf.org  Tue May 18 08:36:18 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 IAA10087
	for <ietf-archive@odin.ietf.org>; Tue, 18 May 2004 08:36: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 1BQ3jv-0006z8-R6
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 08:30:36 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4ICUZEJ026836
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 08:30:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ3P3-0007iR-61; Tue, 18 May 2004 08:09:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPrg1-0002aO-UR
	for ietf@optimus.ietf.org; Mon, 17 May 2004 19:37: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 TAA13337
	for <ietf@ietf.org>; Mon, 17 May 2004 19:37: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 1BPrg0-0007U6-47
	for ietf@ietf.org; Mon, 17 May 2004 19:37:44 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPreq-00075w-00
	for ietf@ietf.org; Mon, 17 May 2004 19:36:33 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPre2-0006Pb-00
	for ietf@ietf.org; Mon, 17 May 2004 19:35:42 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id 1CC4013CDE; Mon, 17 May 2004 23:35:08 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: [dnsop] Re: Complaint on abuse of DNSOP lists
References: <C6111F54-A81D-11D8-8726-000A95928574@kurtis.pp.se>
	<Pine.LNX.4.44.0405171600540.25950-100000@cirrus.av8.net>
From: Paul Vixie <vixie@vix.com>
Date: 17 May 2004 23:35:08 +0000
In-Reply-To: <Pine.LNX.4.44.0405171600540.25950-100000@cirrus.av8.net>
Message-ID: <g3pt92eifn.fsf@sa.vix.com>
Lines: 7
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: 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>

dean@av8.com (Dean Anderson) writes:

> ... For the less technical, an exchange point is ...

I don't think there's anyone on this list less technical than you, Dean.
-- 
Paul Vixie

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



From exim@www1.ietf.org  Tue May 18 08:36:45 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 IAA10132
	for <ietf-archive@odin.ietf.org>; Tue, 18 May 2004 08:36: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 1BQ3nL-0000SC-Jk
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 08:34:07 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4ICY7mK001736
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 08:34:07 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ3P5-0007is-UD; Tue, 18 May 2004 08:09:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ0KD-0008L8-Vd
	for ietf@optimus.ietf.org; Tue, 18 May 2004 04:51: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 EAA25564
	for <ietf@ietf.org>; Tue, 18 May 2004 04:51: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 1BQ0KA-0006hT-Sa
	for ietf@ietf.org; Tue, 18 May 2004 04:51:46 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ0JD-000669-00
	for ietf@ietf.org; Tue, 18 May 2004 04:50:47 -0400
Received: from smail.alcatel.fr ([62.23.212.165])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ0Hy-0005PL-00
	for ietf@ietf.org; Tue, 18 May 2004 04:49:30 -0400
Received: from bemail05.netfr.alcatel.fr (bemail05.netfr.alcatel.fr [155.132.251.11])
	by smail.alcatel.fr (ALCANET/NETFR) with ESMTP id i4I8nQ2S002346;
	Tue, 18 May 2004 10:49:26 +0200
Received: from alcatel.be ([138.203.118.2])
          by bemail05.netfr.alcatel.fr (Lotus Domino Release 5.0.11)
          with ESMTP id 2004051810492561:2030 ;
          Tue, 18 May 2004 10:49:25 +0200 
Message-ID: <40A9CE79.9060202@alcatel.be>
Date: Tue, 18 May 2004 10:51:05 +0200
From: Dimitri.Papadimitriou@alcatel.be
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.5) Gecko/20030925
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Pekka Savola <pekkas@netcore.fi>
CC: ietf@ietf.org
Subject: Re: 60th IETF - Registration
References: <Pine.LNX.4.44.0405180900090.16893-100000@netcore.fi>
In-Reply-To: <Pine.LNX.4.44.0405180900090.16893-100000@netcore.fi>
X-MIMETrack: Itemize by SMTP Server on BEMAIL05/BE/ALCATEL(Release 5.0.11  |July 24, 2002) at
 05/18/2004 10:49:25,
	Serialize by Router on BEMAIL05/BE/ALCATEL(Release 5.0.11  |July 24, 2002) at
 05/18/2004 10:49:26,
	Serialize complete at 05/18/2004 10:49:26
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii; format=flowed
X-Alcanet-MTA-scanned-and-authorized: yes
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,CLICK_BELOW,NO_REAL_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

hi, i've the same problem (from last night around 12:00PM GMT+1), and if 
you click on the "book now" link just below the picture, it says:

"We're Sorry	
		
	
But your chosen hotel cannot currently be reserved online. However, you 
can still book a room at this hotel by calling 888-625-5144 in the U.S. 
or Canada. Residents of all other countries, please see our Worldwide 
Reservations Offices.

Thank you. We apologize for any inconvenience."

Pekka Savola wrote:

> Hi,
> 
> The registration says the hotel is already full.  Is this for real --
> 900 rooms already taken, within 11 hours??
> 
> (Or is the reservation system just broken like in many other times..)
> 
> On Mon, 17 May 2004 ietf-registrar@ietf.org wrote:
> 
>>60th IETF Meeting
>>August 1-6, 2004
>>San Diego, CA
>>
>>Registration for the 60th IETF Meeting is now open.
>>
>>You can register on line at: 
>>http://www.ietf.org/meetings/IETF-60.html 
>>
>>_______________________________________________
>>IETF-Announce mailing list
>>IETF-Announce@ietf.org
>>https://www1.ietf.org/mailman/listinfo/ietf-announce
>>
> 
> 

-- 
Papadimitriou Dimitri
E-mail : dimitri.papadimitriou@alcatel.be
E-mail : dpapadimitriou@psg.com
Webpage: http://psg.com/~dpapadimitriou/
Address: Fr. Wellesplein 1, B-2018 Antwerpen, Belgium
Phone  : +32 3 240-8491


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



From ietf-admin@ietf.org  Tue May 18 08:36:49 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10156
	for <ietf-archive@ietf.org>; Tue, 18 May 2004 08:36:49 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQ3px-00061z-Lf
	for ietf-archive@ietf.org; Tue, 18 May 2004 08:36:49 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ3oZ-0005UQ-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 08:35:24 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ3nL-0004zm-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 08:34:07 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ3P5-0007is-UD; Tue, 18 May 2004 08:09:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ0KD-0008L8-Vd
	for ietf@optimus.ietf.org; Tue, 18 May 2004 04:51: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 EAA25564
	for <ietf@ietf.org>; Tue, 18 May 2004 04:51: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 1BQ0KA-0006hT-Sa
	for ietf@ietf.org; Tue, 18 May 2004 04:51:46 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ0JD-000669-00
	for ietf@ietf.org; Tue, 18 May 2004 04:50:47 -0400
Received: from smail.alcatel.fr ([62.23.212.165])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ0Hy-0005PL-00
	for ietf@ietf.org; Tue, 18 May 2004 04:49:30 -0400
Received: from bemail05.netfr.alcatel.fr (bemail05.netfr.alcatel.fr [155.132.251.11])
	by smail.alcatel.fr (ALCANET/NETFR) with ESMTP id i4I8nQ2S002346;
	Tue, 18 May 2004 10:49:26 +0200
Received: from alcatel.be ([138.203.118.2])
          by bemail05.netfr.alcatel.fr (Lotus Domino Release 5.0.11)
          with ESMTP id 2004051810492561:2030 ;
          Tue, 18 May 2004 10:49:25 +0200 
Message-ID: <40A9CE79.9060202@alcatel.be>
Date: Tue, 18 May 2004 10:51:05 +0200
From: Dimitri.Papadimitriou@alcatel.be
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.5) Gecko/20030925
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Pekka Savola <pekkas@netcore.fi>
CC: ietf@ietf.org
Subject: Re: 60th IETF - Registration
References: <Pine.LNX.4.44.0405180900090.16893-100000@netcore.fi>
In-Reply-To: <Pine.LNX.4.44.0405180900090.16893-100000@netcore.fi>
X-MIMETrack: Itemize by SMTP Server on BEMAIL05/BE/ALCATEL(Release 5.0.11  |July 24, 2002) at
 05/18/2004 10:49:25,
	Serialize by Router on BEMAIL05/BE/ALCATEL(Release 5.0.11  |July 24, 2002) at
 05/18/2004 10:49:26,
	Serialize complete at 05/18/2004 10:49:26
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii; format=flowed
X-Alcanet-MTA-scanned-and-authorized: yes
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.4 required=5.0 tests=AWL,CLICK_BELOW,NO_REAL_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

hi, i've the same problem (from last night around 12:00PM GMT+1), and if 
you click on the "book now" link just below the picture, it says:

"We're Sorry	
		
	
But your chosen hotel cannot currently be reserved online. However, you 
can still book a room at this hotel by calling 888-625-5144 in the U.S. 
or Canada. Residents of all other countries, please see our Worldwide 
Reservations Offices.

Thank you. We apologize for any inconvenience."

Pekka Savola wrote:

> Hi,
> 
> The registration says the hotel is already full.  Is this for real --
> 900 rooms already taken, within 11 hours??
> 
> (Or is the reservation system just broken like in many other times..)
> 
> On Mon, 17 May 2004 ietf-registrar@ietf.org wrote:
> 
>>60th IETF Meeting
>>August 1-6, 2004
>>San Diego, CA
>>
>>Registration for the 60th IETF Meeting is now open.
>>
>>You can register on line at: 
>>http://www.ietf.org/meetings/IETF-60.html 
>>
>>_______________________________________________
>>IETF-Announce mailing list
>>IETF-Announce@ietf.org
>>https://www1.ietf.org/mailman/listinfo/ietf-announce
>>
> 
> 

-- 
Papadimitriou Dimitri
E-mail : dimitri.papadimitriou@alcatel.be
E-mail : dpapadimitriou@psg.com
Webpage: http://psg.com/~dpapadimitriou/
Address: Fr. Wellesplein 1, B-2018 Antwerpen, Belgium
Phone  : +32 3 240-8491


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


From ietf-admin@ietf.org  Tue May 18 09:34: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 JAA14057
	for <ietf-archive@ietf.org>; Tue, 18 May 2004 09:34: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 1BQ4jT-0005oG-P4
	for ietf-archive@ietf.org; Tue, 18 May 2004 09:34:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ4iN-0005Pl-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 09:33:04 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ4hU-00050u-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 09:32:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ4Uq-0007KJ-5t; Tue, 18 May 2004 09:19:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ4Cq-0001IJ-5H
	for ietf@optimus.ietf.org; Tue, 18 May 2004 09:00: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 JAA11942
	for <ietf@ietf.org>; Tue, 18 May 2004 09:00: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 1BQ4Co-00009H-Lh
	for ietf@ietf.org; Tue, 18 May 2004 09:00:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ4C7-0007XX-00
	for ietf@ietf.org; Tue, 18 May 2004 08:59:44 -0400
Received: from cust.92.136.adsl.cistron.nl
	([195.64.92.136] helo=purgatory.unfix.org ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ4B9-00075C-00
	for ietf@ietf.org; Tue, 18 May 2004 08:58:43 -0400
Received: from localhost (localhost [127.0.0.1])
	by purgatory.unfix.org (Postfix) with ESMTP
	id E81797FDC; Tue, 18 May 2004 14:58:37 +0200 (CEST)
Received: from purgatory.unfix.org ([127.0.0.1])
	by localhost (purgatory [127.0.0.1]) (amavisd-new, port 10024)
	with SMTP id 18967-85; Tue, 18 May 2004 14:58:26 +0200 (CEST)
Received: from [9.4.70.109] (pat.zurich.ibm.com [195.176.20.45])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by purgatory.unfix.org (Postfix) with ESMTP
	id E6B1B7F67; Tue, 18 May 2004 14:58:25 +0200 (CEST)
Subject: Re: Root Anycast
From: Jeroen Massar <jeroen@unfix.org>
To: Paul Vixie <vixie@vix.com>
Cc: ietf@ietf.org
In-Reply-To: <g3lljqegi6.fsf@sa.vix.com>
References: <DFC3BD05-A84A-11D8-AC18-000A95CD987A@muada.com>
	 <g3lljqegi6.fsf@sa.vix.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-Ckvqp4zeOtAppuuMp+UO"
Organization: Unfix
Message-Id: <1084885097.12869.1407.camel@segesta.zurich.ibm.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.5 (1.4.5-7) 
Date: Tue, 18 May 2004 14:58:17 +0200
X-Virus-Scanned: purgatory.unfix.org - http://unfix.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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60


--=-Ckvqp4zeOtAppuuMp+UO
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Tue, 2004-05-18 at 02:16, Paul Vixie wrote:

<SNIP>

> If you'd like to unify something, perhaps it could be DNS client behaviou=
r
> and network-owner recursive caching forwarder design.  And while you're a=
t
> it, please outlaw those fiendish DNS-based load balancers.  f-root should
> still be a 486DX2-66 like it was in ~1995, rather than fifty 1GHz pentium=
s,
> and the 500X load 10 years later is due to client stupidity, not populati=
on
> growth or backbone speed increases.

Paul, and other rootserveroperators (good scrabble word :), what would
your answer/problem/arguments/... be if an ISP would decide to inject
routes to the root-servers into their local network and point these
request to a local dns cache(s), which would have the correct routes to
the the global rootservers of course.

It is of course kind of hijacking the connectivity what is happening
here. And might this be an idea for a BCP for ISP's?

Or another thought that have been raised recently on the 6bone list:
Would it be an idea to have 2+ independent globaly routable prefixes,
thus in IPv4 2x at least /24 and in IPv6 2x /32 which are allowed to be
anycasted by anyone, just like the 6to4 stuff currently. So that ISP's
could point these prefixes to their local dns caches, similar to the
above but: documented which prefixes those are and no evil hijacking.
This could also allow for DNS-client to have hardcoded addresses of
these caching DNS prefixes lightening the load on the root servers as
with anycast you will always get an answer from the closest one, if all
is well and murphy is on his day off of course ;)

Greets,
 Jeroen


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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iD8DBQBAqghpKaooUjM+fCMRAjChAKCcG8KVVvD1//iAdb+yOKE7E/+LYQCgp3+S
MOmXbNYvUcrsX4ZiwU8krkc=
=qyYm
-----END PGP SIGNATURE-----

--=-Ckvqp4zeOtAppuuMp+UO--


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


From exim@www1.ietf.org  Tue May 18 09:37:36 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 JAA14331
	for <ietf-archive@odin.ietf.org>; Tue, 18 May 2004 09:37: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 1BQ4hU-0003M8-AH
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 09:32:08 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4IDW8dE012900
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 09:32:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ4Uq-0007KJ-5t; Tue, 18 May 2004 09:19:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ4Cq-0001IJ-5H
	for ietf@optimus.ietf.org; Tue, 18 May 2004 09:00: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 JAA11942
	for <ietf@ietf.org>; Tue, 18 May 2004 09:00: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 1BQ4Co-00009H-Lh
	for ietf@ietf.org; Tue, 18 May 2004 09:00:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ4C7-0007XX-00
	for ietf@ietf.org; Tue, 18 May 2004 08:59:44 -0400
Received: from cust.92.136.adsl.cistron.nl
	([195.64.92.136] helo=purgatory.unfix.org ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ4B9-00075C-00
	for ietf@ietf.org; Tue, 18 May 2004 08:58:43 -0400
Received: from localhost (localhost [127.0.0.1])
	by purgatory.unfix.org (Postfix) with ESMTP
	id E81797FDC; Tue, 18 May 2004 14:58:37 +0200 (CEST)
Received: from purgatory.unfix.org ([127.0.0.1])
	by localhost (purgatory [127.0.0.1]) (amavisd-new, port 10024)
	with SMTP id 18967-85; Tue, 18 May 2004 14:58:26 +0200 (CEST)
Received: from [9.4.70.109] (pat.zurich.ibm.com [195.176.20.45])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by purgatory.unfix.org (Postfix) with ESMTP
	id E6B1B7F67; Tue, 18 May 2004 14:58:25 +0200 (CEST)
Subject: Re: Root Anycast
From: Jeroen Massar <jeroen@unfix.org>
To: Paul Vixie <vixie@vix.com>
Cc: ietf@ietf.org
In-Reply-To: <g3lljqegi6.fsf@sa.vix.com>
References: <DFC3BD05-A84A-11D8-AC18-000A95CD987A@muada.com>
	 <g3lljqegi6.fsf@sa.vix.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-Ckvqp4zeOtAppuuMp+UO"
Organization: Unfix
Message-Id: <1084885097.12869.1407.camel@segesta.zurich.ibm.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.5 (1.4.5-7) 
Date: Tue, 18 May 2004 14:58:17 +0200
X-Virus-Scanned: purgatory.unfix.org - http://unfix.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: 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>


--=-Ckvqp4zeOtAppuuMp+UO
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Tue, 2004-05-18 at 02:16, Paul Vixie wrote:

<SNIP>

> If you'd like to unify something, perhaps it could be DNS client behaviou=
r
> and network-owner recursive caching forwarder design.  And while you're a=
t
> it, please outlaw those fiendish DNS-based load balancers.  f-root should
> still be a 486DX2-66 like it was in ~1995, rather than fifty 1GHz pentium=
s,
> and the 500X load 10 years later is due to client stupidity, not populati=
on
> growth or backbone speed increases.

Paul, and other rootserveroperators (good scrabble word :), what would
your answer/problem/arguments/... be if an ISP would decide to inject
routes to the root-servers into their local network and point these
request to a local dns cache(s), which would have the correct routes to
the the global rootservers of course.

It is of course kind of hijacking the connectivity what is happening
here. And might this be an idea for a BCP for ISP's?

Or another thought that have been raised recently on the 6bone list:
Would it be an idea to have 2+ independent globaly routable prefixes,
thus in IPv4 2x at least /24 and in IPv6 2x /32 which are allowed to be
anycasted by anyone, just like the 6to4 stuff currently. So that ISP's
could point these prefixes to their local dns caches, similar to the
above but: documented which prefixes those are and no evil hijacking.
This could also allow for DNS-client to have hardcoded addresses of
these caching DNS prefixes lightening the load on the root servers as
with anycast you will always get an answer from the closest one, if all
is well and murphy is on his day off of course ;)

Greets,
 Jeroen


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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iD8DBQBAqghpKaooUjM+fCMRAjChAKCcG8KVVvD1//iAdb+yOKE7E/+LYQCgp3+S
MOmXbNYvUcrsX4ZiwU8krkc=
=qyYm
-----END PGP SIGNATURE-----

--=-Ckvqp4zeOtAppuuMp+UO--


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



From ietf-admin@ietf.org  Tue May 18 11:42: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 LAA23557
	for <ietf-archive@ietf.org>; Tue, 18 May 2004 11:42: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 1BQ6jY-0002ib-4n
	for ietf-archive@ietf.org; Tue, 18 May 2004 11:42:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ6iU-0002eT-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 11:41:19 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ6hw-0002Zs-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 11:40:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ6Xi-00026P-PD; Tue, 18 May 2004 11: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 1BQ6Jz-0007TF-9D
	for ietf@optimus.ietf.org; Tue, 18 May 2004 11:15:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22272
	for <ietf@ietf.org>; Tue, 18 May 2004 11:15: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 1BQ6Jy-0001OK-EA
	for ietf@ietf.org; Tue, 18 May 2004 11:15:58 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ6J4-0001JB-00
	for ietf@ietf.org; Tue, 18 May 2004 11:15:02 -0400
Received: from mail-dark.research.att.com ([192.20.225.112])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ6I5-0001CL-00
	for ietf@ietf.org; Tue, 18 May 2004 11:14:01 -0400
Received: from mail-green.research.att.com (mail-green.research.att.com [135.207.30.103])
	by mail-dark.research.att.com (Postfix) with ESMTP id D59E7E80EE;
	Tue, 18 May 2004 11:13:30 -0400 (EDT)
Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46])
	by mail-green.research.att.com (Postfix) with ESMTP id 94376F3A90;
	Tue, 18 May 2004 11:13:29 -0400 (EDT)
Received: (from fenner@localhost)
	by windsor.research.att.com (8.11.6+Sun/8.8.5) id i4IFDTc05074;
	Tue, 18 May 2004 11:13:29 -0400 (EDT)
Message-Id: <200405181513.i4IFDTc05074@windsor.research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
To: ehall@ehsco.com
Subject: Re: ftp license
Cc: ietf@ietf.org
Date: Tue, 18 May 2004 11:13:28 -0400
From: Bill Fenner <fenner@research.att.com>
Versions: dmail (solaris) 2.6d/makemail 2.10
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 forwarded this info to ietf-action@ietf.org, and it was fixed (a
license got installed) within 24 hours.

  Bill

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


From exim@www1.ietf.org  Tue May 18 11:45:15 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 LAA23732
	for <ietf-archive@odin.ietf.org>; Tue, 18 May 2004 11:45:15 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ6hx-0005Tq-0a
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 11:40:45 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4IFei2J020933
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 11:40:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ6Xi-00026P-PD; Tue, 18 May 2004 11: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 1BQ6Jz-0007TF-9D
	for ietf@optimus.ietf.org; Tue, 18 May 2004 11:15:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22272
	for <ietf@ietf.org>; Tue, 18 May 2004 11:15: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 1BQ6Jy-0001OK-EA
	for ietf@ietf.org; Tue, 18 May 2004 11:15:58 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ6J4-0001JB-00
	for ietf@ietf.org; Tue, 18 May 2004 11:15:02 -0400
Received: from mail-dark.research.att.com ([192.20.225.112])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ6I5-0001CL-00
	for ietf@ietf.org; Tue, 18 May 2004 11:14:01 -0400
Received: from mail-green.research.att.com (mail-green.research.att.com [135.207.30.103])
	by mail-dark.research.att.com (Postfix) with ESMTP id D59E7E80EE;
	Tue, 18 May 2004 11:13:30 -0400 (EDT)
Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46])
	by mail-green.research.att.com (Postfix) with ESMTP id 94376F3A90;
	Tue, 18 May 2004 11:13:29 -0400 (EDT)
Received: (from fenner@localhost)
	by windsor.research.att.com (8.11.6+Sun/8.8.5) id i4IFDTc05074;
	Tue, 18 May 2004 11:13:29 -0400 (EDT)
Message-Id: <200405181513.i4IFDTc05074@windsor.research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
To: ehall@ehsco.com
Subject: Re: ftp license
Cc: ietf@ietf.org
Date: Tue, 18 May 2004 11:13:28 -0400
From: Bill Fenner <fenner@research.att.com>
Versions: dmail (solaris) 2.6d/makemail 2.10
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=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 forwarded this info to ietf-action@ietf.org, and it was fixed (a
license got installed) within 24 hours.

  Bill

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



From ietf-admin@ietf.org  Tue May 18 13:19: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 NAA28506
	for <ietf-archive@ietf.org>; Tue, 18 May 2004 13:19: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 1BQ8F8-0000eF-L4
	for ietf-archive@ietf.org; Tue, 18 May 2004 13:19:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ8EE-0000Zy-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 13:18:10 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ8Dc-0000WP-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 13:17: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 1BQ8DY-0008Pq-65
	for ietf-archive@ietf.org; Tue, 18 May 2004 13:17:28 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ7zi-00061A-0t; Tue, 18 May 2004 13:03:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ7tq-0004VH-HP
	for ietf@optimus.ietf.org; Tue, 18 May 2004 12:57: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 MAA27244
	for <ietf@ietf.org>; Tue, 18 May 2004 12:57: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 1BQ7to-00070k-GR
	for ietf@ietf.org; Tue, 18 May 2004 12:57:04 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ7st-0006xF-00
	for ietf@ietf.org; Tue, 18 May 2004 12:56:07 -0400
Received: from smtp.cogeco.net ([216.221.81.25] helo=fep1.cogeco.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ7sP-0006uX-00
	for ietf@ietf.org; Tue, 18 May 2004 12:55:37 -0400
Received: from dot-god.com (d235-151-132.home1.cgocable.net [24.235.151.132])
	by fep1.cogeco.net (Postfix) with ESMTP
	id AE1935FE6; Tue, 18 May 2004 12:55:31 -0400 (EDT)
Received: from baptista (helo=localhost)
	by dot-god.com with local-esmtp (Exim 4.12)
	id 1BQ7sJ-0001ln-00; Tue, 18 May 2004 12:55:31 -0400
Date: Tue, 18 May 2004 12:55:31 -0400 (EDT)
From: Joe Baptista <baptista@dot-god.com>
To: Paul Vixie <vixie@vix.com>
Cc: <ietf@ietf.org>
Subject: Re: Root Anycast
In-Reply-To: <g3lljqegi6.fsf@sa.vix.com>
Message-ID: <Pine.LNX.4.33.0405181253490.5111-100000@dot-god.com>
Organization: http://www.baptista.god/ or http://www.joebaptista.com/
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


On 18 May 2004, Paul Vixie wrote:

> If you'd like to unify something, perhaps it could be DNS client behaviour
> and network-owner recursive caching forwarder design.  And while you're at
> it, please outlaw those fiendish DNS-based load balancers.  f-root should
> still be a 486DX2-66 like it was in ~1995, rather than fifty 1GHz pentiums,
> and the 500X load 10 years later is due to client stupidity, not population
> growth or backbone speed increases.

Not completely due to client stupidity,

http://www.theregister.co.uk/2003/02/05/dud_queries_swamp_us_internet/

it is however a factor :)

regards
joe baptista




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


From exim@www1.ietf.org  Tue May 18 13:21: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 NAA28712
	for <ietf-archive@odin.ietf.org>; Tue, 18 May 2004 13:21: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 1BQ8DU-0001Nz-GP
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 13:17:29 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4IHHODB005091
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 13:17:24 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ7zi-00061A-0t; Tue, 18 May 2004 13:03:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ7tq-0004VH-HP
	for ietf@optimus.ietf.org; Tue, 18 May 2004 12:57: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 MAA27244
	for <ietf@ietf.org>; Tue, 18 May 2004 12:57: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 1BQ7to-00070k-GR
	for ietf@ietf.org; Tue, 18 May 2004 12:57:04 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ7st-0006xF-00
	for ietf@ietf.org; Tue, 18 May 2004 12:56:07 -0400
Received: from smtp.cogeco.net ([216.221.81.25] helo=fep1.cogeco.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ7sP-0006uX-00
	for ietf@ietf.org; Tue, 18 May 2004 12:55:37 -0400
Received: from dot-god.com (d235-151-132.home1.cgocable.net [24.235.151.132])
	by fep1.cogeco.net (Postfix) with ESMTP
	id AE1935FE6; Tue, 18 May 2004 12:55:31 -0400 (EDT)
Received: from baptista (helo=localhost)
	by dot-god.com with local-esmtp (Exim 4.12)
	id 1BQ7sJ-0001ln-00; Tue, 18 May 2004 12:55:31 -0400
Date: Tue, 18 May 2004 12:55:31 -0400 (EDT)
From: Joe Baptista <baptista@dot-god.com>
To: Paul Vixie <vixie@vix.com>
Cc: <ietf@ietf.org>
Subject: Re: Root Anycast
In-Reply-To: <g3lljqegi6.fsf@sa.vix.com>
Message-ID: <Pine.LNX.4.33.0405181253490.5111-100000@dot-god.com>
Organization: http://www.baptista.god/ or http://www.joebaptista.com/
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: 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 18 May 2004, Paul Vixie wrote:

> If you'd like to unify something, perhaps it could be DNS client behaviour
> and network-owner recursive caching forwarder design.  And while you're at
> it, please outlaw those fiendish DNS-based load balancers.  f-root should
> still be a 486DX2-66 like it was in ~1995, rather than fifty 1GHz pentiums,
> and the 500X load 10 years later is due to client stupidity, not population
> growth or backbone speed increases.

Not completely due to client stupidity,

http://www.theregister.co.uk/2003/02/05/dud_queries_swamp_us_internet/

it is however a factor :)

regards
joe baptista




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



From ietf-admin@ietf.org  Tue May 18 13:51:33 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01198
	for <ietf-archive@ietf.org>; Tue, 18 May 2004 13:51: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 1BQ8kX-0002yo-KX
	for ietf-archive@ietf.org; Tue, 18 May 2004 13:51:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ8jS-0002mm-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 13:50:27 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ8hd-0002SA-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 13:48:33 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ8WU-0005t6-5H; Tue, 18 May 2004 13:37:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ8Rs-00055s-Ne
	for ietf@optimus.ietf.org; Tue, 18 May 2004 13:32: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 NAA29439
	for <ietf@ietf.org>; Tue, 18 May 2004 13:32:14 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQ8Rq-0001Vo-IL
	for ietf@ietf.org; Tue, 18 May 2004 13:32:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ8Qv-0001Rb-00
	for ietf@ietf.org; Tue, 18 May 2004 13:31:17 -0400
Received: from cust.92.136.adsl.cistron.nl
	([195.64.92.136] helo=purgatory.unfix.org ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ8QV-0001O0-00
	for ietf@ietf.org; Tue, 18 May 2004 13:30:51 -0400
Received: from localhost (localhost [127.0.0.1])
	by purgatory.unfix.org (Postfix) with ESMTP
	id 39F007FDC; Tue, 18 May 2004 19:30:42 +0200 (CEST)
Received: from purgatory.unfix.org ([127.0.0.1])
	by localhost (purgatory [127.0.0.1]) (amavisd-new, port 10024)
	with SMTP id 20277-86; Tue, 18 May 2004 19:30:28 +0200 (CEST)
Received: from [9.4.70.109] (pat.zurich.ibm.com [195.176.20.45])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by purgatory.unfix.org (Postfix) with ESMTP
	id 0554D7F67; Tue, 18 May 2004 19:30:26 +0200 (CEST)
Subject: Re: Root Anycast
From: Jeroen Massar <jeroen@unfix.org>
To: Joe Baptista <baptista@dot-god.com>
Cc: Paul Vixie <vixie@vix.com>, ietf@ietf.org
In-Reply-To: <Pine.LNX.4.33.0405181253490.5111-100000@dot-god.com>
References: <Pine.LNX.4.33.0405181253490.5111-100000@dot-god.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-e/OP5cRrj71oII0f/Ij8"
Organization: Unfix
Message-Id: <1084901415.22699.239.camel@segesta.zurich.ibm.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.5 (1.4.5-7) 
Date: Tue, 18 May 2004 19:30:15 +0200
X-Virus-Scanned: purgatory.unfix.org - http://unfix.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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60


--=-e/OP5cRrj71oII0f/Ij8
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Tue, 2004-05-18 at 18:55, Joe Baptista wrote:
> On 18 May 2004, Paul Vixie wrote:
>=20
> > If you'd like to unify something, perhaps it could be DNS client behavi=
our
> > and network-owner recursive caching forwarder design.  And while you're=
 at
> > it, please outlaw those fiendish DNS-based load balancers.  f-root shou=
ld
> > still be a 486DX2-66 like it was in ~1995, rather than fifty 1GHz penti=
ums,
> > and the 500X load 10 years later is due to client stupidity, not popula=
tion
> > growth or backbone speed increases.
>=20
> Not completely due to client stupidity,
>=20
> http://www.theregister.co.uk/2003/02/05/dud_queries_swamp_us_internet/
>=20
> it is however a factor :)

If you would have even read the CAIDA article you would know why AS112
has been built and that misconfigured _clients_ perform the queries.
Also if clients would be using local ISP supplied DNS caches, that would
be correctly configured there would be a lot less of a problem.

Adding your .god/satan and whatever tld you are trying to advertise
won't help at all with the fact that clients are trying to get the
RFC1918 and other reverses from the root servers which simply do not
exist. That the register even took the article just tells something
about their quality, having over 70% advertisement in a 'article'...

FYI read up on:
http://www.as112.net
http://www.chagreslabs.net/jmbrown/research/drafts/draft-brown-pvtipdns-01.=
html

And the current CAIDA work at:
http://www.caida.org/projects/dns-analysis/

Greets,
 Jeroen


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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iD8DBQBAqkgnKaooUjM+fCMRAn7oAKCMFZmoij2/bFYGqrZHzd2km35uXgCghqdF
kAX0RXBYiBDAZfY/TeJbRns=
=C4/0
-----END PGP SIGNATURE-----

--=-e/OP5cRrj71oII0f/Ij8--


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


From exim@www1.ietf.org  Tue May 18 13:51:40 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 NAA01234
	for <ietf-archive@odin.ietf.org>; Tue, 18 May 2004 13:51:40 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ8hf-0007zy-4i
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 13:48:35 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4IHmYCD030742
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 13:48:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ8WU-0005t6-5H; Tue, 18 May 2004 13:37:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ8Rs-00055s-Ne
	for ietf@optimus.ietf.org; Tue, 18 May 2004 13:32: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 NAA29439
	for <ietf@ietf.org>; Tue, 18 May 2004 13:32:14 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQ8Rq-0001Vo-IL
	for ietf@ietf.org; Tue, 18 May 2004 13:32:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ8Qv-0001Rb-00
	for ietf@ietf.org; Tue, 18 May 2004 13:31:17 -0400
Received: from cust.92.136.adsl.cistron.nl
	([195.64.92.136] helo=purgatory.unfix.org ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ8QV-0001O0-00
	for ietf@ietf.org; Tue, 18 May 2004 13:30:51 -0400
Received: from localhost (localhost [127.0.0.1])
	by purgatory.unfix.org (Postfix) with ESMTP
	id 39F007FDC; Tue, 18 May 2004 19:30:42 +0200 (CEST)
Received: from purgatory.unfix.org ([127.0.0.1])
	by localhost (purgatory [127.0.0.1]) (amavisd-new, port 10024)
	with SMTP id 20277-86; Tue, 18 May 2004 19:30:28 +0200 (CEST)
Received: from [9.4.70.109] (pat.zurich.ibm.com [195.176.20.45])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by purgatory.unfix.org (Postfix) with ESMTP
	id 0554D7F67; Tue, 18 May 2004 19:30:26 +0200 (CEST)
Subject: Re: Root Anycast
From: Jeroen Massar <jeroen@unfix.org>
To: Joe Baptista <baptista@dot-god.com>
Cc: Paul Vixie <vixie@vix.com>, ietf@ietf.org
In-Reply-To: <Pine.LNX.4.33.0405181253490.5111-100000@dot-god.com>
References: <Pine.LNX.4.33.0405181253490.5111-100000@dot-god.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-e/OP5cRrj71oII0f/Ij8"
Organization: Unfix
Message-Id: <1084901415.22699.239.camel@segesta.zurich.ibm.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.5 (1.4.5-7) 
Date: Tue, 18 May 2004 19:30:15 +0200
X-Virus-Scanned: purgatory.unfix.org - http://unfix.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: 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>


--=-e/OP5cRrj71oII0f/Ij8
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Tue, 2004-05-18 at 18:55, Joe Baptista wrote:
> On 18 May 2004, Paul Vixie wrote:
>=20
> > If you'd like to unify something, perhaps it could be DNS client behavi=
our
> > and network-owner recursive caching forwarder design.  And while you're=
 at
> > it, please outlaw those fiendish DNS-based load balancers.  f-root shou=
ld
> > still be a 486DX2-66 like it was in ~1995, rather than fifty 1GHz penti=
ums,
> > and the 500X load 10 years later is due to client stupidity, not popula=
tion
> > growth or backbone speed increases.
>=20
> Not completely due to client stupidity,
>=20
> http://www.theregister.co.uk/2003/02/05/dud_queries_swamp_us_internet/
>=20
> it is however a factor :)

If you would have even read the CAIDA article you would know why AS112
has been built and that misconfigured _clients_ perform the queries.
Also if clients would be using local ISP supplied DNS caches, that would
be correctly configured there would be a lot less of a problem.

Adding your .god/satan and whatever tld you are trying to advertise
won't help at all with the fact that clients are trying to get the
RFC1918 and other reverses from the root servers which simply do not
exist. That the register even took the article just tells something
about their quality, having over 70% advertisement in a 'article'...

FYI read up on:
http://www.as112.net
http://www.chagreslabs.net/jmbrown/research/drafts/draft-brown-pvtipdns-01.=
html

And the current CAIDA work at:
http://www.caida.org/projects/dns-analysis/

Greets,
 Jeroen


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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iD8DBQBAqkgnKaooUjM+fCMRAn7oAKCMFZmoij2/bFYGqrZHzd2km35uXgCghqdF
kAX0RXBYiBDAZfY/TeJbRns=
=C4/0
-----END PGP SIGNATURE-----

--=-e/OP5cRrj71oII0f/Ij8--


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



From ietf-admin@ietf.org  Tue May 18 14:04: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 OAA01994
	for <ietf-archive@ietf.org>; Tue, 18 May 2004 14:04: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 1BQ8wv-0003iG-Pt
	for ietf-archive@ietf.org; Tue, 18 May 2004 14:04:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ8w4-0003en-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 14:03:29 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ8vR-0003an-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 14:02:49 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ8l0-0000II-Aj; Tue, 18 May 2004 13:52:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ8fF-0007Sc-31
	for ietf@optimus.ietf.org; Tue, 18 May 2004 13:46:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00167
	for <ietf@ietf.org>; Tue, 18 May 2004 13:46: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 1BQ8fC-00028b-MF
	for ietf@ietf.org; Tue, 18 May 2004 13:46:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ8eK-00026V-00
	for ietf@ietf.org; Tue, 18 May 2004 13:45:09 -0400
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ8dS-00024B-00
	for ietf@ietf.org; Tue, 18 May 2004 13:44:14 -0400
Received: from f01m-34-230.d0.club-internet.fr ([212.195.225.230] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.24)
	id 1BQ8dI-0004L3-Uw; Tue, 18 May 2004 10:44:05 -0700
Message-Id: <6.1.0.6.2.20040518171004.04666060@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 6.1.0.6
Date: Tue, 18 May 2004 18:01:05 +0200
To: Paul Vixie <vixie@vix.com>, ietf@ietf.org
From: jfcm <info@utel.net>
Subject: Re: Root Anycast
In-Reply-To: <g3lljqegi6.fsf@sa.vix.com>
References: <DFC3BD05-A84A-11D8-AC18-000A95CD987A@muada.com>
 <g3lljqegi6.fsf@sa.vix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [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

Dear Paul,
pardon me for the previous response. I could not resist!
This post of yours is a very important one as it expresses, from experience 
and in IETF wording, what I try to convey from another origin, experience, 
modelization, architectural logic and culture.

At 02:16 18/05/04, Paul Vixie wrote:
>The table is round.  Policies are discussed as a group but set individually.
>The result is a service which has never been "down hard", not ever, not for
>any millisecond out of the last 15 years.  This is "strength by diversity."

This is exactly what French and now Eurospeak call "concertation". The very 
basis of the emerging European Constitutional culture based upon 
subsidiarity and granularity. Another less confusing word for English 
speakers, less related to French specific thinking, and corresponding to 
the level of the concerned issue is "intergovernance".

>Careful design by whom?  Organic compared to what?  I assure you that f-root
>has grown by careful design.  It's only organic in that we go where we're
>invited rather than having a gigantic budget that could be used as a leash.

This is what we call subisdiarity. To actively (helping when needed) 
respect the responsibilities of those depending on (not from) you. I am 
sure that as F-Root Manager you do not mess within your mirror sites 
management, but are always ready to help on need.

>Check out <http://www.isc.org/ops/f-root/> and the list of mirror sites, and
>look for some sponsors you know, and call them, and ask why they sponsored
>f-root and whether they're happy about it.  Then find someone in that region
>and ask them to do "dig @192.5.5.241 hostname.bind chaos txt" and tell you
>whether they're talking to a local f-root.  What could scale better, or
>allocate resources more efficiently?  (Central planning didn't help USSR.)

Right. The only problem "we" (myself to start with, but also several Gov 
such as Brazil, India, China, etc. etc. as expressed at WSIS and many many 
others) have is that if Root servers are not centraly planned, they 
broadcast the same centraly planed and edited file. Also that this central 
editing imposes constraints due to the 13 limitation. Apart from the 
political issue, this makes that file and the a-root a world economy, life, 
security, single points of failure. This is something that the "we" quoted 
above do not accept.

>Who is "we", though?  That's always the excluded middle of this debate.  I
>know who I am -- a root operator.  But who are "we"?  And which of the
>million different answers to "who are 'we'?" would you like to see govern
>the choice of "who gets to decide how this stuff ought to work?"  E.g., I'm
>sure, without even having heard it, that you wouldn't want the choice of
>"who decides?" governed by Dean Anderson's answer to "who are 'we'?"

There is a very good response to that. RFC 883. It says "we" are the users, 
in saying that no one will be forced to use DNS data he did not chose. It 
seems a realistic simple way to make the table totally round (or at least 
rounder): if no one ask for more than the today situation, it is OK. If 
some ask for more, let them do it. ICANN ICP-3 gives pretty good and 
reasonable rules about their experimentation and implementation constraints.

>In counterpoint, it seems to me that any unified design will make the system
>subject to monoculture attacks or ISO-L9 capture, and that the current
>system which you call "unplanned and organic" (but which is actually just
>"diversity by credo") yields a stronger system overall.

Here is where I disagree: with the "core value" reading (cf. IETF 
description draft by Harald). You are right about what you say. But this is 
not to be a creed. This is to be architectural efficiency. This is pure 
cybernetics - cynernetics as the technical science of autonomous systems 
(where mathematics are for abstract systems and physics for inert systems). 
This would probably permit you to agree with Dean on a conceivable common 
framework where his concerns and your preriquisites would be addressed.

>If you'd like to unify something, perhaps it could be DNS client behaviour
>and network-owner recursive caching forwarder design.  And while you're at
>it, please outlaw those fiendish DNS-based load balancers.  f-root should
>still be a 486DX2-66 like it was in ~1995, rather than fifty 1GHz pentiums,
>and the 500X load 10 years later is due to client stupidity, not population
>growth or backbone speed increases.

You are damned right! This is exactly what we try to build right now with 
the AFRAC project (the DNS root is _not_ the only one concerned, both as a 
root reference and in the way it is used or can be denied service). We are 
concerned by DNS, adressing, etc. data, but also by geosocietal and defense 
information: every information and source code necessary for tier and tier 
applications (everyone interoperating)

1. first target: distribution of the root machines through a root server 
matrix and core network - containing local root information to make it a 
need. Decrease of the pressure, risk containement, new data, new services.

2. second target : a user MITM providing "hardware, software and brainware 
firewalling". At root system level it means that the user is to cache his 
root system. The reason why he will do it is that his root system will 
_not_ be the default public root system. It will be his own version of it, 
adding his local, private space management and views. Once set-up, calling 
on the root system would actually pollute his root system, so he will not 
do it.

Private roots are not subject to DoS. They certainly permit to survive a 
few hours, days and even probably months. In adding all the root themes we 
can objectively consider today for ubiquist new services, plus a "first 
necessity" software kit and root, we are probably talking of an ASN.1 
structure of less than 20 compacted K (comparable to anti-virus updates).

The figures I discussed in a previous memo, show that we could then come 
back to a "486DX2". However discussing of root server the way we consider 
them today would be quite meaningless.

jfc

PS. I do not consider here the problem of the loggers which is another 
(mainly legal) issue.










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


From ietf-admin@ietf.org  Tue May 18 14:10:31 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02423
	for <ietf-archive@ietf.org>; Tue, 18 May 2004 14:10: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 1BQ92t-00048m-4G
	for ietf-archive@ietf.org; Tue, 18 May 2004 14:10:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ91n-00041l-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 14:09:24 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ91I-0003xe-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 14:08:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ8l5-0000JJ-L3; Tue, 18 May 2004 13:52:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ8fE-0007Sa-CW
	for ietf@optimus.ietf.org; Tue, 18 May 2004 13:46:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00163
	for <ietf@ietf.org>; Tue, 18 May 2004 13:46: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 1BQ8fC-00028U-28
	for ietf@ietf.org; Tue, 18 May 2004 13:46:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ8eJ-00026N-00
	for ietf@ietf.org; Tue, 18 May 2004 13:45:08 -0400
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ8dS-00023h-00
	for ietf@ietf.org; Tue, 18 May 2004 13:44:14 -0400
Received: from f01m-34-230.d0.club-internet.fr ([212.195.225.230] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.24)
	id 1BQ8dG-0004L3-AV; Tue, 18 May 2004 10:44:03 -0700
Message-Id: <6.1.0.6.2.20040518170540.0479fd00@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 6.1.0.6
Date: Tue, 18 May 2004 17:06:04 +0200
To: Paul Vixie <vixie@vix.com>, ietf@ietf.org
From: jfcm <info@utel.net>
Subject: Re: [dnsop] Re: Complaint on abuse of DNSOP lists
In-Reply-To: <g3pt92eifn.fsf@sa.vix.com>
References: <C6111F54-A81D-11D8-8726-000A95928574@kurtis.pp.se>
 <Pine.LNX.4.44.0405171600540.25950-100000@cirrus.av8.net>
 <g3pt92eifn.fsf@sa.vix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [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 01:35 18/05/04, Paul Vixie wrote:
>dean@av8.com (Dean Anderson) writes:
> > ... For the less technical, an exchange point is ...
>
>I don't think there's anyone on this list less technical than you, Dean.

Thank you :-)
jfc


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


From exim@www1.ietf.org  Tue May 18 14:11:16 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 OAA02517
	for <ietf-archive@odin.ietf.org>; Tue, 18 May 2004 14:11: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 1BQ8vS-00020v-9k
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 14:02:50 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4II2o4D007742
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 14:02:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ8l0-0000II-Aj; Tue, 18 May 2004 13:52:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ8fF-0007Sc-31
	for ietf@optimus.ietf.org; Tue, 18 May 2004 13:46:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00167
	for <ietf@ietf.org>; Tue, 18 May 2004 13:46: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 1BQ8fC-00028b-MF
	for ietf@ietf.org; Tue, 18 May 2004 13:46:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ8eK-00026V-00
	for ietf@ietf.org; Tue, 18 May 2004 13:45:09 -0400
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ8dS-00024B-00
	for ietf@ietf.org; Tue, 18 May 2004 13:44:14 -0400
Received: from f01m-34-230.d0.club-internet.fr ([212.195.225.230] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.24)
	id 1BQ8dI-0004L3-Uw; Tue, 18 May 2004 10:44:05 -0700
Message-Id: <6.1.0.6.2.20040518171004.04666060@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 6.1.0.6
Date: Tue, 18 May 2004 18:01:05 +0200
To: Paul Vixie <vixie@vix.com>, ietf@ietf.org
From: jfcm <info@utel.net>
Subject: Re: Root Anycast
In-Reply-To: <g3lljqegi6.fsf@sa.vix.com>
References: <DFC3BD05-A84A-11D8-AC18-000A95CD987A@muada.com>
 <g3lljqegi6.fsf@sa.vix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - utel.net
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.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>

Dear Paul,
pardon me for the previous response. I could not resist!
This post of yours is a very important one as it expresses, from experience 
and in IETF wording, what I try to convey from another origin, experience, 
modelization, architectural logic and culture.

At 02:16 18/05/04, Paul Vixie wrote:
>The table is round.  Policies are discussed as a group but set individually.
>The result is a service which has never been "down hard", not ever, not for
>any millisecond out of the last 15 years.  This is "strength by diversity."

This is exactly what French and now Eurospeak call "concertation". The very 
basis of the emerging European Constitutional culture based upon 
subsidiarity and granularity. Another less confusing word for English 
speakers, less related to French specific thinking, and corresponding to 
the level of the concerned issue is "intergovernance".

>Careful design by whom?  Organic compared to what?  I assure you that f-root
>has grown by careful design.  It's only organic in that we go where we're
>invited rather than having a gigantic budget that could be used as a leash.

This is what we call subisdiarity. To actively (helping when needed) 
respect the responsibilities of those depending on (not from) you. I am 
sure that as F-Root Manager you do not mess within your mirror sites 
management, but are always ready to help on need.

>Check out <http://www.isc.org/ops/f-root/> and the list of mirror sites, and
>look for some sponsors you know, and call them, and ask why they sponsored
>f-root and whether they're happy about it.  Then find someone in that region
>and ask them to do "dig @192.5.5.241 hostname.bind chaos txt" and tell you
>whether they're talking to a local f-root.  What could scale better, or
>allocate resources more efficiently?  (Central planning didn't help USSR.)

Right. The only problem "we" (myself to start with, but also several Gov 
such as Brazil, India, China, etc. etc. as expressed at WSIS and many many 
others) have is that if Root servers are not centraly planned, they 
broadcast the same centraly planed and edited file. Also that this central 
editing imposes constraints due to the 13 limitation. Apart from the 
political issue, this makes that file and the a-root a world economy, life, 
security, single points of failure. This is something that the "we" quoted 
above do not accept.

>Who is "we", though?  That's always the excluded middle of this debate.  I
>know who I am -- a root operator.  But who are "we"?  And which of the
>million different answers to "who are 'we'?" would you like to see govern
>the choice of "who gets to decide how this stuff ought to work?"  E.g., I'm
>sure, without even having heard it, that you wouldn't want the choice of
>"who decides?" governed by Dean Anderson's answer to "who are 'we'?"

There is a very good response to that. RFC 883. It says "we" are the users, 
in saying that no one will be forced to use DNS data he did not chose. It 
seems a realistic simple way to make the table totally round (or at least 
rounder): if no one ask for more than the today situation, it is OK. If 
some ask for more, let them do it. ICANN ICP-3 gives pretty good and 
reasonable rules about their experimentation and implementation constraints.

>In counterpoint, it seems to me that any unified design will make the system
>subject to monoculture attacks or ISO-L9 capture, and that the current
>system which you call "unplanned and organic" (but which is actually just
>"diversity by credo") yields a stronger system overall.

Here is where I disagree: with the "core value" reading (cf. IETF 
description draft by Harald). You are right about what you say. But this is 
not to be a creed. This is to be architectural efficiency. This is pure 
cybernetics - cynernetics as the technical science of autonomous systems 
(where mathematics are for abstract systems and physics for inert systems). 
This would probably permit you to agree with Dean on a conceivable common 
framework where his concerns and your preriquisites would be addressed.

>If you'd like to unify something, perhaps it could be DNS client behaviour
>and network-owner recursive caching forwarder design.  And while you're at
>it, please outlaw those fiendish DNS-based load balancers.  f-root should
>still be a 486DX2-66 like it was in ~1995, rather than fifty 1GHz pentiums,
>and the 500X load 10 years later is due to client stupidity, not population
>growth or backbone speed increases.

You are damned right! This is exactly what we try to build right now with 
the AFRAC project (the DNS root is _not_ the only one concerned, both as a 
root reference and in the way it is used or can be denied service). We are 
concerned by DNS, adressing, etc. data, but also by geosocietal and defense 
information: every information and source code necessary for tier and tier 
applications (everyone interoperating)

1. first target: distribution of the root machines through a root server 
matrix and core network - containing local root information to make it a 
need. Decrease of the pressure, risk containement, new data, new services.

2. second target : a user MITM providing "hardware, software and brainware 
firewalling". At root system level it means that the user is to cache his 
root system. The reason why he will do it is that his root system will 
_not_ be the default public root system. It will be his own version of it, 
adding his local, private space management and views. Once set-up, calling 
on the root system would actually pollute his root system, so he will not 
do it.

Private roots are not subject to DoS. They certainly permit to survive a 
few hours, days and even probably months. In adding all the root themes we 
can objectively consider today for ubiquist new services, plus a "first 
necessity" software kit and root, we are probably talking of an ASN.1 
structure of less than 20 compacted K (comparable to anti-virus updates).

The figures I discussed in a previous memo, show that we could then come 
back to a "486DX2". However discussing of root server the way we consider 
them today would be quite meaningless.

jfc

PS. I do not consider here the problem of the loggers which is another 
(mainly legal) issue.










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



From exim@www1.ietf.org  Tue May 18 14:11:22 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 OAA02542
	for <ietf-archive@odin.ietf.org>; Tue, 18 May 2004 14:11: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 1BQ91L-0003Pu-5r
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 14:08:55 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4II8sIA012910
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 14:08:55 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ8l5-0000JJ-L3; Tue, 18 May 2004 13:52:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ8fE-0007Sa-CW
	for ietf@optimus.ietf.org; Tue, 18 May 2004 13:46:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00163
	for <ietf@ietf.org>; Tue, 18 May 2004 13:46: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 1BQ8fC-00028U-28
	for ietf@ietf.org; Tue, 18 May 2004 13:46:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ8eJ-00026N-00
	for ietf@ietf.org; Tue, 18 May 2004 13:45:08 -0400
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ8dS-00023h-00
	for ietf@ietf.org; Tue, 18 May 2004 13:44:14 -0400
Received: from f01m-34-230.d0.club-internet.fr ([212.195.225.230] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.24)
	id 1BQ8dG-0004L3-AV; Tue, 18 May 2004 10:44:03 -0700
Message-Id: <6.1.0.6.2.20040518170540.0479fd00@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 6.1.0.6
Date: Tue, 18 May 2004 17:06:04 +0200
To: Paul Vixie <vixie@vix.com>, ietf@ietf.org
From: jfcm <info@utel.net>
Subject: Re: [dnsop] Re: Complaint on abuse of DNSOP lists
In-Reply-To: <g3pt92eifn.fsf@sa.vix.com>
References: <C6111F54-A81D-11D8-8726-000A95928574@kurtis.pp.se>
 <Pine.LNX.4.44.0405171600540.25950-100000@cirrus.av8.net>
 <g3pt92eifn.fsf@sa.vix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - utel.net
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.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 01:35 18/05/04, Paul Vixie wrote:
>dean@av8.com (Dean Anderson) writes:
> > ... For the less technical, an exchange point is ...
>
>I don't think there's anyone on this list less technical than you, Dean.

Thank you :-)
jfc


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



From ietf-admin@ietf.org  Tue May 18 14:51: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 OAA05249
	for <ietf-archive@ietf.org>; Tue, 18 May 2004 14:51: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 1BQ9gV-0006rp-Ts
	for ietf-archive@ietf.org; Tue, 18 May 2004 14:51:28 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ9fX-0006mH-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 14:50:27 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ9el-0006hK-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 14:49:39 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ9WP-0002vu-M3; Tue, 18 May 2004 14:41:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ9N1-0001Rc-Rk
	for ietf@optimus.ietf.org; Tue, 18 May 2004 14:31: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 OAA03976
	for <ietf@ietf.org>; Tue, 18 May 2004 14:31: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 1BQ9Mz-0005Zv-7v
	for ietf@ietf.org; Tue, 18 May 2004 14:31:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ9M7-0005V8-00
	for ietf@ietf.org; Tue, 18 May 2004 14:30:24 -0400
Received: from mail.consulintel.es ([213.172.48.142] helo=consulintel.es)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ9Lb-0005Qx-00
	for ietf@ietf.org; Tue, 18 May 2004 14:29:51 -0400
Received: from consulintel02 ([212.76.240.58])
	(authenticated user jordi.palet@consulintel.es)
	by consulintel.es (consulintel.es [127.0.0.1])
	(MDaemon.PRO.v7.0.1.R)
	with ESMTP id md50000103243.msg
	for <ietf@ietf.org>; Tue, 18 May 2004 20:30:21 +0200
Message-ID: <0b6001c43d05$f68ccd10$0402200a@consulintel.es>
Reply-To: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
From: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
References: <DC55E4CF3BF32E46B6F1FA9028E35667626A@w3k.win3k.braintec-consult.de>
Subject: Re: 60th IETF - Registration
Date: Tue, 18 May 2004 20:28:45 +0200
Organization: Consulintel
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Spam-Processed: consulintel.es, Tue, 18 May 2004 20:30:21 +0200
	(not processed: message from valid local sender)
X-MDRemoteIP: 212.76.240.58
X-Return-Path: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
X-MDAV-Processed: consulintel.es, Tue, 18 May 2004 20:30:21 +0200
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

I think is unacceptably TODAY, specially for IETF, that we should use a phone instead of on-line or email confirmation.

We should not accept hotels that don't make usage of technology to arrange our meetings.

We aren't asking the hotel (today) to support IPv6, but at least just IPv4 !

Regards,
Jordi

----- Original Message -----=20
From: "Hans Peter Dittler" <dittler@braintec-consult.de>
To: "'Pekka Savola'" <pekkas@netcore.fi>; <ietf@ietf.org>
Sent: Tuesday, May 18, 2004 8:32 AM
Subject: AW: 60th IETF - Registration


> Hi,
>=20
> >The registration says the hotel is already full.  Is this for real --
> 900 rooms already taken, within 11 hours??
>=20
> no - there are rooms of all three kinds available if you call the
> reservation-desk directly.
> (Phone: 1-619-291-2900 or 1-877-734-2726)
>=20
> I just got my confirmation mail back from San Diego (8:23 MEZ =3D 23:23 in
> San Diego)
>=20
> Peter
>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>=20


**********************************
Madrid 2003 Global IPv6 Summit
Presentations and videos on line at:
http://www.ipv6-es.com

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.




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


From exim@www1.ietf.org  Tue May 18 14:57:14 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 OAA05584
	for <ietf-archive@odin.ietf.org>; Tue, 18 May 2004 14:57: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 1BQ9en-0004E6-Io
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 14:49:41 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4IInf7E016245
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 14:49:41 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ9WP-0002vu-M3; Tue, 18 May 2004 14:41:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ9N1-0001Rc-Rk
	for ietf@optimus.ietf.org; Tue, 18 May 2004 14:31: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 OAA03976
	for <ietf@ietf.org>; Tue, 18 May 2004 14:31: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 1BQ9Mz-0005Zv-7v
	for ietf@ietf.org; Tue, 18 May 2004 14:31:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ9M7-0005V8-00
	for ietf@ietf.org; Tue, 18 May 2004 14:30:24 -0400
Received: from mail.consulintel.es ([213.172.48.142] helo=consulintel.es)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ9Lb-0005Qx-00
	for ietf@ietf.org; Tue, 18 May 2004 14:29:51 -0400
Received: from consulintel02 ([212.76.240.58])
	(authenticated user jordi.palet@consulintel.es)
	by consulintel.es (consulintel.es [127.0.0.1])
	(MDaemon.PRO.v7.0.1.R)
	with ESMTP id md50000103243.msg
	for <ietf@ietf.org>; Tue, 18 May 2004 20:30:21 +0200
Message-ID: <0b6001c43d05$f68ccd10$0402200a@consulintel.es>
Reply-To: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
From: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
References: <DC55E4CF3BF32E46B6F1FA9028E35667626A@w3k.win3k.braintec-consult.de>
Subject: Re: 60th IETF - Registration
Date: Tue, 18 May 2004 20:28:45 +0200
Organization: Consulintel
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Spam-Processed: consulintel.es, Tue, 18 May 2004 20:30:21 +0200
	(not processed: message from valid local sender)
X-MDRemoteIP: 212.76.240.58
X-Return-Path: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
X-MDAV-Processed: consulintel.es, Tue, 18 May 2004 20:30:21 +0200
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-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

I think is unacceptably TODAY, specially for IETF, that we should use a phone instead of on-line or email confirmation.

We should not accept hotels that don't make usage of technology to arrange our meetings.

We aren't asking the hotel (today) to support IPv6, but at least just IPv4 !

Regards,
Jordi

----- Original Message -----=20
From: "Hans Peter Dittler" <dittler@braintec-consult.de>
To: "'Pekka Savola'" <pekkas@netcore.fi>; <ietf@ietf.org>
Sent: Tuesday, May 18, 2004 8:32 AM
Subject: AW: 60th IETF - Registration


> Hi,
>=20
> >The registration says the hotel is already full.  Is this for real --
> 900 rooms already taken, within 11 hours??
>=20
> no - there are rooms of all three kinds available if you call the
> reservation-desk directly.
> (Phone: 1-619-291-2900 or 1-877-734-2726)
>=20
> I just got my confirmation mail back from San Diego (8:23 MEZ =3D 23:23 in
> San Diego)
>=20
> Peter
>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>=20


**********************************
Madrid 2003 Global IPv6 Summit
Presentations and videos on line at:
http://www.ipv6-es.com

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.




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



From ietf-admin@ietf.org  Tue May 18 16:22: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 QAA13412
	for <ietf-archive@ietf.org>; Tue, 18 May 2004 16:22: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 1BQB6m-0006Vx-NH
	for ietf-archive@ietf.org; Tue, 18 May 2004 16:22:40 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQB5Z-0006Jz-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 16:21:26 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQB3o-00063N-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 16:19:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQARw-0006GA-LB; Tue, 18 May 2004 15:40:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQANk-0003s1-BJ
	for ietf@optimus.ietf.org; Tue, 18 May 2004 15:36: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 PAA09499
	for <ietf@ietf.org>; Tue, 18 May 2004 15:36: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 1BQANg-0001gM-NY
	for ietf@ietf.org; Tue, 18 May 2004 15:36:04 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQAMu-0001ee-00
	for ietf@ietf.org; Tue, 18 May 2004 15:35:17 -0400
Received: from slimsixten.pilsnet.sunet.se ([192.36.125.115])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQAM8-0001ct-00
	for ietf@ietf.org; Tue, 18 May 2004 15:34:28 -0400
Received: from localhost (localhost [127.0.0.1])
	by slimsixten.pilsnet.sunet.se (8.11.6p3/8.11.6) with ESMTP id i4IJYQv01389
	for <ietf@ietf.org>; Tue, 18 May 2004 21:34:26 +0200 (CEST)
Date: Tue, 18 May 2004 21:34:26 +0200
From: =?ISO-8859-1?Q?M=E5ns_Nilsson?= <mansaxel@besserwisser.org>
To: ietf@ietf.org
Subject: Re: Root Anycast
Message-ID: <114760000.1084908866@slimsixten.pilsnet.sunet.se>
In-Reply-To: <6.1.0.6.2.20040518171004.04666060@mail.utel.net>
References: <DFC3BD05-A84A-11D8-AC18-000A95CD987A@muada.com>
 <g3lljqegi6.fsf@sa.vix.com>
 <6.1.0.6.2.20040518171004.04666060@mail.utel.net>
X-Mailer: Mulberry/3.1.1 (Linux/x86)
X-availability: Yes. 
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="==========9BE4D86D497E616C0E27=========="
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

--==========9BE4D86D497E616C0E27==========
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

--On Tuesday, May 18, 2004 18:01:05 +0200 jfcm <info@utel.net> wrote:

> 1. first target: distribution of the root machines through a root server
> matrix and core network -=20

Yes, this is already done. It works, even if it is not top-guided as you
envision.

> containing local root information to make it a
> need. Decrease of the pressure, risk containement, new data, new =
services.

This is unnecessary and prone to failure.=20

> 2. second target : a user MITM providing "hardware, software and
> brainware firewalling". At root system level it means that the user is to
> cache his root system.=20

Which part of the present caching resolve server does not provide this
service today? Aren't you reinventing the wheel here?=20

> Private roots are not subject to DoS. They certainly permit to survive a
> few hours, days and even probably months. In adding all the root themes
> we can objectively consider today for ubiquist new services, plus a
> "first necessity" software kit and root, we are probably talking of an
> ASN.1 structure of less than 20 compacted K (comparable to anti-virus
> updates).

Private roots are subject to confusion, mis-directed micromanagement by
local admins, overly sensitive to local politics, split-vision of what must
by design be unified, and endless user frustration. I have tried this in a
large corporate network, and it was, even there with a clear chain of
command, a horrible mess. Never, ever again will I take anything like it
outside a lab (except to kill it).

> The figures I discussed in a previous memo, show that we could then come
> back to a "486DX2". However discussing of root server the way we consider
> them today would be quite meaningless.

You have a strong passion for doing something to fix the DNS system. I
suggest you channel this passion towards trying to fix all the b0rkened
clients (cf. the studies of root server load refered to earlier here)
before you try to impose breakage onto the well-functioning root server
system.=20

--=20
M=E5ns Nilsson                    MN1334-RIPE
http://vvv.besserwisser.org     +46 706 81 72 04

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (NetBSD)

iD8DBQFAqmVC02/pMZDM1cURAq+IAJ9LcqdKuOs/RolQp4ej54WoR/HvuACeNp2Y
f36tpKevCONty2LmBdAP3Uo=
=LB7r
-----END PGP SIGNATURE-----

--==========9BE4D86D497E616C0E27==========--


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


From exim@www1.ietf.org  Tue May 18 16:49:21 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 QAA17011
	for <ietf-archive@odin.ietf.org>; Tue, 18 May 2004 16:49:21 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQB3p-0000rW-0R
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 16:19:45 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4IKJatO003315
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 16:19:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQARw-0006GA-LB; Tue, 18 May 2004 15:40:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQANk-0003s1-BJ
	for ietf@optimus.ietf.org; Tue, 18 May 2004 15:36: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 PAA09499
	for <ietf@ietf.org>; Tue, 18 May 2004 15:36: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 1BQANg-0001gM-NY
	for ietf@ietf.org; Tue, 18 May 2004 15:36:04 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQAMu-0001ee-00
	for ietf@ietf.org; Tue, 18 May 2004 15:35:17 -0400
Received: from slimsixten.pilsnet.sunet.se ([192.36.125.115])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQAM8-0001ct-00
	for ietf@ietf.org; Tue, 18 May 2004 15:34:28 -0400
Received: from localhost (localhost [127.0.0.1])
	by slimsixten.pilsnet.sunet.se (8.11.6p3/8.11.6) with ESMTP id i4IJYQv01389
	for <ietf@ietf.org>; Tue, 18 May 2004 21:34:26 +0200 (CEST)
Date: Tue, 18 May 2004 21:34:26 +0200
From: =?ISO-8859-1?Q?M=E5ns_Nilsson?= <mansaxel@besserwisser.org>
To: ietf@ietf.org
Subject: Re: Root Anycast
Message-ID: <114760000.1084908866@slimsixten.pilsnet.sunet.se>
In-Reply-To: <6.1.0.6.2.20040518171004.04666060@mail.utel.net>
References: <DFC3BD05-A84A-11D8-AC18-000A95CD987A@muada.com>
 <g3lljqegi6.fsf@sa.vix.com>
 <6.1.0.6.2.20040518171004.04666060@mail.utel.net>
X-Mailer: Mulberry/3.1.1 (Linux/x86)
X-availability: Yes. 
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="==========9BE4D86D497E616C0E27=========="
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-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>

--==========9BE4D86D497E616C0E27==========
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

--On Tuesday, May 18, 2004 18:01:05 +0200 jfcm <info@utel.net> wrote:

> 1. first target: distribution of the root machines through a root server
> matrix and core network -=20

Yes, this is already done. It works, even if it is not top-guided as you
envision.

> containing local root information to make it a
> need. Decrease of the pressure, risk containement, new data, new =
services.

This is unnecessary and prone to failure.=20

> 2. second target : a user MITM providing "hardware, software and
> brainware firewalling". At root system level it means that the user is to
> cache his root system.=20

Which part of the present caching resolve server does not provide this
service today? Aren't you reinventing the wheel here?=20

> Private roots are not subject to DoS. They certainly permit to survive a
> few hours, days and even probably months. In adding all the root themes
> we can objectively consider today for ubiquist new services, plus a
> "first necessity" software kit and root, we are probably talking of an
> ASN.1 structure of less than 20 compacted K (comparable to anti-virus
> updates).

Private roots are subject to confusion, mis-directed micromanagement by
local admins, overly sensitive to local politics, split-vision of what must
by design be unified, and endless user frustration. I have tried this in a
large corporate network, and it was, even there with a clear chain of
command, a horrible mess. Never, ever again will I take anything like it
outside a lab (except to kill it).

> The figures I discussed in a previous memo, show that we could then come
> back to a "486DX2". However discussing of root server the way we consider
> them today would be quite meaningless.

You have a strong passion for doing something to fix the DNS system. I
suggest you channel this passion towards trying to fix all the b0rkened
clients (cf. the studies of root server load refered to earlier here)
before you try to impose breakage onto the well-functioning root server
system.=20

--=20
M=E5ns Nilsson                    MN1334-RIPE
http://vvv.besserwisser.org     +46 706 81 72 04

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (NetBSD)

iD8DBQFAqmVC02/pMZDM1cURAq+IAJ9LcqdKuOs/RolQp4ej54WoR/HvuACeNp2Y
f36tpKevCONty2LmBdAP3Uo=
=LB7r
-----END PGP SIGNATURE-----

--==========9BE4D86D497E616C0E27==========--


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



From ietf-admin@ietf.org  Tue May 18 16:52:31 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17425
	for <ietf-archive@ietf.org>; Tue, 18 May 2004 16:52: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 1BQBZg-0002v5-Gt
	for ietf-archive@ietf.org; Tue, 18 May 2004 16:52:32 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQBYg-0002kw-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 16:51:30 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQBXm-0002bO-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 16:50:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQBCy-0003OH-Qu; Tue, 18 May 2004 16:29:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQATc-0006j9-Bf
	for ietf@optimus.ietf.org; Tue, 18 May 2004 15:42:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09788
	for <ietf@ietf.org>; Tue, 18 May 2004 15:42: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 1BQATa-0001yM-JJ
	for ietf@ietf.org; Tue, 18 May 2004 15:42:10 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQASd-0001vZ-00
	for ietf@ietf.org; Tue, 18 May 2004 15:41:12 -0400
Received: from 1-1-2-20b.rny.sth.bostream.se ([82.182.132.65] helo=klapautius.it.su.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQAS4-0001tO-00
	for ietf@ietf.org; Tue, 18 May 2004 15:40:36 -0400
Received: from it.su.se (localhost.localdomain [127.0.0.1])
	by klapautius.it.su.se (8.11.6/8.11.6) with ESMTP id i4IJdDl01285;
	Tue, 18 May 2004 21:39:13 +0200
Message-ID: <40AA6661.4000304@it.su.se>
Date: Tue, 18 May 2004 21:39:13 +0200
From: Leif Johansson <leifj@it.su.se>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: sv, en, en-us
MIME-Version: 1.0
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
CC: ietf@ietf.org
Subject: Re: 60th IETF - Registration
References: <DC55E4CF3BF32E46B6F1FA9028E35667626A@w3k.win3k.braintec-consult.de> <0b6001c43d05$f68ccd10$0402200a@consulintel.es>
In-Reply-To: <0b6001c43d05$f68ccd10$0402200a@consulintel.es>
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=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

JORDI PALET MARTINEZ wrote:
> I think is unacceptably TODAY, specially for IETF, that we should use a phone instead of on-line or email confirmation.
> 
> We should not accept hotels that don't make usage of technology to arrange our meetings.
> 
> We aren't asking the hotel (today) to support IPv6, but at least just IPv4 !
> 
> Regards,
> Jordi

Big hotels that are cheap and where the staff won't throw a fit
when we all turn up in force, laptops, duct-tape and all, don't
exactly grow on trees you know! I'm happy if it has a bar.

	MVH leifj

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


From exim@www1.ietf.org  Tue May 18 17:06:59 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 RAA18396
	for <ietf-archive@odin.ietf.org>; Tue, 18 May 2004 17:06: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 1BQBXn-0003eU-QF
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 16:50:45 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4IKoZbQ013998
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 16:50:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQBCy-0003OH-Qu; Tue, 18 May 2004 16:29:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQATc-0006j9-Bf
	for ietf@optimus.ietf.org; Tue, 18 May 2004 15:42:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09788
	for <ietf@ietf.org>; Tue, 18 May 2004 15:42: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 1BQATa-0001yM-JJ
	for ietf@ietf.org; Tue, 18 May 2004 15:42:10 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQASd-0001vZ-00
	for ietf@ietf.org; Tue, 18 May 2004 15:41:12 -0400
Received: from 1-1-2-20b.rny.sth.bostream.se ([82.182.132.65] helo=klapautius.it.su.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQAS4-0001tO-00
	for ietf@ietf.org; Tue, 18 May 2004 15:40:36 -0400
Received: from it.su.se (localhost.localdomain [127.0.0.1])
	by klapautius.it.su.se (8.11.6/8.11.6) with ESMTP id i4IJdDl01285;
	Tue, 18 May 2004 21:39:13 +0200
Message-ID: <40AA6661.4000304@it.su.se>
Date: Tue, 18 May 2004 21:39:13 +0200
From: Leif Johansson <leifj@it.su.se>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: sv, en, en-us
MIME-Version: 1.0
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
CC: ietf@ietf.org
Subject: Re: 60th IETF - Registration
References: <DC55E4CF3BF32E46B6F1FA9028E35667626A@w3k.win3k.braintec-consult.de> <0b6001c43d05$f68ccd10$0402200a@consulintel.es>
In-Reply-To: <0b6001c43d05$f68ccd10$0402200a@consulintel.es>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: 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

JORDI PALET MARTINEZ wrote:
> I think is unacceptably TODAY, specially for IETF, that we should use a phone instead of on-line or email confirmation.
> 
> We should not accept hotels that don't make usage of technology to arrange our meetings.
> 
> We aren't asking the hotel (today) to support IPv6, but at least just IPv4 !
> 
> Regards,
> Jordi

Big hotels that are cheap and where the staff won't throw a fit
when we all turn up in force, laptops, duct-tape and all, don't
exactly grow on trees you know! I'm happy if it has a bar.

	MVH leifj

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



From ietf-admin@ietf.org  Tue May 18 17:22: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 RAA20014
	for <ietf-archive@ietf.org>; Tue, 18 May 2004 17:22: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 1BQC2Z-0005vW-7J
	for ietf-archive@ietf.org; Tue, 18 May 2004 17:22:23 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQC1p-0005rw-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 17:21:38 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQC1C-0005mL-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 17:20:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQBrb-0001sd-OG; Tue, 18 May 2004 17:11:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQBdD-0005Fd-7M
	for ietf@optimus.ietf.org; Tue, 18 May 2004 16:56: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 QAA17824
	for <ietf@ietf.org>; Tue, 18 May 2004 16:56: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 1BQBdA-0003NT-S4
	for ietf@ietf.org; Tue, 18 May 2004 16:56:08 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQBcG-0003Hx-00
	for ietf@ietf.org; Tue, 18 May 2004 16:55:13 -0400
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQBbQ-0003CM-00
	for ietf@ietf.org; Tue, 18 May 2004 16:54:20 -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 i4IKsJ7s020601;
	Tue, 18 May 2004 21:54:19 +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 VAA03915;
	Tue, 18 May 2004 21:54:19 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id i4IKsJk00624;
	Tue, 18 May 2004 21:54:19 +0100
Date: Tue, 18 May 2004 21:54:18 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: Leif Johansson <leifj@it.su.se>
Cc: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>, ietf@ietf.org
Subject: Re: 60th IETF - Registration
Message-ID: <20040518205418.GF31566@login.ecs.soton.ac.uk>
References: <DC55E4CF3BF32E46B6F1FA9028E35667626A@w3k.win3k.braintec-consult.de> <0b6001c43d05$f68ccd10$0402200a@consulintel.es> <40AA6661.4000304@it.su.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <40AA6661.4000304@it.su.se>
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 Tue, May 18, 2004 at 09:39:13PM +0200, Leif Johansson wrote:
> 
> Big hotels that are cheap and where the staff won't throw a fit
> when we all turn up in force, laptops, duct-tape and all, don't
> exactly grow on trees you know! I'm happy if it has a bar.

:)

All we need is 802.11beer, beer over WLAN.

Tim

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


From exim@www1.ietf.org  Tue May 18 17:30:35 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 RAA20376
	for <ietf-archive@odin.ietf.org>; Tue, 18 May 2004 17:30:35 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQC1D-0004ge-P1
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 17:20:59 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4ILKxrb018002
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 17:20:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQBrb-0001sd-OG; Tue, 18 May 2004 17:11:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQBdD-0005Fd-7M
	for ietf@optimus.ietf.org; Tue, 18 May 2004 16:56: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 QAA17824
	for <ietf@ietf.org>; Tue, 18 May 2004 16:56: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 1BQBdA-0003NT-S4
	for ietf@ietf.org; Tue, 18 May 2004 16:56:08 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQBcG-0003Hx-00
	for ietf@ietf.org; Tue, 18 May 2004 16:55:13 -0400
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQBbQ-0003CM-00
	for ietf@ietf.org; Tue, 18 May 2004 16:54:20 -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 i4IKsJ7s020601;
	Tue, 18 May 2004 21:54:19 +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 VAA03915;
	Tue, 18 May 2004 21:54:19 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id i4IKsJk00624;
	Tue, 18 May 2004 21:54:19 +0100
Date: Tue, 18 May 2004 21:54:18 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: Leif Johansson <leifj@it.su.se>
Cc: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>, ietf@ietf.org
Subject: Re: 60th IETF - Registration
Message-ID: <20040518205418.GF31566@login.ecs.soton.ac.uk>
References: <DC55E4CF3BF32E46B6F1FA9028E35667626A@w3k.win3k.braintec-consult.de> <0b6001c43d05$f68ccd10$0402200a@consulintel.es> <40AA6661.4000304@it.su.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <40AA6661.4000304@it.su.se>
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 Tue, May 18, 2004 at 09:39:13PM +0200, Leif Johansson wrote:
> 
> Big hotels that are cheap and where the staff won't throw a fit
> when we all turn up in force, laptops, duct-tape and all, don't
> exactly grow on trees you know! I'm happy if it has a bar.

:)

All we need is 802.11beer, beer over WLAN.

Tim

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



From ietf-admin@ietf.org  Tue May 18 18:00: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 SAA21966
	for <ietf-archive@ietf.org>; Tue, 18 May 2004 18:00: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 1BQCdF-0000bP-Cf
	for ietf-archive@ietf.org; Tue, 18 May 2004 18:00:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQCbE-0000IC-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 17:58:13 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQCZj-00006l-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 17:56:39 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQCUJ-0002Mx-75; Tue, 18 May 2004 17: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 1BQCJs-0000zO-9R
	for ietf@optimus.ietf.org; Tue, 18 May 2004 17:40: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 RAA20849
	for <ietf@ietf.org>; Tue, 18 May 2004 17:40: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 1BQCJp-00071t-Q5
	for ietf@ietf.org; Tue, 18 May 2004 17:40:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQCJ3-0006z6-00
	for ietf@ietf.org; Tue, 18 May 2004 17:39:26 -0400
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQCIV-0006tG-00
	for ietf@ietf.org; Tue, 18 May 2004 17:38:51 -0400
Received: from sj-core-1.cisco.com (171.71.177.237)
  by sj-iport-2.cisco.com with ESMTP; 18 May 2004 13:44:01 +0000
Received: from franklin.cisco.com (franklin.cisco.com [171.70.156.17])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i4ILcIC1026467;
	Tue, 18 May 2004 14:38:19 -0700 (PDT)
Received: from gwzw2k (dhcp-64-101-41-54.cisco.com [64.101.41.54]) by franklin.cisco.com (8.8.6 (PHNE_17190)/CISCO.SERVER.1.2) with ESMTP id OAA07731; Tue, 18 May 2004 14:38:18 -0700 (PDT)
Reply-To: <gwz@cisco.com>
From: "Glen Zorn" <gwz@cisco.com>
To: "'JORDI PALET MARTINEZ'" <jordi.palet@consulintel.es>, <ietf@ietf.org>
Subject: RE: 60th IETF - Registration
Date: Tue, 18 May 2004 14:37:39 -0700
Organization: Cisco Systems
Message-ID: <00a401c43d20$6bfbac00$36296540@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
In-Reply-To: <0b6001c43d05$f68ccd10$0402200a@consulintel.es>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
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

JORDI PALET MARTINEZ <mailto:jordi.palet@consulintel.es> writes:

> I think is unacceptably TODAY, specially for IETF, that we should use
> a phone instead of on-line or email confirmation. 
> 
> We should not accept hotels that don't make usage of technology to
> arrange our meetings. 

Are you expecting, perhaps, that they create a special Web page just for
us?

> 
> We aren't asking the hotel (today) to support IPv6, but at least just
> IPv4 ! 
> 
> Regards,
> Jordi
> 
> ----- Original Message -----
> From: "Hans Peter Dittler" <dittler@braintec-consult.de>
> To: "'Pekka Savola'" <pekkas@netcore.fi>; <ietf@ietf.org>
> Sent: Tuesday, May 18, 2004 8:32 AM
> Subject: AW: 60th IETF - Registration
> 
> 
>> Hi,
>> 
>>> The registration says the hotel is already full.  Is this for real
>>> -- 
>> 900 rooms already taken, within 11 hours??
>> 
>> no - there are rooms of all three kinds available if you call the
>> reservation-desk directly. (Phone: 1-619-291-2900 or 1-877-734-2726)
>> 
>> I just got my confirmation mail back from San Diego (8:23 MEZ =
>> 23:23 in San Diego) 
>> 
>> Peter
>> 
>> 
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www1.ietf.org/mailman/listinfo/ietf
>> 
> 
> 
> **********************************
> Madrid 2003 Global IPv6 Summit
> Presentations and videos on line at:
> http://www.ipv6-es.com
> 
> This electronic message contains information which may be privileged
> or confidential. The information is intended to be for the use of the
> individual(s) named above. If you are not the intended recipient be
> aware that any disclosure, copying, distribution or use of the
> contents of this information, including attached files, is
> prohibited.     
> 
> 
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf

Hope this helps,

~gwz

"They that can give up essential liberty to obtain a little temporary
safety deserve neither..." 
-- Benjamin Franklin, 1759

"It is forbidden to kill; therefore all murderers are punished unless
they kill in large numbers and to the sound of trumpets." 
-- Voltaire



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


From exim@www1.ietf.org  Tue May 18 18:12: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 SAA23553
	for <ietf-archive@odin.ietf.org>; Tue, 18 May 2004 18:12: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 1BQCZl-0003es-2S
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 17:56:42 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4ILufUE014063
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 17:56:41 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQCUJ-0002Mx-75; Tue, 18 May 2004 17: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 1BQCJs-0000zO-9R
	for ietf@optimus.ietf.org; Tue, 18 May 2004 17:40: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 RAA20849
	for <ietf@ietf.org>; Tue, 18 May 2004 17:40: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 1BQCJp-00071t-Q5
	for ietf@ietf.org; Tue, 18 May 2004 17:40:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQCJ3-0006z6-00
	for ietf@ietf.org; Tue, 18 May 2004 17:39:26 -0400
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQCIV-0006tG-00
	for ietf@ietf.org; Tue, 18 May 2004 17:38:51 -0400
Received: from sj-core-1.cisco.com (171.71.177.237)
  by sj-iport-2.cisco.com with ESMTP; 18 May 2004 13:44:01 +0000
Received: from franklin.cisco.com (franklin.cisco.com [171.70.156.17])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i4ILcIC1026467;
	Tue, 18 May 2004 14:38:19 -0700 (PDT)
Received: from gwzw2k (dhcp-64-101-41-54.cisco.com [64.101.41.54]) by franklin.cisco.com (8.8.6 (PHNE_17190)/CISCO.SERVER.1.2) with ESMTP id OAA07731; Tue, 18 May 2004 14:38:18 -0700 (PDT)
Reply-To: <gwz@cisco.com>
From: "Glen Zorn" <gwz@cisco.com>
To: "'JORDI PALET MARTINEZ'" <jordi.palet@consulintel.es>, <ietf@ietf.org>
Subject: RE: 60th IETF - Registration
Date: Tue, 18 May 2004 14:37:39 -0700
Organization: Cisco Systems
Message-ID: <00a401c43d20$6bfbac00$36296540@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
In-Reply-To: <0b6001c43d05$f68ccd10$0402200a@consulintel.es>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: 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

JORDI PALET MARTINEZ <mailto:jordi.palet@consulintel.es> writes:

> I think is unacceptably TODAY, specially for IETF, that we should use
> a phone instead of on-line or email confirmation. 
> 
> We should not accept hotels that don't make usage of technology to
> arrange our meetings. 

Are you expecting, perhaps, that they create a special Web page just for
us?

> 
> We aren't asking the hotel (today) to support IPv6, but at least just
> IPv4 ! 
> 
> Regards,
> Jordi
> 
> ----- Original Message -----
> From: "Hans Peter Dittler" <dittler@braintec-consult.de>
> To: "'Pekka Savola'" <pekkas@netcore.fi>; <ietf@ietf.org>
> Sent: Tuesday, May 18, 2004 8:32 AM
> Subject: AW: 60th IETF - Registration
> 
> 
>> Hi,
>> 
>>> The registration says the hotel is already full.  Is this for real
>>> -- 
>> 900 rooms already taken, within 11 hours??
>> 
>> no - there are rooms of all three kinds available if you call the
>> reservation-desk directly. (Phone: 1-619-291-2900 or 1-877-734-2726)
>> 
>> I just got my confirmation mail back from San Diego (8:23 MEZ =
>> 23:23 in San Diego) 
>> 
>> Peter
>> 
>> 
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www1.ietf.org/mailman/listinfo/ietf
>> 
> 
> 
> **********************************
> Madrid 2003 Global IPv6 Summit
> Presentations and videos on line at:
> http://www.ipv6-es.com
> 
> This electronic message contains information which may be privileged
> or confidential. The information is intended to be for the use of the
> individual(s) named above. If you are not the intended recipient be
> aware that any disclosure, copying, distribution or use of the
> contents of this information, including attached files, is
> prohibited.     
> 
> 
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf

Hope this helps,

~gwz

"They that can give up essential liberty to obtain a little temporary
safety deserve neither..." 
-- Benjamin Franklin, 1759

"It is forbidden to kill; therefore all murderers are punished unless
they kill in large numbers and to the sound of trumpets." 
-- Voltaire



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



From ietf-admin@ietf.org  Tue May 18 18:26: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 SAA24802
	for <ietf-archive@ietf.org>; Tue, 18 May 2004 18:26: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 1BQD2T-0002Wk-Re
	for ietf-archive@ietf.org; Tue, 18 May 2004 18:26:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQD1R-0002Q4-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 18:25:18 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQD0U-0002KR-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 18:24:18 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQCqZ-0003pv-T1; Tue, 18 May 2004 18:14:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQCeu-0004uT-Oj
	for ietf@optimus.ietf.org; Tue, 18 May 2004 18:02: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 SAA22416
	for <ietf@ietf.org>; Tue, 18 May 2004 18:01: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 1BQCer-0000mJ-Tv
	for ietf@ietf.org; Tue, 18 May 2004 18:01:58 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQCcs-0000Y5-00
	for ietf@ietf.org; Tue, 18 May 2004 17:59:56 -0400
Received: from mail.consulintel.es ([213.172.48.142] helo=consulintel.es)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQCas-0000AS-00
	for ietf@ietf.org; Tue, 18 May 2004 17:57:50 -0400
Received: from consulintel02 ([212.76.240.58])
	(authenticated user jordi.palet@consulintel.es)
	by consulintel.es (consulintel.es [127.0.0.1])
	(MDaemon.PRO.v7.0.1.R)
	with ESMTP id md50000103481.msg
	for <ietf@ietf.org>; Tue, 18 May 2004 23:58:26 +0200
Message-ID: <0ee201c43d23$074998f0$0402200a@consulintel.es>
Reply-To: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
From: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
References: <00a401c43d20$6bfbac00$36296540@amer.cisco.com>
Subject: Re: 60th IETF - Registration
Date: Tue, 18 May 2004 23:56:28 +0200
Organization: Consulintel
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Spam-Processed: consulintel.es, Tue, 18 May 2004 23:58:26 +0200
	(not processed: message from valid local sender)
X-MDRemoteIP: 212.76.240.58
X-Return-Path: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
X-MDAV-Processed: consulintel.es, Tue, 18 May 2004 23:58:27 +0200
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

Not really.  They have a site that already supports this, should work, but is not working for a couple of days ... and some of us travel and don't have extra time neither resources (already using our personal time and paying our expenses for IETF from our own pocket) to use phone or fax when it could be done by email or on-line.

We should also remember that the people don't comes just from US. When I called they (not very kindly) suggested me if I can call back in 6 hours (!!!!!) because registration services doesn't work so early. Incredible, this is having fun and supporting international guests. Just quality, hopefully not the same we will get when we are in the meeting.

Anyway, if they want the business, they should make sure that this is working and I'm sure IETF Secretariat is kind to take care of those small details in order to facilitate the participation of the people.

Of course, is only my opinion ... but is comparable as having our web site supporting IPv6 ... is surprising to me that we don't make sure to use our own protocols and show to the rest of the world that what we do, just works. I recall something about "running code" ;-) ?

Regards,
Jordi


----- Original Message -----=20
From: "Glen Zorn" <gwz@cisco.com>
To: "'JORDI PALET MARTINEZ'" <jordi.palet@consulintel.es>; <ietf@ietf.org>
Sent: Tuesday, May 18, 2004 11:37 PM
Subject: RE: 60th IETF - Registration


> JORDI PALET MARTINEZ <mailto:jordi.palet@consulintel.es> writes:
>=20
> > I think is unacceptably TODAY, specially for IETF, that we should use
> > a phone instead of on-line or email confirmation.=20
> >=20
> > We should not accept hotels that don't make usage of technology to
> > arrange our meetings.=20
>=20
> Are you expecting, perhaps, that they create a special Web page just for
> us?
>=20
> >=20
> > We aren't asking the hotel (today) to support IPv6, but at least just
> > IPv4 !=20
> >=20
> > Regards,
> > Jordi
> >=20
> > ----- Original Message -----
> > From: "Hans Peter Dittler" <dittler@braintec-consult.de>
> > To: "'Pekka Savola'" <pekkas@netcore.fi>; <ietf@ietf.org>
> > Sent: Tuesday, May 18, 2004 8:32 AM
> > Subject: AW: 60th IETF - Registration
> >=20
> >=20
> >> Hi,
> >>=20
> >>> The registration says the hotel is already full.  Is this for real
> >>> --=20
> >> 900 rooms already taken, within 11 hours??
> >>=20
> >> no - there are rooms of all three kinds available if you call the
> >> reservation-desk directly. (Phone: 1-619-291-2900 or 1-877-734-2726)
> >>=20
> >> I just got my confirmation mail back from San Diego (8:23 MEZ =3D
> >> 23:23 in San Diego)=20
> >>=20
> >> Peter
> >>=20
> >>=20
> >> _______________________________________________
> >> Ietf mailing list
> >> Ietf@ietf.org
> >> https://www1.ietf.org/mailman/listinfo/ietf
> >>=20
> >=20
> >=20
> > **********************************
> > Madrid 2003 Global IPv6 Summit
> > Presentations and videos on line at:
> > http://www.ipv6-es.com
> >=20
> > This electronic message contains information which may be privileged
> > or confidential. The information is intended to be for the use of the
> > individual(s) named above. If you are not the intended recipient be
> > aware that any disclosure, copying, distribution or use of the
> > contents of this information, including attached files, is
> > prohibited.    =20
> >=20
> >=20
> >=20
> >=20
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www1.ietf.org/mailman/listinfo/ietf
>=20
> Hope this helps,
>=20
> ~gwz
>=20
> "They that can give up essential liberty to obtain a little temporary
> safety deserve neither..."=20
> -- Benjamin Franklin, 1759
>=20
> "It is forbidden to kill; therefore all murderers are punished unless
> they kill in large numbers and to the sound of trumpets."=20
> -- Voltaire
>=20
>=20
>=20


**********************************
Madrid 2003 Global IPv6 Summit
Presentations and videos on line at:
http://www.ipv6-es.com

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.




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


From ietf-admin@ietf.org  Tue May 18 18:27: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 SAA24883
	for <ietf-archive@ietf.org>; Tue, 18 May 2004 18:27: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 1BQD3S-0002dj-Sn
	for ietf-archive@ietf.org; Tue, 18 May 2004 18:27:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQD2g-0002YM-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 18:26:34 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQD1k-0002SV-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 18:25:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQCqk-0003uZ-3B; Tue, 18 May 2004 18:14:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQCnp-0001jb-NW
	for ietf@optimus.ietf.org; Tue, 18 May 2004 18:11:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23457
	for <ietf@ietf.org>; Tue, 18 May 2004 18:11:09 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQCnm-0001Q5-QY
	for ietf@ietf.org; Tue, 18 May 2004 18:11:10 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQCmw-0001NK-00
	for ietf@ietf.org; Tue, 18 May 2004 18:10:18 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQCmH-0001Jj-00
	for ietf@ietf.org; Tue, 18 May 2004 18:09:37 -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 i4IM9A1C083187;
	Wed, 19 May 2004 00:09:10 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <200405180108.i4I18tX00714@boreas.isi.edu>
References: <200405180108.i4I18tX00714@boreas.isi.edu>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <063E0695-A918-11D8-8097-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org ('Internet Engineering Task Force')
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: Root Anycast
Date: Wed, 19 May 2004 00:09:25 +0200
To: Bill Manning <bmanning@ISI.EDU>
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 18-mei-04, at 3:08, Bill Manning wrote:

> 	None (to my knowledge) of the roots have a consistant view of
> 	a shared anycast vision, so you should not read too much into
> 	the summaries found in the RSSAC notes.

Which is exactly the problem.

> % It seems to me that any design that makes the root addresses seem as
> % distributed around the net as possible would be optimal, as in this
> % case the changes of an outage triggering rerouting of a large number 
> of
> % root addresses is as small as possible. In order to do this, the 
> number
> % of root addresses that are available within a geographic region 
> (where
> % "region" < RIR region) should be limited.

> 	Er... geography != network topology.

So people keep telling me...

In reality, geography is a decent predictor of round trip time, 
although the relationship isn't a simple linear one. (Ie, I can predict 
that I'll have an RTT of around 250 ms to most Japanese destinations 
and around 150 ms to most Californian destinations, even though I'm 
closer to Japan than to California.)


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


From exim@www1.ietf.org  Tue May 18 18:31: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 SAA25196
	for <ietf-archive@odin.ietf.org>; Tue, 18 May 2004 18:31: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 1BQD0W-0008EK-PA
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 18:24:20 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4IMOK2J031634
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 18: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 1BQCqZ-0003pv-T1; Tue, 18 May 2004 18:14:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQCeu-0004uT-Oj
	for ietf@optimus.ietf.org; Tue, 18 May 2004 18:02: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 SAA22416
	for <ietf@ietf.org>; Tue, 18 May 2004 18:01: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 1BQCer-0000mJ-Tv
	for ietf@ietf.org; Tue, 18 May 2004 18:01:58 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQCcs-0000Y5-00
	for ietf@ietf.org; Tue, 18 May 2004 17:59:56 -0400
Received: from mail.consulintel.es ([213.172.48.142] helo=consulintel.es)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQCas-0000AS-00
	for ietf@ietf.org; Tue, 18 May 2004 17:57:50 -0400
Received: from consulintel02 ([212.76.240.58])
	(authenticated user jordi.palet@consulintel.es)
	by consulintel.es (consulintel.es [127.0.0.1])
	(MDaemon.PRO.v7.0.1.R)
	with ESMTP id md50000103481.msg
	for <ietf@ietf.org>; Tue, 18 May 2004 23:58:26 +0200
Message-ID: <0ee201c43d23$074998f0$0402200a@consulintel.es>
Reply-To: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
From: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
References: <00a401c43d20$6bfbac00$36296540@amer.cisco.com>
Subject: Re: 60th IETF - Registration
Date: Tue, 18 May 2004 23:56:28 +0200
Organization: Consulintel
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Spam-Processed: consulintel.es, Tue, 18 May 2004 23:58:26 +0200
	(not processed: message from valid local sender)
X-MDRemoteIP: 212.76.240.58
X-Return-Path: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
X-MDAV-Processed: consulintel.es, Tue, 18 May 2004 23:58:27 +0200
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-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

Not really.  They have a site that already supports this, should work, but is not working for a couple of days ... and some of us travel and don't have extra time neither resources (already using our personal time and paying our expenses for IETF from our own pocket) to use phone or fax when it could be done by email or on-line.

We should also remember that the people don't comes just from US. When I called they (not very kindly) suggested me if I can call back in 6 hours (!!!!!) because registration services doesn't work so early. Incredible, this is having fun and supporting international guests. Just quality, hopefully not the same we will get when we are in the meeting.

Anyway, if they want the business, they should make sure that this is working and I'm sure IETF Secretariat is kind to take care of those small details in order to facilitate the participation of the people.

Of course, is only my opinion ... but is comparable as having our web site supporting IPv6 ... is surprising to me that we don't make sure to use our own protocols and show to the rest of the world that what we do, just works. I recall something about "running code" ;-) ?

Regards,
Jordi


----- Original Message -----=20
From: "Glen Zorn" <gwz@cisco.com>
To: "'JORDI PALET MARTINEZ'" <jordi.palet@consulintel.es>; <ietf@ietf.org>
Sent: Tuesday, May 18, 2004 11:37 PM
Subject: RE: 60th IETF - Registration


> JORDI PALET MARTINEZ <mailto:jordi.palet@consulintel.es> writes:
>=20
> > I think is unacceptably TODAY, specially for IETF, that we should use
> > a phone instead of on-line or email confirmation.=20
> >=20
> > We should not accept hotels that don't make usage of technology to
> > arrange our meetings.=20
>=20
> Are you expecting, perhaps, that they create a special Web page just for
> us?
>=20
> >=20
> > We aren't asking the hotel (today) to support IPv6, but at least just
> > IPv4 !=20
> >=20
> > Regards,
> > Jordi
> >=20
> > ----- Original Message -----
> > From: "Hans Peter Dittler" <dittler@braintec-consult.de>
> > To: "'Pekka Savola'" <pekkas@netcore.fi>; <ietf@ietf.org>
> > Sent: Tuesday, May 18, 2004 8:32 AM
> > Subject: AW: 60th IETF - Registration
> >=20
> >=20
> >> Hi,
> >>=20
> >>> The registration says the hotel is already full.  Is this for real
> >>> --=20
> >> 900 rooms already taken, within 11 hours??
> >>=20
> >> no - there are rooms of all three kinds available if you call the
> >> reservation-desk directly. (Phone: 1-619-291-2900 or 1-877-734-2726)
> >>=20
> >> I just got my confirmation mail back from San Diego (8:23 MEZ =3D
> >> 23:23 in San Diego)=20
> >>=20
> >> Peter
> >>=20
> >>=20
> >> _______________________________________________
> >> Ietf mailing list
> >> Ietf@ietf.org
> >> https://www1.ietf.org/mailman/listinfo/ietf
> >>=20
> >=20
> >=20
> > **********************************
> > Madrid 2003 Global IPv6 Summit
> > Presentations and videos on line at:
> > http://www.ipv6-es.com
> >=20
> > This electronic message contains information which may be privileged
> > or confidential. The information is intended to be for the use of the
> > individual(s) named above. If you are not the intended recipient be
> > aware that any disclosure, copying, distribution or use of the
> > contents of this information, including attached files, is
> > prohibited.    =20
> >=20
> >=20
> >=20
> >=20
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www1.ietf.org/mailman/listinfo/ietf
>=20
> Hope this helps,
>=20
> ~gwz
>=20
> "They that can give up essential liberty to obtain a little temporary
> safety deserve neither..."=20
> -- Benjamin Franklin, 1759
>=20
> "It is forbidden to kill; therefore all murderers are punished unless
> they kill in large numbers and to the sound of trumpets."=20
> -- Voltaire
>=20
>=20
>=20


**********************************
Madrid 2003 Global IPv6 Summit
Presentations and videos on line at:
http://www.ipv6-es.com

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.




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



From ietf-admin@ietf.org  Tue May 18 18:48: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 SAA26046
	for <ietf-archive@ietf.org>; Tue, 18 May 2004 18:48: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 1BQDNb-00047q-7p
	for ietf-archive@ietf.org; Tue, 18 May 2004 18:48:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQDMf-00044I-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 18:47:14 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQDLv-00041n-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 18:46:27 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQD6A-0000rZ-LB; Tue, 18 May 2004 18: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 1BQCva-0006JI-IF
	for ietf@optimus.ietf.org; Tue, 18 May 2004 18:19:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24404
	for <ietf@ietf.org>; Tue, 18 May 2004 18:19: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 1BQCvX-0001yn-FY
	for ietf@ietf.org; Tue, 18 May 2004 18:19:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQCup-0001wd-00
	for ietf@ietf.org; Tue, 18 May 2004 18:18:28 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQCuE-0001sp-00
	for ietf@ietf.org; Tue, 18 May 2004 18:17:50 -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 i4IMHO1C083289;
	Wed, 19 May 2004 00:17:26 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <g3lljqegi6.fsf@sa.vix.com>
References: <DFC3BD05-A84A-11D8-AC18-000A95CD987A@muada.com> <g3lljqegi6.fsf@sa.vix.com>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <2CCC734E-A919-11D8-8097-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: Root Anycast
Date: Wed, 19 May 2004 00:17:39 +0200
To: Paul Vixie <vixie@vix.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 18-mei-04, at 2:16, Paul Vixie wrote:

>> Unicast: A, E, H, L
>> Anycast: B, C, D, F, G, I, J, K, M (now or planned)

>> The thing that worries me is that apparently, there is no policy about
>> this whatsoever, the root operators each get to decide what they want
>> to do.

> The table is round.  Policies are discussed as a group but set 
> individually.
> The result is a service which has never been "down hard", not ever, 
> not for
> any millisecond out of the last 15 years.  This is "strength by 
> diversity."

I applaud diversity. The point of my message was that it would be 
harmful if all root servers would all act alike and therefore suffer 
from the same unreachability problems seen from a certain place in the 
net if there is an outage.

However, diversity and lack of policy aren't the same thing. If the 
root operators didn't communicate, it would be possible for all of them 
to select the same DNS server software. That would be a bad thing. The 
anycast issue is similar.

>> The fact that .org is run using only two anycast addresses also 
>> indicates
>> that apparently the ICANN doesn't feel the need to throw their weight
>> around in this area.

> Apparently you have your facts wrong about how much sway ICANN had 
> about
> the anycasting of .ORG, but those details aren't mine, let others 
> speak.

I find this peculiar as ICANN imposes a heavy set of requirements on 
people who want new TLDs, why can't they do the same for existing ones? 
(This is a rhetorical question.)

>> Now obviously anycasting is a very useful mechanism to reduce latency
>> and increase capacity and robustness. However, these properties are
>> best served by careful design rather than organic growth.

> Careful design by whom?

Anyone.

> Organic compared to what?

Compared to purposeful design.

> I assure you that f-root has grown by careful design.

I know the root operators are very responsible people and do a great 
job.

However, I'm not convinced that 13 great parts automatically make a 
great whole.

>> If we consider the number of actual servers/server clusters and the
>> number of root IP addresses as given, there are still many ways to 
>> skin
>> this cat.  One would be using 12 unicast servers and anycast just one
>> address.

> Who is "we", though?  That's always the excluded middle of this debate.

I didn't have a specific "we" in mind, but let's make it the internet 
engineering community. I'm not saying we should make these decisions 
during the IETF plenary (or on this mailinglist for that matter) but I 
do believe someone has to do something. The strength of the IETF is 
that its results generally reflect the collective wisdom and support of 
the participants. (The weakness that many great things that don't have 
this support don't get done, but that's another issue.)

>> It seems to me that any design that makes the root addresses seem as
>> distributed around the net as possible would be optimal, as in this
>> case the changes of an outage triggering rerouting of a large number 
>> of
>> root addresses is as small as possible. In order to do this, the 
>> number
>> of root addresses that are available within a geographic region (where
>> "region" < RIR region) should be limited.

> In counterpoint, it seems to me that any unified design will make the 
> system
> subject to monoculture attacks or ISO-L9 capture, and that the current
> system which you call "unplanned and organic" (but which is actually 
> just
> "diversity by credo") yields a stronger system overall.

I was only talking about a design for root anycasting. I'm sorry if 
this wasn't clear.

>> (Just having the roots close is of little value: good recursive 
>> servers
>> hone in to the one with the lowest RTT anyway, so having one close by
>> is enough. However, when this one fails it's important that after the
>> timeout, the next root address that the recursive server tries is
>> highly likely to be reachable, in order to avoid stacking timeout upon
>> timeout.

> What would help overall DNS robustness would be if more DNS clients 
> used
> recursion,

This is certainly true, but I find it unfortunate that you skip over my 
point. It's easy to claim 100% uptime when sitting 10 meters from a 
server, but it's what real users see that counts. From that viewpoint, 
the root servers have certainly experienced service level degredations 
in the past 15 years. Good anycast design rather than just let it 
happen can minimize this in the future.

> and cached what they heard (both positive and negative).  A
> frightfully large (and growing) segment of the client population always
> walks from the top down (I guess these are worms or viruses or 
> whatever)
> and another growing/frightful segment asks the same question hundreds 
> of
> times a minute and doesn't seem to care whether the response is 
> positive or
> negative, only that it has to arrive so that the (lockstepped) next 
> (same)
> query can be sent.

I feel your pain, but unfortunately the IETF isn't in the position to 
do anything against bad protocol implementations, even the ones that 
aren't part of software that's illegal in most jurisdictions in the 
first place.

Still, this problem once again proves my point that we really need a 
mechanism that allows receivers to stop malicious traffic from reaching 
them.


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


From exim@www1.ietf.org  Tue May 18 18:56: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 SAA26264
	for <ietf-archive@odin.ietf.org>; Tue, 18 May 2004 18:56: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 1BQDLx-00040m-Sz
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 18:46:30 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4IMkTji015413
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 18:46:29 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQD6A-0000rZ-LB; Tue, 18 May 2004 18: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 1BQCva-0006JI-IF
	for ietf@optimus.ietf.org; Tue, 18 May 2004 18:19:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24404
	for <ietf@ietf.org>; Tue, 18 May 2004 18:19: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 1BQCvX-0001yn-FY
	for ietf@ietf.org; Tue, 18 May 2004 18:19:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQCup-0001wd-00
	for ietf@ietf.org; Tue, 18 May 2004 18:18:28 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQCuE-0001sp-00
	for ietf@ietf.org; Tue, 18 May 2004 18:17:50 -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 i4IMHO1C083289;
	Wed, 19 May 2004 00:17:26 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <g3lljqegi6.fsf@sa.vix.com>
References: <DFC3BD05-A84A-11D8-AC18-000A95CD987A@muada.com> <g3lljqegi6.fsf@sa.vix.com>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <2CCC734E-A919-11D8-8097-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: Root Anycast
Date: Wed, 19 May 2004 00:17:39 +0200
To: Paul Vixie <vixie@vix.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 18-mei-04, at 2:16, Paul Vixie wrote:

>> Unicast: A, E, H, L
>> Anycast: B, C, D, F, G, I, J, K, M (now or planned)

>> The thing that worries me is that apparently, there is no policy about
>> this whatsoever, the root operators each get to decide what they want
>> to do.

> The table is round.  Policies are discussed as a group but set 
> individually.
> The result is a service which has never been "down hard", not ever, 
> not for
> any millisecond out of the last 15 years.  This is "strength by 
> diversity."

I applaud diversity. The point of my message was that it would be 
harmful if all root servers would all act alike and therefore suffer 
from the same unreachability problems seen from a certain place in the 
net if there is an outage.

However, diversity and lack of policy aren't the same thing. If the 
root operators didn't communicate, it would be possible for all of them 
to select the same DNS server software. That would be a bad thing. The 
anycast issue is similar.

>> The fact that .org is run using only two anycast addresses also 
>> indicates
>> that apparently the ICANN doesn't feel the need to throw their weight
>> around in this area.

> Apparently you have your facts wrong about how much sway ICANN had 
> about
> the anycasting of .ORG, but those details aren't mine, let others 
> speak.

I find this peculiar as ICANN imposes a heavy set of requirements on 
people who want new TLDs, why can't they do the same for existing ones? 
(This is a rhetorical question.)

>> Now obviously anycasting is a very useful mechanism to reduce latency
>> and increase capacity and robustness. However, these properties are
>> best served by careful design rather than organic growth.

> Careful design by whom?

Anyone.

> Organic compared to what?

Compared to purposeful design.

> I assure you that f-root has grown by careful design.

I know the root operators are very responsible people and do a great 
job.

However, I'm not convinced that 13 great parts automatically make a 
great whole.

>> If we consider the number of actual servers/server clusters and the
>> number of root IP addresses as given, there are still many ways to 
>> skin
>> this cat.  One would be using 12 unicast servers and anycast just one
>> address.

> Who is "we", though?  That's always the excluded middle of this debate.

I didn't have a specific "we" in mind, but let's make it the internet 
engineering community. I'm not saying we should make these decisions 
during the IETF plenary (or on this mailinglist for that matter) but I 
do believe someone has to do something. The strength of the IETF is 
that its results generally reflect the collective wisdom and support of 
the participants. (The weakness that many great things that don't have 
this support don't get done, but that's another issue.)

>> It seems to me that any design that makes the root addresses seem as
>> distributed around the net as possible would be optimal, as in this
>> case the changes of an outage triggering rerouting of a large number 
>> of
>> root addresses is as small as possible. In order to do this, the 
>> number
>> of root addresses that are available within a geographic region (where
>> "region" < RIR region) should be limited.

> In counterpoint, it seems to me that any unified design will make the 
> system
> subject to monoculture attacks or ISO-L9 capture, and that the current
> system which you call "unplanned and organic" (but which is actually 
> just
> "diversity by credo") yields a stronger system overall.

I was only talking about a design for root anycasting. I'm sorry if 
this wasn't clear.

>> (Just having the roots close is of little value: good recursive 
>> servers
>> hone in to the one with the lowest RTT anyway, so having one close by
>> is enough. However, when this one fails it's important that after the
>> timeout, the next root address that the recursive server tries is
>> highly likely to be reachable, in order to avoid stacking timeout upon
>> timeout.

> What would help overall DNS robustness would be if more DNS clients 
> used
> recursion,

This is certainly true, but I find it unfortunate that you skip over my 
point. It's easy to claim 100% uptime when sitting 10 meters from a 
server, but it's what real users see that counts. From that viewpoint, 
the root servers have certainly experienced service level degredations 
in the past 15 years. Good anycast design rather than just let it 
happen can minimize this in the future.

> and cached what they heard (both positive and negative).  A
> frightfully large (and growing) segment of the client population always
> walks from the top down (I guess these are worms or viruses or 
> whatever)
> and another growing/frightful segment asks the same question hundreds 
> of
> times a minute and doesn't seem to care whether the response is 
> positive or
> negative, only that it has to arrive so that the (lockstepped) next 
> (same)
> query can be sent.

I feel your pain, but unfortunately the IETF isn't in the position to 
do anything against bad protocol implementations, even the ones that 
aren't part of software that's illegal in most jurisdictions in the 
first place.

Still, this problem once again proves my point that we really need a 
mechanism that allows receivers to stop malicious traffic from reaching 
them.


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



From ietf-admin@ietf.org  Tue May 18 18:59: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 SAA26403
	for <ietf-archive@ietf.org>; Tue, 18 May 2004 18:59: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 1BQDYJ-0004nJ-Hw
	for ietf-archive@ietf.org; Tue, 18 May 2004 18:59:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQDXH-0004fD-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 18:58:12 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQDWM-0004aI-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 18:57:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQDPU-0004Rt-Jn; Tue, 18 May 2004 18:50:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQDEx-0002le-Op
	for ietf@optimus.ietf.org; Tue, 18 May 2004 18:39: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 SAA25664
	for <ietf@ietf.org>; Tue, 18 May 2004 18:39: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 1BQDEu-0003Ve-Jx
	for ietf@ietf.org; Tue, 18 May 2004 18:39:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQDDw-0003TK-00
	for ietf@ietf.org; Tue, 18 May 2004 18:38:13 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQDDN-0003PB-00
	for ietf@ietf.org; Tue, 18 May 2004 18:37:37 -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 i4IMavAI022913
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 18 May 2004 18:37:00 -0400
Date: Tue, 18 May 2004 18:36:57 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Harald Tveit Alvestrand <harald@alvestrand.no>
cc: ietf@ietf.org
Subject: Re: [dnsop] Re: Complaint on abuse of DNSOP lists
In-Reply-To: <g3pt92eifn.fsf@sa.vix.com>
Message-ID: <Pine.LNX.4.44.0405181819200.22463-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

Sigh. 

Harald, Please add __Another__ complaint to the chair about inappropriate
behavior by Mr. Vixie.

Oh wait, could it be that lying to the general public saying our address
space is hijacked is a personal attack?  Hmm.  Maybe they aren't as
'perfessional' as they made out to be.  Maybe these attacks aren't as
unrelated to the IETF as the Chair asserts.

I guess those that have to resort to name-calling don't have anything else
ot resort to, since they can't resort to facts.  And of course, indeed, no
contrary _facts_ have been given. Well, Vixie hasn't changed in 15 years,
still as infantile as ever.

And these irresponsible and immature people have operational control of a
root nameserver.  How did that ever happen?  That too, should be changed.

		--Dean

On 17 May 2004, Paul Vixie wrote:

> dean@av8.com (Dean Anderson) writes:
> 
> > ... For the less technical, an exchange point is ...
> 
> I don't think there's anyone on this list less technical than you, Dean.
> 




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


From exim@www1.ietf.org  Tue May 18 19:06:21 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 TAA26791
	for <ietf-archive@odin.ietf.org>; Tue, 18 May 2004 19:06:21 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQDWP-0006ke-4S
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 18:57:22 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4IMvH1Q025919
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 18:57:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQDPU-0004Rt-Jn; Tue, 18 May 2004 18:50:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQDEx-0002le-Op
	for ietf@optimus.ietf.org; Tue, 18 May 2004 18:39: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 SAA25664
	for <ietf@ietf.org>; Tue, 18 May 2004 18:39: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 1BQDEu-0003Ve-Jx
	for ietf@ietf.org; Tue, 18 May 2004 18:39:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQDDw-0003TK-00
	for ietf@ietf.org; Tue, 18 May 2004 18:38:13 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQDDN-0003PB-00
	for ietf@ietf.org; Tue, 18 May 2004 18:37:37 -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 i4IMavAI022913
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 18 May 2004 18:37:00 -0400
Date: Tue, 18 May 2004 18:36:57 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Harald Tveit Alvestrand <harald@alvestrand.no>
cc: ietf@ietf.org
Subject: Re: [dnsop] Re: Complaint on abuse of DNSOP lists
In-Reply-To: <g3pt92eifn.fsf@sa.vix.com>
Message-ID: <Pine.LNX.4.44.0405181819200.22463-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>

Sigh. 

Harald, Please add __Another__ complaint to the chair about inappropriate
behavior by Mr. Vixie.

Oh wait, could it be that lying to the general public saying our address
space is hijacked is a personal attack?  Hmm.  Maybe they aren't as
'perfessional' as they made out to be.  Maybe these attacks aren't as
unrelated to the IETF as the Chair asserts.

I guess those that have to resort to name-calling don't have anything else
ot resort to, since they can't resort to facts.  And of course, indeed, no
contrary _facts_ have been given. Well, Vixie hasn't changed in 15 years,
still as infantile as ever.

And these irresponsible and immature people have operational control of a
root nameserver.  How did that ever happen?  That too, should be changed.

		--Dean

On 17 May 2004, Paul Vixie wrote:

> dean@av8.com (Dean Anderson) writes:
> 
> > ... For the less technical, an exchange point is ...
> 
> I don't think there's anyone on this list less technical than you, Dean.
> 




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



From ietf-admin@ietf.org  Tue May 18 19:09: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 TAA26899
	for <ietf-archive@ietf.org>; Tue, 18 May 2004 19:09: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 1BQDi3-0005T4-Si
	for ietf-archive@ietf.org; Tue, 18 May 2004 19:09:19 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQDhE-0005Pg-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 19:08:28 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQDgY-0005Li-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 19:07:46 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQDY7-0007Gk-8J; Tue, 18 May 2004 18:59:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQDTP-0005eo-Sg
	for ietf@optimus.ietf.org; Tue, 18 May 2004 18:54: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 SAA26210
	for <ietf@ietf.org>; Tue, 18 May 2004 18:54: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 1BQDTM-0004PX-Lc
	for ietf@ietf.org; Tue, 18 May 2004 18:54:08 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQDSO-0004Nr-00
	for ietf@ietf.org; Tue, 18 May 2004 18:53:08 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQDS4-0004ML-00
	for ietf@ietf.org; Tue, 18 May 2004 18:52:49 -0400
Received: from sj-core-1.cisco.com (171.71.177.237)
  by sj-iport-5.cisco.com with ESMTP; 18 May 2004 15:51:59 -0700
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i4IMqGC1024595;
	Tue, 18 May 2004 15:52:16 -0700 (PDT)
Received: from cisco.com ([10.25.65.178])
	by mira-sjc5-c.cisco.com (MOS 3.4.5-GR)
	with SMTP id AUG20987;
	Tue, 18 May 2004 15:52:15 -0700 (PDT)
Date: Tue, 18 May 2004 18:52:11 -0400
Subject: Re: 60th IETF - Registration
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v553)
Cc: <ietf@ietf.org>
To: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
From: Melinda Shore <mshore@cisco.com>
In-Reply-To: <0ee201c43d23$074998f0$0402200a@consulintel.es>
Message-Id: <FF68C3C2-A91D-11D8-8468-000A95E35274@cisco.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.553)
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 Tuesday, May 18, 2004, at 05:56 PM, JORDI PALET MARTINEZ wrote:
> We should also remember that the people don't comes just from US. When 
> I called they (not very kindly) suggested me if I can call back in 6 
> hours (!!!!!) because registration services doesn't work so early. 
> Incredible, this is having fun and supporting international guests.

Fax should take care of it.

Obviously it would be preferable to be able to make reservations online.
That we can't is an inconvenience, but a minor one with several 
alternative
mechanisms for making reservations available.

I'm somewhat more concerned about small meeting rooms given our last
experience in the hotel, but maybe with attendance down it won't be a
problem.

Melinda


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


From exim@www1.ietf.org  Tue May 18 19:22: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 TAA27313
	for <ietf-archive@odin.ietf.org>; Tue, 18 May 2004 19:22: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 1BQDgb-0000bw-CV
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 19:07:49 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4IN7nvw002320
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 19:07:49 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQDY7-0007Gk-8J; Tue, 18 May 2004 18:59:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQDTP-0005eo-Sg
	for ietf@optimus.ietf.org; Tue, 18 May 2004 18:54: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 SAA26210
	for <ietf@ietf.org>; Tue, 18 May 2004 18:54: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 1BQDTM-0004PX-Lc
	for ietf@ietf.org; Tue, 18 May 2004 18:54:08 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQDSO-0004Nr-00
	for ietf@ietf.org; Tue, 18 May 2004 18:53:08 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQDS4-0004ML-00
	for ietf@ietf.org; Tue, 18 May 2004 18:52:49 -0400
Received: from sj-core-1.cisco.com (171.71.177.237)
  by sj-iport-5.cisco.com with ESMTP; 18 May 2004 15:51:59 -0700
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i4IMqGC1024595;
	Tue, 18 May 2004 15:52:16 -0700 (PDT)
Received: from cisco.com ([10.25.65.178])
	by mira-sjc5-c.cisco.com (MOS 3.4.5-GR)
	with SMTP id AUG20987;
	Tue, 18 May 2004 15:52:15 -0700 (PDT)
Date: Tue, 18 May 2004 18:52:11 -0400
Subject: Re: 60th IETF - Registration
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v553)
Cc: <ietf@ietf.org>
To: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
From: Melinda Shore <mshore@cisco.com>
In-Reply-To: <0ee201c43d23$074998f0$0402200a@consulintel.es>
Message-Id: <FF68C3C2-A91D-11D8-8468-000A95E35274@cisco.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.553)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: 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 Tuesday, May 18, 2004, at 05:56 PM, JORDI PALET MARTINEZ wrote:
> We should also remember that the people don't comes just from US. When 
> I called they (not very kindly) suggested me if I can call back in 6 
> hours (!!!!!) because registration services doesn't work so early. 
> Incredible, this is having fun and supporting international guests.

Fax should take care of it.

Obviously it would be preferable to be able to make reservations online.
That we can't is an inconvenience, but a minor one with several 
alternative
mechanisms for making reservations available.

I'm somewhat more concerned about small meeting rooms given our last
experience in the hotel, but maybe with attendance down it won't be a
problem.

Melinda


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



From ietf-admin@ietf.org  Tue May 18 19:23: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 TAA27350
	for <ietf-archive@ietf.org>; Tue, 18 May 2004 19:23: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 1BQDvR-0006LO-Vb
	for ietf-archive@ietf.org; Tue, 18 May 2004 19:23:10 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQDuS-0006EP-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 19:22:09 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQDtV-00068Q-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 19:21:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQDer-0008Kj-Q6; Tue, 18 May 2004 19:06:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQDWL-0006g8-RX
	for ietf@optimus.ietf.org; Tue, 18 May 2004 18:57:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26302
	for <ietf@ietf.org>; Tue, 18 May 2004 18:57: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 1BQDWI-0004Zd-Lj
	for ietf@ietf.org; Tue, 18 May 2004 18:57:10 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQDVP-0004VA-00
	for ietf@ietf.org; Tue, 18 May 2004 18:56:15 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQDUV-0004Q9-00
	for ietf@ietf.org; Tue, 18 May 2004 18:55:19 -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 i4IMsnv1023188
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 18 May 2004 18:54:49 -0400
Date: Tue, 18 May 2004 18:54:49 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Paul Vixie <vixie@vix.com>
cc: ietf@ietf.org
Subject: Re: Root Anycast
In-Reply-To: <g3lljqegi6.fsf@sa.vix.com>
Message-ID: <Pine.LNX.4.44.0405181841330.22463-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 18 May 2004, Paul Vixie wrote:

> The result is a service which has never been "down hard", not ever, not for
> any millisecond out of the last 15 years.  This is "strength by diversity."

This isn't quite true. There have been multiple server failures. And if I
recall, I think that there have been quite a few servers (like 12 of 13)  
that have been down at one time in this timeframe.

But I haven't been keeping close track.  If someone has been keeping
operational stats (like outage date, cause, postmortem) on the roots, I'd
appreciate a pointer to this...

		--Dean




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


From ietf-admin@ietf.org  Tue May 18 19:31: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 TAA27857
	for <ietf-archive@ietf.org>; Tue, 18 May 2004 19:31: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 1BQE3G-0006zc-FV
	for ietf-archive@ietf.org; Tue, 18 May 2004 19:31:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQE2K-0006vH-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 19:30:17 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQE1U-0006rg-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 19:29:24 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQDvK-00048P-8a; Tue, 18 May 2004 19:23:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQDf7-0008Sy-KQ
	for ietf@optimus.ietf.org; Tue, 18 May 2004 19: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 TAA26759
	for <ietf@ietf.org>; Tue, 18 May 2004 19:06: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 1BQDf4-0005Fz-8m
	for ietf@ietf.org; Tue, 18 May 2004 19:06:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQDe6-0005CW-00
	for ietf@ietf.org; Tue, 18 May 2004 19:05:14 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQDdG-00056b-00
	for ietf@ietf.org; Tue, 18 May 2004 19:04:22 -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 i4IN3qrn023373
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 18 May 2004 19:03:52 -0400
Date: Tue, 18 May 2004 19:03:52 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Paul Vixie <vixie@vix.com>
cc: ietf@ietf.org
Subject: Re: Root Anycast
In-Reply-To: <g3lljqegi6.fsf@sa.vix.com>
Message-ID: <Pine.LNX.4.44.0405181856430.22463-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 18 May 2004, Paul Vixie wrote:

> Careful design by whom?  Organic compared to what?  I assure you that f-root
> has grown by careful design.  It's only organic in that we go where we're
> invited rather than having a gigantic budget that could be used as a leash.

Do you mean "Careful Design" like the non-standard changes in Bind 9 AXFR
and IXFR?  I don't think we can take too much of that sort of thing in the
operation of the root servers before we have serious problems.

Unilateral action is not a good thing. There is no point in having an IETF
(Remember the "Internet __Engineering__ Task Force" in IETF) if you just
implement whatever you think OK at the moment (AXFR mods, IXFR mods,
Anycast, and probably more that we just don't yet know about)

		--Dean


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


From exim@www1.ietf.org  Tue May 18 19:34:21 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 TAA28042
	for <ietf-archive@odin.ietf.org>; Tue, 18 May 2004 19:34:20 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQE1U-0005He-Pj
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 19:29:24 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4INTO5i020282
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 19:29:24 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQDvK-00048P-8a; Tue, 18 May 2004 19:23:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQDf7-0008Sy-KQ
	for ietf@optimus.ietf.org; Tue, 18 May 2004 19: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 TAA26759
	for <ietf@ietf.org>; Tue, 18 May 2004 19:06: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 1BQDf4-0005Fz-8m
	for ietf@ietf.org; Tue, 18 May 2004 19:06:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQDe6-0005CW-00
	for ietf@ietf.org; Tue, 18 May 2004 19:05:14 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQDdG-00056b-00
	for ietf@ietf.org; Tue, 18 May 2004 19:04:22 -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 i4IN3qrn023373
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 18 May 2004 19:03:52 -0400
Date: Tue, 18 May 2004 19:03:52 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Paul Vixie <vixie@vix.com>
cc: ietf@ietf.org
Subject: Re: Root Anycast
In-Reply-To: <g3lljqegi6.fsf@sa.vix.com>
Message-ID: <Pine.LNX.4.44.0405181856430.22463-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 18 May 2004, Paul Vixie wrote:

> Careful design by whom?  Organic compared to what?  I assure you that f-root
> has grown by careful design.  It's only organic in that we go where we're
> invited rather than having a gigantic budget that could be used as a leash.

Do you mean "Careful Design" like the non-standard changes in Bind 9 AXFR
and IXFR?  I don't think we can take too much of that sort of thing in the
operation of the root servers before we have serious problems.

Unilateral action is not a good thing. There is no point in having an IETF
(Remember the "Internet __Engineering__ Task Force" in IETF) if you just
implement whatever you think OK at the moment (AXFR mods, IXFR mods,
Anycast, and probably more that we just don't yet know about)

		--Dean


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



From exim@www1.ietf.org  Tue May 18 19:49: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 TAA28639
	for <ietf-archive@odin.ietf.org>; Tue, 18 May 2004 19:49: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 1BQEJS-0001Lg-3A
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 19:47:58 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4INlwGH005185
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 19:47:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQE70-0006zD-5a; Tue, 18 May 2004 19:35:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQE5L-0006bN-MA
	for ietf@optimus.ietf.org; Tue, 18 May 2004 19:33:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27982
	for <ietf@ietf.org>; Tue, 18 May 2004 19:33:22 -0400 (EDT)
From: thiagarajan.venkatachalam@wipro.com
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQE5K-0007AZ-0e
	for ietf@ietf.org; Tue, 18 May 2004 19:33:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQE4Q-00076Y-00
	for ietf@ietf.org; Tue, 18 May 2004 19:32:26 -0400
Received: from wiproecmx1.wipro.com ([164.164.31.5])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQE3j-0006zC-00
	for ietf@ietf.org; Tue, 18 May 2004 19:31:43 -0400
Received: from ec-vwall-wd (ec-vwall-wd.wipro.com [10.200.52.125])
	by wiproecmx1.wipro.com (8.12.9-20031013/8.12.9) with SMTP id i4INVAo9023956
	for <ietf@ietf.org>; Wed, 19 May 2004 05:01:10 +0530 (IST)
Received: from blr-ec-bh1.wipro.com ([10.200.50.91]) by ec-vwall-wd with InterScan Messaging Security Suite; Wed, 19 May 2004 05:01:09 +0530
Received: from chn-snr-bh2.wipro.com ([10.145.50.92]) by blr-ec-bh1.wipro.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 19 May 2004 05:01:09 +0530
Received: from chn-gdy-msg.wipro.com ([10.146.50.99]) by chn-snr-bh2.wipro.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 19 May 2004 05:01:08 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C43D30.2F40AD43"
Subject: unsubscribe
Date: Wed, 19 May 2004 05:01:03 +0530
Message-ID: <B99FECA7782B834AB0D4D5B18D89F5F00142142B@chn-gdy-msg.wipro.com>
Thread-Topic: unsubscribe
Thread-Index: AcQ9MC9q5phy4XyxR2uL+Pz4EpWX/Q==
To: <ietf@ietf.org>
X-OriginalArrivalTime: 18 May 2004 23:31:08.0842 (UTC) FILETIME=[328380A0:01C43D30]
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=HTML_90_100,HTML_MESSAGE,
	MIME_HTML_MOSTLY,NO_REAL_NAME 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.

------_=_NextPart_001_01C43D30.2F40AD43
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

=20


------_=_NextPart_001_01C43D30.2F40AD43
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">


<meta name=3DGenerator content=3D"Microsoft Word 10 (filtered)">

<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C43D30.2F40AD43--

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



From ietf-admin@ietf.org  Tue May 18 20:05:44 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29535
	for <ietf-archive@ietf.org>; Tue, 18 May 2004 20:05: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 1BQEad-0001uW-SX
	for ietf-archive@ietf.org; Tue, 18 May 2004 20:05:43 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQEZY-0001nb-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 20:04:37 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQEYw-0001hf-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 20:03:59 -0400
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BQERV-0005NW-Jz
	for ietf-archive@ietf.org; Tue, 18 May 2004 19:56:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQEKd-0001tJ-RL; Tue, 18 May 2004 19:49:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQEHs-0000bx-SZ
	for ietf@optimus.ietf.org; Tue, 18 May 2004 19:46:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28548
	for <ietf@ietf.org>; Tue, 18 May 2004 19:46: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 1BQEHr-0000KY-2B
	for ietf@ietf.org; Tue, 18 May 2004 19:46:19 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQEGz-0000H7-00
	for ietf@ietf.org; Tue, 18 May 2004 19:45:25 -0400
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQEGK-0000C1-00
	for ietf@ietf.org; Tue, 18 May 2004 19:44:44 -0400
Received: from sj-core-2.cisco.com (171.71.177.254)
  by sj-iport-2.cisco.com with ESMTP; 18 May 2004 15:49:55 +0000
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i4INi6T0009008;
	Tue, 18 May 2004 16:44:09 -0700 (PDT)
Received: from imail.cisco.com (imail.cisco.com [172.19.216.204])
	by mira-sjc5-e.cisco.com (MOS 3.4.5-GR)
	with ESMTP id APB32850;
	Tue, 18 May 2004 16:44:05 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by imail.cisco.com (8.12.5/8.12.10) with ESMTP id i4INq963031460;
	Tue, 18 May 2004 16:52:09 -0700
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16554.40901.130204.269632@thomasm-u1.cisco.com>
Date: Tue, 18 May 2004 16:44:05 -0700 (PDT)
To: <gwz@cisco.com>
Cc: "'JORDI PALET MARTINEZ'" <jordi.palet@consulintel.es>, <ietf@ietf.org>
Subject: RE: 60th IETF - Registration
In-Reply-To: <00a401c43d20$6bfbac00$36296540@amer.cisco.com>
References: <0b6001c43d05$f68ccd10$0402200a@consulintel.es>
	<00a401c43d20$6bfbac00$36296540@amer.cisco.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
X-IMAIL-SIG: v:"1"; h:"imail.cisco.com"; d:"cisco.com";
	t:"1084924329.459674"; x:"1085356329"; a:"rsa-sha1"; e:"Iw==";
	n:"zCnd+ByA23/7WMiIwaIZ7Ez3DplzVMdRKP138IXLOvBVeaRZ4yWEPclZ/2Mda"
	"s5Bs9RPWH0BGd3fx6j+txdOXarv4Y8kpMqTexCOMFlDmatpXDXfFj3VI9o4G7"
	"674gFTasaoPcvEfZCwcBgZD7T6sLZa3RTBUGzZqOshAMRpVek=";
	s:"awXOMl/7t/Q9sAwnJd7aoiSqmYktJUYri48GJWTak3Avlqyf8NhMNclbKbeqS"
	"ahdTINKEUAHlmVdNCV7GFV4cUprj5Ki1RVk5GgQWktLbv2M9yIQ5oO3acO3VO"
	"wq6gZPr1VbtfTT0XejoIJfRyX8VWg1qkoLzTleEKcInSNLcyA=";
	c:"From: Michael Thomas <mat@cisco.com>";
	c:"Date: Tue, 18 May 2004 16:44:05 -0700 (PDT)";
	c:"Subject: RE: 60th IETF - Registration"
X-IMAIL-VERIFY: s:"y"; v:"y"; r:"42"; h:"imail.cisco.com"
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

Glen Zorn writes:
 > JORDI PALET MARTINEZ <mailto:jordi.palet@consulintel.es> writes:
 > 
 > > I think is unacceptably TODAY, specially for IETF, that we should use
 > > a phone instead of on-line or email confirmation. 
 > > 
 > > We should not accept hotels that don't make usage of technology to
 > > arrange our meetings. 
 > 
 > Are you expecting, perhaps, that they create a special Web page just for
 > us?

   That seems about like the proper deference to our 
   grandeur and importance, don't you think? The
   real scandal here is that they don't pay us to 
   attend their establishment.

		Mike


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


From ietf-admin@ietf.org  Tue May 18 20:05: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 UAA29566
	for <ietf-archive@ietf.org>; Tue, 18 May 2004 20: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 1BQEan-0001vR-So
	for ietf-archive@ietf.org; Tue, 18 May 2004 20:05:53 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQEZj-0001pD-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 20:04:47 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQEZ5-0001hJ-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 20:04:07 -0400
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BQEJY-0005H8-4v
	for ietf-archive@ietf.org; Tue, 18 May 2004 19:48:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQE70-0006zD-5a; Tue, 18 May 2004 19:35:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQE5L-0006bN-MA
	for ietf@optimus.ietf.org; Tue, 18 May 2004 19:33:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27982
	for <ietf@ietf.org>; Tue, 18 May 2004 19:33:22 -0400 (EDT)
From: thiagarajan.venkatachalam@wipro.com
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQE5K-0007AZ-0e
	for ietf@ietf.org; Tue, 18 May 2004 19:33:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQE4Q-00076Y-00
	for ietf@ietf.org; Tue, 18 May 2004 19:32:26 -0400
Received: from wiproecmx1.wipro.com ([164.164.31.5])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQE3j-0006zC-00
	for ietf@ietf.org; Tue, 18 May 2004 19:31:43 -0400
Received: from ec-vwall-wd (ec-vwall-wd.wipro.com [10.200.52.125])
	by wiproecmx1.wipro.com (8.12.9-20031013/8.12.9) with SMTP id i4INVAo9023956
	for <ietf@ietf.org>; Wed, 19 May 2004 05:01:10 +0530 (IST)
Received: from blr-ec-bh1.wipro.com ([10.200.50.91]) by ec-vwall-wd with InterScan Messaging Security Suite; Wed, 19 May 2004 05:01:09 +0530
Received: from chn-snr-bh2.wipro.com ([10.145.50.92]) by blr-ec-bh1.wipro.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 19 May 2004 05:01:09 +0530
Received: from chn-gdy-msg.wipro.com ([10.146.50.99]) by chn-snr-bh2.wipro.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 19 May 2004 05:01:08 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C43D30.2F40AD43"
Subject: unsubscribe
Date: Wed, 19 May 2004 05:01:03 +0530
Message-ID: <B99FECA7782B834AB0D4D5B18D89F5F00142142B@chn-gdy-msg.wipro.com>
Thread-Topic: unsubscribe
Thread-Index: AcQ9MC9q5phy4XyxR2uL+Pz4EpWX/Q==
To: <ietf@ietf.org>
X-OriginalArrivalTime: 18 May 2004 23:31:08.0842 (UTC) FILETIME=[328380A0:01C43D30]
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=1.6 required=5.0 tests=AWL,HTML_70_80,HTML_MESSAGE,
	MIME_HTML_MOSTLY,NO_REAL_NAME autolearn=no version=2.60

This is a multi-part message in MIME format.

------_=_NextPart_001_01C43D30.2F40AD43
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

=20


------_=_NextPart_001_01C43D30.2F40AD43
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">


<meta name=3DGenerator content=3D"Microsoft Word 10 (filtered)">

<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C43D30.2F40AD43--

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


From exim@www1.ietf.org  Tue May 18 20:07: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 UAA29636
	for <ietf-archive@odin.ietf.org>; Tue, 18 May 2004 20:07: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 1BQERO-0003Hp-09
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 19:56:10 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4INu91w012628
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 19:56:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQEKd-0001tJ-RL; Tue, 18 May 2004 19:49:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQEHs-0000bx-SZ
	for ietf@optimus.ietf.org; Tue, 18 May 2004 19:46:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28548
	for <ietf@ietf.org>; Tue, 18 May 2004 19:46: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 1BQEHr-0000KY-2B
	for ietf@ietf.org; Tue, 18 May 2004 19:46:19 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQEGz-0000H7-00
	for ietf@ietf.org; Tue, 18 May 2004 19:45:25 -0400
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQEGK-0000C1-00
	for ietf@ietf.org; Tue, 18 May 2004 19:44:44 -0400
Received: from sj-core-2.cisco.com (171.71.177.254)
  by sj-iport-2.cisco.com with ESMTP; 18 May 2004 15:49:55 +0000
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i4INi6T0009008;
	Tue, 18 May 2004 16:44:09 -0700 (PDT)
Received: from imail.cisco.com (imail.cisco.com [172.19.216.204])
	by mira-sjc5-e.cisco.com (MOS 3.4.5-GR)
	with ESMTP id APB32850;
	Tue, 18 May 2004 16:44:05 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by imail.cisco.com (8.12.5/8.12.10) with ESMTP id i4INq963031460;
	Tue, 18 May 2004 16:52:09 -0700
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16554.40901.130204.269632@thomasm-u1.cisco.com>
Date: Tue, 18 May 2004 16:44:05 -0700 (PDT)
To: <gwz@cisco.com>
Cc: "'JORDI PALET MARTINEZ'" <jordi.palet@consulintel.es>, <ietf@ietf.org>
Subject: RE: 60th IETF - Registration
In-Reply-To: <00a401c43d20$6bfbac00$36296540@amer.cisco.com>
References: <0b6001c43d05$f68ccd10$0402200a@consulintel.es>
	<00a401c43d20$6bfbac00$36296540@amer.cisco.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
X-IMAIL-SIG: v:"1"; h:"imail.cisco.com"; d:"cisco.com";
	t:"1084924329.459674"; x:"1085356329"; a:"rsa-sha1"; e:"Iw==";
	n:"zCnd+ByA23/7WMiIwaIZ7Ez3DplzVMdRKP138IXLOvBVeaRZ4yWEPclZ/2Mda"
	"s5Bs9RPWH0BGd3fx6j+txdOXarv4Y8kpMqTexCOMFlDmatpXDXfFj3VI9o4G7"
	"674gFTasaoPcvEfZCwcBgZD7T6sLZa3RTBUGzZqOshAMRpVek=";
	s:"awXOMl/7t/Q9sAwnJd7aoiSqmYktJUYri48GJWTak3Avlqyf8NhMNclbKbeqS"
	"ahdTINKEUAHlmVdNCV7GFV4cUprj5Ki1RVk5GgQWktLbv2M9yIQ5oO3acO3VO"
	"wq6gZPr1VbtfTT0XejoIJfRyX8VWg1qkoLzTleEKcInSNLcyA=";
	c:"From: Michael Thomas <mat@cisco.com>";
	c:"Date: Tue, 18 May 2004 16:44:05 -0700 (PDT)";
	c:"Subject: RE: 60th IETF - Registration"
X-IMAIL-VERIFY: s:"y"; v:"y"; r:"42"; h:"imail.cisco.com"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.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

Glen Zorn writes:
 > JORDI PALET MARTINEZ <mailto:jordi.palet@consulintel.es> writes:
 > 
 > > I think is unacceptably TODAY, specially for IETF, that we should use
 > > a phone instead of on-line or email confirmation. 
 > > 
 > > We should not accept hotels that don't make usage of technology to
 > > arrange our meetings. 
 > 
 > Are you expecting, perhaps, that they create a special Web page just for
 > us?

   That seems about like the proper deference to our 
   grandeur and importance, don't you think? The
   real scandal here is that they don't pay us to 
   attend their establishment.

		Mike


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



From exim@www1.ietf.org  Tue May 18 20:27:21 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 UAA00508
	for <ietf-archive@odin.ietf.org>; Tue, 18 May 2004 20:27:20 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQEud-000814-0x
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 20:26:23 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4J0QM4Q030809
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 20:26:22 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQEcv-0005SM-Jw; Tue, 18 May 2004 20:08:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQEaa-0004dp-CW
	for ietf@optimus.ietf.org; Tue, 18 May 2004 20:05:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29506
	for <ietf@ietf.org>; Tue, 18 May 2004 20:05: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 1BQEaX-0001tv-Qj
	for ietf@ietf.org; Tue, 18 May 2004 20:05:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQEZT-0001mg-00
	for ietf@ietf.org; Tue, 18 May 2004 20:04:32 -0400
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQEYo-0001hK-00
	for ietf@ietf.org; Tue, 18 May 2004 20:03:50 -0400
Received: from f01m-34-230.d0.club-internet.fr ([212.195.225.230] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.24)
	id 1BQEYa-0004mu-Ao; Tue, 18 May 2004 17:03:37 -0700
Message-Id: <6.1.0.6.2.20040519003547.059c3620@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 6.1.0.6
Date: Wed, 19 May 2004 01:38:21 +0200
To: Måns Nilsson <mansaxel@besserwisser.org>
From: jfcm <info@utel.net>
Subject: Re: Root Anycast
Cc: ietf@ietf.org
In-Reply-To: <114760000.1084908866@slimsixten.pilsnet.sunet.se>
References: <DFC3BD05-A84A-11D8-AC18-000A95CD987A@muada.com>
 <g3lljqegi6.fsf@sa.vix.com>
 <6.1.0.6.2.20040518171004.04666060@mail.utel.net>
 <114760000.1084908866@slimsixten.pilsnet.sunet.se>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - utel.net
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id UAA29506
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

Dear M=E5ns,
your points would be well taken if we were talking of the same thing (you=
=20
will note that I was very carefull quoting ICP-3). When was the last time=
=20
IETF discussed the way to respond ICANN's ICP-3 call? (what I am try=20
doing). There is a resulting difference of perspective.

- I talk of real world when you talk of the current (unsecure and=20
overloaded?) implementation of the current DNS architecture.
- I do not want to fix the DNS, I want to free me from it: it was not=20
designed to support the current load and it is not managed in a way the=20
Govs will ultimately accept. So, trying to patch the broken current usage=
=20
to make it work as before is of no real interest. At least IMHO. [I have =
a=20
user' side point of view].

The problem we face is an old and too large unique system with a robust y=
et=20
overloaded engine. With all the problems which come with it. We have to=20
split the zones of usage and risks. Either it is planned by IETF or it is=
=20
done by the users. I suggest it is done together.

The novelty of Titanic were waterproof compartiment. Yet she sunk. The=20
world has an unique DNS zone today.

Let me review the points where we fully agree and how.

On 21:34 18/05/04, M=E5ns Nilsson said:
>--On Tuesday, May 18, 2004 18:01:05 +0200 jfcm <info@utel.net> wrote:
> > 1. first target: distribution of the root machines through a root ser=
ver
> > matrix and core network -
>Yes, this is already done. It works, even if it is not top-guided as you
>envision.

I do not envision it as top guided. What we plan is a service of a few=20
separate machines, collecting the national root matrix data (meaning: all=
=20
what is national and above) and concerting towards a unique version, amon=
g=20
themsleves and with other national equivalent agencies. (NB. this concern=
s=20
DNS among many other real time distributed mutually managed directories).

Let take an example, there is a unique time in nature. Yet there are many=
=20
reference clocks in the world, and that does not work badly.

Then the agreed file will be made available to 10 to 250 regional master=20
root severs (one by local business area - probably paid by cities - to=20
support the addition of the local data),. We do not think DNS control and=
=20
machine power, we think surety, security, stablity, distributed servicing=
.=20
Ultimately this means probably a national coverage of 1000 machines  With=
=20
the same global and national data.

> > containing local root information to make it a need. Decrease of the=20
> pressure, risk containement, new data, new services.
>This is unnecessary and prone to failure.

Right. But this is as unnecessary as liberty.
Prone to failure? OK, but failure on what ? Today the big failure is that=
=20
we are not free to chose and to develop. The system is not RFC 883=20
compliant. I cannot chose my data. The root system is not IETF core value=
=20
compliant, decision is not on the edges.

Anyway, you can chose the directory system you want. If you do not like i=
t=20
you do not use it. The only rule is (well worded in ICP-3) not to pollute=
=20
others' space. The DNS root is a 15 K (compressed) file you can update=20
every three months without losing access (but for some ccTLD like mine=20
because ICANN does not want to enter a third/forth secondary) and RIPE do=
es=20
not want to respond ...

> > 2. second target : a user MITM providing "hardware, software and
> > brainware firewalling". At root system level it means that the user i=
s to
> > cache his root system.
>
>Which part of the present caching resolve server does not provide this=20
>service today? Aren't you reinventing the wheel here?

:-) We do not speak of the same thing here. You only refer to the 15 K ro=
ot=20
file and to the 20 years old way to use the internet.

If you want people to change their poor habits, you can only propose them=
=20
better ways for you as part of better services to them. Cache is of no us=
e=20
for them, it is of use for you. Let clarify what you want, and what they=20
want. Let not just continue an old solution because you did not think of=20
something new and better.

You want to reduce the calls to your system, right? Let stop the "cache"=20
idea which is something of _your_ system ibn theirs, and propose them an=20
update of _their_ system - like anti-virus updates (ever heard that=20
anti-virus run huge 50x1G systems? And let discover what a user system ca=
n=20
bring more to its user owner. So when the user has started using and=20
enjoying _his_ system, you will obtain what you want.

> > Private roots are not subject to DoS. They certainly permit to surviv=
e a
> > few hours, days and even probably months. In adding all the root them=
es
> > we can objectively consider today for ubiquist new services, plus a
> > "first necessity" software kit and root, we are probably talking of a=
n
> > ASN.1 structure of less than 20 compacted K (comparable to anti-virus
> > updates).
>
>Private roots are subject to confusion, mis-directed micromanagement by=20
>local admins, overly sensitive to local politics, split-vision of what=20
>must by design be unified, and endless user frustration. I have tried th=
is=20
>in a large corporate network, and it was, even there with a clear chain =
of=20
>command, a horrible mess. Never, ever again will I take anything like it=
=20
>outside a lab (except to kill it)

We are not talking of the same thing. You talk of a system where you have=
=20
admins. Bloody centralization :-) Are you asking GWB everytime you want t=
o=20
call a friend on the phone ? This is what some people do on the DNS and w=
e=20
want them to stop. Calling on the rrot is like calling an operator. Do yo=
u=20
do it often ? I is not the nightmare of creating, training and managing a=
n=20
Operator Corp with local branches.

How many times a year do you call an operator ? How many times a year do=20
you think you really need to update your root file?

> > The figures I discussed in a previous memo, show that we could then c=
ome
> > back to a "486DX2". However discussing of root server the way we cons=
ider
> > them today would be quite meaningless.
>
>You have a strong passion for doing something to fix the DNS system. I
>suggest you channel this passion towards trying to fix all the b0rkened
>clients (cf. the studies of root server load refered to earlier here)
>before you try to impose breakage onto the well-functioning root server
>system.

I am sorry. But I have a strong passion for restoring the name space the=20
way we created it and the way the users need it, as par of the many tools=
=20
and services necessary to support networked interoperations. The DNS=20
concept is good and can partly do it, if it is not centralized. The root=20
server load is purely an architectural illness. That illness is due to th=
e=20
fear of pullution.  For years IETF and ICANN saw the question as "do we=20
want to risk pollution or do we want to risk critics from civil rights an=
d=20
from open roots opponents?"

The question today is "do we want to risk a total collapse of he network=20
and a forced quick and disorganized innovation or to eventually accept th=
at=20
innovation is necessary and to smoothly work towards it", according to=20
ICP-3 which calls on IETF fro experimentation ? Again IETF does not=20
respond. Fixing the broken architecture is the only way to fix the broken=
=20
clients - unless you get a cop behind every user (and it will not work=20
because there will be too many cops plus too many clients).

Take care.
jfc


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



From ietf-admin@ietf.org  Tue May 18 20:28: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 UAA00609
	for <ietf-archive@ietf.org>; Tue, 18 May 2004 20:28: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 1BQEwT-0003Tr-M1
	for ietf-archive@ietf.org; Tue, 18 May 2004 20:28:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQEvX-0003Mn-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 20:27:20 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQEub-0003Gc-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 20:26:21 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQEcv-0005SM-Jw; Tue, 18 May 2004 20:08:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQEaa-0004dp-CW
	for ietf@optimus.ietf.org; Tue, 18 May 2004 20:05:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29506
	for <ietf@ietf.org>; Tue, 18 May 2004 20:05: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 1BQEaX-0001tv-Qj
	for ietf@ietf.org; Tue, 18 May 2004 20:05:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQEZT-0001mg-00
	for ietf@ietf.org; Tue, 18 May 2004 20:04:32 -0400
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQEYo-0001hK-00
	for ietf@ietf.org; Tue, 18 May 2004 20:03:50 -0400
Received: from f01m-34-230.d0.club-internet.fr ([212.195.225.230] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.24)
	id 1BQEYa-0004mu-Ao; Tue, 18 May 2004 17:03:37 -0700
Message-Id: <6.1.0.6.2.20040519003547.059c3620@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 6.1.0.6
Date: Wed, 19 May 2004 01:38:21 +0200
To: Måns Nilsson <mansaxel@besserwisser.org>
From: jfcm <info@utel.net>
Subject: Re: Root Anycast
Cc: ietf@ietf.org
In-Reply-To: <114760000.1084908866@slimsixten.pilsnet.sunet.se>
References: <DFC3BD05-A84A-11D8-AC18-000A95CD987A@muada.com>
 <g3lljqegi6.fsf@sa.vix.com>
 <6.1.0.6.2.20040518171004.04666060@mail.utel.net>
 <114760000.1084908866@slimsixten.pilsnet.sunet.se>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - utel.net
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id UAA29506
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
Content-Transfer-Encoding: quoted-printable

Dear M=E5ns,
your points would be well taken if we were talking of the same thing (you=
=20
will note that I was very carefull quoting ICP-3). When was the last time=
=20
IETF discussed the way to respond ICANN's ICP-3 call? (what I am try=20
doing). There is a resulting difference of perspective.

- I talk of real world when you talk of the current (unsecure and=20
overloaded?) implementation of the current DNS architecture.
- I do not want to fix the DNS, I want to free me from it: it was not=20
designed to support the current load and it is not managed in a way the=20
Govs will ultimately accept. So, trying to patch the broken current usage=
=20
to make it work as before is of no real interest. At least IMHO. [I have =
a=20
user' side point of view].

The problem we face is an old and too large unique system with a robust y=
et=20
overloaded engine. With all the problems which come with it. We have to=20
split the zones of usage and risks. Either it is planned by IETF or it is=
=20
done by the users. I suggest it is done together.

The novelty of Titanic were waterproof compartiment. Yet she sunk. The=20
world has an unique DNS zone today.

Let me review the points where we fully agree and how.

On 21:34 18/05/04, M=E5ns Nilsson said:
>--On Tuesday, May 18, 2004 18:01:05 +0200 jfcm <info@utel.net> wrote:
> > 1. first target: distribution of the root machines through a root ser=
ver
> > matrix and core network -
>Yes, this is already done. It works, even if it is not top-guided as you
>envision.

I do not envision it as top guided. What we plan is a service of a few=20
separate machines, collecting the national root matrix data (meaning: all=
=20
what is national and above) and concerting towards a unique version, amon=
g=20
themsleves and with other national equivalent agencies. (NB. this concern=
s=20
DNS among many other real time distributed mutually managed directories).

Let take an example, there is a unique time in nature. Yet there are many=
=20
reference clocks in the world, and that does not work badly.

Then the agreed file will be made available to 10 to 250 regional master=20
root severs (one by local business area - probably paid by cities - to=20
support the addition of the local data),. We do not think DNS control and=
=20
machine power, we think surety, security, stablity, distributed servicing=
.=20
Ultimately this means probably a national coverage of 1000 machines  With=
=20
the same global and national data.

> > containing local root information to make it a need. Decrease of the=20
> pressure, risk containement, new data, new services.
>This is unnecessary and prone to failure.

Right. But this is as unnecessary as liberty.
Prone to failure? OK, but failure on what ? Today the big failure is that=
=20
we are not free to chose and to develop. The system is not RFC 883=20
compliant. I cannot chose my data. The root system is not IETF core value=
=20
compliant, decision is not on the edges.

Anyway, you can chose the directory system you want. If you do not like i=
t=20
you do not use it. The only rule is (well worded in ICP-3) not to pollute=
=20
others' space. The DNS root is a 15 K (compressed) file you can update=20
every three months without losing access (but for some ccTLD like mine=20
because ICANN does not want to enter a third/forth secondary) and RIPE do=
es=20
not want to respond ...

> > 2. second target : a user MITM providing "hardware, software and
> > brainware firewalling". At root system level it means that the user i=
s to
> > cache his root system.
>
>Which part of the present caching resolve server does not provide this=20
>service today? Aren't you reinventing the wheel here?

:-) We do not speak of the same thing here. You only refer to the 15 K ro=
ot=20
file and to the 20 years old way to use the internet.

If you want people to change their poor habits, you can only propose them=
=20
better ways for you as part of better services to them. Cache is of no us=
e=20
for them, it is of use for you. Let clarify what you want, and what they=20
want. Let not just continue an old solution because you did not think of=20
something new and better.

You want to reduce the calls to your system, right? Let stop the "cache"=20
idea which is something of _your_ system ibn theirs, and propose them an=20
update of _their_ system - like anti-virus updates (ever heard that=20
anti-virus run huge 50x1G systems? And let discover what a user system ca=
n=20
bring more to its user owner. So when the user has started using and=20
enjoying _his_ system, you will obtain what you want.

> > Private roots are not subject to DoS. They certainly permit to surviv=
e a
> > few hours, days and even probably months. In adding all the root them=
es
> > we can objectively consider today for ubiquist new services, plus a
> > "first necessity" software kit and root, we are probably talking of a=
n
> > ASN.1 structure of less than 20 compacted K (comparable to anti-virus
> > updates).
>
>Private roots are subject to confusion, mis-directed micromanagement by=20
>local admins, overly sensitive to local politics, split-vision of what=20
>must by design be unified, and endless user frustration. I have tried th=
is=20
>in a large corporate network, and it was, even there with a clear chain =
of=20
>command, a horrible mess. Never, ever again will I take anything like it=
=20
>outside a lab (except to kill it)

We are not talking of the same thing. You talk of a system where you have=
=20
admins. Bloody centralization :-) Are you asking GWB everytime you want t=
o=20
call a friend on the phone ? This is what some people do on the DNS and w=
e=20
want them to stop. Calling on the rrot is like calling an operator. Do yo=
u=20
do it often ? I is not the nightmare of creating, training and managing a=
n=20
Operator Corp with local branches.

How many times a year do you call an operator ? How many times a year do=20
you think you really need to update your root file?

> > The figures I discussed in a previous memo, show that we could then c=
ome
> > back to a "486DX2". However discussing of root server the way we cons=
ider
> > them today would be quite meaningless.
>
>You have a strong passion for doing something to fix the DNS system. I
>suggest you channel this passion towards trying to fix all the b0rkened
>clients (cf. the studies of root server load refered to earlier here)
>before you try to impose breakage onto the well-functioning root server
>system.

I am sorry. But I have a strong passion for restoring the name space the=20
way we created it and the way the users need it, as par of the many tools=
=20
and services necessary to support networked interoperations. The DNS=20
concept is good and can partly do it, if it is not centralized. The root=20
server load is purely an architectural illness. That illness is due to th=
e=20
fear of pullution.  For years IETF and ICANN saw the question as "do we=20
want to risk pollution or do we want to risk critics from civil rights an=
d=20
from open roots opponents?"

The question today is "do we want to risk a total collapse of he network=20
and a forced quick and disorganized innovation or to eventually accept th=
at=20
innovation is necessary and to smoothly work towards it", according to=20
ICP-3 which calls on IETF fro experimentation ? Again IETF does not=20
respond. Fixing the broken architecture is the only way to fix the broken=
=20
clients - unless you get a cop behind every user (and it will not work=20
because there will be too many cops plus too many clients).

Take care.
jfc


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


From ietf-admin@ietf.org  Tue May 18 21:38: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 VAA03801
	for <ietf-archive@ietf.org>; Tue, 18 May 2004 21:38: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 1BQG29-00015B-VF
	for ietf-archive@ietf.org; Tue, 18 May 2004 21:38:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQG1B-0000yg-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 21:37:14 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQG0D-0000tF-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 21:36:13 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQFmW-00017Q-Hv; Tue, 18 May 2004 21:22:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQFc7-0007x7-L0
	for ietf@optimus.ietf.org; Tue, 18 May 2004 21:11: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 VAA02645
	for <ietf@ietf.org>; Tue, 18 May 2004 21:11: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 1BQFc4-0006jf-SO
	for ietf@ietf.org; Tue, 18 May 2004 21:11:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQFb8-0006fV-00
	for ietf@ietf.org; Tue, 18 May 2004 21:10:19 -0400
Received: from smtp.cogeco.net ([216.221.81.25] helo=fep2.cogeco.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQFaP-0006cA-00
	for ietf@ietf.org; Tue, 18 May 2004 21:09:33 -0400
Received: from dot-god.com (d235-151-132.home1.cgocable.net [24.235.151.132])
	by fep2.cogeco.net (Postfix) with ESMTP
	id A51261C01; Tue, 18 May 2004 21:09:27 -0400 (EDT)
Received: from baptista (helo=localhost)
	by dot-god.com with local-esmtp (Exim 4.12)
	id 1BQFaQ-0003l0-00; Tue, 18 May 2004 21:09:34 -0400
Date: Tue, 18 May 2004 21:09:34 -0400 (EDT)
From: Joe Baptista <baptista@dot-god.com>
To: Dean Anderson <dean@av8.com>
Cc: Paul Vixie <vixie@vix.com>, <ietf@ietf.org>
Subject: Re: Root Anycast
In-Reply-To: <Pine.LNX.4.44.0405181841330.22463-100000@cirrus.av8.net>
Message-ID: <Pine.LNX.4.33.0405182107190.5111-100000@dot-god.com>
Organization: http://www.baptista.god/ or http://www.joebaptista.com/
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


On Tue, 18 May 2004, Dean Anderson wrote:

> On 18 May 2004, Paul Vixie wrote:
>
> > The result is a service which has never been "down hard", not ever, not for
> > any millisecond out of the last 15 years.  This is "strength by diversity."
>
> This isn't quite true. There have been multiple server failures. And if I
> recall, I think that there have been quite a few servers (like 12 of 13)
> that have been down at one time in this timeframe.
>
> But I haven't been keeping close track.  If someone has been keeping
> operational stats (like outage date, cause, postmortem) on the roots, I'd
> appreciate a pointer to this...

Outage reports and an outage archives maintained by the legacy root
operators would be nice.

I also rmember many incidents over the years involving root server outages
- but it's never official.  usually someone discovers a problem and
sometimes a root operator responds.  Usually in NANOG.

cheers
joe baptista


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


From exim@www1.ietf.org  Tue May 18 21:42:27 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03979
	for <ietf-archive@odin.ietf.org>; Tue, 18 May 2004 21:42:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQG0F-00031n-I0
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 21:36:16 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4J1aFL0011596
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 21:36:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQFmW-00017Q-Hv; Tue, 18 May 2004 21:22:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQFc7-0007x7-L0
	for ietf@optimus.ietf.org; Tue, 18 May 2004 21:11: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 VAA02645
	for <ietf@ietf.org>; Tue, 18 May 2004 21:11: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 1BQFc4-0006jf-SO
	for ietf@ietf.org; Tue, 18 May 2004 21:11:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQFb8-0006fV-00
	for ietf@ietf.org; Tue, 18 May 2004 21:10:19 -0400
Received: from smtp.cogeco.net ([216.221.81.25] helo=fep2.cogeco.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQFaP-0006cA-00
	for ietf@ietf.org; Tue, 18 May 2004 21:09:33 -0400
Received: from dot-god.com (d235-151-132.home1.cgocable.net [24.235.151.132])
	by fep2.cogeco.net (Postfix) with ESMTP
	id A51261C01; Tue, 18 May 2004 21:09:27 -0400 (EDT)
Received: from baptista (helo=localhost)
	by dot-god.com with local-esmtp (Exim 4.12)
	id 1BQFaQ-0003l0-00; Tue, 18 May 2004 21:09:34 -0400
Date: Tue, 18 May 2004 21:09:34 -0400 (EDT)
From: Joe Baptista <baptista@dot-god.com>
To: Dean Anderson <dean@av8.com>
Cc: Paul Vixie <vixie@vix.com>, <ietf@ietf.org>
Subject: Re: Root Anycast
In-Reply-To: <Pine.LNX.4.44.0405181841330.22463-100000@cirrus.av8.net>
Message-ID: <Pine.LNX.4.33.0405182107190.5111-100000@dot-god.com>
Organization: http://www.baptista.god/ or http://www.joebaptista.com/
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: 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, 18 May 2004, Dean Anderson wrote:

> On 18 May 2004, Paul Vixie wrote:
>
> > The result is a service which has never been "down hard", not ever, not for
> > any millisecond out of the last 15 years.  This is "strength by diversity."
>
> This isn't quite true. There have been multiple server failures. And if I
> recall, I think that there have been quite a few servers (like 12 of 13)
> that have been down at one time in this timeframe.
>
> But I haven't been keeping close track.  If someone has been keeping
> operational stats (like outage date, cause, postmortem) on the roots, I'd
> appreciate a pointer to this...

Outage reports and an outage archives maintained by the legacy root
operators would be nice.

I also rmember many incidents over the years involving root server outages
- but it's never official.  usually someone discovers a problem and
sometimes a root operator responds.  Usually in NANOG.

cheers
joe baptista


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



From exim@www1.ietf.org  Tue May 18 21:51:10 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA04650
	for <ietf-archive@odin.ietf.org>; Tue, 18 May 2004 21:51: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 1BQGCx-0006Nn-4X
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 21:49:25 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4J1nNFO024492
	for ietf-archive@odin.ietf.org; Tue, 18 May 2004 21:49:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQG6o-0004kg-Kj; Tue, 18 May 2004 21:43:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQG0K-00035O-1L
	for ietf@optimus.ietf.org; Tue, 18 May 2004 21:36:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03765
	for <ietf@ietf.org>; Tue, 18 May 2004 21:36:16 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQG0G-0000tv-Nl
	for ietf@ietf.org; Tue, 18 May 2004 21:36:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQFzJ-0000pf-00
	for ietf@ietf.org; Tue, 18 May 2004 21:35:17 -0400
Received: from c3p0.cc.swin.edu.au ([136.186.1.30] helo=swin.edu.au)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQFyM-0000hv-00
	for ietf@ietf.org; Tue, 18 May 2004 21:34:18 -0400
Received: from swin.edu.au (www.caia.swin.edu.au [136.186.229.16])
	by swin.edu.au (8.9.3p2-20030918/8.9.3) with ESMTP id LAA835260;
	Wed, 19 May 2004 11:33:40 +1000 (EST)
Message-ID: <40AAB96F.29AE48C8@swin.edu.au>
Date: Wed, 19 May 2004 11:33:35 +1000
From: grenville armitage <garmitage@swin.edu.au>
Organization: Centre for Advanced Internet Architectures, Swinburne University of 
 Technology
X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Root Anycast
References: <Pine.LNX.4.33.0405182107190.5111-100000@dot-god.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: 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 Tue, 18 May 2004, Dean Anderson wrote:
> 
> > On 18 May 2004, Paul Vixie wrote:
> >
> > > The result is a service which has never been "down hard", not ever, not for
> > > any millisecond out of the last 15 years.  This is "strength by diversity."
> >
> > This isn't quite true. There have been multiple server failures. And if I
> > recall, I think that there have been quite a few servers (like 12 of 13)
> > that have been down at one time in this timeframe.

I have fond memories of a time when list participants knew the difference
between a _service_ and a _server_

gja

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



From ietf-admin@ietf.org  Tue May 18 21:51: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 VAA04671
	for <ietf-archive@ietf.org>; Tue, 18 May 2004 21:51: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 1BQGEn-0002Ue-TI
	for ietf-archive@ietf.org; Tue, 18 May 2004 21:51:18 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQGDs-0002MS-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 21:50:20 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQGCu-0002Fk-00
	for ietf-archive@ietf.org; Tue, 18 May 2004 21:49:20 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQG6o-0004kg-Kj; Tue, 18 May 2004 21:43:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQG0K-00035O-1L
	for ietf@optimus.ietf.org; Tue, 18 May 2004 21:36:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03765
	for <ietf@ietf.org>; Tue, 18 May 2004 21:36:16 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQG0G-0000tv-Nl
	for ietf@ietf.org; Tue, 18 May 2004 21:36:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQFzJ-0000pf-00
	for ietf@ietf.org; Tue, 18 May 2004 21:35:17 -0400
Received: from c3p0.cc.swin.edu.au ([136.186.1.30] helo=swin.edu.au)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQFyM-0000hv-00
	for ietf@ietf.org; Tue, 18 May 2004 21:34:18 -0400
Received: from swin.edu.au (www.caia.swin.edu.au [136.186.229.16])
	by swin.edu.au (8.9.3p2-20030918/8.9.3) with ESMTP id LAA835260;
	Wed, 19 May 2004 11:33:40 +1000 (EST)
Message-ID: <40AAB96F.29AE48C8@swin.edu.au>
Date: Wed, 19 May 2004 11:33:35 +1000
From: grenville armitage <garmitage@swin.edu.au>
Organization: Centre for Advanced Internet Architectures, Swinburne University of 
 Technology
X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Root Anycast
References: <Pine.LNX.4.33.0405182107190.5111-100000@dot-god.com>
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


> On Tue, 18 May 2004, Dean Anderson wrote:
> 
> > On 18 May 2004, Paul Vixie wrote:
> >
> > > The result is a service which has never been "down hard", not ever, not for
> > > any millisecond out of the last 15 years.  This is "strength by diversity."
> >
> > This isn't quite true. There have been multiple server failures. And if I
> > recall, I think that there have been quite a few servers (like 12 of 13)
> > that have been down at one time in this timeframe.

I have fond memories of a time when list participants knew the difference
between a _service_ and a _server_

gja

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


From ietf-admin@ietf.org  Wed May 19 01:07: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 BAA13141
	for <ietf-archive@ietf.org>; Wed, 19 May 2004 01:07: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 1BQJIy-0006Ly-Oj
	for ietf-archive@ietf.org; Wed, 19 May 2004 01:07:48 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQJI9-0006Do-00
	for ietf-archive@ietf.org; Wed, 19 May 2004 01:06:57 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQJHW-00065T-00
	for ietf-archive@ietf.org; Wed, 19 May 2004 01:06:18 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQJBX-0000sh-Rr; Wed, 19 May 2004 01:00:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQJ80-0000IM-FU
	for ietf@optimus.ietf.org; Wed, 19 May 2004 00:56:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA12641
	for <ietf@ietf.org>; Wed, 19 May 2004 00:56: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 1BQJ7x-00053g-HU
	for ietf@ietf.org; Wed, 19 May 2004 00:56:25 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQJ6z-0004yH-00
	for ietf@ietf.org; Wed, 19 May 2004 00:55:26 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQJ6W-0004sW-00
	for ietf@ietf.org; Wed, 19 May 2004 00:54:57 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id DD3E3621C0; Wed, 19 May 2004 06:54:24 +0200 (CEST)
Received: from eikenes.alvestrand.no ([127.0.0.1])
 by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 12860-01; Wed, 19 May 2004 06:54:24 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 25EC161BD8; Wed, 19 May 2004 06:54:22 +0200 (CEST)
Date: Tue, 18 May 2004 20:52:20 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Dean Anderson <dean@av8.com>
Cc: ietf@ietf.org
Subject: Re: [dnsop] Re: Complaint on abuse of DNSOP lists
Message-ID: <126284898.1084913540@localhost>
In-Reply-To: <Pine.LNX.4.44.0405181819200.22463-100000@cirrus.av8.net>
References: <Pine.LNX.4.44.0405181819200.22463-100000@cirrus.av8.net>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
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

Mr. Anderson,

I note that your use of the terms "infantile", "irresponsible" and 
"immature" are personal attacks. These are inappropriate for the IETF list.

If you have serious complaints to make that you feel require you to use 
these terms, send them to me privately.

If you want to send mail to the public IETF list, be civil.

You have been warned.

                    Harald Alvestrand

--On 18. mai 2004 18:36 -0400 Dean Anderson <dean@av8.com> wrote:

> Sigh.
>
> Harald, Please add __Another__ complaint to the chair about inappropriate
> behavior by Mr. Vixie.
>
> Oh wait, could it be that lying to the general public saying our address
> space is hijacked is a personal attack?  Hmm.  Maybe they aren't as
> 'perfessional' as they made out to be.  Maybe these attacks aren't as
> unrelated to the IETF as the Chair asserts.
>
> I guess those that have to resort to name-calling don't have anything else
> ot resort to, since they can't resort to facts.  And of course, indeed, no
> contrary _facts_ have been given. Well, Vixie hasn't changed in 15 years,
> still as infantile as ever.
>
> And these irresponsible and immature people have operational control of a
> root nameserver.  How did that ever happen?  That too, should be changed.
>
> 		--Dean
>
> On 17 May 2004, Paul Vixie wrote:
>
>> dean@av8.com (Dean Anderson) writes:
>>
>> > ... For the less technical, an exchange point is ...
>>
>> I don't think there's anyone on this list less technical than you, Dean.
>>
>
>
>
>
>





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


From ietf-admin@ietf.org  Wed May 19 01:10:31 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA13287
	for <ietf-archive@ietf.org>; Wed, 19 May 2004 01:10: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 1BQJLa-0006kG-18
	for ietf-archive@ietf.org; Wed, 19 May 2004 01:10:30 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQJKg-0006bj-00
	for ietf-archive@ietf.org; Wed, 19 May 2004 01:09:34 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQJJr-0006UK-00
	for ietf-archive@ietf.org; Wed, 19 May 2004 01:08:43 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQJBa-0000t5-KI; Wed, 19 May 2004 01:00:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQJ81-0000IO-32
	for ietf@optimus.ietf.org; Wed, 19 May 2004 00:56: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 AAA12645
	for <ietf@ietf.org>; Wed, 19 May 2004 00: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 1BQJ7y-00053l-6b
	for ietf@ietf.org; Wed, 19 May 2004 00:56:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQJ70-0004yP-00
	for ietf@ietf.org; Wed, 19 May 2004 00:55:27 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQJ6d-0004t3-00
	for ietf@ietf.org; Wed, 19 May 2004 00:55:03 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id B58086227A; Wed, 19 May 2004 06:54:32 +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 12801-05; Wed, 19 May 2004 06:54:32 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 413EF61BD8; Wed, 19 May 2004 06:54:30 +0200 (CEST)
Date: Tue, 18 May 2004 21:35:37 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Dean Anderson <dean@av8.com>
Cc: ietf@ietf.org
Subject: Response to complaint from Dean Anderson
Message-ID: <128882262.1084916137@localhost>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
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

After re-checking with legal counsel, I repeat what I said before, trying 
to be as clear as possible:

   Bouncing a message to the sender is NOT public defamation.

Therefore, your complaint about "defamation" has no merit.

Dean, I believe that:

- your complaint about the apparently incorrect ownership listing of AV8's 
address space is with ARIN
- your complaint about the listing of this address space with SORBS is with 
SORBS
- your complaint about ISC's use of SORBS is with ISC

None of these are issues that the IETF can solve for you. They are not 
matters that are relevant to the IETF list.

Take care.

                    Harald Alvestrand


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


From exim@www1.ietf.org  Wed May 19 01:11: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 BAA13347
	for <ietf-archive@odin.ietf.org>; Wed, 19 May 2004 01:11: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 1BQJHY-0001eC-6B
	for ietf-archive@odin.ietf.org; Wed, 19 May 2004 01:06:20 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4J56K4H006328
	for ietf-archive@odin.ietf.org; Wed, 19 May 2004 01:06:20 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQJBX-0000sh-Rr; Wed, 19 May 2004 01:00:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQJ80-0000IM-FU
	for ietf@optimus.ietf.org; Wed, 19 May 2004 00:56:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA12641
	for <ietf@ietf.org>; Wed, 19 May 2004 00:56: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 1BQJ7x-00053g-HU
	for ietf@ietf.org; Wed, 19 May 2004 00:56:25 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQJ6z-0004yH-00
	for ietf@ietf.org; Wed, 19 May 2004 00:55:26 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQJ6W-0004sW-00
	for ietf@ietf.org; Wed, 19 May 2004 00:54:57 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id DD3E3621C0; Wed, 19 May 2004 06:54:24 +0200 (CEST)
Received: from eikenes.alvestrand.no ([127.0.0.1])
 by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 12860-01; Wed, 19 May 2004 06:54:24 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 25EC161BD8; Wed, 19 May 2004 06:54:22 +0200 (CEST)
Date: Tue, 18 May 2004 20:52:20 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Dean Anderson <dean@av8.com>
Cc: ietf@ietf.org
Subject: Re: [dnsop] Re: Complaint on abuse of DNSOP lists
Message-ID: <126284898.1084913540@localhost>
In-Reply-To: <Pine.LNX.4.44.0405181819200.22463-100000@cirrus.av8.net>
References: <Pine.LNX.4.44.0405181819200.22463-100000@cirrus.av8.net>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-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: 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

Mr. Anderson,

I note that your use of the terms "infantile", "irresponsible" and 
"immature" are personal attacks. These are inappropriate for the IETF list.

If you have serious complaints to make that you feel require you to use 
these terms, send them to me privately.

If you want to send mail to the public IETF list, be civil.

You have been warned.

                    Harald Alvestrand

--On 18. mai 2004 18:36 -0400 Dean Anderson <dean@av8.com> wrote:

> Sigh.
>
> Harald, Please add __Another__ complaint to the chair about inappropriate
> behavior by Mr. Vixie.
>
> Oh wait, could it be that lying to the general public saying our address
> space is hijacked is a personal attack?  Hmm.  Maybe they aren't as
> 'perfessional' as they made out to be.  Maybe these attacks aren't as
> unrelated to the IETF as the Chair asserts.
>
> I guess those that have to resort to name-calling don't have anything else
> ot resort to, since they can't resort to facts.  And of course, indeed, no
> contrary _facts_ have been given. Well, Vixie hasn't changed in 15 years,
> still as infantile as ever.
>
> And these irresponsible and immature people have operational control of a
> root nameserver.  How did that ever happen?  That too, should be changed.
>
> 		--Dean
>
> On 17 May 2004, Paul Vixie wrote:
>
>> dean@av8.com (Dean Anderson) writes:
>>
>> > ... For the less technical, an exchange point is ...
>>
>> I don't think there's anyone on this list less technical than you, Dean.
>>
>
>
>
>
>





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



From exim@www1.ietf.org  Wed May 19 01:11:14 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 BAA13364
	for <ietf-archive@odin.ietf.org>; Wed, 19 May 2004 01:11: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 1BQJJt-0002Zl-F8
	for ietf-archive@odin.ietf.org; Wed, 19 May 2004 01:08:45 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4J58joK009848
	for ietf-archive@odin.ietf.org; Wed, 19 May 2004 01:08:45 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQJBa-0000t5-KI; Wed, 19 May 2004 01:00:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQJ81-0000IO-32
	for ietf@optimus.ietf.org; Wed, 19 May 2004 00:56: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 AAA12645
	for <ietf@ietf.org>; Wed, 19 May 2004 00: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 1BQJ7y-00053l-6b
	for ietf@ietf.org; Wed, 19 May 2004 00:56:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQJ70-0004yP-00
	for ietf@ietf.org; Wed, 19 May 2004 00:55:27 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQJ6d-0004t3-00
	for ietf@ietf.org; Wed, 19 May 2004 00:55:03 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id B58086227A; Wed, 19 May 2004 06:54:32 +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 12801-05; Wed, 19 May 2004 06:54:32 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 413EF61BD8; Wed, 19 May 2004 06:54:30 +0200 (CEST)
Date: Tue, 18 May 2004 21:35:37 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Dean Anderson <dean@av8.com>
Cc: ietf@ietf.org
Subject: Response to complaint from Dean Anderson
Message-ID: <128882262.1084916137@localhost>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-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: 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

After re-checking with legal counsel, I repeat what I said before, trying 
to be as clear as possible:

   Bouncing a message to the sender is NOT public defamation.

Therefore, your complaint about "defamation" has no merit.

Dean, I believe that:

- your complaint about the apparently incorrect ownership listing of AV8's 
address space is with ARIN
- your complaint about the listing of this address space with SORBS is with 
SORBS
- your complaint about ISC's use of SORBS is with ISC

None of these are issues that the IETF can solve for you. They are not 
matters that are relevant to the IETF list.

Take care.

                    Harald Alvestrand


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



From ietf-admin@ietf.org  Wed May 19 05:21: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 FAA23417
	for <ietf-archive@ietf.org>; Wed, 19 May 2004 05:21: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 1BQNGa-0001Cy-RM
	for ietf-archive@ietf.org; Wed, 19 May 2004 05:21:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQNFj-00014g-00
	for ietf-archive@ietf.org; Wed, 19 May 2004 05:20:44 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQNFH-0000wo-00
	for ietf-archive@ietf.org; Wed, 19 May 2004 05:20:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQN4f-0007NB-1D; Wed, 19 May 2004 05:09:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQL86-0007dm-Fc
	for ietf@optimus.ietf.org; Wed, 19 May 2004 03:04:42 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA16973
	for <ietf@ietf.org>; Wed, 19 May 2004 03:04: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 1BQL82-0005m7-3v
	for ietf@ietf.org; Wed, 19 May 2004 03:04:38 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQL7O-0005bc-00
	for ietf@ietf.org; Wed, 19 May 2004 03:03:59 -0400
Received: from slimsixten.besserwisser.org ([213.212.3.212] helo=slimsixten.pilsnet.sunet.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQL63-0005Rq-00
	for ietf@ietf.org; Wed, 19 May 2004 03:02:35 -0400
Received: from localhost (localhost [127.0.0.1])
	by slimsixten.pilsnet.sunet.se (8.11.6p3/8.11.6) with ESMTP id i4J72Ov02570;
	Wed, 19 May 2004 09:02:25 +0200 (CEST)
Date: Wed, 19 May 2004 09:02:24 +0200
From: =?ISO-8859-1?Q?M=E5ns_Nilsson?= <mansaxel@besserwisser.org>
To: jfcm <info@utel.net>,
        =?ISO-8859-1?Q?M=E5ns_Nilsson?= <mansaxel@besserwisser.org>
cc: ietf@ietf.org
Subject: Re: Root Anycast
Message-ID: <283660000.1084950144@slimsixten.pilsnet.sunet.se>
In-Reply-To: <6.1.0.6.2.20040519003547.059c3620@mail.utel.net>
References: <DFC3BD05-A84A-11D8-AC18-000A95CD987A@muada.com>
 <g3lljqegi6.fsf@sa.vix.com>
 <6.1.0.6.2.20040518171004.04666060@mail.utel.net>
 <114760000.1084908866@slimsixten.pilsnet.sunet.se>
 <6.1.0.6.2.20040519003547.059c3620@mail.utel.net>
X-Mailer: Mulberry/3.1.1 (Linux/x86)
X-availability: Yes. 
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="==========8B49028992764EC8575F=========="
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

--==========8B49028992764EC8575F==========
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable



--On Wednesday, May 19, 2004 01:38:21 +0200 jfcm <info@utel.net> wrote:

> Dear M=E5ns,
> your points would be well taken if we were talking of the same thing=20

We talk about the scalability and stability of a global name-to-number
system. Between us lies some disagreement on how this should be achieved;
that is all.=20

> On 21:34 18/05/04, M=E5ns Nilsson said:
>> --On Tuesday, May 18, 2004 18:01:05 +0200 jfcm <info@utel.net> wrote:
>> > 1. first target: distribution of the root machines through a root
>> > server matrix and core network -
>> Yes, this is already done. It works, even if it is not top-guided as you
>> envision.
>=20
> I do not envision it as top guided. What we plan is a service of a few
> separate machines, collecting the national root matrix data (meaning: all
> what is national and above) and concerting towards a unique version,
> among themsleves and with other national equivalent agencies. (NB. this
> concerns DNS among many other real time distributed mutually managed
> directories).

This can be done with caching. You essentially propose a system where two
things are done:

* Remove the centralism needed for speedy updates. Right now, a new root=20
  zone including delegation data can be made available within 48hrs,=20
  including purge of the old one.=20

* Initiate a government-to-government negotiation procedure. I see only=20
  delay and intervening politics here. Remember -- this is not the length
  of the Meter or the UTC we are talking about, it is names! Names that do
  to peoples irrational brains what flags and marching music used to do in
  the nation-states of the early 20th century.=20

> Then the agreed file will be made available to 10 to 250 regional master
> root severs (one by local business area - probably paid by cities - to
> support the addition of the local data),. We do not think DNS control and
> machine power, we think surety, security, stablity, distributed
> servicing. Ultimately this means probably a national coverage of 1000
> machines  With the same global and national data.
=20
How does this differ from the current anycast developments? I see, for the
anycast cases where I have spoken to root admins, that local economies
effectively sponsor an instance of one or more of the root servers, and all
is well. If the prefix is just locally announced, one gets
compartmentisation should this be desired.=20

> Prone to failure? OK, but failure on what ? Today the big failure is that
> we are not free to chose and to develop. The system is not RFC 883
> compliant. I cannot chose my data. The root system is not IETF core value
> compliant, decision is not on the edges.

You can choose to run another root zone. You may mix this data with the
global version, but doing any of those is an invitation to pain (and your
email address will end up in /dev/null (a.k.a. loonybox) in a lot of
peoples email systems. The DNS system was designed (much like E.164) to be
The One system. Any attempts to break that are painful.=20
=20
> Anyway, you can chose the directory system you want. If you do not like
> it you do not use it.=20

Correct.=20
=20
>> > 2. second target : a user MITM providing "hardware, software and
>> > brainware firewalling". At root system level it means that the user is
>> > to cache his root system.
>>=20
>> Which part of the present caching resolve server does not provide this=20
>> service today? Aren't you reinventing the wheel here?
>=20
> :-) We do not speak of the same thing here. You only refer to the 15 K
> root file and to the 20 years old way to use the internet.
>=20
> If you want people to change their poor habits, you can only propose them
> better ways for you as part of better services to them. Cache is of no
> use for them, it is of use for you. Let clarify what you want, and what
> they want. Let not just continue an old solution because you did not
> think of something new and better.

I, on the contrary, argue that cache is good. It is a carefully balanced
engineering compromise between distributed and centralised load. Again,
instead of fixing what works (albeit with a bit too much load to be
comfortable.) I suggest fixing the cases where caching is not used, ie.=20
broken resolvers and clients.=20

> You want to reduce the calls to your system, right? Let stop the "cache"
> idea which is something of _your_ system ibn theirs, and propose them an
> update of _their_ system - like anti-virus updates (ever heard that
> anti-virus run huge 50x1G systems? And let discover what a user system
> can bring more to its user owner. So when the user has started using and
> enjoying _his_ system, you will obtain what you want.
>=20
>> > Private roots are not subject to DoS. They certainly permit to survive
>> > a few hours, days and even probably months. In adding all the root
>> > themes we can objectively consider today for ubiquist new services,
>> > plus a "first necessity" software kit and root, we are probably
>> > talking of an ASN.1 structure of less than 20 compacted K (comparable
>> > to anti-virus updates).
>>=20
>> Private roots are subject to confusion, mis-directed micromanagement by=20
>> local admins, overly sensitive to local politics, split-vision of what=20
>> must by design be unified, and endless user frustration. I have tried
>> this  in a large corporate network, and it was, even there with a clear
>> chain of  command, a horrible mess. Never, ever again will I take
>> anything like it  outside a lab (except to kill it)
>=20
> We are not talking of the same thing. You talk of a system where you have
> admins. Bloody centralization :-)=20

I have yet to see a computerised information service that does not need
maintenance by competent staff.=20

> Are you asking GWB everytime you want
> to call a friend on the phone ?=20

No, the ITU. Pest or Cholera?=20

> This is what some people do on the DNS
> and we want them to stop. Calling on the rrot is like calling an
> operator. Do you do it often ? I is not the nightmare of creating,
> training and managing an Operator Corp with local branches.

You are utterly confused. One thing here is correct -- the brokenness of
certain clients and their associated malware. Let's fix that. Or have you
given up? The other thing is a synchronisation problem. That is *really*
hard; do believe me.=20

> How many times a year do
> you think you really need to update your root file?

Twice a day, if I remember correctly. Current serial on i (the "real" i in
Stockholm, if you happen to distrust anycast.) is 2004051801, suggesting
that it was updated yesterday.=20

Even if every update does not contain new data, there must be, for business
reasons, a way to reasonably quickly propagate data, with very short =
notice.

> I am sorry. But I have a strong passion for restoring the name space the
> way we created it and the way the users need it, as par of the many tools
> and services necessary to support networked interoperations. The DNS
> concept is good and can partly do it, if it is not centralized. The root
> server load is purely an architectural illness. That illness is due to
> the fear of pullution.  For years IETF and ICANN saw the question as "do
> we want to risk pollution or do we want to risk critics from civil rights
> and from open roots opponents?"
>=20
> The question today is "do we want to risk a total collapse of he network
> and a forced quick and disorganized innovation or to eventually accept
> that innovation is necessary and to smoothly work towards it", according
> to ICP-3 which calls on IETF fro experimentation ? Again IETF does not
> respond.=20

I am still very concerned about pollution. It cannot be avoided if central
control is abandoned. Period.=20

Further, I think that the Internet community with the root server ops
leading the way have responded with innovation -- with anycast, supported
by traffic data, and research clearly showing where the problems are. The
problems are identified, but the solution proposed is not palatable to all
-- and cannot be. But I have strong confidence in the system, because I see
it work despite the horrifying load. And it has never, ever, been down.=20

--=20
M=E5ns Nilsson                    MN1334-RIPE
http://vvv.besserwisser.org     +46 706 81 72 04

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (NetBSD)

iD8DBQFAqwaA02/pMZDM1cURAunvAJ9o1Vu6lMP+o3fuR4ZzbJlcrDNFSgCcC103
FBqf/eNmJJTLCeS2u2ipxKE=
=3YJY
-----END PGP SIGNATURE-----

--==========8B49028992764EC8575F==========--


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


From exim@www1.ietf.org  Wed May 19 05:49: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 FAA25759
	for <ietf-archive@odin.ietf.org>; Wed, 19 May 2004 05:49: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 1BQNFB-0000b8-3h
	for ietf-archive@odin.ietf.org; Wed, 19 May 2004 05:20:22 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4J9K8jK002264
	for ietf-archive@odin.ietf.org; Wed, 19 May 2004 05:20:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQN4f-0007NB-1D; Wed, 19 May 2004 05:09:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQL86-0007dm-Fc
	for ietf@optimus.ietf.org; Wed, 19 May 2004 03:04:42 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA16973
	for <ietf@ietf.org>; Wed, 19 May 2004 03:04: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 1BQL82-0005m7-3v
	for ietf@ietf.org; Wed, 19 May 2004 03:04:38 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQL7O-0005bc-00
	for ietf@ietf.org; Wed, 19 May 2004 03:03:59 -0400
Received: from slimsixten.besserwisser.org ([213.212.3.212] helo=slimsixten.pilsnet.sunet.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQL63-0005Rq-00
	for ietf@ietf.org; Wed, 19 May 2004 03:02:35 -0400
Received: from localhost (localhost [127.0.0.1])
	by slimsixten.pilsnet.sunet.se (8.11.6p3/8.11.6) with ESMTP id i4J72Ov02570;
	Wed, 19 May 2004 09:02:25 +0200 (CEST)
Date: Wed, 19 May 2004 09:02:24 +0200
From: =?ISO-8859-1?Q?M=E5ns_Nilsson?= <mansaxel@besserwisser.org>
To: jfcm <info@utel.net>,
        =?ISO-8859-1?Q?M=E5ns_Nilsson?= <mansaxel@besserwisser.org>
cc: ietf@ietf.org
Subject: Re: Root Anycast
Message-ID: <283660000.1084950144@slimsixten.pilsnet.sunet.se>
In-Reply-To: <6.1.0.6.2.20040519003547.059c3620@mail.utel.net>
References: <DFC3BD05-A84A-11D8-AC18-000A95CD987A@muada.com>
 <g3lljqegi6.fsf@sa.vix.com>
 <6.1.0.6.2.20040518171004.04666060@mail.utel.net>
 <114760000.1084908866@slimsixten.pilsnet.sunet.se>
 <6.1.0.6.2.20040519003547.059c3620@mail.utel.net>
X-Mailer: Mulberry/3.1.1 (Linux/x86)
X-availability: Yes. 
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="==========8B49028992764EC8575F=========="
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-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>

--==========8B49028992764EC8575F==========
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable



--On Wednesday, May 19, 2004 01:38:21 +0200 jfcm <info@utel.net> wrote:

> Dear M=E5ns,
> your points would be well taken if we were talking of the same thing=20

We talk about the scalability and stability of a global name-to-number
system. Between us lies some disagreement on how this should be achieved;
that is all.=20

> On 21:34 18/05/04, M=E5ns Nilsson said:
>> --On Tuesday, May 18, 2004 18:01:05 +0200 jfcm <info@utel.net> wrote:
>> > 1. first target: distribution of the root machines through a root
>> > server matrix and core network -
>> Yes, this is already done. It works, even if it is not top-guided as you
>> envision.
>=20
> I do not envision it as top guided. What we plan is a service of a few
> separate machines, collecting the national root matrix data (meaning: all
> what is national and above) and concerting towards a unique version,
> among themsleves and with other national equivalent agencies. (NB. this
> concerns DNS among many other real time distributed mutually managed
> directories).

This can be done with caching. You essentially propose a system where two
things are done:

* Remove the centralism needed for speedy updates. Right now, a new root=20
  zone including delegation data can be made available within 48hrs,=20
  including purge of the old one.=20

* Initiate a government-to-government negotiation procedure. I see only=20
  delay and intervening politics here. Remember -- this is not the length
  of the Meter or the UTC we are talking about, it is names! Names that do
  to peoples irrational brains what flags and marching music used to do in
  the nation-states of the early 20th century.=20

> Then the agreed file will be made available to 10 to 250 regional master
> root severs (one by local business area - probably paid by cities - to
> support the addition of the local data),. We do not think DNS control and
> machine power, we think surety, security, stablity, distributed
> servicing. Ultimately this means probably a national coverage of 1000
> machines  With the same global and national data.
=20
How does this differ from the current anycast developments? I see, for the
anycast cases where I have spoken to root admins, that local economies
effectively sponsor an instance of one or more of the root servers, and all
is well. If the prefix is just locally announced, one gets
compartmentisation should this be desired.=20

> Prone to failure? OK, but failure on what ? Today the big failure is that
> we are not free to chose and to develop. The system is not RFC 883
> compliant. I cannot chose my data. The root system is not IETF core value
> compliant, decision is not on the edges.

You can choose to run another root zone. You may mix this data with the
global version, but doing any of those is an invitation to pain (and your
email address will end up in /dev/null (a.k.a. loonybox) in a lot of
peoples email systems. The DNS system was designed (much like E.164) to be
The One system. Any attempts to break that are painful.=20
=20
> Anyway, you can chose the directory system you want. If you do not like
> it you do not use it.=20

Correct.=20
=20
>> > 2. second target : a user MITM providing "hardware, software and
>> > brainware firewalling". At root system level it means that the user is
>> > to cache his root system.
>>=20
>> Which part of the present caching resolve server does not provide this=20
>> service today? Aren't you reinventing the wheel here?
>=20
> :-) We do not speak of the same thing here. You only refer to the 15 K
> root file and to the 20 years old way to use the internet.
>=20
> If you want people to change their poor habits, you can only propose them
> better ways for you as part of better services to them. Cache is of no
> use for them, it is of use for you. Let clarify what you want, and what
> they want. Let not just continue an old solution because you did not
> think of something new and better.

I, on the contrary, argue that cache is good. It is a carefully balanced
engineering compromise between distributed and centralised load. Again,
instead of fixing what works (albeit with a bit too much load to be
comfortable.) I suggest fixing the cases where caching is not used, ie.=20
broken resolvers and clients.=20

> You want to reduce the calls to your system, right? Let stop the "cache"
> idea which is something of _your_ system ibn theirs, and propose them an
> update of _their_ system - like anti-virus updates (ever heard that
> anti-virus run huge 50x1G systems? And let discover what a user system
> can bring more to its user owner. So when the user has started using and
> enjoying _his_ system, you will obtain what you want.
>=20
>> > Private roots are not subject to DoS. They certainly permit to survive
>> > a few hours, days and even probably months. In adding all the root
>> > themes we can objectively consider today for ubiquist new services,
>> > plus a "first necessity" software kit and root, we are probably
>> > talking of an ASN.1 structure of less than 20 compacted K (comparable
>> > to anti-virus updates).
>>=20
>> Private roots are subject to confusion, mis-directed micromanagement by=20
>> local admins, overly sensitive to local politics, split-vision of what=20
>> must by design be unified, and endless user frustration. I have tried
>> this  in a large corporate network, and it was, even there with a clear
>> chain of  command, a horrible mess. Never, ever again will I take
>> anything like it  outside a lab (except to kill it)
>=20
> We are not talking of the same thing. You talk of a system where you have
> admins. Bloody centralization :-)=20

I have yet to see a computerised information service that does not need
maintenance by competent staff.=20

> Are you asking GWB everytime you want
> to call a friend on the phone ?=20

No, the ITU. Pest or Cholera?=20

> This is what some people do on the DNS
> and we want them to stop. Calling on the rrot is like calling an
> operator. Do you do it often ? I is not the nightmare of creating,
> training and managing an Operator Corp with local branches.

You are utterly confused. One thing here is correct -- the brokenness of
certain clients and their associated malware. Let's fix that. Or have you
given up? The other thing is a synchronisation problem. That is *really*
hard; do believe me.=20

> How many times a year do
> you think you really need to update your root file?

Twice a day, if I remember correctly. Current serial on i (the "real" i in
Stockholm, if you happen to distrust anycast.) is 2004051801, suggesting
that it was updated yesterday.=20

Even if every update does not contain new data, there must be, for business
reasons, a way to reasonably quickly propagate data, with very short =
notice.

> I am sorry. But I have a strong passion for restoring the name space the
> way we created it and the way the users need it, as par of the many tools
> and services necessary to support networked interoperations. The DNS
> concept is good and can partly do it, if it is not centralized. The root
> server load is purely an architectural illness. That illness is due to
> the fear of pullution.  For years IETF and ICANN saw the question as "do
> we want to risk pollution or do we want to risk critics from civil rights
> and from open roots opponents?"
>=20
> The question today is "do we want to risk a total collapse of he network
> and a forced quick and disorganized innovation or to eventually accept
> that innovation is necessary and to smoothly work towards it", according
> to ICP-3 which calls on IETF fro experimentation ? Again IETF does not
> respond.=20

I am still very concerned about pollution. It cannot be avoided if central
control is abandoned. Period.=20

Further, I think that the Internet community with the root server ops
leading the way have responded with innovation -- with anycast, supported
by traffic data, and research clearly showing where the problems are. The
problems are identified, but the solution proposed is not palatable to all
-- and cannot be. But I have strong confidence in the system, because I see
it work despite the horrifying load. And it has never, ever, been down.=20

--=20
M=E5ns Nilsson                    MN1334-RIPE
http://vvv.besserwisser.org     +46 706 81 72 04

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (NetBSD)

iD8DBQFAqwaA02/pMZDM1cURAunvAJ9o1Vu6lMP+o3fuR4ZzbJlcrDNFSgCcC103
FBqf/eNmJJTLCeS2u2ipxKE=
=3YJY
-----END PGP SIGNATURE-----

--==========8B49028992764EC8575F==========--


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



From ietf-admin@ietf.org  Wed May 19 09:04: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 JAA08183
	for <ietf-archive@ietf.org>; Wed, 19 May 2004 09:04: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 1BQQkD-0002AA-Lw
	for ietf-archive@ietf.org; Wed, 19 May 2004 09:04:25 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQQid-0001mA-00
	for ietf-archive@ietf.org; Wed, 19 May 2004 09:02:47 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQQgb-0001DV-00
	for ietf-archive@ietf.org; Wed, 19 May 2004 09:00:41 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQQLJ-0004Jx-Aw; Wed, 19 May 2004 08:38:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ9o2-0005Z9-QZ
	for ietf@optimus.ietf.org; Tue, 18 May 2004 14:59:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05713
	for <ietf@ietf.org>; Tue, 18 May 2004 14:59: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 1BQ9nz-0007Jd-Qc
	for ietf@ietf.org; Tue, 18 May 2004 14:59:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ9nD-0007HF-00
	for ietf@ietf.org; Tue, 18 May 2004 14:58:24 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ9mK-0007Aj-00
	for ietf@ietf.org; Tue, 18 May 2004 14:57:28 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 0DBBB13DE9
	for <ietf@ietf.org>; Tue, 18 May 2004 18:56:54 +0000 (GMT)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: ietf@ietf.org
Subject: Re: Root Anycast 
In-Reply-To: Message from Jeroen Massar <jeroen@unfix.org> 
	of "Tue, 18 May 2004 14:58:17 +0200."
	<1084885097.12869.1407.camel@segesta.zurich.ibm.com> 
X-Mailer: MH-E 7.4; nmh 1.0.4; GNU Emacs 21.3.1
Date: Tue, 18 May 2004 18:56:54 +0000
Message-Id: <20040518185654.0DBBB13DE9@sa.vix.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=none autolearn=no version=2.60

> Paul, and other rootserveroperators (good scrabble word :), what would
> your answer/problem/arguments/... be if an ISP would decide to inject
> routes to the root-servers into their local network and point these
> request to a local dns cache(s), which would have the correct routes to
> the the global rootservers of course.

if someone injects 192.5.5.241 (or any route which covers it) anywhere
that a dns client will see it whose owner has not explicitly agreed to
have their f-root service modified in this way, and then modifies the
service (which means does something with the queries other than forward
them to an ISC-owned server) then we would of course file a lawsuit of
some kind, even if it meant opening an ISC office in some new place in
order to have "standing."

> Or another thought that have been raised recently on the 6bone list:
> Would it be an idea to have 2+ independent globaly routable prefixes,
> thus in IPv4 2x at least /24 and in IPv6 2x /32 which are allowed to be
> anycasted by anyone, just like the 6to4 stuff currently. So that ISP's
> could point these prefixes to their local dns caches, similar to the
> above but: documented which prefixes those are and no evil hijacking.
> This could also allow for DNS-client to have hardcoded addresses of
> these caching DNS prefixes lightening the load on the root servers as
> with anycast you will always get an answer from the closest one, if all
> is well and murphy is on his day off of course ;)

as far as i know, this would have to be done by iana rather than by ietf,
and the risk/reward tradeoff is such that it's not likely to see daylight.
last time i heard it discussed, the final determination was "better the
evil that we already know."

AS112 uses unowned anycast and it works well, but then, if wrong answers
were sent back by an AS112 server, it wouldn't exactly hurt anybody.
root name service seems more sensitive, to my eye.

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


From ietf-admin@ietf.org  Wed May 19 09:05: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 JAA08391
	for <ietf-archive@ietf.org>; Wed, 19 May 2004 09:05: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 1BQQlW-0002Y7-4W
	for ietf-archive@ietf.org; Wed, 19 May 2004 09:05:46 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQQk9-00029T-00
	for ietf-archive@ietf.org; Wed, 19 May 2004 09:04:21 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQQiZ-0001lU-00
	for ietf-archive@ietf.org; Wed, 19 May 2004 09:02:43 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQQLM-0004KN-1q; Wed, 19 May 2004 08:38:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQC2X-0004uG-Nq
	for ietf@optimus.ietf.org; Tue, 18 May 2004 17:22: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 RAA19998
	for <ietf@ietf.org>; Tue, 18 May 2004 17:22: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 1BQC2U-0005v0-S8
	for ietf@ietf.org; Tue, 18 May 2004 17:22:18 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQC1e-0005qN-00
	for ietf@ietf.org; Tue, 18 May 2004 17:21:26 -0400
Received: from dsl081-100-205.den1.dsl.speakeasy.net ([64.81.100.205] helo=giles.cursive.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQC0r-0005ft-00
	for ietf@ietf.org; Tue, 18 May 2004 17:20:37 -0400
Received: from [10.2.1.62] ([207.182.164.14]) by giles.cursive.net over TLS secured channel with Microsoft SMTPSVC(5.0.2195.6713);
	 Tue, 18 May 2004 15:20:06 -0600
In-Reply-To: <409F93F0.5060300@ehsco.com>
References: <DD72EEC3-A1E7-11D8-8626-003065F939FE@rudd.cc> <Pine.LNX.4.58.0405100019050.1405@perp.cac.washington.edu> <409F93F0.5060300@ehsco.com>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <1E94D875-A911-11D8-B683-000A959A17A6@cursive.net>
Content-Transfer-Encoding: 7bit
Cc: John Rudd <john@rudd.cc>, "RL 'Bob' Morgan" <rlmorgan@washington.edu>,
        IETF <ietf@ietf.org>
From: Joe Hildebrand <joe@cursive.net>
Subject: Re: Not sure if this is the right place for this
Date: Tue, 18 May 2004 15:20:00 -0600
To: "Eric A. Hall" <ehall@ehsco.com>
X-Mailer: Apple Mail (2.613)
X-OriginalArrivalTime: 18 May 2004 21:20:06.0812 (UTC) FILETIME=[E460EDC0:01C43D1D]
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

Configure your client so it *requires* start-tls, and it will error out 
if this attack is attempted.  The same attack is possible against SASL, 
if you remove DIGEST-MD5 and add PLAIN.  The defense is to configure 
your client to only allow non-plaintext SASL mechanisms.

-- 
Joe Hildebrand
Denver, CO, USA

On May 10, 2004, at 8:38 AM, Eric A. Hall wrote:

>
> On 5/10/2004 3:02 AM, RL 'Bob' Morgan wrote:
>
>> So a "secure ports only" policy has very little to do with security 
>> and
>> very much to do with organizational power relationships, and making
>> your computing environment dysfunctional.
>
> Somebody check my math on this please, but it seems to me that the 
> whole
> STARTTLS approach is succeptible to a specific attack which the secure
> socket model is not.
>
> Specifically, a man-in-the-middle can "blank out" the STARTTLS feature
> advertisement, and thus make the client believe that TLS is not 
> available.
> For example:
>
>       server-A                MitM                  client-C
>          |      250-DSN         |     250-DSN
>          +-->   250-AUTH        +->   250-AUTH
>                 250-STARTTLS          250 ok [...pad...]
>                 250 ok
>
> The client, seeing that TLS is not available, dumbs down to cleartext.
> Most clients would probably do that invisibly without even barking at 
> the
> user, or not doing so in a way that most of them would appreciate.
>
> Using an encrypted port just means an attack can only produce failure,
> rather than inducing fallback.
>
> Unless that's wrong for some reason, I'd say that a "secure ports 
> policy"
> actually is more secure.
>
>
> _______________________________________________
> 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 May 19 09:07:04 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 JAA08592
	for <ietf-archive@odin.ietf.org>; Wed, 19 May 2004 09:07: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 1BQQgc-0000PG-BM
	for ietf-archive@odin.ietf.org; Wed, 19 May 2004 09:00:42 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4JD0gc4001559
	for ietf-archive@odin.ietf.org; Wed, 19 May 2004 09:00:42 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQQLJ-0004Jx-Aw; Wed, 19 May 2004 08:38:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQ9o2-0005Z9-QZ
	for ietf@optimus.ietf.org; Tue, 18 May 2004 14:59:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05713
	for <ietf@ietf.org>; Tue, 18 May 2004 14:59: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 1BQ9nz-0007Jd-Qc
	for ietf@ietf.org; Tue, 18 May 2004 14:59:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQ9nD-0007HF-00
	for ietf@ietf.org; Tue, 18 May 2004 14:58:24 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQ9mK-0007Aj-00
	for ietf@ietf.org; Tue, 18 May 2004 14:57:28 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 0DBBB13DE9
	for <ietf@ietf.org>; Tue, 18 May 2004 18:56:54 +0000 (GMT)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: ietf@ietf.org
Subject: Re: Root Anycast 
In-Reply-To: Message from Jeroen Massar <jeroen@unfix.org> 
	of "Tue, 18 May 2004 14:58:17 +0200."
	<1084885097.12869.1407.camel@segesta.zurich.ibm.com> 
X-Mailer: MH-E 7.4; nmh 1.0.4; GNU Emacs 21.3.1
Date: Tue, 18 May 2004 18:56:54 +0000
Message-Id: <20040518185654.0DBBB13DE9@sa.vix.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: 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>

> Paul, and other rootserveroperators (good scrabble word :), what would
> your answer/problem/arguments/... be if an ISP would decide to inject
> routes to the root-servers into their local network and point these
> request to a local dns cache(s), which would have the correct routes to
> the the global rootservers of course.

if someone injects 192.5.5.241 (or any route which covers it) anywhere
that a dns client will see it whose owner has not explicitly agreed to
have their f-root service modified in this way, and then modifies the
service (which means does something with the queries other than forward
them to an ISC-owned server) then we would of course file a lawsuit of
some kind, even if it meant opening an ISC office in some new place in
order to have "standing."

> Or another thought that have been raised recently on the 6bone list:
> Would it be an idea to have 2+ independent globaly routable prefixes,
> thus in IPv4 2x at least /24 and in IPv6 2x /32 which are allowed to be
> anycasted by anyone, just like the 6to4 stuff currently. So that ISP's
> could point these prefixes to their local dns caches, similar to the
> above but: documented which prefixes those are and no evil hijacking.
> This could also allow for DNS-client to have hardcoded addresses of
> these caching DNS prefixes lightening the load on the root servers as
> with anycast you will always get an answer from the closest one, if all
> is well and murphy is on his day off of course ;)

as far as i know, this would have to be done by iana rather than by ietf,
and the risk/reward tradeoff is such that it's not likely to see daylight.
last time i heard it discussed, the final determination was "better the
evil that we already know."

AS112 uses unowned anycast and it works well, but then, if wrong answers
were sent back by an AS112 server, it wouldn't exactly hurt anybody.
root name service seems more sensitive, to my eye.

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



From ietf-admin@ietf.org  Wed May 19 09:07: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 JAA08650
	for <ietf-archive@ietf.org>; Wed, 19 May 2004 09: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 1BQQnC-00030Z-QV
	for ietf-archive@ietf.org; Wed, 19 May 2004 09:07:30 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQQlg-0002ej-00
	for ietf-archive@ietf.org; Wed, 19 May 2004 09:05:56 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQQkI-0002BA-00
	for ietf-archive@ietf.org; Wed, 19 May 2004 09:04:30 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQQLW-0004Tc-Mc; Wed, 19 May 2004 08:38:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQPyO-0001zY-ET
	for ietf@optimus.ietf.org; Wed, 19 May 2004 08:15: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 IAA04876
	for <ietf@ietf.org>; Wed, 19 May 2004 08:14: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 1BQPyN-0000PE-5J
	for ietf@ietf.org; Wed, 19 May 2004 08:14:59 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQPxS-0000Ed-00
	for ietf@ietf.org; Wed, 19 May 2004 08:14:03 -0400
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQPwY-0007fs-00; Wed, 19 May 2004 08:13:06 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i4JCCZS14435;
	Wed, 19 May 2004 15:12:35 +0300
Date: Wed, 19 May 2004 15:12:35 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: iesg@ietf.org
cc: ietf@ietf.org
Subject: Re: Last Call: 'The IESG and RFC Editor documents: Procedures' to
 BCP 
In-Reply-To: <E1BMCH7-0004ua-53@optimus.ietf.org>
Message-ID: <Pine.LNX.4.44.0405191511470.14373-100000@netcore.fi>
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 Fri, 7 May 2004, The IESG wrote:
> The IESG has received a request from the Internet Engineering Steering Group
> to consider the following document:
> 
> - 'The IESG and RFC Editor documents: Procedures '
>    <draft-iesg-rfced-documents-01.txt> as a BCP
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action.  Please send any comments to the
> iesg@ietf.org or ietf@ietf.org mailing lists by 2004-06-04.
> 
> The file can be obtained via
> http://www.ietf.org/internet-drafts/draft-iesg-rfced-documents-01.txt

A good document.  Go for it.  A few minor comments below.

The only thing I felt a bit fuzzy about was the statement:

                                The IETF disclaims any knowledge of the
       fitness of this RFC for any purpose, and in particular notes that
       it has not had IETF review for such things as security, 
       congestion control or inappropriate interaction with deployed   
       protocols.

==> now that we get down to talking about enumerating the important topics
that are being reviewed in the documents, should this list be expanded or
shrinked appropriately?  I'm fine with as it is, but I have a feeling that
those 3 items are not representative of the IETF review, and if we list
specific review subjects, the list should probably be longer..

editorial
---------

   This document gives the IESG's procedures for handling documents
   submitted for RFC publication via the RFC Editor, subsequent to the

==> s/gives/describes/

  RFC 3710 [3] section 5.2.2 describes the spring 2003 review process;

==> was that really spring 2003?  The RFC was published in 2004.

   The last two cases are included for the case where a document
   attempts to do things (such as URI scheme definition) that require  

==> s/URI scheme definition/to define a URI scheme/ ?

References

==> split these; 1-2 normative (or just 1), 3) to informational.



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


From ietf-admin@ietf.org  Wed May 19 10:30: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 KAA15070
	for <ietf-archive@ietf.org>; Wed, 19 May 2004 10:30: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 1BQS5E-00019Z-EX
	for ietf-archive@ietf.org; Wed, 19 May 2004 10:30:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQS43-000121-00
	for ietf-archive@ietf.org; Wed, 19 May 2004 10:28:59 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQS2x-0000uS-00
	for ietf-archive@ietf.org; Wed, 19 May 2004 10: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 1BQRfd-0002eQ-B2; Wed, 19 May 2004 10:03:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQR8m-0005jT-1w
	for ietf@optimus.ietf.org; Wed, 19 May 2004 09:29: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 JAA10369
	for <ietf@ietf.org>; Wed, 19 May 2004 09:29: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 1BQR8k-0004lp-4B
	for ietf@ietf.org; Wed, 19 May 2004 09:29:46 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQR7u-0004ji-00
	for ietf@ietf.org; Wed, 19 May 2004 09:28:55 -0400
Received: from smtp.cogeco.net ([216.221.81.25] helo=fep2.cogeco.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQR7E-0004hM-00
	for ietf@ietf.org; Wed, 19 May 2004 09:28:12 -0400
Received: from dot-god.com (d235-151-132.home1.cgocable.net [24.235.151.132])
	by fep2.cogeco.net (Postfix) with ESMTP
	id B38E31F64; Wed, 19 May 2004 09:28:11 -0400 (EDT)
Received: from baptista (helo=localhost)
	by dot-god.com with local-esmtp (Exim 4.12)
	id 1BQR7V-00018R-00; Wed, 19 May 2004 09:28:29 -0400
Date: Wed, 19 May 2004 09:28:29 -0400 (EDT)
From: Joe Baptista <baptista@dot-god.com>
To: Paul Vixie <paul@vix.com>
Cc: <ietf@ietf.org>
Subject: Re: Root Anycast 
In-Reply-To: <20040518185654.0DBBB13DE9@sa.vix.com>
Message-ID: <Pine.LNX.4.33.0405190926070.29821-100000@dot-god.com>
Organization: http://www.baptista.god/ or http://www.joebaptista.com/
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


On Tue, 18 May 2004, Paul Vixie wrote:

> > Paul, and other rootserveroperators (good scrabble word :), what would
> > your answer/problem/arguments/... be if an ISP would decide to inject
> > routes to the root-servers into their local network and point these
> > request to a local dns cache(s), which would have the correct routes to
> > the the global rootservers of course.
>
> if someone injects 192.5.5.241 (or any route which covers it) anywhere
> that a dns client will see it whose owner has not explicitly agreed to
> have their f-root service modified in this way, and then modifies the
> service (which means does something with the queries other than forward
> them to an ISC-owned server) then we would of course file a lawsuit of
> some kind, even if it meant opening an ISC office in some new place in
> order to have "standing."

I suggest you check isp's in the asia pacific region.  Standard practice
in some cases to intercept all dns including root traffic.  So i'm sure F
is one of them.

regards
joe baptista


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


From exim@www1.ietf.org  Wed May 19 10:36:46 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 KAA15794
	for <ietf-archive@odin.ietf.org>; Wed, 19 May 2004 10:36: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 1BQS33-0002p8-JE
	for ietf-archive@odin.ietf.org; Wed, 19 May 2004 10:27:59 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4JERvUN010585
	for ietf-archive@odin.ietf.org; Wed, 19 May 2004 10:27:57 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQRfd-0002eQ-B2; Wed, 19 May 2004 10:03:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQR8m-0005jT-1w
	for ietf@optimus.ietf.org; Wed, 19 May 2004 09:29: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 JAA10369
	for <ietf@ietf.org>; Wed, 19 May 2004 09:29: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 1BQR8k-0004lp-4B
	for ietf@ietf.org; Wed, 19 May 2004 09:29:46 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQR7u-0004ji-00
	for ietf@ietf.org; Wed, 19 May 2004 09:28:55 -0400
Received: from smtp.cogeco.net ([216.221.81.25] helo=fep2.cogeco.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQR7E-0004hM-00
	for ietf@ietf.org; Wed, 19 May 2004 09:28:12 -0400
Received: from dot-god.com (d235-151-132.home1.cgocable.net [24.235.151.132])
	by fep2.cogeco.net (Postfix) with ESMTP
	id B38E31F64; Wed, 19 May 2004 09:28:11 -0400 (EDT)
Received: from baptista (helo=localhost)
	by dot-god.com with local-esmtp (Exim 4.12)
	id 1BQR7V-00018R-00; Wed, 19 May 2004 09:28:29 -0400
Date: Wed, 19 May 2004 09:28:29 -0400 (EDT)
From: Joe Baptista <baptista@dot-god.com>
To: Paul Vixie <paul@vix.com>
Cc: <ietf@ietf.org>
Subject: Re: Root Anycast 
In-Reply-To: <20040518185654.0DBBB13DE9@sa.vix.com>
Message-ID: <Pine.LNX.4.33.0405190926070.29821-100000@dot-god.com>
Organization: http://www.baptista.god/ or http://www.joebaptista.com/
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: 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, 18 May 2004, Paul Vixie wrote:

> > Paul, and other rootserveroperators (good scrabble word :), what would
> > your answer/problem/arguments/... be if an ISP would decide to inject
> > routes to the root-servers into their local network and point these
> > request to a local dns cache(s), which would have the correct routes to
> > the the global rootservers of course.
>
> if someone injects 192.5.5.241 (or any route which covers it) anywhere
> that a dns client will see it whose owner has not explicitly agreed to
> have their f-root service modified in this way, and then modifies the
> service (which means does something with the queries other than forward
> them to an ISC-owned server) then we would of course file a lawsuit of
> some kind, even if it meant opening an ISC office in some new place in
> order to have "standing."

I suggest you check isp's in the asia pacific region.  Standard practice
in some cases to intercept all dns including root traffic.  So i'm sure F
is one of them.

regards
joe baptista


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



From ietf-admin@ietf.org  Wed May 19 10: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 KAA16410
	for <ietf-archive@ietf.org>; Wed, 19 May 2004 10: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 1BQSIh-0002O5-9E
	for ietf-archive@ietf.org; Wed, 19 May 2004 10:44:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQSHo-0002JE-00
	for ietf-archive@ietf.org; Wed, 19 May 2004 10:43:13 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQSHF-0002E3-00
	for ietf-archive@ietf.org; Wed, 19 May 2004 10:42:37 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQS94-0004oi-Gw; Wed, 19 May 2004 10:34:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQRlf-0004rO-NR
	for ietf@optimus.ietf.org; Wed, 19 May 2004 10:09:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12808
	for <ietf@ietf.org>; Wed, 19 May 2004 10:09: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 1BQRld-00079O-H3
	for ietf@ietf.org; Wed, 19 May 2004 10:09:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQRlB-00074s-00
	for ietf@ietf.org; Wed, 19 May 2004 10:09:30 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQRk5-00070K-00; Wed, 19 May 2004 10:08:22 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 63FA661B9C; Wed, 19 May 2004 16:07:50 +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 24820-09; Wed, 19 May 2004 16:07:49 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 52683621CF; Wed, 19 May 2004 16:07:47 +0200 (CEST)
Date: Wed, 19 May 2004 06:46:38 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Pekka Savola <pekkas@netcore.fi>, iesg@ietf.org
Cc: ietf@ietf.org
Subject: Re: Last Call: 'The IESG and RFC Editor documents: Procedures' to
 BCP 
Message-ID: <161942430.1084949198@localhost>
In-Reply-To: <Pine.LNX.4.44.0405191511470.14373-100000@netcore.fi>
References: <Pine.LNX.4.44.0405191511470.14373-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
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

thanks for your comments, Pekka!

wrt review subjects - we went a few rounds on this, and the current list is 
probably a reasonable compromise between "no list" and "exhaustive list" - 
it's short enough to make people notice that "such as" probably covers a 
lot of stuff not mentioned. Good that you can live with this one!

--On 19. mai 2004 15:12 +0300 Pekka Savola <pekkas@netcore.fi> wrote:

>   RFC 3710 [3] section 5.2.2 describes the spring 2003 review process;
>
> ==> was that really spring 2003?  The RFC was published in 2004.

:-(
even though it was informational only, it did take a year to get from the 
first draft to the published RFC.... and we chose not to make it claim to 
track changes to the process that occured over that time....

                        Harald



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


From ietf-admin@ietf.org  Wed May 19 14:45: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 OAA29780
	for <ietf-archive@ietf.org>; Wed, 19 May 2004 14:45: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 1BQW3u-0007bE-97
	for ietf-archive@ietf.org; Wed, 19 May 2004 14:45:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQW30-0007Ui-00
	for ietf-archive@ietf.org; Wed, 19 May 2004 14:44:11 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQW2P-0007OM-00
	for ietf-archive@ietf.org; Wed, 19 May 2004 14:43:33 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQVmT-0006C7-Bj; Wed, 19 May 2004 14:27:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQSDr-0006bV-Mi
	for ietf@optimus.ietf.org; Wed, 19 May 2004 10:39:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16032
	for <ietf@ietf.org>; Wed, 19 May 2004 10:39: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 1BQSDp-00021v-9Q
	for ietf@ietf.org; Wed, 19 May 2004 10:39:05 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQSCr-0001x6-00
	for ietf@ietf.org; Wed, 19 May 2004 10:38:06 -0400
Received: from ginger.cmf.nrl.navy.mil ([134.207.10.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQSCL-0001rt-00
	for ietf@ietf.org; Wed, 19 May 2004 10:37:33 -0400
Received: from cmf.nrl.navy.mil (elvis.cmf.nrl.navy.mil [134.207.10.38])
	(authenticated bits=0)
	by ginger.cmf.nrl.navy.mil (8.12.11/8.12.11) with ESMTP id i4JEbT7D024972
	for <ietf@ietf.org>; Wed, 19 May 2004 10:37:29 -0400 (EDT)
Message-Id: <200405191437.i4JEbT7D024972@ginger.cmf.nrl.navy.mil>
To: ietf@ietf.org
Subject: Re: 60th IETF - Registration 
In-Reply-To: <0ee201c43d23$074998f0$0402200a@consulintel.es> 
X-Face: "Evs"_GpJ]],xS)b$T2#V&{KfP_i2`TlPrY$Iv9+TQ!6+`~+l)#7I)0xr1>4hfd{#0B4
	WIn3jU;bql;{2Uq%zw5bF4?%F&&j8@KaT?#vBGk}u07<+6/`.F-3_GA@6Bq5gN9\+s;_d
	gD\SW #]iN_U0 KUmOR.P<|um5yP<ea#^"SJK;C*}fMI;Mv(aiO2z~9n.w?@\>kEpSD@*e`
Date: Wed, 19 May 2004 10:37:28 -0400
From: Ken Hornstein <kenh@cmf.nrl.navy.mil>
X-Spam-Score: () hits=0 User Authenticated
X-Virus-Scanned: NAI Completed
X-Scanned-By: MIMEDefang 2.30 (www . roaringpenguin . com / mimedefang)
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

>We should also remember that the people don't comes just from US. When I
>called they (not very kindly) suggested me if I can call back in 6 hours
>(!!!!!) because registration services doesn't work so early. Incredible,
>this is having fun and supporting international guests. Just quality,
>hopefully not the same we will get when we are in the meeting.

To be fair ... I've certainly experienced the same thing at non-US IETF
hotels (the one that sticks out in my mind is Adelaide, but I believe
there were others).  However, instead of whining about it on the IETF
mailing list I just sucked it up and called at the appropriate venue-local
time.

--Ken

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


From ietf-admin@ietf.org  Wed May 19 15:07: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 PAA02323
	for <ietf-archive@ietf.org>; Wed, 19 May 2004 15:07: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 1BQWPS-0003CX-9c
	for ietf-archive@ietf.org; Wed, 19 May 2004 15:07:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQWOY-00031A-00
	for ietf-archive@ietf.org; Wed, 19 May 2004 15:06:27 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQWNb-0002op-00
	for ietf-archive@ietf.org; Wed, 19 May 2004 15:05:27 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQVoP-0006gT-Q7; Wed, 19 May 2004 14:29:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQTay-0002qJ-Ic
	for ietf@optimus.ietf.org; Wed, 19 May 2004 12:07: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 MAA20382
	for <ietf@ietf.org>; Wed, 19 May 2004 12:07: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 1BQTaw-0000cU-Jl
	for ietf@ietf.org; Wed, 19 May 2004 12:07:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQTZw-0000YB-00
	for ietf@ietf.org; Wed, 19 May 2004 12:06:01 -0400
Received: from [68.120.110.66] (helo=laptop2.kurtis.pp.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQTZb-0000Tp-00
	for ietf@ietf.org; Wed, 19 May 2004 12:05:39 -0400
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by laptop2.kurtis.pp.se (Postfix) with ESMTP
	id 8A35640FA79; Wed, 19 May 2004 18:05:22 +0200 (CEST)
In-Reply-To: <Pine.LNX.4.44.0405181841330.22463-100000@cirrus.av8.net>
References: <Pine.LNX.4.44.0405181841330.22463-100000@cirrus.av8.net>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=fixed
Message-Id: <50052501-A9AE-11D8-8726-000A95928574@kurtis.pp.se>
Content-Transfer-Encoding: 7bit
Cc: Paul Vixie <vixie@vix.com>, ietf@ietf.org
From: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
Subject: Re: Root Anycast
Date: Wed, 19 May 2004 18:05:13 +0200
To: Dean Anderson <dean@av8.com>
X-Pgp-Rfc2646-Fix: 1
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

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


On 2004-05-19, at 00.54, Dean Anderson wrote:

> On 18 May 2004, Paul Vixie wrote:
>
>> The result is a service which has never been "down hard", not ever, 
>> not for
>> any millisecond out of the last 15 years.  This is "strength by 
>> diversity."
>
> This isn't quite true. There have been multiple server failures. And 
> if I
> recall, I think that there have been quite a few servers (like 12 of 
> 13)
> that have been down at one time in this timeframe.
>
> But I haven't been keeping close track.  If someone has been keeping
> operational stats (like outage date, cause, postmortem) on the roots, 
> I'd
> appreciate a pointer to this...

So although you don't know, you still like to claim that 12 out of 13 
have been down? That's quite a serious allegation. I'd like that have 
that proved or taken back.

- - kurtis -

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3

iQA/AwUBQKuFwKarNKXTPFCVEQJvvwCgpIrHqDjgER0DOUGlBhZbHRlf2usAoIWk
STNUBlFr5yD2f/brF0AgoHnJ
=NFz5
-----END PGP SIGNATURE-----


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


From exim@www1.ietf.org  Wed May 19 15:29:56 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 PAA05798
	for <ietf-archive@odin.ietf.org>; Wed, 19 May 2004 15:29: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 1BQW2Y-0001KD-LZ
	for ietf-archive@odin.ietf.org; Wed, 19 May 2004 14:43:42 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4JIhgPa004837
	for ietf-archive@odin.ietf.org; Wed, 19 May 2004 14:43:42 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQVmT-0006C7-Bj; Wed, 19 May 2004 14:27:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQSDr-0006bV-Mi
	for ietf@optimus.ietf.org; Wed, 19 May 2004 10:39:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16032
	for <ietf@ietf.org>; Wed, 19 May 2004 10:39: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 1BQSDp-00021v-9Q
	for ietf@ietf.org; Wed, 19 May 2004 10:39:05 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQSCr-0001x6-00
	for ietf@ietf.org; Wed, 19 May 2004 10:38:06 -0400
Received: from ginger.cmf.nrl.navy.mil ([134.207.10.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQSCL-0001rt-00
	for ietf@ietf.org; Wed, 19 May 2004 10:37:33 -0400
Received: from cmf.nrl.navy.mil (elvis.cmf.nrl.navy.mil [134.207.10.38])
	(authenticated bits=0)
	by ginger.cmf.nrl.navy.mil (8.12.11/8.12.11) with ESMTP id i4JEbT7D024972
	for <ietf@ietf.org>; Wed, 19 May 2004 10:37:29 -0400 (EDT)
Message-Id: <200405191437.i4JEbT7D024972@ginger.cmf.nrl.navy.mil>
To: ietf@ietf.org
Subject: Re: 60th IETF - Registration 
In-Reply-To: <0ee201c43d23$074998f0$0402200a@consulintel.es> 
X-Face: "Evs"_GpJ]],xS)b$T2#V&{KfP_i2`TlPrY$Iv9+TQ!6+`~+l)#7I)0xr1>4hfd{#0B4
	WIn3jU;bql;{2Uq%zw5bF4?%F&&j8@KaT?#vBGk}u07<+6/`.F-3_GA@6Bq5gN9\+s;_d
	gD\SW #]iN_U0 KUmOR.P<|um5yP<ea#^"SJK;C*}fMI;Mv(aiO2z~9n.w?@\>kEpSD@*e`
Date: Wed, 19 May 2004 10:37:28 -0400
From: Ken Hornstein <kenh@cmf.nrl.navy.mil>
X-Spam-Score: () hits=0 User Authenticated
X-Virus-Scanned: NAI Completed
X-Scanned-By: MIMEDefang 2.30 (www . roaringpenguin . com / mimedefang)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: 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>

>We should also remember that the people don't comes just from US. When I
>called they (not very kindly) suggested me if I can call back in 6 hours
>(!!!!!) because registration services doesn't work so early. Incredible,
>this is having fun and supporting international guests. Just quality,
>hopefully not the same we will get when we are in the meeting.

To be fair ... I've certainly experienced the same thing at non-US IETF
hotels (the one that sticks out in my mind is Adelaide, but I believe
there were others).  However, instead of whining about it on the IETF
mailing list I just sucked it up and called at the appropriate venue-local
time.

--Ken

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



From ietf-admin@ietf.org  Wed May 19 15:49: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 PAA08771
	for <ietf-archive@ietf.org>; Wed, 19 May 2004 15:49: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 1BQX4Q-0002JM-4p
	for ietf-archive@ietf.org; Wed, 19 May 2004 15:49:42 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQX3Q-00028a-00
	for ietf-archive@ietf.org; Wed, 19 May 2004 15:48:41 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQX29-0001sf-00
	for ietf-archive@ietf.org; Wed, 19 May 2004 15:47:21 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQWmC-00085r-SG; Wed, 19 May 2004 15:30:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQW6p-0002Y6-Ix
	for ietf@optimus.ietf.org; Wed, 19 May 2004 14:48:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29976
	for <ietf@ietf.org>; Wed, 19 May 2004 14:48: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 1BQW6m-0000Et-Kl
	for ietf@ietf.org; Wed, 19 May 2004 14:48:04 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQW5s-00004S-00
	for ietf@ietf.org; Wed, 19 May 2004 14:47:09 -0400
Received: from carwash.centive.com ([65.220.90.249])
	by ietf-mx with smtp (Exim 4.12)
	id 1BQW5K-0007ij-00
	for ietf@ietf.org; Wed, 19 May 2004 14:46:34 -0400
Received: from minglewood.incentivesystems.com ([10.10.30.25])
 by carwash.centive.com (SAVSMTP 3.1.3.37) with SMTP id M2004051914480824356
 for <ietf@ietf.org>; Wed, 19 May 2004 14:48:08 -0400
Received: from [10.10.48.119] ([10.10.48.119]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(6.0.3790.0);
	 Wed, 19 May 2004 14:42:06 -0400
Message-ID: <40ABAA7D.4040008@centive.com>
Date: Wed, 19 May 2004 14:42:06 -0400
From: John Stracke <jstracke@centive.com>
User-Agent: Mozilla Thunderbird 0.6 (Windows/20040502)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: 60th IETF - Registration
References: <200405191437.i4JEbT7D024972@ginger.cmf.nrl.navy.mil>
In-Reply-To: <200405191437.i4JEbT7D024972@ginger.cmf.nrl.navy.mil>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 May 2004 18:42:06.0229 (UTC) FILETIME=[FBEC8450:01C43DD0]
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

Ken Hornstein wrote:

>To be fair ... I've certainly experienced the same thing at non-US IETF
>hotels (the one that sticks out in my mind is Adelaide, but I believe
>there were others).
>  
>
I remember setting my alarm for 3:00 AM to make a reservation for Oslo.

-- 
/============================================================\
|John Stracke      |jstracke@centive.com                     |
|Principal Engineer|http://www.centive.com                   |
|Centive           |My opinions are my own.                  |
|============================================================|
|In the country of the blind, the one-eyed man is in therapy.|
\============================================================/


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


From ietf-admin@ietf.org  Wed May 19 15:53: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 PAA02340
	for <ietf-archive@ietf.org>; Wed, 19 May 2004 15:07: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 1BQWPT-0003Cl-KG
	for ietf-archive@ietf.org; Wed, 19 May 2004 15:07:23 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQWOZ-00031I-00
	for ietf-archive@ietf.org; Wed, 19 May 2004 15:06:28 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQWNb-0002oq-00
	for ietf-archive@ietf.org; Wed, 19 May 2004 15:05:27 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQVoS-0006gs-0L; Wed, 19 May 2004 14:29:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQTie-0004qs-8P
	for ietf@optimus.ietf.org; Wed, 19 May 2004 12:15: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 MAA20701
	for <ietf@ietf.org>; Wed, 19 May 2004 12:14: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 1BQTia-0001Gc-96
	for ietf@ietf.org; Wed, 19 May 2004 12:14:56 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQThW-0001BB-00
	for ietf@ietf.org; Wed, 19 May 2004 12:13:50 -0400
Received: from [68.120.110.66] (helo=laptop2.kurtis.pp.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQTh3-00017N-00
	for ietf@ietf.org; Wed, 19 May 2004 12:13:21 -0400
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by laptop2.kurtis.pp.se (Postfix) with ESMTP
	id 1425E40FAB7; Wed, 19 May 2004 18:13:04 +0200 (CEST)
In-Reply-To: <6.1.0.6.2.20040519003547.059c3620@mail.utel.net>
References: <DFC3BD05-A84A-11D8-AC18-000A95CD987A@muada.com> <g3lljqegi6.fsf@sa.vix.com> <6.1.0.6.2.20040518171004.04666060@mail.utel.net> <114760000.1084908866@slimsixten.pilsnet.sunet.se> <6.1.0.6.2.20040519003547.059c3620@mail.utel.net>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=fixed
Message-Id: <6522B9F0-A9AF-11D8-8726-000A95928574@kurtis.pp.se>
Content-Transfer-Encoding: 7bit
Cc: =?ISO-8859-1?Q?M=E5ns_Nilsson?= <mansaxel@besserwisser.org>, ietf@ietf.org
From: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
Subject: Re: Root Anycast
Date: Wed, 19 May 2004 18:12:58 +0200
To: jfcm <info@utel.net>
X-Pgp-Rfc2646-Fix: 1
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

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


> - I talk of real world when you talk of the current (unsecure and 
> overloaded?) implementation of the current DNS architecture.

In what way overloaded? Do you have any pointers? Proof? Data?

> The problem we face is an old and too large unique system with a 
> robust yet overloaded engine. With all the problems which come with 
> it. We have to split the zones of usage and risks. Either it is 
> planned by IETF or it is done by the users. I suggest it is done 
> together.

Again, overloaded engine in what way?

> Then the agreed file

Agreed by whom?  In what way?

> You want to reduce the calls to your system, right? Let stop the 
> "cache" idea which is something of _your_ system ibn theirs, and 
> propose them an update of _their_ system - like anti-virus updates 
> (ever heard that anti-virus run huge 50x1G systems? And let discover 
> what a user system can bring more to its user owner. So when the user 
> has started using and enjoying _his_ system, you will obtain what you 
> want.

Why would I want to reduce the number of calls on my system? My system 
is doing just fine...

- - kurtis -

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3

iQA/AwUBQKuHjqarNKXTPFCVEQJbDQCbBgjOmqDeK5bjzlbzlCVwB+XtkrIAoIpu
7V0w8Yq6Q6qxIKy1XRwtfHuX
=863T
-----END PGP SIGNATURE-----


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


From ietf-admin@ietf.org  Wed May 19 15:58: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 PAA09356
	for <ietf-archive@ietf.org>; Wed, 19 May 2004 15:58: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 1BQXCc-0003Rf-FK
	for ietf-archive@ietf.org; Wed, 19 May 2004 15:58:10 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQXBh-0003Hh-00
	for ietf-archive@ietf.org; Wed, 19 May 2004 15:57:14 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQXAn-000395-00
	for ietf-archive@ietf.org; Wed, 19 May 2004 15:56:18 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQWnR-0008Sb-Jr; Wed, 19 May 2004 15:32:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQWEb-0004gQ-0s
	for ietf@optimus.ietf.org; Wed, 19 May 2004 14:56: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 OAA00828
	for <ietf@ietf.org>; Wed, 19 May 2004 14:56: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 1BQWEY-0001NM-04
	for ietf@ietf.org; Wed, 19 May 2004 14:56:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQWDg-0001Go-00
	for ietf@ietf.org; Wed, 19 May 2004 14:55:13 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQWDE-00018k-00
	for ietf@ietf.org; Wed, 19 May 2004 14:54:44 -0400
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i4JIsCSu026003;
	Wed, 19 May 2004 11:54:12 -0700 (PDT)
Received: from localhost (ole@localhost) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id LAA16485; Wed, 19 May 2004 11:54:12 -0700 (PDT)
Date: Wed, 19 May 2004 11:54:12 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
Reply-To: Ole Jacobsen <ole@cisco.com>
To: Ken Hornstein <kenh@cmf.nrl.navy.mil>
cc: ietf@ietf.org
Subject: Re: 60th IETF - Registration 
In-Reply-To: <200405191437.i4JEbT7D024972@ginger.cmf.nrl.navy.mil>
Message-ID: <Pine.HPX.4.58.0405191147040.4012@wells.cisco.com>
References: <200405191437.i4JEbT7D024972@ginger.cmf.nrl.navy.mil>
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


The reason there are "no rooms available" through the normal online
reservation system is that the IETF "owns" a huge room block. I tried
booking at the end of MARCH having a hunch it would be this hotel. Same
story back then.


It would of course be nice if you could enter a special code and get the
IETF rate and availability, but this probably requires more programming
than the hotel is willing to throw into the deal. Only other alternative
would be to have the secretariat handle all hotel reservations on our
behalf, but that too is extra work and cost.


So, fax or phone is your friend in this case.

Ole

Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Academic Research and Technology Initiatives, Cisco Systems
Tel: +1 408-527-8972   GSM: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj




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


From exim@www1.ietf.org  Wed May 19 16:14:09 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10857
	for <ietf-archive@odin.ietf.org>; Wed, 19 May 2004 16:14: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 1BQX2D-0005D4-En
	for ietf-archive@odin.ietf.org; Wed, 19 May 2004 15:47:26 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4JJlP1h019767
	for ietf-archive@odin.ietf.org; Wed, 19 May 2004 15:47:25 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQWmC-00085r-SG; Wed, 19 May 2004 15:30:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQW6p-0002Y6-Ix
	for ietf@optimus.ietf.org; Wed, 19 May 2004 14:48:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29976
	for <ietf@ietf.org>; Wed, 19 May 2004 14:48: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 1BQW6m-0000Et-Kl
	for ietf@ietf.org; Wed, 19 May 2004 14:48:04 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQW5s-00004S-00
	for ietf@ietf.org; Wed, 19 May 2004 14:47:09 -0400
Received: from carwash.centive.com ([65.220.90.249])
	by ietf-mx with smtp (Exim 4.12)
	id 1BQW5K-0007ij-00
	for ietf@ietf.org; Wed, 19 May 2004 14:46:34 -0400
Received: from minglewood.incentivesystems.com ([10.10.30.25])
 by carwash.centive.com (SAVSMTP 3.1.3.37) with SMTP id M2004051914480824356
 for <ietf@ietf.org>; Wed, 19 May 2004 14:48:08 -0400
Received: from [10.10.48.119] ([10.10.48.119]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(6.0.3790.0);
	 Wed, 19 May 2004 14:42:06 -0400
Message-ID: <40ABAA7D.4040008@centive.com>
Date: Wed, 19 May 2004 14:42:06 -0400
From: John Stracke <jstracke@centive.com>
User-Agent: Mozilla Thunderbird 0.6 (Windows/20040502)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: 60th IETF - Registration
References: <200405191437.i4JEbT7D024972@ginger.cmf.nrl.navy.mil>
In-Reply-To: <200405191437.i4JEbT7D024972@ginger.cmf.nrl.navy.mil>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 May 2004 18:42:06.0229 (UTC) FILETIME=[FBEC8450:01C43DD0]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-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

Ken Hornstein wrote:

>To be fair ... I've certainly experienced the same thing at non-US IETF
>hotels (the one that sticks out in my mind is Adelaide, but I believe
>there were others).
>  
>
I remember setting my alarm for 3:00 AM to make a reservation for Oslo.

-- 
/============================================================\
|John Stracke      |jstracke@centive.com                     |
|Principal Engineer|http://www.centive.com                   |
|Centive           |My opinions are my own.                  |
|============================================================|
|In the country of the blind, the one-eyed man is in therapy.|
\============================================================/


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



From exim@www1.ietf.org  Wed May 19 16:14: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 QAA10925
	for <ietf-archive@odin.ietf.org>; Wed, 19 May 2004 16:14: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 1BQXAv-00071T-Ol
	for ietf-archive@odin.ietf.org; Wed, 19 May 2004 15:56:30 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4JJuPlg026521
	for ietf-archive@odin.ietf.org; Wed, 19 May 2004 15:56:25 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQWnR-0008Sb-Jr; Wed, 19 May 2004 15:32:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQWEb-0004gQ-0s
	for ietf@optimus.ietf.org; Wed, 19 May 2004 14:56: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 OAA00828
	for <ietf@ietf.org>; Wed, 19 May 2004 14:56: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 1BQWEY-0001NM-04
	for ietf@ietf.org; Wed, 19 May 2004 14:56:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQWDg-0001Go-00
	for ietf@ietf.org; Wed, 19 May 2004 14:55:13 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQWDE-00018k-00
	for ietf@ietf.org; Wed, 19 May 2004 14:54:44 -0400
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i4JIsCSu026003;
	Wed, 19 May 2004 11:54:12 -0700 (PDT)
Received: from localhost (ole@localhost) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id LAA16485; Wed, 19 May 2004 11:54:12 -0700 (PDT)
Date: Wed, 19 May 2004 11:54:12 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
Reply-To: Ole Jacobsen <ole@cisco.com>
To: Ken Hornstein <kenh@cmf.nrl.navy.mil>
cc: ietf@ietf.org
Subject: Re: 60th IETF - Registration 
In-Reply-To: <200405191437.i4JEbT7D024972@ginger.cmf.nrl.navy.mil>
Message-ID: <Pine.HPX.4.58.0405191147040.4012@wells.cisco.com>
References: <200405191437.i4JEbT7D024972@ginger.cmf.nrl.navy.mil>
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>


The reason there are "no rooms available" through the normal online
reservation system is that the IETF "owns" a huge room block. I tried
booking at the end of MARCH having a hunch it would be this hotel. Same
story back then.


It would of course be nice if you could enter a special code and get the
IETF rate and availability, but this probably requires more programming
than the hotel is willing to throw into the deal. Only other alternative
would be to have the secretariat handle all hotel reservations on our
behalf, but that too is extra work and cost.


So, fax or phone is your friend in this case.

Ole

Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Academic Research and Technology Initiatives, Cisco Systems
Tel: +1 408-527-8972   GSM: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj




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



From ietf-admin@ietf.org  Wed May 19 17:47: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 RAA21533
	for <ietf-archive@ietf.org>; Wed, 19 May 2004 17:47: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 1BQYtx-0006Aa-TM
	for ietf-archive@ietf.org; Wed, 19 May 2004 17:47:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQYsy-00060h-00
	for ietf-archive@ietf.org; Wed, 19 May 2004 17:46:01 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQYs0-0005qz-00
	for ietf-archive@ietf.org; Wed, 19 May 2004 17:45:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQYef-0001gx-Cb; Wed, 19 May 2004 17:31:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQXx3-0008GK-FM
	for ietf@optimus.ietf.org; Wed, 19 May 2004 16:46: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 QAA14132
	for <ietf@ietf.org>; Wed, 19 May 2004 16:45:56 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQXwr-00039E-2j
	for ietf@ietf.org; Wed, 19 May 2004 16:45:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQXvr-0002y0-00
	for ietf@ietf.org; Wed, 19 May 2004 16:44:56 -0400
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQXur-0002ij-00
	for ietf@ietf.org; Wed, 19 May 2004 16:43:53 -0400
Received: from f01v-38-32.d0.club-internet.fr ([212.195.249.32] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.24)
	id 1BQXun-0001OF-7z; Wed, 19 May 2004 13:43:49 -0700
Message-Id: <6.1.0.6.2.20040519210528.05d42a60@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 6.1.0.6
Date: Wed, 19 May 2004 21:46:53 +0200
To: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
From: jfcm <info@utel.net>
Subject: Re: Root Anycast
Cc: Måns Nilsson <mansaxel@besserwisser.org>, ietf@ietf.org
In-Reply-To: <6522B9F0-A9AF-11D8-8726-000A95928574@kurtis.pp.se>
References: <DFC3BD05-A84A-11D8-AC18-000A95CD987A@muada.com>
 <g3lljqegi6.fsf@sa.vix.com>
 <6.1.0.6.2.20040518171004.04666060@mail.utel.net>
 <114760000.1084908866@slimsixten.pilsnet.sunet.se>
 <6.1.0.6.2.20040519003547.059c3620@mail.utel.net>
 <6522B9F0-A9AF-11D8-8726-000A95928574@kurtis.pp.se>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - utel.net
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:12 19/05/04, Kurt Erik Lindqvist wrote:
> > - I talk of real world when you talk of the current (unsecure and
> > overloaded?) implementation of the current DNS architecture.
>
>In what way overloaded? Do you have any pointers? Proof? Data?

Dear Kurt Eric,
Let not play this, please. Either you think after careful personal study 
(or you believe) that the current system is the best solution the world 
needs, and that it only calls for some users to be more educated in using 
it - and we are on planets apart. This is fine with me, and the end of a 
non existing debate.

Or you think the DNS does not match the IETF "core values" in being 
centralized (I do not make that "core value" as described by Harald a 
creed, I think they are often outdated, but I fully agree they are a 
technical minimum). And, together with ICANN, you think IETF is the right 
place to respond ICANN's call for more (ICP-3). So you try to understand 
the problem and to imagine solutions. This is what we did. And I explain 
the solutions we are subsequently working on.

> > The problem we face is an old and too large unique system with a
> > robust yet overloaded engine. With all the problems which come with
> > it. We have to split the zones of usage and risks. Either it is
> > planned by IETF or it is done by the users. I suggest it is done
> > together.
>
>Again, overloaded engine in what way?

I just report on our follow up on this premise. If you do not see it, I 
cannot help with details. Just with the alternative. Yu are the judge.

The DNS "engine" is made of all the root/name servers and resolvers.
- either you are satisfied with their present tools, organization, 
limitations and resulting service, then again I cannot discuss it.
- or you are not, and then the question is to know if your disatisfaction 
results from the used solution or from the way this solution is implemented.

IMO the problem is not with the solution (software) but with its 
architectural deployment and usage. This permits a smooth transition, using 
existing and proven building blocks and expertise. But I think that speed 
if the essence. One may also disagree.

> > Then the agreed file
>Agreed by whom?  In what way?

Let me elaborate quickly. The target is not to obtain a file which pleases 
anyone as today, but a file which reports on the TLD Managers entries. So, 
the point is not who does it but the number of identical independent 
results. What follows is for one single national service.

- National because of the legal and political aspects in many aspects (risk 
containment, sensitive information intelligence leaks, justice obligations, 
etc.).
- But subsidiarity applies to the regional, local, corporate, private 
granularities (I explained what this means in my first mail).
- this means that security and verification will probably repeated 20 to 50 
times accross the world. Once a day in each country could mean every hour 
for global issues such as the DNS (the protocol is the same for every root 
information [time, radio frequencies, weather, hospital situation, etc])

The process we retained is to have at least four different independent data 
collection processes (whatever the processes, starting with a simple 
duplication of the NTIA file in the case of the DNS legacy root). The 
reason for at least 4 is to have at a majority if needed, even if one is down.

There must be five conditions for the result to be accepted (there could be 
more?)
1. there must be no reported alarm (nominal situation) on our monitoring system
2. all the results must be identical
3. there must not be an abnormally large difference with preceding copy 
(variance max to be tuned from experience) - to allow reasonable updates if 
permitted.
4. visual review by the four collection managers is positive
5. there must be no significant (similar to 3) with other partenering root 
files on common part of the root matrix.

If these 5 conditions are not met there will be an investigation and 
concerted agreement to be reached among collection managers, or a "no go" 
and escalation to Execom and to BoD (or Gov). These conditions (or more) 
can be made legal and imposed before a State endorses a Root Service for 
its own use and for legal transactions.

There is a possible alternative: the decision of the Government in case of 
national vital crisis. The role of the collection managers will be to 
advise how to reduce pollution in such cases - this may call for 
international concertation [exemple: the "ambassador lounge" at ITU 
(telephone is real time, no 48 hours delay). A doctrine is to be set-up as 
part of Digital Warfare (US say Cybernetic Warfare). Experience in Mines, 
Electronic or Nuclear Warfares shows this is possible.

> > You want to reduce the calls to your system, right? Let stop the
> > "cache" idea which is something of _your_ system ibn theirs, and
> > propose them an update of _their_ system - like anti-virus updates
> > (ever heard that anti-virus run huge 50x1G systems? And let discover
> > what a user system can bring more to its user owner. So when the user
> > has started using and enjoying _his_ system, you will obtain what you
> > want.
>
>Why would I want to reduce the number of calls on my system? My system  is 
>doing just fine...

What is your system ?

In the case discussed the problem is the current increasing load on current 
servers. That load and that type of calls are inappropriate. The 
architecture is to be changed (all the more than it permits DoS). Keeping 
daily updated files of much larger size than the root file is carried by 
many people around the world more efficiently, more securely and with less 
of constraints to innovative usages.

But again, the very nature of the DNS permits such transition to be 
transparent. So if you love the current architecture, it is OK with me. As 
long as you do not pollute what we do and we do not pollute what you do 
there is no problem. This discussion only concerns those (with ICANN ICP-3) 
who want to experiment and work on the resulting experience, towards a 
better response to the people and Gov demands.

I just describe what we have started working on, with scarce resources, 
along those lines for more than two years. And what we target from then on.
jfc



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


From exim@www1.ietf.org  Wed May 19 17:56:26 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22218
	for <ietf-archive@odin.ietf.org>; Wed, 19 May 2004 17:56: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 1BQYs2-0006xa-J6
	for ietf-archive@odin.ietf.org; Wed, 19 May 2004 17:45:10 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4JLj2Ke026744
	for ietf-archive@odin.ietf.org; Wed, 19 May 2004 17:45:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQYef-0001gx-Cb; Wed, 19 May 2004 17:31:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQXx3-0008GK-FM
	for ietf@optimus.ietf.org; Wed, 19 May 2004 16:46: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 QAA14132
	for <ietf@ietf.org>; Wed, 19 May 2004 16:45:56 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQXwr-00039E-2j
	for ietf@ietf.org; Wed, 19 May 2004 16:45:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQXvr-0002y0-00
	for ietf@ietf.org; Wed, 19 May 2004 16:44:56 -0400
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQXur-0002ij-00
	for ietf@ietf.org; Wed, 19 May 2004 16:43:53 -0400
Received: from f01v-38-32.d0.club-internet.fr ([212.195.249.32] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.24)
	id 1BQXun-0001OF-7z; Wed, 19 May 2004 13:43:49 -0700
Message-Id: <6.1.0.6.2.20040519210528.05d42a60@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 6.1.0.6
Date: Wed, 19 May 2004 21:46:53 +0200
To: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
From: jfcm <info@utel.net>
Subject: Re: Root Anycast
Cc: Måns Nilsson <mansaxel@besserwisser.org>, ietf@ietf.org
In-Reply-To: <6522B9F0-A9AF-11D8-8726-000A95928574@kurtis.pp.se>
References: <DFC3BD05-A84A-11D8-AC18-000A95CD987A@muada.com>
 <g3lljqegi6.fsf@sa.vix.com>
 <6.1.0.6.2.20040518171004.04666060@mail.utel.net>
 <114760000.1084908866@slimsixten.pilsnet.sunet.se>
 <6.1.0.6.2.20040519003547.059c3620@mail.utel.net>
 <6522B9F0-A9AF-11D8-8726-000A95928574@kurtis.pp.se>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - utel.net
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.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:12 19/05/04, Kurt Erik Lindqvist wrote:
> > - I talk of real world when you talk of the current (unsecure and
> > overloaded?) implementation of the current DNS architecture.
>
>In what way overloaded? Do you have any pointers? Proof? Data?

Dear Kurt Eric,
Let not play this, please. Either you think after careful personal study 
(or you believe) that the current system is the best solution the world 
needs, and that it only calls for some users to be more educated in using 
it - and we are on planets apart. This is fine with me, and the end of a 
non existing debate.

Or you think the DNS does not match the IETF "core values" in being 
centralized (I do not make that "core value" as described by Harald a 
creed, I think they are often outdated, but I fully agree they are a 
technical minimum). And, together with ICANN, you think IETF is the right 
place to respond ICANN's call for more (ICP-3). So you try to understand 
the problem and to imagine solutions. This is what we did. And I explain 
the solutions we are subsequently working on.

> > The problem we face is an old and too large unique system with a
> > robust yet overloaded engine. With all the problems which come with
> > it. We have to split the zones of usage and risks. Either it is
> > planned by IETF or it is done by the users. I suggest it is done
> > together.
>
>Again, overloaded engine in what way?

I just report on our follow up on this premise. If you do not see it, I 
cannot help with details. Just with the alternative. Yu are the judge.

The DNS "engine" is made of all the root/name servers and resolvers.
- either you are satisfied with their present tools, organization, 
limitations and resulting service, then again I cannot discuss it.
- or you are not, and then the question is to know if your disatisfaction 
results from the used solution or from the way this solution is implemented.

IMO the problem is not with the solution (software) but with its 
architectural deployment and usage. This permits a smooth transition, using 
existing and proven building blocks and expertise. But I think that speed 
if the essence. One may also disagree.

> > Then the agreed file
>Agreed by whom?  In what way?

Let me elaborate quickly. The target is not to obtain a file which pleases 
anyone as today, but a file which reports on the TLD Managers entries. So, 
the point is not who does it but the number of identical independent 
results. What follows is for one single national service.

- National because of the legal and political aspects in many aspects (risk 
containment, sensitive information intelligence leaks, justice obligations, 
etc.).
- But subsidiarity applies to the regional, local, corporate, private 
granularities (I explained what this means in my first mail).
- this means that security and verification will probably repeated 20 to 50 
times accross the world. Once a day in each country could mean every hour 
for global issues such as the DNS (the protocol is the same for every root 
information [time, radio frequencies, weather, hospital situation, etc])

The process we retained is to have at least four different independent data 
collection processes (whatever the processes, starting with a simple 
duplication of the NTIA file in the case of the DNS legacy root). The 
reason for at least 4 is to have at a majority if needed, even if one is down.

There must be five conditions for the result to be accepted (there could be 
more?)
1. there must be no reported alarm (nominal situation) on our monitoring system
2. all the results must be identical
3. there must not be an abnormally large difference with preceding copy 
(variance max to be tuned from experience) - to allow reasonable updates if 
permitted.
4. visual review by the four collection managers is positive
5. there must be no significant (similar to 3) with other partenering root 
files on common part of the root matrix.

If these 5 conditions are not met there will be an investigation and 
concerted agreement to be reached among collection managers, or a "no go" 
and escalation to Execom and to BoD (or Gov). These conditions (or more) 
can be made legal and imposed before a State endorses a Root Service for 
its own use and for legal transactions.

There is a possible alternative: the decision of the Government in case of 
national vital crisis. The role of the collection managers will be to 
advise how to reduce pollution in such cases - this may call for 
international concertation [exemple: the "ambassador lounge" at ITU 
(telephone is real time, no 48 hours delay). A doctrine is to be set-up as 
part of Digital Warfare (US say Cybernetic Warfare). Experience in Mines, 
Electronic or Nuclear Warfares shows this is possible.

> > You want to reduce the calls to your system, right? Let stop the
> > "cache" idea which is something of _your_ system ibn theirs, and
> > propose them an update of _their_ system - like anti-virus updates
> > (ever heard that anti-virus run huge 50x1G systems? And let discover
> > what a user system can bring more to its user owner. So when the user
> > has started using and enjoying _his_ system, you will obtain what you
> > want.
>
>Why would I want to reduce the number of calls on my system? My system  is 
>doing just fine...

What is your system ?

In the case discussed the problem is the current increasing load on current 
servers. That load and that type of calls are inappropriate. The 
architecture is to be changed (all the more than it permits DoS). Keeping 
daily updated files of much larger size than the root file is carried by 
many people around the world more efficiently, more securely and with less 
of constraints to innovative usages.

But again, the very nature of the DNS permits such transition to be 
transparent. So if you love the current architecture, it is OK with me. As 
long as you do not pollute what we do and we do not pollute what you do 
there is no problem. This discussion only concerns those (with ICANN ICP-3) 
who want to experiment and work on the resulting experience, towards a 
better response to the people and Gov demands.

I just describe what we have started working on, with scarce resources, 
along those lines for more than two years. And what we target from then on.
jfc



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



From exim@www1.ietf.org  Wed May 19 22:48: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 WAA07582
	for <ietf-archive@odin.ietf.org>; Wed, 19 May 2004 22:48: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 1BQdaU-0006UM-S4
	for ietf-archive@odin.ietf.org; Wed, 19 May 2004 22:47:15 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4K2lE9v024937
	for ietf-archive@odin.ietf.org; Wed, 19 May 2004 22:47:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQdSb-0004Ow-TM; Wed, 19 May 2004 22:39:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQdOz-0002kG-4n
	for ietf@optimus.ietf.org; Wed, 19 May 2004 22:35: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 WAA07048
	for <ietf@ietf.org>; Wed, 19 May 2004 22:35: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 1BQdOv-0003xq-H7
	for ietf@ietf.org; Wed, 19 May 2004 22:35:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQdO0-0003qC-00
	for ietf@ietf.org; Wed, 19 May 2004 22:34:21 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQdNW-0003gt-00
	for ietf@ietf.org; Wed, 19 May 2004 22:33:50 -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 i4K2XAKg021065
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 19 May 2004 22:33:13 -0400
Date: Wed, 19 May 2004 22:33:10 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Harald Tveit Alvestrand <harald@alvestrand.no>
cc: ietf@ietf.org
Subject: Re: [dnsop] Re: Complaint on abuse of DNSOP lists
In-Reply-To: <126284898.1084913540@localhost>
Message-ID: <Pine.LNX.4.44.0405192230260.20973-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>

This isn't really a serious resolution.

It smacks exactly of the Army's response to the red cross over abuse at 
Abu Graib. For months, the Army has said it responded promptly to the Red 
Cross' written complaints. Today, in the NY Times, it was revealed what 
the response was:  Tell us when you are coming, and we will hide the abuse 
before you get here. 

A personal attack is "infantile", "irresponsible", and "immature".  
Calling a personal attack what it is, it not itself a personal attack. 

Talk about going through the looking glass.

		--Dean

On Tue, 18 May 2004, Harald Tveit Alvestrand wrote:

> Mr. Anderson,
> 
> I note that your use of the terms "infantile", "irresponsible" and 
> "immature" are personal attacks. These are inappropriate for the IETF list.
> 
> If you have serious complaints to make that you feel require you to use 
> these terms, send them to me privately.
> 
> If you want to send mail to the public IETF list, be civil.
> 
> You have been warned.
> 
>                     Harald Alvestrand
> 
> --On 18. mai 2004 18:36 -0400 Dean Anderson <dean@av8.com> wrote:
> 
> > Sigh.
> >
> > Harald, Please add __Another__ complaint to the chair about inappropriate
> > behavior by Mr. Vixie.
> >
> > Oh wait, could it be that lying to the general public saying our address
> > space is hijacked is a personal attack?  Hmm.  Maybe they aren't as
> > 'perfessional' as they made out to be.  Maybe these attacks aren't as
> > unrelated to the IETF as the Chair asserts.
> >
> > I guess those that have to resort to name-calling don't have anything else
> > ot resort to, since they can't resort to facts.  And of course, indeed, no
> > contrary _facts_ have been given. Well, Vixie hasn't changed in 15 years,
> > still as infantile as ever.
> >
> > And these irresponsible and immature people have operational control of a
> > root nameserver.  How did that ever happen?  That too, should be changed.
> >
> > 		--Dean
> >
> > On 17 May 2004, Paul Vixie wrote:
> >
> >> dean@av8.com (Dean Anderson) writes:
> >>
> >> > ... For the less technical, an exchange point is ...
> >>
> >> I don't think there's anyone on this list less technical than you, Dean.
> >>
> >
> >
> >
> >
> >
> 
> 
> 
> 
> 


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



From ietf-admin@ietf.org  Wed May 19 22:49: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 WAA07603
	for <ietf-archive@ietf.org>; Wed, 19 May 2004 22:49: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 1BQdcL-00068M-Dp
	for ietf-archive@ietf.org; Wed, 19 May 2004 22:49:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQdbO-0005vq-00
	for ietf-archive@ietf.org; Wed, 19 May 2004 22:48:10 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQdaR-0005kQ-00
	for ietf-archive@ietf.org; Wed, 19 May 2004 22:47:11 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQdSb-0004Ow-TM; Wed, 19 May 2004 22:39:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQdOz-0002kG-4n
	for ietf@optimus.ietf.org; Wed, 19 May 2004 22:35: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 WAA07048
	for <ietf@ietf.org>; Wed, 19 May 2004 22:35: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 1BQdOv-0003xq-H7
	for ietf@ietf.org; Wed, 19 May 2004 22:35:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQdO0-0003qC-00
	for ietf@ietf.org; Wed, 19 May 2004 22:34:21 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQdNW-0003gt-00
	for ietf@ietf.org; Wed, 19 May 2004 22:33:50 -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 i4K2XAKg021065
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 19 May 2004 22:33:13 -0400
Date: Wed, 19 May 2004 22:33:10 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Harald Tveit Alvestrand <harald@alvestrand.no>
cc: ietf@ietf.org
Subject: Re: [dnsop] Re: Complaint on abuse of DNSOP lists
In-Reply-To: <126284898.1084913540@localhost>
Message-ID: <Pine.LNX.4.44.0405192230260.20973-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

This isn't really a serious resolution.

It smacks exactly of the Army's response to the red cross over abuse at 
Abu Graib. For months, the Army has said it responded promptly to the Red 
Cross' written complaints. Today, in the NY Times, it was revealed what 
the response was:  Tell us when you are coming, and we will hide the abuse 
before you get here. 

A personal attack is "infantile", "irresponsible", and "immature".  
Calling a personal attack what it is, it not itself a personal attack. 

Talk about going through the looking glass.

		--Dean

On Tue, 18 May 2004, Harald Tveit Alvestrand wrote:

> Mr. Anderson,
> 
> I note that your use of the terms "infantile", "irresponsible" and 
> "immature" are personal attacks. These are inappropriate for the IETF list.
> 
> If you have serious complaints to make that you feel require you to use 
> these terms, send them to me privately.
> 
> If you want to send mail to the public IETF list, be civil.
> 
> You have been warned.
> 
>                     Harald Alvestrand
> 
> --On 18. mai 2004 18:36 -0400 Dean Anderson <dean@av8.com> wrote:
> 
> > Sigh.
> >
> > Harald, Please add __Another__ complaint to the chair about inappropriate
> > behavior by Mr. Vixie.
> >
> > Oh wait, could it be that lying to the general public saying our address
> > space is hijacked is a personal attack?  Hmm.  Maybe they aren't as
> > 'perfessional' as they made out to be.  Maybe these attacks aren't as
> > unrelated to the IETF as the Chair asserts.
> >
> > I guess those that have to resort to name-calling don't have anything else
> > ot resort to, since they can't resort to facts.  And of course, indeed, no
> > contrary _facts_ have been given. Well, Vixie hasn't changed in 15 years,
> > still as infantile as ever.
> >
> > And these irresponsible and immature people have operational control of a
> > root nameserver.  How did that ever happen?  That too, should be changed.
> >
> > 		--Dean
> >
> > On 17 May 2004, Paul Vixie wrote:
> >
> >> dean@av8.com (Dean Anderson) writes:
> >>
> >> > ... For the less technical, an exchange point is ...
> >>
> >> I don't think there's anyone on this list less technical than you, Dean.
> >>
> >
> >
> >
> >
> >
> 
> 
> 
> 
> 


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


From ietf-admin@ietf.org  Thu May 20 00:05: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 AAA11031
	for <ietf-archive@ietf.org>; Thu, 20 May 2004 00:05:20 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQeo5-0001bj-CY
	for ietf-archive@ietf.org; Thu, 20 May 2004 00:05:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQenD-0001Rz-00
	for ietf-archive@ietf.org; Thu, 20 May 2004 00:04:28 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQemJ-0001IK-00
	for ietf-archive@ietf.org; Thu, 20 May 2004 00:03:31 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQedA-00040k-7A; Wed, 19 May 2004 23:54:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQeTf-0001GP-QY
	for ietf@optimus.ietf.org; Wed, 19 May 2004 23:44:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA10380
	for <ietf@ietf.org>; Wed, 19 May 2004 23:44: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 1BQeTd-0006QY-FQ
	for ietf@ietf.org; Wed, 19 May 2004 23:44:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQeSi-0006Iq-00
	for ietf@ietf.org; Wed, 19 May 2004 23:43:17 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQeS1-000638-00
	for ietf@ietf.org; Wed, 19 May 2004 23:42: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 i4K3g1i2022337
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 19 May 2004 23:42:02 -0400
Date: Wed, 19 May 2004 23:42:01 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Harald Tveit Alvestrand <harald@alvestrand.no>
cc: ietf@ietf.org
Subject: Re: Response to complaint from Dean Anderson
In-Reply-To: <128882262.1084916137@localhost>
Message-ID: <Pine.LNX.4.44.0405192233180.20973-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, 18 May 2004, Harald Tveit Alvestrand wrote:

> After re-checking with legal counsel, I repeat what I said before, trying 
> to be as clear as possible:
> 
>    Bouncing a message to the sender is NOT public defamation.

Not by itself, no. But that isn't the whole story of what happened. It is
always a bad thing to mislead your counsel as to the facts. This is
typically the case though, unfortunately, having been though it before.
People tend to put their own "spin" on the tale they tell their counsel,
leaving out a lot of important details.  Later, those details are
provided--that's the beauty of the legal process.

Here's a quick summary:

After becoming aware of defamatory comments being made by ISC.ORG
participants who were using 'harrassment by computer' techniques to
automatically send or began to send messages to all Av8 Internet customers
who participate in the IETF.  Unsuspecting Av8 Internet customers who
partipated in the IETF and who sent mail in response to ISC.ORG messages
involving IETF business were automatically sent these harrassing,
defamatory, and disparaging messages.  These ISC.ORG participants
eventually included IETF representatives.  The harrassing computer
response messages falsely claimed that Av8 Internet's IP Address space was
hijacked.

I was then forced to forward the defamatory messages to the IETF and DNSOP
lists in order to make a complaint.  This forced republication is the
legal responsiblity of the original sender: Paul Vixie, Joe Abley, and Rob
Austein and possibly involving ISC and SORBS depending on as yet unknown
relationships between them. Rob Austein was an IETF representative acting
on behalf of the IETF.  I note that while 47 USC 230 provides a fairly
general protection against defamation by electronic republishing, it only
provides that protection to those who are behaving consistently with its
stated policy, and has no effect on law (eg defamation claims) that is
consistent with its policy. Its policy is to _prevent_ harrassment by
computer, and so, in this case, it provides no protection to the IETF with
respect to republishing harrassment by computer.

Further, the message from Mr Austein was involving IETF business, and from
an IETF representative, direct IETF speech to customers of Av8 Internet
for which the IETF is legally responsible, and for which I was also forced
to republish to the appropriate IETF lists in order to make a complaint.

The message in question came from Mr. Austein and was with his permission
and knowledge (otherwise there would be an ECPA violation).  Mr. Austein
is clearly participating in defamatory and harrassing conduct, of the very
sort that 47 USC 230 expects as policy to prohibit. (see 47 USC 230
(b)(5)).

47 USC 230 (d)(3) specifies that the statute doesn't affect any state law
that is consistent with this statute. Therefore, it can't be used in
against the stated policy as stated in section (b) of the statute.  I
don't think 47 USC 230 can be used to completely disable every defamation
claim. It will only disable those claims that are inconsistent with the
stated policy in Section (b).  However, the 47 USC 230 exemption does not
apply to Mr. Austein's, Mr. Bush's, or Mr. Alvestrand's comments, since
those comments were on behalf of the IETF, and so the IETF is the original
publisher of those comments.

Then there is the defamatory and disparaging statements made by Randy
Bush, in his role as WG chair.  That was not even a bounce, as you
apparently described it to your counsel.  Yet it is still disparaging.
Again, the IETF is the original publisher, and these commets are the legal
responsibility of the IETF.

Recently, Paul Vixie sent another disparaging ad hominem attack to the
IETF list, disparaging Dean Anderson, and by implication, Av8 Internet.  
A complaint was again made to Mr. Alvestrand, the IETF chairman. Instead
of chastising Mr. Vixie, Mr Alvestrand chastised Dean Anderson for his
characterization of Mr. Vixie's ad hominem as 'infantile, irresponsible
and immature'. That is a fair description of any ad hominem attack, and is
a fair description of Mr. Vixie's ad hominem attack.  Mr. Alvestrand's
unreasonable behavior in this incident reveals his latent hostility to
Dean Anderson and Av8 Internet, which adds further substance to the claim
that the IETF has, inter alia, defamed and commercially disparaged Av8
Internet.

Mr. Austein's and hence the IETF's participation in a group boycott known
as the SORBS list, which is supported and promoted by ISC, is unlawful and
a violation of, inter alia, the Sherman Act.

> Therefore, your complaint about "defamation" has no merit.
> 
> Dean, I believe that:
> 
> - your complaint about the apparently incorrect ownership listing of AV8's 
> address space is with ARIN

ARIN has nothing to do with this. ARIN has done nothing wrong, and neither
has Av8. There is no incorrect ownership listing by ARIN. Your false claim
is an original false claim by the IETF that many would interpret as
stating a fact. This is itself defamatory since it is false and suggests
that either ARIN or Av8 Internet has done something wrong or that there is
an incorrect ownership listing. The IETF has again directly made false and
defamatory statements.  These are also not "bounces" as you apparently
described them to your counsel.

> - your complaint about the listing of this address space with SORBS is with 
> SORBS
> - your complaint about ISC's use of SORBS is with ISC

And the ISC is run by Paul Vixie, who has just posted his own abusive and
inappropriate comments, which I note that Mr. Alvestrand failed to
chastise, but instead chastised our complaint. Our only involvement with
the ISC and Mr. Vixie is through the IETF.  Mr. Vixie's abuse is directly
and very nearly exclusively in the IETF.  Mr. Alvestrand has now made the
false, defamatory, and disparaging statement that there is some incorrect
ownership listing in the ARIN records. That is also not a "bounce" as you
apparently described it to your counsel.

> None of these are issues that the IETF can solve for you. They are not 
> matters that are relevant to the IETF list.

Another false (but not defamatory) statement. There are a number of things
the IETF can do, and is morally obligated (and perhaps legally obligated)  
by the IETF and ISOC Code of Conduct, and the IETF Mission Statement:

1)  The IETF can publicly tell Mr Vixie to stop its harrassment by
computer of Av8 Internet.

2) In response to Mr. Vixie efforts in trying to use the IETF lists to use
harrassment by computer techniques to tell Av8 Internet and its customers
that they should change their email addresses, the IETF can tell Mr. Vixie
to use different addresses on the IETF lists.  Mr. Abley readily
acknowledged that he routinely uses other addresses. It is clear that Mr.
Austein also has other email addresses.

3) The IETF can tell Mr. Austein that he must accept email from _all_ IETF
participants in his role as an IETF Working Group Chair.

4) The IETF can stop participating in unlawful group boycotts in violation 
of the Sherman Act.

5) The IETF can stop making original defamatory and commercially
disparaging statements against Av8 Internet.

6) The IETF can apologize for its past abuses of Av8 Internet and others.

7) The IETF can renounce its unfair and unequal relationship with Paul
Vixie and ISC.ORG which is in violation of its Mission Statement.

These are not unreasonable requests.

> 
> Take care.
> 
>                     Harald Alvestrand
> 
> 




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


From exim@www1.ietf.org  Thu May 20 00: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 AAA11221
	for <ietf-archive@odin.ietf.org>; Thu, 20 May 2004 00: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 1BQemK-0006Fs-NV
	for ietf-archive@odin.ietf.org; Thu, 20 May 2004 00:03:33 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4K43WAa024035
	for ietf-archive@odin.ietf.org; Thu, 20 May 2004 00:03:32 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQedA-00040k-7A; Wed, 19 May 2004 23:54:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQeTf-0001GP-QY
	for ietf@optimus.ietf.org; Wed, 19 May 2004 23:44:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA10380
	for <ietf@ietf.org>; Wed, 19 May 2004 23:44: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 1BQeTd-0006QY-FQ
	for ietf@ietf.org; Wed, 19 May 2004 23:44:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQeSi-0006Iq-00
	for ietf@ietf.org; Wed, 19 May 2004 23:43:17 -0400
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQeS1-000638-00
	for ietf@ietf.org; Wed, 19 May 2004 23:42: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 i4K3g1i2022337
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 19 May 2004 23:42:02 -0400
Date: Wed, 19 May 2004 23:42:01 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Harald Tveit Alvestrand <harald@alvestrand.no>
cc: ietf@ietf.org
Subject: Re: Response to complaint from Dean Anderson
In-Reply-To: <128882262.1084916137@localhost>
Message-ID: <Pine.LNX.4.44.0405192233180.20973-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, 18 May 2004, Harald Tveit Alvestrand wrote:

> After re-checking with legal counsel, I repeat what I said before, trying 
> to be as clear as possible:
> 
>    Bouncing a message to the sender is NOT public defamation.

Not by itself, no. But that isn't the whole story of what happened. It is
always a bad thing to mislead your counsel as to the facts. This is
typically the case though, unfortunately, having been though it before.
People tend to put their own "spin" on the tale they tell their counsel,
leaving out a lot of important details.  Later, those details are
provided--that's the beauty of the legal process.

Here's a quick summary:

After becoming aware of defamatory comments being made by ISC.ORG
participants who were using 'harrassment by computer' techniques to
automatically send or began to send messages to all Av8 Internet customers
who participate in the IETF.  Unsuspecting Av8 Internet customers who
partipated in the IETF and who sent mail in response to ISC.ORG messages
involving IETF business were automatically sent these harrassing,
defamatory, and disparaging messages.  These ISC.ORG participants
eventually included IETF representatives.  The harrassing computer
response messages falsely claimed that Av8 Internet's IP Address space was
hijacked.

I was then forced to forward the defamatory messages to the IETF and DNSOP
lists in order to make a complaint.  This forced republication is the
legal responsiblity of the original sender: Paul Vixie, Joe Abley, and Rob
Austein and possibly involving ISC and SORBS depending on as yet unknown
relationships between them. Rob Austein was an IETF representative acting
on behalf of the IETF.  I note that while 47 USC 230 provides a fairly
general protection against defamation by electronic republishing, it only
provides that protection to those who are behaving consistently with its
stated policy, and has no effect on law (eg defamation claims) that is
consistent with its policy. Its policy is to _prevent_ harrassment by
computer, and so, in this case, it provides no protection to the IETF with
respect to republishing harrassment by computer.

Further, the message from Mr Austein was involving IETF business, and from
an IETF representative, direct IETF speech to customers of Av8 Internet
for which the IETF is legally responsible, and for which I was also forced
to republish to the appropriate IETF lists in order to make a complaint.

The message in question came from Mr. Austein and was with his permission
and knowledge (otherwise there would be an ECPA violation).  Mr. Austein
is clearly participating in defamatory and harrassing conduct, of the very
sort that 47 USC 230 expects as policy to prohibit. (see 47 USC 230
(b)(5)).

47 USC 230 (d)(3) specifies that the statute doesn't affect any state law
that is consistent with this statute. Therefore, it can't be used in
against the stated policy as stated in section (b) of the statute.  I
don't think 47 USC 230 can be used to completely disable every defamation
claim. It will only disable those claims that are inconsistent with the
stated policy in Section (b).  However, the 47 USC 230 exemption does not
apply to Mr. Austein's, Mr. Bush's, or Mr. Alvestrand's comments, since
those comments were on behalf of the IETF, and so the IETF is the original
publisher of those comments.

Then there is the defamatory and disparaging statements made by Randy
Bush, in his role as WG chair.  That was not even a bounce, as you
apparently described it to your counsel.  Yet it is still disparaging.
Again, the IETF is the original publisher, and these commets are the legal
responsibility of the IETF.

Recently, Paul Vixie sent another disparaging ad hominem attack to the
IETF list, disparaging Dean Anderson, and by implication, Av8 Internet.  
A complaint was again made to Mr. Alvestrand, the IETF chairman. Instead
of chastising Mr. Vixie, Mr Alvestrand chastised Dean Anderson for his
characterization of Mr. Vixie's ad hominem as 'infantile, irresponsible
and immature'. That is a fair description of any ad hominem attack, and is
a fair description of Mr. Vixie's ad hominem attack.  Mr. Alvestrand's
unreasonable behavior in this incident reveals his latent hostility to
Dean Anderson and Av8 Internet, which adds further substance to the claim
that the IETF has, inter alia, defamed and commercially disparaged Av8
Internet.

Mr. Austein's and hence the IETF's participation in a group boycott known
as the SORBS list, which is supported and promoted by ISC, is unlawful and
a violation of, inter alia, the Sherman Act.

> Therefore, your complaint about "defamation" has no merit.
> 
> Dean, I believe that:
> 
> - your complaint about the apparently incorrect ownership listing of AV8's 
> address space is with ARIN

ARIN has nothing to do with this. ARIN has done nothing wrong, and neither
has Av8. There is no incorrect ownership listing by ARIN. Your false claim
is an original false claim by the IETF that many would interpret as
stating a fact. This is itself defamatory since it is false and suggests
that either ARIN or Av8 Internet has done something wrong or that there is
an incorrect ownership listing. The IETF has again directly made false and
defamatory statements.  These are also not "bounces" as you apparently
described them to your counsel.

> - your complaint about the listing of this address space with SORBS is with 
> SORBS
> - your complaint about ISC's use of SORBS is with ISC

And the ISC is run by Paul Vixie, who has just posted his own abusive and
inappropriate comments, which I note that Mr. Alvestrand failed to
chastise, but instead chastised our complaint. Our only involvement with
the ISC and Mr. Vixie is through the IETF.  Mr. Vixie's abuse is directly
and very nearly exclusively in the IETF.  Mr. Alvestrand has now made the
false, defamatory, and disparaging statement that there is some incorrect
ownership listing in the ARIN records. That is also not a "bounce" as you
apparently described it to your counsel.

> None of these are issues that the IETF can solve for you. They are not 
> matters that are relevant to the IETF list.

Another false (but not defamatory) statement. There are a number of things
the IETF can do, and is morally obligated (and perhaps legally obligated)  
by the IETF and ISOC Code of Conduct, and the IETF Mission Statement:

1)  The IETF can publicly tell Mr Vixie to stop its harrassment by
computer of Av8 Internet.

2) In response to Mr. Vixie efforts in trying to use the IETF lists to use
harrassment by computer techniques to tell Av8 Internet and its customers
that they should change their email addresses, the IETF can tell Mr. Vixie
to use different addresses on the IETF lists.  Mr. Abley readily
acknowledged that he routinely uses other addresses. It is clear that Mr.
Austein also has other email addresses.

3) The IETF can tell Mr. Austein that he must accept email from _all_ IETF
participants in his role as an IETF Working Group Chair.

4) The IETF can stop participating in unlawful group boycotts in violation 
of the Sherman Act.

5) The IETF can stop making original defamatory and commercially
disparaging statements against Av8 Internet.

6) The IETF can apologize for its past abuses of Av8 Internet and others.

7) The IETF can renounce its unfair and unequal relationship with Paul
Vixie and ISC.ORG which is in violation of its Mission Statement.

These are not unreasonable requests.

> 
> Take care.
> 
>                     Harald Alvestrand
> 
> 




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



From exim@www1.ietf.org  Thu May 20 01:00:07 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 BAA13597
	for <ietf-archive@odin.ietf.org>; Thu, 20 May 2004 01:00: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 1BQfdd-0003lg-Nm
	for ietf-archive@odin.ietf.org; Thu, 20 May 2004 00:58:37 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4K4wbF7014428
	for ietf-archive@odin.ietf.org; Thu, 20 May 2004 00:58:37 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQfUN-0001E8-PJ; Thu, 20 May 2004 00:49:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQfSi-0000pK-Dz
	for ietf@optimus.ietf.org; Thu, 20 May 2004 00:47:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA12937
	for <ietf@ietf.org>; Thu, 20 May 2004 00:47: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 1BQfSf-0000DB-FO
	for ietf@ietf.org; Thu, 20 May 2004 00:47:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQfRf-000021-00
	for ietf@ietf.org; Thu, 20 May 2004 00:46:15 -0400
Received: from 149.cust48.nsw.dsl.ozemail.com.au ([203.103.127.149] helo=nosense.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQfQd-0007Yp-00
	for ietf@ietf.org; Thu, 20 May 2004 00:45:12 -0400
Received: from Dupy2.nosense.org (localhost.localdomain [127.0.0.1])
	by nosense.org (Postfix) with SMTP
	id F2CDA3F02A; Thu, 20 May 2004 14:14:39 +0930 (CST)
Date: Thu, 20 May 2004 14:14:39 +0930
From: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
To: Dean Anderson <dean@av8.com>
Cc: harald@alvestrand.no, ietf@ietf.org
Subject: Re: Response to complaint from Dean Anderson
Message-Id: <20040520141439.2e64ca9d.ietf@130c04165a5b40404e4440445758487a.nosense.org>
In-Reply-To: <Pine.LNX.4.44.0405192233180.20973-100000@cirrus.av8.net>
References: <128882262.1084916137@localhost>
	<Pine.LNX.4.44.0405192233180.20973-100000@cirrus.av8.net>
Organization: The No Sense Organisation (http://www.nosense.org)
X-Mailer: Sylpheed version 0.9.10 (GTK+ 1.2.10; i686-pc-linux-gnu)
X-Location: Adelaide, Australia
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-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 Wed, 19 May 2004 23:42:01 -0400 (EDT)
Dean Anderson <dean@av8.com> wrote:

> On Tue, 18 May 2004, Harald Tveit Alvestrand wrote:
> 

<snip - whole lot of legal stuff that I don't have time to
read - I've got a few thousand RFCs to go ...>

Firstly, let me say that it is really sad that legalease, legal
council and legal positions have appeared on an IETF mailing
list to the extent we've seen. I've understood that the IETF was
all about best technical solutions and positions, not best legal
solutions and positions.

Dean, I'm in no position to implement this as a solution (nor
have I spent time thinking about how hard or easy it
would be to implement), however, presuming that @ietf.org doesn't
implement MTA blocking via methods such as SORBS, and I don't
think they do, would you be happy if all people who have official
IETF positions (eg. area advisor, working group chair, etc) had
@ietf.org email addresses, and used those for any IETF related
correspondence ?

Regards,
Mark.

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



From ietf-admin@ietf.org  Thu May 20 01:00: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 BAA13636
	for <ietf-archive@ietf.org>; Thu, 20 May 2004 01:00:29 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQffQ-0002TU-Ds
	for ietf-archive@ietf.org; Thu, 20 May 2004 01:00:28 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQfeU-0002HS-00
	for ietf-archive@ietf.org; Thu, 20 May 2004 00:59:30 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQfdb-00027u-00
	for ietf-archive@ietf.org; Thu, 20 May 2004 00:58:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQfUN-0001E8-PJ; Thu, 20 May 2004 00:49:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQfSi-0000pK-Dz
	for ietf@optimus.ietf.org; Thu, 20 May 2004 00:47:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA12937
	for <ietf@ietf.org>; Thu, 20 May 2004 00:47: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 1BQfSf-0000DB-FO
	for ietf@ietf.org; Thu, 20 May 2004 00:47:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQfRf-000021-00
	for ietf@ietf.org; Thu, 20 May 2004 00:46:15 -0400
Received: from 149.cust48.nsw.dsl.ozemail.com.au ([203.103.127.149] helo=nosense.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQfQd-0007Yp-00
	for ietf@ietf.org; Thu, 20 May 2004 00:45:12 -0400
Received: from Dupy2.nosense.org (localhost.localdomain [127.0.0.1])
	by nosense.org (Postfix) with SMTP
	id F2CDA3F02A; Thu, 20 May 2004 14:14:39 +0930 (CST)
Date: Thu, 20 May 2004 14:14:39 +0930
From: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
To: Dean Anderson <dean@av8.com>
Cc: harald@alvestrand.no, ietf@ietf.org
Subject: Re: Response to complaint from Dean Anderson
Message-Id: <20040520141439.2e64ca9d.ietf@130c04165a5b40404e4440445758487a.nosense.org>
In-Reply-To: <Pine.LNX.4.44.0405192233180.20973-100000@cirrus.av8.net>
References: <128882262.1084916137@localhost>
	<Pine.LNX.4.44.0405192233180.20973-100000@cirrus.av8.net>
Organization: The No Sense Organisation (http://www.nosense.org)
X-Mailer: Sylpheed version 0.9.10 (GTK+ 1.2.10; i686-pc-linux-gnu)
X-Location: Adelaide, Australia
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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 Wed, 19 May 2004 23:42:01 -0400 (EDT)
Dean Anderson <dean@av8.com> wrote:

> On Tue, 18 May 2004, Harald Tveit Alvestrand wrote:
> 

<snip - whole lot of legal stuff that I don't have time to
read - I've got a few thousand RFCs to go ...>

Firstly, let me say that it is really sad that legalease, legal
council and legal positions have appeared on an IETF mailing
list to the extent we've seen. I've understood that the IETF was
all about best technical solutions and positions, not best legal
solutions and positions.

Dean, I'm in no position to implement this as a solution (nor
have I spent time thinking about how hard or easy it
would be to implement), however, presuming that @ietf.org doesn't
implement MTA blocking via methods such as SORBS, and I don't
think they do, would you be happy if all people who have official
IETF positions (eg. area advisor, working group chair, etc) had
@ietf.org email addresses, and used those for any IETF related
correspondence ?

Regards,
Mark.

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


From ietf-admin@ietf.org  Thu May 20 11:38: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 LAA24901
	for <ietf-archive@ietf.org>; Thu, 20 May 2004 11:38: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 1BQpdA-0005TS-2I
	for ietf-archive@ietf.org; Thu, 20 May 2004 11:38:48 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQpcF-0005Mz-00
	for ietf-archive@ietf.org; Thu, 20 May 2004 11:37:51 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQpbG-0005En-00
	for ietf-archive@ietf.org; Thu, 20 May 2004 11:36:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQp6S-0004Rx-Kw; Thu, 20 May 2004 11:05:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQZOz-0006qD-QJ
	for ietf@optimus.ietf.org; Wed, 19 May 2004 18:19:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24764
	for <ietf@ietf.org>; Wed, 19 May 2004 18:19: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 1BQZOw-0002NP-ND
	for ietf@ietf.org; Wed, 19 May 2004 18:19:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQZO1-0002Hp-00
	for ietf@ietf.org; Wed, 19 May 2004 18:18:05 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQZN4-000273-00
	for ietf@ietf.org; Wed, 19 May 2004 18:17:06 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id 3336C13CDE; Wed, 19 May 2004 22:16:36 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: Root Anycast
References: <6.1.0.6.2.20040519210528.05d42a60@mail.utel.net>
From: Paul Vixie <vixie@vix.com>
Date: 19 May 2004 22:16:36 +0000
In-Reply-To: <6.1.0.6.2.20040519210528.05d42a60@mail.utel.net>
Message-ID: <g3smdwxdtn.fsf@sa.vix.com>
Lines: 11
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
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

there are two things that i think it's important that everybody understand.

first, anyone who posts from roll accounts like "info@utel.net (jfcm)"
tends to be dismissed as a troll.

second, anyone who seriously uses the term "legacy DNS root" tends to be
dismissed as a loon.

i now return control of your television set to the loons and trolls...
-- 
Paul Vixie

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


From ietf-admin@ietf.org  Thu May 20 11:44: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 LAA25558
	for <ietf-archive@ietf.org>; Thu, 20 May 2004 11:44: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 1BQpjA-0006Mj-K6
	for ietf-archive@ietf.org; Thu, 20 May 2004 11:45:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQphX-00068X-00
	for ietf-archive@ietf.org; Thu, 20 May 2004 11:43:20 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQpfj-0005rB-00
	for ietf-archive@ietf.org; Thu, 20 May 2004 11:41:27 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQp7a-0004cB-ON; Thu, 20 May 2004 11:06:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQoOo-0003tc-Hu
	for ietf@optimus.ietf.org; Thu, 20 May 2004 10:19: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 KAA19277
	for <ietf@ietf.org>; Thu, 20 May 2004 10:19: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 1BQoOj-0004Ci-Ut
	for ietf@ietf.org; Thu, 20 May 2004 10:19:50 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQoNn-0003zV-00
	for ietf@ietf.org; Thu, 20 May 2004 10:18:52 -0400
Received: from [68.120.110.66] (helo=laptop2.kurtis.pp.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQoN4-0003Z8-00
	for ietf@ietf.org; Thu, 20 May 2004 10:18:06 -0400
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by laptop2.kurtis.pp.se (Postfix) with ESMTP
	id C34FB414EC4; Thu, 20 May 2004 16:17:47 +0200 (CEST)
In-Reply-To: <6.1.0.6.2.20040519210528.05d42a60@mail.utel.net>
References: <DFC3BD05-A84A-11D8-AC18-000A95CD987A@muada.com> <g3lljqegi6.fsf@sa.vix.com> <6.1.0.6.2.20040518171004.04666060@mail.utel.net> <114760000.1084908866@slimsixten.pilsnet.sunet.se> <6.1.0.6.2.20040519003547.059c3620@mail.utel.net> <6522B9F0-A9AF-11D8-8726-000A95928574@kurtis.pp.se> <6.1.0.6.2.20040519210528.05d42a60@mail.utel.net>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=fixed
Message-Id: <74FA20C4-AA68-11D8-8726-000A95928574@kurtis.pp.se>
Content-Transfer-Encoding: 7bit
Cc: =?ISO-8859-1?Q?M=E5ns_Nilsson?= <mansaxel@besserwisser.org>, ietf@ietf.org
From: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
Subject: Re: Root Anycast
Date: Thu, 20 May 2004 16:17:42 +0200
To: jfcm <info@utel.net>
X-Pgp-Rfc2646-Fix: 1
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

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


We must be talking about two different Internets.

- - kurtis -

On 2004-05-19, at 21.46, jfcm wrote:

> At 18:12 19/05/04, Kurt Erik Lindqvist wrote:
>> > - I talk of real world when you talk of the current (unsecure and
>> > overloaded?) implementation of the current DNS architecture.
>>
>> In what way overloaded? Do you have any pointers? Proof? Data?
>
> Dear Kurt Eric,
> Let not play this, please. Either you think after careful personal 
> study (or you believe) that the current system is the best solution 
> the world needs, and that it only calls for some users to be more 
> educated in using it - and we are on planets apart. This is fine with 
> me, and the end of a non existing debate.
>
> Or you think the DNS does not match the IETF "core values" in being 
> centralized (I do not make that "core value" as described by Harald a 
> creed, I think they are often outdated, but I fully agree they are a 
> technical minimum). And, together with ICANN, you think IETF is the 
> right place to respond ICANN's call for more (ICP-3). So you try to 
> understand the problem and to imagine solutions. This is what we did. 
> And I explain the solutions we are subsequently working on.
>
>> > The problem we face is an old and too large unique system with a
>> > robust yet overloaded engine. With all the problems which come with
>> > it. We have to split the zones of usage and risks. Either it is
>> > planned by IETF or it is done by the users. I suggest it is done
>> > together.
>>
>> Again, overloaded engine in what way?
>
> I just report on our follow up on this premise. If you do not see it, 
> I cannot help with details. Just with the alternative. Yu are the 
> judge.
>
> The DNS "engine" is made of all the root/name servers and resolvers.
> - either you are satisfied with their present tools, organization, 
> limitations and resulting service, then again I cannot discuss it.
> - or you are not, and then the question is to know if your 
> disatisfaction results from the used solution or from the way this 
> solution is implemented.
>
> IMO the problem is not with the solution (software) but with its 
> architectural deployment and usage. This permits a smooth transition, 
> using existing and proven building blocks and expertise. But I think 
> that speed if the essence. One may also disagree.
>
>> > Then the agreed file
>> Agreed by whom?  In what way?
>
> Let me elaborate quickly. The target is not to obtain a file which 
> pleases anyone as today, but a file which reports on the TLD Managers 
> entries. So, the point is not who does it but the number of identical 
> independent results. What follows is for one single national service.
>
> - National because of the legal and political aspects in many aspects 
> (risk containment, sensitive information intelligence leaks, justice 
> obligations, etc.).
> - But subsidiarity applies to the regional, local, corporate, private 
> granularities (I explained what this means in my first mail).
> - this means that security and verification will probably repeated 20 
> to 50 times accross the world. Once a day in each country could mean 
> every hour for global issues such as the DNS (the protocol is the same 
> for every root information [time, radio frequencies, weather, hospital 
> situation, etc])
>
> The process we retained is to have at least four different independent 
> data collection processes (whatever the processes, starting with a 
> simple duplication of the NTIA file in the case of the DNS legacy 
> root). The reason for at least 4 is to have at a majority if needed, 
> even if one is down.
>
> There must be five conditions for the result to be accepted (there 
> could be more?)
> 1. there must be no reported alarm (nominal situation) on our 
> monitoring system
> 2. all the results must be identical
> 3. there must not be an abnormally large difference with preceding 
> copy (variance max to be tuned from experience) - to allow reasonable 
> updates if permitted.
> 4. visual review by the four collection managers is positive
> 5. there must be no significant (similar to 3) with other partenering 
> root files on common part of the root matrix.
>
> If these 5 conditions are not met there will be an investigation and 
> concerted agreement to be reached among collection managers, or a "no 
> go" and escalation to Execom and to BoD (or Gov). These conditions (or 
> more) can be made legal and imposed before a State endorses a Root 
> Service for its own use and for legal transactions.
>
> There is a possible alternative: the decision of the Government in 
> case of national vital crisis. The role of the collection managers 
> will be to advise how to reduce pollution in such cases - this may 
> call for international concertation [exemple: the "ambassador lounge" 
> at ITU (telephone is real time, no 48 hours delay). A doctrine is to 
> be set-up as part of Digital Warfare (US say Cybernetic Warfare). 
> Experience in Mines, Electronic or Nuclear Warfares shows this is 
> possible.
>
>> > You want to reduce the calls to your system, right? Let stop the
>> > "cache" idea which is something of _your_ system ibn theirs, and
>> > propose them an update of _their_ system - like anti-virus updates
>> > (ever heard that anti-virus run huge 50x1G systems? And let discover
>> > what a user system can bring more to its user owner. So when the 
>> user
>> > has started using and enjoying _his_ system, you will obtain what 
>> you
>> > want.
>>
>> Why would I want to reduce the number of calls on my system? My 
>> system  is doing just fine...
>
> What is your system ?
>
> In the case discussed the problem is the current increasing load on 
> current servers. That load and that type of calls are inappropriate. 
> The architecture is to be changed (all the more than it permits DoS). 
> Keeping daily updated files of much larger size than the root file is 
> carried by many people around the world more efficiently, more 
> securely and with less of constraints to innovative usages.
>
> But again, the very nature of the DNS permits such transition to be 
> transparent. So if you love the current architecture, it is OK with 
> me. As long as you do not pollute what we do and we do not pollute 
> what you do there is no problem. This discussion only concerns those 
> (with ICANN ICP-3) who want to experiment and work on the resulting 
> experience, towards a better response to the people and Gov demands.
>
> I just describe what we have started working on, with scarce 
> resources, along those lines for more than two years. And what we 
> target from then on.
> jfc
>
>

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3

iQA/AwUBQKy+CaarNKXTPFCVEQItNACfcM5bSRoC0Xvatk0UnhbCukQuryMAoJr1
7/tT51H4rs0t9JKdmq62a0Ga
=aiJ1
-----END PGP SIGNATURE-----


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


From exim@www1.ietf.org  Thu May 20 11:49:59 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 LAA26312
	for <ietf-archive@odin.ietf.org>; Thu, 20 May 2004 11:49:58 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQpbG-00052B-Ra
	for ietf-archive@odin.ietf.org; Thu, 20 May 2004 11:36:51 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4KFaofF019323
	for ietf-archive@odin.ietf.org; Thu, 20 May 2004 11:36:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQp6S-0004Rx-Kw; Thu, 20 May 2004 11:05:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQZOz-0006qD-QJ
	for ietf@optimus.ietf.org; Wed, 19 May 2004 18:19:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24764
	for <ietf@ietf.org>; Wed, 19 May 2004 18:19: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 1BQZOw-0002NP-ND
	for ietf@ietf.org; Wed, 19 May 2004 18:19:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQZO1-0002Hp-00
	for ietf@ietf.org; Wed, 19 May 2004 18:18:05 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQZN4-000273-00
	for ietf@ietf.org; Wed, 19 May 2004 18:17:06 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id 3336C13CDE; Wed, 19 May 2004 22:16:36 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: Root Anycast
References: <6.1.0.6.2.20040519210528.05d42a60@mail.utel.net>
From: Paul Vixie <vixie@vix.com>
Date: 19 May 2004 22:16:36 +0000
In-Reply-To: <6.1.0.6.2.20040519210528.05d42a60@mail.utel.net>
Message-ID: <g3smdwxdtn.fsf@sa.vix.com>
Lines: 11
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: 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>

there are two things that i think it's important that everybody understand.

first, anyone who posts from roll accounts like "info@utel.net (jfcm)"
tends to be dismissed as a troll.

second, anyone who seriously uses the term "legacy DNS root" tends to be
dismissed as a loon.

i now return control of your television set to the loons and trolls...
-- 
Paul Vixie

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



From ietf-admin@ietf.org  Thu May 20 14:25: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 OAA09291
	for <ietf-archive@ietf.org>; Thu, 20 May 2004 14:25: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 1BQsEF-0007aS-UX
	for ietf-archive@ietf.org; Thu, 20 May 2004 14:25:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQsDI-0007Sn-00
	for ietf-archive@ietf.org; Thu, 20 May 2004 14:24:16 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQsCe-0007Ls-00
	for ietf-archive@ietf.org; Thu, 20 May 2004 14:23:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQs0V-0004a0-7f; Thu, 20 May 2004 14:11:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQrtd-0002Vm-SM
	for ietf@optimus.ietf.org; Thu, 20 May 2004 14:03: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 OAA07739
	for <ietf@ietf.org>; Thu, 20 May 2004 14:03:54 -0400 (EDT)
From: bill@strahm.net
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQrtb-0005Zg-9I
	for ietf@ietf.org; Thu, 20 May 2004 14:03:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQrse-0005VM-00
	for ietf@ietf.org; Thu, 20 May 2004 14:02:57 -0400
Received: from smtpout03-03.mesa1.secureserver.net ([64.202.165.73])
	by ietf-mx with smtp (Exim 4.12)
	id 1BQrri-0005MK-00
	for ietf@ietf.org; Thu, 20 May 2004 14:01:58 -0400
Received: (qmail 22416 invoked from network); 20 May 2004 18:01:47 -0000
Received: from unknown (HELO webmail-2-6.mesa1.secureserver.net) (64.202.166.93)
  by smtpout03-03.mesa1.secureserver.net with SMTP; 20 May 2004 18:01:47 -0000
Received: (qmail 9599 invoked by uid 99); 20 May 2004 18:01:25 -0000
Message-ID: <20040520180125.9598.qmail@webmail-2-6.mesa1.secureserver.net>
Date: Thu, 20 May 2004 11:01:25 -0700
Subject: RE: Root Anycast
To: Paul Vixie <vixie@vix.com>
cc: ietf@ietf.org
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.4 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60

Ok Paul,

This is twice in two days now.

Yesterdays was much worse, and apparently my response didn't make it to the IEFT reflector (maybe I just sent
it to you privately I hope)

The name calling doesn't help anything - if people are trolls, don't say anything - everyone here can come up
with their own list of trolls.  As for loons - well my summer job in college was as a canoe guide in Minnesota,
I kinda like loons - so please quit your attack on the good name of loons, I don't appreciate it.

This list has gotten way to hot and way to personal over the last few weeks - it is time to step in and get
back to real engineering work, no one is running for president on this list (you there Kerry/Bush/Nader ?) so
we don't need the mudslinging.  I miss IPv8 (my favorite loonie troll)

Bill Strahm
> -------- Original Message --------
> Subject: Re: Root Anycast
> From: "Paul Vixie" <vixie@vix.com>
> Date: Wed, May 19, 2004 3:16 pm
> To: ietf@ietf.org
>
> there are two things that i think it's important that everybody
> understand.
>
> first, anyone who posts from roll accounts like "info@utel.net (jfcm)"
> tends to be dismissed as a troll.
>
> second, anyone who seriously uses the term "legacy DNS root" tends to
> be
> dismissed as a loon.
>
> i now return control of your television set to the loons and trolls...
> --
> Paul Vixie
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf

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


From exim@www1.ietf.org  Thu May 20 14:25: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 OAA09320
	for <ietf-archive@odin.ietf.org>; Thu, 20 May 2004 14:25: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 1BQsCg-0007jB-KU
	for ietf-archive@odin.ietf.org; Thu, 20 May 2004 14:23:40 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4KINcb9029675
	for ietf-archive@odin.ietf.org; Thu, 20 May 2004 14:23:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQs0V-0004a0-7f; Thu, 20 May 2004 14:11:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQrtd-0002Vm-SM
	for ietf@optimus.ietf.org; Thu, 20 May 2004 14:03: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 OAA07739
	for <ietf@ietf.org>; Thu, 20 May 2004 14:03:54 -0400 (EDT)
From: bill@strahm.net
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQrtb-0005Zg-9I
	for ietf@ietf.org; Thu, 20 May 2004 14:03:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQrse-0005VM-00
	for ietf@ietf.org; Thu, 20 May 2004 14:02:57 -0400
Received: from smtpout03-03.mesa1.secureserver.net ([64.202.165.73])
	by ietf-mx with smtp (Exim 4.12)
	id 1BQrri-0005MK-00
	for ietf@ietf.org; Thu, 20 May 2004 14:01:58 -0400
Received: (qmail 22416 invoked from network); 20 May 2004 18:01:47 -0000
Received: from unknown (HELO webmail-2-6.mesa1.secureserver.net) (64.202.166.93)
  by smtpout03-03.mesa1.secureserver.net with SMTP; 20 May 2004 18:01:47 -0000
Received: (qmail 9599 invoked by uid 99); 20 May 2004 18:01:25 -0000
Message-ID: <20040520180125.9598.qmail@webmail-2-6.mesa1.secureserver.net>
Date: Thu, 20 May 2004 11:01:25 -0700
Subject: RE: Root Anycast
To: Paul Vixie <vixie@vix.com>
cc: 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.5 required=5.0 tests=AWL,NO_REAL_NAME 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>

Ok Paul,

This is twice in two days now.

Yesterdays was much worse, and apparently my response didn't make it to the IEFT reflector (maybe I just sent
it to you privately I hope)

The name calling doesn't help anything - if people are trolls, don't say anything - everyone here can come up
with their own list of trolls.  As for loons - well my summer job in college was as a canoe guide in Minnesota,
I kinda like loons - so please quit your attack on the good name of loons, I don't appreciate it.

This list has gotten way to hot and way to personal over the last few weeks - it is time to step in and get
back to real engineering work, no one is running for president on this list (you there Kerry/Bush/Nader ?) so
we don't need the mudslinging.  I miss IPv8 (my favorite loonie troll)

Bill Strahm
> -------- Original Message --------
> Subject: Re: Root Anycast
> From: "Paul Vixie" <vixie@vix.com>
> Date: Wed, May 19, 2004 3:16 pm
> To: ietf@ietf.org
>
> there are two things that i think it's important that everybody
> understand.
>
> first, anyone who posts from roll accounts like "info@utel.net (jfcm)"
> tends to be dismissed as a troll.
>
> second, anyone who seriously uses the term "legacy DNS root" tends to
> be
> dismissed as a loon.
>
> i now return control of your television set to the loons and trolls...
> --
> Paul Vixie
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf

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



From ietf-admin@ietf.org  Thu May 20 19:29: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 TAA05491
	for <ietf-archive@ietf.org>; Thu, 20 May 2004 19:29: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 1BQwyR-0002D1-GM
	for ietf-archive@ietf.org; Thu, 20 May 2004 19:29:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQwxb-00028Y-00
	for ietf-archive@ietf.org; Thu, 20 May 2004 19:28:24 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQwwh-00023E-00
	for ietf-archive@ietf.org; Thu, 20 May 2004 19:27:27 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQwle-00036J-1v; Thu, 20 May 2004 19:16:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQwjg-0002SG-Sh
	for ietf@optimus.ietf.org; Thu, 20 May 2004 19:14: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 TAA04590
	for <ietf@ietf.org>; Thu, 20 May 2004 19:13: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 1BQwjf-0000zj-3m
	for ietf@ietf.org; Thu, 20 May 2004 19:13:59 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQwij-0000wF-00
	for ietf@ietf.org; Thu, 20 May 2004 19:13:02 -0400
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQwiJ-0000tt-00
	for ietf@ietf.org; Thu, 20 May 2004 19:12:35 -0400
Received: from f01v-44-174.d0.club-internet.fr ([212.195.255.174] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.24)
	id 1BQwi7-0005sz-Bu; Thu, 20 May 2004 16:12:24 -0700
Message-Id: <6.1.0.6.2.20040520215405.03c4a320@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 6.1.0.6
Date: Thu, 20 May 2004 23:12:14 +0200
To: Paul Vixie <vixie@vix.com>, ietf@ietf.org
From: jfcm <info@utel.net>
Subject: Re: Root Anycast
In-Reply-To: <g3smdwxdtn.fsf@sa.vix.com>
References: <6.1.0.6.2.20040519210528.05d42a60@mail.utel.net>
 <g3smdwxdtn.fsf@sa.vix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [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 00:16 20/05/04, Paul Vixie wrote:
>there are two things that i think it's important that everybody understand.
>first, anyone who posts from roll accounts like "info@utel.net (jfcm)"
>tends to be dismissed as a troll.
>second, anyone who seriously uses the term "legacy DNS root" tends to be
>dismissed as a loon.
>i now return control of your television set to the loons and trolls...

A part from documenting a root server manager mentality, I fail to see the 
use of such a mail.

1. I ran a seach of my IETF folder for "legacy DNS root". It only listed 
your mail....

I said "the NTIA file in the case of the DNS legacy root". In the context 
of responses to ICANN's ICP-3 call for DNS deployment R&D and 
experimentation (we work on this for two years now, while IETF did not even 
considered) it means: "in the case of the current root file system we use 
the current reference file". This is what you do twice a day, don't you?. 
Should your comment result from a Frenglish fault of mine, that you would 
be teasing, it would call for an immediate apology. Otherwise in my world 
one may disagree with others - in seriously documenting why - but one does 
not despise their work. Those who do that have a name.

2. Being arrogant does not make you wrong. info@utel.net was only a patch 
due to some past ietf mailing list problem. It lasted. I will resume using 
my regular mail name. Thx.
jfc

First they ignore you, then they laugh at you, then they fight you, then 
you win. Gandhi.

    


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


From exim@www1.ietf.org  Thu May 20 19:32: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 TAA05736
	for <ietf-archive@odin.ietf.org>; Thu, 20 May 2004 19:32: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 1BQwwi-0005dX-VS
	for ietf-archive@odin.ietf.org; Thu, 20 May 2004 19:27:29 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4KNRSqH021603
	for ietf-archive@odin.ietf.org; Thu, 20 May 2004 19:27:28 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQwle-00036J-1v; Thu, 20 May 2004 19:16:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQwjg-0002SG-Sh
	for ietf@optimus.ietf.org; Thu, 20 May 2004 19:14: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 TAA04590
	for <ietf@ietf.org>; Thu, 20 May 2004 19:13: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 1BQwjf-0000zj-3m
	for ietf@ietf.org; Thu, 20 May 2004 19:13:59 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQwij-0000wF-00
	for ietf@ietf.org; Thu, 20 May 2004 19:13:02 -0400
Received: from montage.altserver.com ([63.247.74.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQwiJ-0000tt-00
	for ietf@ietf.org; Thu, 20 May 2004 19:12:35 -0400
Received: from f01v-44-174.d0.club-internet.fr ([212.195.255.174] helo=jfc2.utel.net)
	by montage.altserver.com with esmtp (Exim 4.24)
	id 1BQwi7-0005sz-Bu; Thu, 20 May 2004 16:12:24 -0700
Message-Id: <6.1.0.6.2.20040520215405.03c4a320@mail.utel.net>
X-Sender: info+utel.net@mail.utel.net
X-Mailer: QUALCOMM Windows Eudora Version 6.1.0.6
Date: Thu, 20 May 2004 23:12:14 +0200
To: Paul Vixie <vixie@vix.com>, ietf@ietf.org
From: jfcm <info@utel.net>
Subject: Re: Root Anycast
In-Reply-To: <g3smdwxdtn.fsf@sa.vix.com>
References: <6.1.0.6.2.20040519210528.05d42a60@mail.utel.net>
 <g3smdwxdtn.fsf@sa.vix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - utel.net
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.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 00:16 20/05/04, Paul Vixie wrote:
>there are two things that i think it's important that everybody understand.
>first, anyone who posts from roll accounts like "info@utel.net (jfcm)"
>tends to be dismissed as a troll.
>second, anyone who seriously uses the term "legacy DNS root" tends to be
>dismissed as a loon.
>i now return control of your television set to the loons and trolls...

A part from documenting a root server manager mentality, I fail to see the 
use of such a mail.

1. I ran a seach of my IETF folder for "legacy DNS root". It only listed 
your mail....

I said "the NTIA file in the case of the DNS legacy root". In the context 
of responses to ICANN's ICP-3 call for DNS deployment R&D and 
experimentation (we work on this for two years now, while IETF did not even 
considered) it means: "in the case of the current root file system we use 
the current reference file". This is what you do twice a day, don't you?. 
Should your comment result from a Frenglish fault of mine, that you would 
be teasing, it would call for an immediate apology. Otherwise in my world 
one may disagree with others - in seriously documenting why - but one does 
not despise their work. Those who do that have a name.

2. Being arrogant does not make you wrong. info@utel.net was only a patch 
due to some past ietf mailing list problem. It lasted. I will resume using 
my regular mail name. Thx.
jfc

First they ignore you, then they laugh at you, then they fight you, then 
you win. Gandhi.

    


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



From ietf-admin@ietf.org  Thu May 20 22:37: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 WAA13821
	for <ietf-archive@ietf.org>; Thu, 20 May 2004 22:37:05 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQzuD-0001dU-QL
	for ietf-archive@ietf.org; Thu, 20 May 2004 22:37:05 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQztL-0001YJ-00
	for ietf-archive@ietf.org; Thu, 20 May 2004 22:36:12 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQzsX-0001TA-00
	for ietf-archive@ietf.org; Thu, 20 May 2004 22:35:21 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQzmR-00052s-1C; Thu, 20 May 2004 22:29:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQzki-0004bf-7l
	for ietf@optimus.ietf.org; Thu, 20 May 2004 22:27: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 WAA13544
	for <ietf@ietf.org>; Thu, 20 May 2004 22:27:12 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQzke-0000ic-SL
	for ietf@ietf.org; Thu, 20 May 2004 22:27:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQzjf-0000cd-00
	for ietf@ietf.org; Thu, 20 May 2004 22:26:12 -0400
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQzjG-0000VI-00; Thu, 20 May 2004 22:25:46 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i4L2O9I09340;
	Thu, 20 May 2004 19:24:09 -0700
X-mProtect: <200405210224> 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 smtpdmD8Keb; Thu, 20 May 2004 17:35:18 PDT
Message-ID: <40AD4ED6.3010206@iprg.nokia.com>
Date: Thu, 20 May 2004 17:35:34 -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: Harald Tveit Alvestrand <harald@alvestrand.no>
CC: Pekka Savola <pekkas@netcore.fi>, iesg@ietf.org, ietf@ietf.org,
        ftemplin@iprg.nokia.com
Subject: Re: Last Call: 'The IESG and RFC Editor documents: Procedures' to
 BCP
References: <Pine.LNX.4.44.0405191511470.14373-100000@netcore.fi> <161942430.1084949198@localhost>
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.1 required=5.0 tests=AWL,UPPERCASE_25_50 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Hello Harald,

I had a question on this that may be somewhat related to Pekka's.
On the final page of the document, we find:

>Disclaimer of Validity
>
>   This document and the information contained herein are provided on an
>   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
>   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
>   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
>   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
>   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
>   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
>  
>

I have never seen such a statement appearing in an I-D before.
Is this a standard statement for such procedural documents?
And,  is the intention that it be removed (by the RFC editor,
I guess) before publishing as BCP?

Thanks - Fred
ftemplin@iprg.nokia.com

On Fri, 7 May 2004, The IESG wrote:

>The IESG has received a request from the Internet Engineering Steering Group
>to consider the following document:
>
>- 'The IESG and RFC Editor documents: Procedures '
>   <draft-iesg-rfced-documents-01.txt> as a BCP
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action.  Please send any comments to the
>iesg@ietf.org or ietf@ietf.org mailing lists by 2004-06-04.
>
>The file can be obtained via
>http://www.ietf.org/internet-drafts/draft-iesg-rfced-documents-01.txt
>  
>


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


From exim@www1.ietf.org  Thu May 20 22:37:35 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 WAA13896
	for <ietf-archive@odin.ietf.org>; Thu, 20 May 2004 22:37:35 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQzsZ-00061n-Gq
	for ietf-archive@odin.ietf.org; Thu, 20 May 2004 22:35:24 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4L2ZNHH023172
	for ietf-archive@odin.ietf.org; Thu, 20 May 2004 22:35:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQzmR-00052s-1C; Thu, 20 May 2004 22:29:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQzki-0004bf-7l
	for ietf@optimus.ietf.org; Thu, 20 May 2004 22:27: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 WAA13544
	for <ietf@ietf.org>; Thu, 20 May 2004 22:27:12 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BQzke-0000ic-SL
	for ietf@ietf.org; Thu, 20 May 2004 22:27:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQzjf-0000cd-00
	for ietf@ietf.org; Thu, 20 May 2004 22:26:12 -0400
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQzjG-0000VI-00; Thu, 20 May 2004 22:25:46 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i4L2O9I09340;
	Thu, 20 May 2004 19:24:09 -0700
X-mProtect: <200405210224> 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 smtpdmD8Keb; Thu, 20 May 2004 17:35:18 PDT
Message-ID: <40AD4ED6.3010206@iprg.nokia.com>
Date: Thu, 20 May 2004 17:35:34 -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: Harald Tveit Alvestrand <harald@alvestrand.no>
CC: Pekka Savola <pekkas@netcore.fi>, iesg@ietf.org, ietf@ietf.org,
        ftemplin@iprg.nokia.com
Subject: Re: Last Call: 'The IESG and RFC Editor documents: Procedures' to
 BCP
References: <Pine.LNX.4.44.0405191511470.14373-100000@netcore.fi> <161942430.1084949198@localhost>
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.1 required=5.0 tests=AWL,UPPERCASE_25_50 
	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

Hello Harald,

I had a question on this that may be somewhat related to Pekka's.
On the final page of the document, we find:

>Disclaimer of Validity
>
>   This document and the information contained herein are provided on an
>   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
>   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
>   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
>   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
>   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
>   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
>  
>

I have never seen such a statement appearing in an I-D before.
Is this a standard statement for such procedural documents?
And,  is the intention that it be removed (by the RFC editor,
I guess) before publishing as BCP?

Thanks - Fred
ftemplin@iprg.nokia.com

On Fri, 7 May 2004, The IESG wrote:

>The IESG has received a request from the Internet Engineering Steering Group
>to consider the following document:
>
>- 'The IESG and RFC Editor documents: Procedures '
>   <draft-iesg-rfced-documents-01.txt> as a BCP
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action.  Please send any comments to the
>iesg@ietf.org or ietf@ietf.org mailing lists by 2004-06-04.
>
>The file can be obtained via
>http://www.ietf.org/internet-drafts/draft-iesg-rfced-documents-01.txt
>  
>


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



From ietf-admin@ietf.org  Thu May 20 23:39: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 XAA17009
	for <ietf-archive@ietf.org>; Thu, 20 May 2004 23:39: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 1BR0sM-0000Nk-0f
	for ietf-archive@ietf.org; Thu, 20 May 2004 23:39:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BR0rO-0000E4-00
	for ietf-archive@ietf.org; Thu, 20 May 2004 23:38:15 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BR0qT-000041-00
	for ietf-archive@ietf.org; Thu, 20 May 2004 23:37:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BR0lO-0000l5-Vq; Thu, 20 May 2004 23:32:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BR0ho-0008Lm-FY
	for ietf@optimus.ietf.org; Thu, 20 May 2004 23:28:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA16070
	for <ietf@ietf.org>; Thu, 20 May 2004 23:28: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 1BR0hm-0006dp-0B
	for ietf@ietf.org; Thu, 20 May 2004 23:28:18 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BR0gn-0006UK-00
	for ietf@ietf.org; Thu, 20 May 2004 23:27:17 -0400
Received: from flamingo.mail.pas.earthlink.net ([207.217.120.232])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BR0fo-0006ML-00
	for ietf@ietf.org; Thu, 20 May 2004 23:26:16 -0400
Received: from h-68-164-95-135.snvacaid.dynamic.covad.net ([68.164.95.135] helo=oemcomputer)
	by flamingo.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 1BR0fn-0001Vw-00
	for ietf@ietf.org; Thu, 20 May 2004 20:26:15 -0700
Message-ID: <000c01c43ee3$5eeff920$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <ietf@ietf.org>
References: <Pine.LNX.4.44.0405191511470.14373-100000@netcore.fi> <161942430.1084949198@localhost> <40AD4ED6.3010206@iprg.nokia.com>
Subject: Re: Last Call: 'The IESG and RFC Editor documents: Procedures' to BCP
Date: Thu, 20 May 2004 20:26:13 -0700
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
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 -

> From: "Fred Templin" <ftemplin@iprg.nokia.com>
> To: "Harald Tveit Alvestrand" <harald@alvestrand.no>
> Cc: "Pekka Savola" <pekkas@netcore.fi>; <iesg@ietf.org>; <ietf@ietf.org>; <ftemplin@iprg.nokia.com>
> Sent: Thursday, May 20, 2004 5:35 PM
> Subject: Re: Last Call: 'The IESG and RFC Editor documents: Procedures' to BCP
...
> I have never seen such a statement appearing in an I-D before.
> Is this a standard statement for such procedural documents?
> And,  is the intention that it be removed (by the RFC editor,
> I guess) before publishing as BCP?
...

RFC 3667 clause 5.5 says it's required in all IETF documents.
None of the exceptions listed in clause 5.6 would appear to apply.

Randy



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


From exim@www1.ietf.org  Thu May 20 23:40: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 XAA17202
	for <ietf-archive@odin.ietf.org>; Thu, 20 May 2004 23:40: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 1BR0qV-0001uT-7t
	for ietf-archive@odin.ietf.org; Thu, 20 May 2004 23:37:19 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4L3bJVt007292
	for ietf-archive@odin.ietf.org; Thu, 20 May 2004 23:37:19 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BR0lO-0000l5-Vq; Thu, 20 May 2004 23:32:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BR0ho-0008Lm-FY
	for ietf@optimus.ietf.org; Thu, 20 May 2004 23:28:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA16070
	for <ietf@ietf.org>; Thu, 20 May 2004 23:28: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 1BR0hm-0006dp-0B
	for ietf@ietf.org; Thu, 20 May 2004 23:28:18 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BR0gn-0006UK-00
	for ietf@ietf.org; Thu, 20 May 2004 23:27:17 -0400
Received: from flamingo.mail.pas.earthlink.net ([207.217.120.232])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BR0fo-0006ML-00
	for ietf@ietf.org; Thu, 20 May 2004 23:26:16 -0400
Received: from h-68-164-95-135.snvacaid.dynamic.covad.net ([68.164.95.135] helo=oemcomputer)
	by flamingo.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 1BR0fn-0001Vw-00
	for ietf@ietf.org; Thu, 20 May 2004 20:26:15 -0700
Message-ID: <000c01c43ee3$5eeff920$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <ietf@ietf.org>
References: <Pine.LNX.4.44.0405191511470.14373-100000@netcore.fi> <161942430.1084949198@localhost> <40AD4ED6.3010206@iprg.nokia.com>
Subject: Re: Last Call: 'The IESG and RFC Editor documents: Procedures' to BCP
Date: Thu, 20 May 2004 20:26:13 -0700
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
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 -

> From: "Fred Templin" <ftemplin@iprg.nokia.com>
> To: "Harald Tveit Alvestrand" <harald@alvestrand.no>
> Cc: "Pekka Savola" <pekkas@netcore.fi>; <iesg@ietf.org>; <ietf@ietf.org>; <ftemplin@iprg.nokia.com>
> Sent: Thursday, May 20, 2004 5:35 PM
> Subject: Re: Last Call: 'The IESG and RFC Editor documents: Procedures' to BCP
...
> I have never seen such a statement appearing in an I-D before.
> Is this a standard statement for such procedural documents?
> And,  is the intention that it be removed (by the RFC editor,
> I guess) before publishing as BCP?
...

RFC 3667 clause 5.5 says it's required in all IETF documents.
None of the exceptions listed in clause 5.6 would appear to apply.

Randy



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



From exim@www1.ietf.org  Fri May 21 00:46:58 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 AAA20238
	for <ietf-archive@odin.ietf.org>; Fri, 21 May 2004 00:46:58 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BR1qh-0008C2-Br
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 00:41:35 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4L4fZAv031344
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 00:41:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BR1kR-0006Se-4S; Fri, 21 May 2004 00:35:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BR1eG-00056t-QQ
	for ietf@optimus.ietf.org; Fri, 21 May 2004 00:28:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA19664
	for <ietf@ietf.org>; Fri, 21 May 2004 00: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 1BR1eE-0005tA-4F
	for ietf@ietf.org; Fri, 21 May 2004 00:28:42 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BR1dF-0005hW-00
	for ietf@ietf.org; Fri, 21 May 2004 00:27:41 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BR1cC-0005T7-00; Fri, 21 May 2004 00:26:36 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 4C3D161B8B; Fri, 21 May 2004 06:26:07 +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 24879-03; Fri, 21 May 2004 06:26:06 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 7029C622BE; Fri, 21 May 2004 06:26:04 +0200 (CEST)
Date: Thu, 20 May 2004 21:15:11 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Fred Templin <ftemplin@iprg.nokia.com>
Cc: Pekka Savola <pekkas@netcore.fi>, iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: 'The IESG and RFC Editor documents: Procedures' to
 BCP
Message-ID: <300454600.1085087711@localhost>
In-Reply-To: <40AD4ED6.3010206@iprg.nokia.com>
References: <Pine.LNX.4.44.0405191511470.14373-100000@netcore.fi>
 <161942430.1084949198@localhost> <40AD4ED6.3010206@iprg.nokia.com>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-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.2 required=5.0 tests=AWL,UPPERCASE_25_50 
	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. mai 2004 17:35 -0700 Fred Templin <ftemplin@iprg.nokia.com> wrote:

>> Disclaimer of Validity
>>
>>   This document and the information contained herein are provided on an
>>   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
>>   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
>>   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
>>   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
>>   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
>>   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
>>
>>
>
> I have never seen such a statement appearing in an I-D before.
> Is this a standard statement for such procedural documents?
> And,  is the intention that it be removed (by the RFC editor,
> I guess) before publishing as BCP?

Inserted by xml2rfc. See RFC 3667 section 5.5 - this notice should appear 
in all IETF documents.

                         Harald


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



From ietf-admin@ietf.org  Fri May 21 00:53:58 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20594
	for <ietf-archive@ietf.org>; Fri, 21 May 2004 00:53: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 1BR22i-0000uW-26
	for ietf-archive@ietf.org; Fri, 21 May 2004 00:54:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BR1zD-0000Hh-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 00:50:24 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BR1xD-0007jK-02
	for ietf-archive@ietf.org; Fri, 21 May 2004 00:48:19 -0400
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BR1qm-0004yw-F9
	for ietf-archive@ietf.org; Fri, 21 May 2004 00:41:40 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BR1kR-0006Se-4S; Fri, 21 May 2004 00:35:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BR1eG-00056t-QQ
	for ietf@optimus.ietf.org; Fri, 21 May 2004 00:28:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA19664
	for <ietf@ietf.org>; Fri, 21 May 2004 00: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 1BR1eE-0005tA-4F
	for ietf@ietf.org; Fri, 21 May 2004 00:28:42 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BR1dF-0005hW-00
	for ietf@ietf.org; Fri, 21 May 2004 00:27:41 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BR1cC-0005T7-00; Fri, 21 May 2004 00:26:36 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 4C3D161B8B; Fri, 21 May 2004 06:26:07 +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 24879-03; Fri, 21 May 2004 06:26:06 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 7029C622BE; Fri, 21 May 2004 06:26:04 +0200 (CEST)
Date: Thu, 20 May 2004 21:15:11 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Fred Templin <ftemplin@iprg.nokia.com>
Cc: Pekka Savola <pekkas@netcore.fi>, iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: 'The IESG and RFC Editor documents: Procedures' to
 BCP
Message-ID: <300454600.1085087711@localhost>
In-Reply-To: <40AD4ED6.3010206@iprg.nokia.com>
References: <Pine.LNX.4.44.0405191511470.14373-100000@netcore.fi>
 <161942430.1084949198@localhost> <40AD4ED6.3010206@iprg.nokia.com>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
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.2 required=5.0 tests=AWL,UPPERCASE_25_50 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit



--On 20. mai 2004 17:35 -0700 Fred Templin <ftemplin@iprg.nokia.com> wrote:

>> Disclaimer of Validity
>>
>>   This document and the information contained herein are provided on an
>>   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
>>   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
>>   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
>>   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
>>   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
>>   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
>>
>>
>
> I have never seen such a statement appearing in an I-D before.
> Is this a standard statement for such procedural documents?
> And,  is the intention that it be removed (by the RFC editor,
> I guess) before publishing as BCP?

Inserted by xml2rfc. See RFC 3667 section 5.5 - this notice should appear 
in all IETF documents.

                         Harald


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


From ietf-admin@ietf.org  Fri May 21 01: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 BAA22286
	for <ietf-archive@ietf.org>; Fri, 21 May 2004 01: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 1BR2MJ-0003dM-Nu
	for ietf-archive@ietf.org; Fri, 21 May 2004 01:14:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BR2La-0003XG-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 01:13:31 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BR2Kp-0003Pk-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 01:12:43 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BR2FM-0004dQ-Oe; Fri, 21 May 2004 01:07:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BR2Dh-0004Ds-IG
	for ietf@optimus.ietf.org; Fri, 21 May 2004 01:05: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 BAA21725
	for <ietf@ietf.org>; Fri, 21 May 2004 01:05: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 1BR2De-0002EG-Lk
	for ietf@ietf.org; Fri, 21 May 2004 01:05:18 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BR2Co-00028X-00
	for ietf@ietf.org; Fri, 21 May 2004 01:04:26 -0400
Received: from ganesh.hcltech.com ([202.54.64.2] helo=ganesh.ctd.hcltech.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BR2CQ-00021i-00
	for ietf@ietf.org; Fri, 21 May 2004 01:04:03 -0400
Received: by GANESH with Internet Mail Service (5.5.2653.19)
	id <K0NX1ZGH>; Fri, 21 May 2004 10:38:11 +0530
Message-ID: <68C9DA8F50019B4E8622C53811BEE1D6EAD40B@kavithai.ctd.hcltech.com>
From: "Guru Rajan A  - CTD, Chennai." <gurur@ctd.hcltech.com>
To: ietf@ietf.org
Subject: Unsubscribe
Date: Fri, 21 May 2004 10:33:12 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
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.2 required=5.0 tests=EXCUSE_16 autolearn=no 
	version=2.60



> Hello 
> I like to get unsubscribed from the IETF Mailing list. 
> Thanks !
> Guru 
> 
> 
> Happy Moments, Praise GOD
> Difficult Moments, Seek GOD
> Quiet Moments, Worship GOD
> Painful Moments, Trust GOD
> Every Moment, Thank GOD
> 
> Regards
> Guru Rajan 
> Disclaimer: 
> 		This message and any attachment(s) contained here are
> information that is confidential, proprietary to HCL Technologies and its
> customers. Contents may be privileged or otherwise protected by law. The
> information is solely intended for the individual or the entity it is
> addressed to. If you are not the intended recipient of this message, you
> are not authorized to read, forward, print, retain, copy or disseminate
> this message or any part of it. If you have received this e-mail in error,
> please notify the sender immediately by return e-mail and delete it from
> your computer.
> 
> 
> 

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


From exim@www1.ietf.org  Fri May 21 01:14:38 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 BAA22309
	for <ietf-archive@odin.ietf.org>; Fri, 21 May 2004 01:14:38 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BR2Ks-0006cT-9t
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 01:12:46 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4L5CkVi025395
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 01:12:46 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BR2FM-0004dQ-Oe; Fri, 21 May 2004 01:07:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BR2Dh-0004Ds-IG
	for ietf@optimus.ietf.org; Fri, 21 May 2004 01:05: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 BAA21725
	for <ietf@ietf.org>; Fri, 21 May 2004 01:05: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 1BR2De-0002EG-Lk
	for ietf@ietf.org; Fri, 21 May 2004 01:05:18 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BR2Co-00028X-00
	for ietf@ietf.org; Fri, 21 May 2004 01:04:26 -0400
Received: from ganesh.hcltech.com ([202.54.64.2] helo=ganesh.ctd.hcltech.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BR2CQ-00021i-00
	for ietf@ietf.org; Fri, 21 May 2004 01:04:03 -0400
Received: by GANESH with Internet Mail Service (5.5.2653.19)
	id <K0NX1ZGH>; Fri, 21 May 2004 10:38:11 +0530
Message-ID: <68C9DA8F50019B4E8622C53811BEE1D6EAD40B@kavithai.ctd.hcltech.com>
From: "Guru Rajan A  - CTD, Chennai." <gurur@ctd.hcltech.com>
To: ietf@ietf.org
Subject: Unsubscribe
Date: Fri, 21 May 2004 10:33:12 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=EXCUSE_16 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>



> Hello 
> I like to get unsubscribed from the IETF Mailing list. 
> Thanks !
> Guru 
> 
> 
> Happy Moments, Praise GOD
> Difficult Moments, Seek GOD
> Quiet Moments, Worship GOD
> Painful Moments, Trust GOD
> Every Moment, Thank GOD
> 
> Regards
> Guru Rajan 
> Disclaimer: 
> 		This message and any attachment(s) contained here are
> information that is confidential, proprietary to HCL Technologies and its
> customers. Contents may be privileged or otherwise protected by law. The
> information is solely intended for the individual or the entity it is
> addressed to. If you are not the intended recipient of this message, you
> are not authorized to read, forward, print, retain, copy or disseminate
> this message or any part of it. If you have received this e-mail in error,
> please notify the sender immediately by return e-mail and delete it from
> your computer.
> 
> 
> 

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



From ietf-admin@ietf.org  Fri May 21 03:19: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 DAA11678
	for <ietf-archive@ietf.org>; Fri, 21 May 2004 03:19: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 1BR4Jk-0003td-Pq
	for ietf-archive@ietf.org; Fri, 21 May 2004 03:19:44 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BR4Ii-0003hq-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 03:18:41 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BR4Hr-0003Xr-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 03:17:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BR42u-0003Ot-U0; Fri, 21 May 2004 03:02:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BR410-0002hD-G6
	for ietf@optimus.ietf.org; Fri, 21 May 2004 03:00: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 DAA10700
	for <ietf@ietf.org>; Fri, 21 May 2004 03:00: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 1BR40v-0001H2-T7
	for ietf@ietf.org; Fri, 21 May 2004 03:00:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BR401-00017o-00
	for ietf@ietf.org; Fri, 21 May 2004 02:59:21 -0400
Received: from 1-1-2-20b.rny.sth.bostream.se ([82.182.132.65] helo=klapautius.it.su.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BR3zE-0000yZ-00
	for ietf@ietf.org; Fri, 21 May 2004 02:58:32 -0400
Received: from it.su.se (localhost.localdomain [127.0.0.1])
	by klapautius.it.su.se (8.11.6/8.11.6) with ESMTP id i4L6um507729;
	Fri, 21 May 2004 08:56:53 +0200
Message-ID: <40ADA830.3070107@it.su.se>
Date: Fri, 21 May 2004 08:56:48 +0200
From: Leif Johansson <leifj@it.su.se>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: sv, en, en-us
MIME-Version: 1.0
To: Dave Crocker <dcrocker@brandenburg.com>
CC: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>, ietf@ietf.org
Subject: Re: 60th IETF - Registration
References: <DC55E4CF3BF32E46B6F1FA9028E35667626A@w3k.win3k.braintec-consult.de> <0b6001c43d05$f68ccd10$0402200a@consulintel.es> <40AA6661.4000304@it.su.se> <852774956.20040520163528@brandenburg.com>
In-Reply-To: <852774956.20040520163528@brandenburg.com>
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=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Dave Crocker wrote:
> Leif,
> 
> LJ> Big hotels that are cheap and where the staff won't throw a fit
> LJ> when we all turn up in force, laptops, duct-tape and all, don't
> LJ> exactly grow on trees you know! I'm happy if it has a bar.
> 
> 
>     that must be why we are going to one that costs US$ 179/night,
>     with no secondary lodging listed.

Hey - I'm all for a permanent relocation to Minneapolis! But I have
seen worse. The LA IETF was >200$ per night. The 'throw-a-fit' bit
probably limits the choices a bit too. I remember working on the
Stockholm IETF. We (the local staff) were politely asked but the
staff of the Grand Hotel to please use the service entrances as we
were scaring the other guests :-)

	MVH leifj

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


From ietf-admin@ietf.org  Fri May 21 05:00: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 FAA16610
	for <ietf-archive@ietf.org>; Fri, 21 May 2004 05:00: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 1BR5t8-0002RZ-LA
	for ietf-archive@ietf.org; Fri, 21 May 2004 05:00:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BR5sE-0002GE-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 04:59:26 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BR5rK-00025X-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 04:58:30 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BR5eS-00037A-BR; Fri, 21 May 2004 04:45:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BR5T4-0008BP-Vd
	for ietf@optimus.ietf.org; Fri, 21 May 2004 04:33: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 EAA14898
	for <ietf@ietf.org>; Fri, 21 May 2004 04:33: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 1BR5T1-0005wI-Rt
	for ietf@ietf.org; Fri, 21 May 2004 04:33:23 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BR5SB-0005oT-00
	for ietf@ietf.org; Fri, 21 May 2004 04:32:32 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BR5Rg-0005fw-00
	for ietf@ietf.org; Fri, 21 May 2004 04:32:00 -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 i4L8VX1C046332;
	Fri, 21 May 2004 10:31:33 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <40ADA830.3070107@it.su.se>
References: <DC55E4CF3BF32E46B6F1FA9028E35667626A@w3k.win3k.braintec-consult.de> <0b6001c43d05$f68ccd10$0402200a@consulintel.es> <40AA6661.4000304@it.su.se> <852774956.20040520163528@brandenburg.com> <40ADA830.3070107@it.su.se>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <4D17E587-AB01-11D8-8097-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: "'Internet Engineering Task Force'" <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: 60th IETF - Registration
Date: Fri, 21 May 2004 10:31:48 +0200
To: Leif Johansson <leifj@it.su.se>
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 21-mei-04, at 8:56, Leif Johansson wrote:

>> LJ> Big hotels that are cheap and where the staff won't throw a fit
>> LJ> when we all turn up in force, laptops, duct-tape and all, don't
>> LJ> exactly grow on trees you know! I'm happy if it has a bar.
>>     that must be why we are going to one that costs US$ 179/night,
>>     with no secondary lodging listed.

> Hey - I'm all for a permanent relocation to Minneapolis!

Great, then I can get fingerprinted three times a year... If the IETF 
is going for permanent relocation, let's make it outside the US, ok?

> But I have
> seen worse. The LA IETF was >200$ per night. The 'throw-a-fit' bit
> probably limits the choices a bit too. I remember working on the
> Stockholm IETF. We (the local staff) were politely asked but the
> staff of the Grand Hotel to please use the service entrances as we
> were scaring the other guests :-)

On a related note: can someone who is in the know say whether efforts 
to host an IETF meeting are appreciated? I sent a message to the 
secretariat asking about conference room sizes and so on a while back 
but didn't get an answer, and some rumors I heard weren't exactly 
inspiring either.


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


From exim@www1.ietf.org  Fri May 21 05:11:32 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 FAA17380
	for <ietf-archive@odin.ietf.org>; Fri, 21 May 2004 05:11: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 1BR5rN-0006o6-9D
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 04:58:35 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4L8wW5h025986
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 04:58:32 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BR5eS-00037A-BR; Fri, 21 May 2004 04:45:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BR5T4-0008BP-Vd
	for ietf@optimus.ietf.org; Fri, 21 May 2004 04:33: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 EAA14898
	for <ietf@ietf.org>; Fri, 21 May 2004 04:33: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 1BR5T1-0005wI-Rt
	for ietf@ietf.org; Fri, 21 May 2004 04:33:23 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BR5SB-0005oT-00
	for ietf@ietf.org; Fri, 21 May 2004 04:32:32 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BR5Rg-0005fw-00
	for ietf@ietf.org; Fri, 21 May 2004 04:32:00 -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 i4L8VX1C046332;
	Fri, 21 May 2004 10:31:33 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <40ADA830.3070107@it.su.se>
References: <DC55E4CF3BF32E46B6F1FA9028E35667626A@w3k.win3k.braintec-consult.de> <0b6001c43d05$f68ccd10$0402200a@consulintel.es> <40AA6661.4000304@it.su.se> <852774956.20040520163528@brandenburg.com> <40ADA830.3070107@it.su.se>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <4D17E587-AB01-11D8-8097-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: "'Internet Engineering Task Force'" <ietf@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: 60th IETF - Registration
Date: Fri, 21 May 2004 10:31:48 +0200
To: Leif Johansson <leifj@it.su.se>
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 21-mei-04, at 8:56, Leif Johansson wrote:

>> LJ> Big hotels that are cheap and where the staff won't throw a fit
>> LJ> when we all turn up in force, laptops, duct-tape and all, don't
>> LJ> exactly grow on trees you know! I'm happy if it has a bar.
>>     that must be why we are going to one that costs US$ 179/night,
>>     with no secondary lodging listed.

> Hey - I'm all for a permanent relocation to Minneapolis!

Great, then I can get fingerprinted three times a year... If the IETF 
is going for permanent relocation, let's make it outside the US, ok?

> But I have
> seen worse. The LA IETF was >200$ per night. The 'throw-a-fit' bit
> probably limits the choices a bit too. I remember working on the
> Stockholm IETF. We (the local staff) were politely asked but the
> staff of the Grand Hotel to please use the service entrances as we
> were scaring the other guests :-)

On a related note: can someone who is in the know say whether efforts 
to host an IETF meeting are appreciated? I sent a message to the 
secretariat asking about conference room sizes and so on a while back 
but didn't get an answer, and some rumors I heard weren't exactly 
inspiring either.


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



From ietf-admin@ietf.org  Fri May 21 08:44: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 IAA27690
	for <ietf-archive@ietf.org>; Fri, 21 May 2004 08:44: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 1BR9O2-0002U8-NO
	for ietf-archive@ietf.org; Fri, 21 May 2004 08:44:30 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BR9N1-0002EV-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 08:43:28 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BR9Lz-0001s7-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 08: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 1BR94S-0007X4-5M; Fri, 21 May 2004 08:24:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BR8BR-00044X-DE
	for ietf@optimus.ietf.org; Fri, 21 May 2004 07:27: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 HAA24704
	for <ietf@ietf.org>; Fri, 21 May 2004 07:27: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 1BR8BQ-0003xI-Nx
	for ietf@ietf.org; Fri, 21 May 2004 07:27:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BR8AS-0003n5-00
	for ietf@ietf.org; Fri, 21 May 2004 07:26:24 -0400
Received: from mail.consulintel.es ([213.172.48.142] helo=consulintel.es)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BR89S-0003U8-00
	for ietf@ietf.org; Fri, 21 May 2004 07:25:22 -0400
Received: from consulintel02 ([217.126.187.160])
	(authenticated user jordi.palet@consulintel.es)
	by consulintel.es (consulintel.es [127.0.0.1])
	(MDaemon.PRO.v7.0.1.R)
	with ESMTP id md50000111406.msg
	for <ietf@ietf.org>; Fri, 21 May 2004 13:26:00 +0200
Message-ID: <0fa701c43f26$2939af90$8700000a@consulintel.es>
Reply-To: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
From: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
Subject: respect privacy please !
Date: Fri, 21 May 2004 13:24:19 +0200
Organization: Consulintel
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Spam-Processed: consulintel.es, Fri, 21 May 2004 13:26:00 +0200
	(not processed: message from valid local sender)
X-MDRemoteIP: 217.126.187.160
X-Return-Path: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
X-MDAV-Processed: consulintel.es, Fri, 21 May 2004 13:26:04 +0200
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.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable

Hi,

I've already raised this some time ago, same as other people did, but I still see my name being published, w/o my consent, in the list of attendees.

This is not acceptable, we should have the option to choose if we want to have our name published or not when we do the registration.

I will also like to get some response about the time frame to get the IETF sites IPv6-enabled. If there is any problem for doing that, I already volunteered to host a mirror.

Regards,
Jordi





**********************************
Madrid 2003 Global IPv6 Summit
Presentations and videos on line at:
http://www.ipv6-es.com

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.




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


From exim@www1.ietf.org  Fri May 21 08: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 IAA27971
	for <ietf-archive@odin.ietf.org>; Fri, 21 May 2004 08:46: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 1BR9M0-0003Gd-PY
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 08:42:26 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4LCgOAn012298
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 08:42:24 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BR94S-0007X4-5M; Fri, 21 May 2004 08:24:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BR8BR-00044X-DE
	for ietf@optimus.ietf.org; Fri, 21 May 2004 07:27: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 HAA24704
	for <ietf@ietf.org>; Fri, 21 May 2004 07:27: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 1BR8BQ-0003xI-Nx
	for ietf@ietf.org; Fri, 21 May 2004 07:27:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BR8AS-0003n5-00
	for ietf@ietf.org; Fri, 21 May 2004 07:26:24 -0400
Received: from mail.consulintel.es ([213.172.48.142] helo=consulintel.es)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BR89S-0003U8-00
	for ietf@ietf.org; Fri, 21 May 2004 07:25:22 -0400
Received: from consulintel02 ([217.126.187.160])
	(authenticated user jordi.palet@consulintel.es)
	by consulintel.es (consulintel.es [127.0.0.1])
	(MDaemon.PRO.v7.0.1.R)
	with ESMTP id md50000111406.msg
	for <ietf@ietf.org>; Fri, 21 May 2004 13:26:00 +0200
Message-ID: <0fa701c43f26$2939af90$8700000a@consulintel.es>
Reply-To: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
From: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
Subject: respect privacy please !
Date: Fri, 21 May 2004 13:24:19 +0200
Organization: Consulintel
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Spam-Processed: consulintel.es, Fri, 21 May 2004 13:26:00 +0200
	(not processed: message from valid local sender)
X-MDRemoteIP: 217.126.187.160
X-Return-Path: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
X-MDAV-Processed: consulintel.es, Fri, 21 May 2004 13:26:04 +0200
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: 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

Hi,

I've already raised this some time ago, same as other people did, but I still see my name being published, w/o my consent, in the list of attendees.

This is not acceptable, we should have the option to choose if we want to have our name published or not when we do the registration.

I will also like to get some response about the time frame to get the IETF sites IPv6-enabled. If there is any problem for doing that, I already volunteered to host a mirror.

Regards,
Jordi





**********************************
Madrid 2003 Global IPv6 Summit
Presentations and videos on line at:
http://www.ipv6-es.com

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.




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



From ietf-admin@ietf.org  Fri May 21 09:57: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 JAA01824
	for <ietf-archive@ietf.org>; Fri, 21 May 2004 09:57:35 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRAWn-0002Ap-89
	for ietf-archive@ietf.org; Fri, 21 May 2004 09:57:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRAVr-0001x0-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 09:56:39 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRAUy-0001iw-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 09:55:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRAEv-0001Yu-1h; Fri, 21 May 2004 09:39:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRACT-0000TQ-I5
	for ietf@optimus.ietf.org; Fri, 21 May 2004 09:36:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00817
	for <ietf@ietf.org>; Fri, 21 May 2004 09:36: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 1BRACR-0005SI-Ea
	for ietf@ietf.org; Fri, 21 May 2004 09:36:35 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRABT-0005GP-00
	for ietf@ietf.org; Fri, 21 May 2004 09:35:36 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRAAW-000549-00
	for ietf@ietf.org; Fri, 21 May 2004 09:34:36 -0400
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1BRAAV-0005GX-00; Fri, 21 May 2004 08:34:35 -0500
Date: Fri, 21 May 2004 09:34:35 -0400
From: John C Klensin <john-ietf@jck.com>
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
cc: ietf@ietf.org
Subject: Re: respect privacy please !
Message-ID: <C920A0255CBCAF05FBEE6AC9@scan.jck.com>
In-Reply-To: <0fa701c43f26$2939af90$8700000a@consulintel.es>
References: <0fa701c43f26$2939af90$8700000a@consulintel.es>
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.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Jordi,

This has been discussed several times before.  While I share 
your discomfort, IETF is not some "conference" you might be 
attending.  It is very difficult to claim that one has an open 
standards process when some participants are permitted attend 
meetings and, potentially, influence decisions while being 
hidden or anonymous. We do not discourage people from lurking 
quietly on mailing lists. But I think that, as soon as anyone 
more actively participates -- whether by posting to mailing 
lists or attending meetings (especially since the latter is a 
qualification for Nomcom membership that must be publicly 
verifiable) -- then I think desires for privacy have to yield to 
the importance of trust in the IETF community and its processes. 
As with IPR disclosures, if one can't accept the rules, the best 
option is to decide to not play.

Out of curiosity, would you feed better about this if the 
boilerplate you need to page through to register said, 
explicitly, "if you don't want your name to be made public as a 
registrant and participant, please don't register or attend" or 
"by registering, you consent..."?  I don't have any control over 
the text or decisions but assume that, if lots of people wanted 
such language to eliminate any misunderstandings about whether 
you had consented, the IESG and Secretariat would probably agree 
to add it.

At least the Secretariat no longer feels a need to publish email 
addresses with the list of registrants :-(

     best,
      john

p.s. Note that the above is purely a process and moral position. 
There is, I'm sure, a legal one that parallels it, but I'd 
rather not go there --and set off a wave of amateur lawyering-- 
if we can help it.



--On Friday, 21 May, 2004 13:24 +0200 JORDI PALET MARTINEZ 
<jordi.palet@consulintel.es> wrote:

> Hi,
>
> I've already raised this some time ago, same as other people
> did, but I still see my name being published, w/o my consent,
> in the list of attendees.
>
> This is not acceptable, we should have the option to choose if
> we want to have our name published or not when we do the
> registration.
>
> I will also like to get some response about the time frame to
> get the IETF sites IPv6-enabled. If there is any problem for
> doing that, I already volunteered to host a mirror.
>
> Regards,
> Jordi





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


From exim@www1.ietf.org  Fri May 21 10:02:05 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 KAA02143
	for <ietf-archive@odin.ietf.org>; Fri, 21 May 2004 10:02: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 1BRAUz-00055o-FP
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 09:55:45 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4LDtjjM019568
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 09:55:45 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRAEv-0001Yu-1h; Fri, 21 May 2004 09:39:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRACT-0000TQ-I5
	for ietf@optimus.ietf.org; Fri, 21 May 2004 09:36:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00817
	for <ietf@ietf.org>; Fri, 21 May 2004 09:36: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 1BRACR-0005SI-Ea
	for ietf@ietf.org; Fri, 21 May 2004 09:36:35 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRABT-0005GP-00
	for ietf@ietf.org; Fri, 21 May 2004 09:35:36 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRAAW-000549-00
	for ietf@ietf.org; Fri, 21 May 2004 09:34:36 -0400
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1BRAAV-0005GX-00; Fri, 21 May 2004 08:34:35 -0500
Date: Fri, 21 May 2004 09:34:35 -0400
From: John C Klensin <john-ietf@jck.com>
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
cc: ietf@ietf.org
Subject: Re: respect privacy please !
Message-ID: <C920A0255CBCAF05FBEE6AC9@scan.jck.com>
In-Reply-To: <0fa701c43f26$2939af90$8700000a@consulintel.es>
References: <0fa701c43f26$2939af90$8700000a@consulintel.es>
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.1 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

Jordi,

This has been discussed several times before.  While I share 
your discomfort, IETF is not some "conference" you might be 
attending.  It is very difficult to claim that one has an open 
standards process when some participants are permitted attend 
meetings and, potentially, influence decisions while being 
hidden or anonymous. We do not discourage people from lurking 
quietly on mailing lists. But I think that, as soon as anyone 
more actively participates -- whether by posting to mailing 
lists or attending meetings (especially since the latter is a 
qualification for Nomcom membership that must be publicly 
verifiable) -- then I think desires for privacy have to yield to 
the importance of trust in the IETF community and its processes. 
As with IPR disclosures, if one can't accept the rules, the best 
option is to decide to not play.

Out of curiosity, would you feed better about this if the 
boilerplate you need to page through to register said, 
explicitly, "if you don't want your name to be made public as a 
registrant and participant, please don't register or attend" or 
"by registering, you consent..."?  I don't have any control over 
the text or decisions but assume that, if lots of people wanted 
such language to eliminate any misunderstandings about whether 
you had consented, the IESG and Secretariat would probably agree 
to add it.

At least the Secretariat no longer feels a need to publish email 
addresses with the list of registrants :-(

     best,
      john

p.s. Note that the above is purely a process and moral position. 
There is, I'm sure, a legal one that parallels it, but I'd 
rather not go there --and set off a wave of amateur lawyering-- 
if we can help it.



--On Friday, 21 May, 2004 13:24 +0200 JORDI PALET MARTINEZ 
<jordi.palet@consulintel.es> wrote:

> Hi,
>
> I've already raised this some time ago, same as other people
> did, but I still see my name being published, w/o my consent,
> in the list of attendees.
>
> This is not acceptable, we should have the option to choose if
> we want to have our name published or not when we do the
> registration.
>
> I will also like to get some response about the time frame to
> get the IETF sites IPv6-enabled. If there is any problem for
> doing that, I already volunteered to host a mirror.
>
> Regards,
> Jordi





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



From ietf-admin@ietf.org  Fri May 21 10:27: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 KAA04520
	for <ietf-archive@ietf.org>; Fri, 21 May 2004 10:27:52 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRB06-00017c-E9
	for ietf-archive@ietf.org; Fri, 21 May 2004 10:27:54 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRAzB-0000re-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 10:26:58 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRAyF-0000cG-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 10:25:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRAoe-0005LA-DE; Fri, 21 May 2004 10:16:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRAbu-0008OL-Rg
	for ietf@optimus.ietf.org; Fri, 21 May 2004 10:02: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 KAA02207
	for <ietf@ietf.org>; Fri, 21 May 2004 10:02: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 1BRAbs-0003Ka-Eb
	for ietf@ietf.org; Fri, 21 May 2004 10:02:52 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRAat-00037u-00
	for ietf@ietf.org; Fri, 21 May 2004 10:01:52 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRAaP-0002sX-00
	for ietf@ietf.org; Fri, 21 May 2004 10:01:22 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 98A27621CC; Fri, 21 May 2004 16:00:49 +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 05266-10; Fri, 21 May 2004 16:00:48 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 4F8B6621B6; Fri, 21 May 2004 16:00:46 +0200 (CEST)
Date: Fri, 21 May 2004 06:56:46 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Iljitsch van Beijnum <iljitsch@muada.com>, Leif Johansson <leifj@it.su.se>
Cc: "'Internet Engineering Task Force'" <ietf@ietf.org>
Subject: Re: 60th IETF - Registration
Message-ID: <335313705.1085122606@localhost>
In-Reply-To: <4D17E587-AB01-11D8-8097-000A95CD987A@muada.com>
References: <DC55E4CF3BF32E46B6F1FA9028E35667626A@w3k.win3k.braintec-consult.
 de> <0b6001c43d05$f68ccd10$0402200a@consulintel.es>
 <40AA6661.4000304@it.su.se> <852774956.20040520163528@brandenburg.com>
 <40ADA830.3070107@it.su.se> <4D17E587-AB01-11D8-8097-000A95CD987A@muada.com>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
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 21. mai 2004 10:31 +0200 Iljitsch van Beijnum <iljitsch@muada.com> 
wrote:

>> But I have
>> seen worse. The LA IETF was >200$ per night. The 'throw-a-fit' bit
>> probably limits the choices a bit too. I remember working on the
>> Stockholm IETF. We (the local staff) were politely asked but the
>> staff of the Grand Hotel to please use the service entrances as we
>> were scaring the other guests :-)
>
> On a related note: can someone who is in the know say whether efforts to
> host an IETF meeting are appreciated? I sent a message to the secretariat
> asking about conference room sizes and so on a while back but didn't get
> an answer, and some rumors I heard weren't exactly inspiring either.

Offers ARE appreciated. Very much so!

However, not all of them work out - we had an offer last year that we 
decided not to follow up on - after thinking about it, the best available 
site had some logistical problems we were unable to accept.

Please re-send your message, CC me - you should at least get an answer!

                           Harald




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


From ietf-admin@ietf.org  Fri May 21 10:29: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 KAA04683
	for <ietf-archive@ietf.org>; Fri, 21 May 2004 10:29: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 1BRB1E-0001OX-0f
	for ietf-archive@ietf.org; Fri, 21 May 2004 10:29:04 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRB0G-000195-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 10:28:04 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRAzR-0000tG-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 10:27:13 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRAof-0005LO-R1; Fri, 21 May 2004 10:16:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRAbv-0008OV-EL
	for ietf@optimus.ietf.org; Fri, 21 May 2004 10:02: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 KAA02214
	for <ietf@ietf.org>; Fri, 21 May 2004 10:02: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 1BRAbt-0003Kf-2k
	for ietf@ietf.org; Fri, 21 May 2004 10:02:53 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRAau-000382-00
	for ietf@ietf.org; Fri, 21 May 2004 10:01:52 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRAaR-0002sr-00
	for ietf@ietf.org; Fri, 21 May 2004 10:01:23 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id B038E622C9; Fri, 21 May 2004 16:00:52 +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 05416-05; Fri, 21 May 2004 16:00:52 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 028A5621B6; Fri, 21 May 2004 16:00:50 +0200 (CEST)
Date: Fri, 21 May 2004 06:58:29 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>, ietf@ietf.org
Subject: Re: respect privacy please !
Message-ID: <335417014.1085122709@localhost>
In-Reply-To: <0fa701c43f26$2939af90$8700000a@consulintel.es>
References: <0fa701c43f26$2939af90$8700000a@consulintel.es>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
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 21. mai 2004 13:24 +0200 JORDI PALET MARTINEZ 
<jordi.palet@consulintel.es> wrote:

> Hi,
>
> I've already raised this some time ago, same as other people did, but I
> still see my name being published, w/o my consent, in the list of
> attendees.
>
> This is not acceptable, we should have the option to choose if we want to
> have our name published or not when we do the registration.

Jordi,

are you objecting to having your name published *at all*, or having your 
name published *before the meeting*?

The list of attendees (but not their contact info) is (according to the 
lawyers) a legal requirement for our way of doing business; it is part of 
the transparency requirement that it's possible to find out who was there.

                      Harald




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


From ietf-admin@ietf.org  Fri May 21 10:37: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 KAA05754
	for <ietf-archive@ietf.org>; Fri, 21 May 2004 10:37: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 1BRB9g-0003RT-Jy
	for ietf-archive@ietf.org; Fri, 21 May 2004 10:37:48 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRB8k-0003D2-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 10:36:51 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRB82-0002zH-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 10:36:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRAvN-0008Vx-UW; Fri, 21 May 2004 10:23:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRAgX-0002Dw-0V
	for ietf@optimus.ietf.org; Fri, 21 May 2004 10:07: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 KAA02596
	for <ietf@ietf.org>; Fri, 21 May 2004 10:07: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 1BRAgR-0004M6-VA
	for ietf@ietf.org; Fri, 21 May 2004 10:07:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRAfS-00049K-00
	for ietf@ietf.org; Fri, 21 May 2004 10:06:35 -0400
Received: from c3p0.cc.swin.edu.au ([136.186.1.30] helo=swin.edu.au)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRAeU-0003jt-00
	for ietf@ietf.org; Fri, 21 May 2004 10:05:34 -0400
Received: from swin.edu.au (www.caia.swin.edu.au [136.186.229.16])
	by swin.edu.au (8.9.3p2-20030918/8.9.3) with ESMTP id AAA764860;
	Sat, 22 May 2004 00:05:01 +1000 (EST)
Message-ID: <40AE0C8C.6CFD72A3@swin.edu.au>
Date: Sat, 22 May 2004 00:05:00 +1000
From: grenville armitage <garmitage@swin.edu.au>
Organization: Centre for Advanced Internet Architectures, Swinburne University of 
 Technology
X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: respect privacy please !
References: <0fa701c43f26$2939af90$8700000a@consulintel.es> <C920A0255CBCAF05FBEE6AC9@scan.jck.com>
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


> --On Friday, 21 May, 2004 13:24 +0200 JORDI PALET MARTINEZ
> <jordi.palet@consulintel.es> wrote:
> 
> > Hi,
> >
> > I've already raised this some time ago, same as other people
> > did, but I still see my name being published, w/o my consent,
> > in the list of attendees.

This could be solved by the IETF insisting that consent is required
before attendance. I, like John, do not believe it is acceptable for
the IETF meetings to be populated by anonymous attendees.

(The irony of your email address being public on this list is
not lost.)

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

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


From exim@www1.ietf.org  Fri May 21 10:41:51 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 KAA06010
	for <ietf-archive@odin.ietf.org>; Fri, 21 May 2004 10:41:51 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRAyH-0001V2-74
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 10:26:07 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4LEQ1ZX005755
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 10:26:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRAoe-0005LA-DE; Fri, 21 May 2004 10:16:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRAbu-0008OL-Rg
	for ietf@optimus.ietf.org; Fri, 21 May 2004 10:02: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 KAA02207
	for <ietf@ietf.org>; Fri, 21 May 2004 10:02: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 1BRAbs-0003Ka-Eb
	for ietf@ietf.org; Fri, 21 May 2004 10:02:52 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRAat-00037u-00
	for ietf@ietf.org; Fri, 21 May 2004 10:01:52 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRAaP-0002sX-00
	for ietf@ietf.org; Fri, 21 May 2004 10:01:22 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 98A27621CC; Fri, 21 May 2004 16:00:49 +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 05266-10; Fri, 21 May 2004 16:00:48 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 4F8B6621B6; Fri, 21 May 2004 16:00:46 +0200 (CEST)
Date: Fri, 21 May 2004 06:56:46 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Iljitsch van Beijnum <iljitsch@muada.com>, Leif Johansson <leifj@it.su.se>
Cc: "'Internet Engineering Task Force'" <ietf@ietf.org>
Subject: Re: 60th IETF - Registration
Message-ID: <335313705.1085122606@localhost>
In-Reply-To: <4D17E587-AB01-11D8-8097-000A95CD987A@muada.com>
References: <DC55E4CF3BF32E46B6F1FA9028E35667626A@w3k.win3k.braintec-consult.
 de> <0b6001c43d05$f68ccd10$0402200a@consulintel.es>
 <40AA6661.4000304@it.su.se> <852774956.20040520163528@brandenburg.com>
 <40ADA830.3070107@it.su.se> <4D17E587-AB01-11D8-8097-000A95CD987A@muada.com>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-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: 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 21. mai 2004 10:31 +0200 Iljitsch van Beijnum <iljitsch@muada.com> 
wrote:

>> But I have
>> seen worse. The LA IETF was >200$ per night. The 'throw-a-fit' bit
>> probably limits the choices a bit too. I remember working on the
>> Stockholm IETF. We (the local staff) were politely asked but the
>> staff of the Grand Hotel to please use the service entrances as we
>> were scaring the other guests :-)
>
> On a related note: can someone who is in the know say whether efforts to
> host an IETF meeting are appreciated? I sent a message to the secretariat
> asking about conference room sizes and so on a while back but didn't get
> an answer, and some rumors I heard weren't exactly inspiring either.

Offers ARE appreciated. Very much so!

However, not all of them work out - we had an offer last year that we 
decided not to follow up on - after thinking about it, the best available 
site had some logistical problems we were unable to accept.

Please re-send your message, CC me - you should at least get an answer!

                           Harald




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



From exim@www1.ietf.org  Fri May 21 10:41:53 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 KAA06029
	for <ietf-archive@odin.ietf.org>; Fri, 21 May 2004 10:41: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 1BRAzT-0002Kj-KV
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 10:27:15 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4LERFeK008924
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 10:27:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRAof-0005LO-R1; Fri, 21 May 2004 10:16:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRAbv-0008OV-EL
	for ietf@optimus.ietf.org; Fri, 21 May 2004 10:02: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 KAA02214
	for <ietf@ietf.org>; Fri, 21 May 2004 10:02: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 1BRAbt-0003Kf-2k
	for ietf@ietf.org; Fri, 21 May 2004 10:02:53 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRAau-000382-00
	for ietf@ietf.org; Fri, 21 May 2004 10:01:52 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRAaR-0002sr-00
	for ietf@ietf.org; Fri, 21 May 2004 10:01:23 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id B038E622C9; Fri, 21 May 2004 16:00:52 +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 05416-05; Fri, 21 May 2004 16:00:52 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 028A5621B6; Fri, 21 May 2004 16:00:50 +0200 (CEST)
Date: Fri, 21 May 2004 06:58:29 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>, ietf@ietf.org
Subject: Re: respect privacy please !
Message-ID: <335417014.1085122709@localhost>
In-Reply-To: <0fa701c43f26$2939af90$8700000a@consulintel.es>
References: <0fa701c43f26$2939af90$8700000a@consulintel.es>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-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: 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 21. mai 2004 13:24 +0200 JORDI PALET MARTINEZ 
<jordi.palet@consulintel.es> wrote:

> Hi,
>
> I've already raised this some time ago, same as other people did, but I
> still see my name being published, w/o my consent, in the list of
> attendees.
>
> This is not acceptable, we should have the option to choose if we want to
> have our name published or not when we do the registration.

Jordi,

are you objecting to having your name published *at all*, or having your 
name published *before the meeting*?

The list of attendees (but not their contact info) is (according to the 
lawyers) a legal requirement for our way of doing business; it is part of 
the transparency requirement that it's possible to find out who was there.

                      Harald




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



From exim@www1.ietf.org  Fri May 21 10:45:00 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 KAA06388
	for <ietf-archive@odin.ietf.org>; Fri, 21 May 2004 10:45: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 1BRB87-0006AY-41
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 10:36:14 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4LEa8ZV023457
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 10:36:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRAvN-0008Vx-UW; Fri, 21 May 2004 10:23:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRAgX-0002Dw-0V
	for ietf@optimus.ietf.org; Fri, 21 May 2004 10:07: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 KAA02596
	for <ietf@ietf.org>; Fri, 21 May 2004 10:07: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 1BRAgR-0004M6-VA
	for ietf@ietf.org; Fri, 21 May 2004 10:07:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRAfS-00049K-00
	for ietf@ietf.org; Fri, 21 May 2004 10:06:35 -0400
Received: from c3p0.cc.swin.edu.au ([136.186.1.30] helo=swin.edu.au)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRAeU-0003jt-00
	for ietf@ietf.org; Fri, 21 May 2004 10:05:34 -0400
Received: from swin.edu.au (www.caia.swin.edu.au [136.186.229.16])
	by swin.edu.au (8.9.3p2-20030918/8.9.3) with ESMTP id AAA764860;
	Sat, 22 May 2004 00:05:01 +1000 (EST)
Message-ID: <40AE0C8C.6CFD72A3@swin.edu.au>
Date: Sat, 22 May 2004 00:05:00 +1000
From: grenville armitage <garmitage@swin.edu.au>
Organization: Centre for Advanced Internet Architectures, Swinburne University of 
 Technology
X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: respect privacy please !
References: <0fa701c43f26$2939af90$8700000a@consulintel.es> <C920A0255CBCAF05FBEE6AC9@scan.jck.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: 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 Friday, 21 May, 2004 13:24 +0200 JORDI PALET MARTINEZ
> <jordi.palet@consulintel.es> wrote:
> 
> > Hi,
> >
> > I've already raised this some time ago, same as other people
> > did, but I still see my name being published, w/o my consent,
> > in the list of attendees.

This could be solved by the IETF insisting that consent is required
before attendance. I, like John, do not believe it is acceptable for
the IETF meetings to be populated by anonymous attendees.

(The irony of your email address being public on this list is
not lost.)

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

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



From ietf-admin@ietf.org  Fri May 21 11:04: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 LAA07526
	for <ietf-archive@ietf.org>; Fri, 21 May 2004 11:04: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 1BRBZh-0001oF-2V
	for ietf-archive@ietf.org; Fri, 21 May 2004 11:04:41 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRBYj-0001Zh-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 11:03:41 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRBXr-0001MU-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 11:02:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRBPS-00029Q-8m; Fri, 21 May 2004 10:54:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRBJe-0000ns-KY
	for ietf@optimus.ietf.org; Fri, 21 May 2004 10:48: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 KAA06682
	for <ietf@ietf.org>; Fri, 21 May 2004 10:47: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 1BRBJW-0005uE-7N
	for ietf@ietf.org; Fri, 21 May 2004 10:47:58 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRBIr-0005fo-00
	for ietf@ietf.org; Fri, 21 May 2004 10:47:17 -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 1BRBHr-0005M2-00
	for ietf@ietf.org; Fri, 21 May 2004 10:46:15 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: respect privacy please !
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Date: Fri, 21 May 2004 07:45:44 -0700
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B0DB133@server2003.arneill-py.sacramento.ca.us>
Thread-Topic: respect privacy please !
thread-index: AcQ/MQ2sYCaX2jNfQMKrOLPGIsd0BQAEF2kQ
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Jordi Palet Martinez" <jordi.palet@consulintel.es>, <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

> JORDI PALET MARTINEZ wrote:
> I've already raised this some time ago, same as other
> people did, but I still see my name being published,
> w/o my consent, in the list of attendees.

Besides the fact that it is done without your consent, is there
something fundamentally wrong with it in your view? I don't care if the
IETF lists my name, is there a reason I should?

> This is not acceptable, we should have the option to
> choose if we want to have our name published or not
> when we do the registration.

It appears this will not happen.

Michel.


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


From exim@www1.ietf.org  Fri May 21 11:08: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 LAA07699
	for <ietf-archive@odin.ietf.org>; Fri, 21 May 2004 11:08: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 1BRBXu-0004GW-2G
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 11:02:50 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4LF2nbA016141
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 11:02:49 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRBPS-00029Q-8m; Fri, 21 May 2004 10:54:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRBJe-0000ns-KY
	for ietf@optimus.ietf.org; Fri, 21 May 2004 10:48: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 KAA06682
	for <ietf@ietf.org>; Fri, 21 May 2004 10:47: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 1BRBJW-0005uE-7N
	for ietf@ietf.org; Fri, 21 May 2004 10:47:58 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRBIr-0005fo-00
	for ietf@ietf.org; Fri, 21 May 2004 10:47:17 -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 1BRBHr-0005M2-00
	for ietf@ietf.org; Fri, 21 May 2004 10:46:15 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: respect privacy please !
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Date: Fri, 21 May 2004 07:45:44 -0700
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B0DB133@server2003.arneill-py.sacramento.ca.us>
Thread-Topic: respect privacy please !
thread-index: AcQ/MQ2sYCaX2jNfQMKrOLPGIsd0BQAEF2kQ
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Jordi Palet Martinez" <jordi.palet@consulintel.es>, <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

> JORDI PALET MARTINEZ wrote:
> I've already raised this some time ago, same as other
> people did, but I still see my name being published,
> w/o my consent, in the list of attendees.

Besides the fact that it is done without your consent, is there
something fundamentally wrong with it in your view? I don't care if the
IETF lists my name, is there a reason I should?

> This is not acceptable, we should have the option to
> choose if we want to have our name published or not
> when we do the registration.

It appears this will not happen.

Michel.


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



From ietf-admin@ietf.org  Fri May 21 11:17:57 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08276
	for <ietf-archive@ietf.org>; Fri, 21 May 2004 11:17: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 1BRBmZ-0004pV-Kh
	for ietf-archive@ietf.org; Fri, 21 May 2004 11:17:59 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRBld-0004a6-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 11:17:02 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRBkr-0004K1-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 11:16:13 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRBZ6-0004eZ-FY; Fri, 21 May 2004 11:04:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRBT9-0002tc-CB
	for ietf@optimus.ietf.org; Fri, 21 May 2004 10:57: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 KAA07092
	for <ietf@ietf.org>; Fri, 21 May 2004 10:57: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 1BRBT6-0000Em-FH
	for ietf@ietf.org; Fri, 21 May 2004 10:57:52 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRBS5-00001M-00
	for ietf@ietf.org; Fri, 21 May 2004 10:56:49 -0400
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRBRC-0007cC-00
	for ietf@ietf.org; Fri, 21 May 2004 10:55:55 -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 i4LEtsWE006786
	for <ietf@ietf.org>; Fri, 21 May 2004 15:55:54 +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 PAA03215
	for <ietf@ietf.org>; Fri, 21 May 2004 15:55:50 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id i4LEtok25916
	for ietf@ietf.org; Fri, 21 May 2004 15:55:50 +0100
Date: Fri, 21 May 2004 15:55:50 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: ietf@ietf.org
Subject: Re: respect privacy please !
Message-ID: <20040521145550.GB25670@login.ecs.soton.ac.uk>
References: <0fa701c43f26$2939af90$8700000a@consulintel.es> <C920A0255CBCAF05FBEE6AC9@scan.jck.com> <40AE0C8C.6CFD72A3@swin.edu.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <40AE0C8C.6CFD72A3@swin.edu.au>
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 Sat, May 22, 2004 at 12:05:00AM +1000, grenville armitage wrote:
> 
> This could be solved by the IETF insisting that consent is required
> before attendance. I, like John, do not believe it is acceptable for
> the IETF meetings to be populated by anonymous attendees.

The issue is someone knowing where I am for a week, in advance.

Harald's suggestion of releasing the list post-event is an improvement...

> (The irony of your email address being public on this list is
> not lost.)

Maybe I'm using an alias... I could be Jim Fleming :)

Tim

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


From ietf-admin@ietf.org  Fri May 21 11:20:49 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08461
	for <ietf-archive@ietf.org>; Fri, 21 May 2004 11: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 1BRBpK-0005Y1-NN
	for ietf-archive@ietf.org; Fri, 21 May 2004 11:20:50 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRBoV-0005KD-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 11:20:01 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRBo0-00055Y-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 11:19:28 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRBa2-0004sf-Vc; Fri, 21 May 2004 11:05:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRBWo-0003rv-9k
	for ietf@optimus.ietf.org; Fri, 21 May 2004 11:01: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 LAA07389
	for <ietf@ietf.org>; Fri, 21 May 2004 11:01:37 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRBWl-00017i-JG
	for ietf@ietf.org; Fri, 21 May 2004 11:01:39 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRBVs-0000tm-00
	for ietf@ietf.org; Fri, 21 May 2004 11:00:45 -0400
Received: from mail.consulintel.es ([213.172.48.142] helo=consulintel.es)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRBVF-0000fC-00
	for ietf@ietf.org; Fri, 21 May 2004 11:00:05 -0400
Received: from consulintel02 ([217.126.187.160])
	(authenticated user jordi.palet@consulintel.es)
	by consulintel.es (consulintel.es [127.0.0.1])
	(MDaemon.PRO.v7.0.1.R)
	with ESMTP id md50000111990.msg
	for <ietf@ietf.org>; Fri, 21 May 2004 17:00:46 +0200
Message-ID: <126b01c43f44$29e2c530$8700000a@consulintel.es>
Reply-To: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
From: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
References: <0fa701c43f26$2939af90$8700000a@consulintel.es> <C920A0255CBCAF05FBEE6AC9@scan.jck.com>
Subject: Re: respect privacy please !
Date: Fri, 21 May 2004 16:59:04 +0200
Organization: Consulintel
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Spam-Processed: consulintel.es, Fri, 21 May 2004 17:00:46 +0200
	(not processed: message from valid local sender)
X-MDRemoteIP: 217.126.187.160
X-Return-Path: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
X-MDAV-Processed: consulintel.es, Fri, 21 May 2004 17:00:47 +0200
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.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable

Hi John,

I actually (myself) have no problem to have my name published, my complain was somehow an indirect one ... because what is surprising is that when we had this type of discussion several times, no solution or decision is publicly provided. That's really annoying. We aren't here volunteering with our time and resources to provide our inputs and then being ignored, at least not most of us, I guess. So the openness of the process is already broken not taking decisions after the discussions :-(

Also is interesting that even when I typed it correctly, is now incorrectly mistyped in the attendee list, what just adds distrust to the process looking manual and prone to errors.

I also agree with the need of openness in the process, BUT the IETF has not any right to infringe the laws/regulations even if the openness is so important. Just imagine that a given country decides to block because something like this (not complying the local laws, that in this case are very common at least as I know in Europe), the www.ietf.org or even the mail exploders on that domain. It will be much worst !

Despite this, I think you provide a very good solution for this with your suggested boilerplate. Probably this is the minimum legal one that we should have. We like it or not, we live in a world with rules, that we must accept (or change). In part the problem is probably that there is not a clear legal situation for a non-legal organization ... but that's another history.

The other good example is the IPv6 issue. As I recall, I saw (and even participated) in that debate a couple of times. Today I see no objective reason for not doing that, but we don't have a decision on that. Is that good ? Is this what we expect for an open process ?

Regards,
Jordi

----- Original Message -----=20
From: "John C Klensin" <john-ietf@jck.com>
To: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
Cc: <ietf@ietf.org>
Sent: Friday, May 21, 2004 3:34 PM
Subject: Re: respect privacy please !


> Jordi,
>=20
> This has been discussed several times before.  While I share=20
> your discomfort, IETF is not some "conference" you might be=20
> attending.  It is very difficult to claim that one has an open=20
> standards process when some participants are permitted attend=20
> meetings and, potentially, influence decisions while being=20
> hidden or anonymous. We do not discourage people from lurking=20
> quietly on mailing lists. But I think that, as soon as anyone=20
> more actively participates -- whether by posting to mailing=20
> lists or attending meetings (especially since the latter is a=20
> qualification for Nomcom membership that must be publicly=20
> verifiable) -- then I think desires for privacy have to yield to=20
> the importance of trust in the IETF community and its processes.=20
> As with IPR disclosures, if one can't accept the rules, the best=20
> option is to decide to not play.
>=20
> Out of curiosity, would you feed better about this if the=20
> boilerplate you need to page through to register said,=20
> explicitly, "if you don't want your name to be made public as a=20
> registrant and participant, please don't register or attend" or=20
> "by registering, you consent..."?  I don't have any control over=20
> the text or decisions but assume that, if lots of people wanted=20
> such language to eliminate any misunderstandings about whether=20
> you had consented, the IESG and Secretariat would probably agree=20
> to add it.
>=20
> At least the Secretariat no longer feels a need to publish email=20
> addresses with the list of registrants :-(
>=20
>      best,
>       john
>=20
> p.s. Note that the above is purely a process and moral position.=20
> There is, I'm sure, a legal one that parallels it, but I'd=20
> rather not go there --and set off a wave of amateur lawyering--=20
> if we can help it.
>=20
>=20
>=20
> --On Friday, 21 May, 2004 13:24 +0200 JORDI PALET MARTINEZ=20
> <jordi.palet@consulintel.es> wrote:
>=20
> > Hi,
> >
> > I've already raised this some time ago, same as other people
> > did, but I still see my name being published, w/o my consent,
> > in the list of attendees.
> >
> > This is not acceptable, we should have the option to choose if
> > we want to have our name published or not when we do the
> > registration.
> >
> > I will also like to get some response about the time frame to
> > get the IETF sites IPv6-enabled. If there is any problem for
> > doing that, I already volunteered to host a mirror.
> >
> > Regards,
> > Jordi
>=20
>=20
>=20
>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>=20


**********************************
Madrid 2003 Global IPv6 Summit
Presentations and videos on line at:
http://www.ipv6-es.com

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.




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


From exim@www1.ietf.org  Fri May 21 11:26: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 LAA08709
	for <ietf-archive@odin.ietf.org>; Fri, 21 May 2004 11:26: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 1BRBkh-0007RC-IV
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 11:16:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4LFG3Ix028446
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 11:16:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRBZ6-0004eZ-FY; Fri, 21 May 2004 11:04:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRBT9-0002tc-CB
	for ietf@optimus.ietf.org; Fri, 21 May 2004 10:57: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 KAA07092
	for <ietf@ietf.org>; Fri, 21 May 2004 10:57: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 1BRBT6-0000Em-FH
	for ietf@ietf.org; Fri, 21 May 2004 10:57:52 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRBS5-00001M-00
	for ietf@ietf.org; Fri, 21 May 2004 10:56:49 -0400
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRBRC-0007cC-00
	for ietf@ietf.org; Fri, 21 May 2004 10:55:55 -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 i4LEtsWE006786
	for <ietf@ietf.org>; Fri, 21 May 2004 15:55:54 +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 PAA03215
	for <ietf@ietf.org>; Fri, 21 May 2004 15:55:50 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id i4LEtok25916
	for ietf@ietf.org; Fri, 21 May 2004 15:55:50 +0100
Date: Fri, 21 May 2004 15:55:50 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: ietf@ietf.org
Subject: Re: respect privacy please !
Message-ID: <20040521145550.GB25670@login.ecs.soton.ac.uk>
References: <0fa701c43f26$2939af90$8700000a@consulintel.es> <C920A0255CBCAF05FBEE6AC9@scan.jck.com> <40AE0C8C.6CFD72A3@swin.edu.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <40AE0C8C.6CFD72A3@swin.edu.au>
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 Sat, May 22, 2004 at 12:05:00AM +1000, grenville armitage wrote:
> 
> This could be solved by the IETF insisting that consent is required
> before attendance. I, like John, do not believe it is acceptable for
> the IETF meetings to be populated by anonymous attendees.

The issue is someone knowing where I am for a week, in advance.

Harald's suggestion of releasing the list post-event is an improvement...

> (The irony of your email address being public on this list is
> not lost.)

Maybe I'm using an alias... I could be Jim Fleming :)

Tim

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



From exim@www1.ietf.org  Fri May 21 11:26: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 LAA08727
	for <ietf-archive@odin.ietf.org>; Fri, 21 May 2004 11:26: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 1BRBo0-0008AT-Fv
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 11:19:28 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4LFJSiC031393
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 11:19:28 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRBa2-0004sf-Vc; Fri, 21 May 2004 11:05:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRBWo-0003rv-9k
	for ietf@optimus.ietf.org; Fri, 21 May 2004 11:01: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 LAA07389
	for <ietf@ietf.org>; Fri, 21 May 2004 11:01:37 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRBWl-00017i-JG
	for ietf@ietf.org; Fri, 21 May 2004 11:01:39 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRBVs-0000tm-00
	for ietf@ietf.org; Fri, 21 May 2004 11:00:45 -0400
Received: from mail.consulintel.es ([213.172.48.142] helo=consulintel.es)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRBVF-0000fC-00
	for ietf@ietf.org; Fri, 21 May 2004 11:00:05 -0400
Received: from consulintel02 ([217.126.187.160])
	(authenticated user jordi.palet@consulintel.es)
	by consulintel.es (consulintel.es [127.0.0.1])
	(MDaemon.PRO.v7.0.1.R)
	with ESMTP id md50000111990.msg
	for <ietf@ietf.org>; Fri, 21 May 2004 17:00:46 +0200
Message-ID: <126b01c43f44$29e2c530$8700000a@consulintel.es>
Reply-To: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
From: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
References: <0fa701c43f26$2939af90$8700000a@consulintel.es> <C920A0255CBCAF05FBEE6AC9@scan.jck.com>
Subject: Re: respect privacy please !
Date: Fri, 21 May 2004 16:59:04 +0200
Organization: Consulintel
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Spam-Processed: consulintel.es, Fri, 21 May 2004 17:00:46 +0200
	(not processed: message from valid local sender)
X-MDRemoteIP: 217.126.187.160
X-Return-Path: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
X-MDAV-Processed: consulintel.es, Fri, 21 May 2004 17:00:47 +0200
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: 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

Hi John,

I actually (myself) have no problem to have my name published, my complain was somehow an indirect one ... because what is surprising is that when we had this type of discussion several times, no solution or decision is publicly provided. That's really annoying. We aren't here volunteering with our time and resources to provide our inputs and then being ignored, at least not most of us, I guess. So the openness of the process is already broken not taking decisions after the discussions :-(

Also is interesting that even when I typed it correctly, is now incorrectly mistyped in the attendee list, what just adds distrust to the process looking manual and prone to errors.

I also agree with the need of openness in the process, BUT the IETF has not any right to infringe the laws/regulations even if the openness is so important. Just imagine that a given country decides to block because something like this (not complying the local laws, that in this case are very common at least as I know in Europe), the www.ietf.org or even the mail exploders on that domain. It will be much worst !

Despite this, I think you provide a very good solution for this with your suggested boilerplate. Probably this is the minimum legal one that we should have. We like it or not, we live in a world with rules, that we must accept (or change). In part the problem is probably that there is not a clear legal situation for a non-legal organization ... but that's another history.

The other good example is the IPv6 issue. As I recall, I saw (and even participated) in that debate a couple of times. Today I see no objective reason for not doing that, but we don't have a decision on that. Is that good ? Is this what we expect for an open process ?

Regards,
Jordi

----- Original Message -----=20
From: "John C Klensin" <john-ietf@jck.com>
To: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
Cc: <ietf@ietf.org>
Sent: Friday, May 21, 2004 3:34 PM
Subject: Re: respect privacy please !


> Jordi,
>=20
> This has been discussed several times before.  While I share=20
> your discomfort, IETF is not some "conference" you might be=20
> attending.  It is very difficult to claim that one has an open=20
> standards process when some participants are permitted attend=20
> meetings and, potentially, influence decisions while being=20
> hidden or anonymous. We do not discourage people from lurking=20
> quietly on mailing lists. But I think that, as soon as anyone=20
> more actively participates -- whether by posting to mailing=20
> lists or attending meetings (especially since the latter is a=20
> qualification for Nomcom membership that must be publicly=20
> verifiable) -- then I think desires for privacy have to yield to=20
> the importance of trust in the IETF community and its processes.=20
> As with IPR disclosures, if one can't accept the rules, the best=20
> option is to decide to not play.
>=20
> Out of curiosity, would you feed better about this if the=20
> boilerplate you need to page through to register said,=20
> explicitly, "if you don't want your name to be made public as a=20
> registrant and participant, please don't register or attend" or=20
> "by registering, you consent..."?  I don't have any control over=20
> the text or decisions but assume that, if lots of people wanted=20
> such language to eliminate any misunderstandings about whether=20
> you had consented, the IESG and Secretariat would probably agree=20
> to add it.
>=20
> At least the Secretariat no longer feels a need to publish email=20
> addresses with the list of registrants :-(
>=20
>      best,
>       john
>=20
> p.s. Note that the above is purely a process and moral position.=20
> There is, I'm sure, a legal one that parallels it, but I'd=20
> rather not go there --and set off a wave of amateur lawyering--=20
> if we can help it.
>=20
>=20
>=20
> --On Friday, 21 May, 2004 13:24 +0200 JORDI PALET MARTINEZ=20
> <jordi.palet@consulintel.es> wrote:
>=20
> > Hi,
> >
> > I've already raised this some time ago, same as other people
> > did, but I still see my name being published, w/o my consent,
> > in the list of attendees.
> >
> > This is not acceptable, we should have the option to choose if
> > we want to have our name published or not when we do the
> > registration.
> >
> > I will also like to get some response about the time frame to
> > get the IETF sites IPv6-enabled. If there is any problem for
> > doing that, I already volunteered to host a mirror.
> >
> > Regards,
> > Jordi
>=20
>=20
>=20
>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>=20


**********************************
Madrid 2003 Global IPv6 Summit
Presentations and videos on line at:
http://www.ipv6-es.com

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.




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



From ietf-admin@ietf.org  Fri May 21 11:41: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 LAA09631
	for <ietf-archive@ietf.org>; Fri, 21 May 2004 11:41: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 1BRC9O-0006mN-2B
	for ietf-archive@ietf.org; Fri, 21 May 2004 11:41:34 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRC8U-0006jA-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 11:40:39 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRC7X-0006gf-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 11:39:39 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRBrW-0000Fm-Dx; Fri, 21 May 2004 11:23:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRBgj-00069x-9s
	for ietf@optimus.ietf.org; Fri, 21 May 2004 11:11: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 LAA07942
	for <ietf@ietf.org>; Fri, 21 May 2004 11:11: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 1BRBgg-0003Oq-Ev
	for ietf@ietf.org; Fri, 21 May 2004 11:11:54 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRBff-0003AA-00
	for ietf@ietf.org; Fri, 21 May 2004 11:10:51 -0400
Received: from mail.consulintel.es ([213.172.48.142] helo=consulintel.es)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRBep-0002jm-00
	for ietf@ietf.org; Fri, 21 May 2004 11:09:59 -0400
Received: from consulintel02 ([217.126.187.160])
	(authenticated user jordi.palet@consulintel.es)
	by consulintel.es (consulintel.es [127.0.0.1])
	(MDaemon.PRO.v7.0.1.R)
	with ESMTP id md50000112021.msg
	for <ietf@ietf.org>; Fri, 21 May 2004 17:10:38 +0200
Message-ID: <128901c43f45$8b640de0$8700000a@consulintel.es>
Reply-To: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
From: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
References: <0fa701c43f26$2939af90$8700000a@consulintel.es> <335417014.1085122709@localhost>
Subject: Re: respect privacy please !
Date: Fri, 21 May 2004 17:08:47 +0200
Organization: Consulintel
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Spam-Processed: consulintel.es, Fri, 21 May 2004 17:10:38 +0200
	(not processed: message from valid local sender)
X-MDRemoteIP: 217.126.187.160
X-Return-Path: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
X-MDAV-Processed: consulintel.es, Fri, 21 May 2004 17:10:42 +0200
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

Hi Harald,

I'm not expert in legal stuff, but I think the European regulations (at least in Spain because I needed to learn this in order to host web sites with any kind of registration or list of people and comply with the law), there is no difference in publishing it before, during or after. Just can't be published w/o the consent of the participant.

>From a practical point of view, probably is good to do what John suggested, but alternatively also publishing only after the meetings will be a good protection for example to avoid a thief go to your home when you're in the IETF, as I recall somebody suggested was already happening in UK.

I don't think a legal requirement for our process can jump over the laws. Is like if we decide that we need to sacrifice one of us in every meeting to sign the minutes with human blood, while we know that killing some one is forbidden. Yes I know ... is a quite exaggerated example, but some times is the best way to show what is wrong ;-)

May be the 1st thing to do is to be really open in all the aspects, and that means clarifying our legal "situation", the terms under we take all the decisions, and so on.

Regards,
Jordi

----- Original Message -----=20
From: "Harald Tveit Alvestrand" <harald@alvestrand.no>
To: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>; <ietf@ietf.org>
Sent: Friday, May 21, 2004 3:58 PM
Subject: Re: respect privacy please !


>=20
>=20
> --On 21. mai 2004 13:24 +0200 JORDI PALET MARTINEZ=20
> <jordi.palet@consulintel.es> wrote:
>=20
> > Hi,
> >
> > I've already raised this some time ago, same as other people did, but I
> > still see my name being published, w/o my consent, in the list of
> > attendees.
> >
> > This is not acceptable, we should have the option to choose if we want to
> > have our name published or not when we do the registration.
>=20
> Jordi,
>=20
> are you objecting to having your name published *at all*, or having your=20
> name published *before the meeting*?
>=20
> The list of attendees (but not their contact info) is (according to the=20
> lawyers) a legal requirement for our way of doing business; it is part of=20
> the transparency requirement that it's possible to find out who was there.
>=20
>                       Harald
>=20
>=20
>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>=20


**********************************
Madrid 2003 Global IPv6 Summit
Presentations and videos on line at:
http://www.ipv6-es.com

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.




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


From exim@www1.ietf.org  Fri May 21 11:47:15 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 LAA10050
	for <ietf-archive@odin.ietf.org>; Fri, 21 May 2004 11:47:15 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRC7X-0004xL-H4
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 11:39:39 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4LFdd6B019051
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 11:39:39 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRBrW-0000Fm-Dx; Fri, 21 May 2004 11:23:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRBgj-00069x-9s
	for ietf@optimus.ietf.org; Fri, 21 May 2004 11:11: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 LAA07942
	for <ietf@ietf.org>; Fri, 21 May 2004 11:11: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 1BRBgg-0003Oq-Ev
	for ietf@ietf.org; Fri, 21 May 2004 11:11:54 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRBff-0003AA-00
	for ietf@ietf.org; Fri, 21 May 2004 11:10:51 -0400
Received: from mail.consulintel.es ([213.172.48.142] helo=consulintel.es)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRBep-0002jm-00
	for ietf@ietf.org; Fri, 21 May 2004 11:09:59 -0400
Received: from consulintel02 ([217.126.187.160])
	(authenticated user jordi.palet@consulintel.es)
	by consulintel.es (consulintel.es [127.0.0.1])
	(MDaemon.PRO.v7.0.1.R)
	with ESMTP id md50000112021.msg
	for <ietf@ietf.org>; Fri, 21 May 2004 17:10:38 +0200
Message-ID: <128901c43f45$8b640de0$8700000a@consulintel.es>
Reply-To: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
From: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
References: <0fa701c43f26$2939af90$8700000a@consulintel.es> <335417014.1085122709@localhost>
Subject: Re: respect privacy please !
Date: Fri, 21 May 2004 17:08:47 +0200
Organization: Consulintel
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Spam-Processed: consulintel.es, Fri, 21 May 2004 17:10:38 +0200
	(not processed: message from valid local sender)
X-MDRemoteIP: 217.126.187.160
X-Return-Path: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
X-MDAV-Processed: consulintel.es, Fri, 21 May 2004 17:10:42 +0200
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: 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

Hi Harald,

I'm not expert in legal stuff, but I think the European regulations (at least in Spain because I needed to learn this in order to host web sites with any kind of registration or list of people and comply with the law), there is no difference in publishing it before, during or after. Just can't be published w/o the consent of the participant.

>From a practical point of view, probably is good to do what John suggested, but alternatively also publishing only after the meetings will be a good protection for example to avoid a thief go to your home when you're in the IETF, as I recall somebody suggested was already happening in UK.

I don't think a legal requirement for our process can jump over the laws. Is like if we decide that we need to sacrifice one of us in every meeting to sign the minutes with human blood, while we know that killing some one is forbidden. Yes I know ... is a quite exaggerated example, but some times is the best way to show what is wrong ;-)

May be the 1st thing to do is to be really open in all the aspects, and that means clarifying our legal "situation", the terms under we take all the decisions, and so on.

Regards,
Jordi

----- Original Message -----=20
From: "Harald Tveit Alvestrand" <harald@alvestrand.no>
To: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>; <ietf@ietf.org>
Sent: Friday, May 21, 2004 3:58 PM
Subject: Re: respect privacy please !


>=20
>=20
> --On 21. mai 2004 13:24 +0200 JORDI PALET MARTINEZ=20
> <jordi.palet@consulintel.es> wrote:
>=20
> > Hi,
> >
> > I've already raised this some time ago, same as other people did, but I
> > still see my name being published, w/o my consent, in the list of
> > attendees.
> >
> > This is not acceptable, we should have the option to choose if we want to
> > have our name published or not when we do the registration.
>=20
> Jordi,
>=20
> are you objecting to having your name published *at all*, or having your=20
> name published *before the meeting*?
>=20
> The list of attendees (but not their contact info) is (according to the=20
> lawyers) a legal requirement for our way of doing business; it is part of=20
> the transparency requirement that it's possible to find out who was there.
>=20
>                       Harald
>=20
>=20
>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>=20


**********************************
Madrid 2003 Global IPv6 Summit
Presentations and videos on line at:
http://www.ipv6-es.com

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.




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



From exim@www1.ietf.org  Fri May 21 11:48: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 LAA10154
	for <ietf-archive@odin.ietf.org>; Fri, 21 May 2004 11:48: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 1BRCD4-0006jp-Kr
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 11:45:25 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4LFjMBM025882
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 11:45:22 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRBvM-0001dS-Jt; Fri, 21 May 2004 11:27:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRBqz-0000AF-Gq
	for ietf@optimus.ietf.org; Fri, 21 May 2004 11:22: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 LAA08518
	for <ietf@ietf.org>; Fri, 21 May 2004 11:22: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 1BRBqy-0005gV-Em
	for ietf@ietf.org; Fri, 21 May 2004 11:22:32 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRBqA-0005du-00
	for ietf@ietf.org; Fri, 21 May 2004 11:21:43 -0400
Received: from 1-1-2-20b.rny.sth.bostream.se ([82.182.132.65] helo=klapautius.it.su.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRBp7-0005WF-00
	for ietf@ietf.org; Fri, 21 May 2004 11:20:37 -0400
Received: from it.su.se (localhost.localdomain [127.0.0.1])
	by klapautius.it.su.se (8.11.6/8.11.6) with ESMTP id i4LFJEv11530;
	Fri, 21 May 2004 17:19:14 +0200
Message-ID: <40AE1DF2.1080809@it.su.se>
Date: Fri, 21 May 2004 17:19:14 +0200
From: Leif Johansson <leifj@it.su.se>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: sv, en, en-us
MIME-Version: 1.0
To: Tim Chown <tjc@ecs.soton.ac.uk>
CC: ietf@ietf.org
Subject: Re: respect privacy please !
References: <0fa701c43f26$2939af90$8700000a@consulintel.es> <C920A0255CBCAF05FBEE6AC9@scan.jck.com> <40AE0C8C.6CFD72A3@swin.edu.au> <20040521145550.GB25670@login.ecs.soton.ac.uk>
In-Reply-To: <20040521145550.GB25670@login.ecs.soton.ac.uk>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: 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


> 
> Maybe I'm using an alias... I could be Jim Fleming :)

Tim... Jim... the plot thickens!

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



From ietf-admin@ietf.org  Fri May 21 12:05: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 MAA10949
	for <ietf-archive@ietf.org>; Fri, 21 May 2004 12:05: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 1BRCWT-0000Lh-3S
	for ietf-archive@ietf.org; Fri, 21 May 2004 12:05:25 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRCTr-00007Q-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 12:02:44 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRCTF-00004i-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 12:02:05 -0400
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BRCTG-0008JY-Ao
	for ietf-archive@ietf.org; Fri, 21 May 2004 12:02:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRCEh-0007GL-G9; Fri, 21 May 2004 11:47:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRC2d-0003Jg-Bk
	for ietf@optimus.ietf.org; Fri, 21 May 2004 11:34: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 LAA09363
	for <ietf@ietf.org>; Fri, 21 May 2004 11:34: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 1BRC2c-0006UU-64
	for ietf@ietf.org; Fri, 21 May 2004 11:34:34 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRC1i-0006QT-00
	for ietf@ietf.org; Fri, 21 May 2004 11:33:39 -0400
Received: from cust.92.136.adsl.cistron.nl
	([195.64.92.136] helo=purgatory.unfix.org ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRC0n-0006OJ-00
	for ietf@ietf.org; Fri, 21 May 2004 11:32:41 -0400
Received: from localhost (localhost [127.0.0.1])
	by purgatory.unfix.org (Postfix) with ESMTP
	id E12B87FF0; Fri, 21 May 2004 17:32:37 +0200 (CEST)
Received: from purgatory.unfix.org ([127.0.0.1])
	by localhost (purgatory [127.0.0.1]) (amavisd-new, port 10024)
	with SMTP id 10347-31; Fri, 21 May 2004 17:32:24 +0200 (CEST)
Received: from [9.4.70.109] (pat.zurich.ibm.com [195.176.20.45])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by purgatory.unfix.org (Postfix) with ESMTP
	id 24F097F67; Fri, 21 May 2004 17:32:20 +0200 (CEST)
Subject: IPv6 for *.ietf.org services (Was: Re: respect privacy please !)
From: Jeroen Massar <jeroen@unfix.org>
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Cc: ietf@ietf.org
In-Reply-To: <126b01c43f44$29e2c530$8700000a@consulintel.es>
References: <0fa701c43f26$2939af90$8700000a@consulintel.es>
	 <C920A0255CBCAF05FBEE6AC9@scan.jck.com>
	 <126b01c43f44$29e2c530$8700000a@consulintel.es>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-XWh/5lDpZzSXcsq69d0F"
Organization: Unfix
Message-Id: <1085153528.22699.5746.camel@segesta.zurich.ibm.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.5 (1.4.5-7) 
Date: Fri, 21 May 2004 17:32:08 +0200
X-Virus-Scanned: purgatory.unfix.org - http://unfix.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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60


--=-XWh/5lDpZzSXcsq69d0F
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Fri, 2004-05-21 at 16:59, JORDI PALET MARTINEZ wrote:

<SNIP privacy talk>

> The other good example is the IPv6 issue. As I recall, I saw (and even pa=
rticipated)
> in that debate a couple of times. Today I see no objective reason for not=
 doing that,
> but we don't have a decision on that. Is that good ? Is this what we expe=
ct for an open process ?

I heared one reason that there is that the IETF servers don't have IPv6
(yet) is simply because their ISP/transit/upstream doesn't do it and
thus it makes it pretty impossible unfortunatly.
The software can cope with it without problem mind you.

For the web if you really want http://www.ietf.org.sixxs.org
et tada you are going through the proxy, thus one can read the website
and all of the related sites over IPv6 if you only have IPv6
connectivity, which is quite uncommon I guess, but could happen.

As for the rest of the services, namely SMTP, that needs connectivity.
It doesn't make much sense of setting up a 'external' mailer which
handles the mail over IPv6 and passes it over IPv4 to the real machines.
If you need that just make your own MX IPv4+IPv6 complaint, which I
think, certainly in the world of today is simply required.

Also remember that the roots haven't got any published, that is in the
'.' IPv6 DNS addresses thus running 100% IPv6 is unfortunatly not
possible yet due to these obstacles...

Greets,
 Jeroen


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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iD8DBQBAriD4KaooUjM+fCMRAh6GAJ9ATZQkKuSEGWc/5Io5Hi/aRJDOagCfXo9X
TcSCdgjxTBoL1+dz+mT70Vs=
=YyE5
-----END PGP SIGNATURE-----

--=-XWh/5lDpZzSXcsq69d0F--


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


From ietf-admin@ietf.org  Fri May 21 12:05: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 MAA10988
	for <ietf-archive@ietf.org>; Fri, 21 May 2004 12:05: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 1BRCWZ-0000NG-Th
	for ietf-archive@ietf.org; Fri, 21 May 2004 12:05:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRCTy-00008n-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 12:02:51 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRCTH-00004m-01
	for ietf-archive@ietf.org; Fri, 21 May 2004 12:02:07 -0400
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BRCMb-000859-L7
	for ietf-archive@ietf.org; Fri, 21 May 2004 11:55:13 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRCEf-0007Fw-ID; Fri, 21 May 2004 11:47:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRC1e-00032e-H9
	for ietf@optimus.ietf.org; Fri, 21 May 2004 11:33:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09327
	for <ietf@ietf.org>; Fri, 21 May 2004 11:33:31 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRC1d-0006Pn-EU
	for ietf@ietf.org; Fri, 21 May 2004 11:33:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRC0e-0006NQ-00
	for ietf@ietf.org; Fri, 21 May 2004 11:32:32 -0400
Received: from turing-police.cirt.vt.edu ([128.173.54.129] ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRBzx-0006Mp-00
	for ietf@ietf.org; Fri, 21 May 2004 11:31:49 -0400
Received: from turing-police.cc.vt.edu (IDENT:valdis@localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.13.0.Beta2/8.13.0.Beta2) with ESMTP id i4LFVlji027135;
	Fri, 21 May 2004 11:31:47 -0400
Message-Id: <200405211531.i4LFVlji027135@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Tim Chown <tjc@ecs.soton.ac.uk>
Cc: ietf@ietf.org
Subject: Re: respect privacy please ! 
In-Reply-To: Your message of "Fri, 21 May 2004 15:55:50 BST."
             <20040521145550.GB25670@login.ecs.soton.ac.uk> 
References: <0fa701c43f26$2939af90$8700000a@consulintel.es> <C920A0255CBCAF05FBEE6AC9@scan.jck.com> <40AE0C8C.6CFD72A3@swin.edu.au>
            <20040521145550.GB25670@login.ecs.soton.ac.uk>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1339079540P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Fri, 21 May 2004 11:31:47 -0400
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,NO_REAL_NAME autolearn=no 
	version=2.60

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

(Finally back after a prolonged sabbatical - last few months have been
too weird/hectic for me to do much of anything IETF-related)..

On Fri, 21 May 2004 15:55:50 BST, Tim Chown <tjc@ecs.soton.ac.uk>  said:
> On Sat, May 22, 2004 at 12:05:00AM +1000, grenville armitage wrote:
> > 
> > This could be solved by the IETF insisting that consent is required
> > before attendance. I, like John, do not believe it is acceptable for
> > the IETF meetings to be populated by anonymous attendees.
> 
> The issue is someone knowing where I am for a week, in advance.

It's amazing how many people, even on security-related mailing lists, are
surprised when this aspect of Out-of-Office replies is pointed out to them..

> Harald's suggestion of releasing the list post-event is an improvement...

I tend to concur here - I think a "The following people attended" list published
after the fact, with optional suppression of contact info and/or affiliation, is
sufficient to address the "openness" issue.  Whether suppression should be
opt-in or opt-out is debatable - I wouldn't have a problem with my e-mail
address and affiliation being listed in that context (even though I do have
issues with it elsewhere), but I can sympathize with those who feel otherwise.

> Maybe I'm using an alias... I could be Jim Fleming :)

Waving my patent-pending kook-o-meter over your email and Jim's produces
different characteristic patterns... so I doubt it. ;)

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

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

iD8DBQFAriDicC3lWbTT17ARAjW1AJ9Lk90NMC++Fj2YeTqUrjqsu61PtwCcDKVy
YCLPEd4DHqmFb16h14M//G8=
=PVFf
-----END PGP SIGNATURE-----

--==_Exmh_-1339079540P--

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


From ietf-admin@ietf.org  Fri May 21 12:06: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 MAA11222
	for <ietf-archive@ietf.org>; Fri, 21 May 2004 12:06: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 1BRCXO-0000Uk-4f
	for ietf-archive@ietf.org; Fri, 21 May 2004 12:06:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRCUm-0000HL-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 12:03:41 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRCTO-00004i-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 12:02:14 -0400
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BRCD7-0007qi-3e
	for ietf-archive@ietf.org; Fri, 21 May 2004 11:45:25 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRBvM-0001dS-Jt; Fri, 21 May 2004 11:27:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRBqz-0000AF-Gq
	for ietf@optimus.ietf.org; Fri, 21 May 2004 11:22: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 LAA08518
	for <ietf@ietf.org>; Fri, 21 May 2004 11:22: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 1BRBqy-0005gV-Em
	for ietf@ietf.org; Fri, 21 May 2004 11:22:32 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRBqA-0005du-00
	for ietf@ietf.org; Fri, 21 May 2004 11:21:43 -0400
Received: from 1-1-2-20b.rny.sth.bostream.se ([82.182.132.65] helo=klapautius.it.su.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRBp7-0005WF-00
	for ietf@ietf.org; Fri, 21 May 2004 11:20:37 -0400
Received: from it.su.se (localhost.localdomain [127.0.0.1])
	by klapautius.it.su.se (8.11.6/8.11.6) with ESMTP id i4LFJEv11530;
	Fri, 21 May 2004 17:19:14 +0200
Message-ID: <40AE1DF2.1080809@it.su.se>
Date: Fri, 21 May 2004 17:19:14 +0200
From: Leif Johansson <leifj@it.su.se>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: sv, en, en-us
MIME-Version: 1.0
To: Tim Chown <tjc@ecs.soton.ac.uk>
CC: ietf@ietf.org
Subject: Re: respect privacy please !
References: <0fa701c43f26$2939af90$8700000a@consulintel.es> <C920A0255CBCAF05FBEE6AC9@scan.jck.com> <40AE0C8C.6CFD72A3@swin.edu.au> <20040521145550.GB25670@login.ecs.soton.ac.uk>
In-Reply-To: <20040521145550.GB25670@login.ecs.soton.ac.uk>
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=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit


> 
> Maybe I'm using an alias... I could be Jim Fleming :)

Tim... Jim... the plot thickens!

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


From exim@www1.ietf.org  Fri May 21 12:07:26 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 MAA11313
	for <ietf-archive@odin.ietf.org>; Fri, 21 May 2004 12:07: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 1BRCMa-0000pY-3R
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 11:55:12 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4LFtCKg003192
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 11:55:12 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRCEf-0007Fw-ID; Fri, 21 May 2004 11:47:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRC1e-00032e-H9
	for ietf@optimus.ietf.org; Fri, 21 May 2004 11:33:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09327
	for <ietf@ietf.org>; Fri, 21 May 2004 11:33:31 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRC1d-0006Pn-EU
	for ietf@ietf.org; Fri, 21 May 2004 11:33:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRC0e-0006NQ-00
	for ietf@ietf.org; Fri, 21 May 2004 11:32:32 -0400
Received: from turing-police.cirt.vt.edu ([128.173.54.129] ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRBzx-0006Mp-00
	for ietf@ietf.org; Fri, 21 May 2004 11:31:49 -0400
Received: from turing-police.cc.vt.edu (IDENT:valdis@localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.13.0.Beta2/8.13.0.Beta2) with ESMTP id i4LFVlji027135;
	Fri, 21 May 2004 11:31:47 -0400
Message-Id: <200405211531.i4LFVlji027135@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Tim Chown <tjc@ecs.soton.ac.uk>
Cc: ietf@ietf.org
Subject: Re: respect privacy please ! 
In-Reply-To: Your message of "Fri, 21 May 2004 15:55:50 BST."
             <20040521145550.GB25670@login.ecs.soton.ac.uk> 
References: <0fa701c43f26$2939af90$8700000a@consulintel.es> <C920A0255CBCAF05FBEE6AC9@scan.jck.com> <40AE0C8C.6CFD72A3@swin.edu.au>
            <20040521145550.GB25670@login.ecs.soton.ac.uk>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_-1339079540P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Fri, 21 May 2004 11:31:47 -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.4 required=5.0 tests=AWL,NO_REAL_NAME 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>

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

(Finally back after a prolonged sabbatical - last few months have been
too weird/hectic for me to do much of anything IETF-related)..

On Fri, 21 May 2004 15:55:50 BST, Tim Chown <tjc@ecs.soton.ac.uk>  said:
> On Sat, May 22, 2004 at 12:05:00AM +1000, grenville armitage wrote:
> > 
> > This could be solved by the IETF insisting that consent is required
> > before attendance. I, like John, do not believe it is acceptable for
> > the IETF meetings to be populated by anonymous attendees.
> 
> The issue is someone knowing where I am for a week, in advance.

It's amazing how many people, even on security-related mailing lists, are
surprised when this aspect of Out-of-Office replies is pointed out to them..

> Harald's suggestion of releasing the list post-event is an improvement...

I tend to concur here - I think a "The following people attended" list published
after the fact, with optional suppression of contact info and/or affiliation, is
sufficient to address the "openness" issue.  Whether suppression should be
opt-in or opt-out is debatable - I wouldn't have a problem with my e-mail
address and affiliation being listed in that context (even though I do have
issues with it elsewhere), but I can sympathize with those who feel otherwise.

> Maybe I'm using an alias... I could be Jim Fleming :)

Waving my patent-pending kook-o-meter over your email and Jim's produces
different characteristic patterns... so I doubt it. ;)

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

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

iD8DBQFAriDicC3lWbTT17ARAjW1AJ9Lk90NMC++Fj2YeTqUrjqsu61PtwCcDKVy
YCLPEd4DHqmFb16h14M//G8=
=PVFf
-----END PGP SIGNATURE-----

--==_Exmh_-1339079540P--

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



From ietf-admin@ietf.org  Fri May 21 12:07:46 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11397
	for <ietf-archive@ietf.org>; Fri, 21 May 2004 12:07:46 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRCYm-0000jj-Gl
	for ietf-archive@ietf.org; Fri, 21 May 2004 12:07:48 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRCXU-0000W5-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 12:06:29 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRCUq-0000I6-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 12:03:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRCEn-0007Hl-2s; Fri, 21 May 2004 11:47:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRC8V-0005EZ-Gy
	for ietf@optimus.ietf.org; Fri, 21 May 2004 11:40:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09602
	for <ietf@ietf.org>; Fri, 21 May 2004 11:40: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 1BRC8U-0006j5-EC
	for ietf@ietf.org; Fri, 21 May 2004 11:40:38 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRC7X-0006gc-00
	for ietf@ietf.org; Fri, 21 May 2004 11:39:40 -0400
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRC6r-0006eh-00
	for ietf@ietf.org; Fri, 21 May 2004 11:38:57 -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 i4LFcvWE007652
	for <ietf@ietf.org>; Fri, 21 May 2004 16:38:57 +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 QAA05594
	for <ietf@ietf.org>; Fri, 21 May 2004 16:38:56 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id i4LFcuS26883
	for ietf@ietf.org; Fri, 21 May 2004 16:38:56 +0100
Date: Fri, 21 May 2004 16:38:56 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: ietf@ietf.org
Subject: Re: respect privacy please !
Message-ID: <20040521153856.GF25670@login.ecs.soton.ac.uk>
References: <0fa701c43f26$2939af90$8700000a@consulintel.es> <C920A0255CBCAF05FBEE6AC9@scan.jck.com> <40AE0C8C.6CFD72A3@swin.edu.au> <20040521145550.GB25670@login.ecs.soton.ac.uk> <970C9F77980BFAC803543C7D@scan.jck.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <970C9F77980BFAC803543C7D@scan.jck.com>
User-Agent: Mutt/1.4i
X-MailScanner-Information: Please contact helpdesk@ecs.soton.ac.uk for more information
X-ECS-MailScanner: Found to be clean
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, May 21, 2004 at 11:33:14AM -0400, John C Klensin wrote:
> 
> However, before we say "that is a wonderful idea" (or not), 
> let's remember the substance of several of the "IETF 
> administration" notes and documents that have been circulated in 
> the last several months.  If I understand those materials and 
> ...

I appreciate the IETF's resource issues.

But just block web access to the registration list page until 8th August,
the data is still there, just noone can publicly see it?   That doesn't
take long to do (a few minutes).

If people are suspicious, publish a hash of the list or something.

> having _my_ name and payment status listed -- it provides an 
> easy way for me to check on whether I've registered and paid or 
> whether I let it fall through the cracks.  

Fair point, but you get an email confirmation?

Tim

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


From exim@www1.ietf.org  Fri May 21 12:28:18 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 MAA12542
	for <ietf-archive@odin.ietf.org>; Fri, 21 May 2004 12:28: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 1BRCT8-0002Y7-Mr
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 12:02:01 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4LG1wMS009795
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 12:01:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRCEh-0007GL-G9; Fri, 21 May 2004 11:47:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRC2d-0003Jg-Bk
	for ietf@optimus.ietf.org; Fri, 21 May 2004 11:34: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 LAA09363
	for <ietf@ietf.org>; Fri, 21 May 2004 11:34: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 1BRC2c-0006UU-64
	for ietf@ietf.org; Fri, 21 May 2004 11:34:34 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRC1i-0006QT-00
	for ietf@ietf.org; Fri, 21 May 2004 11:33:39 -0400
Received: from cust.92.136.adsl.cistron.nl
	([195.64.92.136] helo=purgatory.unfix.org ident=postfix)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRC0n-0006OJ-00
	for ietf@ietf.org; Fri, 21 May 2004 11:32:41 -0400
Received: from localhost (localhost [127.0.0.1])
	by purgatory.unfix.org (Postfix) with ESMTP
	id E12B87FF0; Fri, 21 May 2004 17:32:37 +0200 (CEST)
Received: from purgatory.unfix.org ([127.0.0.1])
	by localhost (purgatory [127.0.0.1]) (amavisd-new, port 10024)
	with SMTP id 10347-31; Fri, 21 May 2004 17:32:24 +0200 (CEST)
Received: from [9.4.70.109] (pat.zurich.ibm.com [195.176.20.45])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by purgatory.unfix.org (Postfix) with ESMTP
	id 24F097F67; Fri, 21 May 2004 17:32:20 +0200 (CEST)
Subject: IPv6 for *.ietf.org services (Was: Re: respect privacy please !)
From: Jeroen Massar <jeroen@unfix.org>
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Cc: ietf@ietf.org
In-Reply-To: <126b01c43f44$29e2c530$8700000a@consulintel.es>
References: <0fa701c43f26$2939af90$8700000a@consulintel.es>
	 <C920A0255CBCAF05FBEE6AC9@scan.jck.com>
	 <126b01c43f44$29e2c530$8700000a@consulintel.es>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-XWh/5lDpZzSXcsq69d0F"
Organization: Unfix
Message-Id: <1085153528.22699.5746.camel@segesta.zurich.ibm.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.5 (1.4.5-7) 
Date: Fri, 21 May 2004 17:32:08 +0200
X-Virus-Scanned: purgatory.unfix.org - http://unfix.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: 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>


--=-XWh/5lDpZzSXcsq69d0F
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Fri, 2004-05-21 at 16:59, JORDI PALET MARTINEZ wrote:

<SNIP privacy talk>

> The other good example is the IPv6 issue. As I recall, I saw (and even pa=
rticipated)
> in that debate a couple of times. Today I see no objective reason for not=
 doing that,
> but we don't have a decision on that. Is that good ? Is this what we expe=
ct for an open process ?

I heared one reason that there is that the IETF servers don't have IPv6
(yet) is simply because their ISP/transit/upstream doesn't do it and
thus it makes it pretty impossible unfortunatly.
The software can cope with it without problem mind you.

For the web if you really want http://www.ietf.org.sixxs.org
et tada you are going through the proxy, thus one can read the website
and all of the related sites over IPv6 if you only have IPv6
connectivity, which is quite uncommon I guess, but could happen.

As for the rest of the services, namely SMTP, that needs connectivity.
It doesn't make much sense of setting up a 'external' mailer which
handles the mail over IPv6 and passes it over IPv4 to the real machines.
If you need that just make your own MX IPv4+IPv6 complaint, which I
think, certainly in the world of today is simply required.

Also remember that the roots haven't got any published, that is in the
'.' IPv6 DNS addresses thus running 100% IPv6 is unfortunatly not
possible yet due to these obstacles...

Greets,
 Jeroen


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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iD8DBQBAriD4KaooUjM+fCMRAh6GAJ9ATZQkKuSEGWc/5Io5Hi/aRJDOagCfXo9X
TcSCdgjxTBoL1+dz+mT70Vs=
=YyE5
-----END PGP SIGNATURE-----

--=-XWh/5lDpZzSXcsq69d0F--


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



From exim@www1.ietf.org  Fri May 21 12:28:31 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 MAA12597
	for <ietf-archive@odin.ietf.org>; Fri, 21 May 2004 12:28: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 1BRCUr-0003D8-1b
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 12:03:45 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4LG3jRx012327
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 12:03:45 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRCEn-0007Hl-2s; Fri, 21 May 2004 11:47:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRC8V-0005EZ-Gy
	for ietf@optimus.ietf.org; Fri, 21 May 2004 11:40:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09602
	for <ietf@ietf.org>; Fri, 21 May 2004 11:40: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 1BRC8U-0006j5-EC
	for ietf@ietf.org; Fri, 21 May 2004 11:40:38 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRC7X-0006gc-00
	for ietf@ietf.org; Fri, 21 May 2004 11:39:40 -0400
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRC6r-0006eh-00
	for ietf@ietf.org; Fri, 21 May 2004 11:38:57 -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 i4LFcvWE007652
	for <ietf@ietf.org>; Fri, 21 May 2004 16:38:57 +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 QAA05594
	for <ietf@ietf.org>; Fri, 21 May 2004 16:38:56 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id i4LFcuS26883
	for ietf@ietf.org; Fri, 21 May 2004 16:38:56 +0100
Date: Fri, 21 May 2004 16:38:56 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: ietf@ietf.org
Subject: Re: respect privacy please !
Message-ID: <20040521153856.GF25670@login.ecs.soton.ac.uk>
References: <0fa701c43f26$2939af90$8700000a@consulintel.es> <C920A0255CBCAF05FBEE6AC9@scan.jck.com> <40AE0C8C.6CFD72A3@swin.edu.au> <20040521145550.GB25670@login.ecs.soton.ac.uk> <970C9F77980BFAC803543C7D@scan.jck.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <970C9F77980BFAC803543C7D@scan.jck.com>
User-Agent: Mutt/1.4i
X-MailScanner-Information: Please contact helpdesk@ecs.soton.ac.uk for more information
X-ECS-MailScanner: Found to be clean
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=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, May 21, 2004 at 11:33:14AM -0400, John C Klensin wrote:
> 
> However, before we say "that is a wonderful idea" (or not), 
> let's remember the substance of several of the "IETF 
> administration" notes and documents that have been circulated in 
> the last several months.  If I understand those materials and 
> ...

I appreciate the IETF's resource issues.

But just block web access to the registration list page until 8th August,
the data is still there, just noone can publicly see it?   That doesn't
take long to do (a few minutes).

If people are suspicious, publish a hash of the list or something.

> having _my_ name and payment status listed -- it provides an 
> easy way for me to check on whether I've registered and paid or 
> whether I let it fall through the cracks.  

Fair point, but you get an email confirmation?

Tim

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



From ietf-admin@ietf.org  Fri May 21 12:31:01 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12869
	for <ietf-archive@ietf.org>; Fri, 21 May 2004 12: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 1BRCvH-00023K-6U
	for ietf-archive@ietf.org; Fri, 21 May 2004 12:31:03 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRCuO-0001xJ-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 12:30:08 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRCte-0001qh-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 12:29:22 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRCY4-00040j-0s; Fri, 21 May 2004 12:07:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRCKC-0000Wq-E0
	for ietf@optimus.ietf.org; Fri, 21 May 2004 11:52:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10378
	for <ietf@ietf.org>; Fri, 21 May 2004 11:52: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 1BRCKB-0007QN-6t
	for ietf@ietf.org; Fri, 21 May 2004 11:52:43 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRCJG-0007Nt-00
	for ietf@ietf.org; Fri, 21 May 2004 11:51:46 -0400
Received: from carwash.centive.com ([65.220.90.249])
	by ietf-mx with smtp (Exim 4.12)
	id 1BRCIw-0007L3-00
	for ietf@ietf.org; Fri, 21 May 2004 11:51:26 -0400
Received: from minglewood.incentivesystems.com ([10.10.30.25])
 by carwash.centive.com (SAVSMTP 3.1.3.37) with SMTP id M2004052111530429060
 for <ietf@ietf.org>; Fri, 21 May 2004 11:53:11 -0400
Received: from [10.10.48.119] ([10.10.48.119]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(6.0.3790.0);
	 Fri, 21 May 2004 11:46:59 -0400
Message-ID: <40AE2473.3080706@centive.com>
Date: Fri, 21 May 2004 11:46:59 -0400
From: John Stracke <jstracke@centive.com>
User-Agent: Mozilla Thunderbird 0.6 (Windows/20040502)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: respect privacy please !
References: <0fa701c43f26$2939af90$8700000a@consulintel.es> <C920A0255CBCAF05FBEE6AC9@scan.jck.com> <40AE0C8C.6CFD72A3@swin.edu.au> <20040521145550.GB25670@login.ecs.soton.ac.uk> <40AE1DF2.1080809@it.su.se>
In-Reply-To: <40AE1DF2.1080809@it.su.se>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 May 2004 15:46:59.0613 (UTC) FILETIME=[DA51A4D0:01C43F4A]
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

Leif Johansson wrote:

>> Maybe I'm using an alias... I could be Jim Fleming :)
>
> Tim... Jim... the plot thickens!

<conspiracy>And the ASCII representations of "Tim Chown" and "Jim 
Fleming" can *both* be written as 0s and 1s!
</conspiracy>

-- 
/================================================================\
|John Stracke      |jstracke@centive.com                         |
|Principal Engineer|http://www.centive.com                       |
|Centive           |My opinions are my own.                      |
|================================================================|
|"What now, Brain?" "We should flee in terror. Yes, that would be|
|the wisest course."                                             |
\================================================================/


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


From exim@www1.ietf.org  Fri May 21 12:36:24 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 MAA13275
	for <ietf-archive@odin.ietf.org>; Fri, 21 May 2004 12:36: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 1BRCtf-0002ph-Ba
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 12:29:23 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4LGTNCS010784
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 12:29:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRCY4-00040j-0s; Fri, 21 May 2004 12:07:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRCKC-0000Wq-E0
	for ietf@optimus.ietf.org; Fri, 21 May 2004 11:52:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10378
	for <ietf@ietf.org>; Fri, 21 May 2004 11:52: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 1BRCKB-0007QN-6t
	for ietf@ietf.org; Fri, 21 May 2004 11:52:43 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRCJG-0007Nt-00
	for ietf@ietf.org; Fri, 21 May 2004 11:51:46 -0400
Received: from carwash.centive.com ([65.220.90.249])
	by ietf-mx with smtp (Exim 4.12)
	id 1BRCIw-0007L3-00
	for ietf@ietf.org; Fri, 21 May 2004 11:51:26 -0400
Received: from minglewood.incentivesystems.com ([10.10.30.25])
 by carwash.centive.com (SAVSMTP 3.1.3.37) with SMTP id M2004052111530429060
 for <ietf@ietf.org>; Fri, 21 May 2004 11:53:11 -0400
Received: from [10.10.48.119] ([10.10.48.119]) by minglewood.incentivesystems.com with Microsoft SMTPSVC(6.0.3790.0);
	 Fri, 21 May 2004 11:46:59 -0400
Message-ID: <40AE2473.3080706@centive.com>
Date: Fri, 21 May 2004 11:46:59 -0400
From: John Stracke <jstracke@centive.com>
User-Agent: Mozilla Thunderbird 0.6 (Windows/20040502)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: respect privacy please !
References: <0fa701c43f26$2939af90$8700000a@consulintel.es> <C920A0255CBCAF05FBEE6AC9@scan.jck.com> <40AE0C8C.6CFD72A3@swin.edu.au> <20040521145550.GB25670@login.ecs.soton.ac.uk> <40AE1DF2.1080809@it.su.se>
In-Reply-To: <40AE1DF2.1080809@it.su.se>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 May 2004 15:46:59.0613 (UTC) FILETIME=[DA51A4D0:01C43F4A]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-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

Leif Johansson wrote:

>> Maybe I'm using an alias... I could be Jim Fleming :)
>
> Tim... Jim... the plot thickens!

<conspiracy>And the ASCII representations of "Tim Chown" and "Jim 
Fleming" can *both* be written as 0s and 1s!
</conspiracy>

-- 
/================================================================\
|John Stracke      |jstracke@centive.com                         |
|Principal Engineer|http://www.centive.com                       |
|Centive           |My opinions are my own.                      |
|================================================================|
|"What now, Brain?" "We should flee in terror. Yes, that would be|
|the wisest course."                                             |
\================================================================/


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



From ietf-admin@ietf.org  Fri May 21 12:42: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 MAA14032
	for <ietf-archive@ietf.org>; Fri, 21 May 2004 12:42: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 1BRD6S-00030y-QT
	for ietf-archive@ietf.org; Fri, 21 May 2004 12:42:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRD5R-0002y8-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 12:41:34 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRD4f-0002vz-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 12:40: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 1BRD4h-0000g3-1Y
	for ietf-archive@ietf.org; Fri, 21 May 2004 12:40:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRCvG-0003PH-5I; Fri, 21 May 2004 12:31:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRCYt-0004JU-B8
	for ietf@optimus.ietf.org; Fri, 21 May 2004 12:07: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 MAA11438
	for <ietf@ietf.org>; Fri, 21 May 2004 12:07: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 1BRCYr-0000kP-Vf
	for ietf@ietf.org; Fri, 21 May 2004 12:07:54 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRCXb-0000XG-00
	for ietf@ietf.org; Fri, 21 May 2004 12:06:36 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRCVD-0000Ie-00
	for ietf@ietf.org; Fri, 21 May 2004 12:04:07 -0400
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1BRCVD-0008E5-00; Fri, 21 May 2004 11:04:07 -0500
Date: Fri, 21 May 2004 12:04:05 -0400
From: John C Klensin <john-ietf@jck.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>, ietf@ietf.org
Subject: Re: respect privacy please !
Message-ID: <E7C210D74CABB2E2628DB4ED@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



--On Friday, 21 May, 2004 15:55 +0100 Tim Chown 
<tjc@ecs.soton.ac.uk> wrote:

> On Sat, May 22, 2004 at 12:05:00AM +1000, grenville armitage
> wrote:
>>
>> This could be solved by the IETF insisting that consent is
>> required before attendance. I, like John, do not believe it
>> is acceptable for the IETF meetings to be populated by
>> anonymous attendees.
>
> The issue is someone knowing where I am for a week, in advance.
>
> Harald's suggestion of releasing the list post-event is an
> improvement...

Hmm.  Being paranoid about folks who arrive or depart in black 
helicopters (despite being accused in the past of being one of 
that group), post-meeting feels too late to me.   But, other 
than whatever additional burdens it adds for the Secretariat, I 
can see almost no objection to keeping the list confidential 
until Sunday afternoon or early Monday of the meeting week.

However, before we say "that is a wonderful idea" (or not), 
let's remember the substance of several of the "IETF 
administration" notes and documents that have been circulated in 
the last several months.  If I understand those materials and 
discussions correctly, the Secretariat is stretched pretty thin, 
there are no spare dollars floating around, few if any of us are 
anxious to see increased meeting fees, and I gather that almost 
every request for something new involves a decision about what 
doesn't get done instead.  Even when there has been a perception 
of lots of resources, the Secretariat has, for as long as I can 
remember, been flat-out during the few days before and after an 
IETF meeting starts.  So "post Sunday afternoon" is possibly 
unworkable in practice unless it can be turned over to some 
automated process... and I don't know if the database structure 
lends itself to that without considerable work.

Moreover, I've several times noticed a significant advantage of 
having _my_ name and payment status listed -- it provides an 
easy way for me to check on whether I've registered and paid or 
whether I let it fall through the cracks.  So, for purely 
pragmatic reasons, I'd hate to see the advanced registration 
list taken down unless there is an easy and automated way for me 
to inquire as to whether or not I'm correctly registered. Or the 
_advanced_ registration list could be made opt-out until Sunday, 
and then posted with all names listed.  But either probably 
implies more Secretariat work, even if we don't care much about 
the security (authenticity) of the query in the former case.

So, how important is this, really?  For most of the regular 
attendees, someone wanting to know that you will be away for a 
week and when needs only to determine when an IETF meeting is 
being held.  That isn't 100% reliable, of course, but, because 
you can register (and even pay) and then not come (and I gather 
a significant number of people do so every time), neither is the 
current list.

Speaking for myself only, of course.

best,
    john



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


From exim@www1.ietf.org  Fri May 21 12:50:46 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 MAA14682
	for <ietf-archive@odin.ietf.org>; Fri, 21 May 2004 12:50: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 1BRD4Y-00068Q-TG
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 12:40:49 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4LGecwL023565
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 12:40:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRCvG-0003PH-5I; Fri, 21 May 2004 12:31:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRCYt-0004JU-B8
	for ietf@optimus.ietf.org; Fri, 21 May 2004 12:07: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 MAA11438
	for <ietf@ietf.org>; Fri, 21 May 2004 12:07: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 1BRCYr-0000kP-Vf
	for ietf@ietf.org; Fri, 21 May 2004 12:07:54 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRCXb-0000XG-00
	for ietf@ietf.org; Fri, 21 May 2004 12:06:36 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRCVD-0000Ie-00
	for ietf@ietf.org; Fri, 21 May 2004 12:04:07 -0400
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1BRCVD-0008E5-00; Fri, 21 May 2004 11:04:07 -0500
Date: Fri, 21 May 2004 12:04:05 -0400
From: John C Klensin <john-ietf@jck.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>, ietf@ietf.org
Subject: Re: respect privacy please !
Message-ID: <E7C210D74CABB2E2628DB4ED@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.1 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 Friday, 21 May, 2004 15:55 +0100 Tim Chown 
<tjc@ecs.soton.ac.uk> wrote:

> On Sat, May 22, 2004 at 12:05:00AM +1000, grenville armitage
> wrote:
>>
>> This could be solved by the IETF insisting that consent is
>> required before attendance. I, like John, do not believe it
>> is acceptable for the IETF meetings to be populated by
>> anonymous attendees.
>
> The issue is someone knowing where I am for a week, in advance.
>
> Harald's suggestion of releasing the list post-event is an
> improvement...

Hmm.  Being paranoid about folks who arrive or depart in black 
helicopters (despite being accused in the past of being one of 
that group), post-meeting feels too late to me.   But, other 
than whatever additional burdens it adds for the Secretariat, I 
can see almost no objection to keeping the list confidential 
until Sunday afternoon or early Monday of the meeting week.

However, before we say "that is a wonderful idea" (or not), 
let's remember the substance of several of the "IETF 
administration" notes and documents that have been circulated in 
the last several months.  If I understand those materials and 
discussions correctly, the Secretariat is stretched pretty thin, 
there are no spare dollars floating around, few if any of us are 
anxious to see increased meeting fees, and I gather that almost 
every request for something new involves a decision about what 
doesn't get done instead.  Even when there has been a perception 
of lots of resources, the Secretariat has, for as long as I can 
remember, been flat-out during the few days before and after an 
IETF meeting starts.  So "post Sunday afternoon" is possibly 
unworkable in practice unless it can be turned over to some 
automated process... and I don't know if the database structure 
lends itself to that without considerable work.

Moreover, I've several times noticed a significant advantage of 
having _my_ name and payment status listed -- it provides an 
easy way for me to check on whether I've registered and paid or 
whether I let it fall through the cracks.  So, for purely 
pragmatic reasons, I'd hate to see the advanced registration 
list taken down unless there is an easy and automated way for me 
to inquire as to whether or not I'm correctly registered. Or the 
_advanced_ registration list could be made opt-out until Sunday, 
and then posted with all names listed.  But either probably 
implies more Secretariat work, even if we don't care much about 
the security (authenticity) of the query in the former case.

So, how important is this, really?  For most of the regular 
attendees, someone wanting to know that you will be away for a 
week and when needs only to determine when an IETF meeting is 
being held.  That isn't 100% reliable, of course, but, because 
you can register (and even pay) and then not come (and I gather 
a significant number of people do so every time), neither is the 
current list.

Speaking for myself only, of course.

best,
    john



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



From exim@www1.ietf.org  Fri May 21 13:18: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 NAA16105
	for <ietf-archive@odin.ietf.org>; Fri, 21 May 2004 13:18: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 1BRDaS-0005kC-Cd
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 13:13:36 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4LHDaA8021929
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 13:13:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRDW9-0004cL-Kr; Fri, 21 May 2004 13:09:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRDPz-0002aw-IH
	for ietf@optimus.ietf.org; Fri, 21 May 2004 13:02:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15288
	for <ietf@ietf.org>; Fri, 21 May 2004 13:02: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 1BRDPx-0004SZ-NP
	for ietf@ietf.org; Fri, 21 May 2004 13:02:45 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRDOz-0004PR-00
	for ietf@ietf.org; Fri, 21 May 2004 13:01:46 -0400
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRDOA-0004IE-00
	for ietf@ietf.org; Fri, 21 May 2004 13:00:54 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i4LH0MT00623
	for <ietf@ietf.org>; Fri, 21 May 2004 20:00:23 +0300
Date: Fri, 21 May 2004 20:00:22 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: ietf@ietf.org
Subject: Re: IPv6 for *.ietf.org services (Was: Re: respect privacy please
 !)
In-Reply-To: <1085153528.22699.5746.camel@segesta.zurich.ibm.com>
Message-ID: <Pine.LNX.4.44.0405211952350.32663-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: 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, 21 May 2004, Jeroen Massar wrote:
> On Fri, 2004-05-21 at 16:59, JORDI PALET MARTINEZ wrote:
> 
> <SNIP privacy talk>
> 
> > The other good example is the IPv6 issue. As I recall, I saw (and even participated)
> > in that debate a couple of times. Today I see no objective reason for not doing that,
> > but we don't have a decision on that. Is that good ? Is this what we expect for an open process ?
> 
> I heared one reason that there is that the IETF servers don't have IPv6
> (yet) is simply because their ISP/transit/upstream doesn't do it and
> thus it makes it pretty impossible unfortunatly.
> The software can cope with it without problem mind you.

All the services IETF servers offer are purely client-server based.  
There is no significant technical advantage that I could see in making
them IPv6-enabled, because all such services are very usable with
IPv4.  On the other hand, doing so would just strengthen the illusion
that wide-scale migration of all IPv4 services to IPv4/IPv6 is an
important short-term goal.  

However, IPv6-enabling the IETF services may have _political_
justifications ("eating our own dogfood", etc.), which I'm not
commenting here.

See Keith Moore's excellent write-up:
http://www.cs.utk.edu/~moore/opinions/ipv6/dubious-assumptions.html

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



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



From ietf-admin@ietf.org  Fri May 21 13:30: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 NAA16814
	for <ietf-archive@ietf.org>; Fri, 21 May 2004 13:30: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 1BRDrE-0006Kd-Ow
	for ietf-archive@ietf.org; Fri, 21 May 2004 13:30:56 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRDq3-00068d-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 13:29:45 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRDoe-0005vR-03
	for ietf-archive@ietf.org; Fri, 21 May 2004 13:28:16 -0400
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BRDaT-0001RM-1C
	for ietf-archive@ietf.org; Fri, 21 May 2004 13:13:37 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRDW9-0004cL-Kr; Fri, 21 May 2004 13:09:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRDPz-0002aw-IH
	for ietf@optimus.ietf.org; Fri, 21 May 2004 13:02:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15288
	for <ietf@ietf.org>; Fri, 21 May 2004 13:02: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 1BRDPx-0004SZ-NP
	for ietf@ietf.org; Fri, 21 May 2004 13:02:45 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRDOz-0004PR-00
	for ietf@ietf.org; Fri, 21 May 2004 13:01:46 -0400
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRDOA-0004IE-00
	for ietf@ietf.org; Fri, 21 May 2004 13:00:54 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i4LH0MT00623
	for <ietf@ietf.org>; Fri, 21 May 2004 20:00:23 +0300
Date: Fri, 21 May 2004 20:00:22 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: ietf@ietf.org
Subject: Re: IPv6 for *.ietf.org services (Was: Re: respect privacy please
 !)
In-Reply-To: <1085153528.22699.5746.camel@segesta.zurich.ibm.com>
Message-ID: <Pine.LNX.4.44.0405211952350.32663-100000@netcore.fi>
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 Fri, 21 May 2004, Jeroen Massar wrote:
> On Fri, 2004-05-21 at 16:59, JORDI PALET MARTINEZ wrote:
> 
> <SNIP privacy talk>
> 
> > The other good example is the IPv6 issue. As I recall, I saw (and even participated)
> > in that debate a couple of times. Today I see no objective reason for not doing that,
> > but we don't have a decision on that. Is that good ? Is this what we expect for an open process ?
> 
> I heared one reason that there is that the IETF servers don't have IPv6
> (yet) is simply because their ISP/transit/upstream doesn't do it and
> thus it makes it pretty impossible unfortunatly.
> The software can cope with it without problem mind you.

All the services IETF servers offer are purely client-server based.  
There is no significant technical advantage that I could see in making
them IPv6-enabled, because all such services are very usable with
IPv4.  On the other hand, doing so would just strengthen the illusion
that wide-scale migration of all IPv4 services to IPv4/IPv6 is an
important short-term goal.  

However, IPv6-enabling the IETF services may have _political_
justifications ("eating our own dogfood", etc.), which I'm not
commenting here.

See Keith Moore's excellent write-up:
http://www.cs.utk.edu/~moore/opinions/ipv6/dubious-assumptions.html

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



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


From exim@www1.ietf.org  Fri May 21 13:35: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 NAA17160
	for <ietf-archive@odin.ietf.org>; Fri, 21 May 2004 13:35: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 1BRDtr-0001qX-D8
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 13:33:39 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4LHXdD9007073
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 13:33:39 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRDnT-0008UC-Fz; Fri, 21 May 2004 13:27:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRDj7-0007Tl-GF
	for ietf@optimus.ietf.org; Fri, 21 May 2004 13:22: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 NAA16245
	for <ietf@ietf.org>; Fri, 21 May 2004 13:22: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 1BRDj5-0005dr-8U
	for ietf@ietf.org; Fri, 21 May 2004 13:22:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRDi7-0005bK-00
	for ietf@ietf.org; Fri, 21 May 2004 13:21:31 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRDhA-0005WU-00
	for ietf@ietf.org; Fri, 21 May 2004 13:20:32 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id CF366622D4
	for <ietf@ietf.org>; Fri, 21 May 2004 19:20:01 +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 10660-04 for <ietf@ietf.org>;
 Fri, 21 May 2004 19:20:00 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id 2D98A61A93
	for <ietf@ietf.org>; Fri, 21 May 2004 19:20:00 +0200 (CEST)
Date: Fri, 21 May 2004 10:20:31 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: ietf@ietf.org
Subject: Privacy notice on IETF meeting registration form (fwd)
Message-ID: <347539675.1085134831@dhcp-128-107-163-53.cisco.com>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-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: 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

This is what I asked to have done at the conclusion of our last debate on 
the issue. It seems to not have been carried forward into the IETF 60 
webform.

                  Harald


---------- Forwarded Message ----------
Date: 28. januar 2004 17:30 -0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: ietf-action@ietf.org
Subject: Privacy notice on IETF meeting registration form

Following up on the IETF list debate on privacy of data....

Please add the following text to the registration form on
<http://www.ietf.org/meetings/reg_form59.html> - just before "Thank you"!:

Your name will be published in the list of attendees.
Your email and address will not be made public.
Information on company is used to print your badge.
Information on company and country are used for statistical purposes.

I think that's reasonable disclosure.....

                  Harald

---------- End Forwarded Message ----------





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



From ietf-admin@ietf.org  Fri May 21 13:35: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 NAA17224
	for <ietf-archive@ietf.org>; Fri, 21 May 2004 13:35: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 1BRDvo-0006pN-34
	for ietf-archive@ietf.org; Fri, 21 May 2004 13:35:40 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRDup-0006ip-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 13:34:40 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRDtq-0006cv-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 13:33:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRDnT-0008UC-Fz; Fri, 21 May 2004 13:27:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRDj7-0007Tl-GF
	for ietf@optimus.ietf.org; Fri, 21 May 2004 13:22: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 NAA16245
	for <ietf@ietf.org>; Fri, 21 May 2004 13:22: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 1BRDj5-0005dr-8U
	for ietf@ietf.org; Fri, 21 May 2004 13:22:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRDi7-0005bK-00
	for ietf@ietf.org; Fri, 21 May 2004 13:21:31 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRDhA-0005WU-00
	for ietf@ietf.org; Fri, 21 May 2004 13:20:32 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id CF366622D4
	for <ietf@ietf.org>; Fri, 21 May 2004 19:20:01 +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 10660-04 for <ietf@ietf.org>;
 Fri, 21 May 2004 19:20:00 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id 2D98A61A93
	for <ietf@ietf.org>; Fri, 21 May 2004 19:20:00 +0200 (CEST)
Date: Fri, 21 May 2004 10:20:31 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: ietf@ietf.org
Subject: Privacy notice on IETF meeting registration form (fwd)
Message-ID: <347539675.1085134831@dhcp-128-107-163-53.cisco.com>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
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

This is what I asked to have done at the conclusion of our last debate on 
the issue. It seems to not have been carried forward into the IETF 60 
webform.

                  Harald


---------- Forwarded Message ----------
Date: 28. januar 2004 17:30 -0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: ietf-action@ietf.org
Subject: Privacy notice on IETF meeting registration form

Following up on the IETF list debate on privacy of data....

Please add the following text to the registration form on
<http://www.ietf.org/meetings/reg_form59.html> - just before "Thank you"!:

Your name will be published in the list of attendees.
Your email and address will not be made public.
Information on company is used to print your badge.
Information on company and country are used for statistical purposes.

I think that's reasonable disclosure.....

                  Harald

---------- End Forwarded Message ----------





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


From exim@www1.ietf.org  Fri May 21 13:46:01 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 NAA17648
	for <ietf-archive@odin.ietf.org>; Fri, 21 May 2004 13:46: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 1BRE2h-0004Kk-Hr
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 13:42:52 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4LHglQP016403
	for ietf-archive@odin.ietf.org; Fri, 21 May 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 1BRDuF-0001x1-Nh; Fri, 21 May 2004 13: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 1BRDqZ-0000x9-Ld
	for ietf@optimus.ietf.org; Fri, 21 May 2004 13:30: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 NAA16595
	for <ietf@ietf.org>; Fri, 21 May 2004 13:30:12 -0400 (EDT)
From: bill@strahm.net
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRDqX-0006CS-Dy
	for ietf@ietf.org; Fri, 21 May 2004 13:30:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRDow-0005xY-00
	for ietf@ietf.org; Fri, 21 May 2004 13:28:34 -0400
Received: from smtpout03-03.mesa1.secureserver.net ([64.202.165.73])
	by ietf-mx with smtp (Exim 4.12)
	id 1BRDo5-0005pz-00
	for ietf@ietf.org; Fri, 21 May 2004 13:27:41 -0400
Received: (qmail 4262 invoked from network); 21 May 2004 17:27:35 -0000
Received: from unknown (HELO webmail-2-6.mesa1.secureserver.net) (64.202.166.93)
  by smtpout03-03.mesa1.secureserver.net with SMTP; 21 May 2004 17:27:35 -0000
Received: (qmail 1642 invoked by uid 99); 21 May 2004 17:27:09 -0000
Message-ID: <20040521172709.1641.qmail@webmail-2-6.mesa1.secureserver.net>
Date: Fri, 21 May 2004 10:27:09 -0700
Subject: RE: respect privacy please !
To: Valdis.Kletnieks@vt.edu
cc: 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.4 required=5.0 tests=AWL,NO_REAL_NAME 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>

> -------- Original Message --------
> Subject: Re: respect privacy please !
> From: Valdis.Kletnieks@vt.edu
> Date: Fri, May 21, 2004 8:31 am
> To: "Tim Chown" <tjc@ecs.soton.ac.uk>
> Cc: ietf@ietf.org
> 
> > Maybe I'm using an alias... I could be Jim Fleming :)
> 
> Waving my patent-pending kook-o-meter over your email and Jim's
> produces
> different characteristic patterns... so I doubt it. ;)

Boy I miss Jim F. - The best part about a good troll is you never know when they will raise their ugly head
again in a different disguise

Bill

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



From ietf-admin@ietf.org  Fri May 21 13: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 NAA18101
	for <ietf-archive@ietf.org>; Fri, 21 May 2004 13: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 1BREE8-0000L3-2G
	for ietf-archive@ietf.org; Fri, 21 May 2004 13:54:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRECu-00007P-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 13:53:21 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BREBx-0007li-01
	for ietf-archive@ietf.org; Fri, 21 May 2004 13:52:21 -0400
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BRE2l-000271-Qp
	for ietf-archive@ietf.org; Fri, 21 May 2004 13:42:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRDuF-0001x1-Nh; Fri, 21 May 2004 13: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 1BRDqZ-0000x9-Ld
	for ietf@optimus.ietf.org; Fri, 21 May 2004 13:30: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 NAA16595
	for <ietf@ietf.org>; Fri, 21 May 2004 13:30:12 -0400 (EDT)
From: bill@strahm.net
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRDqX-0006CS-Dy
	for ietf@ietf.org; Fri, 21 May 2004 13:30:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRDow-0005xY-00
	for ietf@ietf.org; Fri, 21 May 2004 13:28:34 -0400
Received: from smtpout03-03.mesa1.secureserver.net ([64.202.165.73])
	by ietf-mx with smtp (Exim 4.12)
	id 1BRDo5-0005pz-00
	for ietf@ietf.org; Fri, 21 May 2004 13:27:41 -0400
Received: (qmail 4262 invoked from network); 21 May 2004 17:27:35 -0000
Received: from unknown (HELO webmail-2-6.mesa1.secureserver.net) (64.202.166.93)
  by smtpout03-03.mesa1.secureserver.net with SMTP; 21 May 2004 17:27:35 -0000
Received: (qmail 1642 invoked by uid 99); 21 May 2004 17:27:09 -0000
Message-ID: <20040521172709.1641.qmail@webmail-2-6.mesa1.secureserver.net>
Date: Fri, 21 May 2004 10:27:09 -0700
Subject: RE: respect privacy please !
To: Valdis.Kletnieks@vt.edu
cc: ietf@ietf.org
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.4 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60

> -------- Original Message --------
> Subject: Re: respect privacy please !
> From: Valdis.Kletnieks@vt.edu
> Date: Fri, May 21, 2004 8:31 am
> To: "Tim Chown" <tjc@ecs.soton.ac.uk>
> Cc: ietf@ietf.org
> 
> > Maybe I'm using an alias... I could be Jim Fleming :)
> 
> Waving my patent-pending kook-o-meter over your email and Jim's
> produces
> different characteristic patterns... so I doubt it. ;)

Boy I miss Jim F. - The best part about a good troll is you never know when they will raise their ugly head
again in a different disguise

Bill

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


From ietf-admin@ietf.org  Fri May 21 14:12: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 OAA19130
	for <ietf-archive@ietf.org>; Fri, 21 May 2004 14:12: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 1BREVr-0001j2-0k
	for ietf-archive@ietf.org; Fri, 21 May 2004 14:12:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BREUz-0001c4-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 14:12:02 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BREU5-0001UL-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 14:11:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRELK-0008M8-Q0; Fri, 21 May 2004 14: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 1BREJ6-0007r1-Fq
	for ietf@optimus.ietf.org; Fri, 21 May 2004 13:59:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18467
	for <ietf@ietf.org>; Fri, 21 May 2004 13:59:37 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BREJ0-0000hr-9U
	for ietf@ietf.org; Fri, 21 May 2004 13:59:38 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BREI5-0000ec-00
	for ietf@ietf.org; Fri, 21 May 2004 13:58:41 -0400
Received: from 206-169-2-196.gen.twtelecom.net ([206.169.2.196] helo=mail.optistreams.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BREHW-0000Ys-00
	for ietf@ietf.org; Fri, 21 May 2004 13:58:06 -0400
Received: from [192.168.0.103] [68.42.70.186] by mail.optistreams.net with ESMTP
  (SMTPD32-8.04) id ADB057401E0; Fri, 21 May 2004 10:34:40 -0700
In-Reply-To: <20040520141439.2e64ca9d.ietf@130c04165a5b40404e4440445758487a.nosense.org>
References: <128882262.1084916137@localhost> <Pine.LNX.4.44.0405192233180.20973-100000@cirrus.av8.net> <20040520141439.2e64ca9d.ietf@130c04165a5b40404e4440445758487a.nosense.org>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <4FDDDC46-AB50-11D8-88E2-000A9571873E@guppylake.com>
Content-Transfer-Encoding: quoted-printable
Cc: Dean Anderson <dean@av8.com>, harald@alvestrand.no, ietf@ietf.org
From: Nathaniel Borenstein <nsb@guppylake.com>
Subject: Re: Response to complaint from Dean Anderson
Date: Fri, 21 May 2004 13:57:23 -0400
To: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
X-Mailer: Apple Mail (2.613)
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

I think Mark's suggestion is very reasonable in the short term, as it=20
neatly bypasses the problem of accuracy and accountability in spam=20
blacklisting services.  And of course Dean always has the option of=20
getting an email account on a non-blacklisted provider.  =02(When I=20
complained to Road Runner that they were unfairly blacklisting my=20
provider, they cheerfully offered to steal my account from my provider=20=

rather than fix the problem.)  But someone will have to wrestle with=20
this problem eventually, and if it isn't IETF it will probably be the=20
US government in the end.

Email has become so important for society and business that very few=20
people will have even as much tolerance as Dean does for being (in his=20=

own mind, at the very least) unfairly blacklisted.  Those of you who=20
are angry at Dean for "flaming" in this case should consider how much=20
more constructive it is for him to bring this matter up on the IETF=20
list than to simply sue everyone who might have played a role in=20
blocking his email.  But frankly, I suspect it is inevitable that the=20
courts in several countries will be called on to resolve these issues=20
fairly soon.  -- Nathaniel


On May 20, 2004, at 12:44 AM, Mark Smith wrote:

> On Wed, 19 May 2004 23:42:01 -0400 (EDT)
> Dean Anderson <dean@av8.com> wrote:
>
>> On Tue, 18 May 2004, Harald Tveit Alvestrand wrote:
>>
>
> <snip - whole lot of legal stuff that I don't have time to
> read - I've got a few thousand RFCs to go ...>
>
> Firstly, let me say that it is really sad that legalease, legal
> council and legal positions have appeared on an IETF mailing
> list to the extent we've seen. I've understood that the IETF was
> all about best technical solutions and positions, not best legal
> solutions and positions.
>
> Dean, I'm in no position to implement this as a solution (nor
> have I spent time thinking about how hard or easy it
> would be to implement), however, presuming that @ietf.org doesn't
> implement MTA blocking via methods such as SORBS, and I don't
> think they do, would you be happy if all people who have official
> IETF positions (eg. area advisor, working group chair, etc) had
> @ietf.org email addresses, and used those for any IETF related
> correspondence ?
>
> Regards,
> Mark.
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>
>


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


From exim@www1.ietf.org  Fri May 21 14:21:35 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 OAA19476
	for <ietf-archive@odin.ietf.org>; Fri, 21 May 2004 14:21:35 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BREU6-0002Bh-FH
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 14:11:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4LIB6Xo008409
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 14:11:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRELK-0008M8-Q0; Fri, 21 May 2004 14: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 1BREJ6-0007r1-Fq
	for ietf@optimus.ietf.org; Fri, 21 May 2004 13:59:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18467
	for <ietf@ietf.org>; Fri, 21 May 2004 13:59:37 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BREJ0-0000hr-9U
	for ietf@ietf.org; Fri, 21 May 2004 13:59:38 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BREI5-0000ec-00
	for ietf@ietf.org; Fri, 21 May 2004 13:58:41 -0400
Received: from 206-169-2-196.gen.twtelecom.net ([206.169.2.196] helo=mail.optistreams.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BREHW-0000Ys-00
	for ietf@ietf.org; Fri, 21 May 2004 13:58:06 -0400
Received: from [192.168.0.103] [68.42.70.186] by mail.optistreams.net with ESMTP
  (SMTPD32-8.04) id ADB057401E0; Fri, 21 May 2004 10:34:40 -0700
In-Reply-To: <20040520141439.2e64ca9d.ietf@130c04165a5b40404e4440445758487a.nosense.org>
References: <128882262.1084916137@localhost> <Pine.LNX.4.44.0405192233180.20973-100000@cirrus.av8.net> <20040520141439.2e64ca9d.ietf@130c04165a5b40404e4440445758487a.nosense.org>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <4FDDDC46-AB50-11D8-88E2-000A9571873E@guppylake.com>
Content-Transfer-Encoding: quoted-printable
Cc: Dean Anderson <dean@av8.com>, harald@alvestrand.no, ietf@ietf.org
From: Nathaniel Borenstein <nsb@guppylake.com>
Subject: Re: Response to complaint from Dean Anderson
Date: Fri, 21 May 2004 13:57:23 -0400
To: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
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: 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

I think Mark's suggestion is very reasonable in the short term, as it=20
neatly bypasses the problem of accuracy and accountability in spam=20
blacklisting services.  And of course Dean always has the option of=20
getting an email account on a non-blacklisted provider.  =02(When I=20
complained to Road Runner that they were unfairly blacklisting my=20
provider, they cheerfully offered to steal my account from my provider=20=

rather than fix the problem.)  But someone will have to wrestle with=20
this problem eventually, and if it isn't IETF it will probably be the=20
US government in the end.

Email has become so important for society and business that very few=20
people will have even as much tolerance as Dean does for being (in his=20=

own mind, at the very least) unfairly blacklisted.  Those of you who=20
are angry at Dean for "flaming" in this case should consider how much=20
more constructive it is for him to bring this matter up on the IETF=20
list than to simply sue everyone who might have played a role in=20
blocking his email.  But frankly, I suspect it is inevitable that the=20
courts in several countries will be called on to resolve these issues=20
fairly soon.  -- Nathaniel


On May 20, 2004, at 12:44 AM, Mark Smith wrote:

> On Wed, 19 May 2004 23:42:01 -0400 (EDT)
> Dean Anderson <dean@av8.com> wrote:
>
>> On Tue, 18 May 2004, Harald Tveit Alvestrand wrote:
>>
>
> <snip - whole lot of legal stuff that I don't have time to
> read - I've got a few thousand RFCs to go ...>
>
> Firstly, let me say that it is really sad that legalease, legal
> council and legal positions have appeared on an IETF mailing
> list to the extent we've seen. I've understood that the IETF was
> all about best technical solutions and positions, not best legal
> solutions and positions.
>
> Dean, I'm in no position to implement this as a solution (nor
> have I spent time thinking about how hard or easy it
> would be to implement), however, presuming that @ietf.org doesn't
> implement MTA blocking via methods such as SORBS, and I don't
> think they do, would you be happy if all people who have official
> IETF positions (eg. area advisor, working group chair, etc) had
> @ietf.org email addresses, and used those for any IETF related
> correspondence ?
>
> Regards,
> Mark.
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>
>


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



From ietf-admin@ietf.org  Fri May 21 14:53:33 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21349
	for <ietf-archive@ietf.org>; Fri, 21 May 2004 14:53: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 1BRF9B-0004hN-T4
	for ietf-archive@ietf.org; Fri, 21 May 2004 14:53:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRF8E-0004bR-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 14:52:34 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRF7F-0004Vv-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 14:51:33 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRF0w-0001Dt-ES; Fri, 21 May 2004 14:45:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BREq7-0007Cr-F1
	for ietf@optimus.ietf.org; Fri, 21 May 2004 14:33:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20333
	for <ietf@ietf.org>; Fri, 21 May 2004 14:33: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 1BREq4-0003F5-J2
	for ietf@ietf.org; Fri, 21 May 2004 14:33:48 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BREp6-00037G-00
	for ietf@ietf.org; Fri, 21 May 2004 14:32:48 -0400
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BREnc-0002uH-00; Fri, 21 May 2004 14:31:17 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i4LIUYt09696;
	Fri, 21 May 2004 11:30:34 -0700
X-mProtect: <200405211830> 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 smtpdPc0IZK; Fri, 21 May 2004 11:30:32 PDT
Message-ID: <40AE4ADC.3060502@iprg.nokia.com>
Date: Fri, 21 May 2004 11:30:52 -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: Harald Tveit Alvestrand <harald@alvestrand.no>
CC: Pekka Savola <pekkas@netcore.fi>, iesg@ietf.org, ietf@ietf.org,
        ftemplin@iprg.nokia.com
Subject: Re: Last Call: 'The IESG and RFC Editor documents: Procedures' to
 BCP
References: <Pine.LNX.4.44.0405191511470.14373-100000@netcore.fi> <161942430.1084949198@localhost> <40AD4ED6.3010206@iprg.nokia.com> <300454600.1085087711@localhost>
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.2 required=5.0 tests=AWL,UPPERCASE_25_50 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Thanks Harald, and also to the others who responded. It appears I
was mistaken in saying that I had never seen the statement beginning:

  "This document and the information contained herein...",

since the same text appears in some of my own documents. However,
I don't recall ever seeing it prefaced with a section heading such as:
"Disclaimer of Validity".

([RFC 3667], section 5.5) just says that the statement is: "(Normally
placed at the end of the IETF Document after the copyright notice.)",
i.e., it doesn't say anything about adding a "Disclaimer of Validity"
section heading.

I'm still a bit puzzled by what "Disclaimer of Validity" could mean,
.e.g., could it mean that everything that appears in the document
before it is "invalid"? Would appreciate clarification on this.

Thanks - Fred
ftemplin@iprg.nokia.com

Harald Tveit Alvestrand wrote:

>
>
> --On 20. mai 2004 17:35 -0700 Fred Templin <ftemplin@iprg.nokia.com> 
> wrote:
>
>>> Disclaimer of Validity
>>>
>>>   This document and the information contained herein are provided on an
>>>   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
>>>   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
>>>   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
>>>   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
>>>   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
>>>   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
>>>
>>>
>>
>> I have never seen such a statement appearing in an I-D before.
>> Is this a standard statement for such procedural documents?
>> And,  is the intention that it be removed (by the RFC editor,
>> I guess) before publishing as BCP?
>
>
> Inserted by xml2rfc. See RFC 3667 section 5.5 - this notice should 
> appear in all IETF documents.
>
>                         Harald
>
>
> _______________________________________________
> 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  Fri May 21 15:03: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 PAA22051
	for <ietf-archive@ietf.org>; Fri, 21 May 2004 15:03: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 1BRFJ4-0005bJ-BU
	for ietf-archive@ietf.org; Fri, 21 May 2004 15:03:46 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRFIa-0005V1-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 15:03:16 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRFHU-0005Ot-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 15:02:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRF6k-0002Ro-NL; Fri, 21 May 2004 14:51:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRF0b-000190-El
	for ietf@optimus.ietf.org; Fri, 21 May 2004 14:44: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 OAA21066
	for <ietf@ietf.org>; Fri, 21 May 2004 14:44: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 1BRF0Y-00044O-Js
	for ietf@ietf.org; Fri, 21 May 2004 14:44:38 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BREzv-000408-00
	for ietf@ietf.org; Fri, 21 May 2004 14:44:00 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BREzI-0003uB-00; Fri, 21 May 2004 14:43:20 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 806B9622D7; Fri, 21 May 2004 20:42:49 +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 12810-04; Fri, 21 May 2004 20:42:48 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 67F6D61A93; Fri, 21 May 2004 20:42:47 +0200 (CEST)
Date: Fri, 21 May 2004 11:43:19 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Fred Templin <ftemplin@iprg.nokia.com>
Cc: Pekka Savola <pekkas@netcore.fi>, iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: 'The IESG and RFC Editor documents: Procedures' to
 BCP
Message-ID: <352506647.1085139799@dhcp-128-107-163-53.cisco.com>
In-Reply-To: <40AE4ADC.3060502@iprg.nokia.com>
References: <Pine.LNX.4.44.0405191511470.14373-100000@netcore.fi>
 <161942430.1084949198@localhost> <40AD4ED6.3010206@iprg.nokia.com>
 <300454600.1085087711@localhost> <40AE4ADC.3060502@iprg.nokia.com>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
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 21. mai 2004 11:30 -0700 Fred Templin <ftemplin@iprg.nokia.com> wrote:

> I'm still a bit puzzled by what "Disclaimer of Validity" could mean,
> .e.g., could it mean that everything that appears in the document
> before it is "invalid"? Would appreciate clarification on this.

I think it means that "ISOC and IETF make no promise of validity"....



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


From exim@www1.ietf.org  Fri May 21 15:05: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 PAA22321
	for <ietf-archive@odin.ietf.org>; Fri, 21 May 2004 15:05: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 1BRF7H-0002gC-Dd
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 14:51:40 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4LIpZnN010300
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 14:51:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRF0w-0001Dt-ES; Fri, 21 May 2004 14:45:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BREq7-0007Cr-F1
	for ietf@optimus.ietf.org; Fri, 21 May 2004 14:33:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20333
	for <ietf@ietf.org>; Fri, 21 May 2004 14:33: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 1BREq4-0003F5-J2
	for ietf@ietf.org; Fri, 21 May 2004 14:33:48 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BREp6-00037G-00
	for ietf@ietf.org; Fri, 21 May 2004 14:32:48 -0400
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BREnc-0002uH-00; Fri, 21 May 2004 14:31:17 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i4LIUYt09696;
	Fri, 21 May 2004 11:30:34 -0700
X-mProtect: <200405211830> 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 smtpdPc0IZK; Fri, 21 May 2004 11:30:32 PDT
Message-ID: <40AE4ADC.3060502@iprg.nokia.com>
Date: Fri, 21 May 2004 11:30:52 -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: Harald Tveit Alvestrand <harald@alvestrand.no>
CC: Pekka Savola <pekkas@netcore.fi>, iesg@ietf.org, ietf@ietf.org,
        ftemplin@iprg.nokia.com
Subject: Re: Last Call: 'The IESG and RFC Editor documents: Procedures' to
 BCP
References: <Pine.LNX.4.44.0405191511470.14373-100000@netcore.fi> <161942430.1084949198@localhost> <40AD4ED6.3010206@iprg.nokia.com> <300454600.1085087711@localhost>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,UPPERCASE_25_50 
	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

Thanks Harald, and also to the others who responded. It appears I
was mistaken in saying that I had never seen the statement beginning:

  "This document and the information contained herein...",

since the same text appears in some of my own documents. However,
I don't recall ever seeing it prefaced with a section heading such as:
"Disclaimer of Validity".

([RFC 3667], section 5.5) just says that the statement is: "(Normally
placed at the end of the IETF Document after the copyright notice.)",
i.e., it doesn't say anything about adding a "Disclaimer of Validity"
section heading.

I'm still a bit puzzled by what "Disclaimer of Validity" could mean,
.e.g., could it mean that everything that appears in the document
before it is "invalid"? Would appreciate clarification on this.

Thanks - Fred
ftemplin@iprg.nokia.com

Harald Tveit Alvestrand wrote:

>
>
> --On 20. mai 2004 17:35 -0700 Fred Templin <ftemplin@iprg.nokia.com> 
> wrote:
>
>>> Disclaimer of Validity
>>>
>>>   This document and the information contained herein are provided on an
>>>   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
>>>   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
>>>   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
>>>   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
>>>   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
>>>   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
>>>
>>>
>>
>> I have never seen such a statement appearing in an I-D before.
>> Is this a standard statement for such procedural documents?
>> And,  is the intention that it be removed (by the RFC editor,
>> I guess) before publishing as BCP?
>
>
> Inserted by xml2rfc. See RFC 3667 section 5.5 - this notice should 
> appear in all IETF documents.
>
>                         Harald
>
>
> _______________________________________________
> 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  Fri May 21 15:07: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 PAA22607
	for <ietf-archive@odin.ietf.org>; Fri, 21 May 2004 15:07:55 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRFHX-0004rG-CY
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 15:02:11 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4LJ2BFt018625
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 15:02:11 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRF6k-0002Ro-NL; Fri, 21 May 2004 14:51:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRF0b-000190-El
	for ietf@optimus.ietf.org; Fri, 21 May 2004 14:44: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 OAA21066
	for <ietf@ietf.org>; Fri, 21 May 2004 14:44: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 1BRF0Y-00044O-Js
	for ietf@ietf.org; Fri, 21 May 2004 14:44:38 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BREzv-000408-00
	for ietf@ietf.org; Fri, 21 May 2004 14:44:00 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BREzI-0003uB-00; Fri, 21 May 2004 14:43:20 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 806B9622D7; Fri, 21 May 2004 20:42:49 +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 12810-04; Fri, 21 May 2004 20:42:48 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 67F6D61A93; Fri, 21 May 2004 20:42:47 +0200 (CEST)
Date: Fri, 21 May 2004 11:43:19 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Fred Templin <ftemplin@iprg.nokia.com>
Cc: Pekka Savola <pekkas@netcore.fi>, iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: 'The IESG and RFC Editor documents: Procedures' to
 BCP
Message-ID: <352506647.1085139799@dhcp-128-107-163-53.cisco.com>
In-Reply-To: <40AE4ADC.3060502@iprg.nokia.com>
References: <Pine.LNX.4.44.0405191511470.14373-100000@netcore.fi>
 <161942430.1084949198@localhost> <40AD4ED6.3010206@iprg.nokia.com>
 <300454600.1085087711@localhost> <40AE4ADC.3060502@iprg.nokia.com>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-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: 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 21. mai 2004 11:30 -0700 Fred Templin <ftemplin@iprg.nokia.com> wrote:

> I'm still a bit puzzled by what "Disclaimer of Validity" could mean,
> .e.g., could it mean that everything that appears in the document
> before it is "invalid"? Would appreciate clarification on this.

I think it means that "ISOC and IETF make no promise of validity"....



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



From ietf-admin@ietf.org  Fri May 21 16:03:43 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26174
	for <ietf-archive@ietf.org>; Fri, 21 May 2004 16:03:43 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRGF6-0002Mz-Ak
	for ietf-archive@ietf.org; Fri, 21 May 2004 16:03:44 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRGEI-0002HV-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 16:02:55 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRGDO-0002CZ-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 16:01:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRG7o-000745-3V; Fri, 21 May 2004 15:56:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRG08-0005gC-7i
	for ietf@optimus.ietf.org; Fri, 21 May 2004 15:48: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 PAA25295
	for <ietf@ietf.org>; Fri, 21 May 2004 15:48:13 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRG06-00019U-Lx
	for ietf@ietf.org; Fri, 21 May 2004 15:48:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRFxm-0000iC-00
	for ietf@ietf.org; Fri, 21 May 2004 15:45:51 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRFun-000087-00; Fri, 21 May 2004 15:42:45 -0400
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BRFRc-0003fc-0U; Fri, 21 May 2004 15:12:36 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i4LJBtu14359;
	Fri, 21 May 2004 12:11:55 -0700
X-mProtect: <200405211911> 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 smtpduXS5Ha; Fri, 21 May 2004 12:11:54 PDT
Message-ID: <40AE548D.1020200@iprg.nokia.com>
Date: Fri, 21 May 2004 12:12:13 -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: Harald Tveit Alvestrand <harald@alvestrand.no>
CC: Pekka Savola <pekkas@netcore.fi>, iesg@ietf.org, ietf@ietf.org,
        ftemplin@iprg.nokia.com
Subject: Re: Last Call: 'The IESG and RFC Editor documents: Procedures' to
 BCP
References: <Pine.LNX.4.44.0405191511470.14373-100000@netcore.fi> <161942430.1084949198@localhost> <40AD4ED6.3010206@iprg.nokia.com> <300454600.1085087711@localhost> <40AE4ADC.3060502@iprg.nokia.com> <352506647.1085139799@dhcp-128-107-163-53.cisco.com>
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

Harald Tveit Alvestrand wrote:

> --On 21. mai 2004 11:30 -0700 Fred Templin <ftemplin@iprg.nokia.com> 
> wrote:
>
>> I'm still a bit puzzled by what "Disclaimer of Validity" could mean,
>> .e.g., could it mean that everything that appears in the document
>> before it is "invalid"? Would appreciate clarification on this.
>
>
> I think it means that "ISOC and IETF make no promise of validity"....


Perhaps, but with no prior formalization (e.g., in RFC 3667)
it seems left rather open to the reader's interpretation.

One possible interpretation is that perhaps the author was
"only kidding" and the document should be taken with a
grain of salt. Could that be the case here?

Thanks - Fred
ftemplin@iprg.nokia.com



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


From exim@www1.ietf.org  Fri May 21 16:44:55 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00873
	for <ietf-archive@odin.ietf.org>; Fri, 21 May 2004 16:44:55 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRGDP-0008K3-Gf
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 16:01:59 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4LK1xRF031963
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 16:01:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRG7o-000745-3V; Fri, 21 May 2004 15:56:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRG08-0005gC-7i
	for ietf@optimus.ietf.org; Fri, 21 May 2004 15:48: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 PAA25295
	for <ietf@ietf.org>; Fri, 21 May 2004 15:48:13 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRG06-00019U-Lx
	for ietf@ietf.org; Fri, 21 May 2004 15:48:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRFxm-0000iC-00
	for ietf@ietf.org; Fri, 21 May 2004 15:45:51 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRFun-000087-00; Fri, 21 May 2004 15:42:45 -0400
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BRFRc-0003fc-0U; Fri, 21 May 2004 15:12:36 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i4LJBtu14359;
	Fri, 21 May 2004 12:11:55 -0700
X-mProtect: <200405211911> 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 smtpduXS5Ha; Fri, 21 May 2004 12:11:54 PDT
Message-ID: <40AE548D.1020200@iprg.nokia.com>
Date: Fri, 21 May 2004 12:12:13 -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: Harald Tveit Alvestrand <harald@alvestrand.no>
CC: Pekka Savola <pekkas@netcore.fi>, iesg@ietf.org, ietf@ietf.org,
        ftemplin@iprg.nokia.com
Subject: Re: Last Call: 'The IESG and RFC Editor documents: Procedures' to
 BCP
References: <Pine.LNX.4.44.0405191511470.14373-100000@netcore.fi> <161942430.1084949198@localhost> <40AD4ED6.3010206@iprg.nokia.com> <300454600.1085087711@localhost> <40AE4ADC.3060502@iprg.nokia.com> <352506647.1085139799@dhcp-128-107-163-53.cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=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

Harald Tveit Alvestrand wrote:

> --On 21. mai 2004 11:30 -0700 Fred Templin <ftemplin@iprg.nokia.com> 
> wrote:
>
>> I'm still a bit puzzled by what "Disclaimer of Validity" could mean,
>> .e.g., could it mean that everything that appears in the document
>> before it is "invalid"? Would appreciate clarification on this.
>
>
> I think it means that "ISOC and IETF make no promise of validity"....


Perhaps, but with no prior formalization (e.g., in RFC 3667)
it seems left rather open to the reader's interpretation.

One possible interpretation is that perhaps the author was
"only kidding" and the document should be taken with a
grain of salt. Could that be the case here?

Thanks - Fred
ftemplin@iprg.nokia.com



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



From ietf-admin@ietf.org  Fri May 21 17:09: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 RAA03734
	for <ietf-archive@ietf.org>; Fri, 21 May 2004 17:09: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 1BRHGO-00050D-Je
	for ietf-archive@ietf.org; Fri, 21 May 2004 17:09:08 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRHFq-0004sn-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 17:08:35 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRHEF-0004hB-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 17:06:55 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRH3G-0004kU-C4; Fri, 21 May 2004 16:55:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRGkW-0005Nt-28
	for ietf@optimus.ietf.org; Fri, 21 May 2004 16:36:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29496
	for <ietf@ietf.org>; Fri, 21 May 2004 16:36: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 1BRGkT-0007Gv-UM
	for ietf@ietf.org; Fri, 21 May 2004 16:36:10 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRGj5-0006zA-00
	for ietf@ietf.org; Fri, 21 May 2004 16:34:43 -0400
Received: from 1-1-2-20b.rny.sth.bostream.se ([82.182.132.65] helo=klapautius.it.su.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRGhZ-0006j0-00
	for ietf@ietf.org; Fri, 21 May 2004 16:33:09 -0400
Received: from it.su.se (localhost.localdomain [127.0.0.1])
	by klapautius.it.su.se (8.11.6/8.11.6) with ESMTP id i4LKVkv09446;
	Fri, 21 May 2004 22:31:46 +0200
Message-ID: <40AE6732.3050400@it.su.se>
Date: Fri, 21 May 2004 22:31:46 +0200
From: Leif Johansson <leifj@it.su.se>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: sv, en, en-us
MIME-Version: 1.0
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
CC: ietf@ietf.org
Subject: Re: respect privacy please !
References: <0fa701c43f26$2939af90$8700000a@consulintel.es> <335417014.1085122709@localhost> <128901c43f45$8b640de0$8700000a@consulintel.es>
In-Reply-To: <128901c43f45$8b640de0$8700000a@consulintel.es>
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=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

JORDI PALET MARTINEZ wrote:
> Hi Harald,
> 
> I'm not expert in legal stuff, but I think the European regulations (at least in Spain because I needed to learn this in order to host web sites with any kind of registration or list of people and comply with the law), there is no difference in publishing it before, during or after. Just can't be published w/o the consent of the participant.
> 

I think you are right, however that does not mean that a 'to use this
service you must agree to having your information published'-rule is
incompatible with EU privacy legislation. I think Haralds proposed
fix is probably fine.

	MVH leifj

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


From exim@www1.ietf.org  Fri May 21 17:20:18 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04391
	for <ietf-archive@odin.ietf.org>; Fri, 21 May 2004 17:20: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 1BRHEG-0001tt-Gg
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 17:06:57 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4LL6ufS007287
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 17:06:56 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRH3G-0004kU-C4; Fri, 21 May 2004 16:55:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRGkW-0005Nt-28
	for ietf@optimus.ietf.org; Fri, 21 May 2004 16:36:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29496
	for <ietf@ietf.org>; Fri, 21 May 2004 16:36: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 1BRGkT-0007Gv-UM
	for ietf@ietf.org; Fri, 21 May 2004 16:36:10 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRGj5-0006zA-00
	for ietf@ietf.org; Fri, 21 May 2004 16:34:43 -0400
Received: from 1-1-2-20b.rny.sth.bostream.se ([82.182.132.65] helo=klapautius.it.su.se)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRGhZ-0006j0-00
	for ietf@ietf.org; Fri, 21 May 2004 16:33:09 -0400
Received: from it.su.se (localhost.localdomain [127.0.0.1])
	by klapautius.it.su.se (8.11.6/8.11.6) with ESMTP id i4LKVkv09446;
	Fri, 21 May 2004 22:31:46 +0200
Message-ID: <40AE6732.3050400@it.su.se>
Date: Fri, 21 May 2004 22:31:46 +0200
From: Leif Johansson <leifj@it.su.se>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: sv, en, en-us
MIME-Version: 1.0
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
CC: ietf@ietf.org
Subject: Re: respect privacy please !
References: <0fa701c43f26$2939af90$8700000a@consulintel.es> <335417014.1085122709@localhost> <128901c43f45$8b640de0$8700000a@consulintel.es>
In-Reply-To: <128901c43f45$8b640de0$8700000a@consulintel.es>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: 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

JORDI PALET MARTINEZ wrote:
> Hi Harald,
> 
> I'm not expert in legal stuff, but I think the European regulations (at least in Spain because I needed to learn this in order to host web sites with any kind of registration or list of people and comply with the law), there is no difference in publishing it before, during or after. Just can't be published w/o the consent of the participant.
> 

I think you are right, however that does not mean that a 'to use this
service you must agree to having your information published'-rule is
incompatible with EU privacy legislation. I think Haralds proposed
fix is probably fine.

	MVH leifj

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



From exim@www1.ietf.org  Fri May 21 20:45:07 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16004
	for <ietf-archive@odin.ietf.org>; Fri, 21 May 2004 20: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 1BRKa6-0003GG-2t
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 20:41:44 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4M0fghJ012281
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 20:41:42 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRKVa-0001dk-RI; Fri, 21 May 2004 20:37:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRKLh-00008J-DK
	for ietf@optimus.ietf.org; Fri, 21 May 2004 20:26: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 UAA15474
	for <ietf@ietf.org>; Fri, 21 May 2004 20:26: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 1BRKLe-0000Kx-TK
	for ietf@ietf.org; Fri, 21 May 2004 20:26:47 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRKKo-0000FU-00
	for ietf@ietf.org; Fri, 21 May 2004 20:25:54 -0400
Received: from c3p0.cc.swin.edu.au ([136.186.1.30] helo=swin.edu.au)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRKJt-00004H-00
	for ietf@ietf.org; Fri, 21 May 2004 20:24:57 -0400
Received: from swin.edu.au (www.caia.swin.edu.au [136.186.229.16])
	by swin.edu.au (8.9.3p2-20030918/8.9.3) with ESMTP id KAA809539;
	Sat, 22 May 2004 10:24:15 +1000 (EST)
Message-ID: <40AE9DAE.41D764C7@swin.edu.au>
Date: Sat, 22 May 2004 10:24:14 +1000
From: grenville armitage <garmitage@swin.edu.au>
Organization: Centre for Advanced Internet Architectures, Swinburne University of 
 Technology
X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: respect privacy please !
References: <0fa701c43f26$2939af90$8700000a@consulintel.es> <C920A0255CBCAF05FBEE6AC9@scan.jck.com> <40AE0C8C.6CFD72A3@swin.edu.au> <20040521145550.GB25670@login.ecs.soton.ac.uk>
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

Tim Chown wrote:
> 
> On Sat, May 22, 2004 at 12:05:00AM +1000, grenville armitage wrote:
> >
> > This could be solved by the IETF insisting that consent is required
> > before attendance. I, like John, do not believe it is acceptable for
> > the IETF meetings to be populated by anonymous attendees.
> 
> The issue is someone knowing where I am for a week, in advance.

If your threat model postulates someone knowing enough about you to check
for your IETF registration, then simply knowing when IETF meetings occur gives
them a pretty good start. Testing your email account for 'out of office'
replies gives them on-the-week confirmation. Just watching what you've
been saying on ietf mailing lists leading up to the next scheduled IETF
meeting can confirm their suspicions.

I.e. hiding IETF registrations is hardly likely to impact on the threat offered
to your personal security by anyone knowledgable enough about your behavior
to be checking the IETF's online registrations list in the first place.

But in any case, post-meeting release of the registration list would go
along way to satisfying the goal of knowing "who was there".

cheers,
gja

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



From ietf-admin@ietf.org  Fri May 21 20:49:43 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16288
	for <ietf-archive@ietf.org>; Fri, 21 May 2004 20:49: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 1BRKhs-0002Ko-38
	for ietf-archive@ietf.org; Fri, 21 May 2004 20:49:44 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRKgc-000284-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 20:48:26 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRKfX-0001yK-01
	for ietf-archive@ietf.org; Fri, 21 May 2004 20:47:19 -0400
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BRKa7-0004Hb-So
	for ietf-archive@ietf.org; Fri, 21 May 2004 20:41:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRKVa-0001dk-RI; Fri, 21 May 2004 20:37:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRKLh-00008J-DK
	for ietf@optimus.ietf.org; Fri, 21 May 2004 20:26: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 UAA15474
	for <ietf@ietf.org>; Fri, 21 May 2004 20:26: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 1BRKLe-0000Kx-TK
	for ietf@ietf.org; Fri, 21 May 2004 20:26:47 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRKKo-0000FU-00
	for ietf@ietf.org; Fri, 21 May 2004 20:25:54 -0400
Received: from c3p0.cc.swin.edu.au ([136.186.1.30] helo=swin.edu.au)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRKJt-00004H-00
	for ietf@ietf.org; Fri, 21 May 2004 20:24:57 -0400
Received: from swin.edu.au (www.caia.swin.edu.au [136.186.229.16])
	by swin.edu.au (8.9.3p2-20030918/8.9.3) with ESMTP id KAA809539;
	Sat, 22 May 2004 10:24:15 +1000 (EST)
Message-ID: <40AE9DAE.41D764C7@swin.edu.au>
Date: Sat, 22 May 2004 10:24:14 +1000
From: grenville armitage <garmitage@swin.edu.au>
Organization: Centre for Advanced Internet Architectures, Swinburne University of 
 Technology
X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: respect privacy please !
References: <0fa701c43f26$2939af90$8700000a@consulintel.es> <C920A0255CBCAF05FBEE6AC9@scan.jck.com> <40AE0C8C.6CFD72A3@swin.edu.au> <20040521145550.GB25670@login.ecs.soton.ac.uk>
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

Tim Chown wrote:
> 
> On Sat, May 22, 2004 at 12:05:00AM +1000, grenville armitage wrote:
> >
> > This could be solved by the IETF insisting that consent is required
> > before attendance. I, like John, do not believe it is acceptable for
> > the IETF meetings to be populated by anonymous attendees.
> 
> The issue is someone knowing where I am for a week, in advance.

If your threat model postulates someone knowing enough about you to check
for your IETF registration, then simply knowing when IETF meetings occur gives
them a pretty good start. Testing your email account for 'out of office'
replies gives them on-the-week confirmation. Just watching what you've
been saying on ietf mailing lists leading up to the next scheduled IETF
meeting can confirm their suspicions.

I.e. hiding IETF registrations is hardly likely to impact on the threat offered
to your personal security by anyone knowledgable enough about your behavior
to be checking the IETF's online registrations list in the first place.

But in any case, post-meeting release of the registration list would go
along way to satisfying the goal of knowing "who was there".

cheers,
gja

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


From ietf-admin@ietf.org  Fri May 21 21:12: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 VAA17167
	for <ietf-archive@ietf.org>; Fri, 21 May 2004 21:12: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 1BRL44-0004k3-L5
	for ietf-archive@ietf.org; Fri, 21 May 2004 21:12:40 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRL2o-0004WD-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 21:11:23 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRL1Y-0004Fz-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 21:10:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRKsp-0006Pa-R6; Fri, 21 May 2004 21: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 1BRKlo-0004zd-Jd
	for ietf@optimus.ietf.org; Fri, 21 May 2004 20:53:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16552
	for <ietf@ietf.org>; Fri, 21 May 2004 20:53: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 1BRKlm-0002rQ-5P
	for ietf@ietf.org; Fri, 21 May 2004 20:53:46 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRKkn-0002m7-00
	for ietf@ietf.org; Fri, 21 May 2004 20:52:46 -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 1BRKjq-0002aR-00
	for ietf@ietf.org; Fri, 21 May 2004 20:51:47 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: respect privacy please !
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Date: Fri, 21 May 2004 17:51:12 -0700
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B0DB138@server2003.arneill-py.sacramento.ca.us>
Thread-Topic: respect privacy please !
Thread-Index: AcQ/lefWvWDjsFMpSO2F7HF8RGqaqAAABr0g
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: <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

> Tim Chown wrote:
> The issue is someone knowing where I am for a week, in advance.

I'm sure Osama would care about that, but do you mind explaining why you
do? Hitmen are going to hunt you down? If there is a bounty on your
head, consider allowing a fellow IETFer to get it instead of an
anonymous sniper :-)

Michel.



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


From exim@www1.ietf.org  Fri May 21 21:19:12 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA17379
	for <ietf-archive@odin.ietf.org>; Fri, 21 May 2004 21:19: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 1BRL1b-0000O3-2B
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 21:10:07 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4M1A7Q0001231
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 21:10:07 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRKsp-0006Pa-R6; Fri, 21 May 2004 21: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 1BRKlo-0004zd-Jd
	for ietf@optimus.ietf.org; Fri, 21 May 2004 20:53:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16552
	for <ietf@ietf.org>; Fri, 21 May 2004 20:53: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 1BRKlm-0002rQ-5P
	for ietf@ietf.org; Fri, 21 May 2004 20:53:46 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRKkn-0002m7-00
	for ietf@ietf.org; Fri, 21 May 2004 20:52:46 -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 1BRKjq-0002aR-00
	for ietf@ietf.org; Fri, 21 May 2004 20:51:47 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: respect privacy please !
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Date: Fri, 21 May 2004 17:51:12 -0700
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B0DB138@server2003.arneill-py.sacramento.ca.us>
Thread-Topic: respect privacy please !
Thread-Index: AcQ/lefWvWDjsFMpSO2F7HF8RGqaqAAABr0g
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: <ietf@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: 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

> Tim Chown wrote:
> The issue is someone knowing where I am for a week, in advance.

I'm sure Osama would care about that, but do you mind explaining why you
do? Hitmen are going to hunt you down? If there is a bounty on your
head, consider allowing a fellow IETFer to get it instead of an
anonymous sniper :-)

Michel.



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



From ietf-admin@ietf.org  Fri May 21 21:44:01 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18375
	for <ietf-archive@ietf.org>; Fri, 21 May 2004 21:44: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 1BRLYQ-0000Ac-Bu
	for ietf-archive@ietf.org; Fri, 21 May 2004 21:44:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRLXS-00003N-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 21:43:03 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRLX6-0007kP-00
	for ietf-archive@ietf.org; Fri, 21 May 2004 21:42:40 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRLKt-0004IO-4G; Fri, 21 May 2004 21:30:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRLEu-00038n-Ck
	for ietf@optimus.ietf.org; Fri, 21 May 2004 21:23:52 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA17647
	for <ietf@ietf.org>; Fri, 21 May 2004 21:23:49 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRLEr-0005u8-LL
	for ietf@ietf.org; Fri, 21 May 2004 21:23:49 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRLE6-0005ou-00
	for ietf@ietf.org; Fri, 21 May 2004 21:23:02 -0400
Received: from bdsl.66.12.25.131.gte.net ([66.12.25.131])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRLDL-0005jI-00
	for ietf@ietf.org; Fri, 21 May 2004 21:22:15 -0400
Received: by 2cah.com (MTSPro MTSAgent 1.60) ; Fri, 21 May 2004 20:31:50 -0500
    for <ietf@ietf.org>
Received: from shininglightpro.com (66.12.25.130, Peer IP=[24.11.219.156]) by 2cah.com (MTSPro MTSSmtp 1.61); Fri, 21 May 2004 20:31:41 -0500
    for <ietf@ietf.org>
Message-Id: <3.0.6.32.20040521212159.00b48010@mail.shininglightpro.com>
X-Sender: shinelight@mail.shininglightpro.com
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32)
Date: Fri, 21 May 2004 21:21:59 -0400
To: ietf@ietf.org
From: "Thomas J. Hruska" <shinelight@shininglightpro.com>
Subject: RE: respect privacy please !
In-Reply-To: <DD7FE473A8C3C245ADA2A2FE1709D90B0DB138@server2003.arneill-
 py.sacramento.ca.us>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Envelope-Sender: <shinelight@shininglightpro.com>
X-Envelope-Receiver: <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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-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 05:51 PM 5/21/2004 -0700, Michel Py writeth:
>> Tim Chown wrote:
>> The issue is someone knowing where I am for a week, in advance.
>
>I'm sure Osama would care about that, but do you mind explaining why you
>do? Hitmen are going to hunt you down? If there is a bounty on your
>head, consider allowing a fellow IETFer to get it instead of an
>anonymous sniper :-)

Why are bounties always for people's heads?  I mean, why can't there be a
bounty on someone's pinky toe?  The head is this big, bloated target, but
the pinky toe is far more challenging.  Anyone can snipe someone's head,
but it takes real aim to shoot someone else in the foot.

Hope this doesn't help!


          Thomas J. Hruska -- shinelight@shininglightpro.com
Shining Light Productions -- "Meeting the needs of fellow programmers"
                     http://www.slproweb.com/

`'*-~.,_,.~-*'`'*-~.,_,.~-*'`'*-~.,_,.~-*'`'*-~.,_,.~-*'`'*-~.,_,.~-*'`'*-~
  Why spend more for the same functionality that is in ColdFusion?
  Try Nuclear Vision today!

  http://www.slproweb.com/products/nvml.html

  Announcing Nuclear Vision v2.0:
  Easy to learn, easy to use, and has unlimited precision math
  capabilities.

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


From exim@www1.ietf.org  Fri May 21 21:44:08 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18392
	for <ietf-archive@odin.ietf.org>; Fri, 21 May 2004 21:44: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 1BRLX8-0006ZF-UT
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 21:42:43 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4M1ggJN025091
	for ietf-archive@odin.ietf.org; Fri, 21 May 2004 21: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 1BRLKt-0004IO-4G; Fri, 21 May 2004 21:30:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRLEu-00038n-Ck
	for ietf@optimus.ietf.org; Fri, 21 May 2004 21:23:52 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA17647
	for <ietf@ietf.org>; Fri, 21 May 2004 21:23:49 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRLEr-0005u8-LL
	for ietf@ietf.org; Fri, 21 May 2004 21:23:49 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRLE6-0005ou-00
	for ietf@ietf.org; Fri, 21 May 2004 21:23:02 -0400
Received: from bdsl.66.12.25.131.gte.net ([66.12.25.131])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRLDL-0005jI-00
	for ietf@ietf.org; Fri, 21 May 2004 21:22:15 -0400
Received: by 2cah.com (MTSPro MTSAgent 1.60) ; Fri, 21 May 2004 20:31:50 -0500
    for <ietf@ietf.org>
Received: from shininglightpro.com (66.12.25.130, Peer IP=[24.11.219.156]) by 2cah.com (MTSPro MTSSmtp 1.61); Fri, 21 May 2004 20:31:41 -0500
    for <ietf@ietf.org>
Message-Id: <3.0.6.32.20040521212159.00b48010@mail.shininglightpro.com>
X-Sender: shinelight@mail.shininglightpro.com
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32)
Date: Fri, 21 May 2004 21:21:59 -0400
To: ietf@ietf.org
From: "Thomas J. Hruska" <shinelight@shininglightpro.com>
Subject: RE: respect privacy please !
In-Reply-To: <DD7FE473A8C3C245ADA2A2FE1709D90B0DB138@server2003.arneill-
 py.sacramento.ca.us>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Envelope-Sender: <shinelight@shininglightpro.com>
X-Envelope-Receiver: <ietf@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
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 05:51 PM 5/21/2004 -0700, Michel Py writeth:
>> Tim Chown wrote:
>> The issue is someone knowing where I am for a week, in advance.
>
>I'm sure Osama would care about that, but do you mind explaining why you
>do? Hitmen are going to hunt you down? If there is a bounty on your
>head, consider allowing a fellow IETFer to get it instead of an
>anonymous sniper :-)

Why are bounties always for people's heads?  I mean, why can't there be a
bounty on someone's pinky toe?  The head is this big, bloated target, but
the pinky toe is far more challenging.  Anyone can snipe someone's head,
but it takes real aim to shoot someone else in the foot.

Hope this doesn't help!


          Thomas J. Hruska -- shinelight@shininglightpro.com
Shining Light Productions -- "Meeting the needs of fellow programmers"
                     http://www.slproweb.com/

`'*-~.,_,.~-*'`'*-~.,_,.~-*'`'*-~.,_,.~-*'`'*-~.,_,.~-*'`'*-~.,_,.~-*'`'*-~
  Why spend more for the same functionality that is in ColdFusion?
  Try Nuclear Vision today!

  http://www.slproweb.com/products/nvml.html

  Announcing Nuclear Vision v2.0:
  Easy to learn, easy to use, and has unlimited precision math
  capabilities.

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



From ietf-admin@ietf.org  Sat May 22 01:50: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 BAA00033
	for <ietf-archive@ietf.org>; Sat, 22 May 2004 01:50: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 1BRPOY-000639-19
	for ietf-archive@ietf.org; Sat, 22 May 2004 01:50:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRPNf-0005vs-00
	for ietf-archive@ietf.org; Sat, 22 May 2004 01:49:11 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRPNI-0005oB-00
	for ietf-archive@ietf.org; Sat, 22 May 2004 01:48:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRPGn-0001Sm-MN; Sat, 22 May 2004 01:42:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRPE6-0000kv-9p
	for ietf@optimus.ietf.org; Sat, 22 May 2004 01:39:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA29453
	for <ietf@ietf.org>; Sat, 22 May 2004 01:39: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 1BRPE2-0004Wc-Um
	for ietf@ietf.org; Sat, 22 May 2004 01:39:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRPDC-0004Od-00
	for ietf@ietf.org; Sat, 22 May 2004 01:38:23 -0400
Received: from adsl-1-22-168.dab.bellsouth.net ([65.1.22.168] helo=sleekfreak.ath.cx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRPCR-0004FA-00
	for ietf@ietf.org; Sat, 22 May 2004 01:37:35 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 1BRKWE-0002lB-00; Fri, 21 May 2004 20:37:42 -0400
Date: Fri, 21 May 2004 20:37:36 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: "Thomas J. Hruska" <shinelight@shininglightpro.com>
cc: ietf@ietf.org
Subject: RE: respect privacy please !
In-Reply-To: <3.0.6.32.20040521212159.00b48010@mail.shininglightpro.com>
Message-ID: <Pine.LNX.4.44.0405212035220.10612-100000@sleekfreak.ath.cx>
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=1.9 required=5.0 tests=AWL,WEIRD_PORT autolearn=no 
	version=2.60

Yes, but what about those of us who just show up, instead of registering?
We are able to maintain a modicum of privacy;)

On Fri, 21 May 2004, Thomas J. Hruska wrote:

> At 05:51 PM 5/21/2004 -0700, Michel Py writeth:
> >> Tim Chown wrote:
> >> The issue is someone knowing where I am for a week, in advance.
> >
> >I'm sure Osama would care about that, but do you mind explaining why you
> >do? Hitmen are going to hunt you down? If there is a bounty on your
> >head, consider allowing a fellow IETFer to get it instead of an
> >anonymous sniper :-)
>
> Why are bounties always for people's heads?  I mean, why can't there be a
> bounty on someone's pinky toe?  The head is this big, bloated target, but
> the pinky toe is far more challenging.  Anyone can snipe someone's head,
> but it takes real aim to shoot someone else in the foot.
>
> Hope this doesn't help!
>
>
>           Thomas J. Hruska -- shinelight@shininglightpro.com
> Shining Light Productions -- "Meeting the needs of fellow programmers"
>                      http://www.slproweb.com/
>
> `'*-~.,_,.~-*'`'*-~.,_,.~-*'`'*-~.,_,.~-*'`'*-~.,_,.~-*'`'*-~.,_,.~-*'`'*-~
>   Why spend more for the same functionality that is in ColdFusion?
>   Try Nuclear Vision today!
>
>   http://www.slproweb.com/products/nvml.html
>
>   Announcing Nuclear Vision v2.0:
>   Easy to learn, easy to use, and has unlimited precision math
>   capabilities.
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>

sleekfreak pirate broadcast
http://sleekfreak.ath.cx:81/


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


From exim@www1.ietf.org  Sat May 22 01:53: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 BAA00144
	for <ietf-archive@odin.ietf.org>; Sat, 22 May 2004 01:53: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 1BRPNK-00030u-Uf
	for ietf-archive@odin.ietf.org; Sat, 22 May 2004 01:48:51 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4M5moPL011440
	for ietf-archive@odin.ietf.org; Sat, 22 May 2004 01:48:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRPGn-0001Sm-MN; Sat, 22 May 2004 01:42:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRPE6-0000kv-9p
	for ietf@optimus.ietf.org; Sat, 22 May 2004 01:39:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA29453
	for <ietf@ietf.org>; Sat, 22 May 2004 01:39: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 1BRPE2-0004Wc-Um
	for ietf@ietf.org; Sat, 22 May 2004 01:39:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRPDC-0004Od-00
	for ietf@ietf.org; Sat, 22 May 2004 01:38:23 -0400
Received: from adsl-1-22-168.dab.bellsouth.net ([65.1.22.168] helo=sleekfreak.ath.cx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRPCR-0004FA-00
	for ietf@ietf.org; Sat, 22 May 2004 01:37:35 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 1BRKWE-0002lB-00; Fri, 21 May 2004 20:37:42 -0400
Date: Fri, 21 May 2004 20:37:36 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: "Thomas J. Hruska" <shinelight@shininglightpro.com>
cc: ietf@ietf.org
Subject: RE: respect privacy please !
In-Reply-To: <3.0.6.32.20040521212159.00b48010@mail.shininglightpro.com>
Message-ID: <Pine.LNX.4.44.0405212035220.10612-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=1.9 required=5.0 tests=WEIRD_PORT 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>

Yes, but what about those of us who just show up, instead of registering?
We are able to maintain a modicum of privacy;)

On Fri, 21 May 2004, Thomas J. Hruska wrote:

> At 05:51 PM 5/21/2004 -0700, Michel Py writeth:
> >> Tim Chown wrote:
> >> The issue is someone knowing where I am for a week, in advance.
> >
> >I'm sure Osama would care about that, but do you mind explaining why you
> >do? Hitmen are going to hunt you down? If there is a bounty on your
> >head, consider allowing a fellow IETFer to get it instead of an
> >anonymous sniper :-)
>
> Why are bounties always for people's heads?  I mean, why can't there be a
> bounty on someone's pinky toe?  The head is this big, bloated target, but
> the pinky toe is far more challenging.  Anyone can snipe someone's head,
> but it takes real aim to shoot someone else in the foot.
>
> Hope this doesn't help!
>
>
>           Thomas J. Hruska -- shinelight@shininglightpro.com
> Shining Light Productions -- "Meeting the needs of fellow programmers"
>                      http://www.slproweb.com/
>
> `'*-~.,_,.~-*'`'*-~.,_,.~-*'`'*-~.,_,.~-*'`'*-~.,_,.~-*'`'*-~.,_,.~-*'`'*-~
>   Why spend more for the same functionality that is in ColdFusion?
>   Try Nuclear Vision today!
>
>   http://www.slproweb.com/products/nvml.html
>
>   Announcing Nuclear Vision v2.0:
>   Easy to learn, easy to use, and has unlimited precision math
>   capabilities.
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>

sleekfreak pirate broadcast
http://sleekfreak.ath.cx:81/


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



From exim@www1.ietf.org  Sat May 22 05:13: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 FAA21951
	for <ietf-archive@odin.ietf.org>; Sat, 22 May 2004 05:13:55 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRSX8-00019P-Uz
	for ietf-archive@odin.ietf.org; Sat, 22 May 2004 05:11:11 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4M9BAqT004393
	for ietf-archive@odin.ietf.org; Sat, 22 May 2004 05:11:10 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRSOK-0007UM-5c; Sat, 22 May 2004 05:02:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRSFm-00066t-C5
	for ietf@optimus.ietf.org; Sat, 22 May 2004 04:53:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21303
	for <ietf@ietf.org>; Sat, 22 May 2004 04:53: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 1BRSFj-0006ke-56
	for ietf@ietf.org; Sat, 22 May 2004 04:53:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRSEl-0006cx-00
	for ietf@ietf.org; Sat, 22 May 2004 04:52:12 -0400
Received: from mail.consulintel.es ([213.172.48.142] helo=consulintel.es)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRSEY-0006Uz-00
	for ietf@ietf.org; Sat, 22 May 2004 04:51:59 -0400
Received: from consulintel02 ([217.126.187.160])
	(authenticated user jordi.palet@consulintel.es)
	by consulintel.es (consulintel.es [127.0.0.1])
	(MDaemon.PRO.v7.0.1.R)
	with ESMTP id md50000113159.msg
	for <ietf@ietf.org>; Sat, 22 May 2004 10:52:40 +0200
Message-ID: <163701c43fd9$e6a76640$8700000a@consulintel.es>
Reply-To: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
From: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
References: <8723A4EA11C8D7119DC80003470D204904A2909D@ex2beimcombx08>
Subject: Re: respect privacy please !
Date: Sat, 22 May 2004 10:50:49 +0200
Organization: Consulintel
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Spam-Processed: consulintel.es, Sat, 22 May 2004 10:52:40 +0200
	(not processed: message from valid local sender)
X-MDRemoteIP: 217.126.187.160
X-Return-Path: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
X-MDAV-Processed: consulintel.es, Sat, 22 May 2004 10:52:43 +0200
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-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

Hi Gordon,

I guess the interpretation of the law is unclear, but facts count. In Spain several sites had been closed/modified because they publish data, and they needed to pay very high penalizations (many million of Euros) because that.

Also I see more and more conferences not presenting this data, not just in the web site, but just printed in the documentation facilitated for the attendees.

I guess the policy in the web site is a must, I think is also a legal requirement if you are gathering the data (our lawyers asked us to put it in any registration page, because the single fact of now having that means also many million of Euros !).

Regards,
Jordi

----- Original Message -----=20
From: <Gordon.Lennox@cec.eu.int>
To: <jordi.palet@consulintel.es>; <ietf-admin@ietf.org>
Sent: Friday, May 21, 2004 6:59 PM
Subject: RE: respect privacy please !


> This is not an official view...
>=20
> European privacy laws basically say that personal data ought to be gathered
> with the explicit consent of the person, the amount of data should be
> appropriate for the declared purpose (not excessive) and not used for other
> purposes. They do not say you cannot gather personal data. They do not say
> you cannot publish personal data. There is probably a gray area of course if
> you publish information in a way that clearly facilitates further abuse.
>=20
> Given the style and purpose of the iETF a public record of registration
> (attendance?) may be appropriate, especially if the information published is
> very limited. i would expect  most people to understand why it is done.  But
> a statement to make it clear could be useful.
>=20
> There could of course be a problem if the IETF made *all* the information it
> gathered available to a third party, especially if nobody was asked for
> their permission. Somehow I never thought of this happening in this context.
>=20
> Personally I can also see an indication of the intended participation by
> some people as part of some justification for attending.=20
>=20
> On the other hand publishing the blue-sheets might be considered excessve!
> (RFID's in the badges anyone?<g>)
>=20
> Do we need a simple, very simple, statement of policy on the IETF web-site?
>=20
> Gordon
>=20
>=20
> -----Original Message-----
> From: ietf-admin@ietf.org
> To: ietf@ietf.org
> Sent: 5/21/04 5:08 PM
> Subject: Re: respect privacy please !
>=20
> Hi Harald,
>=20
> I'm not expert in legal stuff, but I think the European regulations (at
> least in Spain because I needed to learn this in order to host web sites
> with any kind of registration or list of people and comply with the
> law), there is no difference in publishing it before, during or after.
> Just can't be published w/o the consent of the participant.
>=20
> From a practical point of view, probably is good to do what John
> suggested, but alternatively also publishing only after the meetings
> will be a good protection for example to avoid a thief go to your home
> when you're in the IETF, as I recall somebody suggested was already
> happening in UK.
>=20
> I don't think a legal requirement for our process can jump over the
> laws. Is like if we decide that we need to sacrifice one of us in every
> meeting to sign the minutes with human blood, while we know that killing
> some one is forbidden. Yes I know ... is a quite exaggerated example,
> but some times is the best way to show what is wrong ;-)
>=20
> May be the 1st thing to do is to be really open in all the aspects, and
> that means clarifying our legal "situation", the terms under we take all
> the decisions, and so on.
>=20
> Regards,
> Jordi
>=20
> ----- Original Message -----=20
> From: "Harald Tveit Alvestrand" <harald@alvestrand.no>
> To: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>; <ietf@ietf.org>
> Sent: Friday, May 21, 2004 3:58 PM
> Subject: Re: respect privacy please !
>=20
>=20
> >=20
> >=20
> > --On 21. mai 2004 13:24 +0200 JORDI PALET MARTINEZ=20
> > <jordi.palet@consulintel.es> wrote:
> >=20
> > > Hi,
> > >
> > > I've already raised this some time ago, same as other people did,
> but I
> > > still see my name being published, w/o my consent, in the list of
> > > attendees.
> > >
> > > This is not acceptable, we should have the option to choose if we
> want to
> > > have our name published or not when we do the registration.
> >=20
> > Jordi,
> >=20
> > are you objecting to having your name published *at all*, or having
> your=20
> > name published *before the meeting*?
> >=20
> > The list of attendees (but not their contact info) is (according to
> the=20
> > lawyers) a legal requirement for our way of doing business; it is part
> of=20
> > the transparency requirement that it's possible to find out who was
> there.
> >=20
> >                       Harald
> >=20
> >=20
> >=20
> >=20
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www1.ietf.org/mailman/listinfo/ietf
> >=20
>=20
>=20
> **********************************
> Madrid 2003 Global IPv6 Summit
> Presentations and videos on line at:
> http://www.ipv6-es.com
>=20
> This electronic message contains information which may be privileged or
> confidential. The information is intended to be for the use of the
> individual(s) named above. If you are not the intended recipient be
> aware that any disclosure, copying, distribution or use of the contents
> of this information, including attached files, is prohibited.
>=20
>=20
>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>=20


**********************************
Madrid 2003 Global IPv6 Summit
Presentations and videos on line at:
http://www.ipv6-es.com

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.




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



From ietf-admin@ietf.org  Sat May 22 05:27: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 FAA22413
	for <ietf-archive@ietf.org>; Sat, 22 May 2004 05:27: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 1BRSmt-0003ju-Kq
	for ietf-archive@ietf.org; Sat, 22 May 2004 05:27:27 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRSls-0003S4-00
	for ietf-archive@ietf.org; Sat, 22 May 2004 05:26:26 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRSjq-000377-01
	for ietf-archive@ietf.org; Sat, 22 May 2004 05:24:18 -0400
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BRSXB-0004Pl-Nw
	for ietf-archive@ietf.org; Sat, 22 May 2004 05:11:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRSOK-0007UM-5c; Sat, 22 May 2004 05:02:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRSFm-00066t-C5
	for ietf@optimus.ietf.org; Sat, 22 May 2004 04:53:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21303
	for <ietf@ietf.org>; Sat, 22 May 2004 04:53: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 1BRSFj-0006ke-56
	for ietf@ietf.org; Sat, 22 May 2004 04:53:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRSEl-0006cx-00
	for ietf@ietf.org; Sat, 22 May 2004 04:52:12 -0400
Received: from mail.consulintel.es ([213.172.48.142] helo=consulintel.es)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRSEY-0006Uz-00
	for ietf@ietf.org; Sat, 22 May 2004 04:51:59 -0400
Received: from consulintel02 ([217.126.187.160])
	(authenticated user jordi.palet@consulintel.es)
	by consulintel.es (consulintel.es [127.0.0.1])
	(MDaemon.PRO.v7.0.1.R)
	with ESMTP id md50000113159.msg
	for <ietf@ietf.org>; Sat, 22 May 2004 10:52:40 +0200
Message-ID: <163701c43fd9$e6a76640$8700000a@consulintel.es>
Reply-To: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
From: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
References: <8723A4EA11C8D7119DC80003470D204904A2909D@ex2beimcombx08>
Subject: Re: respect privacy please !
Date: Sat, 22 May 2004 10:50:49 +0200
Organization: Consulintel
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Spam-Processed: consulintel.es, Sat, 22 May 2004 10:52:40 +0200
	(not processed: message from valid local sender)
X-MDRemoteIP: 217.126.187.160
X-Return-Path: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
X-MDAV-Processed: consulintel.es, Sat, 22 May 2004 10:52:43 +0200
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

Hi Gordon,

I guess the interpretation of the law is unclear, but facts count. In Spain several sites had been closed/modified because they publish data, and they needed to pay very high penalizations (many million of Euros) because that.

Also I see more and more conferences not presenting this data, not just in the web site, but just printed in the documentation facilitated for the attendees.

I guess the policy in the web site is a must, I think is also a legal requirement if you are gathering the data (our lawyers asked us to put it in any registration page, because the single fact of now having that means also many million of Euros !).

Regards,
Jordi

----- Original Message -----=20
From: <Gordon.Lennox@cec.eu.int>
To: <jordi.palet@consulintel.es>; <ietf-admin@ietf.org>
Sent: Friday, May 21, 2004 6:59 PM
Subject: RE: respect privacy please !


> This is not an official view...
>=20
> European privacy laws basically say that personal data ought to be gathered
> with the explicit consent of the person, the amount of data should be
> appropriate for the declared purpose (not excessive) and not used for other
> purposes. They do not say you cannot gather personal data. They do not say
> you cannot publish personal data. There is probably a gray area of course if
> you publish information in a way that clearly facilitates further abuse.
>=20
> Given the style and purpose of the iETF a public record of registration
> (attendance?) may be appropriate, especially if the information published is
> very limited. i would expect  most people to understand why it is done.  But
> a statement to make it clear could be useful.
>=20
> There could of course be a problem if the IETF made *all* the information it
> gathered available to a third party, especially if nobody was asked for
> their permission. Somehow I never thought of this happening in this context.
>=20
> Personally I can also see an indication of the intended participation by
> some people as part of some justification for attending.=20
>=20
> On the other hand publishing the blue-sheets might be considered excessve!
> (RFID's in the badges anyone?<g>)
>=20
> Do we need a simple, very simple, statement of policy on the IETF web-site?
>=20
> Gordon
>=20
>=20
> -----Original Message-----
> From: ietf-admin@ietf.org
> To: ietf@ietf.org
> Sent: 5/21/04 5:08 PM
> Subject: Re: respect privacy please !
>=20
> Hi Harald,
>=20
> I'm not expert in legal stuff, but I think the European regulations (at
> least in Spain because I needed to learn this in order to host web sites
> with any kind of registration or list of people and comply with the
> law), there is no difference in publishing it before, during or after.
> Just can't be published w/o the consent of the participant.
>=20
> From a practical point of view, probably is good to do what John
> suggested, but alternatively also publishing only after the meetings
> will be a good protection for example to avoid a thief go to your home
> when you're in the IETF, as I recall somebody suggested was already
> happening in UK.
>=20
> I don't think a legal requirement for our process can jump over the
> laws. Is like if we decide that we need to sacrifice one of us in every
> meeting to sign the minutes with human blood, while we know that killing
> some one is forbidden. Yes I know ... is a quite exaggerated example,
> but some times is the best way to show what is wrong ;-)
>=20
> May be the 1st thing to do is to be really open in all the aspects, and
> that means clarifying our legal "situation", the terms under we take all
> the decisions, and so on.
>=20
> Regards,
> Jordi
>=20
> ----- Original Message -----=20
> From: "Harald Tveit Alvestrand" <harald@alvestrand.no>
> To: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>; <ietf@ietf.org>
> Sent: Friday, May 21, 2004 3:58 PM
> Subject: Re: respect privacy please !
>=20
>=20
> >=20
> >=20
> > --On 21. mai 2004 13:24 +0200 JORDI PALET MARTINEZ=20
> > <jordi.palet@consulintel.es> wrote:
> >=20
> > > Hi,
> > >
> > > I've already raised this some time ago, same as other people did,
> but I
> > > still see my name being published, w/o my consent, in the list of
> > > attendees.
> > >
> > > This is not acceptable, we should have the option to choose if we
> want to
> > > have our name published or not when we do the registration.
> >=20
> > Jordi,
> >=20
> > are you objecting to having your name published *at all*, or having
> your=20
> > name published *before the meeting*?
> >=20
> > The list of attendees (but not their contact info) is (according to
> the=20
> > lawyers) a legal requirement for our way of doing business; it is part
> of=20
> > the transparency requirement that it's possible to find out who was
> there.
> >=20
> >                       Harald
> >=20
> >=20
> >=20
> >=20
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www1.ietf.org/mailman/listinfo/ietf
> >=20
>=20
>=20
> **********************************
> Madrid 2003 Global IPv6 Summit
> Presentations and videos on line at:
> http://www.ipv6-es.com
>=20
> This electronic message contains information which may be privileged or
> confidential. The information is intended to be for the use of the
> individual(s) named above. If you are not the intended recipient be
> aware that any disclosure, copying, distribution or use of the contents
> of this information, including attached files, is prohibited.
>=20
>=20
>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>=20


**********************************
Madrid 2003 Global IPv6 Summit
Presentations and videos on line at:
http://www.ipv6-es.com

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.




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


From ietf-admin@ietf.org  Sat May 22 07:05: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 HAA28845
	for <ietf-archive@ietf.org>; Sat, 22 May 2004 07:05: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 1BRUJa-0004Q2-0B
	for ietf-archive@ietf.org; Sat, 22 May 2004 07:05:18 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRUIg-0004CL-00
	for ietf-archive@ietf.org; Sat, 22 May 2004 07:04:22 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRUHn-0003wX-00
	for ietf-archive@ietf.org; Sat, 22 May 2004 07:03:27 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRU36-0000Ob-FG; Sat, 22 May 2004 06:48:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRTzQ-0007lB-Ry
	for ietf@optimus.ietf.org; Sat, 22 May 2004 06:44: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 GAA27459
	for <ietf@ietf.org>; Sat, 22 May 2004 06:44: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 1BRTzM-0000jt-K6
	for ietf@ietf.org; Sat, 22 May 2004 06:44:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRTyH-0000Z4-00
	for ietf@ietf.org; Sat, 22 May 2004 06:43:18 -0400
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRTxA-0000PE-00
	for ietf@ietf.org; Sat, 22 May 2004 06:42:08 -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 i4MAg9WE001364
	for <ietf@ietf.org>; Sat, 22 May 2004 11:42:09 +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 LAA16077
	for <ietf@ietf.org>; Sat, 22 May 2004 11:42:07 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id i4MAg7U05834
	for ietf@ietf.org; Sat, 22 May 2004 11:42:07 +0100
Date: Sat, 22 May 2004 11:42:07 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: ietf@ietf.org
Subject: Re: respect privacy please !
Message-ID: <20040522104206.GC5178@login.ecs.soton.ac.uk>
References: <0fa701c43f26$2939af90$8700000a@consulintel.es> <C920A0255CBCAF05FBEE6AC9@scan.jck.com> <40AE0C8C.6CFD72A3@swin.edu.au> <20040521145550.GB25670@login.ecs.soton.ac.uk> <40AE9DAE.41D764C7@swin.edu.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <40AE9DAE.41D764C7@swin.edu.au>
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 Sat, May 22, 2004 at 10:24:14AM +1000, grenville armitage wrote:
> 
> If your threat model postulates someone knowing enough about you to check
> for your IETF registration, then simply knowing when IETF meetings occur gives
> them a pretty good start. Testing your email account for 'out of office'
> replies gives them on-the-week confirmation. Just watching what you've
> been saying on ietf mailing lists leading up to the next scheduled IETF
> meeting can confirm their suspicions.

Not everyone attends every IETF.   Not everyone uses email autoreplies.
 
> I.e. hiding IETF registrations is hardly likely to impact on the threat offered
> to your personal security by anyone knowledgable enough about your behavior
> to be checking the IETF's online registrations list in the first place.

But there's no reason the list should be published in advance.
 
> But in any case, post-meeting release of the registration list would go
> along way to satisfying the goal of knowing "who was there".

The only issue seems to be people who want to check their *own* registration
status, and who didn't keep a record of their email confirmation.   There
are other ways to solve that.

Tim

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


From exim@www1.ietf.org  Sat May 22 07:13:01 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 HAA29192
	for <ietf-archive@odin.ietf.org>; Sat, 22 May 2004 07:13: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 1BRUHq-0002u7-HX
	for ietf-archive@odin.ietf.org; Sat, 22 May 2004 07:03:30 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4MB3Ugi011155
	for ietf-archive@odin.ietf.org; Sat, 22 May 2004 07:03:30 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRU36-0000Ob-FG; Sat, 22 May 2004 06:48:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRTzQ-0007lB-Ry
	for ietf@optimus.ietf.org; Sat, 22 May 2004 06:44: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 GAA27459
	for <ietf@ietf.org>; Sat, 22 May 2004 06:44: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 1BRTzM-0000jt-K6
	for ietf@ietf.org; Sat, 22 May 2004 06:44:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRTyH-0000Z4-00
	for ietf@ietf.org; Sat, 22 May 2004 06:43:18 -0400
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRTxA-0000PE-00
	for ietf@ietf.org; Sat, 22 May 2004 06:42:08 -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 i4MAg9WE001364
	for <ietf@ietf.org>; Sat, 22 May 2004 11:42:09 +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 LAA16077
	for <ietf@ietf.org>; Sat, 22 May 2004 11:42:07 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id i4MAg7U05834
	for ietf@ietf.org; Sat, 22 May 2004 11:42:07 +0100
Date: Sat, 22 May 2004 11:42:07 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: ietf@ietf.org
Subject: Re: respect privacy please !
Message-ID: <20040522104206.GC5178@login.ecs.soton.ac.uk>
References: <0fa701c43f26$2939af90$8700000a@consulintel.es> <C920A0255CBCAF05FBEE6AC9@scan.jck.com> <40AE0C8C.6CFD72A3@swin.edu.au> <20040521145550.GB25670@login.ecs.soton.ac.uk> <40AE9DAE.41D764C7@swin.edu.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <40AE9DAE.41D764C7@swin.edu.au>
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 Sat, May 22, 2004 at 10:24:14AM +1000, grenville armitage wrote:
> 
> If your threat model postulates someone knowing enough about you to check
> for your IETF registration, then simply knowing when IETF meetings occur gives
> them a pretty good start. Testing your email account for 'out of office'
> replies gives them on-the-week confirmation. Just watching what you've
> been saying on ietf mailing lists leading up to the next scheduled IETF
> meeting can confirm their suspicions.

Not everyone attends every IETF.   Not everyone uses email autoreplies.
 
> I.e. hiding IETF registrations is hardly likely to impact on the threat offered
> to your personal security by anyone knowledgable enough about your behavior
> to be checking the IETF's online registrations list in the first place.

But there's no reason the list should be published in advance.
 
> But in any case, post-meeting release of the registration list would go
> along way to satisfying the goal of knowing "who was there".

The only issue seems to be people who want to check their *own* registration
status, and who didn't keep a record of their email confirmation.   There
are other ways to solve that.

Tim

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



From ietf-admin@ietf.org  Sat May 22 08:12: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 IAA02812
	for <ietf-archive@ietf.org>; Sat, 22 May 2004 08:12: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 1BRVMS-0000b0-UJ
	for ietf-archive@ietf.org; Sat, 22 May 2004 08:12:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRVLU-0000QB-00
	for ietf-archive@ietf.org; Sat, 22 May 2004 08:11:21 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRVKk-0000G8-00
	for ietf-archive@ietf.org; Sat, 22 May 2004 08:10:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRV9Z-0005DM-Tq; Sat, 22 May 2004 07:59:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQx77-00009m-8E
	for ietf@optimus.ietf.org; Thu, 20 May 2004 19:38:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06185
	for <ietf@ietf.org>; Thu, 20 May 2004 19:38: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 1BQx74-0002zn-H5
	for ietf@ietf.org; Thu, 20 May 2004 19:38:10 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQx6B-0002vi-00
	for ietf@ietf.org; Thu, 20 May 2004 19:37:16 -0400
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQx5K-0002nN-00
	for ietf@ietf.org; Thu, 20 May 2004 19:36:22 -0400
Received: from bbfujip (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id i4KNZeS20251;
	Thu, 20 May 2004 16:35:41 -0700
Date: Thu, 20 May 2004 16:35:28 -0700
From: Dave Crocker <dhc@dcrocker.net>
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <852774956.20040520163528@brandenburg.com>
To: Leif Johansson <leifj@it.su.se>
CC: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>, ietf@ietf.org
Subject: Re: 60th IETF - Registration
In-Reply-To: <40AA6661.4000304@it.su.se>
References: 
 <DC55E4CF3BF32E46B6F1FA9028E35667626A@w3k.win3k.braintec-consult.de>
 <0b6001c43d05$f68ccd10$0402200a@consulintel.es> <40AA6661.4000304@it.su.se>
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.7 required=5.0 tests=AWL,PRIORITY_NO_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Leif,

LJ> Big hotels that are cheap and where the staff won't throw a fit
LJ> when we all turn up in force, laptops, duct-tape and all, don't
LJ> exactly grow on trees you know! I'm happy if it has a bar.


    that must be why we are going to one that costs US$ 179/night,
    with no secondary lodging listed.


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


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


From ietf-admin@ietf.org  Sat May 22 08:16: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 IAA03124
	for <ietf-archive@ietf.org>; Sat, 22 May 2004 08:16: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 1BRVQO-0001QA-5H
	for ietf-archive@ietf.org; Sat, 22 May 2004 08:16:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRVPZ-0001GJ-00
	for ietf-archive@ietf.org; Sat, 22 May 2004 08:15:34 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRVOk-00015N-00
	for ietf-archive@ietf.org; Sat, 22 May 2004 08:14:42 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRV9b-0005Db-CK; Sat, 22 May 2004 07:59:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQyyB-00021Q-NC
	for ietf@optimus.ietf.org; Thu, 20 May 2004 21:37:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11753
	for <ietf@ietf.org>; Thu, 20 May 2004 21:37: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 1BQyy8-0004Ae-Lb
	for ietf@ietf.org; Thu, 20 May 2004 21:37:04 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQyxB-000479-00
	for ietf@ietf.org; Thu, 20 May 2004 21:36:06 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQywa-00040Z-00
	for ietf@ietf.org; Thu, 20 May 2004 21:35:28 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id 85CB513DE5; Fri, 21 May 2004 01:34:58 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: Root Anycast
References: <20040520180125.9598.qmail@webmail-2-6.mesa1.secureserver.net>
From: Paul Vixie <vixie@vix.com>
Date: 21 May 2004 01:34:58 +0000
In-Reply-To: <20040520180125.9598.qmail@webmail-2-6.mesa1.secureserver.net>
Message-ID: <g365aqo94t.fsf@sa.vix.com>
Lines: 42
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: 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

y'know... if the people who have told me how glad they are that i've taken
certain loons and whackos to task here recently would cc the ietf@ list as
often as the people who have told me to stop feeding the trolls or the other
people who have told me that i lack manners...

                                           ...then we could have a real food
fight here, which would help nobody and construct nothing.  so, thanks for
your good wishes, and i understand your motives for keeping it just twixt us.

anyway, bill@strahm.net writes:

> This is twice in two days now.

actually it's about once a year.

once a year it occurs to me that we have a hoard of new lurkers -- a new
gallery, if you will.  and as i watch posts from loons and whackos go
largely unanswered, it further occurs to me that some of these lurkers
might be confused as to why posts on certain topics, or posts from certain
authors, seem to die without much argument even though the articles are
clearly provocative in their content.

the reasons vary.  many long time ietf@ participants have seen these
threads before and just ignore them.  many others are wary of getting mail
asking them "please don't feel the trolls" and so they stay silent.  some
others have configured their mail tools to eradicate all evidence of certain
other participants, including original text, followups, or quoted text.

but to a lurker, none of this is necessarily obvious.  for all "they" know,
the reason noone answers is that the whackos and loons have stated their case
so brilliantly that no answer is possible.  so while it's clear without
context that most people are hoping that threads will just die, there's
possible ambiguity as to the reason for this widespread hope.

let there be no ambiguity.  the reason i'm not answering these whackos and
loons, and the reason most often given to me by others why they don't answer,
is that "you should never try to teach a pig to sing, because it wastes your
time and annoys the pig." (RAH, writing as LL)

and until next spring or early summer, i'll be content to leave it at that.
-- 
Paul Vixie

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


From ietf-admin@ietf.org  Sat May 22 08:19: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 IAA03297
	for <ietf-archive@ietf.org>; Sat, 22 May 2004 08:19:24 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRVTJ-0001wD-Sw
	for ietf-archive@ietf.org; Sat, 22 May 2004 08:19:25 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRVSU-0001mC-00
	for ietf-archive@ietf.org; Sat, 22 May 2004 08:18:35 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRVRn-0001br-00
	for ietf-archive@ietf.org; Sat, 22 May 2004 08:17:51 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRV9c-0005Dr-Ie; Sat, 22 May 2004 07:59:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRC2q-0003N5-5r
	for ietf@optimus.ietf.org; Fri, 21 May 2004 11:34: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 LAA09416
	for <ietf@ietf.org>; Fri, 21 May 2004 11:34:45 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRC2p-0006Vw-0y
	for ietf@ietf.org; Fri, 21 May 2004 11:34:47 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRC1t-0006SC-00
	for ietf@ietf.org; Fri, 21 May 2004 11:33:49 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRC1O-0006P7-00
	for ietf@ietf.org; Fri, 21 May 2004 11:33:18 -0400
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1BRC1N-0007gn-00; Fri, 21 May 2004 10:33:17 -0500
Date: Fri, 21 May 2004 11:33:14 -0400
From: John C Klensin <john@jck.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>, ietf@ietf.org
Subject: Re: respect privacy please !
Message-ID: <970C9F77980BFAC803543C7D@scan.jck.com>
In-Reply-To: <20040521145550.GB25670@login.ecs.soton.ac.uk>
References: <0fa701c43f26$2939af90$8700000a@consulintel.es>
 <C920A0255CBCAF05FBEE6AC9@scan.jck.com>
 <40AE0C8C.6CFD72A3@swin.edu.au>
 <20040521145550.GB25670@login.ecs.soton.ac.uk>
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=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit



--On Friday, 21 May, 2004 15:55 +0100 Tim Chown 
<tjc@ecs.soton.ac.uk> wrote:

> On Sat, May 22, 2004 at 12:05:00AM +1000, grenville armitage
> wrote:
>>
>> This could be solved by the IETF insisting that consent is
>> required before attendance. I, like John, do not believe it
>> is acceptable for the IETF meetings to be populated by
>> anonymous attendees.
>
> The issue is someone knowing where I am for a week, in advance.
>
> Harald's suggestion of releasing the list post-event is an
> improvement...

Hmm.  Being paranoid about folks who arrive or depart in black 
helicopters (despite being accused in the past of being one of 
that group), post-meeting feels too late to me.   But, other 
than whatever additional burdens it adds for the Secretariat, I 
can see almost no objection to keeping the list confidential 
until Sunday afternoon or early Monday of the meeting week.

However, before we say "that is a wonderful idea" (or not), 
let's remember the substance of several of the "IETF 
administration" notes and documents that have been circulated in 
the last several months.  If I understand those materials and 
discussions correctly, the Secretariat is stretched pretty thin, 
there are no spare dollars floating around, few if any of us are 
anxious to see increased meeting fees, and I gather that almost 
every request for something new involves a decision about what 
doesn't get done instead.  Even when there has been a perception 
of lots of resources, the Secretariat has, for as long as I can 
remember, been flat-out during the few days before and after an 
IETF meeting starts.  So "post Sunday afternoon" is possibly 
unworkable in practice unless it can be turned over to some 
automated process... and I don't know if the database structure 
lends itself to that without considerable work.

Moreover, I've several times noticed a significant advantage of 
having _my_ name and payment status listed -- it provides an 
easy way for me to check on whether I've registered and paid or 
whether I let it fall through the cracks.  So, for purely 
pragmatic reasons, I'd hate to see the advanced registration 
list taken down unless there is an easy and automated way for me 
to inquire as to whether or not I'm correctly registered. Or the 
_advanced_ registration list could be made opt-out until Sunday, 
and then posted with all names listed.  But either probably 
implies more Secretariat work, even if we don't care much about 
the security (authenticity) of the query in the former case.

So, how important is this, really?  For most of the regular 
attendees, someone wanting to know that you will be away for a 
week and when needs only to determine when an IETF meeting is 
being held.  That isn't 100% reliable, of course, but, because 
you can register (and even pay) and then not come (and I gather 
a significant number of people do so every time), neither is the 
current list.

Speaking for myself only, of course.

best,
    john



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


From ietf-admin@ietf.org  Sat May 22 08:21: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 IAA03387
	for <ietf-archive@ietf.org>; Sat, 22 May 2004 08:21: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 1BRVVN-0002JB-Rb
	for ietf-archive@ietf.org; Sat, 22 May 2004 08:21:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRVUN-00028B-00
	for ietf-archive@ietf.org; Sat, 22 May 2004 08:20:32 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRVTx-0001xS-00
	for ietf-archive@ietf.org; Sat, 22 May 2004 08:20:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRV9e-0005E3-7p; Sat, 22 May 2004 07: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 1BRM97-0005za-AG
	for ietf@optimus.ietf.org; Fri, 21 May 2004 22:21:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20532
	for <ietf@ietf.org>; Fri, 21 May 2004 22:21: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 1BRM93-0004hY-UN
	for ietf@ietf.org; Fri, 21 May 2004 22:21:54 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRM8A-0004cY-00
	for ietf@ietf.org; Fri, 21 May 2004 22:20:59 -0400
Received: from rwcrmhc13.comcast.net ([204.127.198.39])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRM7x-0004Wn-00
	for ietf@ietf.org; Fri, 21 May 2004 22:20:45 -0400
Received: from dfnjgl21 (c-24-1-99-5.client.comcast.net[24.1.99.5])
          by comcast.net (rwcrmhc13) with SMTP
          id <20040522022015015007isade>
          (Authid: sdawkins@comcast.net);
          Sat, 22 May 2004 02:20:15 +0000
Message-ID: <094301c43fa3$7054a0b0$0200a8c0@DFNJGL21>
Reply-To: "Spencer Dawkins" <spencer@mcsr-labs.org>
From: "Spencer Dawkins" <spencer@mcsr-labs.org>
To: <ietf@ietf.org>
References: <0fa701c43f26$2939af90$8700000a@consulintel.es> <335417014.1085122709@localhost> <128901c43f45$8b640de0$8700000a@consulintel.es>
Subject: Re: respect privacy please !
Date: Fri, 21 May 2004 21:21:03 -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

Dear Harald,

From: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
Sent: Friday, May 21, 2004 10:08 AM
Subject: Re: respect privacy please !

>
> I don't think a legal requirement for our process can jump over the
laws. Is like if we
> decide that we need to sacrifice one of us in every meeting to sign
the minutes with human
> blood, while we know that killing some one is forbidden.

Given the right choice of sacrificial victims, this could be a
spectacular introduction for the first experiment under
draft-klensin-process-july14-02.txt...

But let's not go there for now, OK?

Spencer



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


From exim@www1.ietf.org  Sat May 22 08:23:41 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03575
	for <ietf-archive@odin.ietf.org>; Sat, 22 May 2004 08:23:41 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRVKl-0007ZN-5V
	for ietf-archive@odin.ietf.org; Sat, 22 May 2004 08:10:41 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4MCAZhT029076
	for ietf-archive@odin.ietf.org; Sat, 22 May 2004 08:10:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRV9Z-0005DM-Tq; Sat, 22 May 2004 07:59:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQx77-00009m-8E
	for ietf@optimus.ietf.org; Thu, 20 May 2004 19:38:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06185
	for <ietf@ietf.org>; Thu, 20 May 2004 19:38: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 1BQx74-0002zn-H5
	for ietf@ietf.org; Thu, 20 May 2004 19:38:10 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQx6B-0002vi-00
	for ietf@ietf.org; Thu, 20 May 2004 19:37:16 -0400
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQx5K-0002nN-00
	for ietf@ietf.org; Thu, 20 May 2004 19:36:22 -0400
Received: from bbfujip (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id i4KNZeS20251;
	Thu, 20 May 2004 16:35:41 -0700
Date: Thu, 20 May 2004 16:35:28 -0700
From: Dave Crocker <dhc@dcrocker.net>
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <852774956.20040520163528@brandenburg.com>
To: Leif Johansson <leifj@it.su.se>
CC: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>, ietf@ietf.org
Subject: Re: 60th IETF - Registration
In-Reply-To: <40AA6661.4000304@it.su.se>
References: 
 <DC55E4CF3BF32E46B6F1FA9028E35667626A@w3k.win3k.braintec-consult.de>
 <0b6001c43d05$f68ccd10$0402200a@consulintel.es> <40AA6661.4000304@it.su.se>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.7 required=5.0 tests=AWL,PRIORITY_NO_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: 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

Leif,

LJ> Big hotels that are cheap and where the staff won't throw a fit
LJ> when we all turn up in force, laptops, duct-tape and all, don't
LJ> exactly grow on trees you know! I'm happy if it has a bar.


    that must be why we are going to one that costs US$ 179/night,
    with no secondary lodging listed.


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


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



From exim@www1.ietf.org  Sat May 22 08:23:46 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03602
	for <ietf-archive@odin.ietf.org>; Sat, 22 May 2004 08:23: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 1BRVOl-0000Hw-3r
	for ietf-archive@odin.ietf.org; Sat, 22 May 2004 08:14:43 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4MCEhjZ001082
	for ietf-archive@odin.ietf.org; Sat, 22 May 2004 08:14:43 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRV9b-0005Db-CK; Sat, 22 May 2004 07:59:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BQyyB-00021Q-NC
	for ietf@optimus.ietf.org; Thu, 20 May 2004 21:37:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11753
	for <ietf@ietf.org>; Thu, 20 May 2004 21:37: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 1BQyy8-0004Ae-Lb
	for ietf@ietf.org; Thu, 20 May 2004 21:37:04 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BQyxB-000479-00
	for ietf@ietf.org; Thu, 20 May 2004 21:36:06 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BQywa-00040Z-00
	for ietf@ietf.org; Thu, 20 May 2004 21:35:28 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id 85CB513DE5; Fri, 21 May 2004 01:34:58 +0000 (GMT)
To: ietf@ietf.org
Subject: Re: Root Anycast
References: <20040520180125.9598.qmail@webmail-2-6.mesa1.secureserver.net>
From: Paul Vixie <vixie@vix.com>
Date: 21 May 2004 01:34:58 +0000
In-Reply-To: <20040520180125.9598.qmail@webmail-2-6.mesa1.secureserver.net>
Message-ID: <g365aqo94t.fsf@sa.vix.com>
Lines: 42
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-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>

y'know... if the people who have told me how glad they are that i've taken
certain loons and whackos to task here recently would cc the ietf@ list as
often as the people who have told me to stop feeding the trolls or the other
people who have told me that i lack manners...

                                           ...then we could have a real food
fight here, which would help nobody and construct nothing.  so, thanks for
your good wishes, and i understand your motives for keeping it just twixt us.

anyway, bill@strahm.net writes:

> This is twice in two days now.

actually it's about once a year.

once a year it occurs to me that we have a hoard of new lurkers -- a new
gallery, if you will.  and as i watch posts from loons and whackos go
largely unanswered, it further occurs to me that some of these lurkers
might be confused as to why posts on certain topics, or posts from certain
authors, seem to die without much argument even though the articles are
clearly provocative in their content.

the reasons vary.  many long time ietf@ participants have seen these
threads before and just ignore them.  many others are wary of getting mail
asking them "please don't feel the trolls" and so they stay silent.  some
others have configured their mail tools to eradicate all evidence of certain
other participants, including original text, followups, or quoted text.

but to a lurker, none of this is necessarily obvious.  for all "they" know,
the reason noone answers is that the whackos and loons have stated their case
so brilliantly that no answer is possible.  so while it's clear without
context that most people are hoping that threads will just die, there's
possible ambiguity as to the reason for this widespread hope.

let there be no ambiguity.  the reason i'm not answering these whackos and
loons, and the reason most often given to me by others why they don't answer,
is that "you should never try to teach a pig to sing, because it wastes your
time and annoys the pig." (RAH, writing as LL)

and until next spring or early summer, i'll be content to leave it at that.
-- 
Paul Vixie

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



From exim@www1.ietf.org  Sat May 22 08:23:49 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03630
	for <ietf-archive@odin.ietf.org>; Sat, 22 May 2004 08:23:49 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRVRo-00011K-81
	for ietf-archive@odin.ietf.org; Sat, 22 May 2004 08:17:53 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4MCHqGv003913
	for ietf-archive@odin.ietf.org; Sat, 22 May 2004 08:17:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRV9c-0005Dr-Ie; Sat, 22 May 2004 07:59:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRC2q-0003N5-5r
	for ietf@optimus.ietf.org; Fri, 21 May 2004 11:34: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 LAA09416
	for <ietf@ietf.org>; Fri, 21 May 2004 11:34:45 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRC2p-0006Vw-0y
	for ietf@ietf.org; Fri, 21 May 2004 11:34:47 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRC1t-0006SC-00
	for ietf@ietf.org; Fri, 21 May 2004 11:33:49 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRC1O-0006P7-00
	for ietf@ietf.org; Fri, 21 May 2004 11:33:18 -0400
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1BRC1N-0007gn-00; Fri, 21 May 2004 10:33:17 -0500
Date: Fri, 21 May 2004 11:33:14 -0400
From: John C Klensin <john@jck.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>, ietf@ietf.org
Subject: Re: respect privacy please !
Message-ID: <970C9F77980BFAC803543C7D@scan.jck.com>
In-Reply-To: <20040521145550.GB25670@login.ecs.soton.ac.uk>
References: <0fa701c43f26$2939af90$8700000a@consulintel.es>
 <C920A0255CBCAF05FBEE6AC9@scan.jck.com>
 <40AE0C8C.6CFD72A3@swin.edu.au>
 <20040521145550.GB25670@login.ecs.soton.ac.uk>
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=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 Friday, 21 May, 2004 15:55 +0100 Tim Chown 
<tjc@ecs.soton.ac.uk> wrote:

> On Sat, May 22, 2004 at 12:05:00AM +1000, grenville armitage
> wrote:
>>
>> This could be solved by the IETF insisting that consent is
>> required before attendance. I, like John, do not believe it
>> is acceptable for the IETF meetings to be populated by
>> anonymous attendees.
>
> The issue is someone knowing where I am for a week, in advance.
>
> Harald's suggestion of releasing the list post-event is an
> improvement...

Hmm.  Being paranoid about folks who arrive or depart in black 
helicopters (despite being accused in the past of being one of 
that group), post-meeting feels too late to me.   But, other 
than whatever additional burdens it adds for the Secretariat, I 
can see almost no objection to keeping the list confidential 
until Sunday afternoon or early Monday of the meeting week.

However, before we say "that is a wonderful idea" (or not), 
let's remember the substance of several of the "IETF 
administration" notes and documents that have been circulated in 
the last several months.  If I understand those materials and 
discussions correctly, the Secretariat is stretched pretty thin, 
there are no spare dollars floating around, few if any of us are 
anxious to see increased meeting fees, and I gather that almost 
every request for something new involves a decision about what 
doesn't get done instead.  Even when there has been a perception 
of lots of resources, the Secretariat has, for as long as I can 
remember, been flat-out during the few days before and after an 
IETF meeting starts.  So "post Sunday afternoon" is possibly 
unworkable in practice unless it can be turned over to some 
automated process... and I don't know if the database structure 
lends itself to that without considerable work.

Moreover, I've several times noticed a significant advantage of 
having _my_ name and payment status listed -- it provides an 
easy way for me to check on whether I've registered and paid or 
whether I let it fall through the cracks.  So, for purely 
pragmatic reasons, I'd hate to see the advanced registration 
list taken down unless there is an easy and automated way for me 
to inquire as to whether or not I'm correctly registered. Or the 
_advanced_ registration list could be made opt-out until Sunday, 
and then posted with all names listed.  But either probably 
implies more Secretariat work, even if we don't care much about 
the security (authenticity) of the query in the former case.

So, how important is this, really?  For most of the regular 
attendees, someone wanting to know that you will be away for a 
week and when needs only to determine when an IETF meeting is 
being held.  That isn't 100% reliable, of course, but, because 
you can register (and even pay) and then not come (and I gather 
a significant number of people do so every time), neither is the 
current list.

Speaking for myself only, of course.

best,
    john



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



From exim@www1.ietf.org  Sat May 22 10:53:05 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 KAA10923
	for <ietf-archive@odin.ietf.org>; Sat, 22 May 2004 10:53: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 1BRXqS-0005j3-7f
	for ietf-archive@odin.ietf.org; Sat, 22 May 2004 10:51:28 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4MEpS3f022007
	for ietf-archive@odin.ietf.org; Sat, 22 May 2004 10:51:28 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRXcp-0002fb-30; Sat, 22 May 2004 10:37:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRXZ5-0001Zq-13
	for ietf@optimus.ietf.org; Sat, 22 May 2004 10:33:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10055
	for <ietf@ietf.org>; Sat, 22 May 2004 10:33: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 1BRXZ2-00017x-K3
	for ietf@ietf.org; Sat, 22 May 2004 10:33:28 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRXYB-0000xw-00
	for ietf@ietf.org; Sat, 22 May 2004 10:32:36 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRXXZ-0000mm-00
	for ietf@ietf.org; Sat, 22 May 2004 10:31:57 -0400
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1BRXXY-000Atb-00; Sat, 22 May 2004 09:31:56 -0500
Date: Sat, 22 May 2004 10:31:54 -0400
From: John C Klensin <john-ietf@jck.com>
To: Spencer Dawkins <spencer@mcsr-labs.org>, ietf@ietf.org
Subject: Re: respect privacy please !
Message-ID: <44B38B0B2A7142BFB7245E67@scan.jck.com>
In-Reply-To: <094301c43fa3$7054a0b0$0200a8c0@DFNJGL21>
References: <0fa701c43f26$2939af90$8700000a@consulintel.es>
 <335417014.1085122709@localhost>
 <128901c43f45$8b640de0$8700000a@consulintel.es>
 <094301c43fa3$7054a0b0$0200a8c0@DFNJGL21>
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

Spencer,

I may be just misunderstanding your sense of humor, but it seems 
to me that any sort of formal experimental process is too 
heavyweight for this, or at least the core issue.  It seems to 
me that what we have is...

	* Jordi noticed a problem and pointed it out.
	
	* Harald indicated that the core issue had been noticed
	before and fixed, but the fix had apparently come
	unglued between the last meeting and this one... without
	anyone but Jordi noticing.
	
	* Some further discussion then suggested that "get
	explicit consent as a condition of registration" was
	probably better, and certainly no worse, than "notifying
	people about what will happen".

I assume that, by now, Harald has told the Secretariat to apply 
a fix.  I hope they aren't sitting on the request or, if they 
are, that we will rapidly see an explanation.

We've also had an almost-separate discussion as to whether it is 
necessary/ desirable to post names at the time of registration 
or whether it can be deferred until just before or just after 
the meeting.  And there has been discussion that having the 
information visible from registration time forward is of 
advantage to some people -- whether checking on one's own 
registrations, checking on organizational ones, or deciding to 
come or not based on the presence or absence of others on the 
list.   We don't appear to have consensus on the subject of 
desirability.  And, on the feasibility part of the question, it 
seems to me that one key question is about what is feasible 
given other priorities and limited resources.  I hope we hear 
from the secretariat and the IESG about that, but, at the 
moment, I'm waiting.

So what is there that seems to justify an experimental 
procedure?  This seems to me to fall much more into the "just do 
it" (or, indeed, "fix screwup") category for the matter of 
consent or notification and into the "no consensus" one for the 
matter of posting time.

     john


--On Friday, 21 May, 2004 21:21 -0500 Spencer Dawkins 
<spencer@mcsr-labs.org> wrote:

> Dear Harald,
>
> From: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
> To: <ietf@ietf.org>
> Sent: Friday, May 21, 2004 10:08 AM
> Subject: Re: respect privacy please !
>
>>
>> I don't think a legal requirement for our process can jump
>> over the
> laws. Is like if we
>> decide that we need to sacrifice one of us in every meeting
>> to sign
> the minutes with human
>> blood, while we know that killing some one is forbidden.
>
> Given the right choice of sacrificial victims, this could be a
> spectacular introduction for the first experiment under
> draft-klensin-process-july14-02.txt...
>
> But let's not go there for now, OK?
>
> Spencer
>
>
>
> _______________________________________________
> 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  Sat May 22 10:54: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 KAA11041
	for <ietf-archive@ietf.org>; Sat, 22 May 2004 10:54: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 1BRXsw-0004vb-I8
	for ietf-archive@ietf.org; Sat, 22 May 2004 10:54:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRXrk-0004eB-00
	for ietf-archive@ietf.org; Sat, 22 May 2004 10:52:49 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRXqQ-0004NN-00
	for ietf-archive@ietf.org; Sat, 22 May 2004 10:51:26 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRXcp-0002fb-30; Sat, 22 May 2004 10:37:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRXZ5-0001Zq-13
	for ietf@optimus.ietf.org; Sat, 22 May 2004 10:33:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10055
	for <ietf@ietf.org>; Sat, 22 May 2004 10:33: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 1BRXZ2-00017x-K3
	for ietf@ietf.org; Sat, 22 May 2004 10:33:28 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRXYB-0000xw-00
	for ietf@ietf.org; Sat, 22 May 2004 10:32:36 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRXXZ-0000mm-00
	for ietf@ietf.org; Sat, 22 May 2004 10:31:57 -0400
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.10)
	id 1BRXXY-000Atb-00; Sat, 22 May 2004 09:31:56 -0500
Date: Sat, 22 May 2004 10:31:54 -0400
From: John C Klensin <john-ietf@jck.com>
To: Spencer Dawkins <spencer@mcsr-labs.org>, ietf@ietf.org
Subject: Re: respect privacy please !
Message-ID: <44B38B0B2A7142BFB7245E67@scan.jck.com>
In-Reply-To: <094301c43fa3$7054a0b0$0200a8c0@DFNJGL21>
References: <0fa701c43f26$2939af90$8700000a@consulintel.es>
 <335417014.1085122709@localhost>
 <128901c43f45$8b640de0$8700000a@consulintel.es>
 <094301c43fa3$7054a0b0$0200a8c0@DFNJGL21>
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

Spencer,

I may be just misunderstanding your sense of humor, but it seems 
to me that any sort of formal experimental process is too 
heavyweight for this, or at least the core issue.  It seems to 
me that what we have is...

	* Jordi noticed a problem and pointed it out.
	
	* Harald indicated that the core issue had been noticed
	before and fixed, but the fix had apparently come
	unglued between the last meeting and this one... without
	anyone but Jordi noticing.
	
	* Some further discussion then suggested that "get
	explicit consent as a condition of registration" was
	probably better, and certainly no worse, than "notifying
	people about what will happen".

I assume that, by now, Harald has told the Secretariat to apply 
a fix.  I hope they aren't sitting on the request or, if they 
are, that we will rapidly see an explanation.

We've also had an almost-separate discussion as to whether it is 
necessary/ desirable to post names at the time of registration 
or whether it can be deferred until just before or just after 
the meeting.  And there has been discussion that having the 
information visible from registration time forward is of 
advantage to some people -- whether checking on one's own 
registrations, checking on organizational ones, or deciding to 
come or not based on the presence or absence of others on the 
list.   We don't appear to have consensus on the subject of 
desirability.  And, on the feasibility part of the question, it 
seems to me that one key question is about what is feasible 
given other priorities and limited resources.  I hope we hear 
from the secretariat and the IESG about that, but, at the 
moment, I'm waiting.

So what is there that seems to justify an experimental 
procedure?  This seems to me to fall much more into the "just do 
it" (or, indeed, "fix screwup") category for the matter of 
consent or notification and into the "no consensus" one for the 
matter of posting time.

     john


--On Friday, 21 May, 2004 21:21 -0500 Spencer Dawkins 
<spencer@mcsr-labs.org> wrote:

> Dear Harald,
>
> From: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
> To: <ietf@ietf.org>
> Sent: Friday, May 21, 2004 10:08 AM
> Subject: Re: respect privacy please !
>
>>
>> I don't think a legal requirement for our process can jump
>> over the
> laws. Is like if we
>> decide that we need to sacrifice one of us in every meeting
>> to sign
> the minutes with human
>> blood, while we know that killing some one is forbidden.
>
> Given the right choice of sacrificial victims, this could be a
> spectacular introduction for the first experiment under
> draft-klensin-process-july14-02.txt...
>
> But let's not go there for now, OK?
>
> Spencer
>
>
>
> _______________________________________________
> 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  Sat May 22 15:09: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 PAA22083
	for <ietf-archive@ietf.org>; Sat, 22 May 2004 15:09: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 1BRbsI-0006km-DA
	for ietf-archive@ietf.org; Sat, 22 May 2004 15:09:38 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRbrT-0006XG-00
	for ietf-archive@ietf.org; Sat, 22 May 2004 15:08:48 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRbqA-00069Z-00
	for ietf-archive@ietf.org; Sat, 22 May 2004 15:07:26 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRbj1-0002yI-NA; Sat, 22 May 2004 15:00:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRbhh-0002jr-BF
	for ietf@optimus.ietf.org; Sat, 22 May 2004 14:58: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 OAA21197
	for <ietf@ietf.org>; Sat, 22 May 2004 14:58: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 1BRbhe-0004Sn-65
	for ietf@ietf.org; Sat, 22 May 2004 14:58:38 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRbge-0004Go-00
	for ietf@ietf.org; Sat, 22 May 2004 14:57:36 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRbfy-0003sh-00
	for ietf@ietf.org; Sat, 22 May 2004 14:56:54 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 949E4621ED; Sat, 22 May 2004 20:56:23 +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 17333-04; Sat, 22 May 2004 20:56:22 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id D3A4D61AA5; Sat, 22 May 2004 20:56:20 +0200 (CEST)
Date: Sat, 22 May 2004 11:42:15 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: John C Klensin <john-ietf@jck.com>,
        Spencer Dawkins <spencer@mcsr-labs.org>, ietf@ietf.org
Subject: Re: respect privacy please !
Message-ID: <438876931.1085226135@localhost>
In-Reply-To: <44B38B0B2A7142BFB7245E67@scan.jck.com>
References: <0fa701c43f26$2939af90$8700000a@consulintel.es>
 <335417014.1085122709@localhost>
 <128901c43f45$8b640de0$8700000a@consulintel.es>
 <094301c43fa3$7054a0b0$0200a8c0@DFNJGL21>
 <44B38B0B2A7142BFB7245E67@scan.jck.com>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
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 22. mai 2004 10:31 -0400 John C Klensin <john-ietf@jck.com> wrote:

> Spencer,
>
> I may be just misunderstanding your sense of humor, but it seems to me
> that any sort of formal experimental process is too heavyweight for this,
> or at least the core issue.  It seems to me that what we have is...
>
> 	* Jordi noticed a problem and pointed it out.
> 	
> 	* Harald indicated that the core issue had been noticed
> 	before and fixed, but the fix had apparently come
> 	unglued between the last meeting and this one... without
> 	anyone but Jordi noticing.
> 	
> 	* Some further discussion then suggested that "get
> 	explicit consent as a condition of registration" was
> 	probably better, and certainly no worse, than "notifying
> 	people about what will happen".
>
> I assume that, by now, Harald has told the Secretariat to apply a fix.  I
> hope they aren't sitting on the request or, if they are, that we will
> rapidly see an explanation.

actually the fix request had gotten lost in the first round - it was never 
applied to the Seoul web pages, and nobody noticed.
Guess what.... it had been deleted along with a bunch of spam...... points 
out the importance of improving the secretariat's spamfiltering abilities, 
as per the announcement on Friday.

The fix has now been applied.

                   Harald





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


From exim@www1.ietf.org  Sat May 22 15:11: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 PAA22286
	for <ietf-archive@odin.ietf.org>; Sat, 22 May 2004 15:11: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 1BRbqC-0004Wc-Dk
	for ietf-archive@odin.ietf.org; Sat, 22 May 2004 15:07:34 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4MJ7S1H017387
	for ietf-archive@odin.ietf.org; Sat, 22 May 2004 15:07:28 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRbj1-0002yI-NA; Sat, 22 May 2004 15:00:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRbhh-0002jr-BF
	for ietf@optimus.ietf.org; Sat, 22 May 2004 14:58: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 OAA21197
	for <ietf@ietf.org>; Sat, 22 May 2004 14:58: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 1BRbhe-0004Sn-65
	for ietf@ietf.org; Sat, 22 May 2004 14:58:38 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRbge-0004Go-00
	for ietf@ietf.org; Sat, 22 May 2004 14:57:36 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRbfy-0003sh-00
	for ietf@ietf.org; Sat, 22 May 2004 14:56:54 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 949E4621ED; Sat, 22 May 2004 20:56:23 +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 17333-04; Sat, 22 May 2004 20:56:22 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id D3A4D61AA5; Sat, 22 May 2004 20:56:20 +0200 (CEST)
Date: Sat, 22 May 2004 11:42:15 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: John C Klensin <john-ietf@jck.com>,
        Spencer Dawkins <spencer@mcsr-labs.org>, ietf@ietf.org
Subject: Re: respect privacy please !
Message-ID: <438876931.1085226135@localhost>
In-Reply-To: <44B38B0B2A7142BFB7245E67@scan.jck.com>
References: <0fa701c43f26$2939af90$8700000a@consulintel.es>
 <335417014.1085122709@localhost>
 <128901c43f45$8b640de0$8700000a@consulintel.es>
 <094301c43fa3$7054a0b0$0200a8c0@DFNJGL21>
 <44B38B0B2A7142BFB7245E67@scan.jck.com>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-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: 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 22. mai 2004 10:31 -0400 John C Klensin <john-ietf@jck.com> wrote:

> Spencer,
>
> I may be just misunderstanding your sense of humor, but it seems to me
> that any sort of formal experimental process is too heavyweight for this,
> or at least the core issue.  It seems to me that what we have is...
>
> 	* Jordi noticed a problem and pointed it out.
> 	
> 	* Harald indicated that the core issue had been noticed
> 	before and fixed, but the fix had apparently come
> 	unglued between the last meeting and this one... without
> 	anyone but Jordi noticing.
> 	
> 	* Some further discussion then suggested that "get
> 	explicit consent as a condition of registration" was
> 	probably better, and certainly no worse, than "notifying
> 	people about what will happen".
>
> I assume that, by now, Harald has told the Secretariat to apply a fix.  I
> hope they aren't sitting on the request or, if they are, that we will
> rapidly see an explanation.

actually the fix request had gotten lost in the first round - it was never 
applied to the Seoul web pages, and nobody noticed.
Guess what.... it had been deleted along with a bunch of spam...... points 
out the importance of improving the secretariat's spamfiltering abilities, 
as per the announcement on Friday.

The fix has now been applied.

                   Harald





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



From ietf-admin@ietf.org  Sat May 22 18:39: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 SAA02394
	for <ietf-archive@ietf.org>; Sat, 22 May 2004 18:39: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 1BRf9n-0002Xo-FI
	for ietf-archive@ietf.org; Sat, 22 May 2004 18:39:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRf90-0002Kk-00
	for ietf-archive@ietf.org; Sat, 22 May 2004 18:39:07 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRf8R-000264-00
	for ietf-archive@ietf.org; Sat, 22 May 2004 18:38:31 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRf38-00011Y-AA; Sat, 22 May 2004 18:33:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRez1-0000PV-6v
	for ietf@optimus.ietf.org; Sat, 22 May 2004 18:28:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01833
	for <ietf@ietf.org>; Sat, 22 May 2004 18:28: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 1BReyx-00002j-Go
	for ietf@ietf.org; Sat, 22 May 2004 18:28:43 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRey0-0007ea-00
	for ietf@ietf.org; Sat, 22 May 2004 18:27:44 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRexV-0007Sg-00
	for ietf@ietf.org; Sat, 22 May 2004 18:27:13 -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 i4MMQg1C086491;
	Sun, 23 May 2004 00:26:44 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <Pine.LNX.4.44.0405211952350.32663-100000@netcore.fi>
References: <Pine.LNX.4.44.0405211952350.32663-100000@netcore.fi>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <2478F39C-AC3F-11D8-A753-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: IPv6 for *.ietf.org services (Was: Re: respect privacy please !)
Date: Sun, 23 May 2004 00:27:00 +0200
To: Pekka Savola <pekkas@netcore.fi>
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 21-mei-04, at 19:00, Pekka Savola wrote:

> All the services IETF servers offer are purely client-server based.
> There is no significant technical advantage that I could see in making
> them IPv6-enabled, because all such services are very usable with
> IPv4.  On the other hand, doing so would just strengthen the illusion
> that wide-scale migration of all IPv4 services to IPv4/IPv6 is an
> important short-term goal.

While the importance of making any specific website or other service 
IPv6-capable is debatable, I certainly believe migrating these to 
dual-stack is an important goal. (I'm not saying short-term, as there 
is no specific deadline, but this doesn't mean waiting forever is a 
good idea.)

The reason for this is very simple: we sorely need operational 
experience. The proof of the pudding is in the eating and all that. The 
good part about making websites v6-capable is that people who use 
IPv6-capable browsers on IPv6-capable systems with IPv6 connectivity 
then get to see how well this works, without undue interference to IPv4 
reachability of the same website.

The idea that it would be possible to start using IPv6 for services 
that can't work well with IPv4 is a mistake, as breaking the 
chicken/egg cycle is much, much harder in this case. If it is 
completely impossible to deliver the service over IPv4 and living 
without it isn't an option, then IPv6 adoption will happen. But guess 
what: there is nothing you can do with IPv6 that you can't also do with 
IPv4. It just takes more effort.

What we need to do is show that providing connectivity using IPv6 is 
actually easier than doing the same using IPv4. This isn't entirely the 
case just yet, but we're getting there. And an important aspect of 
showing that something is easy is simply doing it.

Unfortunately, pretty much everyone seems to assume we'll be running 
dual stack until the cows come home, and obviously running dual stack 
is more work than just running IPv4. A bit more focus on the time when 
we get to remove IPv4 from 90% of the network would be in order.

> See Keith Moore's excellent write-up:
> http://www.cs.utk.edu/~moore/opinions/ipv6/dubious-assumptions.html

Sorry, I'm not impressed. I'm not sure whose assumptions Keith tries to 
debunk here, but just replacing them with his isn't much of an 
improvement.

For completeness (not necessarily agreeing with everything, probably 
want to skip the IPv6 introduction): 
http://www.potaroo.net/papers/isoc/2003-01/Waiting.html


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


From exim@www1.ietf.org  Sat May 22 18:43:14 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 SAA02500
	for <ietf-archive@odin.ietf.org>; Sat, 22 May 2004 18:43: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 1BRf8U-0002X0-1d
	for ietf-archive@odin.ietf.org; Sat, 22 May 2004 18:38:34 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4MMcY0x009731
	for ietf-archive@odin.ietf.org; Sat, 22 May 2004 18:38:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRf38-00011Y-AA; Sat, 22 May 2004 18:33:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRez1-0000PV-6v
	for ietf@optimus.ietf.org; Sat, 22 May 2004 18:28:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01833
	for <ietf@ietf.org>; Sat, 22 May 2004 18:28: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 1BReyx-00002j-Go
	for ietf@ietf.org; Sat, 22 May 2004 18:28:43 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRey0-0007ea-00
	for ietf@ietf.org; Sat, 22 May 2004 18:27:44 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRexV-0007Sg-00
	for ietf@ietf.org; Sat, 22 May 2004 18:27:13 -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 i4MMQg1C086491;
	Sun, 23 May 2004 00:26:44 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <Pine.LNX.4.44.0405211952350.32663-100000@netcore.fi>
References: <Pine.LNX.4.44.0405211952350.32663-100000@netcore.fi>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <2478F39C-AC3F-11D8-A753-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: IPv6 for *.ietf.org services (Was: Re: respect privacy please !)
Date: Sun, 23 May 2004 00:27:00 +0200
To: Pekka Savola <pekkas@netcore.fi>
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 21-mei-04, at 19:00, Pekka Savola wrote:

> All the services IETF servers offer are purely client-server based.
> There is no significant technical advantage that I could see in making
> them IPv6-enabled, because all such services are very usable with
> IPv4.  On the other hand, doing so would just strengthen the illusion
> that wide-scale migration of all IPv4 services to IPv4/IPv6 is an
> important short-term goal.

While the importance of making any specific website or other service 
IPv6-capable is debatable, I certainly believe migrating these to 
dual-stack is an important goal. (I'm not saying short-term, as there 
is no specific deadline, but this doesn't mean waiting forever is a 
good idea.)

The reason for this is very simple: we sorely need operational 
experience. The proof of the pudding is in the eating and all that. The 
good part about making websites v6-capable is that people who use 
IPv6-capable browsers on IPv6-capable systems with IPv6 connectivity 
then get to see how well this works, without undue interference to IPv4 
reachability of the same website.

The idea that it would be possible to start using IPv6 for services 
that can't work well with IPv4 is a mistake, as breaking the 
chicken/egg cycle is much, much harder in this case. If it is 
completely impossible to deliver the service over IPv4 and living 
without it isn't an option, then IPv6 adoption will happen. But guess 
what: there is nothing you can do with IPv6 that you can't also do with 
IPv4. It just takes more effort.

What we need to do is show that providing connectivity using IPv6 is 
actually easier than doing the same using IPv4. This isn't entirely the 
case just yet, but we're getting there. And an important aspect of 
showing that something is easy is simply doing it.

Unfortunately, pretty much everyone seems to assume we'll be running 
dual stack until the cows come home, and obviously running dual stack 
is more work than just running IPv4. A bit more focus on the time when 
we get to remove IPv4 from 90% of the network would be in order.

> See Keith Moore's excellent write-up:
> http://www.cs.utk.edu/~moore/opinions/ipv6/dubious-assumptions.html

Sorry, I'm not impressed. I'm not sure whose assumptions Keith tries to 
debunk here, but just replacing them with his isn't much of an 
improvement.

For completeness (not necessarily agreeing with everything, probably 
want to skip the IPv6 introduction): 
http://www.potaroo.net/papers/isoc/2003-01/Waiting.html


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



From ietf-admin@ietf.org  Sat May 22 21:13: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 VAA07453
	for <ietf-archive@ietf.org>; Sat, 22 May 2004 21:13: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 1BRhY1-0003cH-Kk
	for ietf-archive@ietf.org; Sat, 22 May 2004 21:13:05 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRhWy-0003N6-00
	for ietf-archive@ietf.org; Sat, 22 May 2004 21:12:00 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRhWS-000397-00
	for ietf-archive@ietf.org; Sat, 22 May 2004 21:11:28 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRhQF-00026L-05; Sat, 22 May 2004 21:05:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRhN7-0001lV-Si
	for ietf@optimus.ietf.org; Sat, 22 May 2004 21:01: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 VAA07110
	for <ietf@ietf.org>; Sat, 22 May 2004 21:01: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 1BRhN5-0001C7-0j
	for ietf@ietf.org; Sat, 22 May 2004 21:01:47 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRhM5-0000zX-00
	for ietf@ietf.org; Sat, 22 May 2004 21:00:46 -0400
Received: from c3p0.cc.swin.edu.au ([136.186.1.30] helo=swin.edu.au)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRhL3-0000bY-00
	for ietf@ietf.org; Sat, 22 May 2004 20:59:41 -0400
Received: from swin.edu.au (www.caia.swin.edu.au [136.186.229.16])
	by swin.edu.au (8.9.3p2-20030918/8.9.3) with ESMTP id KAA911179;
	Sun, 23 May 2004 10:59:04 +1000 (EST)
Message-ID: <40AFF757.BE217675@swin.edu.au>
Date: Sun, 23 May 2004 10:59:03 +1000
From: grenville armitage <garmitage@swin.edu.au>
Organization: Centre for Advanced Internet Architectures, Swinburne University of 
 Technology
X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: respect privacy please !
References: <0fa701c43f26$2939af90$8700000a@consulintel.es> <C920A0255CBCAF05FBEE6AC9@scan.jck.com> <40AE0C8C.6CFD72A3@swin.edu.au> <20040521145550.GB25670@login.ecs.soton.ac.uk> <40AE9DAE.41D764C7@swin.edu.au> <20040522104206.GC5178@login.ecs.soton.ac.uk>
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


Tim Chown wrote:
	[..]
> But there's no reason the list should be published in advance.

Clearly that's a matter of opinion. My sole observation is that the
threat model postulated for yanking the pre-meeting publication seem
insufficiently analysed.

cheers,
gja

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


From exim@www1.ietf.org  Sat May 22 21:14:11 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA07573
	for <ietf-archive@odin.ietf.org>; Sat, 22 May 2004 21: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 1BRhWU-00049B-VZ
	for ietf-archive@odin.ietf.org; Sat, 22 May 2004 21:11:31 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4N1BU8u015832
	for ietf-archive@odin.ietf.org; Sat, 22 May 2004 21:11:30 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRhQF-00026L-05; Sat, 22 May 2004 21:05:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRhN7-0001lV-Si
	for ietf@optimus.ietf.org; Sat, 22 May 2004 21:01: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 VAA07110
	for <ietf@ietf.org>; Sat, 22 May 2004 21:01: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 1BRhN5-0001C7-0j
	for ietf@ietf.org; Sat, 22 May 2004 21:01:47 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRhM5-0000zX-00
	for ietf@ietf.org; Sat, 22 May 2004 21:00:46 -0400
Received: from c3p0.cc.swin.edu.au ([136.186.1.30] helo=swin.edu.au)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRhL3-0000bY-00
	for ietf@ietf.org; Sat, 22 May 2004 20:59:41 -0400
Received: from swin.edu.au (www.caia.swin.edu.au [136.186.229.16])
	by swin.edu.au (8.9.3p2-20030918/8.9.3) with ESMTP id KAA911179;
	Sun, 23 May 2004 10:59:04 +1000 (EST)
Message-ID: <40AFF757.BE217675@swin.edu.au>
Date: Sun, 23 May 2004 10:59:03 +1000
From: grenville armitage <garmitage@swin.edu.au>
Organization: Centre for Advanced Internet Architectures, Swinburne University of 
 Technology
X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: respect privacy please !
References: <0fa701c43f26$2939af90$8700000a@consulintel.es> <C920A0255CBCAF05FBEE6AC9@scan.jck.com> <40AE0C8C.6CFD72A3@swin.edu.au> <20040521145550.GB25670@login.ecs.soton.ac.uk> <40AE9DAE.41D764C7@swin.edu.au> <20040522104206.GC5178@login.ecs.soton.ac.uk>
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


Tim Chown wrote:
	[..]
> But there's no reason the list should be published in advance.

Clearly that's a matter of opinion. My sole observation is that the
threat model postulated for yanking the pre-meeting publication seem
insufficiently analysed.

cheers,
gja

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



From ietf-admin@ietf.org  Sat May 22 21:43: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 VAA08256
	for <ietf-archive@ietf.org>; Sat, 22 May 2004 21:43: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 1BRi19-0002IO-MB
	for ietf-archive@ietf.org; Sat, 22 May 2004 21:43:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRi08-000212-00
	for ietf-archive@ietf.org; Sat, 22 May 2004 21:42:09 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRhzO-0001lx-00
	for ietf-archive@ietf.org; Sat, 22 May 2004 21:41:22 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRhmT-0006uP-TS; Sat, 22 May 2004 21:28:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRhkN-0006Zb-Gn
	for ietf@optimus.ietf.org; Sat, 22 May 2004 21:25: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 VAA07829
	for <ietf@ietf.org>; Sat, 22 May 2004 21:25: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 1BRhkK-0006Mp-Lv
	for ietf@ietf.org; Sat, 22 May 2004 21:25:48 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRhjK-00066s-00
	for ietf@ietf.org; Sat, 22 May 2004 21:24:46 -0400
Received: from mail4.microsoft.com ([131.107.3.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRhhR-0005ZF-00
	for ietf@ietf.org; Sat, 22 May 2004 21:22:49 -0400
Received: from mail5.microsoft.com ([157.54.6.156]) by mail4.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Sat, 22 May 2004 18:22:08 -0700
Received: from inet-vrs-05.redmond.corp.microsoft.com ([157.54.6.157]) by mail5.microsoft.com with Microsoft SMTPSVC(6.0.3790.1039);
	 Sat, 22 May 2004 18:22:12 -0700
Received: from 157.54.5.25 by inet-vrs-05.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Sat, 22 May 2004 18:22:18 -0700
Received: from red-imc-01.redmond.corp.microsoft.com ([157.54.9.102]) by inet-hub-03.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Sat, 22 May 2004 18:22:15 -0700
Received: from win-imc-02.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.84]) by red-imc-01.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.1069);
	 Sat, 22 May 2004 18:22:17 -0700
Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com ([157.54.12.81]) by win-imc-02.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3790.1069);
	 Sat, 22 May 2004 18:22:49 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: respect privacy please !
Date: Sat, 22 May 2004 18:22:15 -0700
Message-ID: <DAC3FCB50E31C54987CD10797DA511BA09281518@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: respect privacy please !
Thread-Index: AcRAYtdogrVo/XcoQneVitotgNAJUwAATyog
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: "grenville armitage" <garmitage@swin.edu.au>, <ietf@ietf.org>
X-OriginalArrivalTime: 23 May 2004 01:22:49.0592 (UTC) FILETIME=[761FCF80:01C44064]
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

> Tim Chown wrote:
> 	[..]
> > But there's no reason the list should be published in advance.

Well, actually there is a reason. Suppose that a particular company
decides to "stuff the room" and send a large number of participant to
the meeting. There is a big difference between making the behavior
public before the meeting and after.

-- Christian Huitema

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


From exim@www1.ietf.org  Sat May 22 21:45:19 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA08406
	for <ietf-archive@odin.ietf.org>; Sat, 22 May 2004 21:45: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 1BRhzQ-0000g3-8G
	for ietf-archive@odin.ietf.org; Sat, 22 May 2004 21:41:24 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4N1fOOF002571
	for ietf-archive@odin.ietf.org; Sat, 22 May 2004 21:41:24 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRhmT-0006uP-TS; Sat, 22 May 2004 21:28:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRhkN-0006Zb-Gn
	for ietf@optimus.ietf.org; Sat, 22 May 2004 21:25: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 VAA07829
	for <ietf@ietf.org>; Sat, 22 May 2004 21:25: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 1BRhkK-0006Mp-Lv
	for ietf@ietf.org; Sat, 22 May 2004 21:25:48 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRhjK-00066s-00
	for ietf@ietf.org; Sat, 22 May 2004 21:24:46 -0400
Received: from mail4.microsoft.com ([131.107.3.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRhhR-0005ZF-00
	for ietf@ietf.org; Sat, 22 May 2004 21:22:49 -0400
Received: from mail5.microsoft.com ([157.54.6.156]) by mail4.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Sat, 22 May 2004 18:22:08 -0700
Received: from inet-vrs-05.redmond.corp.microsoft.com ([157.54.6.157]) by mail5.microsoft.com with Microsoft SMTPSVC(6.0.3790.1039);
	 Sat, 22 May 2004 18:22:12 -0700
Received: from 157.54.5.25 by inet-vrs-05.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Sat, 22 May 2004 18:22:18 -0700
Received: from red-imc-01.redmond.corp.microsoft.com ([157.54.9.102]) by inet-hub-03.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Sat, 22 May 2004 18:22:15 -0700
Received: from win-imc-02.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.84]) by red-imc-01.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.1069);
	 Sat, 22 May 2004 18:22:17 -0700
Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com ([157.54.12.81]) by win-imc-02.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3790.1069);
	 Sat, 22 May 2004 18:22:49 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: respect privacy please !
Date: Sat, 22 May 2004 18:22:15 -0700
Message-ID: <DAC3FCB50E31C54987CD10797DA511BA09281518@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: respect privacy please !
Thread-Index: AcRAYtdogrVo/XcoQneVitotgNAJUwAATyog
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: "grenville armitage" <garmitage@swin.edu.au>, <ietf@ietf.org>
X-OriginalArrivalTime: 23 May 2004 01:22:49.0592 (UTC) FILETIME=[761FCF80:01C44064]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-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

> Tim Chown wrote:
> 	[..]
> > But there's no reason the list should be published in advance.

Well, actually there is a reason. Suppose that a particular company
decides to "stuff the room" and send a large number of participant to
the meeting. There is a big difference between making the behavior
public before the meeting and after.

-- Christian Huitema

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



From exim@www1.ietf.org  Sat May 22 21:57:10 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA08741
	for <ietf-archive@odin.ietf.org>; Sat, 22 May 2004 21:57: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 1BRiBq-0003s6-Is
	for ietf-archive@odin.ietf.org; Sat, 22 May 2004 21:54:17 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4N1sEpF014626
	for ietf-archive@odin.ietf.org; Sat, 22 May 2004 21:54:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRi2w-0001fw-6z; Sat, 22 May 2004 21:45:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRhx7-0008So-KB
	for ietf@optimus.ietf.org; Sat, 22 May 2004 21:39: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 VAA08165
	for <ietf@ietf.org>; Sat, 22 May 2004 21:38: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 1BRhx4-0001Ma-Os
	for ietf@ietf.org; Sat, 22 May 2004 21:38:58 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRhw7-00019S-00
	for ietf@ietf.org; Sat, 22 May 2004 21:38:00 -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 1BRhvd-0000wB-00
	for ietf@ietf.org; Sat, 22 May 2004 21:37:29 -0400
Subject: RE: respect privacy please !
Date: Sat, 22 May 2004 18:36:54 -0700
MIME-Version: 1.0
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B0DB145@server2003.arneill-py.sacramento.ca.us>
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Thread-Topic: respect privacy please !
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Thread-Index: AcRAYthN9IVRMmgdSS6ZsdcxPjT1zAAACJsg
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "grenville armitage" <garmitage@swin.edu.au>, <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

> grenville armitage wrote:
> My sole observation is that the threat model postulated for
> yanking the pre-meeting publication seem insufficiently analysed.

Besides, yanking it would be useless. If one wants to know if Joe
Sixpack is going to attend the meeting a week in advance, here are a few
tricks:


1. Email Joe Sixpack:
"Dear Joe,
I am Jane Doe from {vendor|organization}, I have read your excellent
comments about draft-ietf-whatever and I would like to know if you could
find a few minutes in your busy schedule to discuss the issue in person
at the San Diego meeting."

2. Call the meeting hotel and a few ones around:
"Hi, my name is Joe Sixpack and I just wanted to verify that you have a
reservation for me on August 1 2004".

3. Call the IETF secretariat:
"Hi, my name is Joe Sixpack, I pre-registered but I did not get any
confirmation email. Did the computer eat my registration?"

4. Call Joe Sixpack:
"Good morning Mr Sixpack, this is the Sheraton San Diego Hotel & Marina.
We have two reservations in your name, one starting on Saturday July 31
and another one starting on Sunday August 1. Which one is correct
please?"

Etc....

I still have to see _one_ reason why the registration list represents a
threat. I agree that the disclaimer is a good idea though.

Michel.



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



From ietf-admin@ietf.org  Sat May 22 21:58:01 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA08821
	for <ietf-archive@ietf.org>; Sat, 22 May 2004 21:58: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 1BRiFW-0005b5-Cb
	for ietf-archive@ietf.org; Sat, 22 May 2004 21:58:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRiEi-0005Ju-00
	for ietf-archive@ietf.org; Sat, 22 May 2004 21:57:13 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRiDk-000539-02
	for ietf-archive@ietf.org; Sat, 22 May 2004 21:56:12 -0400
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BRiBq-0004KA-0Q
	for ietf-archive@ietf.org; Sat, 22 May 2004 21:54:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRi2w-0001fw-6z; Sat, 22 May 2004 21:45:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRhx7-0008So-KB
	for ietf@optimus.ietf.org; Sat, 22 May 2004 21:39: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 VAA08165
	for <ietf@ietf.org>; Sat, 22 May 2004 21:38: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 1BRhx4-0001Ma-Os
	for ietf@ietf.org; Sat, 22 May 2004 21:38:58 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRhw7-00019S-00
	for ietf@ietf.org; Sat, 22 May 2004 21:38:00 -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 1BRhvd-0000wB-00
	for ietf@ietf.org; Sat, 22 May 2004 21:37:29 -0400
Subject: RE: respect privacy please !
Date: Sat, 22 May 2004 18:36:54 -0700
MIME-Version: 1.0
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B0DB145@server2003.arneill-py.sacramento.ca.us>
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Thread-Topic: respect privacy please !
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Thread-Index: AcRAYthN9IVRMmgdSS6ZsdcxPjT1zAAACJsg
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "grenville armitage" <garmitage@swin.edu.au>, <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

> grenville armitage wrote:
> My sole observation is that the threat model postulated for
> yanking the pre-meeting publication seem insufficiently analysed.

Besides, yanking it would be useless. If one wants to know if Joe
Sixpack is going to attend the meeting a week in advance, here are a few
tricks:


1. Email Joe Sixpack:
"Dear Joe,
I am Jane Doe from {vendor|organization}, I have read your excellent
comments about draft-ietf-whatever and I would like to know if you could
find a few minutes in your busy schedule to discuss the issue in person
at the San Diego meeting."

2. Call the meeting hotel and a few ones around:
"Hi, my name is Joe Sixpack and I just wanted to verify that you have a
reservation for me on August 1 2004".

3. Call the IETF secretariat:
"Hi, my name is Joe Sixpack, I pre-registered but I did not get any
confirmation email. Did the computer eat my registration?"

4. Call Joe Sixpack:
"Good morning Mr Sixpack, this is the Sheraton San Diego Hotel & Marina.
We have two reservations in your name, one starting on Saturday July 31
and another one starting on Sunday August 1. Which one is correct
please?"

Etc....

I still have to see _one_ reason why the registration list represents a
threat. I agree that the disclaimer is a good idea though.

Michel.



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


From exim@www1.ietf.org  Sun May 23 01:13:36 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA15702
	for <ietf-archive@odin.ietf.org>; Sun, 23 May 2004 01:13: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 1BRlHQ-00072j-Kf
	for ietf-archive@odin.ietf.org; Sun, 23 May 2004 01:12:13 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4N5CCFV026853
	for ietf-archive@odin.ietf.org; Sun, 23 May 2004 01:12:12 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRlBS-0005T5-T2; Sun, 23 May 2004 01:06:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRl8W-00050a-NB
	for ietf@optimus.ietf.org; Sun, 23 May 2004 01:03:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA15357
	for <ietf@ietf.org>; Sun, 23 May 2004 01:02: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 1BRl8T-0000RT-M9
	for ietf@ietf.org; Sun, 23 May 2004 01:02:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRl7X-0000Eo-00
	for ietf@ietf.org; Sun, 23 May 2004 01:02:00 -0400
Received: from tierw.net.avaya.com ([198.152.13.100])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRl6b-00001d-00
	for ietf@ietf.org; Sun, 23 May 2004 01:01:02 -0400
Received: from tierw.net.avaya.com (localhost [127.0.0.1])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id i4N4thrw021067
	for <ietf@ietf.org>; Sat, 22 May 2004 23:55:43 -0500 (EST)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id i4N4tRrw020785
	for <ietf@ietf.org>; Sat, 22 May 2004 23:55:28 -0500 (EST)
content-class: urn:content-classes:message
Subject: Out of Office AutoReply: <Possible SPAM> Re: Your website
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C44082.E61D391C"
Date: Sun, 23 May 2004 08:00:42 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F061D8D5E@is0004avexu1.global.avaya.com>
Thread-Topic: <Possible SPAM> Re: Your website
Thread-Index: AcRAguYMo2U7rKeNTJ2i8sntKgOftAAAAATi
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ietf@ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,HTML_30_40,HTML_MESSAGE 
	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.

------_=_NextPart_001_01C44082.E61D391C
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

I am at the IEEE meeting and may not be able to read and reply to your =
message until May 23rd. If you need to contact me directly, please call =
+972-50-692-8065.

Regards,

Dan


------_=_NextPart_001_01C44082.E61D391C
Content-Type: text/html;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dwindows-1255">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.6487.1">
<TITLE>Out of Office AutoReply: &lt;Possible SPAM&gt; Re: Your =
website</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>I am at the IEEE meeting and may not be able to read =
and reply to your message until May 23rd. If you need to contact me =
directly, please call +972-50-692-8065.<BR>
<BR>
Regards,<BR>
<BR>
Dan<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C44082.E61D391C--

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



From ietf-admin@ietf.org  Sun May 23 01:14: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 BAA15764
	for <ietf-archive@ietf.org>; Sun, 23 May 2004 01:14: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 1BRlJD-000325-Ij
	for ietf-archive@ietf.org; Sun, 23 May 2004 01:14:03 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRlIL-0002n8-00
	for ietf-archive@ietf.org; Sun, 23 May 2004 01:13:09 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRlHN-0002Yf-00
	for ietf-archive@ietf.org; Sun, 23 May 2004 01:12:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRlBS-0005T5-T2; Sun, 23 May 2004 01:06:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRl8W-00050a-NB
	for ietf@optimus.ietf.org; Sun, 23 May 2004 01:03:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA15357
	for <ietf@ietf.org>; Sun, 23 May 2004 01:02: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 1BRl8T-0000RT-M9
	for ietf@ietf.org; Sun, 23 May 2004 01:02:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRl7X-0000Eo-00
	for ietf@ietf.org; Sun, 23 May 2004 01:02:00 -0400
Received: from tierw.net.avaya.com ([198.152.13.100])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRl6b-00001d-00
	for ietf@ietf.org; Sun, 23 May 2004 01:01:02 -0400
Received: from tierw.net.avaya.com (localhost [127.0.0.1])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id i4N4thrw021067
	for <ietf@ietf.org>; Sat, 22 May 2004 23:55:43 -0500 (EST)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id i4N4tRrw020785
	for <ietf@ietf.org>; Sat, 22 May 2004 23:55:28 -0500 (EST)
content-class: urn:content-classes:message
Subject: Out of Office AutoReply: <Possible SPAM> Re: Your website
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C44082.E61D391C"
Date: Sun, 23 May 2004 08:00:42 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F061D8D5E@is0004avexu1.global.avaya.com>
Thread-Topic: <Possible SPAM> Re: Your website
Thread-Index: AcRAguYMo2U7rKeNTJ2i8sntKgOftAAAAATi
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <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>
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

This is a multi-part message in MIME format.

------_=_NextPart_001_01C44082.E61D391C
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

I am at the IEEE meeting and may not be able to read and reply to your =
message until May 23rd. If you need to contact me directly, please call =
+972-50-692-8065.

Regards,

Dan


------_=_NextPart_001_01C44082.E61D391C
Content-Type: text/html;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dwindows-1255">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.6487.1">
<TITLE>Out of Office AutoReply: &lt;Possible SPAM&gt; Re: Your =
website</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>I am at the IEEE meeting and may not be able to read =
and reply to your message until May 23rd. If you need to contact me =
directly, please call +972-50-692-8065.<BR>
<BR>
Regards,<BR>
<BR>
Dan<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C44082.E61D391C--

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


From ietf-admin@ietf.org  Mon May 24 05: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 FAA22940
	for <ietf-archive@ietf.org>; Mon, 24 May 2004 05: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 1BSBzV-00051H-LT
	for ietf-archive@ietf.org; Mon, 24 May 2004 05:43:29 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BSBya-0004iD-00
	for ietf-archive@ietf.org; Mon, 24 May 2004 05:42:32 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BSBy0-0004OJ-00
	for ietf-archive@ietf.org; Mon, 24 May 2004 05:41:56 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BSBkX-000860-Nu; Mon, 24 May 2004 05:28:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BSBd0-0006tI-RK
	for ietf@optimus.ietf.org; Mon, 24 May 2004 05:20:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22040
	for <ietf@ietf.org>; Mon, 24 May 2004 05:20: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 1BSBcx-0005lm-5B
	for ietf@ietf.org; Mon, 24 May 2004 05:20:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BSBbx-0005TN-00
	for ietf@ietf.org; Mon, 24 May 2004 05:19:10 -0400
Received: from smtp.nildram.co.uk ([195.112.4.54])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BSBas-0004uP-00
	for ietf@ietf.org; Mon, 24 May 2004 05:18:02 -0400
Received: from pcgz600re (unknown [81.6.214.202])
	by smtp.nildram.co.uk (Postfix) with SMTP id 4D86F24DB9A
	for <ietf@ietf.org>; Mon, 24 May 2004 10:18:00 +0100 (BST)
Reply-To: <cdel@firsthand.net>
From: "Christian de Larrinaga" <cdel@firsthand.net>
To: <ietf@ietf.org>
Subject: spoofing email addresses
Date: Mon, 24 May 2004 10:18:28 +0100
Message-ID: <OKEPLEIOJKFGFGCKMDKJKEDMCDAA.cdel@firsthand.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Importance: Normal
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

Since Thursday (last) I've been receiving hundreds of bounces from spam
filters and mail servers for email messages I've not sent at
cdel@firsthand.net. I can see from those bounces where the header info of
the orginal message is included that somebody has been using my address to
disguise the origin of their spam.

I'm hoping that spam filters will detect the inconsistent header information
and not blacklist me at cdel@firsthand.net but I'm not hopeful. If you want
to get email from me you might want to check. I intend to continue to use
this address. Incidentally does anybody run a retribution service?


Christian de Larrinaga


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


From exim@www1.ietf.org  Mon May 24 05:49:01 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 FAA23148
	for <ietf-archive@odin.ietf.org>; Mon, 24 May 2004 05:49: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 1BSBy4-0001c0-P5
	for ietf-archive@odin.ietf.org; Mon, 24 May 2004 05:42:01 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4O9fwiR005942
	for ietf-archive@odin.ietf.org; Mon, 24 May 2004 05:41:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BSBkX-000860-Nu; Mon, 24 May 2004 05:28:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BSBd0-0006tI-RK
	for ietf@optimus.ietf.org; Mon, 24 May 2004 05:20:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22040
	for <ietf@ietf.org>; Mon, 24 May 2004 05:20: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 1BSBcx-0005lm-5B
	for ietf@ietf.org; Mon, 24 May 2004 05:20:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BSBbx-0005TN-00
	for ietf@ietf.org; Mon, 24 May 2004 05:19:10 -0400
Received: from smtp.nildram.co.uk ([195.112.4.54])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BSBas-0004uP-00
	for ietf@ietf.org; Mon, 24 May 2004 05:18:02 -0400
Received: from pcgz600re (unknown [81.6.214.202])
	by smtp.nildram.co.uk (Postfix) with SMTP id 4D86F24DB9A
	for <ietf@ietf.org>; Mon, 24 May 2004 10:18:00 +0100 (BST)
Reply-To: <cdel@firsthand.net>
From: "Christian de Larrinaga" <cdel@firsthand.net>
To: <ietf@ietf.org>
Subject: spoofing email addresses
Date: Mon, 24 May 2004 10:18:28 +0100
Message-ID: <OKEPLEIOJKFGFGCKMDKJKEDMCDAA.cdel@firsthand.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Importance: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=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

Since Thursday (last) I've been receiving hundreds of bounces from spam
filters and mail servers for email messages I've not sent at
cdel@firsthand.net. I can see from those bounces where the header info of
the orginal message is included that somebody has been using my address to
disguise the origin of their spam.

I'm hoping that spam filters will detect the inconsistent header information
and not blacklist me at cdel@firsthand.net but I'm not hopeful. If you want
to get email from me you might want to check. I intend to continue to use
this address. Incidentally does anybody run a retribution service?


Christian de Larrinaga


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



From exim@www1.ietf.org  Mon May 24 12:42:12 2004
Received: from optimus.ietf.org ([132.151.1.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18657
	for <ietf-archive@odin.ietf.org>; Mon, 24 May 2004 12:42: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 1BSITI-0008J1-Ti
	for ietf-archive@odin.ietf.org; Mon, 24 May 2004 12:38:40 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4OGcevi031920
	for ietf-archive@odin.ietf.org; Mon, 24 May 2004 12:38:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BSIIg-0005rf-5k
	for ietf-web-archive@optimus.ietf.org; Mon, 24 May 2004 12:27: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 MAA18038
	for <ietf-web-archive@ietf.org>; Mon, 24 May 2004 12:27: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 1BSIIe-0004f0-Kk
	for ietf-web-archive@ietf.org; Mon, 24 May 2004 12:27:40 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BSIHh-0004XU-00
	for ietf-web-archive@ietf.org; Mon, 24 May 2004 12:26:42 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BSIHJ-0004RO-00
	for ietf-web-archive@ietf.org; Mon, 24 May 2004 12:26:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BSHyM-0001GJ-8e
	for ietf-web-archive@ietf.org; Mon, 24 May 2004 12:06:42 -0400
Date: Mon, 24 May 2004 12:06:42 -0400
Message-ID: <20040524160642.4854.63231.Mailman@www1.ietf.org>
Subject: Welcome to the "Ietf" mailing list
From: ietf-request@ietf.org
To: ietf-web-archive@ietf.org
X-No-Archive: yes
X-Ack: no
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.3 required=5.0 tests=NO_REAL_NAME autolearn=no 
	version=2.60

Welcome to the Ietf@ietf.org mailing list!

To post to this list, send your email to:

  ietf@ietf.org

General information about the mailing list is at:

  https://www1.ietf.org/mailman/listinfo/ietf

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


                                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 ever want to unsubscribe or change your options (eg, switch to
or from digest mode, change your password, etc.), visit your
subscription page at:

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


You can also make such adjustments via email by sending a message to:

  Ietf-request@ietf.org

with the word `help' in the subject or body (don't include the
quotes), and you will get back a message with instructions.

You must know your password to change your options (including changing
the password, itself) or to unsubscribe.  It is:

  enetzo

If you forget your password, don't worry, you will receive a monthly
reminder telling you what all your ietf.org mailing list passwords
are, and how to unsubscribe or change your options.  There is also a
button on your options page that will email your current password to
you.

You may also have your password mailed to you automatically off of the
Web page noted above.



From ietf-bounces@ietf.org  Mon May 24 17:34:44 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04559
	for <ietf-archive@ietf.org>; Mon, 24 May 2004 17:34:44 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BSN5p-0002yN-Q7
	for ietf-archive@ietf.org; Mon, 24 May 2004 17:34:45 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BSMo2-0007Sh-00
	for ietf-archive@ietf.org; Mon, 24 May 2004 17:16:24 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BSMRI-0004xC-00; Mon, 24 May 2004 16:52:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BSMPY-0002HV-2d; Mon, 24 May 2004 16:51:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BSMPW-0002HK-Lu
	for ietf@megatron.ietf.org; Mon, 24 May 2004 16:51: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 QAA27992
	for <ietf@ietf.org>; Mon, 24 May 2004 16:50:59 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BSMPV-0004oV-36
	for ietf@ietf.org; Mon, 24 May 2004 16:51:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BSM4C-0001a2-00
	for ietf@ietf.org; Mon, 24 May 2004 16:29:01 -0400
Received: from turing-police.cirt.vt.edu ([128.173.54.129] ident=root)
	by ietf-mx with esmtp (Exim 4.12) id 1BSJZg-0006wn-00
	for ietf@ietf.org; Mon, 24 May 2004 13:49:20 -0400
Received: from turing-police.cc.vt.edu (IDENT:valdis@localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.13.0.Beta2/8.13.0.Beta2) with ESMTP id
	i4OHn2X1004192; Mon, 24 May 2004 13:49:02 -0400
Message-Id: <200405241749.i4OHn2X1004192@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: cdel@firsthand.net
In-Reply-To: Your message of "Mon, 24 May 2004 10:18:28 BST."
	<OKEPLEIOJKFGFGCKMDKJKEDMCDAA.cdel@firsthand.net> 
References: <OKEPLEIOJKFGFGCKMDKJKEDMCDAA.cdel@firsthand.net>
Mime-Version: 1.0
Date: Mon, 24 May 2004 13:49:02 -0400
Cc: ietf@ietf.org
Subject: Re: spoofing email addresses 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0775961935=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60

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

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

On Mon, 24 May 2004 10:18:28 BST, Christian de Larrinaga <cdel@firsthand.net>  said:

> I'm hoping that spam filters will detect the inconsistent header information
> and not blacklist me at cdel@firsthand.net but I'm not hopeful.

In fact, there isn't any sane way to detect "inconsistent" header information
without external hints - this is the reason why there's the SPF proposal, the
Yahoo domain-keys proposal, and Microsoft's proposal.  (Contemplate
the headers on this piece of e-mail for a nonce, and ask yourself if they're
consistent or not.  Then consider the fact that I've on at least one occasion
posted to this list from this same laptop, but at the time I was behind a
NAT'ed firewall in California....)


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

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

iD8DBQFAsjWOcC3lWbTT17ARAn0MAKCsDYI3WMz5jONHh3zPHwAUDsPLkACfZP7c
WBy0cQodedidDgz6VIdArE8=
=BQAZ
-----END PGP SIGNATURE-----

--==_Exmh_398607630P--


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

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

--===============0775961935==--



From ietf-bounces@ietf.org  Mon May 24 17: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 RAA06964
	for <ietf-archive@ietf.org>; Mon, 24 May 2004 17: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 1BSNGP-0004yC-CL
	for ietf-archive@ietf.org; Mon, 24 May 2004 17:45:41 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BSN36-0002OI-00
	for ietf-archive@ietf.org; Mon, 24 May 2004 17:31:59 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BSMjS-0006eH-00; Mon, 24 May 2004 17:11:38 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BSMjS-0001f2-TZ; Mon, 24 May 2004 17:11:39 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BSMjJ-0005EQ-9y; Mon, 24 May 2004 17:11:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BSMjH-0005EL-GQ
	for ietf@megatron.ietf.org; Mon, 24 May 2004 17:11: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 RAA01509
	for <ietf@ietf.org>; Mon, 24 May 2004 17:11: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 1BSMjG-0006ba-14
	for ietf@ietf.org; Mon, 24 May 2004 17:11:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BSMJE-0003vV-00
	for ietf@ietf.org; Mon, 24 May 2004 16:44:34 -0400
Received: from turkey.mail.pas.earthlink.net ([207.217.120.126])
	by ietf-mx with esmtp (Exim 4.12) id 1BSLdp-0000Z5-00
	for ietf@ietf.org; Mon, 24 May 2004 16:01:45 -0400
Received: from h-68-164-94-33.snvacaid.dynamic.covad.net ([68.164.94.33]
	helo=oemcomputer)
	by turkey.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 1BSLdo-00048D-00
	for ietf@ietf.org; Mon, 24 May 2004 13:01:44 -0700
Message-ID: <007201c441c9$f4b5bec0$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <ietf@ietf.org>
References: <OKEPLEIOJKFGFGCKMDKJKEDMCDAA.cdel@firsthand.net>
Date: Mon, 24 May 2004 13:01:51 -0700
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
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

Hi -

> From: "Christian de Larrinaga" <cdel@firsthand.net>
> To: <ietf@ietf.org>
> Sent: Monday, May 24, 2004 2:18 AM
> Subject: spoofing email addresses
>

> Since Thursday (last) I've been receiving hundreds of bounces from spam
> filters and mail servers for email messages I've not sent at
> cdel@firsthand.net. I can see from those bounces where the header info of
> the orginal message is included that somebody has been using my address to
> disguise the origin of their spam.
...

Welcome to the club.  In "joe-job" spam (viral or otherwise)
I think I've seen the email addresses of just about everone I
know from the IETF.

Randy



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


From ietf-bounces@ietf.org  Mon May 24 17:54:22 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09026
	for <ietf-archive@ietf.org>; Mon, 24 May 2004 17:54:22 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BSNOq-0006Qv-C9
	for ietf-archive@ietf.org; Mon, 24 May 2004 17:54:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BSNIj-0005P0-00
	for ietf-archive@ietf.org; Mon, 24 May 2004 17:48:05 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BSN7s-0003Hd-00; Mon, 24 May 2004 17:36:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BSN7C-0007id-GR; Mon, 24 May 2004 17:36:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BSN7A-0007iK-Rv
	for ietf@megatron.ietf.org; Mon, 24 May 2004 17:36: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 RAA04930
	for <ietf@ietf.org>; Mon, 24 May 2004 17:36: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 1BSN79-0003E2-5X
	for ietf@ietf.org; Mon, 24 May 2004 17:36:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BSMq5-00005N-00
	for ietf@ietf.org; Mon, 24 May 2004 17:18:31 -0400
Received: from 206-169-2-196.gen.twtelecom.net ([206.169.2.196]
	helo=mail.optistreams.net) by ietf-mx with esmtp (Exim 4.12)
	id 1BSMUh-0005Ix-00
	for ietf@ietf.org; Mon, 24 May 2004 16:56:24 -0400
Received: from [192.168.0.101] [68.42.70.186] by mail.optistreams.net with
	ESMTP (SMTPD32-8.04) id ABF9EA00242; Mon, 24 May 2004 13:32:57 -0700
In-Reply-To: <OKEPLEIOJKFGFGCKMDKJKEDMCDAA.cdel@firsthand.net>
References: <OKEPLEIOJKFGFGCKMDKJKEDMCDAA.cdel@firsthand.net>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <BA37B9BD-ADC4-11D8-88E2-000A9571873E@guppylake.com>
Content-Transfer-Encoding: 7bit
From: Nathaniel Borenstein <nsb@guppylake.com>
Date: Mon, 24 May 2004 16:55:45 -0400
To: <cdel@firsthand.net>
X-Mailer: Apple Mail (2.613)
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

On May 24, 2004, at 5:18 AM, Christian de Larrinaga wrote:

> Incidentally does anybody run a retribution service?

Boy, do I hope this question is a joke.  But if I were running some of 
the blacklisting services, I would worry that someone might get serious 
about revenge.  If I were a less placid person, I hate to think what I 
might have done after being unfairly blacklisted by RoadRunner for 6 
months.  (As it is, even after a year, I still find some juvenile 
satisfaction in repeatedly mentioning them by name in this context.  
But the desire for revenge could easily get much nastier.)   -- 
Nathaniel


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


From ietf-bounces@ietf.org  Mon May 24 19:22: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 TAA15896
	for <ietf-archive@ietf.org>; Mon, 24 May 2004 19:22: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 1BSOmG-0007mi-Vi
	for ietf-archive@ietf.org; Mon, 24 May 2004 19:22:41 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BSOlX-0007aT-00
	for ietf-archive@ietf.org; Mon, 24 May 2004 19:21:56 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BSOkZ-0007MF-00; Mon, 24 May 2004 19:20:55 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BSOgd-0006Y5-6w; Mon, 24 May 2004 19:16:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BSOdw-0006Ja-TT
	for ietf@megatron.ietf.org; Mon, 24 May 2004 19:14: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 TAA15327
	for <ietf@ietf.org>; Mon, 24 May 2004 19:14: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 1BSOdv-0006r7-7l
	for ietf@ietf.org; Mon, 24 May 2004 19:14:03 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BSOd3-0006nM-00
	for ietf@ietf.org; Mon, 24 May 2004 19:13:10 -0400
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12) id 1BSOcS-0006iD-00
	for ietf@ietf.org; Mon, 24 May 2004 19:12:33 -0400
Received: from bbprime (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id i4ONBoT14655;
	Mon, 24 May 2004 16:11:50 -0700
Date: Mon, 24 May 2004 16:11:48 -0700
From: Dave Crocker <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <323779608.20040524161148@brandenburg.com>
To: Nathaniel Borenstein <nsb@guppylake.com>
In-Reply-To: <BA37B9BD-ADC4-11D8-88E2-000A9571873E@guppylake.com>
References: <OKEPLEIOJKFGFGCKMDKJKEDMCDAA.cdel@firsthand.net>
	<BA37B9BD-ADC4-11D8-88E2-000A9571873E@guppylake.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Cc: cdel@firsthand.net, ietf@ietf.org
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.8 required=5.0 tests=PRIORITY_NO_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit

Nathaniel,

NB> Boy, do I hope this question is a joke.  But if I were running some of 
NB> the blacklisting services, I would worry that someone might get serious 
NB> about revenge.

already happens, mostly through DDOS attacks.




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


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


From ietf-bounces@ietf.org  Tue May 25 05:29: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 FAA26534
	for <ietf-archive@ietf.org>; Tue, 25 May 2004 05:29: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 1BSYFn-0003u6-LH
	for ietf-archive@ietf.org; Tue, 25 May 2004 05:29:47 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BSYF4-0003jF-00
	for ietf-archive@ietf.org; Tue, 25 May 2004 05:29:02 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BSYEL-0003Sn-00; Tue, 25 May 2004 05:28:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BSYBz-000476-Ca; Tue, 25 May 2004 05:25:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BSY57-0003Kr-LE
	for ietf@megatron.ietf.org; Tue, 25 May 2004 05:18: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 FAA25896
	for <ietf@ietf.org>; Tue, 25 May 2004 05:18: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 1BSY55-0001hQ-7J
	for ietf@ietf.org; Tue, 25 May 2004 05:18:43 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BSY45-0001X1-00
	for ietf@ietf.org; Tue, 25 May 2004 05:17:42 -0400
Received: from [61.11.62.217] (helo=ganapathy.SILICOMPINDIA)
	by ietf-mx with smtp (Exim 4.12) id 1BSY3A-0001N0-00
	for ietf@ietf.org; Tue, 25 May 2004 05:16:45 -0400
Received: From apdas (unverified [192.168.1.23]) by SMTP Server [192.168.1.25]
	(WinGate SMTP Receiver v5.2.2 (Build 892)) with SMTP id
	<0000000075@GANAPATHY>; Tue, 25 May 2004 14:53:46 +0530
Message-ID: <015801c44239$fb2c4c90$1701a8c0@SILICOMPINDIA>
From: "Ambika Prasad Das" <apdas@silicomp.co.in>
To: "IETF Mailing List" <ietf@ietf.org>
Date: Tue, 25 May 2004 14:53:46 +0530
MIME-Version: 1.0
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
Subject: Telecom standards
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Ambika Prasad Das <apdas@silicomp.co.in>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0699916780=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,HTML_20_30,HTML_MESSAGE 
	autolearn=no version=2.60

This is a multi-part message in MIME format.

--===============0699916780==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0155_01C44268.14DAEBA0"

This is a multi-part message in MIME format.

------=_NextPart_000_0155_01C44268.14DAEBA0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi All,

I am working on a telecom project and am totally new to CDR file =
formats. CDR files are files where call detail records are kept. I want =
to know more about the following formats.=20

Variable length
ASN.1/TLV
GPRS CDR

Can anybody help ? Please also let me know the sources from which I will =
get authentic information about all these formats.

Regards,

Ambika Prasad Das
Software Engineer
Silicomp India Pvt Ltd.
ph: +91-9886071231(M)


------=_NextPart_000_0155_01C44268.14DAEBA0
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>Hi All,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I am working on a telecom project and =
am totally=20
new to CDR file formats. CDR files are files where call detail records =
are kept.=20
I want to know more about the following formats. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV>Variable length<BR>ASN.1/TLV<BR>GPRS CDR<BR></DIV>
<DIV><FONT face=3DArial size=3D2>Can anybody help ? Please also let me =
know the=20
sources from which I will get authentic information about all these=20
formats.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Regards,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Ambika Prasad Das<BR>Software =
Engineer<BR>Silicomp=20
India Pvt Ltd.<BR>ph: +91-9886071231(M)</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_0155_01C44268.14DAEBA0--



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

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

--===============0699916780==--




From ietf-bounces@ietf.org  Tue May 25 15:31: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 PAA11682
	for <ietf-archive@ietf.org>; Tue, 25 May 2004 15:31: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 1BShdx-0005bU-La
	for ietf-archive@ietf.org; Tue, 25 May 2004 15:31:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BShd5-0005Tv-00
	for ietf-archive@ietf.org; Tue, 25 May 2004 15:30:28 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BShc4-0005Gs-00; Tue, 25 May 2004 15:29:24 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BShTu-0005Zj-RZ; Tue, 25 May 2004 15:20:58 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BShMF-00029L-TO
	for ietf@megatron.ietf.org; Tue, 25 May 2004 15:13: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 PAA09996
	for <ietf@ietf.org>; Tue, 25 May 2004 15:13: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 1BShME-0003vL-Ef
	for ietf@ietf.org; Tue, 25 May 2004 15:13:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BShLN-0003r4-00
	for ietf@ietf.org; Tue, 25 May 2004 15:12:10 -0400
Received: from bay2-dav28.bay2.hotmail.com ([65.54.246.85] helo=hotmail.com)
	by ietf-mx with esmtp (Exim 4.12) id 1BShKf-0003is-00
	for ietf@ietf.org; Tue, 25 May 2004 15:11:25 -0400
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	Tue, 25 May 2004 12:10:54 -0700
Received: from 24.157.202.64 by bay2-dav28.bay2.hotmail.com with DAV;
	Tue, 25 May 2004 19:10:54 +0000
X-Originating-IP: [24.157.202.64]
X-Originating-Email: [fghxu@hotmail.com]
X-Sender: fghxu@hotmail.com
From: "Frank Xu" <fghxu@hotmail.com>
To: <ietf@ietf.org>
Date: Tue, 25 May 2004 15:10:50 -0400
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Message-ID: <BAY2-DAV28VFJKp0DS800017c02@hotmail.com>
X-OriginalArrivalTime: 25 May 2004 19:10:54.0819 (UTC)
	FILETIME=[00B8EB30:01C4428C]
Cc: Uyen Trang Nguyen <utn@cs.yorku.ca>, gxu@cs.yorku.ca
Subject: How to start my network simulation project in Glomosim
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Frank Xu <gxu@cs.yorku.ca>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0447146231=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=2.0 required=5.0 tests=AWL,FORGED_OUTLOOK_TAGS,
	MIME_BASE64_TEXT autolearn=no version=2.60

This is a multi-part message in MIME format.

--===============0447146231==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_001C_01C4426A.76FA2C90"

This is a multi-part message in MIME format.

------=_NextPart_000_001C_01C4426A.76FA2C90
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: base64

SGVsbG8gYWxsLA0KDQpJIGFtIHN0YXJ0aW5nIG15IE1TYyBwcm9qZWN0IG9uIGEgbmV3bHkgZGV2
ZWxvcGVkIHN0cmVhbSB2aWRlbyBlbmNvZGluZy9kZWNvZGluZyBzY2hlbWUuIFdlIHdhbnQgdG8g
Y29tcGFyZSBhbmQgdGVzdCBvdXIgc2NoZW1lIHdpdGggdGhlIGN1cnJlbnRseSBzdGFuZGFyZCB2
aWRlbyBlbmNvZGluZyBzY2hlbWVzIGluIHRoZSB3aXJlZC93aXJlbGVzcyBtdWx0aS1jYXN0aW5n
IG5ldHdvcmsgZW52aXJvbm1lbnQuICBXZSBhcmUgY29uc2lkZXJpbmcgdG8gdXNlIHRoZSBuZXR3
b3JrIHNpbXVsYXRvciAtIEdsb21vc2ltLiANCg0KU2luY2UgSSBhbSBuZXcgdG8gdGhlIEdsb21v
c2ltLiBJIGRvbid0IGtub3cgaG93IHRvIG1vZGlmeSBpdCB0byBtYWtlIGl0IHN1aXQgZm9yIG91
ciByZXNlYXJjaCBwdXJwb3NlLiBJIHdvdWxkIGxpa2UgdG8ga25vdyBzb21lIGd1aWRlbGluZXMg
b2YgaG93IHRvIHN0YXJ0IG15IHByb2plY3QgdXNpbmcgR2xvbW9zaW0uDQoNCldlIHdpbGwgZW5j
b2RlIHRoZSB2aWRlbyBpbnRvIGZyYW1lcyBhbmQgZmVlZCB0aGVtIHRvIHRoZSBHbG9tb3NpbSBh
bmQgcmVjZWl2ZSB0aGVtIGF0IG11bHRpcGxlIGVuZHMuICBVcG9uIHJlY2VpdmluZywgdGhlIHJl
Y2VpdmVzIHdpbGwgZGVjb2RlIHRoZSBmcmFtZXMgaW50byBzdHJlYW0gdmlkZW8gYWdhaW4uICBU
aGUgbWFpbiBnb2FsIG9mIHVzaW5nIHRoZSBzaW11bGF0b3IgaXMgdG8gc2VlIGhvdyB0aGUgZW5j
b2RpbmcvZGVjb2Rpbmcgc2NoZW1lIHdvcmsgaW4gdGhlIHVucmVsaWFibGUgbmV0d29yayBlbnZp
cm9ubWVudC4gIA0KDQpJIHdvdWxkIGxpa2UgdG8ga25vdyAgaG93IGNhbiBJIG1vZGlmeSB0aGUg
R2xvbW9zaW0gaW4gb3JkZXIgdG8gdHJhbnNmZXIgdGhvc2UgY3VzdG9tIG1hZGUgImZyYW1lIiBk
YXRhPyAgd2hpY2ggcGFydCBpbiB0aGUgR2xvbW9zaW0gc2hhbGwgSSBtb2RpZnk/ICBTaGFsbCBJ
IHN0YXJ0IGZyb20gbG9va2luZyBhdCBjb2RlcyBpbiB0aGUgQXBwbGljYXRpb24gTGF5ZXI/DQoN
CldlIHdpbGwgdXNlIHRoZSBPRE1SUCByb3V0aW5nIHByb3RvY29sIGFuZCBJRUVFODAyLjExIGFu
ZC9vciBVRFAuDQoNCg0KQW55IHN1Z2dlc3Rpb24gaXMgdmVyeSB3ZWxjb21lZC4gIFRoYW5rcyBp
biBhZHZhbmNlIQ0KDQoNCkJlc3QgcmVnYXJkcw0KDQpGcmFuaw0KDQoNCg0KDQoNCg0KDQoNCl4g
XiANCnwgDQotLS0gDQo+RnJvbTogaWV0Zi1yZXF1ZXN0QGlldGYub3JnIA0KPlRvOiBmZ2h4dUBo
b3RtYWlsLmNvbSANCj5TdWJqZWN0OiBXZWxjb21lIHRvIHRoZSAiSWV0ZiIgbWFpbGluZyBsaXN0
IChEaWdlc3QgbW9kZSkgDQo+RGF0ZTogVHVlLCAyNSBNYXkgMjAwNCAxNDoyMDo0MiAtMDQwMCAN
Cj4gDQo+V2VsY29tZSB0byB0aGUgSWV0ZkBpZXRmLm9yZyBtYWlsaW5nIGxpc3QhIA0KPiANCj5U
byBwb3N0IHRvIHRoaXMgbGlzdCwgc2VuZCB5b3VyIGVtYWlsIHRvOiANCj4gDQo+ICAgaWV0ZkBp
ZXRmLm9yZyANCj4gDQo+R2VuZXJhbCBpbmZvcm1hdGlvbiBhYm91dCB0aGUgbWFpbGluZyBsaXN0
IGlzIGF0OiANCj4gDQo+ICAgaHR0cHM6Ly93d3cxLmlldGYub3JnL21haWxtYW4vbGlzdGluZm8v
aWV0ZiANCj4gDQo+SWYgeW91IGV2ZXIgd2FudCB0byB1bnN1YnNjcmliZSBvciBjaGFuZ2UgeW91
ciBvcHRpb25zIChlZywgc3dpdGNoIHRvIA0KPm9yIGZyb20gZGlnZXN0IG1vZGUsIGNoYW5nZSB5
b3VyIHBhc3N3b3JkLCBldGMuKSwgdmlzaXQgeW91ciANCj5zdWJzY3JpcHRpb24gcGFnZSBhdDog
DQo+IA0KPiAgIGh0dHBzOi8vd3d3MS5pZXRmLm9yZy9tYWlsbWFuL29wdGlvbnMvaWV0Zi9mZ2h4
dSU0MGhvdG1haWwuY29tIA0KPiANCj5Zb3UgY2FuIGFsc28gbWFrZSBzdWNoIGFkanVzdG1lbnRz
IHZpYSBlbWFpbCBieSBzZW5kaW5nIGEgbWVzc2FnZSB0bzogDQo+IA0KPiAgIElldGYtcmVxdWVz
dEBpZXRmLm9yZyANCj4gDQo+d2l0aCB0aGUgd29yZCBgaGVscCcgaW4gdGhlIHN1YmplY3Qgb3Ig
Ym9keSAoZG9uJ3QgaW5jbHVkZSB0aGUgDQo+cXVvdGVzKSwgYW5kIHlvdSB3aWxsIGdldCBiYWNr
IGEgbWVzc2FnZSB3aXRoIGluc3RydWN0aW9ucy4gDQo+IA0KPllvdSBtdXN0IGtub3cgeW91ciBw
YXNzd29yZCB0byBjaGFuZ2UgeW91ciBvcHRpb25zIChpbmNsdWRpbmcgY2hhbmdpbmcgDQo+dGhl
IHBhc3N3b3JkLCBpdHNlbGYpIG9yIHRvIHVuc3Vic2NyaWJlLiAgSXQgaXM6IA0KPiANCj4gICBB
YTExMTEgDQo+IA0KPk5vcm1hbGx5LCBNYWlsbWFuIHdpbGwgcmVtaW5kIHlvdSBvZiB5b3VyIGll
dGYub3JnIG1haWxpbmcgbGlzdCANCj5wYXNzd29yZHMgb25jZSBldmVyeSBtb250aCwgYWx0aG91
Z2ggeW91IGNhbiBkaXNhYmxlIHRoaXMgaWYgeW91IA0KPnByZWZlci4gIFRoaXMgcmVtaW5kZXIg
d2lsbCBhbHNvIGluY2x1ZGUgaW5zdHJ1Y3Rpb25zIG9uIGhvdyB0byANCj51bnN1YnNjcmliZSBv
ciBjaGFuZ2UgeW91ciBhY2NvdW50IG9wdGlvbnMuICBUaGVyZSBpcyBhbHNvIGEgYnV0dG9uIG9u
IA0KPnlvdXIgb3B0aW9ucyBwYWdlIHRoYXQgd2lsbCBlbWFpbCB5b3VyIGN1cnJlbnQgcGFzc3dv
cmQgdG8geW91LiANCg==

------=_NextPart_000_001C_01C4426A.76FA2C90
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PWdiMjMxMiI+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNi4w
MC4yNjAwLjAiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+DQo8Qk9E
WSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPjxGT05UIHNpemU9Mj5IZWxsbyBhbGwsPC9GT05UPjwv
RElWPg0KPERJVj4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPkkgYW0gc3RhcnRpbmcg
bXkgTVNjIHByb2plY3Qgb24gYSZuYnNwO25ld2x5IGRldmVsb3BlZCBzdHJlYW0gDQp2aWRlbyBl
bmNvZGluZy9kZWNvZGluZyBzY2hlbWUuIDwvRk9OVD48Rk9OVCBzaXplPTI+V2Ugd2FudCB0byZu
YnNwO2NvbXBhcmUgYW5kIA0KdGVzdCBvdXImbmJzcDtzY2hlbWUgd2l0aCB0aGUgY3VycmVudGx5
IHN0YW5kYXJkIHZpZGVvIGVuY29kaW5nIHNjaGVtZXMgaW4gDQp0aGUmbmJzcDt3aXJlZC93aXJl
bGVzcyBtdWx0aS1jYXN0aW5nIG5ldHdvcmsgZW52aXJvbm1lbnQuJm5ic3A7IFdlIGFyZSANCmNv
bnNpZGVyaW5nIHRvIHVzZSB0aGUgbmV0d29yayBzaW11bGF0b3ImbmJzcDstIEdsb21vc2ltLiZu
YnNwOzwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4N
CjxESVY+PEZPTlQgc2l6ZT0yPlNpbmNlIEkgYW0gbmV3IHRvIHRoZSBHbG9tb3NpbS4gSSBkb24n
dCBrbm93IGhvdyANCnRvJm5ic3A7bW9kaWZ5IGl0IHRvIG1ha2UgaXQgc3VpdCBmb3Igb3VyIHJl
c2VhcmNoIHB1cnBvc2UuIEkgd291bGQgbGlrZSB0byBrbm93IA0Kc29tZSBndWlkZWxpbmVzIG9m
IGhvdyB0byBzdGFydCBteSBwcm9qZWN0IHVzaW5nIEdsb21vc2ltLjwvRk9OVD48L0RJVj4NCjxE
SVY+PEZPTlQgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPldl
IHdpbGwgZW5jb2RlIHRoZSB2aWRlbyBpbnRvIGZyYW1lcyBhbmQgZmVlZCB0aGVtIHRvIA0KdGhl
Jm5ic3A7R2xvbW9zaW0gYW5kIHJlY2VpdmUgdGhlbSBhdCBtdWx0aXBsZSBlbmRzLiZuYnNwOyBV
cG9uIHJlY2VpdmluZywgdGhlIA0KcmVjZWl2ZXMgd2lsbCBkZWNvZGUgdGhlIGZyYW1lcyBpbnRv
IHN0cmVhbSB2aWRlbyBhZ2Fpbi4mbmJzcDsgPC9GT05UPjxGT05UIA0Kc2l6ZT0yPlRoZSBtYWlu
IGdvYWwgb2YgdXNpbmcgdGhlIHNpbXVsYXRvciBpcyB0byBzZWUgaG93IHRoZSBlbmNvZGluZy9k
ZWNvZGluZyANCnNjaGVtZSB3b3JrIGluIHRoZSB1bnJlbGlhYmxlIG5ldHdvcmsgZW52aXJvbm1l
bnQuJm5ic3A7IDwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8
L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPkkgd291bGQgbGlrZSB0byBrbm93Jm5ic3A7IGhvdyBj
YW4gSSBtb2RpZnkgdGhlIEdsb21vc2ltIGluIA0Kb3JkZXIgdG8gdHJhbnNmZXIgdGhvc2UgY3Vz
dG9tIG1hZGUgImZyYW1lIiBkYXRhPyZuYnNwOyB3aGljaCBwYXJ0IGluIHRoZSANCkdsb21vc2lt
IHNoYWxsIEkgbW9kaWZ5PyZuYnNwOyBTaGFsbCBJIHN0YXJ0IGZyb20gbG9va2luZyBhdCBjb2Rl
cyBpbiANCnRoZSZuYnNwO0FwcGxpY2F0aW9uIExheWVyPzwvRk9OVD48L0RJVj4NCjxESVY+Jm5i
c3A7PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj5XZSB3aWxsIHVzZSB0aGUgT0RNUlAgcm91dGlu
ZyBwcm90b2NvbCBhbmQgSUVFRTgwMi4xMSBhbmQvb3IgDQpVRFAuPC9GT05UPjwvRElWPg0KPERJ
Vj48Rk9OVCBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+PC9G
T05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+QW55IHN1Z2dlc3Rpb24gaXMgdmVy
eSB3ZWxjb21lZC4mbmJzcDsgVGhhbmtzIGluIA0KYWR2YW5jZSE8L0ZPTlQ+PC9ESVY+DQo8RElW
PiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJ
Vj48Rk9OVCBzaXplPTI+QmVzdCByZWdhcmRzPC9GT05UPjwvRElWPg0KPERJVj4mbmJzcDs8L0RJ
Vj4NCjxESVY+PEZPTlQgc2l6ZT0yPkZyYW5rPEJSPjwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQg
c2l6ZT0yPg0KPERJViBjbGFzcz1SVEU+DQo8UD48QlI+PEJSPjwvUD48L0RJVj48QlI+PEJSPjxC
Uj5eIF4gDQo8RElWPjwvRElWPnwgDQo8RElWPjwvRElWPi0tLSANCjxESVY+PC9ESVY+DQo8RElW
PjwvRElWPg0KPERJVj48L0RJVj4NCjxESVY+PC9ESVY+Jmd0O0Zyb206IGlldGYtcmVxdWVzdEBp
ZXRmLm9yZyANCjxESVY+PC9ESVY+Jmd0O1RvOiBmZ2h4dUBob3RtYWlsLmNvbSANCjxESVY+PC9E
SVY+Jmd0O1N1YmplY3Q6IFdlbGNvbWUgdG8gdGhlICJJZXRmIiBtYWlsaW5nIGxpc3QgKERpZ2Vz
dCBtb2RlKSANCjxESVY+PC9ESVY+Jmd0O0RhdGU6IFR1ZSwgMjUgTWF5IDIwMDQgMTQ6MjA6NDIg
LTA0MDAgDQo8RElWPjwvRElWPiZndDsgDQo8RElWPjwvRElWPiZndDtXZWxjb21lIHRvIHRoZSBJ
ZXRmQGlldGYub3JnIG1haWxpbmcgbGlzdCEgDQo8RElWPjwvRElWPiZndDsgDQo8RElWPjwvRElW
PiZndDtUbyBwb3N0IHRvIHRoaXMgbGlzdCwgc2VuZCB5b3VyIGVtYWlsIHRvOiANCjxESVY+PC9E
SVY+Jmd0OyANCjxESVY+PC9ESVY+Jmd0OyZuYnNwOyZuYnNwOyBpZXRmQGlldGYub3JnIA0KPERJ
Vj48L0RJVj4mZ3Q7IA0KPERJVj48L0RJVj4mZ3Q7R2VuZXJhbCBpbmZvcm1hdGlvbiBhYm91dCB0
aGUgbWFpbGluZyBsaXN0IGlzIGF0OiANCjxESVY+PC9ESVY+Jmd0OyANCjxESVY+PC9ESVY+Jmd0
OyZuYnNwOyZuYnNwOyBodHRwczovL3d3dzEuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pZXRm
IA0KPERJVj48L0RJVj4mZ3Q7IA0KPERJVj48L0RJVj4mZ3Q7SWYgeW91IGV2ZXIgd2FudCB0byB1
bnN1YnNjcmliZSBvciBjaGFuZ2UgeW91ciBvcHRpb25zIChlZywgDQpzd2l0Y2ggdG8gDQo8RElW
PjwvRElWPiZndDtvciBmcm9tIGRpZ2VzdCBtb2RlLCBjaGFuZ2UgeW91ciBwYXNzd29yZCwgZXRj
LiksIHZpc2l0IHlvdXIgDQo8RElWPjwvRElWPiZndDtzdWJzY3JpcHRpb24gcGFnZSBhdDogDQo8
RElWPjwvRElWPiZndDsgDQo8RElWPjwvRElWPiZndDsmbmJzcDsmbmJzcDsgDQpodHRwczovL3d3
dzEuaWV0Zi5vcmcvbWFpbG1hbi9vcHRpb25zL2lldGYvZmdoeHUlNDBob3RtYWlsLmNvbSANCjxE
SVY+PC9ESVY+Jmd0OyANCjxESVY+PC9ESVY+Jmd0O1lvdSBjYW4gYWxzbyBtYWtlIHN1Y2ggYWRq
dXN0bWVudHMgdmlhIGVtYWlsIGJ5IHNlbmRpbmcgYSBtZXNzYWdlIA0KdG86IA0KPERJVj48L0RJ
Vj4mZ3Q7IA0KPERJVj48L0RJVj4mZ3Q7Jm5ic3A7Jm5ic3A7IElldGYtcmVxdWVzdEBpZXRmLm9y
ZyANCjxESVY+PC9ESVY+Jmd0OyANCjxESVY+PC9ESVY+Jmd0O3dpdGggdGhlIHdvcmQgYGhlbHAn
IGluIHRoZSBzdWJqZWN0IG9yIGJvZHkgKGRvbid0IGluY2x1ZGUgdGhlIA0KPERJVj48L0RJVj4m
Z3Q7cXVvdGVzKSwgYW5kIHlvdSB3aWxsIGdldCBiYWNrIGEgbWVzc2FnZSB3aXRoIGluc3RydWN0
aW9ucy4gDQo8RElWPjwvRElWPiZndDsgDQo8RElWPjwvRElWPiZndDtZb3UgbXVzdCBrbm93IHlv
dXIgcGFzc3dvcmQgdG8gY2hhbmdlIHlvdXIgb3B0aW9ucyAoaW5jbHVkaW5nIA0KY2hhbmdpbmcg
DQo8RElWPjwvRElWPiZndDt0aGUgcGFzc3dvcmQsIGl0c2VsZikgb3IgdG8gdW5zdWJzY3JpYmUu
Jm5ic3A7Jm5ic3A7SXQgaXM6IA0KPERJVj48L0RJVj4mZ3Q7IA0KPERJVj48L0RJVj4mZ3Q7Jm5i
c3A7Jm5ic3A7IEFhMTExMSANCjxESVY+PC9ESVY+Jmd0OyANCjxESVY+PC9ESVY+Jmd0O05vcm1h
bGx5LCBNYWlsbWFuIHdpbGwgcmVtaW5kIHlvdSBvZiB5b3VyIGlldGYub3JnIG1haWxpbmcgbGlz
dCANCjxESVY+PC9ESVY+Jmd0O3Bhc3N3b3JkcyBvbmNlIGV2ZXJ5IG1vbnRoLCBhbHRob3VnaCB5
b3UgY2FuIGRpc2FibGUgdGhpcyBpZiB5b3UgDQo8RElWPjwvRElWPiZndDtwcmVmZXIuJm5ic3A7
Jm5ic3A7VGhpcyByZW1pbmRlciB3aWxsIGFsc28gaW5jbHVkZSBpbnN0cnVjdGlvbnMgDQpvbiBo
b3cgdG8gDQo8RElWPjwvRElWPiZndDt1bnN1YnNjcmliZSBvciBjaGFuZ2UgeW91ciBhY2NvdW50
IG9wdGlvbnMuJm5ic3A7Jm5ic3A7VGhlcmUgaXMgDQphbHNvIGEgYnV0dG9uIG9uIA0KPERJVj48
L0RJVj4mZ3Q7eW91ciBvcHRpb25zIHBhZ2UgdGhhdCB3aWxsIGVtYWlsIHlvdXIgY3VycmVudCBw
YXNzd29yZCB0byB5b3UuIA0KPC9ESVY+PC9GT05UPjwvQk9EWT48L0hUTUw+DQo=

------=_NextPart_000_001C_01C4426A.76FA2C90--


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

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

--===============0447146231==--



From ietf-bounces@ietf.org  Wed May 26 16:12: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 QAA11616
	for <ietf-archive@ietf.org>; Wed, 26 May 2004 16:12: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 1BT4ll-00062x-BN
	for ietf-archive@ietf.org; Wed, 26 May 2004 16:12:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BT4kl-0005vT-00
	for ietf-archive@ietf.org; Wed, 26 May 2004 16:11:56 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BT4jp-0005kA-00; Wed, 26 May 2004 16:10:57 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BT4T7-0005ZC-So; Wed, 26 May 2004 15:53:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BSlCT-00042E-0e
	for ietf@megatron.ietf.org; Tue, 25 May 2004 19:19:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06761
	for <ietf@ietf.org>; Tue, 25 May 2004 19:19: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 1BSlCP-0007JB-13
	for ietf@ietf.org; Tue, 25 May 2004 19:19:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BSlBa-0007Fd-00
	for ietf@ietf.org; Tue, 25 May 2004 19:18:19 -0400
Received: from zak.ecotroph.net ([216.93.164.123])
	by ietf-mx with esmtp (Exim 4.12) id 1BSlAq-0007Bt-00
	for ietf@ietf.org; Tue, 25 May 2004 19:17:32 -0400
Received: from [10.0.1.70] ([::ffff:64.83.8.178])
	(AUTH: LOGIN anewton, SSL: TLSv1/SSLv3,128bits,RC4-SHA)
	by zak.ecotroph.net with esmtp; Tue, 25 May 2004 19:17:32 -0400
	id 0005C5FA.40B3D40C.00000640
In-Reply-To: <200405241749.i4OHn2X1004192@turing-police.cc.vt.edu>
References: <OKEPLEIOJKFGFGCKMDKJKEDMCDAA.cdel@firsthand.net>
	<200405241749.i4OHn2X1004192@turing-police.cc.vt.edu>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <B2403217-AEA1-11D8-A66A-000A95B3BA44@hxr.us>
Content-Transfer-Encoding: 7bit
From: Andrew Newton <andy@hxr.us>
Date: Tue, 25 May 2004 19:17:31 -0400
To: Valdis.Kletnieks@vt.edu
X-Mailer: Apple Mail (2.613)
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 26 May 2004 15:53:40 -0400
Cc: cdel@firsthand.net, ietf@ietf.org
Subject: Re: spoofing email addresses 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit


On May 24, 2004, at 1:49 PM, Valdis.Kletnieks@vt.edu wrote:
>
> In fact, there isn't any sane way to detect "inconsistent" header 
> information
> without external hints - this is the reason why there's the SPF 
> proposal, the
> Yahoo domain-keys proposal, and Microsoft's proposal.

And MARID.

-andy


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


From ietf-bounces@ietf.org  Wed May 26 16:12:58 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11649
	for <ietf-archive@ietf.org>; Wed, 26 May 2004 16:12:58 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BT4ln-00063H-Ho
	for ietf-archive@ietf.org; Wed, 26 May 2004 16:12:59 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BT4kn-0005vp-00
	for ietf-archive@ietf.org; Wed, 26 May 2004 16:11:58 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BT4jp-0005kB-00; Wed, 26 May 2004 16:10:57 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BT4Sy-0005Q0-9K; Wed, 26 May 2004 15:53:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BSoKq-0002D3-PX
	for ietf@megatron.ietf.org; Tue, 25 May 2004 22:40:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA16625
	for <ietf@ietf.org>; Tue, 25 May 2004 22:39: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 1BSoK0-000071-M4
	for ietf@ietf.org; Tue, 25 May 2004 22:39:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BSoJ0-0007iz-00
	for ietf@ietf.org; Tue, 25 May 2004 22:38:10 -0400
Received: from shell4.bayarea.net ([209.128.82.1])
	by ietf-mx with esmtp (Exim 4.12) id 1BSoI1-0007XA-00
	for ietf@ietf.org; Tue, 25 May 2004 22:37:09 -0400
Received: from localhost (heard@localhost)
	by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id i4Q2b4r08870
	for <ietf@ietf.org>; Tue, 25 May 2004 19:37:04 -0700
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Tue, 25 May 2004 19:37:02 -0700 (PDT)
From: "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: ietf@ietf.org
Message-ID: <Pine.LNX.4.10.10405251928001.6788-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailman-Approved-At: Wed, 26 May 2004 15:53:29 -0400
Subject: http://www.ietf.org/WG-WEB-Mail.html
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

I see that http://www.ietf.org/WG-WEB-Mail.html, which used to point
to HTML working group mailing list archives, now points instead to
the stuff on the WG charter pages, which consist mostly of
text-based FTP archives, and in may cases the links are broken.

I know that there were a lot of broken links on the old page, but
IMHO this one is much worse.  Can we please have the old page back?

Mike Heard


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


From ietf-bounces@ietf.org  Wed May 26 17:12: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 RAA17597
	for <ietf-archive@ietf.org>; Wed, 26 May 2004 17:12: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 1BT5h7-0006zY-NF
	for ietf-archive@ietf.org; Wed, 26 May 2004 17:12:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BT5g0-0006mH-00
	for ietf-archive@ietf.org; Wed, 26 May 2004 17:11:06 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BT5eE-0006NP-00; Wed, 26 May 2004 17:09:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BT4nL-0004oY-Le; Wed, 26 May 2004 16:14:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BT4cN-0000JK-Bw
	for ietf@megatron.ietf.org; Wed, 26 May 2004 16:03: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 QAA11058
	for <ietf@ietf.org>; Wed, 26 May 2004 16:03: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 1BT4cF-00056H-BR
	for ietf@ietf.org; Wed, 26 May 2004 16:03:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BT4bB-0004yn-00
	for ietf@ietf.org; Wed, 26 May 2004 16:02:01 -0400
Received: from zak.ecotroph.net ([216.93.164.123])
	by ietf-mx with esmtp (Exim 4.12) id 1BT4a5-0004pk-00
	for ietf@ietf.org; Wed, 26 May 2004 16:00:53 -0400
Received: from thinkingcat.com ([::ffff:216.168.239.87])
	(AUTH: LOGIN leslie, TLS: TLSv1/SSLv3,256bits,AES256-SHA)
	by zak.ecotroph.net with esmtp; Wed, 26 May 2004 16:00:52 -0400
	id 0005C5FA.40B4F774.0000731D
Message-ID: <40B4F72F.8020401@thinkingcat.com>
Date: Wed, 26 May 2004 15:59:43 -0400
From: Leslie Daigle <leslie@thinkingcat.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031114
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Cc: Harald Tveit Alvestrand <harald@alvestrand.no>
Subject: Update on AdminRest activities
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit


Since the Seoul plenary meetings, Harald and I have been
working on our take-away action items.  We had the opportunity
to talk with the ISOC Board in mid-May.  We reviewed briefly the
trajectory set in motion from the AdvComm document, and outlined the
framework that we presented in plenary in Seoul (the "AdminRest"
framework, draft-daigle-adminrest).  Following up on our statements
in Seoul, we asked for support to address some of the cross-organization
and specific organization tasks for current operational needs,
and to support the task of exploring the AdminRest framework to the
extent of producing more of a concrete proposal.  I'm happy to
report that the ISOC BoT was indeed very supportive of this
effort.  The specifics (i.e., ISOC Board resolution) will be
published as part of the ISOC Board meeting minutes.

The highlights of that support include the allocation of
an ISOC budget sum, not to exceed $250,000,  to be spent over a six
month period for personnel, incidental expenses, and legal and 
accounting fees to hire and manage a consultant who will complete the
analysis started in RFC 3716 and make recommendations regarding the
organizational requirements and potential organizational models of the
IETF.

The first step, clearly, is to find and hire the appropriate
person.  We have a few people in mind to talk to, but as we can
always use pointers to people we may not have thought of, here's
an outline of the characteristics and expectations we're using
as guidelines:

This is a support function is not intended as a policy-making role,
but intended to execute and clarify the policy set forth by the
IETF leadership, reporting to the ISOC president (as an ISOC project).
Essentially, we are looking for someone we can work with; the
kinds of deliverables and requiremed skills are as outlined below.

Deliverables for the project will include:

      Data Flow:  a set of requirements for implementing appropriate
      tracking of IETF documents and reporting of status across the
      support organizations.

      RFC Editor contract:  a negotiated contract that is agreeable to
      all concerned parties.

      Administrative restructuring:  documentation and support as
      appropriate to the continued evolution of the restructuring
      effort, which is continuously reviewed by the IAB, IESG and the
      rest of the IETF community.

Types of activities/tasks this will include:

  - Assist in drafting the proposed structure/bylaws for the IETF 
administrative entity
  - Revising proposed structure/bylaws based on the public review, 
including reviews by competent counsel
  - Negotiate the contracts for RFC Editor as a model for eventual use 
by the IETF administrative entity
  - Interacting with the RFC Editor, IANA and Secretariat to determine 
the requirements for inter-organizational document flow matched to 
overall IETF process needs


So from this, we have the required skill set:

- understanding inter-organizational relationships and document flows
- ability in contract negotiation
- insight into organization formalization
- experience with the creation of organizations (preferably nonprofits)
- understanding of the legal aspects of such an organization
- understanding of the financial aspects of such an organization


(all of this with the understanding that specific other expertise,
e.g., financial and legal advice, can be brought in on an as-needed
basis).


We hope to identify a suitable candidate in the upcoming weeks.

Leslie.




-- 

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



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


From ietf-bounces@ietf.org  Wed May 26 17:38:01 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20788
	for <ietf-archive@ietf.org>; Wed, 26 May 2004 17:38: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 1BT665-0003DE-Sm
	for ietf-archive@ietf.org; Wed, 26 May 2004 17:38:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BT655-00033v-00
	for ietf-archive@ietf.org; Wed, 26 May 2004 17:37:00 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BT647-0002n3-00; Wed, 26 May 2004 17:35:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BT5lL-0006FX-IF; Wed, 26 May 2004 17:16:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BT5ZH-0008QM-QH
	for ietf@megatron.ietf.org; Wed, 26 May 2004 17:04:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16478
	for <ietf@ietf.org>; Wed, 26 May 2004 17:03: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 1BT5Z1-0005Zg-GO
	for ietf@ietf.org; Wed, 26 May 2004 17:03:51 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BT5Wk-0005GK-00
	for ietf@ietf.org; Wed, 26 May 2004 17:01:31 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12) id 1BT5Vm-00052B-00
	for ietf@ietf.org; Wed, 26 May 2004 17:00:30 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.11/8.12.11) id i4QL00Ua008101
	for ietf@ietf.org env-from <vjs>;
	Wed, 26 May 2004 15:00:00 -0600 (MDT)
Date: Wed, 26 May 2004 15:00:00 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200405262100.i4QL00Ua008101@calcite.rhyolite.com>
To: ietf@ietf.org
References: <B2403217-AEA1-11D8-A66A-000A95B3BA44@hxr.us>
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

> From: Andrew Newton <andy@hxr.us>

> On May 24, 2004, at 1:49 PM, Valdis.Kletnieks@vt.edu wrote:
> >
> > In fact, there isn't any sane way to detect "inconsistent" header 
> > information
> > without external hints - this is the reason why there's the SPF 
> > proposal, the
> > Yahoo domain-keys proposal, and Microsoft's proposal.
>
> And MARID.

I don't see any of those proposals and their competitors as sane.
Some of them, such as SPF, do not even meet their own design goals
as stated informally by their advocates.  Others such as domain-keys
do not seem to do anything that is not already done by SMTP-TLS, despite
the goals in the I-D that seem to be closer to S/MIME.  None of them
have much to do with spam, but only with a currently popular mode of
attack used by spammers.  None have any hope of affecting even that
particular attack mode for years, because none can have any significant
effect until deployed on most SMTP clients.  Many seem to be based on
insufficient familiarity with the nature of SMTP (e.g. SPF's incredible
source-routing scheme) and the urge to Do Something Now regardless of
actual results.


Vernon Schryver    vjs@rhyolite.com

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


From ietf-bounces@ietf.org  Wed May 26 18:55: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 SAA26422
	for <ietf-archive@ietf.org>; Wed, 26 May 2004 18:55: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 1BT7Ih-0003r9-UM
	for ietf-archive@ietf.org; Wed, 26 May 2004 18:55:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BT7Hn-0003lY-00
	for ietf-archive@ietf.org; Wed, 26 May 2004 18:54:12 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BT7HO-0003ff-00; Wed, 26 May 2004 18:53:46 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BT73y-0002Mx-Me; Wed, 26 May 2004 18:39:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BT6qd-0006by-Qi
	for ietf@megatron.ietf.org; Wed, 26 May 2004 18:26: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 SAA24990
	for <ietf@ietf.org>; Wed, 26 May 2004 18:26: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 1BT6qc-00014m-CX
	for ietf@ietf.org; Wed, 26 May 2004 18:26:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BT6pl-0000zi-00
	for ietf@ietf.org; Wed, 26 May 2004 18:25:14 -0400
Received: from nyc.rimasec.net
	([209.133.8.161] helo=mta.rimasec.net ident=postfix)
	by ietf-mx with esmtp (Exim 4.12) id 1BT6pA-0000uO-00
	for ietf@ietf.org; Wed, 26 May 2004 18:24:36 -0400
Received: from localhost (mta.rimasec.net [209.133.8.163])
	by mta.rimasec.net (Postfix) with ESMTP
	id D66132B83D; Wed, 26 May 2004 18:24:34 -0400 (EDT)
Received: from mta.rimasec.net ([209.133.8.163])
	by localhost (nyc.rimasec.net [209.133.8.163]) (amavisd-new, port 10024)
	with ESMTP id 84377-09; Wed, 26 May 2004 18:24:34 -0400 (EDT)
Received: from localhost (localhost.rimasec.net [127.0.0.1])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client did not present a certificate)
	by mta.rimasec.net (Postfix) with ESMTP
	id 292242B818; Wed, 26 May 2004 18:24:34 -0400 (EDT)
Date: Wed, 26 May 2004 18:24:32 -0400 (EDT)
From: James Denness <jd@nyc.rimasec.net>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
In-Reply-To: <200405262100.i4QL00Ua008101@calcite.rhyolite.com>
Message-ID: <20040526181202.K84741@nyc.rimasec.net>
References: <B2403217-AEA1-11D8-A66A-000A95B3BA44@hxr.us>
	<200405262100.i4QL00Ua008101@calcite.rhyolite.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanned: by amavisd-new at mta.rimasec.net
Cc: ietf@ietf.org
Subject: Request for comments on draft mail protocol
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

Hello,

I am currently involved in a project to create an internet-draft for a
domain/key based system allowing mail domains to be validated using rsa
keys, distributed using the DNS system, with minimal modification to
existing infrastructure. Does a specification for such a system already
exist? I have many ideas for extentions to the existing SMTP protocol, as
well as plans for a derivative protocol incorporating this key-based
system as a more secure and verifiable method of exchanging mail. If
anyone is interested, I would appreciate being contacted off-list to
discuss the possible formation of a working group to discuss such ideas.

Regards,
James Denness

On Wed, 26 May 2004, Vernon Schryver wrote:

> Date: Wed, 26 May 2004 15:00:00 -0600 (MDT)
> From: Vernon Schryver <vjs@calcite.rhyolite.com>
> To: ietf@ietf.org
> Subject: Re: spoofing email addresses
>
> > From: Andrew Newton <andy@hxr.us>
>
> > On May 24, 2004, at 1:49 PM, Valdis.Kletnieks@vt.edu wrote:
> > >
> > > In fact, there isn't any sane way to detect "inconsistent" header
> > > information
> > > without external hints - this is the reason why there's the SPF
> > > proposal, the
> > > Yahoo domain-keys proposal, and Microsoft's proposal.
> >
> > And MARID.
>
> I don't see any of those proposals and their competitors as sane.
> Some of them, such as SPF, do not even meet their own design goals
> as stated informally by their advocates.  Others such as domain-keys
> do not seem to do anything that is not already done by SMTP-TLS, despite
> the goals in the I-D that seem to be closer to S/MIME.  None of them
> have much to do with spam, but only with a currently popular mode of
> attack used by spammers.  None have any hope of affecting even that
> particular attack mode for years, because none can have any significant
> effect until deployed on most SMTP clients.  Many seem to be based on
> insufficient familiarity with the nature of SMTP (e.g. SPF's incredible
> source-routing scheme) and the urge to Do Something Now regardless of
> actual results.
>
>
> Vernon Schryver    vjs@rhyolite.com
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>

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


From ietf-bounces@ietf.org  Wed May 26 19:27: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 TAA28143
	for <ietf-archive@ietf.org>; Wed, 26 May 2004 19:27: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 1BT7nj-00077d-Fv
	for ietf-archive@ietf.org; Wed, 26 May 2004 19:27:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BT7mm-00070E-00
	for ietf-archive@ietf.org; Wed, 26 May 2004 19:26:13 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BT7lw-0006pU-00; Wed, 26 May 2004 19:25:20 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BT7bu-0005x6-Q6; Wed, 26 May 2004 19:14:58 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BT7UJ-0003Dy-42
	for ietf@megatron.ietf.org; Wed, 26 May 2004 19:07:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27080
	for <ietf@ietf.org>; Wed, 26 May 2004 19:07: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 1BT7UH-0005FS-Mj
	for ietf@ietf.org; Wed, 26 May 2004 19:07:05 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BT7TP-0005A7-00
	for ietf@ietf.org; Wed, 26 May 2004 19:06:12 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12) id 1BT7Sc-0004yC-00
	for ietf@ietf.org; Wed, 26 May 2004 19:05:22 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.11/8.12.11) id i4QN4qP7042280
	for ietf@ietf.org env-from <vjs>;
	Wed, 26 May 2004 17:04:52 -0600 (MDT)
Date: Wed, 26 May 2004 17:04:52 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200405262304.i4QN4qP7042280@calcite.rhyolite.com>
To: ietf@ietf.org
References: <20040526181202.K84741@nyc.rimasec.net>
Subject: Re: Request for comments on draft mail protocol
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

> From: James Denness 

> I am currently involved in a project to create an internet-draft for a
> domain/key based system allowing mail domains to be validated using rsa
> keys, distributed using the DNS system, with minimal modification to
> existing infrastructure. Does a specification for such a system already
> exist? I have many ideas for extentions to the existing SMTP protocol, as
> well as plans for a derivative protocol incorporating this key-based
> system as a more secure and verifiable method of exchanging mail. If
> anyone is interested, I would appreciate being contacted off-list to
> discuss the possible formation of a working group to discuss such ideas.

what about http://ietf.org/html.charters/marid-charter.html ?

It might be interesting to contact the author of
draft-delany-domainkeys-base-00.txt
or the authors of the at least half a dozen other proposals to use
public keys or other mechanisms along with the domain name system to
authenticate mail senders.


My rather negative view of the area can be inferred from
http://www.rhyolite.com/anti-spam/you-might-be.html


Vernon Schryver    vjs@rhyolite.com

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


From ietf-bounces@ietf.org  Wed May 26 19:48: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 TAA29396
	for <ietf-archive@ietf.org>; Wed, 26 May 2004 19:48: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 1BT88C-0001i2-Ix
	for ietf-archive@ietf.org; Wed, 26 May 2004 19:48:20 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BT879-0001Wq-00
	for ietf-archive@ietf.org; Wed, 26 May 2004 19:47:16 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BT864-0001IF-00; Wed, 26 May 2004 19:46:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BT7pm-00020k-Qe; Wed, 26 May 2004 19:29:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BT7gm-0007MV-Hw
	for ietf@megatron.ietf.org; Wed, 26 May 2004 19:20: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 TAA27656
	for <ietf@ietf.org>; Wed, 26 May 2004 19:19: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 1BT7gl-0006Rv-2C
	for ietf@ietf.org; Wed, 26 May 2004 19:19:59 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BT7fp-0006MP-00
	for ietf@ietf.org; Wed, 26 May 2004 19:19:02 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12) id 1BT7ey-0006Cx-00
	for ietf@ietf.org; Wed, 26 May 2004 19:18:08 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.11/8.12.11) id i4QNHcqM044838
	for ietf@ietf.org env-from <vjs>;
	Wed, 26 May 2004 17:17:38 -0600 (MDT)
Date: Wed, 26 May 2004 17:17:38 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200405262317.i4QNHcqM044838@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: out-of-office notifications
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL,HTML_MESSAGE autolearn=no 
	version=2.60

How many years must this stuff continue?  If someone asked me, I'd
say that the people responsible for the enclosed meant to ask the
Secretariat to be unsubscribed with prejudice from all IETF mailing
lists.  Then there are people who send HTML out-of-office noise.

This stuff is a tad ironic given the recently expressed concerns about
bad guys checking the IETF attendance list.

How about a Modest Proposal:  no one be allowed to subscribe to any
IETF mailing list without submitting evidence that Microsoft MUAs or
MTAs are not in use.  Those with sufficient clues to contribute usefully
could doubtless arrange things so that even if they were using Microsoft
virus, worm, spam, and OFN distrubution malware, their mail headers
would lie.


Vernon Schryver    vjs@rhyolite.com


> From: Eric Burger <eburger@brooktrout.com>
> To: Vernon Schryver <vjs@calcite.rhyolite.com>
> Subject: Out of Office AutoReply: spoofing email addresses
>
> Not reachable by e-mail or phone until 6/2, and then only by e-mail.


> From: Paul Georgiou <pgeorgiou@tor.microage.ca>
> To: Vernon Schryver <vjs@calcite.rhyolite.com>
> Subject: Out of Office AutoReply: spoofing email addresses
>
> Please note I will be out of the office from Friday May 21st to Tuesday May
> 25th inclusive without access to email or Voicemail. For urgent matters
> please contact Rosemary Hagholm, rhagholm@tor.microage.ca, 416-410-6050, or
> David YoungPow, dyounpow@tor.microage.ca, 905-264-5785.


> From: WaterCove Email <email@watercove.com>
> To: Vernon Schryver <vjs@calcite.rhyolite.com>
> Subject: WaterCove Email
>
> Hello,
>
> The watercove.com email address you sent to is no longer active.  With the
> recent acquisition of WaterCove by Alcatel, please contact the intended
> recipient directly to get their updated email address.
>
> Thank you.


> From: Joerg Reichelt <Joerg.Reichelt@webex.com>
> To: Vernon Schryver <vjs@calcite.rhyolite.com>
> Subject: Out of Office AutoReply: spoofing email addresses
>
> This message is in MIME format. Since your mail reader does not understand
> this format, some or all of this message may not be legible.
>
> ------_=_NextPart_001_01C4436B.0F91EDC0
> Content-Type: text/plain;
> 	charset="windows-1252"
>
> I am currently out of the office and will be back on 6/14/2004. In case of
> urgent matters, please contact 
>     Eric Yuan 
>     (408) 944-4928
>    Eric.Yuan@webex.com
>
> Thanks, 
> Joerg Reichelt
>
> ------_=_NextPart_001_01C4436B.0F91EDC0
> Content-Type: text/html;
> 	charset="windows-1252"
>
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
> <HTML>
> <HEAD>
> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=windows-1252">
> <META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.45">
> <TITLE>Out of Office AutoReply: spoofing email addresses</TITLE>
> </HEAD>
> <BODY>
>
> <P><FONT SIZE=2>I am currently out of the office and will be back on 6/14/2004. In case of urgent matters, please contact </FONT>
> <BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; Eric Yuan </FONT>
> <BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; (408) 944-4928</FONT>
> <BR><FONT SIZE=2>&nbsp;&nbsp; Eric.Yuan@webex.com</FONT>
> </P>
>
> <P><FONT SIZE=2>Thanks, </FONT>
> <BR><FONT SIZE=2>Joerg Reichelt</FONT>
> </P>
>
> </BODY>
> </HTML>
> ------_=_NextPart_001_01C4436B.0F91EDC0--
>

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


From ietf-bounces@ietf.org  Thu May 27 08:42:44 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA21324
	for <ietf-archive@ietf.org>; Thu, 27 May 2004 08:42: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 1BTKDc-00040x-Pu
	for ietf-archive@ietf.org; Thu, 27 May 2004 08:42:44 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTKCc-0003kU-00
	for ietf-archive@ietf.org; Thu, 27 May 2004 08:41:43 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BTKBn-0003JB-00; Thu, 27 May 2004 08:40:51 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BTJPF-0004Zz-Sc; Thu, 27 May 2004 07:50:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BT6UQ-0001cu-Bg
	for ietf@megatron.ietf.org; Wed, 26 May 2004 18:03: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 SAA22356
	for <ietf@ietf.org>; Wed, 26 May 2004 18:02: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 1BT6UF-0006BM-Oe
	for ietf@ietf.org; Wed, 26 May 2004 18:02:59 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BT6TI-000663-00
	for ietf@ietf.org; Wed, 26 May 2004 18:02:00 -0400
Received: from sa.vix.com ([204.152.187.1]) by ietf-mx with esmtp (Exim 4.12)
	id 1BT6SM-0005wG-00
	for ietf@ietf.org; Wed, 26 May 2004 18:01:02 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id 7CEE513E07; Wed, 26 May 2004 22:00:26 +0000 (GMT)
To: ietf@ietf.org
References: <B2403217-AEA1-11D8-A66A-000A95B3BA44@hxr.us>
From: Paul Vixie <vixie@vix.com>
Date: 26 May 2004 22:00:26 +0000
In-Reply-To: <B2403217-AEA1-11D8-A66A-000A95B3BA44@hxr.us>
Message-ID: <g3ekp626it.fsf@sa.vix.com>
Lines: 9
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailman-Approved-At: Thu, 27 May 2004 07:50:38 -0400
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

> > In fact, there isn't any sane way to detect "inconsistent" header
> > information without external hints - this is the reason why there's the
> > SPF proposal, the Yahoo domain-keys proposal, and Microsoft's proposal.
> 
> And MARID.

and don't forget <HREF="http://sa.vix.com/~vixie/mailfrom.txt">MAIL-FROM</A>.
-- 
Paul Vixie

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


From ietf-bounces@ietf.org  Thu May 27 11:42: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 LAA03162
	for <ietf-archive@ietf.org>; Thu, 27 May 2004 11:42: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 1BTN1w-0000qp-Pl
	for ietf-archive@ietf.org; Thu, 27 May 2004 11:42:52 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTN18-0000bQ-00
	for ietf-archive@ietf.org; Thu, 27 May 2004 11:42:02 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BTN0K-0000N6-00; Thu, 27 May 2004 11:41:12 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BTN0J-0007wt-Kb; Thu, 27 May 2004 11:41:12 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BTMbm-0005Vv-1S; Thu, 27 May 2004 11:15:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BTMLF-0007rF-MA
	for ietf@megatron.ietf.org; Thu, 27 May 2004 10:58: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 KAA00479
	for <ietf@ietf.org>; Thu, 27 May 2004 10:58:43 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BTMLE-0005KD-Su
	for ietf@ietf.org; Thu, 27 May 2004 10:58:44 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTMKE-00050C-00
	for ietf@ietf.org; Thu, 27 May 2004 10:57:43 -0400
Received: from turing-police.cc.vt.edu ([128.173.14.107] ident=root)
	by ietf-mx with esmtp (Exim 4.12) id 1BTMJC-0004dT-00
	for ietf@ietf.org; Thu, 27 May 2004 10:56:38 -0400
Received: from turing-police.cc.vt.edu (IDENT:valdis@localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.13.0.Beta2/8.13.0.Beta2) with ESMTP id
	i4REuawJ022844; Thu, 27 May 2004 10:56:36 -0400
Message-Id: <200405271456.i4REuawJ022844@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Vernon Schryver <vjs@calcite.rhyolite.com>
In-Reply-To: Your message of "Wed, 26 May 2004 15:00:00 MDT."
	<200405262100.i4QL00Ua008101@calcite.rhyolite.com> 
References: <B2403217-AEA1-11D8-A66A-000A95B3BA44@hxr.us>
	<200405262100.i4QL00Ua008101@calcite.rhyolite.com>
Mime-Version: 1.0
Date: Thu, 27 May 2004 10:56:36 -0400
Cc: ietf@ietf.org
Subject: Re: spoofing email addresses 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1686554745=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60

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

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

On Wed, 26 May 2004 15:00:00 MDT, Vernon Schryver <vjs@calcite.rhyolite.com>  said:
> I don't see any of those proposals and their competitors as sane.

Oh, I wasn't addressing whether the proposals were workable, merely listing
proposals motivated by the fact that verifying the legitimacy of a sending
machine is difficult.

As you correctly note below, the proposals aren't even a workable solution to
the real problem (I've yet to see a proposal that works if the spammers start
utilizing zombie machines that snarf the already-stored credentials of the user
to send mail)....

> Some of them, such as SPF, do not even meet their own design goals
> as stated informally by their advocates.  Others such as domain-keys
> do not seem to do anything that is not already done by SMTP-TLS, despite
> the goals in the I-D that seem to be closer to S/MIME.  None of them
> have much to do with spam, but only with a currently popular mode of
> attack used by spammers.  None have any hope of affecting even that
> particular attack mode for years, because none can have any significant
> effect until deployed on most SMTP clients.  Many seem to be based on
> insufficient familiarity with the nature of SMTP (e.g. SPF's incredible
> source-routing scheme) and the urge to Do Something Now regardless of
> actual results.

Do you realize how *difficult* it is to create a workable anti-spam scheme that
doesn't run afoul of at least one line item of your "you-might-be" checklist? :)
(Thanks for writing it, BTW - I've decided it's the canonical answer to the
question "Why is stopping spam so hard?")


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

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

iD8DBQFAtgGjcC3lWbTT17ARAsg/AKCpYowui57INvQr00qXisd75IkUwQCfVRAA
3yJRxkKnUzD1GwkDlA0x9iI=
=eCLT
-----END PGP SIGNATURE-----

--==_Exmh_1372374206P--


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

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

--===============1686554745==--



From ietf-bounces@ietf.org  Thu May 27 13:06: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 NAA09311
	for <ietf-archive@ietf.org>; Thu, 27 May 2004 13:06: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 1BTOKX-0006AJ-Gh
	for ietf-archive@ietf.org; Thu, 27 May 2004 13:06:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTOJF-0005mG-00
	for ietf-archive@ietf.org; Thu, 27 May 2004 13:04:51 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BTOGD-0004yA-00; Thu, 27 May 2004 13:01:41 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BTOAL-00053S-T8; Thu, 27 May 2004 12:55:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BTNsU-0008Q0-HH
	for ietf@megatron.ietf.org; Thu, 27 May 2004 12:37: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 MAA06537
	for <ietf@ietf.org>; Thu, 27 May 2004 12:37: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 1BTNsT-00076G-K9
	for ietf@ietf.org; Thu, 27 May 2004 12:37:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTNon-0006F0-00
	for ietf@ietf.org; Thu, 27 May 2004 12:33:22 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx with esmtp (Exim 4.12) id 1BTNfS-0003gM-00
	for ietf@ietf.org; Thu, 27 May 2004 12:23:43 -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 i4RGMw1C000733;
	Thu, 27 May 2004 18:22:59 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <200405271456.i4REuawJ022844@turing-police.cc.vt.edu>
References: <B2403217-AEA1-11D8-A66A-000A95B3BA44@hxr.us>
	<200405262100.i4QL00Ua008101@calcite.rhyolite.com>
	<200405271456.i4REuawJ022844@turing-police.cc.vt.edu>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <294A7108-AFFA-11D8-8E28-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Thu, 27 May 2004 18:23:17 +0200
To: Valdis.Kletnieks@vt.edu
X-Mailer: Apple Mail (2.613)
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: spoofing email addresses 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

On 27-mei-04, at 16:56, Valdis.Kletnieks@vt.edu wrote:

> the proposals aren't even a workable solution to
> the real problem (I've yet to see a proposal that works if the 
> spammers start
> utilizing zombie machines that snarf the already-stored credentials of 
> the user
> to send mail)....

It amazes me how many people are eager to declare defeat on the spam 
problem.

Regardless of anything else, having authenticated mail allows 
whitelisting. If credentials are compromised they're simply removed 
from the whitelist. This should work well for all non-huge whitelists.

There is also the possibility of blacklisting known bad credentials. 
Yes, spammers can steal credentials, but this is several orders of 
magnitude more difficult than just generating a random from address as 
can be done today. The question is whether spammers can obtain new 
credentials (stolen or otherwise) faster than others can blacklist 
them. For user-based credentials this could very well be the case 
(although I'm not conceding to that), but for MTA-based credentials it 
should be possible to rate limit the obtaining of a new identity such 
that spammers can no longer reach critical mass. (I.e., wait a week 
before you can use an MTA with a certain address, then spam an hour 
before you're blacklisted reduces the amount of spam that can be sent 
from an address by a factor 169.)

"The people who claim that something can't be done shouldn't get in the 
way of the people doing it."


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


From ietf-bounces@ietf.org  Thu May 27 13:32:55 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10551
	for <ietf-archive@ietf.org>; Thu, 27 May 2004 13:32:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BTOkR-0005UE-5L
	for ietf-archive@ietf.org; Thu, 27 May 2004 13:32:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTOjK-00056X-00
	for ietf-archive@ietf.org; Thu, 27 May 2004 13:31:47 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BTOiG-0004ba-00; Thu, 27 May 2004 13:30:40 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BTOCn-00071w-Nu; Thu, 27 May 2004 12:58:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BTO6o-0003nQ-3x
	for ietf@megatron.ietf.org; Thu, 27 May 2004 12:51: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 MAA08357
	for <ietf@ietf.org>; Thu, 27 May 2004 12:51:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BTO6n-0002EW-6i
	for ietf@ietf.org; Thu, 27 May 2004 12:51:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTO5d-0001jN-00
	for ietf@ietf.org; Thu, 27 May 2004 12:50:45 -0400
Received: from ns2.system-techniques.com ([192.103.194.6]
	helo=ns2.baby-dragons.com) by ietf-mx with esmtp (Exim 4.12)
	id 1BTO2h-0000pW-00
	for ietf@ietf.org; Thu, 27 May 2004 12:47:43 -0400
Received: from localhost (ns2.baby-dragons.com [192.103.194.6])
	by ns2.baby-dragons.com (8.12.10/8.12.7) with ESMTP id i4RGl4is012744; 
	Thu, 27 May 2004 09:47:04 -0700
Date: Thu, 27 May 2004 10:47:04 -0600 (MDT)
From: "Mr. James W. Laferriere" <babydr@baby-dragons.com>
To: Paul Vixie <vixie@vix.com>
In-Reply-To: <g3ekp626it.fsf@sa.vix.com>
Message-ID: <Pine.LNX.4.58.0405271044030.16548@filesrv1.baby-dragons.com>
References: <B2403217-AEA1-11D8-A66A-000A95B3BA44@hxr.us>
	<g3ekp626it.fsf@sa.vix.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: ietf@ietf.org
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

	Hello Paul ,

On Wed, 26 May 2004, Paul Vixie wrote:
> > > In fact, there isn't any sane way to detect "inconsistent" header
> > > information without external hints - this is the reason why there's the
> > > SPF proposal, the Yahoo domain-keys proposal, and Microsoft's proposal.
> > And MARID.
>
> and don't forget <HREF="http://sa.vix.com/~vixie/mailfrom.txt">MAIL-FROM</A>.
	I do not see a draft in the ietf process anyplace .  Was this
	ever submitted ?  I do notice that several of the other
	proposal's make mention of this work ,  But in none of them do
	they mention it as a draft or other ietf work .  Any plans to
	submit it as a draft .  Tia ,  JimL
-- 
       +------------------------------------------------------------------+
       | James   W.   Laferriere | System    Techniques | Give me VMS     |
       | Network        Engineer | 3542 Broken Yoke Dr. |  Give me Linux  |
       | babydr@baby-dragons.com | Billings , MT. 59105 |   only  on  AXP |
       +------------------------------------------------------------------+

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


From ietf-bounces@ietf.org  Thu May 27 14:01: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 OAA12956
	for <ietf-archive@ietf.org>; Thu, 27 May 2004 14:01: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 1BTPCQ-0005oK-6F
	for ietf-archive@ietf.org; Thu, 27 May 2004 14:01:50 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTPBS-0005Wz-00
	for ietf-archive@ietf.org; Thu, 27 May 2004 14:00:50 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BTPAN-00051k-00; Thu, 27 May 2004 13:59:43 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BTOtW-0000aR-Ci; Thu, 27 May 2004 13:42:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BTOgv-0004lH-Dr
	for ietf@megatron.ietf.org; Thu, 27 May 2004 13:29:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10412
	for <ietf@ietf.org>; Thu, 27 May 2004 13:29:01 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BTOgf-0004Ly-Ax
	for ietf@ietf.org; Thu, 27 May 2004 13:29:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTOfh-00046z-00
	for ietf@ietf.org; Thu, 27 May 2004 13:28:01 -0400
Received: from turing-police.cc.vt.edu ([128.173.14.107] ident=root)
	by ietf-mx with esmtp (Exim 4.12) id 1BTOf8-0003rj-00
	for ietf@ietf.org; Thu, 27 May 2004 13:27:26 -0400
Received: from turing-police.cc.vt.edu (IDENT:valdis@localhost [127.0.0.1])
	by turing-police.cc.vt.edu (8.13.0.Beta2/8.13.0.Beta2) with ESMTP id
	i4RHRJNM021294; Thu, 27 May 2004 13:27:19 -0400
Message-Id: <200405271727.i4RHRJNM021294@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4+dev
To: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: Your message of "Thu, 27 May 2004 18:23:17 +0200."
	<294A7108-AFFA-11D8-8E28-000A95CD987A@muada.com> 
References: <B2403217-AEA1-11D8-A66A-000A95B3BA44@hxr.us>
	<200405262100.i4QL00Ua008101@calcite.rhyolite.com>
	<200405271456.i4REuawJ022844@turing-police.cc.vt.edu>
	<294A7108-AFFA-11D8-8E28-000A95CD987A@muada.com>
Mime-Version: 1.0
Date: Thu, 27 May 2004 13:27:19 -0400
Cc: ietf@ietf.org
Subject: Re: spoofing email addresses 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1445217898=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60

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

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

On Thu, 27 May 2004 18:23:17 +0200, Iljitsch van Beijnum said:
> There is also the possibility of blacklisting known bad credentials.

Anybody who's had to get themselves out of 3,000 private blacklists, and
anybody who's had to fight with places that were blackholing the 69/8 address
space, knows that private blacklists are a bad idea.

And nobody seems to want to trust anybody to run a public blacklist to
everybody's satisfaction.  Consider that we as an industry haven't even figured
out how to pick an organization to supervise the DNS to everybody's
satisfaction.  Think about ICANN and "how many TLD's should there be?" and
Verisign's "Site Finder".  Add in Matt Blaze's adage about "A CA can protect
you from anybody they're not accepting money from", and the various
jurisdictional issues.  Then ask yourself if we're in any position to let
*anybody* decide "You can't send/receive email".

(Notice, I haven't said it's impossible - I said that we as a community don't
know how to do it.  There's a big and very important distinction there...)

> Yes, spammers can steal credentials, but this is several orders of 
> magnitude more difficult than just generating a random from address as 
> can be done today. The question is whether spammers can obtain new 
> credentials (stolen or otherwise) faster than others can blacklist 
> them. For user-based credentials this could very well be the case 
> (although I'm not conceding to that), but for MTA-based credentials it
> should be possible to rate limit the obtaining of a new identity such 
> that spammers can no longer reach critical mass. (I.e., wait a week 
> before you can use an MTA with a certain address, then spam an hour 
> before you're blacklisted reduces the amount of spam that can be sent 
> from an address by a factor 169.)

There's two problems with this:

1) Waiting a week probably isn't a sellable to the user community.  If you
don't believe me, consider how fast people bailed their domain registrations
away from a registrar that had a reputation of taking a week to do anything,
and going to registrars that promised setup times measured in hours.

2) The assumption that you can catch, verify, and deploy a blacklist for a
spammer in an hour is highly suspect, for several reasons:

(a) it means that the *effective* TTL of a DNS MX entry is much lower than an
hour (as everybody will have to re-fetch at least 2-3 times an hour to verify
they're not blacklisted - a once-an-hour update means that on the *average*
there will be a 30 minute delay, and up to 59 minutes at worst case).  Notice
how few software products that use X.509 certs actually implement CRL's
*correctly*...

(b) "Under an hour" deployment almost certainly implies an automated process to
blacklist..  That has "denial of service" written all over it....

Again, I haven't said it's *impossible* - merely that we've not seen a concrete
proposal that actually has the right scaling and uptake characteristics...

> "The people who claim that something can't be done shouldn't get in the 
> way of the people doing it."

I didn't say it *cant* be done.  I said there were known problems that any
successful solution would have to address.

Solving the spam problem is like solving global warming - neither is a problem
that demonstrably *cant* be done, but both are problems that we don't know how
to solve and which don't have anybody actively solving the problem in a production
mode (the fact that both are still perceived as a problem is proof that neither is
actually being solved).


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

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

iD8DBQFAtiT2cC3lWbTT17ARAvjPAJ0cdN9MheJf3yF0bPfhBfPMvRMWbQCg2/rQ
d6pd02qy+6hSRrEBVJAAoLo=
=tcsZ
-----END PGP SIGNATURE-----

--==_Exmh_1841505932P--


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

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

--===============1445217898==--



From ietf-bounces@ietf.org  Thu May 27 15:19: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 PAA18439
	for <ietf-archive@ietf.org>; Thu, 27 May 2004 15:19: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 1BTQPQ-000391-Vp
	for ietf-archive@ietf.org; Thu, 27 May 2004 15:19:20 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTQOH-0002rO-00
	for ietf-archive@ietf.org; Thu, 27 May 2004 15:18:10 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BTQNk-0002aI-00; Thu, 27 May 2004 15:17:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BTQB1-0002Op-Ja; Thu, 27 May 2004 15:04:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BTQ1A-0003ji-Oo
	for ietf@megatron.ietf.org; Thu, 27 May 2004 14:54:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15982
	for <ietf@ietf.org>; Thu, 27 May 2004 14:54: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 1BTQ19-0004Eu-K4
	for ietf@ietf.org; Thu, 27 May 2004 14:54:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTQ0R-0003xT-00
	for ietf@ietf.org; Thu, 27 May 2004 14:53:32 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12) id 1BTPzH-0003Y4-00
	for ietf@ietf.org; Thu, 27 May 2004 14:52:20 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.11/8.12.11) id i4RIpnuV070162
	for ietf@ietf.org env-from <vjs>;
	Thu, 27 May 2004 12:51:49 -0600 (MDT)
Date: Thu, 27 May 2004 12:51:49 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200405271851.i4RIpnuV070162@calcite.rhyolite.com>
To: ietf@ietf.org
References: <200405271727.i4RHRJNM021294@turing-police.cc.vt.edu>
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

> From: Valdis.Kletnieks@vt.edu

> > "The people who claim that something can't be done shouldn't get in the 
> > way of the people doing it."
>
> I didn't say it *cant* be done.  I said there were known problems that any
> successful solution would have to address.

Another response is to point out that all of the sender validating
systems are today only proposals that can be seen as getting in the
way of effective tactics.  The talkers trying to get in the way of the
doers are, as usual, those who endless prescribe spam solutions that
they themselves have not thought out, not to mention documented, tested,
or deployed.

The vast majority of the spam that sender validating systems might
block after they have been installed in most SMTP clients 5 or 10 years
from now is rejected today at any organization that really cares about
spam using any of various tactics including DNS blacklists (e.g. the
CBL or the so called "dynamic IP" lists) and greylisting.
Essentially all of the spam that any sender validating system might
someday block after large outfits like Comcast have installed validating
code on their SMTP clients and servers would be blocked today at the
source if those same outfits would block port 25 for all types of IP
service except the one that draft-klensin-ip-service-terms-01.txt calls
"Full Internet Connectivity."  That is because current spam that
would be blocked by sender validating comes "trojan proxies."

The current state of the art in spam defenses reject more than 99%
of spam with less than 1% false positives (or variations of those
numbers such as 95% and 0.1%).  No one who is actually do anything
about spam is content with those numbers or confident that new
tactics will not be needed, but please don't tell the experts who
don't know the difference betwee an SMTP rejection and a bounce, lest
they be encouraged to tell us some more what we really should be doing.

As usual, the usual suspects who might someday get around to reading
an RFC, any RFC, tell us that The Final Ultimate Solution to the Spam
Problem is just around the corner.  Their Finual Ultimate Solution is
waiting for the obstructionists to get out of the way of those who
will realsoonnow write the FUSSP RFC.  Of course, the usual suspects
can't be bothered to come down from Mt. Olympus to write a I-D or
learn the relationship between I-Ds and RFCs.  They don't care about
the differences among documenting, testing, or deploying, or the chasm
between practice and sidewalk superintendent theory.


Probably the best response is to send people to the MADID mailing list.
I've often said that the IETF is well served by working groups that do
no more than absorb the energies of standards committee goers.


Vernon Schryver    vjs@rhyolite.com

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


From ietf-bounces@ietf.org  Thu May 27 17:30: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 RAA27474
	for <ietf-archive@ietf.org>; Thu, 27 May 2004 17:30: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 1BTSRt-0001jW-9A
	for ietf-archive@ietf.org; Thu, 27 May 2004 17:30:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTSQu-0001Qf-00
	for ietf-archive@ietf.org; Thu, 27 May 2004 17:29:00 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BTSPr-00015E-00; Thu, 27 May 2004 17:27:55 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BTSPp-0003EF-US; Thu, 27 May 2004 17:27:56 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BTSDo-0001cI-JA; Thu, 27 May 2004 17:15:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BTRz4-0005Z9-1n
	for ietf@megatron.ietf.org; Thu, 27 May 2004 17:00:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24660
	for <ietf@ietf.org>; Thu, 27 May 2004 16:59: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 1BTRyn-0001AV-H7
	for ietf@ietf.org; Thu, 27 May 2004 16:59:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTRxo-0000u8-00
	for ietf@ietf.org; Thu, 27 May 2004 16:58:56 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx with esmtp (Exim 4.12) id 1BTRwk-0000RL-00
	for ietf@ietf.org; Thu, 27 May 2004 16:57:50 -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 i4RKvE1C005647;
	Thu, 27 May 2004 22:57:17 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <200405271851.i4RIpnuV070162@calcite.rhyolite.com>
References: <200405271727.i4RHRJNM021294@turing-police.cc.vt.edu>
	<200405271851.i4RIpnuV070162@calcite.rhyolite.com>
Mime-Version: 1.0 (Apple Message framework v618)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <7A5A1396-B020-11D8-B41C-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Thu, 27 May 2004 22:57:34 +0200
To: Vernon Schryver <vjs@calcite.rhyolite.com>
X-Mailer: Apple Mail (2.618)
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

On 27-mei-04, at 20:51, Vernon Schryver wrote:

> The vast majority of the spam that sender validating systems might
> block after they have been installed in most SMTP clients 5 or 10 years
> from now is rejected today at any organization that really cares about
> spam using any of various tactics including DNS blacklists (e.g. the
> CBL or the so called "dynamic IP" lists) and greylisting.

I'd say "back this up" but then we're once again having one of these 
unproductive spam discussions. Why don't we all do this on our personal 
favorite anti-spam list and revist the issue here only when there is a 
pertinent draft in last call?

One last remark:

> block port 25

This is evil for several reasons:

1. blocking ports reduces the functionality of the internet
2. doing work per-packet rather than per-session is inefficient 
(especially considering that only a small fraction of all packets is 
email to begin with)
3. requiring others to clean up their act rather than do something 
yourself is ineffective


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


From ietf-bounces@ietf.org  Fri May 28 03:27: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 DAA09510
	for <ietf-archive@ietf.org>; Fri, 28 May 2004 03:27: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 1BTbm4-0005Up-LH
	for ietf-archive@ietf.org; Fri, 28 May 2004 03:27:28 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTbl3-000571-00
	for ietf-archive@ietf.org; Fri, 28 May 2004 03:26:26 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BTbjz-0004Ry-00; Fri, 28 May 2004 03:25:19 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BTbZw-0007sM-AI; Fri, 28 May 2004 03:14:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BTbSv-0006UX-JB
	for ietf@megatron.ietf.org; Fri, 28 May 2004 03:07: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 DAA08623
	for <ietf@ietf.org>; Fri, 28 May 2004 03:07: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 1BTbSt-0006Pc-1W
	for ietf@ietf.org; Fri, 28 May 2004 03:07:39 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTbRy-00064z-00
	for ietf@ietf.org; Fri, 28 May 2004 03:06:42 -0400
Received: from mail.consulintel.es ([213.172.48.142] helo=consulintel.es)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BTbRK-0005dt-00; Fri, 28 May 2004 03:06:02 -0400
Received: from consulintel02 by consulintel.es (MDaemon.PRO.v7.1.0.R)
	with ESMTP id md50000127753.msg; Fri, 28 May 2004 09:06:46 +0200
Message-ID: <60ef01c44482$0e5efd40$8700000a@consulintel.es>
From: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
To: <ietf@ietf.org>, <v6ops@ops.ietf.org>, <ipv6@rediris.es>, <ipv6@ietf.org>
Date: Fri, 28 May 2004 09:04:43 +0200
Organization: Consulintel
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Spam-Processed: consulintel.es, Fri, 28 May 2004 09:06:46 +0200
	(not processed: message from valid local sender)
X-MDRemoteIP: 217.126.187.160
X-Return-Path: jordi.palet@consulintel.es
X-MDAV-Processed: consulintel.es, Fri, 28 May 2004 09:06:46 +0200
Content-Transfer-Encoding: quoted-printable
Subject: ICANN Board to implement IPv6 in root servers
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable


http://www.ist-ipv6.org/modules.php?op=3Dmodload&name=3DNews&file=3Darticle&sid=3D567





**********************************
Madrid 2003 Global IPv6 Summit
Presentations and videos on line at:
http://www.ipv6-es.com

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.




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


From ietf-bounces@ietf.org  Fri May 28 09:03: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 JAA28124
	for <ietf-archive@ietf.org>; Fri, 28 May 2004 09:03: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 1BTh0x-0005UP-V9
	for ietf-archive@ietf.org; Fri, 28 May 2004 09:03:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTgzO-0004z8-00
	for ietf-archive@ietf.org; Fri, 28 May 2004 09:01:35 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BTgwh-000418-00; Fri, 28 May 2004 08:58:47 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BTgwh-0000dw-9o; Fri, 28 May 2004 08:58:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BTgL9-0004cf-46; Fri, 28 May 2004 08:19:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BTRO8-0003aM-AX
	for ietf@megatron.ietf.org; Thu, 27 May 2004 16:22: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 QAA22086
	for <ietf@ietf.org>; Thu, 27 May 2004 16:22: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 1BTRO5-0005RY-MS
	for ietf@ietf.org; Thu, 27 May 2004 16:22:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTRN1-000581-00
	for ietf@ietf.org; Thu, 27 May 2004 16:20:56 -0400
Received: from firewall.seawaynetworks.com ([216.209.86.50]
	helo=apollo.seawaynetworks.com) by ietf-mx with esmtp (Exim 4.12)
	id 1BTRLx-0004WM-00
	for ietf@ietf.org; Thu, 27 May 2004 16:19:49 -0400
Received: from camelot-054 (camelot-054 [10.10.1.54])
	by apollo.seawaynetworks.com (8.12.8/8.12.8) with ESMTP id
	i4RKJGcP000678
	for <ietf@ietf.org>; Thu, 27 May 2004 16:19:17 -0400 (EDT)
To: ietf@ietf.org
X-Mailer: X-Emacs with mh, mh-e and other stuff
Date: Thu, 27 May 2004 16:19:15 -0400
Message-ID: <2015.1085689155@camelot-054>
From: Michael Richardson <Michael.Richardson@seawaynetworks.com>
X-Mailman-Approved-At: Fri, 28 May 2004 08:19:57 -0400
Subject: STD series of documents
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=UPPERCASE_25_50 autolearn=no 
	version=2.60

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


May I suggest that a URL like:

    http://www.ietf.org/std/std0051.txt

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

- --
]       ON HUMILITY: to err is human. To moo, bovine.                         [
]   Michael Richardson,            Seaway Networks Corporation                [
]   michael@seawaynetworks.com     http://www.seawaynetworks.com/             [
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Finger me for keys

iD8DBQFAtk0i22r3dfT9QZERAiWLAJ9O9dRISdt7fagCGJyfAS7hdUSrZACfWRWW
6LKcWWq7HHXPFDZp7w0xHmk=
=iDjo
-----END PGP SIGNATURE-----

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


From ietf-bounces@ietf.org  Fri May 28 09:04: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 JAA28304
	for <ietf-archive@ietf.org>; Fri, 28 May 2004 09:04: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 1BTh2Q-00063U-BU
	for ietf-archive@ietf.org; Fri, 28 May 2004 09:04:42 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTh15-0005VR-00
	for ietf-archive@ietf.org; Fri, 28 May 2004 09:03:19 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BTgzZ-000519-00; Fri, 28 May 2004 09:01:45 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BTgzX-0000wB-SQ; Fri, 28 May 2004 09:01:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BTgLA-0004cm-6K; Fri, 28 May 2004 08:20:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BTSJ7-0003Hb-FO
	for ietf@megatron.ietf.org; Thu, 27 May 2004 17:20: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 RAA26675
	for <ietf@ietf.org>; Thu, 27 May 2004 17:20: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 1BTSJ5-0006mP-HR
	for ietf@ietf.org; Thu, 27 May 2004 17:20:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTSH2-0005zy-00
	for ietf@ietf.org; Thu, 27 May 2004 17:18:48 -0400
Received: from sa.vix.com ([204.152.187.1]) by ietf-mx with esmtp (Exim 4.12)
	id 1BTSG4-0005as-00
	for ietf@ietf.org; Thu, 27 May 2004 17:17:49 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id B6D1D13951
	for <ietf@ietf.org>; Thu, 27 May 2004 21:17:14 +0000 (GMT)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: ietf@ietf.org
In-Reply-To: Message from "Mr. James W. Laferriere" <babydr@baby-dragons.com> 
	of "Thu, 27 May 2004 10:47:04 CST."
	<Pine.LNX.4.58.0405271044030.16548@filesrv1.baby-dragons.com> 
X-Mailer: MH-E 7.4; nmh 1.0.4; GNU Emacs 21.3.1
Date: Thu, 27 May 2004 21:17:14 +0000
Message-Id: <20040527211714.B6D1D13951@sa.vix.com>
X-Mailman-Approved-At: Fri, 28 May 2004 08:19:57 -0400
Subject: Re: spoofing email addresses 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

> > ... <HREF="http://sa.vix.com/~vixie/mailfrom.txt">MAIL-FROM</A>.
> 
> 	I do not see a draft in the ietf process anyplace .  Was this
> 	ever submitted ?  I do notice that several of the other
> 	proposal's make mention of this work ,  But in none of them do
> 	they mention it as a draft or other ietf work .  

there was no working group where it was appropriate at the time it was
written.  i've sent it to every one of the dozen people who have asked
me to review some similar, and usually ill considered thing.  i've also
sent it to several spam-related and dns-related mailing lists, including
this one (ietf@).

>       Any plans to submit it as a draft .  Tia ,  JimL

MARID is basically a layer 9 exercise, uninterested in engineering as
such.  it was formed to merge two ill considered ideas, one from yahoo
and one from microsoft, in a way that would cause either no loss of face,
or equal loss of face, for those two parties.  the people who submit
their own ideas to it are wasting their time.

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


From ietf-bounces@ietf.org  Fri May 28 09:22:31 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29319
	for <ietf-archive@ietf.org>; Fri, 28 May 2004 09:22: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 1BThJg-0005Li-KX
	for ietf-archive@ietf.org; Fri, 28 May 2004 09:22:32 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BThIQ-0004uw-00
	for ietf-archive@ietf.org; Fri, 28 May 2004 09:21:15 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BThGz-0004NE-00; Fri, 28 May 2004 09:19:45 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BTh1E-00015j-2c; Fri, 28 May 2004 09:03:28 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BTgLB-0004cx-7Q; Fri, 28 May 2004 08:20:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BTfoT-0006i6-43
	for ietf@megatron.ietf.org; Fri, 28 May 2004 07:46:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22256
	for <ietf@ietf.org>; Fri, 28 May 2004 07:46: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 1BTfoR-0005kv-Rs
	for ietf@ietf.org; Fri, 28 May 2004 07:46:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTfnZ-0005Lo-00
	for ietf@ietf.org; Fri, 28 May 2004 07:45:17 -0400
Received: from vacation.karoshi.com ([198.32.6.68] helo=karoshi.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BTfml-0004w1-00; Fri, 28 May 2004 07:44:27 -0400
Received: from karoshi.com (localhost.localdomain [127.0.0.1])
	by karoshi.com (8.12.8/8.12.8) with ESMTP id i4SBiLW4013588;
	Fri, 28 May 2004 11:44:21 GMT
Received: (from bmanning@localhost)
	by karoshi.com (8.12.8/8.12.8/Submit) id i4SBiK35013585;
	Fri, 28 May 2004 11:44:20 GMT
Date: Fri, 28 May 2004 11:44:20 +0000
From: bmanning@vacation.karoshi.com
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Message-ID: <20040528114420.GB13184@vacation.karoshi.com.>
References: <60ef01c44482$0e5efd40$8700000a@consulintel.es>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <60ef01c44482$0e5efd40$8700000a@consulintel.es>
User-Agent: Mutt/1.4.1i
X-Mailman-Approved-At: Fri, 28 May 2004 08:19:57 -0400
Cc: v6ops@ops.ietf.org, ipv6@ietf.org, ipv6@rediris.es, ietf@ietf.org
Subject: Re: ICANN Board to implement IPv6 in root servers
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=NO_REAL_NAME autolearn=no 
	version=2.60


	The headline is misleading. The recommendation is to support
	IPv6 registration of TLD servers in the root zone. The root
	servers themselves still need some testing before registration
	of their IPv6 capabilities.

--bill manning

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


From ietf-bounces@ietf.org  Fri May 28 09:52: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 JAA01020
	for <ietf-archive@ietf.org>; Fri, 28 May 2004 09:52: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 1BThmI-0001oS-Rk
	for ietf-archive@ietf.org; Fri, 28 May 2004 09:52:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BThlJ-0001Nx-00
	for ietf-archive@ietf.org; Fri, 28 May 2004 09:51:06 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BThkR-0000sY-00; Fri, 28 May 2004 09:50:13 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BThWA-0006pA-Nz; Fri, 28 May 2004 09:35:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BThBX-00016k-OU
	for ietf@megatron.ietf.org; Fri, 28 May 2004 09:14:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28892
	for <ietf@ietf.org>; Fri, 28 May 2004 09:13:50 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BThBH-0002B2-Vm
	for ietf@ietf.org; Fri, 28 May 2004 09:13:52 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BThAP-0001mU-00
	for ietf@ietf.org; Fri, 28 May 2004 09:12:58 -0400
Received: from carwash.centive.com ([65.220.90.249])
	by ietf-mx with smtp (Exim 4.12) id 1BTh9I-00011U-00
	for ietf@ietf.org; Fri, 28 May 2004 09:11:48 -0400
Received: from minglewood.incentivesystems.com ([10.10.30.25])
	by carwash.centive.com (SAVSMTP 3.1.3.37) with SMTP id
	M2004052809130312600
	for <ietf@ietf.org>; Fri, 28 May 2004 09:13:03 -0400
Received: from [10.10.48.119] ([10.10.48.119]) by
	minglewood.incentivesystems.com with Microsoft SMTPSVC(6.0.3790.0); 
	Fri, 28 May 2004 09:06:50 -0400
Message-ID: <40B7396A.2090309@centive.com>
Date: Fri, 28 May 2004 09:06:50 -0400
From: John Stracke <jstracke@centive.com>
User-Agent: Mozilla Thunderbird 0.6 (Windows/20040502)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
References: <B2403217-AEA1-11D8-A66A-000A95B3BA44@hxr.us>	<200405262100.i4QL00Ua008101@calcite.rhyolite.com>	<200405271456.i4REuawJ022844@turing-police.cc.vt.edu>
	<294A7108-AFFA-11D8-8E28-000A95CD987A@muada.com>
In-Reply-To: <294A7108-AFFA-11D8-8E28-000A95CD987A@muada.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 28 May 2004 13:06:50.0319 (UTC)
	FILETIME=[A39FFDF0:01C444B4]
Content-Transfer-Encoding: 7bit
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Iljitsch van Beijnum wrote:

> On 27-mei-04, at 16:56, Valdis.Kletnieks@vt.edu wrote:
>
>> (I've yet to see a proposal that works if the spammers start
>> utilizing zombie machines that snarf the already-stored credentials 
>> of the user
>> to send mail)....
>
> The question is whether spammers can obtain new credentials (stolen or 
> otherwise) faster than others can blacklist them.

And, if you had actually read the message you replied to, you would have 
realized that the answer is yes.  Send out a worm that makes N zombies, 
have each zombie send one message under the local user's credentials, 
and none of them will get blacklisted.

-- 
/===============================================================\
|John Stracke      |jstracke@centive.com                        |
|Principal Engineer|http://www.centive.com                      |
|Centive           |My opinions are my own.                     |
|===============================================================|
|The light at the end of the tunnel is a terawatt laser cannon. |
\===============================================================/


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


From ietf-bounces@ietf.org  Fri May 28 10:04: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 KAA02186
	for <ietf-archive@ietf.org>; Fri, 28 May 2004 10:04: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 1BThyg-0007MS-Sv
	for ietf-archive@ietf.org; Fri, 28 May 2004 10:04:54 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BThxO-0006Ws-00
	for ietf-archive@ietf.org; Fri, 28 May 2004 10:03:35 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BThw5-0005re-00; Fri, 28 May 2004 10:02:13 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BThch-0000Av-LY; Fri, 28 May 2004 09:42:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BThPw-0004ol-Fh
	for ietf@megatron.ietf.org; Fri, 28 May 2004 09:29: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 JAA29712
	for <ietf@ietf.org>; Fri, 28 May 2004 09:28:43 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BThPg-0000QZ-L4
	for ietf@ietf.org; Fri, 28 May 2004 09:28:44 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BThOa-0007az-00
	for ietf@ietf.org; Fri, 28 May 2004 09:27:37 -0400
Received: from [162.33.195.162] (helo=wsmalky.com)
	by ietf-mx with smtp (Exim 4.12) id 1BThNN-00070u-00
	for ietf@ietf.org; Fri, 28 May 2004 09:26:21 -0400
Date: Fri, 28 May 2004 09:27:03 -0500
To: "Ietf" <ietf@ietf.org>
From: "Cook" <cook@COOKREPORT.COM>
Message-ID: <roafudublifpbhzanbc@ietf.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="--------svrztbkylytchcyngbza"
Subject: Re: Msg reply
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,HTML_MESSAGE autolearn=no 
	version=2.60

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

<html><body>
 

<br>
</body></html>

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



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

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

----------svrztbkylytchcyngbza--




From ietf-bounces@ietf.org  Fri May 28 11:21:55 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09131
	for <ietf-archive@ietf.org>; Fri, 28 May 2004 11:21:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BTjBG-0000Hs-08
	for ietf-archive@ietf.org; Fri, 28 May 2004 11:21:58 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTj8X-00074n-00
	for ietf-archive@ietf.org; Fri, 28 May 2004 11:19:10 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BTj6T-0005ta-00; Fri, 28 May 2004 11:17:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BTig1-0005R4-Tw; Fri, 28 May 2004 10:49:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BTiKH-0000bY-2W
	for ietf@megatron.ietf.org; Fri, 28 May 2004 10:27:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05682
	for <ietf@ietf.org>; Fri, 28 May 2004 10:27: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 1BTiKG-0001W2-9f
	for ietf@ietf.org; Fri, 28 May 2004 10:27:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTiJR-00015I-00
	for ietf@ietf.org; Fri, 28 May 2004 10:26:22 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12) id 1BTiIJ-0000Hy-00
	for ietf@ietf.org; Fri, 28 May 2004 10:25:11 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.11/8.12.11) id i4SEOeR3003213
	for ietf@ietf.org env-from <vjs>;
	Fri, 28 May 2004 08:24:40 -0600 (MDT)
Date: Fri, 28 May 2004 08:24:40 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200405281424.i4SEOeR3003213@calcite.rhyolite.com>
To: ietf@ietf.org
References: <40B7396A.2090309@centive.com>
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

> From: John Stracke <jstracke@centive.com>

> >> (I've yet to see a proposal that works if the spammers start
> >> utilizing zombie machines that snarf the already-stored credentials 
> >> of the user
> >> to send mail)....
> >
> > The question is whether spammers can obtain new credentials (stolen or 
> > otherwise) faster than others can blacklist them.
>
> And, if you had actually read the message you replied to, you would have 
> realized that the answer is yes.  Send out a worm that makes N zombies, 
> have each zombie send one message under the local user's credentials, 
> and none of them will get blacklisted.

Here's a defense for that scenario:

  1. block port 25 to external IP addresses for all of your customers
    except those with what draft-klensin-ip-service-terms-01.txt calls
    Full Internet Connectivity.

  2. Do not sell Full Internet Connectivity to anyone running Microsoft
    software exposed to the Internet.  Possibly relax this with a $2000
    bond forfeited along with connectivity at the first propagation
    of a worm or other spam.

  3. The effects of #1 and #2 include forcing all mail from the usual
    suspects through your own mail systems so that you can do as the
    credit card companies do.  Track SMTP envelope Mail_To values or
    other characteristics for each customer.  When you see a change,
    contact the customer by voice to check.

In practice, you could probably get by with detecting changes in mail
volumes, since a spam spew of 1 message/zombie is at least 10 and
probably 1000 times too low to be practical for high volume spammers.
As far as I can tell, the typical user sends only about a dozen
messages/day.

Of course, the fatal problem with this spam defense is that it is not
based on other people doing the work and paying the costs.  It is not
a coincidence that as far as I can tell Yahoo continues to be the most
important U.S. host for Nigerian 419 spammers or that Windows XP
practically requires or at least strongly encourages individual users
to run their browsers and MUAs as "administrator."  It is not a
coincidence that sender validating systems including those Yahoo and
Microsoft are based on the rest of the Internet doing most of the work.

The howls from the Special People who feel that they are entitled  to
Full Internet Connectivity at prices and terms they find comfortable
(and about the per capita income in large parts of the world) are also
related to the fundamental cause of all spam.  There would be no spam
problem including worms if every ISP would look after its own problems
by terminating all spammers including customers who let their machines
be "owned" or if all users were willing to pull their own weight instead
of expecting something for nothing.


Vernon Schryver    vjs@rhyolite.com

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


From ietf-bounces@ietf.org  Fri May 28 12: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 MAA15011
	for <ietf-archive@ietf.org>; Fri, 28 May 2004 12: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 1BTkOz-0001E4-RV
	for ietf-archive@ietf.org; Fri, 28 May 2004 12:40:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTkNz-0000mP-00
	for ietf-archive@ietf.org; Fri, 28 May 2004 12:39:12 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BTkNU-0000Kv-00; Fri, 28 May 2004 12:38:40 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BTkGj-0004c0-Q2; Fri, 28 May 2004 12:31:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BTjpM-0005vg-3c
	for ietf@megatron.ietf.org; Fri, 28 May 2004 12:03: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 MAA12215
	for <ietf@ietf.org>; Fri, 28 May 2004 12:03: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 1BTjpL-0001rq-1k
	for ietf@ietf.org; Fri, 28 May 2004 12:03:23 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTjnJ-0001DA-00
	for ietf@ietf.org; Fri, 28 May 2004 12:01:18 -0400
Received: from above.proper.com ([208.184.76.39])
	by ietf-mx with esmtp (Exim 4.12) id 1BTjmM-0000md-00
	for ietf@ietf.org; Fri, 28 May 2004 12:00:18 -0400
Received: from [10.20.30.249] (dsl2-63-249-109-252.cruzio.com [63.249.109.252])
	(authenticated bits=0)
	by above.proper.com (8.12.11/8.12.9) with ESMTP id i4SG0Een021065
	for <ietf@ietf.org>; Fri, 28 May 2004 09:00:14 -0700 (PDT)
	(envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
X-Sender: phoffvpnc@mail.vpnc.org
Message-Id: <p06100516bcdd11fdf9c5@[10.20.30.249]>
Date: Fri, 28 May 2004 09:00:15 -0700
To: ietf@ietf.org
From: Paul Hoffman / VPNC <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Subject: Summary of the ad-hoc WiFi problems at IETF meetings?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60

Greetings again. I was at a conference this week that offered WiFi. 
They had the same problems we had at the past two IETFs with a few 
folks doing ad-hoc mode, thereby knocking out access for many of us. 
Was there any writeup from the IETF NOC teams about the problem and 
how we fixed it? If so, it would be great to make that information 
available to the wider world.

Please send responses to me, and I'll summarize them to the list.

--Paul Hoffman, Director
--VPN Consortium

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


From ietf-bounces@ietf.org  Fri May 28 12:56: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 MAA15785
	for <ietf-archive@ietf.org>; Fri, 28 May 2004 12:56: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 1BTkeM-0000FF-9y
	for ietf-archive@ietf.org; Fri, 28 May 2004 12:56:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTkdQ-0007c4-00
	for ietf-archive@ietf.org; Fri, 28 May 2004 12:55:08 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BTkcy-0007C9-00; Fri, 28 May 2004 12:54:40 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BTkIB-0005ks-Kx; Fri, 28 May 2004 12:33:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BTjtO-0007al-D8
	for ietf@megatron.ietf.org; Fri, 28 May 2004 12:07: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 MAA12474
	for <ietf@ietf.org>; Fri, 28 May 2004 12: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 1BTjtN-0002yV-7q
	for ietf@ietf.org; Fri, 28 May 2004 12:07:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTjq4-00029h-00
	for ietf@ietf.org; Fri, 28 May 2004 12:04:09 -0400
Received: from sokol.elan.net ([216.151.192.200])
	by ietf-mx with esmtp (Exim 4.12) id 1BTjng-0001Fc-00
	for ietf@ietf.org; Fri, 28 May 2004 12:01:40 -0400
Received: from sokol.elan.net (localhost.localdomain [127.0.0.1])
	by sokol.elan.net (8.12.11/8.12.5) with ESMTP id i4S2uuS5029591;
	Thu, 27 May 2004 19:56:56 -0700
Received: from localhost (william@localhost)
	by sokol.elan.net (8.12.11/8.12.5/Submit) with ESMTP id i4S2uu4N029588; 
	Thu, 27 May 2004 19:56:56 -0700
X-Authentication-Warning: sokol.elan.net: william owned process doing -bs
Date: Thu, 27 May 2004 19:56:56 -0700 (PDT)
From: "william(at)elan.net" <william@elan.net>
To: Paul Vixie <paul@vix.com>
In-Reply-To: <20040527211714.B6D1D13951@sa.vix.com>
Message-ID: <Pine.LNX.4.44.0405271939430.21375-100000@sokol.elan.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: ietf@ietf.org
Subject: Re: spoofing email addresses 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60


Paul,

  MARID was formed to merge Microsoft Caller-ID with SPF and so far has
been successfully used by Microsoft to bully us to submit to their own
proposal or else ... There are better ways to implement mail-from (i.e.
as from Paul's draft which is basicly still the basis for MARID) which 
would not require reusing TXT records, nor is it totally clear that
Mail-from is what we actually need to protect, it is being done under 
pretese of anti-spam measures but the reality shows that it will most 
likely have minimum effect as its far too easy for spammers to adapt to
it anyway. There are however good reasons to have MARID as IETF WG anyway
and hopefully the worst ideas implementation details can be stopped and 
new ideas discussed in the future if the group is extended.
  Yahoo is different proposal which has nothing to do with MARID and is
being discussed at the ASRG. It is basicly a header containing a signature
added to mail message that signs the content (including headers) with 
public key encryption and with public key available in DNS to verify the 
signature at the other end. The idea is not new and its a good idea, but 
yahoo's implementation is just bad and I think it breaks far too many 
things (it breaks with almost all maillists) and offers security that is 
too weak because its based on 348-bit key size. It should have been done 
different by reusing most likely PGP implementation but with message 
signed by MTAs and public key available through dns and if necessary 
being split into multiple dns records to have each at < 512k.

On Thu, 27 May 2004, Paul Vixie wrote:

> > > ... <HREF="http://sa.vix.com/~vixie/mailfrom.txt">MAIL-FROM</A>.
> > 
> > 	I do not see a draft in the ietf process anyplace .  Was this
> > 	ever submitted ?  I do notice that several of the other
> > 	proposal's make mention of this work ,  But in none of them do
> > 	they mention it as a draft or other ietf work .  
> 
> there was no working group where it was appropriate at the time it was
> written.  i've sent it to every one of the dozen people who have asked
> me to review some similar, and usually ill considered thing.  i've also
> sent it to several spam-related and dns-related mailing lists, including
> this one (ietf@).
> 
> >       Any plans to submit it as a draft .  Tia ,  JimL
> 
> MARID is basically a layer 9 exercise, uninterested in engineering as
> such.  it was formed to merge two ill considered ideas, one from yahoo
> and one from microsoft, in a way that would cause either no loss of face,
> or equal loss of face, for those two parties.  the people who submit
> their own ideas to it are wasting their time.
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf


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


From ietf-bounces@ietf.org  Fri May 28 13:14: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 NAA16892
	for <ietf-archive@ietf.org>; Fri, 28 May 2004 13:14: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 1BTkvm-0000U0-7Z
	for ietf-archive@ietf.org; Fri, 28 May 2004 13:14:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTkuz-00003t-00
	for ietf-archive@ietf.org; Fri, 28 May 2004 13:13:18 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BTku9-0007Ol-00; Fri, 28 May 2004 13:12:25 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BTkK3-0006ui-Iz; Fri, 28 May 2004 12:35:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BTk3v-0001t2-8A
	for ietf@megatron.ietf.org; Fri, 28 May 2004 12:18: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 MAA13786
	for <ietf@ietf.org>; Fri, 28 May 2004 12:18: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 1BTk3s-0007H1-Ua
	for ietf@ietf.org; Fri, 28 May 2004 12:18:25 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTk2z-0006oh-00
	for ietf@ietf.org; Fri, 28 May 2004 12:17:30 -0400
Received: from mail3.microsoft.com ([131.107.3.123])
	by ietf-mx with esmtp (Exim 4.12) id 1BTk1k-0005sW-00
	for ietf@ietf.org; Fri, 28 May 2004 12:16:13 -0400
Received: from INET-VRS-03.redmond.corp.microsoft.com ([157.54.5.27]) by
	mail3.microsoft.com with Microsoft SMTPSVC(6.0.3790.0); 
	Fri, 28 May 2004 09:15:40 -0700
Received: from 157.54.5.25 by INET-VRS-03.redmond.corp.microsoft.com
	(InterScan E-Mail VirusWall NT); Fri, 28 May 2004 09:15:41 -0700
Received: from RED-IMC-04.redmond.corp.microsoft.com ([157.54.2.168]) by
	inet-hub-03.redmond.corp.microsoft.com with Microsoft
	SMTPSVC(6.0.3790.0); Fri, 28 May 2004 09:15:36 -0700
Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com
	([157.54.0.39]) by RED-IMC-04.redmond.corp.microsoft.com with
	Microsoft SMTPSVC(6.0.3790.0); Fri, 28 May 2004 09:15:40 -0700
Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com
	([157.54.12.81]) by
	win-imc-01.wingroup.windeploy.ntdev.microsoft.com with
	Microsoft SMTPSVC(6.0.3790.1069); Fri, 28 May 2004 09:15:34 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 28 May 2004 09:15:06 -0700
Message-ID: <DAC3FCB50E31C54987CD10797DA511BA09450055@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: spoofing email addresses
Thread-Index: AcRExuRlfQVfsxUVQxSsgm5PMNOlqwABz0Bw
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: "Vernon Schryver" <vjs@calcite.rhyolite.com>, <ietf@ietf.org>
X-OriginalArrivalTime: 28 May 2004 16:15:34.0105 (UTC)
	FILETIME=[01209C90:01C444CF]
Content-Transfer-Encoding: quoted-printable
Subject: RE: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable


>   1. block port 25 to external IP addresses for all of your customers
>     except those with what draft-klensin-ip-service-terms-01.txt calls
>     Full Internet Connectivity.

... and receive a flood of complaints because 10% of your users are
using a mail service provided by someone else than you.

>   2. Do not sell Full Internet Connectivity to anyone running
Microsoft
>     software exposed to the Internet.

Regardless of whether Microsoft's software can be secured (it can), this
is a big no-op as a PC behind a "home firewall" is still at risk from
e-mail viruses and questionable web downloads.

>   3. The effects of #1 and #2 include forcing all mail from the usual
>     suspects through your own mail systems so that you can do as the
>     credit card companies do.  Track SMTP envelope Mail_To values or
>     other characteristics for each customer.  When you see a change,
>     contact the customer by voice to check.

So the solution to Spam has to be a massive surrender of privacy!=20

I am afraid that you are falling in the very trap that you often
denounce, present you personal definitive solution to Spam...

-- Christian Huitema

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


From ietf-bounces@ietf.org  Fri May 28 13:41: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 NAA18841
	for <ietf-archive@ietf.org>; Fri, 28 May 2004 13:41: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 1BTlLv-0003Ta-Gb
	for ietf-archive@ietf.org; Fri, 28 May 2004 13:41:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTlJq-0002bf-00
	for ietf-archive@ietf.org; Fri, 28 May 2004 13:38:58 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BTlGv-0001Qn-00; Fri, 28 May 2004 13:35:57 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BTkz9-0007WN-MV; Fri, 28 May 2004 13:17:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BTkcK-0001kv-A9
	for ietf@megatron.ietf.org; Fri, 28 May 2004 12: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 MAA15736
	for <ietf@ietf.org>; Fri, 28 May 2004 12:53: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 1BTkcJ-0007At-4g
	for ietf@ietf.org; Fri, 28 May 2004 12:53:59 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTkbP-0006mE-00
	for ietf@ietf.org; Fri, 28 May 2004 12:53:04 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx with esmtp (Exim 4.12) id 1BTkau-0006N7-00
	for ietf@ietf.org; Fri, 28 May 2004 12:52:32 -0400
Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150])
	by ithilien.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id
	i4SGpuU9016372; Fri, 28 May 2004 09:51:56 -0700 (PDT)
Received: from [129.46.227.161] (carbuncle.qualcomm.com [129.46.227.161])
	by sabrina.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id
	i4SGpsKB008031; Fri, 28 May 2004 09:51:55 -0700 (PDT)
Mime-Version: 1.0
X-Sender: hardie@mage.qualcomm.com
Message-Id: <p06100504bcdd19f751de@[129.46.227.161]>
In-Reply-To: <20040527211714.B6D1D13951@sa.vix.com>
References: <20040527211714.B6D1D13951@sa.vix.com>
Date: Fri, 28 May 2004 09:51:53 -0700
To: Paul Vixie <paul@vix.com>, ietf@ietf.org
From: Ted Hardie <hardie@qualcomm.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

At 9:17 PM +0000 05/27/2004, Paul Vixie wrote:
>
>MARID is basically a layer 9 exercise, uninterested in engineering as
>such.  it was formed to merge two ill considered ideas, one from yahoo
>and one from microsoft, in a way that would cause either no loss of face,
>or equal loss of face, for those two parties.  the people who submit
>their own ideas to it are wasting their time.
>

As the AD who sponsored this work, I have to disagree.   The MARID
work came out of the LMAP area of the Anti-Spam Research Group,
and there were multiple proposals there.  All of them are being
treated as input into MARID, and that fact is called out in the charter.
The recent interim meeting resulted in an agreement to work on
a converged spec taking ideas from SPF and Caller-ID.  There are
two other proposals on the table which address other parts of
the mail exchange, and there was a sense in the meeting that they
were sufficiently orthogonal that they might progress independently.
None of the work mentioned above relates to Yahoo's proposal.
Anyone interested in the work is welcome to participate in
MARID's mailing list; it has a very tight deadline and a very high
volume mailing list, and those willing to put engineering effort
into it are more than welcome.

Speaking as a participant, I have to say that this is a hard set of
problems, both to define well and to solve.  The efforts to
define it well do occasionally drift into layer 9, and limiting
that is something everyone involved has to watch.  But
I do believe there are some tractable pieces here we can pull
off of the problem and solve, and I believe the working group
is committed to that task, no matter who proposes the solution.

			regards,
				Ted Hardie

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


From ietf-bounces@ietf.org  Fri May 28 13:43: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 NAA19062
	for <ietf-archive@ietf.org>; Fri, 28 May 2004 13:43: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 1BTlOC-0004UC-IH
	for ietf-archive@ietf.org; Fri, 28 May 2004 13:43:28 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTlMp-0003gi-00
	for ietf-archive@ietf.org; Fri, 28 May 2004 13:42:04 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BTlLK-00031F-00; Fri, 28 May 2004 13:40:30 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BTkzM-0007ft-RR; Fri, 28 May 2004 13:17:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BTkhU-0003D3-Uf
	for ietf@megatron.ietf.org; Fri, 28 May 2004 12:59:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15999
	for <ietf@ietf.org>; Fri, 28 May 2004 12:59: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 1BTkhT-0001fD-Ti
	for ietf@ietf.org; Fri, 28 May 2004 12:59:20 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTkgh-0001CE-00
	for ietf@ietf.org; Fri, 28 May 2004 12:58:31 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12) id 1BTkfL-0000Iw-00
	for ietf@ietf.org; Fri, 28 May 2004 12:57:07 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.11/8.12.11) id i4SGubi3051575
	for ietf@ietf.org env-from <vjs>;
	Fri, 28 May 2004 10:56:37 -0600 (MDT)
Date: Fri, 28 May 2004 10:56:37 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200405281656.i4SGubi3051575@calcite.rhyolite.com>
To: ietf@ietf.org
References: <DAC3FCB50E31C54987CD10797DA511BA09450055@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Subject: RE: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

> From: "Christian Huitema" <huitema@windows.microsoft.com>

> >   1. block port 25 to external IP addresses for all of your customers
> >     except those with what draft-klensin-ip-service-terms-01.txt calls
> >     Full Internet Connectivity.
>
> ... and receive a flood of complaints because 10% of your users are
> using a mail service provided by someone else than you.

That's a significant problem, but so what?  Stopping spam is not without
costs. The spam problem exists only because service providers sell
other than Full Internet Connectivity and cannot charge enough for the
other flavors to squash abuse.

The reason spam is a problem is that ISPs are unwilling or unable to
pay the costs necessary to zap spamming customers.  If spam were a
certain path to termination with prejudice, there would be no significant
spam.  If ISPs would immediately and permanently terminate all spamming
customers and refuse to exchange STMP/TCP/IP with other ISPs that fail
to terminate spammers, there would be no spam problem and no need for
blocking port 25 and so forth.

If Microsoft would have been willing to pay the costs to ship secure
software for the last 10 years, than the spam distribution mechanism
currently favored by the worst spammers would not exist.


> >   2. Do not sell Full Internet Connectivity to anyone running Microsoft
> >     software exposed to the Internet.
>
> Regardless of whether Microsoft's software can be secured (it can), 

As we all know, that is true in Microsoft marketing liturature and
plausible theories but false in practice.  As I said, practically all
desktop Windows XP and NT installations have users running browsers
and MUAs as "administrator."  Contrary to the knowingly misleading
statements from Microsoft appologists, that fact makes Windows a
hopelessly insecure system.

Then there are the versions of Windows not related to Windows NT
that cannot be secured even in theory.

>                                                                     this
> is a big no-op as a PC behind a "home firewall" is still at risk from
> e-mail viruses and questionable web downloads.

A PC running Microsoft software behind a "home firewall" for most
meanings of that phrase including Microsoft's is not protected. 
It must not be exposed to the Internet.


> >   3. The effects of #1 and #2 include forcing all mail from the usual
> >     suspects through your own mail systems so that you can do as the
> >     credit card companies do.  Track SMTP envelope Mail_To values or
> >     other characteristics for each customer.  When you see a change,
> >     contact the customer by voice to check.
>
> So the solution to Spam has to be a massive surrender of privacy! 

This statement is disingenous.  No existing privacy is lost.  It is
just as false and dishonest to claim that the credit card companies
reduce someone's privacy with their anti-fraud mechanisms.  Exactly
the same mail information is already present in ISP SMTP server logs.
Privacy is not lost by people acting on your private information.  It
is lost when your private information is collected.  Changing how
computers manipulate your no-longer-private information does not reduce
your privacy.  Disclosing the fact that you do not have privacy
does not reduce your privacy.

If you want privacy, you must use cash instead of a credit card.
You must also buy full internet connectivity, run your own SMTP
client, and use at least SMTP-TLS, and of course, that's only a
start toward mail privacy.


> I am afraid that you are falling in the very trap that you often
> denounce, present you personal definitive solution to Spam...

My modest proposal would stop spam, but is not unique.  As I wrote in
words you did not quote, the spam problem results from service providers
such as UUNet, Comcast, and Yahoo and software vendors such as your
employer refusing to pay their shares of the costs to stop network abuse.


Vernon Schryver    vjs@rhyolite.com


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


From ietf-bounces@ietf.org  Fri May 28 14:23: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 OAA21111
	for <ietf-archive@ietf.org>; Fri, 28 May 2004 14:23: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 1BTm0e-00065p-DT
	for ietf-archive@ietf.org; Fri, 28 May 2004 14:23:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTlzZ-0005d7-00
	for ietf-archive@ietf.org; Fri, 28 May 2004 14:22:05 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BTlyp-0004vx-00; Fri, 28 May 2004 14:21:19 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BTlbq-0000Qh-Tt; Fri, 28 May 2004 13:57:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BTlQf-0006KI-IS
	for ietf@megatron.ietf.org; Fri, 28 May 2004 13:46: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 NAA19300
	for <ietf@ietf.org>; Fri, 28 May 2004 13:45: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 1BTlQe-0005qC-ID
	for ietf@ietf.org; Fri, 28 May 2004 13:46:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTlPl-0005O0-00
	for ietf@ietf.org; Fri, 28 May 2004 13:45:06 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx with esmtp (Exim 4.12) id 1BTlOV-0004Su-00
	for ietf@ietf.org; Fri, 28 May 2004 13:43:47 -0400
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i4SHgfJ02180;
	Fri, 28 May 2004 10:42:41 -0700 (PDT)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost) by gra.isi.edu (8.9.3/8.8.6) id KAA19773;
	Fri, 28 May 2004 10:42:41 -0700 (PDT)
Date: Fri, 28 May 2004 10:42:41 -0700 (PDT)
Message-Id: <200405281742.KAA19773@gra.isi.edu>
To: ietf@ietf.org, Michael.Richardson@seawaynetworks.com
X-Sun-Charset: US-ASCII
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: braden@isi.edu
Subject: Re: STD series of documents
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60


  *> From ietf-bounces@ietf.org  Fri May 28 05:58:39 2004
  *> To: ietf@ietf.org
  *> Date: Thu, 27 May 2004 16:19:15 -0400
  *> From: Michael Richardson <Michael.Richardson@seawaynetworks.com>
  *> X-Mailman-Approved-At: Fri, 28 May 2004 08:19:57 -0400
  *> Subject: STD series of documents
  *> X-BeenThere: ietf@ietf.org
  *> X-Mailman-Version: 2.1.5
  *> List-Id: IETF-Discussion <ietf.ietf.org>
  *> List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
  *> 	<mailto:ietf-request@ietf.org?subject=unsubscribe>
  *> List-Post: <mailto:ietf@ietf.org>
  *> List-Help: <mailto:ietf-request@ietf.org?subject=help>
  *> List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
  *> 	<mailto:ietf-request@ietf.org?subject=subscribe>
  *> X-ISI-4-30-3-MailScanner: Found to be clean, Found to be clean
  *> X-MailScanner-From: ietf-bounces@ietf.org
  *> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on boreas.isi.edu
  *> X-Spam-Level: 
  *> X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00,UPPERCASE_25_50 
  *> 	autolearn=no version=2.63
  *> X-Status: 
  *> X-Keywords:                  
  *> X-UID: 3100
  *> 
  *> -----BEGIN PGP SIGNED MESSAGE-----
  *> Hash: SHA1
  *> 
  *> 
  *> May I suggest that a URL like:
  *> 
  *>     http://www.ietf.org/std/std0051.txt
  *> 
  *> be made that can refer to the STD series of documents?

Note that:

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

already works.

Bob Braden for the RFC Editor



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


From ietf-bounces@ietf.org  Fri May 28 15:32: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 PAA27333
	for <ietf-archive@ietf.org>; Fri, 28 May 2004 15:32: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 1BTn5o-0004cg-8n
	for ietf-archive@ietf.org; Fri, 28 May 2004 15:32:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTn4c-0004BT-00
	for ietf-archive@ietf.org; Fri, 28 May 2004 15:31:23 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BTn3t-0003jP-00; Fri, 28 May 2004 15:30:37 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BTmx1-0005yh-Ot; Fri, 28 May 2004 15:23:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BTmmO-000161-0O
	for ietf@megatron.ietf.org; Fri, 28 May 2004 15:12: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 PAA25885
	for <ietf@ietf.org>; Fri, 28 May 2004 15:12: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 1BTmm7-00040i-GF
	for ietf@ietf.org; Fri, 28 May 2004 15:12:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTml3-0003av-00
	for ietf@ietf.org; Fri, 28 May 2004 15:11:10 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx with esmtp (Exim 4.12) id 1BTmkF-0003BS-00
	for ietf@ietf.org; Fri, 28 May 2004 15:10:19 -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 i4SJ7K1C028100;
	Fri, 28 May 2004 21:07:21 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <40B7396A.2090309@centive.com>
References: <B2403217-AEA1-11D8-A66A-000A95B3BA44@hxr.us>	<200405262100.i4QL00Ua008101@calcite.rhyolite.com>	<200405271456.i4REuawJ022844@turing-police.cc.vt.edu>
	<294A7108-AFFA-11D8-8E28-000A95CD987A@muada.com>
	<40B7396A.2090309@centive.com>
Mime-Version: 1.0 (Apple Message framework v618)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <49FC4550-B0DA-11D8-B41C-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Fri, 28 May 2004 21:07:39 +0200
To: John Stracke <jstracke@centive.com>
X-Mailer: Apple Mail (2.618)
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

On 28-mei-04, at 15:06, John Stracke wrote:

>>> (I've yet to see a proposal that works if the spammers start
>>> utilizing zombie machines that snarf the already-stored credentials 
>>> of the user to send mail)....

>> The question is whether spammers can obtain new credentials (stolen 
>> or otherwise) faster than others can blacklist them.

> And, if you had actually read the message you replied to, you would 
> have realized that the answer is yes.

I don't see why.

> Send out a worm that makes N zombies, have each zombie send one 
> message under the local user's credentials, and none of them will get 
> blacklisted.

That makes the number of spam messages received by an email user (on 
average) equal to the number of email users divided by the number of 
systems vulnerable to becoming a zombie. So one spam a day/week/month 
or so = a lot better than the current situation.

Don't assume that the high level of vulnerability we're seeing today 
will remain the same in the future. (It will remain > 0 though.) There 
was a time when desktop systems would completely crash regularly 
because badly written software would take down the whole system. 
Software quality isn't beter these days, but desktop operating systems 
are now able to protect the system against most software errors. I'm 
sure we'll see similar developments in the area of security. Zone Alarm 
(network access restricted on a per-application basis) and the MacOS 
keychain system (access to passwords and certificates restricted on a 
per-application basis) are the way of the future.

-- 
"Every computer sold in the US is safe by default.  It is powered off,
disconnected, in a factory sealed box" - Sean Donelan, on NANOG


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


From ietf-bounces@ietf.org  Fri May 28 17:47: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 RAA09266
	for <ietf-archive@ietf.org>; Fri, 28 May 2004 17: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 1BTpCT-0000bY-2Z
	for ietf-archive@ietf.org; Fri, 28 May 2004 17:47:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTpAc-0007W0-00
	for ietf-archive@ietf.org; Fri, 28 May 2004 17:45:42 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BTp9F-0006av-00; Fri, 28 May 2004 17:44:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BTomd-00038w-Pm; Fri, 28 May 2004 17:20:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BTo3u-0006wl-E7
	for ietf@megatron.ietf.org; Fri, 28 May 2004 16:34: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 QAA02496
	for <ietf@ietf.org>; Fri, 28 May 2004 16:34: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 1BTo3t-0001Fc-4D
	for ietf@ietf.org; Fri, 28 May 2004 16:34:41 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BTo2x-0000m1-00
	for ietf@ietf.org; Fri, 28 May 2004 16:33:44 -0400
Received: from rwcrmhc13.comcast.net ([204.127.198.39])
	by ietf-mx with esmtp (Exim 4.12) id 1BTo1V-0007cE-00
	for ietf@ietf.org; Fri, 28 May 2004 16:32:13 -0400
Received: from [10.0.1.3]
	(pcp08936879pcs.trentn01.nj.comcast.net[69.141.151.92])
	by comcast.net (rwcrmhc13) with ESMTP
	id <20040528203142015006p9o8e>; Fri, 28 May 2004 20:31:43 +0000
Mime-Version: 1.0
X-Sender: cook+cookreport.com@cookreport.com
Message-Id: <p06100513bcdd515fc8cf@[10.0.1.3]>
Date: Fri, 28 May 2004 16:31:39 -0400
To: ietf@ietf.org
From: Gordon Cook <cook@cookreport.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Subject: telecom recovery unlikely as long as best effort is industry's
 only business model
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

Since mid March I have been leading a private mail list and came out 
with a conclusion last weekend  that there can be no telecom recovery 
as long as the industry relies solely on the best effort business 
model which I believe is not economically sustainable.

This has led to two articles on my June-July issue conclusions this 
week in the trade press.  Something that has never happened to me 
before.  :-)

The first is ISP Planet and the second Broadband Edge.

Here are the urls

http://www.isp-planet.com/perspectives/2004/cook_internet.html  (monday)

http://bbedge.mblast.com/presentation/page798-878156.asp  (today)

Finally my summary, table of contents and list of contributors is at 
http://cookreport.com/13.04.shtml

Enjoy the weekend.

-- 
=============================================================
The COOK Report on Internet Protocol, 431 Greenway Ave, Ewing, NJ 08618 USA
  609 882-2572 (PSTN) 703 738-6031 (Vonage) Subscription info & prices 
at http://cookreport.com/subscriptions.shtml Report on economic black 
hole of best
effort networks at: http://cookreport.com/13.04.shtml  E-mail 
cook@cookreport.com
=============================================================


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


From ietf-bounces@ietf.org  Sat May 29 11:47: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 LAA09039
	for <ietf-archive@ietf.org>; Sat, 29 May 2004 11:47: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 1BU63w-0004y6-7b
	for ietf-archive@ietf.org; Sat, 29 May 2004 11:47:56 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BU62v-0004bJ-00
	for ietf-archive@ietf.org; Sat, 29 May 2004 11:46:54 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BU622-0003tu-00; Sat, 29 May 2004 11:45:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BU5vC-0004Wc-9C; Sat, 29 May 2004 11:38:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BU5sI-00046M-4B
	for ietf@megatron.ietf.org; Sat, 29 May 2004 11:35: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 LAA08732
	for <ietf@ietf.org>; Sat, 29 May 2004 11:35: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 1BU5sG-0000gZ-TM
	for ietf@ietf.org; Sat, 29 May 2004 11:35:53 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BU5rH-0000KA-00
	for ietf@ietf.org; Sat, 29 May 2004 11:34:52 -0400
Received: from web40504.mail.yahoo.com ([66.218.78.121])
	by ietf-mx with smtp (Exim 4.12) id 1BU5qK-0007RR-00
	for Ietf@ietf.org; Sat, 29 May 2004 11:33:52 -0400
Message-ID: <20040529153321.88694.qmail@web40504.mail.yahoo.com>
Received: from [210.210.39.58] by web40504.mail.yahoo.com via HTTP;
	Sat, 29 May 2004 08:33:21 PDT
Date: Sat, 29 May 2004 08:33:21 -0700 (PDT)
From: raj kamath <smile4yuth@yahoo.com>
To: Ietf@ietf.org
MIME-Version: 1.0
Subject: unsubscribe me from the mailing list
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0561610766=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,HTML_MESSAGE autolearn=no 
	version=2.60

--===============0561610766==
Content-Type: multipart/alternative; boundary="0-2065666338-1085844801=:86579"

--0-2065666338-1085844801=:86579
Content-Type: text/plain; charset=us-ascii

  
		
---------------------------------
Do you Yahoo!?
Friends.  Fun. Try the all-new Yahoo! Messenger
--0-2065666338-1085844801=:86579
Content-Type: text/html; charset=us-ascii

 
 <p>
		<hr size=1><font face=arial size=-1>Do you Yahoo!?<br>Friends.  Fun. <a href="http://messenger.yahoo.com/">Try the all-new Yahoo! Messenger</a>
--0-2065666338-1085844801=:86579--


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

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

--===============0561610766==--



From ietf-bounces@ietf.org  Sun May 30 06:37: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 GAA00051
	for <ietf-archive@ietf.org>; Sun, 30 May 2004 06:37: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 1BUNhS-0002tC-Kc
	for ietf-archive@ietf.org; Sun, 30 May 2004 06:37:54 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUNgU-0002Xo-00
	for ietf-archive@ietf.org; Sun, 30 May 2004 06:36:55 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BUNft-0001vG-00; Sun, 30 May 2004 06:36:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BUNYN-0005YB-Pj; Sun, 30 May 2004 06:28:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BUNWe-0005JQ-Tn
	for ietf@megatron.ietf.org; Sun, 30 May 2004 06:26:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29570
	for <ietf@ietf.org>; Sun, 30 May 2004 06:26: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 1BUNWc-00074z-A1
	for ietf@ietf.org; Sun, 30 May 2004 06:26:42 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUNVj-0006kv-00
	for ietf@ietf.org; Sun, 30 May 2004 06:25:48 -0400
Received: from av4-2-sn3.vrr.skanova.net ([81.228.9.112])
	by ietf-mx with esmtp (Exim 4.12) id 1BUNVA-0006LA-00
	for ietf@ietf.org; Sun, 30 May 2004 06:25:12 -0400
Received: by av4-2-sn3.vrr.skanova.net (Postfix, from userid 502)
	id 8D36037E82; Sun, 30 May 2004 12:24:33 +0200 (CEST)
Received: from smtp1-2-sn3.vrr.skanova.net (smtp1-2-sn3.vrr.skanova.net
	[81.228.9.178])
	by av4-2-sn3.vrr.skanova.net (Postfix) with ESMTP id 800F837E5C
	for <ietf@ietf.org>; Sun, 30 May 2004 12:24:33 +0200 (CEST)
Received: from slimsixten.pilsnet.sunet.se (t5o38p52.telia.com [62.20.172.52])
	by smtp1-2-sn3.vrr.skanova.net (Postfix) with ESMTP id 5A3FC3800B
	for <ietf@ietf.org>; Sun, 30 May 2004 12:24:32 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1])
	by slimsixten.pilsnet.sunet.se (8.11.6p3/8.11.6) with ESMTP id
	i4TEEGW08066
	for <ietf@ietf.org>; Sat, 29 May 2004 16:14:16 +0200 (CEST)
Date: Fri, 28 May 2004 22:12:00 +0200
From: =?ISO-8859-1?Q?M=E5ns_Nilsson?= <mansaxel@besserwisser.org>
To: ietf@ietf.org
Message-ID: <83800000.1085775120@localhost>
In-Reply-To: <200405271851.i4RIpnuV070162@calcite.rhyolite.com>
References: <200405271727.i4RHRJNM021294@turing-police.cc.vt.edu>
	<200405271851.i4RIpnuV070162@calcite.rhyolite.com>
X-Mailer: Mulberry/3.1.1 (Linux/x86)
X-availability: Yes. 
MIME-Version: 1.0
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1580503441=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=DATE_IN_PAST_12_24 
	autolearn=no version=2.60

--===============1580503441==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="==========72A48CB32C08201F6BB0=========="

--==========72A48CB32C08201F6BB0==========
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable



--On Thursday, May 27, 2004 12:51:49 -0600 Vernon Schryver
<vjs@calcite.rhyolite.com> wrote:

> block port 25 for all types of IP
> service except the one that draft-klensin-ip-service-terms-01.txt calls
> "Full Internet Connectivity." =20

(agreeing with Iljitsch on this snippet)=20

I have a *very* hard time seeing an IETF document (or discussion on the
list) coming even close to endorsing this blocking malpractice. It does not
scale (forcing people to use central, probably misconfigured, relays, and
it is IMNSHO thorougly bad engineering to try solving L8 problems on L3/4.=20

--=20
M=E5ns Nilsson                    MN1334-RIPE
http://vvv.besserwisser.org     +46 706 81 72 04

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (NetBSD)

iD8DBQFAt50Q02/pMZDM1cURArdWAKCWlNuEihPoR91+MkKqwWMo1T6rfQCfbQlE
ui7MF5T1DvsP+qkwYlFBeNo=
=4oSt
-----END PGP SIGNATURE-----

--==========72A48CB32C08201F6BB0==========--



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

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

--===============1580503441==--




From ietf-bounces@ietf.org  Sun May 30 09:16: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 JAA05224
	for <ietf-archive@ietf.org>; Sun, 30 May 2004 09:16: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 1BUQBK-0001Bd-Fx
	for ietf-archive@ietf.org; Sun, 30 May 2004 09:16:54 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUQAH-0000qZ-00
	for ietf-archive@ietf.org; Sun, 30 May 2004 09:15:50 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BUQ9k-0000Vk-00; Sun, 30 May 2004 09:15:16 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BUQ76-000693-MM; Sun, 30 May 2004 09:12:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BUQ3b-0005fQ-Uy
	for ietf@megatron.ietf.org; Sun, 30 May 2004 09:08: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 JAA05072
	for <ietf@ietf.org>; Sun, 30 May 2004 09:08: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 1BUQ3b-0006Lu-6b
	for ietf@ietf.org; Sun, 30 May 2004 09:08:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUQ2b-00061V-00
	for ietf@ietf.org; Sun, 30 May 2004 09:07:54 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12) id 1BUQ20-0005fj-00
	for ietf@ietf.org; Sun, 30 May 2004 09:07:16 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.11/8.12.11) id i4UD6juG015370
	for ietf@ietf.org env-from <vjs>;
	Sun, 30 May 2004 07:06:45 -0600 (MDT)
Date: Sun, 30 May 2004 07:06:45 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200405301306.i4UD6juG015370@calcite.rhyolite.com>
To: ietf@ietf.org
References: <83800000.1085775120@localhost>
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

> From: =?ISO-8859-1?Q?M=E5ns_Nilsson?= <mansaxel@besserwisser.org>

>
> > block port 25 for all types of IP
> > service except the one that draft-klensin-ip-service-terms-01.txt calls
> > "Full Internet Connectivity." 

> I have a *very* hard time seeing an IETF document (or discussion on the
> list) coming even close to endorsing this blocking malpractice. It does not
> scale (forcing people to use central, probably misconfigured, relays, and
> it is IMNSHO thorougly bad engineering to try solving L8 problems on L3/4.

So say each of you who feel you have a right to pay less than what
providing full internet connectivity costs.   Full connectivity is
priced at about $100-$250/month, and plausibly and apparently costs
less to provide.  The $20-$30/month services provided by the providers
that cannot afford real abuse desks or local technical support are not
really Internet service, no matter that you might wish.

What I find really strange thing is the price point chosen for this
divinely ordained right.  Why is $300-$400/year ok but $200/month is
a violation of your fundamental human rights?  Why is paying what Full
Internet Connective costs evil and wrong, but it is ok to pay more
than the $300/year that people in some parts of the world live on for
a whole year?

The scaling argument is obvious nonsense.  If having $30/month
customers use SMTP servers provided by their ISPs did not "scale",
then it would not "scale" to have those same customers use the
routers provided by those same ISPs.

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

If ISPs and their customers were willing to deal with spam, including
immediately and permanently terminating customers that send any spam,
regardless of whether they are paid for their efforts (e.g. operators
of trojan zombies), then there would be no spam problem.

Why should the rest of us subsidize your ISP and your connectivity by
accepting SMTP/TCP/IP SYNs from your neighbors that are more than 99%
likely to be spam from trojan zombies that your ISP cannot be bothered
to terminate?


Vernon Schryver    vjs@rhyolite.com

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


From ietf-bounces@ietf.org  Sun May 30 10:20: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 KAA08633
	for <ietf-archive@ietf.org>; Sun, 30 May 2004 10:20: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 1BURAU-0007R2-9D
	for ietf-archive@ietf.org; Sun, 30 May 2004 10:20:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUR9Q-000741-00
	for ietf-archive@ietf.org; Sun, 30 May 2004 10:19:01 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BUR8f-0006ZG-00; Sun, 30 May 2004 10:18:13 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BUR1c-0007jz-B8; Sun, 30 May 2004 10:10:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BUQyc-0006cE-G1
	for ietf@megatron.ietf.org; Sun, 30 May 2004 10:07:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07217
	for <ietf@ietf.org>; Sun, 30 May 2004 10:07: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 1BUQyb-000395-Od
	for ietf@ietf.org; Sun, 30 May 2004 10:07:49 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUQxb-0002mQ-00
	for ietf@ietf.org; Sun, 30 May 2004 10:06:48 -0400
Received: from 206-169-2-196.gen.twtelecom.net ([206.169.2.196]
	helo=mail.optistreams.net) by ietf-mx with esmtp (Exim 4.12)
	id 1BUQwV-00026l-00
	for ietf@ietf.org; Sun, 30 May 2004 10:05:39 -0400
Received: from [192.168.0.101] [68.42.70.186] by mail.optistreams.net with
	ESMTP (SMTPD32-8.04) id A49B35BA01E2; Sun, 30 May 2004 06:41:47 -0700
In-Reply-To: <200405301306.i4UD6juG015370@calcite.rhyolite.com>
References: <83800000.1085775120@localhost>
	<200405301306.i4UD6juG015370@calcite.rhyolite.com>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <5144465C-B242-11D8-903D-000A9571873E@guppylake.com>
Content-Transfer-Encoding: 7bit
From: Nathaniel Borenstein <nsb@guppylake.com>
Date: Sun, 30 May 2004 10:04:50 -0400
To: Vernon Schryver <vjs@calcite.rhyolite.com>
X-Mailer: Apple Mail (2.613)
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

This would be a very interesting philosophical argument if in fact what 
we were discussing was something that could take a significant bite out 
of spam.  In the absence of such an ability, however, the real question 
is whether user accounts should be crippled in the name of spam 
fighting when the crippling *isn't* going to help significantly with 
the spam problem.  And that's not a philosophical debate, just a matter 
of common sense.    Grocery stores probably have the right to require 
their customers to wear formal attire, but if they don't have a good 
reason to do it, they're going to drive away customers no matter what 
the outcome of any philosophical debates.  My expectation is that ISP's 
who implement anti-spam measures that are both intrusive and 
ineffective are going to drive away customers as long as there's a 
better alternative out there, and I'd be inclined to simply let them do 
it unless they're in near-monopolistic market positions.  The latter 
exception is important, however; I'd certainly be upset if my cable 
provider did it, because I don't have any good alternatives.  -- 
Nathaniel

On May 30, 2004, at 9:06 AM, Vernon Schryver wrote:

>> From: =?ISO-8859-1?Q?M=E5ns_Nilsson?= <mansaxel@besserwisser.org>
>
>>
>>> block port 25 for all types of IP
>>> service except the one that draft-klensin-ip-service-terms-01.txt 
>>> calls
>>> "Full Internet Connectivity."
>
>> I have a *very* hard time seeing an IETF document (or discussion on 
>> the
>> list) coming even close to endorsing this blocking malpractice. It 
>> does not
>> scale (forcing people to use central, probably misconfigured, relays, 
>> and
>> it is IMNSHO thorougly bad engineering to try solving L8 problems on 
>> L3/4.
>
> So say each of you who feel you have a right to pay less than what
> providing full internet connectivity costs.   Full connectivity is
> priced at about $100-$250/month, and plausibly and apparently costs
> less to provide.  The $20-$30/month services provided by the providers
> that cannot afford real abuse desks or local technical support are not
> really Internet service, no matter that you might wish.
>
> What I find really strange thing is the price point chosen for this
> divinely ordained right.  Why is $300-$400/year ok but $200/month is
> a violation of your fundamental human rights?  Why is paying what Full
> Internet Connective costs evil and wrong, but it is ok to pay more
> than the $300/year that people in some parts of the world live on for
> a whole year?
>
> The scaling argument is obvious nonsense.  If having $30/month
> customers use SMTP servers provided by their ISPs did not "scale",
> then it would not "scale" to have those same customers use the
> routers provided by those same ISPs.
>
> If your ISP is incompetent at configuring an SMTP server, then whose
> fault is it that you continue to buy bad service?   Why don't you treat
> your incompetent locl provider of "Client only, non-public address"
> or "Client only, public address" as a provider of those services and
> use them only to connect to a system where you get competent Full
> Internet Connectivity?
>
> If ISPs and their customers were willing to deal with spam, including
> immediately and permanently terminating customers that send any spam,
> regardless of whether they are paid for their efforts (e.g. operators
> of trojan zombies), then there would be no spam problem.
>
> Why should the rest of us subsidize your ISP and your connectivity by
> accepting SMTP/TCP/IP SYNs from your neighbors that are more than 99%
> likely to be spam from trojan zombies that your ISP cannot be bothered
> to terminate?
>
>
> Vernon Schryver    vjs@rhyolite.com
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>
>


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


From ietf-bounces@ietf.org  Sun May 30 11:05: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 LAA10253
	for <ietf-archive@ietf.org>; Sun, 30 May 2004 11:05:53 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BURsp-0007Wg-61
	for ietf-archive@ietf.org; Sun, 30 May 2004 11:05:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BURrr-00078l-00
	for ietf-archive@ietf.org; Sun, 30 May 2004 11:04:56 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BURr5-0006U0-00; Sun, 30 May 2004 11:04:07 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BURjs-0005wh-UF; Sun, 30 May 2004 10:56:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BURbM-0005AO-O9
	for ietf@megatron.ietf.org; Sun, 30 May 2004 10:47:52 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09717
	for <ietf@ietf.org>; Sun, 30 May 2004 10:47: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 1BURbM-0001Ou-0V
	for ietf@ietf.org; Sun, 30 May 2004 10:47:52 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BURaQ-00014W-00
	for ietf@ietf.org; Sun, 30 May 2004 10:46:55 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12) id 1BURZk-0000VM-00
	for ietf@ietf.org; Sun, 30 May 2004 10:46:12 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.11/8.12.11) id i4UEjfs6043917
	for ietf@ietf.org env-from <vjs>;
	Sun, 30 May 2004 08:45:41 -0600 (MDT)
Date: Sun, 30 May 2004 08:45:41 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200405301445.i4UEjfs6043917@calcite.rhyolite.com>
To: ietf@ietf.org
References: <5144465C-B242-11D8-903D-000A9571873E@guppylake.com>
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

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

> This would be a very interesting philosophical argument if in fact what 
> we were discussing was something that could take a significant bite out 
> of spam.  In the absence of such an ability, however, the real question 
> is whether user accounts should be crippled in the name of spam 
> fighting when the crippling *isn't* going to help significantly with 
> the spam problem.  And that's not a philosophical debate, just a matter 
> of common sense.    Grocery stores probably have the right to require 
> their customers to wear formal attire, but if they don't have a good 
> reason to do it, they're going to drive away customers no matter what 
> the outcome of any philosophical debates.

Grocery stores frequently requires shirts and shoes.  A better analogy
is that grocery stores that sell alcohol or other regulated drugs are
required to pay substantial extra costs.  Complaints about monopolies
in the beer and wine trade are laughed at, as are demands that pharmacies
in grocery stores not charge prices high enough to pay their pharmacists.

As Mr. Borenstein knows, a substantial fraction and probably most spam
is current sent using $30/month consumer accounts.  The spam that is
not sent using such accounts is very easily blocked.  As he knows, if
providers of those services would either filter port 25 or terminate
customers running trojan zombies, that spam would stop.  Providers of
those $30/month accounts have made clear that they cannot afford to
hire the people to monitor and deal with their abusive customers.  That
is why many of the providers of those $30/month accounts submit their
own IP address blocks to various "dynamic" backlists or block port 25
themselves.

Stopping trojan zombies would not end the spam problem, but it would
be a major improvement.  You can see the truth of that in the results
of UUNet's imposition of port 25 filtering on its dial-up resellers.
It would also significantly improve security problems caused by Microsoft
systems, because viruses and worms could be filtered by ISP SMTP servers
from outgoing mail.


>                                            My expectation is that ISP's 
> who implement anti-spam measures that are both intrusive and 
> ineffective are going to drive away customers as long as there's a 
> better alternative out there, and I'd be inclined to simply let them do 
> it unless they're in near-monopolistic market positions.  The latter 
> exception is important, however; I'd certainly be upset if my cable 
> provider did it, because I don't have any good alternatives.  -- 

It is dishonest to imply that cable TV providers have near-monopolistic
market positions in providing Internet service.  They often have near
or true monopolies in providing cable TV service.  However, in no U.S.
market do cable TV providers have anything like monopolies in providing
Internet service.  They may have monopolies in providing some of
services at $30/month, including "Web connectivity," "Client only,
non-public address," and "Client only, public address."  Mr. Borenstein
can buy Full Internet Connectivity from many service providers, although
not at $30/month.

Mr. Borenstein and others like him expect the rest of us to subsidize
their $30/month connectivity by dealing with the network abuse of his
fellow customers, because they find $30/month comfortable.  That position
would be less despicable if they would demand free Internet connectivity,
since that is the only price that billions of other people can afford.


Vernon Schryver    vjs@rhyolite.com

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


From ietf-bounces@ietf.org  Sun May 30 12:22: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 MAA13444
	for <ietf-archive@ietf.org>; Sun, 30 May 2004 12:22: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 1BUT5R-0006xd-El
	for ietf-archive@ietf.org; Sun, 30 May 2004 12:23:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUT4Y-0006dr-00
	for ietf-archive@ietf.org; Sun, 30 May 2004 12:22:06 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BUT46-0006KJ-00; Sun, 30 May 2004 12:21:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BUSz8-0006WA-3o; Sun, 30 May 2004 12:16:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BUSu4-00056v-9E
	for ietf@megatron.ietf.org; Sun, 30 May 2004 12:11: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 MAA12788
	for <ietf@ietf.org>; Sun, 30 May 2004 12:10: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 1BUSto-00030h-BQ
	for ietf@ietf.org; Sun, 30 May 2004 12:11:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUSss-0002hA-00
	for ietf@ietf.org; Sun, 30 May 2004 12:10:03 -0400
Received: from 206-169-2-196.gen.twtelecom.net ([206.169.2.196]
	helo=mail.optistreams.net) by ietf-mx with esmtp (Exim 4.12)
	id 1BUSsE-0002CW-00
	for ietf@ietf.org; Sun, 30 May 2004 12:09:22 -0400
Received: from [192.168.0.101] [68.42.70.186] by mail.optistreams.net with
	ESMTP (SMTPD32-8.04) id A1A012F3024E; Sun, 30 May 2004 08:45:36 -0700
In-Reply-To: <200405301445.i4UEjfs6043917@calcite.rhyolite.com>
References: <5144465C-B242-11D8-903D-000A9571873E@guppylake.com>
	<200405301445.i4UEjfs6043917@calcite.rhyolite.com>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <9DA4FA7E-B253-11D8-903D-000A9571873E@guppylake.com>
Content-Transfer-Encoding: 7bit
From: Nathaniel Borenstein <nsb@guppylake.com>
Date: Sun, 30 May 2004 12:08:40 -0400
To: Vernon Schryver <vjs@calcite.rhyolite.com>
X-Mailer: Apple Mail (2.613)
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

On May 30, 2004, at 10:45 AM, Vernon Schryver wrote:

> Mr. Borenstein and others like him expect the rest of us to subsidize
> their $30/month connectivity by dealing with the network abuse of his
> fellow customers, because they find $30/month comfortable.

Just for the record, I spend plenty more than $30 per month on Internet 
connectivity, as does my employer.  My views on this have nothing to do 
with the cost of my Internet service, which is why I said nothing about 
such costs.  Since your message seems to be based entirely on a 
misguided assessment of my motives, there's not much else in it that 
needs to be answered.  (We could argue forever about what constitutes a 
monopoly, but I doubt any minds would be changed.)

Port 25 blocking may be sometimes necessary simply to preserve the 
integrity of a network under heavy spam attack.  But I believe that a 
long-term solution is possible that will be both more effective and 
less restrictive.  My own focus is on that long-term planning, and I 
just can't see port 25 blocking as anything more than a rather 
problematic stopgap measure in advance of a more spam-resistant 
infrastructure for SMTP message submission.  -- Nathaniel


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


From ietf-bounces@ietf.org  Sun May 30 12:43: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 MAA14439
	for <ietf-archive@ietf.org>; Sun, 30 May 2004 12:43: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 1BUTOo-0005mM-P3
	for ietf-archive@ietf.org; Sun, 30 May 2004 12:43:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUTNk-0005Ol-00
	for ietf-archive@ietf.org; Sun, 30 May 2004 12:41:57 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BUTMe-0004lm-00; Sun, 30 May 2004 12:40:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BUTE2-0000Rk-5d; Sun, 30 May 2004 12:31:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BUTAI-0008Oh-J8
	for ietf@megatron.ietf.org; Sun, 30 May 2004 12:28: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 MAA13709
	for <ietf@ietf.org>; Sun, 30 May 2004 12:27: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 1BUTAH-0000rf-LU
	for ietf@ietf.org; Sun, 30 May 2004 12:28:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUT9N-0000Yi-00
	for ietf@ietf.org; Sun, 30 May 2004 12:27:06 -0400
Received: from 117.cust55.nsw.dsl.ozemail.com.au ([203.102.126.117]
	helo=nosense.org) by ietf-mx with esmtp (Exim 4.12)
	id 1BUT8z-0000EM-00
	for ietf@ietf.org; Sun, 30 May 2004 12:26:42 -0400
Received: from Dupy2.nosense.org (localhost.localdomain [127.0.0.1])
	by nosense.org (Postfix) with SMTP
	id C682B3F02A; Mon, 31 May 2004 01:56:04 +0930 (CST)
Date: Mon, 31 May 2004 01:56:04 +0930
From: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <20040531015604.3f5d996d.ietf@130c04165a5b40404e4440445758487a.nosense.org>
In-Reply-To: <200405301445.i4UEjfs6043917@calcite.rhyolite.com>
References: <5144465C-B242-11D8-903D-000A9571873E@guppylake.com>
	<200405301445.i4UEjfs6043917@calcite.rhyolite.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
Cc: ietf@ietf.org
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

On Sun, 30 May 2004 08:45:41 -0600 (MDT)
Vernon Schryver <vjs@calcite.rhyolite.com> wrote:

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

<snip>

> As Mr. Borenstein knows, a substantial fraction and probably
> most spam is current sent using $30/month consumer accounts. 
> The spam that is not sent using such accounts is very easily
> blocked.  As he knows, if providers of those services would
> either filter port 25 or terminate customers running trojan
> zombies, that spam would stop.  Providers of those $30/month
> accounts have made clear that they cannot afford to hire the
> people to monitor and deal with their abusive customers.  That
> is why many of the providers of those $30/month accounts submit
> their own IP address blocks to various "dynamic" backlists or
> block port 25 themselves.
> 

Do you have more information or references regarding your
statements above? I'm interested in any studies etc.


I would find TCP port 25  being blocked by my ISP to be
unacceptable. It isn't the Internet anymore. The Internet's job
is to shunt around IP packets, irrespective of what is in them.

My anti-spam measures are so effective that I can't remember the
last spam I received. I would find not be able to run my own MTA,
unfortunately on a dynamically assigned IP ADSL service, as that
is all I can afford, to be far more costly than the very
negligable reduction in spam I would receive if TCP port 25 was
blocked by ISPs.


Regards,
Mark.

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


From ietf-bounces@ietf.org  Sun May 30 12:54: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 MAA14966
	for <ietf-archive@ietf.org>; Sun, 30 May 2004 12:54: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 1BUTaM-0001xZ-II
	for ietf-archive@ietf.org; Sun, 30 May 2004 12:54:58 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUTZL-0001av-00
	for ietf-archive@ietf.org; Sun, 30 May 2004 12:53:56 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BUTYP-0000xa-00; Sun, 30 May 2004 12:52:57 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BUTPK-00027u-SM; Sun, 30 May 2004 12:43:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BUTJp-0000rT-TE
	for ietf@megatron.ietf.org; Sun, 30 May 2004 12:37: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 MAA14130
	for <ietf@ietf.org>; Sun, 30 May 2004 12:37: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 1BUTJo-000458-TG
	for ietf@ietf.org; Sun, 30 May 2004 12:37:53 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUTIp-0003k9-00
	for ietf@ietf.org; Sun, 30 May 2004 12:36:51 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12) id 1BUTHq-00037G-00
	for ietf@ietf.org; Sun, 30 May 2004 12:35:50 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id AEAA3621E4; Sun, 30 May 2004 18:35:19 +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 05310-05; Sun, 30 May 2004 18:35:19 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain
	[127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP
	id 63AEB62209; Sun, 30 May 2004 18:35:17 +0200 (CEST)
Date: Sun, 30 May 2004 08:29:45 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: "Paul Hoffman / VPNC" <paul.hoffman@vpnc.org>, ietf@ietf.org
Message-ID: <2F2BC1062895C438503853B1@B50854F0A9192E8EC6CDA126>
In-Reply-To: <p06100516bcdd11fdf9c5@[10.20.30.249]>
References: <p06100516bcdd11fdf9c5@[10.20.30.249]>
X-Mailer: Mulberry/3.1.5 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
Content-Transfer-Encoding: 7bit
Subject: Re: Summary of the ad-hoc WiFi problems at IETF meetings?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Paul,

I'll ask - but Brett Thorson was the person that was gathering the info, 
and he has just left CNRI. So I don't know whether the information has been 
preserved.

                        Harald

--On 28. mai 2004 09:00 -0700 "Paul Hoffman / VPNC" <paul.hoffman@vpnc.org> 
wrote:

> Greetings again. I was at a conference this week that offered WiFi. They
> had the same problems we had at the past two IETFs with a few folks doing
> ad-hoc mode, thereby knocking out access for many of us. Was there any
> writeup from the IETF NOC teams about the problem and how we fixed it? If
> so, it would be great to make that information available to the wider
> world.
>
> Please send responses to me, and I'll summarize them to the list.
>
> --Paul Hoffman, Director
> --VPN Consortium
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>
>





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


From ietf-bounces@ietf.org  Sun May 30 13:06: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 NAA15484
	for <ietf-archive@ietf.org>; Sun, 30 May 2004 13:06: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 1BUTlJ-0005Yo-EA
	for ietf-archive@ietf.org; Sun, 30 May 2004 13:06:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUTkD-0005D6-00
	for ietf-archive@ietf.org; Sun, 30 May 2004 13:05:10 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BUTjH-0004ZQ-00; Sun, 30 May 2004 13:04:11 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BUTcp-0003uH-89; Sun, 30 May 2004 12:57:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BUTVW-0002ml-DI
	for ietf@megatron.ietf.org; Sun, 30 May 2004 12:49:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14833
	for <ietf@ietf.org>; Sun, 30 May 2004 12:49:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BUTVV-0000Kj-Ha
	for ietf@ietf.org; Sun, 30 May 2004 12:49:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUTUZ-00000R-00
	for ietf@ietf.org; Sun, 30 May 2004 12:48:59 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12) id 1BUTTb-0007AR-00
	for ietf@ietf.org; Sun, 30 May 2004 12:47:59 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.11/8.12.11) id i4UGlP1W086129
	for ietf@ietf.org env-from <vjs>;
	Sun, 30 May 2004 10:47:25 -0600 (MDT)
Date: Sun, 30 May 2004 10:47:25 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200405301647.i4UGlP1W086129@calcite.rhyolite.com>
To: ietf@ietf.org
References: <9DA4FA7E-B253-11D8-903D-000A9571873E@guppylake.com>
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

>Received: from mail.optistreams.net (206-169-2-196.gen.twtelecom.net [206.169.2.196])
>        by calcite.rhyolite.com (8.12.11/8.12.11) with ESMTP id i4UG8bio077225
>        for <vjs@calcite.rhyolite.com> env-from <nsb@guppylake.com>;
>        Sun, 30 May 2004 10:08:38 -0600 (MDT)

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

> > Mr. Borenstein and others like him expect the rest of us to subsidize
> > their $30/month connectivity by dealing with the network abuse of his
> > fellow customers, because they find $30/month comfortable.
>
> Just for the record, I spend plenty more than $30 per month on Internet 
> connectivity, as does my employer.  My views on this have nothing to do 
> with the cost of my Internet service, which is why I said nothing about 
> such costs. Since your message seems to be based entirely on a 
> misguided assessment of my motives, there's not much else in it that 
> needs to be answered.  (We could argue forever about what constitutes a 
> monopoly, but I doubt any minds would be changed.)
>
> Port 25 blocking may be sometimes necessary simply to preserve the 
> integrity of a network under heavy spam attack. 

Perhaps I am mistaken, but I believe that Mr. Borenstein has mentioned
his costs in the past.  His recent talk about the supposed "near
monopolies" of "cable providers" makes absolutely no sense except
in the context of $30/month services.

The copy of his message appears to have been sent to my SMTP server
from one of those $30/month accounts.  Mr. Borenstein certainly has
complained about some sort of blocking of his mail.  I think that
blocking involved a cable provider account.  However, if the blocking
that bothered him was not from his TimeWarner acocunt, then perhaps
this is relevant:

traceroute to guppylake.com (64.71.173.70), 64 hops max, 44 byte packets
11  ix-8-0.core1.SanJose.teleglobe.net (66.198.97.18)  59.309 ms
12  pos2-3.gsr12416.pao.he.net (66.220.13.42)  119.297 ms
13  pos2-0.gsr12012.fmt.he.net (64.62.249.121)  61.106 ms
14  64.71.173.70 (64.71.173.70)  62.479 ms

traceroute to thehideout.net (64.71.176.110), 64 hops max, 44 byte packets
13  pos2-0.gsr12012.fmt.he.net (64.62.249.121)  60.953 ms
14  64.71.176.110 (64.71.176.110)  61.028 ms


Hurricane Electric has earned a reputation as a provider that avoids
dealing with reports of spam sent by its customers except by
forwarding them reports to its customers.  See
http://groups.google.com/groups?scoring=d&q=+%22he.net%22+group%3A*email
http://groups.google.com/groups?scoring=d&as_epq=Hurricane%20Electric 
http://groups.google.com/groups?scoring=d&q=+%22he.net%22+group%3A*abuse*

Juging from http://spews.org/html/S2100.html 64.71.173.70 is currently
listed by SPEWS at level 2.  (I do not use or advocate SPEWS' list;
I'm pointing out SPEWS' data only to support my point about the supposed
unfairness of the blocking of Mr. Borenstein's mail.)

>                                                  But I believe that a 
> long-term solution is possible that will be both more effective and 
> less restrictive.  My own focus is on that long-term planning, and I 
> just can't see port 25 blocking as anything more than a rather 
> problematic stopgap measure in advance of a more spam-resistant 
> infrastructure for SMTP message submission.

People have been talking about such ideas since Cyberpromo's day.  The
closest thing that has ever been implemented and proven effective is
blocking port 25 SYNs from blocks of IP address that have a better
than 99.9% probability of sending only spam and worms, namely the IP
addresses of spammers and of "dynamic address."  In practice the latter
is synonmous with block port 25 for $30/month accounts.

Blocking port 25 from $30/month accounts does not affect SMTP-SUBMIT,
which is the IETF standardized "spam-resistant infrastructure for SMTP
message submission."   One must wonder how Mr.  Borenstein's mail could
be blocked by the sort of blocking he has repeatedly complained about
if he used SMTP-SUBMIT to reach reputable MTAs.

Note also the disconnect between the reverse-DNS of Mr. Borenstein's
SMTP client and his envelope Mail_From and header From: values,
and the lack of DNS RRs supporting any of the proposals for DNS-based
sender authentication.  According to the advocates of those mechanisms,
Mr. Borenstein's is "forging" his messages.


Vernon Schryver    vjs@rhyolite.com

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


From ietf-bounces@ietf.org  Sun May 30 13:13: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 NAA15897
	for <ietf-archive@ietf.org>; Sun, 30 May 2004 13:13: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 1BUTsi-0000Nl-BH
	for ietf-archive@ietf.org; Sun, 30 May 2004 13:13:56 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUTrn-00003p-00
	for ietf-archive@ietf.org; Sun, 30 May 2004 13:12:59 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BUTqy-0007G0-00; Sun, 30 May 2004 13:12:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BUToG-0005Va-O5; Sun, 30 May 2004 13:09:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BUTmH-0005AN-8X
	for ietf@megatron.ietf.org; Sun, 30 May 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 NAA15644
	for <ietf@ietf.org>; Sun, 30 May 2004 13:07: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 1BUTmG-0005vu-B1
	for ietf@ietf.org; Sun, 30 May 2004 13:07:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUTlE-0005Y9-00
	for ietf@ietf.org; Sun, 30 May 2004 13:06:13 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12) id 1BUTk6-0004tV-00
	for ietf@ietf.org; Sun, 30 May 2004 13:05:02 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.11/8.12.11) id i4UH4WJL092983
	for ietf@ietf.org env-from <vjs>;
	Sun, 30 May 2004 11:04:32 -0600 (MDT)
Date: Sun, 30 May 2004 11:04:32 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200405301704.i4UH4WJL092983@calcite.rhyolite.com>
To: ietf@ietf.org
References: <20040531015604.3f5d996d.ietf@130c04165a5b40404e4440445758487a.nosense.org>
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

> From: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>

> > people to monitor and deal with their abusive customers.  That
> > is why many of the providers of those $30/month accounts submit
> > their own IP address blocks to various "dynamic" backlists or
> > block port 25 themselves.
>
> Do you have more information or references regarding your
> statements above? I'm interested in any studies etc.

The easiest study is to look at your own spam load.

The most recent public study or reliable comment I'm aware of 
was the statement from Comcast about how much spam they send in
http://news.com.com/Attack+of+Comcast%27s+Internet+zombies/2010-1034_3-5218178.html

See also http://www.senderbase.org/?searchString=comcast.net&searchBy=domain
and http://www.senderbase.org/

(I do not believe SenderBase's numbers are accurate to better than
several percent of total Internet mail or tens of millions of
msgs/day.  I know that their numbers for the domain names and IP
addresses I control are nonsense, but my domains and addresses are
directly involved with 5 or 6 orders of magnitude less mail than
those listed in http://www.senderbase.org/ )



> I would find TCP port 25  being blocked by my ISP to be
> unacceptable. It isn't the Internet anymore. The Internet's job
> is to shunt around IP packets, irrespective of what is in them.

That is inaccurate.  From ancient days it has also been the job
of people running things to prevent traffic that would violate
various agreements, AUPs, TOS, and so forth.


> My anti-spam measures are so effective that I can't remember the
> last spam I received. 

Yes, spam filtering can be quite effective.  I say this based in part
on the results of the DCC, which handled about 136,000,000 mail messages
on May 26.  However, the effectiveness of input filtering is irrelevant
to the need to deal with spam at its sources.

>                       I would find not be able to run my own MTA,
> unfortunately on a dynamically assigned IP ADSL service, as that
> is all I can afford, to be far more costly than the very
> negligable reduction in spam I would receive if TCP port 25 was
> blocked by ISPs.

I cannot understand that as other than a demand that I subsidize your
Internet service.

If you think that everyone has the right to run their own MTAs, why
don't you insist that Full Internet Connectivity be free?


Vernon Schryver    vjs@rhyolite.com

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


From ietf-bounces@ietf.org  Sun May 30 13:55:56 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17612
	for <ietf-archive@ietf.org>; Sun, 30 May 2004 13:55:56 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BUUXM-00064C-BF
	for ietf-archive@ietf.org; Sun, 30 May 2004 13:55:56 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUUWN-0005jB-00
	for ietf-archive@ietf.org; Sun, 30 May 2004 13:54:56 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BUUVH-00055w-00; Sun, 30 May 2004 13:53:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BUUSU-00021i-TI; Sun, 30 May 2004 13:50:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BUUKp-0001GI-0h
	for ietf@megatron.ietf.org; Sun, 30 May 2004 13:42:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17008
	for <ietf@ietf.org>; Sun, 30 May 2004 13:42: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 1BUUKn-0001uc-Vc
	for ietf@ietf.org; Sun, 30 May 2004 13:42:58 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUUJo-0001Zm-00
	for ietf@ietf.org; Sun, 30 May 2004 13:41:57 -0400
Received: from 206-169-2-196.gen.twtelecom.net ([206.169.2.196]
	helo=mail.optistreams.net) by ietf-mx with esmtp (Exim 4.12)
	id 1BUUIo-0000yC-00
	for ietf@ietf.org; Sun, 30 May 2004 13:40:54 -0400
Received: from [192.168.0.101] [68.42.70.186] by mail.optistreams.net with
	ESMTP (SMTPD32-8.04) id A722377901E2; Sun, 30 May 2004 10:17:22 -0700
In-Reply-To: <200405301647.i4UGlP1W086129@calcite.rhyolite.com>
References: <9DA4FA7E-B253-11D8-903D-000A9571873E@guppylake.com>
	<200405301647.i4UGlP1W086129@calcite.rhyolite.com>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <6ED4A208-B260-11D8-903D-000A9571873E@guppylake.com>
Content-Transfer-Encoding: 7bit
From: Nathaniel Borenstein <nsb@guppylake.com>
Date: Sun, 30 May 2004 13:40:25 -0400
To: Vernon Schryver <vjs@calcite.rhyolite.com>
X-Mailer: Apple Mail (2.613)
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Please stop this random speculating.  The ISP that was blocked is not  
my current ISP (I moved last fall), so none of this is relevant.  And  
if I'm dealing with Hurricane now, well, that's the first I'd heard of  
it, since I'm downstream on a hosted service and never bothered to  
check who all my upstream providers are.  Are you seriously asserting  
that I deserve to be blocked if I don't confirm that all my upstream  
ISP's are complying with J. Random Blacklist?

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

On May 30, 2004, at 12:47 PM, Vernon Schryver wrote:

>> Received: from mail.optistreams.net (206-169-2-196.gen.twtelecom.net  
>> [206.169.2.196])
>>        by calcite.rhyolite.com (8.12.11/8.12.11) with ESMTP id  
>> i4UG8bio077225
>>        for <vjs@calcite.rhyolite.com> env-from <nsb@guppylake.com>;
>>        Sun, 30 May 2004 10:08:38 -0600 (MDT)
>
>> From: Nathaniel Borenstein <nsb@guppylake.com>
>
>>> Mr. Borenstein and others like him expect the rest of us to subsidize
>>> their $30/month connectivity by dealing with the network abuse of his
>>> fellow customers, because they find $30/month comfortable.
>>
>> Just for the record, I spend plenty more than $30 per month on  
>> Internet
>> connectivity, as does my employer.  My views on this have nothing to  
>> do
>> with the cost of my Internet service, which is why I said nothing  
>> about
>> such costs. Since your message seems to be based entirely on a
>> misguided assessment of my motives, there's not much else in it that
>> needs to be answered.  (We could argue forever about what constitutes  
>> a
>> monopoly, but I doubt any minds would be changed.)
>>
>> Port 25 blocking may be sometimes necessary simply to preserve the
>> integrity of a network under heavy spam attack.
>
> Perhaps I am mistaken, but I believe that Mr. Borenstein has mentioned
> his costs in the past.  His recent talk about the supposed "near
> monopolies" of "cable providers" makes absolutely no sense except
> in the context of $30/month services.
>
> The copy of his message appears to have been sent to my SMTP server
> from one of those $30/month accounts.  Mr. Borenstein certainly has
> complained about some sort of blocking of his mail.  I think that
> blocking involved a cable provider account.  However, if the blocking
> that bothered him was not from his TimeWarner acocunt, then perhaps
> this is relevant:
>
> traceroute to guppylake.com (64.71.173.70), 64 hops max, 44 byte  
> packets
> 11  ix-8-0.core1.SanJose.teleglobe.net (66.198.97.18)  59.309 ms
> 12  pos2-3.gsr12416.pao.he.net (66.220.13.42)  119.297 ms
> 13  pos2-0.gsr12012.fmt.he.net (64.62.249.121)  61.106 ms
> 14  64.71.173.70 (64.71.173.70)  62.479 ms
>
> traceroute to thehideout.net (64.71.176.110), 64 hops max, 44 byte  
> packets
> 13  pos2-0.gsr12012.fmt.he.net (64.62.249.121)  60.953 ms
> 14  64.71.176.110 (64.71.176.110)  61.028 ms
>
>
> Hurricane Electric has earned a reputation as a provider that avoids
> dealing with reports of spam sent by its customers except by
> forwarding them reports to its customers.  See
> http://groups.google.com/groups? 
> scoring=d&q=+%22he.net%22+group%3A*email
> http://groups.google.com/groups?scoring=d&as_epq=Hurricane%20Electric
> http://groups.google.com/groups? 
> scoring=d&q=+%22he.net%22+group%3A*abuse*
>
> Juging from http://spews.org/html/S2100.html 64.71.173.70 is currently
> listed by SPEWS at level 2.  (I do not use or advocate SPEWS' list;
> I'm pointing out SPEWS' data only to support my point about the  
> supposed
> unfairness of the blocking of Mr. Borenstein's mail.)
>
>>                                                  But I believe that a
>> long-term solution is possible that will be both more effective and
>> less restrictive.  My own focus is on that long-term planning, and I
>> just can't see port 25 blocking as anything more than a rather
>> problematic stopgap measure in advance of a more spam-resistant
>> infrastructure for SMTP message submission.
>
> People have been talking about such ideas since Cyberpromo's day.  The
> closest thing that has ever been implemented and proven effective is
> blocking port 25 SYNs from blocks of IP address that have a better
> than 99.9% probability of sending only spam and worms, namely the IP
> addresses of spammers and of "dynamic address."  In practice the latter
> is synonmous with block port 25 for $30/month accounts.
>
> Blocking port 25 from $30/month accounts does not affect SMTP-SUBMIT,
> which is the IETF standardized "spam-resistant infrastructure for SMTP
> message submission."   One must wonder how Mr.  Borenstein's mail could
> be blocked by the sort of blocking he has repeatedly complained about
> if he used SMTP-SUBMIT to reach reputable MTAs.
>
> Note also the disconnect between the reverse-DNS of Mr. Borenstein's
> SMTP client and his envelope Mail_From and header From: values,
> and the lack of DNS RRs supporting any of the proposals for DNS-based
> sender authentication.  According to the advocates of those mechanisms,
> Mr. Borenstein's is "forging" his messages.
>
>
> Vernon Schryver    vjs@rhyolite.com
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>
>


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


From ietf-bounces@ietf.org  Sun May 30 14:38: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 OAA19531
	for <ietf-archive@ietf.org>; Sun, 30 May 2004 14:38: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 1BUVC6-0004BP-Ji
	for ietf-archive@ietf.org; Sun, 30 May 2004 14:38:02 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUVB8-0003sG-00
	for ietf-archive@ietf.org; Sun, 30 May 2004 14:37:03 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BUVAU-0003PZ-00; Sun, 30 May 2004 14:36:22 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BUV7k-0006vC-FI; Sun, 30 May 2004 14:33:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BUV4R-0006RA-8U
	for ietf@megatron.ietf.org; Sun, 30 May 2004 14:30:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19213
	for <ietf@ietf.org>; Sun, 30 May 2004 14:30: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 1BUV4P-0001gu-Tr
	for ietf@ietf.org; Sun, 30 May 2004 14:30:06 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUV3R-0001N1-00
	for ietf@ietf.org; Sun, 30 May 2004 14:29:06 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12) id 1BUV2a-0000ka-00
	for ietf@ietf.org; Sun, 30 May 2004 14:28:12 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.11/8.12.11) id i4UIRgm8018347
	for ietf@ietf.org env-from <vjs>;
	Sun, 30 May 2004 12:27:42 -0600 (MDT)
Date: Sun, 30 May 2004 12:27:42 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200405301827.i4UIRgm8018347@calcite.rhyolite.com>
To: ietf@ietf.org
References: <6ED4A208-B260-11D8-903D-000A9571873E@guppylake.com>
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

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

> Please stop this random speculating.  The ISP that was blocked is not  
> my current ISP (I moved last fall), so none of this is relevant. 

So what ISP was blocked?  Why do I suspect you are being disingenuous
and that it was a $30/month account?

>                                                                   And  
> if I'm dealing with Hurricane now, well, that's the first I'd heard of  
> it, since I'm downstream on a hosted service and never bothered to  
> check who all my upstream providers are. 

As always, the buyer must beware.  Adopting the terminology in
draft-klensin-ip-service-terms-01.txt or similar would help.  Hurricane
Electric could say that its IP addresses may not be optimal for SMTP
clients but are useful for SMTP, HTTP, and other servers.


>                                           Are you seriously asserting  
> that I deserve to be blocked if I don't confirm that all my upstream  
> ISP's are complying with J. Random Blacklist?

That is a obviously an intentional distortion of my point.  However,
now that you "ask," then yes, you do "deserve" to have your mail
blocked if you buy service from a provider with a reputation for
being friendly to spammers.  Your failure to exercise due diligence
does not impose an obligation to accept more spam on others.  You
"deserve to be blocked" more than the rest of us "deserve" to receive
the spam that helps support Hurricane Electric.


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

On the contrary, Caller-ID and SPF would not stop as much spam without
collateral damage as blocking port 25 from TimeWarner, Comcast, and
other $30/month service providers.  Caller-ID and SPF cannot have
significant effects against spam for at least the 5-10 years before
most domains support them.  Caller-ID, SPF, and the rest would in
effect block port 25 about the same IP addresses as simple port 25
blocking of $30/month accounts, in the unlikely event that Caller-ID
etc. ever have any effects.  If you would switch to SUBMIT, you would
not care if your TimeWarner account is port 25 blocked, except that
you might expect TimeWarner's prices to drop for needing even less
abuse-desk staff.  On the other hand, port 25 blocking can be done
today and has immediate good effects against spam, as well as worms
and viruses.

Of course, port 25 is not a panacea for spam, worms, or viruses.
Of course, some viruses and spammers would adopt the obvious
countermeasure of using the ISP's servers, but many would not.
Besides, the ISP is could filter or at least rate limit, and there
are no easy countermeasures for spammers against that.


Vernon Schryver    vjs@rhyolite.com

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


From ietf-bounces@ietf.org  Sun May 30 16:12: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 QAA23299
	for <ietf-archive@ietf.org>; Sun, 30 May 2004 16:12: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 1BUWfB-0002Tf-CX
	for ietf-archive@ietf.org; Sun, 30 May 2004 16:12:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUWeC-00027j-00
	for ietf-archive@ietf.org; Sun, 30 May 2004 16:11:09 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BUWd7-0001T5-00; Sun, 30 May 2004 16:10:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BUWXA-00022P-MW; Sun, 30 May 2004 16:03:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BUWVP-0001kl-4n
	for ietf@megatron.ietf.org; Sun, 30 May 2004 16:02: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 QAA23001
	for <ietf@ietf.org>; Sun, 30 May 2004 16:02: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 1BUWVN-00074W-NS
	for ietf@ietf.org; Sun, 30 May 2004 16:02:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUWUS-0006lx-00
	for ietf@ietf.org; Sun, 30 May 2004 16:01:05 -0400
Received: from 206-169-2-196.gen.twtelecom.net ([206.169.2.196]
	helo=mail.optistreams.net) by ietf-mx with esmtp (Exim 4.12)
	id 1BUWU5-0006TY-00
	for ietf@ietf.org; Sun, 30 May 2004 16:00:41 -0400
Received: from [192.168.0.101] [68.42.70.186] by mail.optistreams.net with
	ESMTP (SMTPD32-8.04) id A7E412290240; Sun, 30 May 2004 12:37:08 -0700
In-Reply-To: <200405301827.i4UIRgm8018347@calcite.rhyolite.com>
References: <6ED4A208-B260-11D8-903D-000A9571873E@guppylake.com>
	<200405301827.i4UIRgm8018347@calcite.rhyolite.com>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <F60EDD1E-B273-11D8-903D-000A9571873E@guppylake.com>
Content-Transfer-Encoding: 7bit
From: Nathaniel Borenstein <nsb@guppylake.com>
Date: Sun, 30 May 2004 16:00:12 -0400
To: Vernon Schryver <vjs@calcite.rhyolite.com>
X-Mailer: Apple Mail (2.613)
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

On May 30, 2004, at 2:27 PM, Vernon Schryver wrote:

> So what ISP was blocked?

What are you, the ISP police?  Not that it's any of your business, it 
was X0 DSL and I paid just under $100/month and hosted my server at 
home; it was blacklisted as part of a larger block of IP addresses 
beyond my control.  When I moved physically, I took the opportunity to 
move my server to a hosted service for guppylake.com, and NOW am on a 
normal cable modem at home.  I've been associated with the domain 
guppylake.com for almost twenty years, however, and I rather like to 
continue sending mail from that address even though I now obtain my 
bitstream from Comcast.

But I imagine that X0 is also on your list of ISP's-that-are-evil, so 
it was my fault for using them in the first place.

> Why do I suspect you are being disingenuous
> and that it was a $30/month account?

I don't know, perhaps because you have a suspicious nature and are 
quick to assume the worst about people?  I am not really the sort of 
person who tells lies on an IETF list just to make a point.

For my part, I am sufficiently paranoid to fear that ISP's might 
advocate port 25 blocking because they hope it will lock people into 
email addresses that are less portable (e.g. nsb@comcast.net).  But 
when they give other reasons, no matter how irrational I may think they 
sound, I try at least to give their sincerity the benefit of the doubt. 
   -- Nathaniel


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


From ietf-bounces@ietf.org  Sun May 30 17:28: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 RAA25782
	for <ietf-archive@ietf.org>; Sun, 30 May 2004 17:28: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 1BUXqf-0002Ql-HL
	for ietf-archive@ietf.org; Sun, 30 May 2004 17:28:05 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUXpf-000276-00
	for ietf-archive@ietf.org; Sun, 30 May 2004 17:27:04 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BUXoa-0001Vb-00; Sun, 30 May 2004 17:25:56 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BUXiX-00025c-Jl; Sun, 30 May 2004 17:19:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BUXh4-0001eY-J0
	for ietf@megatron.ietf.org; Sun, 30 May 2004 17:18: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 RAA25524
	for <ietf@ietf.org>; Sun, 30 May 2004 17:18: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 1BUXh3-00077N-3A
	for ietf@ietf.org; Sun, 30 May 2004 17:18:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUXg6-0006oo-00
	for ietf@ietf.org; Sun, 30 May 2004 17:17:11 -0400
Received: from snark.piermont.com ([166.84.151.72])
	by ietf-mx with esmtp (Exim 4.12) id 1BUXfe-0006W5-00
	for ietf@ietf.org; Sun, 30 May 2004 17:16:42 -0400
Received: by snark.piermont.com (Postfix, from userid 1000)
	id 55CD7D97CF; Sun, 30 May 2004 17:16:42 -0400 (EDT)
To: Nathaniel Borenstein <nsb@guppylake.com>
References: <83800000.1085775120@localhost>
	<200405301306.i4UD6juG015370@calcite.rhyolite.com>
	<5144465C-B242-11D8-903D-000A9571873E@guppylake.com>
From: "Perry E. Metzger" <perry@piermont.com>
Date: Sun, 30 May 2004 17:16:42 -0400
In-Reply-To: <5144465C-B242-11D8-903D-000A9571873E@guppylake.com> (Nathaniel
	Borenstein's message of "Sun, 30 May 2004 10:04:50 -0400")
Message-ID: <873c5hr4xx.fsf@snark.piermont.com>
User-Agent: Gnus/5.1002 (Gnus v5.10.2) Emacs/21.3 (berkeley-unix)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: ietf@ietf.org, Vernon Schryver <vjs@calcite.rhyolite.com>
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60


Nathaniel Borenstein <nsb@guppylake.com> writes:
> This would be a very interesting philosophical argument if in fact
> what we were discussing was something that could take a significant
> bite out of spam.  In the absence of such an ability, however, the
> real question is whether user accounts should be crippled in the
> name of spam fighting when the crippling *isn't* going to help
> significantly with the spam problem.

But it will. Almost all of my spam comes via incompetent end users
who've had their machines taken over by the bad guys. Blocking dynamic
IP ranges also nukes a very large fraction of my spam.

I think the easy solution is just to block port 25 unless someone asks
for it to be opened. Average users have no idea what
port 25 does or even what TCP is, so they won't care.

Perry

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


From ietf-bounces@ietf.org  Sun May 30 18:05:12 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27280
	for <ietf-archive@ietf.org>; Sun, 30 May 2004 18:05: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 1BUYQb-0006JV-CW
	for ietf-archive@ietf.org; Sun, 30 May 2004 18:05:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUYPY-0005z1-00
	for ietf-archive@ietf.org; Sun, 30 May 2004 18:04:09 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BUYOa-0005Np-00; Sun, 30 May 2004 18:03:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BUYMO-0007P6-EQ; Sun, 30 May 2004 18:00:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BUYC6-00063Z-Hh
	for ietf@megatron.ietf.org; Sun, 30 May 2004 17:50:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26841
	for <ietf@ietf.org>; Sun, 30 May 2004 17:50:11 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BUYC5-0001qs-6I
	for ietf@ietf.org; Sun, 30 May 2004 17:50:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUYB9-0001Y5-00
	for ietf@ietf.org; Sun, 30 May 2004 17:49:15 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12) id 1BUYAS-00018d-00
	for ietf@ietf.org; Sun, 30 May 2004 17:48:32 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.11/8.12.11) id i4ULm2Ng071871
	for ietf@ietf.org env-from <vjs>;
	Sun, 30 May 2004 15:48:02 -0600 (MDT)
Date: Sun, 30 May 2004 15:48:02 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200405302148.i4ULm2Ng071871@calcite.rhyolite.com>
To: ietf@ietf.org
References: <F60EDD1E-B273-11D8-903D-000A9571873E@guppylake.com>
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

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

>
> On May 30, 2004, at 2:27 PM, Vernon Schryver wrote:
>
> > So what ISP was blocked?
>
> What are you, the ISP police?  Not that it's any of your business, it 
> was X0 DSL 

Your repeated, unprovoked public complaints about the blocking that
affected you made XO's identity not the business of everyone who cares
about such issues.  Then there were your comments about "near monopolies."

>            and I paid just under $100/month and hosted my server at 
> home; it was blacklisted as part of a larger block of IP addresses 
> beyond my control.  When I moved physically, I took the opportunity to 
> move my server to a hosted service for guppylake.com, and NOW am on a 
> normal cable modem at home.  I've been associated with the domain 
> guppylake.com for almost twenty years, however, and I rather like to 
> continue sending mail from that address even though I now obtain my 
> bitstream from Comcast.
>
> But I imagine that X0 is also on your list of ISP's-that-are-evil, so 
> it was my fault for using them in the first place.

That reference that any list of mine of evil ISPs is disingenuous.
Besides, I bet you know as well as I do that RoadRunner probably
blocked that larger block of addresses because of lots of spam.
For a while XO was having difficulty acting against its spamming
customers.  I've not noticed such complaints for a while.

It does sounds as if you have made a habit of hiring ISPs without
exercising due diligence.  If that is true, you might blame your
parents but not me.   I don't blame you for the fact that until
recently I've always paid much more than $100/month to host my
vanity domain, but then it has not been blacklisted.  I have moved
it more than once when I lost confidence in an ISP.


> > Why do I suspect you are being disingenuous
> > and that it was a $30/month account?
>
> I don't know, perhaps because you have a suspicious nature and are 
> quick to assume the worst about people? 

Instead of using ad hominem, you might recall your own words such as

]      ... near-monopolistic market positions. The latter exception
] is important, however; I'd certainly be upset if my cable provider
] did it, because I don't have any good alternatives

Then there is your coyness about XO's identity.  Why didn't you come
out and name it at the start?


>                                          I am not really the sort of 
> person who tells lies on an IETF list just to make a point.

Where have I lied?  For your part, you have repeatedly intentionally
misrepresented my words and generally been disingenuous.  For example,
your words above imply that I had no business asking which ISP was
involved in the blocking you have repeatedly complained about.  You
made the identity of the ISP a relevant point by your demands that I
stop "random speculating" as well as by your repeated complaints about
RoadRunner's blocking.


> For my part, I am sufficiently paranoid to fear that ISP's might 
> advocate port 25 blocking because they hope it will lock people into 
> email addresses that are less portable (e.g. nsb@comcast.net).  But 
> when they give other reasons, no matter how irrational I may think they 
> sound, I try at least to give their sincerity the benefit of the doubt. 

That is also disingenuous.  While I share concerns about locking
people into addresses, you know that blocking port 25 is unrelated
if people use some flavors of what you called "a more spam-resistant
infrastructure for SMTP message submission," such as SMTP-SUBMIT,
or simple "web mail."

Why don't you give RoadRunner's sincerity the benefit of the doubt
about the blocking of your XO address?  Did you check any of the well
know resources such as news.admin.net-abuse.sightings for evidence of
spam from your neighbors or did you just start complaining about evil
"near-monopolies"?

Do you have any substantive responses to my counters against your
claims that port 25 blocking is useless and harmful?  I claim 

 - port 25 blocking by $30/month providers would block little more
  than the spam that might someday be blocked by Caller-ID, SPF, etc.  

 - the legitimate mail blocked or false positives caused by port 25
  blocking is similar or less than that for Caller-ID, SPF, etc.

 - port 25 blocking can be implemented today piecemeal by individual
  providers on the sending side in routers and on the receiving side
  using blacklists, while Caller-ID, SPF, etc. must wait at least 5
  or 10 years until most of the Internet implements them.


Vernon Schryver    vjs@rhyolite.com

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


From ietf-bounces@ietf.org  Sun May 30 19:05: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 TAA00269
	for <ietf-archive@ietf.org>; Sun, 30 May 2004 19:05: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 1BUZMt-0001pv-6i
	for ietf-archive@ietf.org; Sun, 30 May 2004 19:05:27 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUZLl-0001Vu-00
	for ietf-archive@ietf.org; Sun, 30 May 2004 19:04:18 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BUZLQ-0001CB-00; Sun, 30 May 2004 19:03:56 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BUZD5-0003M4-NU; Sun, 30 May 2004 18:55:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BUZC4-0003C6-0m
	for ietf@megatron.ietf.org; Sun, 30 May 2004 18:54:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29758
	for <ietf@ietf.org>; Sun, 30 May 2004 18:54: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 1BUZC2-000657-FX
	for ietf@ietf.org; Sun, 30 May 2004 18:54:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUZB2-0005lE-00
	for ietf@ietf.org; Sun, 30 May 2004 18:53:12 -0400
Received: from 206-169-2-196.gen.twtelecom.net ([206.169.2.196]
	helo=mail.optistreams.net) by ietf-mx with esmtp (Exim 4.12)
	id 1BUZAI-0005A4-00
	for ietf@ietf.org; Sun, 30 May 2004 18:52:27 -0400
Received: from [192.168.0.101] [68.42.70.186] by mail.optistreams.net with
	ESMTP (SMTPD32-8.04) id A00915B00240; Sun, 30 May 2004 15:28:25 -0700
In-Reply-To: <873c5hr4xx.fsf@snark.piermont.com>
References: <83800000.1085775120@localhost>
	<200405301306.i4UD6juG015370@calcite.rhyolite.com>
	<5144465C-B242-11D8-903D-000A9571873E@guppylake.com>
	<873c5hr4xx.fsf@snark.piermont.com>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <E3D558B8-B28B-11D8-903D-000A9571873E@guppylake.com>
Content-Transfer-Encoding: 7bit
From: Nathaniel Borenstein <nsb@guppylake.com>
Date: Sun, 30 May 2004 18:51:30 -0400
To: "Perry E. Metzger" <perry@piermont.com>
X-Mailer: Apple Mail (2.613)
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, Vernon Schryver <vjs@calcite.rhyolite.com>
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

This is a remarkably reasonable proposal, and I would have no objection 
to it (just a fear that ISPs might make it unnecessarily hard to get it 
opened, but they tend to make everything hard).  Heck, I might not even 
mind paying an extra dollar or two per month to have it open.  As long 
as consumers have an option, I'm fine with this as a default.  Good 
idea.  -- Nathaniel

On May 30, 2004, at 5:16 PM, Perry E. Metzger wrote:

> I think the easy solution is just to block port 25 unless someone asks
> for it to be opened. Average users have no idea what
> port 25 does or even what TCP is, so they won't care.
>


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


From ietf-bounces@ietf.org  Sun May 30 20:45: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 UAA03694
	for <ietf-archive@ietf.org>; Sun, 30 May 2004 20:45:13 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BUavR-0002GB-8p
	for ietf-archive@ietf.org; Sun, 30 May 2004 20:45:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUauT-0001ue-00
	for ietf-archive@ietf.org; Sun, 30 May 2004 20:44:13 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BUatO-0001Ib-00; Sun, 30 May 2004 20:43:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BUanR-0005DA-9p; Sun, 30 May 2004 20:36:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BUag3-0004eM-So
	for ietf@megatron.ietf.org; Sun, 30 May 2004 20:29: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 UAA03203
	for <ietf@ietf.org>; Sun, 30 May 2004 20:29: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 1BUag0-000533-M3
	for ietf@ietf.org; Sun, 30 May 2004 20:29:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUaex-0004jr-00
	for ietf@ietf.org; Sun, 30 May 2004 20:28:11 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12) id 1BUadr-00049K-00
	for ietf@ietf.org; Sun, 30 May 2004 20:27:03 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.11/8.12.11) id i4V0QX7u018576
	for ietf@ietf.org env-from <vjs>;
	Sun, 30 May 2004 18:26:33 -0600 (MDT)
Date: Sun, 30 May 2004 18:26:33 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200405310026.i4V0QX7u018576@calcite.rhyolite.com>
To: ietf@ietf.org
References: <E3D558B8-B28B-11D8-903D-000A9571873E@guppylake.com>
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

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

> This is a remarkably reasonable proposal, and I would have no objection 
> to it (just a fear that ISPs might make it unnecessarily hard to get it 
> opened, but they tend to make everything hard).  Heck, I might not even 
> mind paying an extra dollar or two per month to have it open.  As long 
> as consumers have an option, I'm fine with this as a default.  Good 
> idea.  -- Nathaniel

> > I think the easy solution is just to block port 25 unless someone asks
> > for it to be opened. Average users have no idea what
> > port 25 does or even what TCP is, so they won't care.

and how does that proposal differ from what I wrote Thursday?:

]                                    block port 25 for all types of IP
] service except the one that draft-klensin-ip-service-terms-01.txt calls
] "Full Internet Connectivity." 

Mr. Borenstein recently wrote the following apparently about that:

} ... Grocery stores probably have the right to require their
} customers to wear formal attire, but if they don't have a good
} reason to do it, they're going to drive away customers no matter
} what the outcome of any philosophical debates.  My expectation is
} that ISP's who implement anti-spam measures that are both intrusive
} and ineffective are going to drive away customers as long as there's
} a better alternative out there, and I'd be inclined to simply let them
} do it unless they're in near-monopolistic market positions. The latter
} exception is important, however; I'd certainly be upset if my cable
} provider did it, because I don't have any good alternatives.

I don't mind in the least if Mr. Borenstein has changed his mind but
does not wish to say so.  I also don't care if he prefers the ancient
statement of the old idea offered by Perry Metzger.

I will mind if Mr. Borenstein resumes his campaign against the
supposed evils of blocking port 25.  Such unfounded complaints give
aid and comfort spammers and to marketing departments resisting
blocking port 25 for customers who aren't competent to use it.

Until consumer grade services providers such as Comcast do something
to stem the floods of spam they are sending, other organizations will
stem their incoming floods with bad tactics such as rejecting mail
from IP addresses with reverse DNS names containing "dsl".


Vernon Schryver    vjs@rhyolite.com

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


From ietf-bounces@ietf.org  Sun May 30 23:44: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 XAA10470
	for <ietf-archive@ietf.org>; Sun, 30 May 2004 23: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 1BUdin-0003FE-Me
	for ietf-archive@ietf.org; Sun, 30 May 2004 23:44:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUdhp-0002wc-00
	for ietf-archive@ietf.org; Sun, 30 May 2004 23:43:22 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BUdgq-0002M1-00; Sun, 30 May 2004 23:42:20 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BUdaZ-0008WT-4l; Sun, 30 May 2004 23:35:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BUdXN-0008LC-5h
	for ietf@megatron.ietf.org; Sun, 30 May 2004 23:32:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA10028
	for <ietf@ietf.org>; Sun, 30 May 2004 23:32: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 1BUdXL-0007Hl-6F
	for ietf@ietf.org; Sun, 30 May 2004 23:32:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUdWJ-0006wr-00
	for ietf@ietf.org; Sun, 30 May 2004 23:31:27 -0400
Received: from 117.cust55.nsw.dsl.ozemail.com.au ([203.102.126.117]
	helo=nosense.org) by ietf-mx with esmtp (Exim 4.12)
	id 1BUdVJ-0006JV-00
	for ietf@ietf.org; Sun, 30 May 2004 23:30:26 -0400
Received: from Dupy2.nosense.org (localhost.localdomain [127.0.0.1])
	by nosense.org (Postfix) with SMTP
	id 0D4433F02A; Mon, 31 May 2004 12:59:52 +0930 (CST)
Date: Mon, 31 May 2004 12:59:52 +0930
From: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <20040531125952.18baac6b.ietf@130c04165a5b40404e4440445758487a.nosense.org>
In-Reply-To: <200405301704.i4UH4WJL092983@calcite.rhyolite.com>
References: <20040531015604.3f5d996d.ietf@130c04165a5b40404e4440445758487a.nosense.org>
	<200405301704.i4UH4WJL092983@calcite.rhyolite.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
Cc: ietf@ietf.org
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

On Sun, 30 May 2004 11:04:32 -0600 (MDT)
Vernon Schryver <vjs@calcite.rhyolite.com> wrote:

> > From: Mark Smith
> > <ietf@130c04165a5b40404e4440445758487a.nosense.org>
> 
> > > people to monitor and deal with their abusive customers. 
> > > That is why many of the providers of those $30/month
> > > accounts submit their own IP address blocks to various
> > > "dynamic" backlists or block port 25 themselves.
> >
> > Do you have more information or references regarding your
> > statements above? I'm interested in any studies etc.
> 
> The easiest study is to look at your own spam load.
> 
> The most recent public study or reliable comment I'm aware of 
> was the statement from Comcast about how much spam they send in
> http://news.com.com/Attack+of+Comcast%27s+Internet+zombies/2010-1034_3-5218178.html
> 
> See also
> http://www.senderbase.org/?searchString=comcast.net&searchBy=domain
> and http://www.senderbase.org/
> 
> (I do not believe SenderBase's numbers are accurate to better
> than several percent of total Internet mail or tens of millions
> of msgs/day.  I know that their numbers for the domain names
> and IP addresses I control are nonsense, but my domains and
> addresses are directly involved with 5 or 6 orders of magnitude
> less mail than those listed in http://www.senderbase.org/ )
> 
> 

Thanks for those links, I'll have a read.

> 
> > I would find TCP port 25  being blocked by my ISP to be
> > unacceptable. It isn't the Internet anymore. The Internet's
> > job is to shunt around IP packets, irrespective of what is in
> > them.
> 
> That is inaccurate.  From ancient days it has also been the job
> of people running things to prevent traffic that would violate
> various agreements, AUPs, TOS, and so forth.
> 
> 
> > My anti-spam measures are so effective that I can't remember
> > the last spam I received. 
> 
> Yes, spam filtering can be quite effective.

Not using spam filtering ... I don't like the chances of false
positives or negatives.

My idea is similar to the idea of abandoning a phone number if
you get too many prank calls. Similar to abandoning a phone
number, when I abandon an email address, I don't even see the
spam traffic - I'm not filtering it out.

I've got a bit of a description of what I'm doing at the
following URL.

http://forums.whirlpool.net.au/forum-replies.cfm?t=184280#r4

It's not going to be perfect, nor am I claiming it to be,
however, I've found it to be pretty effective.

  I say this based
> in part on the results of the DCC, which handled about
> 136,000,000 mail messages on May 26.  However, the
> effectiveness of input filtering is irrelevant to the need to
> deal with spam at its sources.
> 
> >                       I would find not be able to run my own
> >                       MTA,
> > unfortunately on a dynamically assigned IP ADSL service, as
> > that is all I can afford, to be far more costly than the very
> > negligable reduction in spam I would receive if TCP port 25
> > was blocked by ISPs.
> 
> I cannot understand that as other than a demand that I
> subsidize your Internet service.
> 
> If you think that everyone has the right to run their own MTAs,
> why don't you insist that Full Internet Connectivity be free?
> 

I struggle to understand how you make such a dramatic jump in
"position" (I can't think of a better way to describe it at the
moment). I can't see the logical progression from being able to
run an MTA, to getting Internet connectivity for free. Of course,
if you're really making that offer, I'm quite interested :-)

Why do I run an MTA, and want that ability ? Because I run my own
domain name (nosense.org), allowing my email addresses to be ISP
independent, and I use multiple subdomains for email, which means
I fairly regularly need to change the MTA configuration. My
broadly, I don't want to have to rely on an ISP running an MTA
configuration which may not best suit my needs, when those needs
are or may be different from the general requirements of their
user base. It's sort of a "if you want something done
properly, do it yourself" situation.

Regards,
Mark.


> 
> Vernon Schryver    vjs@rhyolite.com
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf

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


From ietf-bounces@ietf.org  Mon May 31 00:07: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 AAA11568
	for <ietf-archive@ietf.org>; Mon, 31 May 2004 00:07: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 1BUe4t-0002Ja-V2
	for ietf-archive@ietf.org; Mon, 31 May 2004 00:07:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUe3g-0001rc-00
	for ietf-archive@ietf.org; Mon, 31 May 2004 00:05:57 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BUe1Q-0001OM-00; Mon, 31 May 2004 00:03:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BUdsi-0002Y9-6N; Sun, 30 May 2004 23:54:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BUdni-0001wB-TB
	for ietf@megatron.ietf.org; Sun, 30 May 2004 23:49: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 XAA10756
	for <ietf@ietf.org>; Sun, 30 May 2004 23:49: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 1BUdnf-0004uA-SW
	for ietf@ietf.org; Sun, 30 May 2004 23:49:23 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUdmh-0004bL-00
	for ietf@ietf.org; Sun, 30 May 2004 23:48:23 -0400
Received: from 117.cust55.nsw.dsl.ozemail.com.au ([203.102.126.117]
	helo=nosense.org) by ietf-mx with esmtp (Exim 4.12)
	id 1BUdmJ-0004Hc-00
	for ietf@ietf.org; Sun, 30 May 2004 23:48:00 -0400
Received: from Dupy2.nosense.org (localhost.localdomain [127.0.0.1])
	by nosense.org (Postfix) with SMTP
	id 372783F02A; Mon, 31 May 2004 13:17:29 +0930 (CST)
Date: Mon, 31 May 2004 13:17:29 +0930
From: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
To: "Perry E. Metzger" <perry@piermont.com>
Message-Id: <20040531131729.61123fde.ietf@130c04165a5b40404e4440445758487a.nosense.org>
In-Reply-To: <873c5hr4xx.fsf@snark.piermont.com>
References: <83800000.1085775120@localhost>
	<200405301306.i4UD6juG015370@calcite.rhyolite.com>
	<5144465C-B242-11D8-903D-000A9571873E@guppylake.com>
	<873c5hr4xx.fsf@snark.piermont.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
Cc: nsb@guppylake.com, ietf@ietf.org, vjs@calcite.rhyolite.com
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

On Sun, 30 May 2004 17:16:42 -0400
"Perry E. Metzger" <perry@piermont.com> wrote:

> 
> Nathaniel Borenstein <nsb@guppylake.com> writes:
> > This would be a very interesting philosophical argument if in
> > fact what we were discussing was something that could take a
> > significant bite out of spam.  In the absence of such an
> > ability, however, the real question is whether user accounts
> > should be crippled in the name of spam fighting when the
> > crippling *isn't* going to help significantly with the spam
> > problem.
> 
> But it will. Almost all of my spam comes via incompetent end
> users who've had their machines taken over by the bad guys.
> Blocking dynamic IP ranges also nukes a very large fraction of
> my spam.
> 

I really, really hesitate to suggest the following, I really hope
I'm not going to make the future happen by predicting it.

I'm just waiting for the next Outlook based (or alternatively, a
socially engineered executable based) worm that uses legitimate
email addresses and "legitimate" (in the sense of
"legitimate because TCP port 25 is not blocked") MTAs to send out
spam. Blocking TCP port 25 on dialup accounts (or any other
Internet service) will have no effect in mitigating these types
of attacks. Blocking TCP port 25 for ALL Internet access would be
the only way a traffic blocking technique would have any effect
in mitigating a spam delivery method like this.

> I think the easy solution is just to block port 25 unless
> someone asks for it to be opened. Average users have no idea
> what port 25 does or even what TCP is, so they won't care.
>

This isn't a bad idea, what it really does is adds a level of
manual, non-Internet, once-off authentication to the TCP port 25
service. The only question then is how well the authentication
procedures are followed. See Kevin Mitnick's book about those
problems.

Regards,
Mark.
 

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


From ietf-bounces@ietf.org  Mon May 31 01:39:33 2004
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA15435
	for <ietf-archive@ietf.org>; Mon, 31 May 2004 01:39:33 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BUfWF-0001no-WA
	for ietf-archive@ietf.org; Mon, 31 May 2004 01:39:32 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUfVN-0001Ti-00
	for ietf-archive@ietf.org; Mon, 31 May 2004 01:38:38 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BUfUX-0000tF-00; Mon, 31 May 2004 01:37:45 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BUfPy-0000EJ-Eg; Mon, 31 May 2004 01:33:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BUfGg-0007iY-1J
	for ietf@megatron.ietf.org; Mon, 31 May 2004 01:23:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA14946
	for <ietf@ietf.org>; Mon, 31 May 2004 01:23: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 1BUfGd-0004RW-QN
	for ietf@ietf.org; Mon, 31 May 2004 01:23:23 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUfFe-00047j-00
	for ietf@ietf.org; Mon, 31 May 2004 01:22:23 -0400
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx with esmtp (Exim 4.12) id 1BUfEd-0003WP-00
	for ietf@ietf.org; Mon, 31 May 2004 01:21:20 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.12.11/8.12.11) id i4V5KnUH000935
	for ietf@ietf.org env-from <vjs>;
	Sun, 30 May 2004 23:20:49 -0600 (MDT)
Date: Sun, 30 May 2004 23:20:49 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200405310520.i4V5KnUH000935@calcite.rhyolite.com>
To: ietf@ietf.org
References: <20040531125952.18baac6b.ietf@130c04165a5b40404e4440445758487a.nosense.org>
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

> From: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>

> > Yes, spam filtering can be quite effective.
>
> Not using spam filtering ... I don't like the chances of false
> positives or negatives.

Today either you filter spam, or you get practically no mail from
strangers.  If your address is exposed for legitimate mail from
strangers, then lots of spam will be sent your way.  At least 50% and
by some accounts more than 80% of all mail is spam.  If you get the
10 legitimate message/day typical of a non-technical user, and your
spam load is 80%, then you also receive 40 spam/day.  My various layers
of filters averaged 521 spam/day for the last 40 days.

Either your computers filter using blacklists, whitelists, various
content filters, and/or other mechanisms, or you filter spam manually.
40, not to mention 521 spam/day are too many to filter manually without
frequently overlooking legitimate mail.  Those are false positives.
Thus, if your mailbox is open to legitimate mail from strangers, then
you have false positives, whether they are human or computer errors.


> My idea is similar to the idea of abandoning a phone number if
> you get too many prank calls. Similar to abandoning a phone
> number, when I abandon an email address, I don't even see the
> spam traffic - I'm not filtering it out.

On the contrary, legitimate messages sent to your abandoned mailboxes
are false positives.  They are filtered out.


> > > I would find not be able to run my own MTA,
> > > unfortunately on a dynamically assigned IP ADSL service, as
> > > that is all I can afford, to be far more costly than the very
> > > negligable reduction in spam I would receive if TCP port 25
> > > was blocked by ISPs.
> > 
> > I cannot understand that as other than a demand that I
> > subsidize your Internet service.
> > 
> > If you think that everyone has the right to run their own MTAs,
> > why don't you insist that Full Internet Connectivity be free?
>
> I struggle to understand how you make such a dramatic jump in
> "position" (I can't think of a better way to describe it at the
> moment). I can't see the logical progression from being able to
> run an MTA, to getting Internet connectivity for free. 

I thought you were repeating the too familiar whine that it would be
Wrong and Evil to be forced to choose between paying for Full internet
Connectivity and having port 25 blocked.  The familiar claims from
others about unblocked port 25 for $30/month being a fundamental human
right of communication are irritating.  Those making those claims want
only a price they can afford, instead of the $0.00 price appropriate
for a fundamental human right.
    ................



} From: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>

} I'm just waiting for the next Outlook based (or alternatively, a
} socially engineered executable based) worm that uses legitimate
} email addresses and "legitimate" (in the sense of
} "legitimate because TCP port 25 is not blocked") MTAs to send out
} spam. 

That is such an obvious countermeasure that you must assume it it
probably is already in use.

}       Blocking TCP port 25 on dialup accounts (or any other
} Internet service) will have no effect in mitigating these types
} of attacks. 

That is mistaken.  Spam, worms, and viruses sent through ISP mail
systems can be filter.  I understand that worm and virus filtering is
quite effective, but don't really know.  Filtering spam from an ISP's
own customers can be extremely effective.  For example, an ISP can
rate-limit customers to 10 or 20 messages/day, and require customers
to make arrangements for higher rates.


Vernon Schryver    vjs@rhyolite.com

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


From ietf-bounces@ietf.org  Mon May 31 03:42: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 DAA03833
	for <ietf-archive@ietf.org>; Mon, 31 May 2004 03:42: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 1BUhRi-0002oJ-RT
	for ietf-archive@ietf.org; Mon, 31 May 2004 03:42:58 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUhQd-0002QM-00
	for ietf-archive@ietf.org; Mon, 31 May 2004 03:41:51 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BUhPb-0001iw-00; Mon, 31 May 2004 03:40:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BUh2a-0004nm-Dy; Mon, 31 May 2004 03:17:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BUgmr-0002Q4-S2
	for ietf@megatron.ietf.org; Mon, 31 May 2004 03: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 DAA01942
	for <ietf@ietf.org>; Mon, 31 May 2004 03:00:29 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BUgma-0004fC-Hj
	for ietf@ietf.org; Mon, 31 May 2004 03:00:28 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUgla-0004KV-00
	for ietf@ietf.org; Mon, 31 May 2004 02:59:27 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx with esmtp (Exim 4.12) id 1BUgkW-0003f7-00
	for ietf@ietf.org; Mon, 31 May 2004 02:58:20 -0400
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-5.cisco.com with ESMTP; 30 May 2004 23:57:13 -0700
X-BrightmailFiltered: true
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com
	[171.71.163.15])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id i4V6vjls017871;
	Sun, 30 May 2004 23:57:45 -0700 (PDT)
Received: from imail.cisco.com (imail.cisco.com [172.19.216.204])
	by mira-sjc5-e.cisco.com (MOS 3.4.5-GR) with ESMTP id APJ89288;
	Sun, 30 May 2004 23:57:44 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by imail.cisco.com (8.12.5/8.12.10) with ESMTP id i4V79JTw016730;
	Mon, 31 May 2004 00:09:19 -0700
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16570.55143.534703.347795@thomasm-u1.cisco.com>
Date: Sun, 30 May 2004 23:57:43 -0700 (PDT)
To: "Perry E. Metzger" <perry@piermont.com>
In-Reply-To: <873c5hr4xx.fsf@snark.piermont.com>
References: <83800000.1085775120@localhost>
	<200405301306.i4UD6juG015370@calcite.rhyolite.com>
	<5144465C-B242-11D8-903D-000A9571873E@guppylake.com>
	<873c5hr4xx.fsf@snark.piermont.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &, heK/V66p?[2!i|tVn,
	9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
	@RFNnJEg~WZ/(8<`5a), -7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,
	g">$%B!0w{W)qIhmwhye104zd bUcI'1!
X-IMAIL-SIG: v:"1"; h:"imail.cisco.com"; d:"cisco.com";
	t:"1085987360.130416"; x:"1086419360"; a:"rsa-sha1"; e:"Iw==";
	n:"zCnd+ByA23/7WMiIwaIZ7Ez3DplzVMdRKP138IXLOvBVeaRZ4yWEPclZ/2Mda"
	"s5Bs9RPWH0BGd3fx6j+txdOXarv4Y8kpMqTexCOMFlDmatpXDXfFj3VI9o4G7"
	"674gFTasaoPcvEfZCwcBgZD7T6sLZa3RTBUGzZqOshAMRpVek=";
	s:"LNsfLIvoiJYeBc54/cJlDmgGQpPNJepAquBtem/tkYMuZrBWwtJMz4ogEgP+t"
	"ldRxEF/oowEA79OFyKYc2YimpxIZdDkSyf6yd2eoRsj6O7gbwk1J4hWBOv70f"
	"AsE7aKLqFZjIyjMbQ4hZjWSXUy1BnckfrQkRZcyP/KC5VNiqg=";
	c:"From: Michael Thomas <mat@cisco.com>";
	c:"Date: Sun, 30 May 2004 23:57:43 -0700 (PDT)";
	c:"Subject: Re: spoofing email addresses"
X-IMAIL-VERIFY: s:"y"; v:"y"; r:"42"; h:"imail.cisco.com"
Content-Transfer-Encoding: 7bit
Cc: Nathaniel Borenstein <nsb@guppylake.com>, ietf@ietf.org,
        Vernon Schryver <vjs@calcite.rhyolite.com>
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Perry E. Metzger writes:
 > I think the easy solution is just to block port 25 

   You can stop right there. The rest is so much
   wishful thinking.

	   Mike

 > unless someone asks
 > for it to be opened. Average users have no idea what
 > port 25 does or even what TCP is, so they won't care.
 > 
 > Perry
 > 
 > _______________________________________________
 > Ietf mailing list
 > Ietf@ietf.org
 > https://www1.ietf.org/mailman/listinfo/ietf


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


From ietf-bounces@ietf.org  Mon May 31 03:48: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 DAA04300
	for <ietf-archive@ietf.org>; Mon, 31 May 2004 03:48: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 1BUhXR-0004x3-UL
	for ietf-archive@ietf.org; Mon, 31 May 2004 03:48:54 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUhWM-0004Z1-00
	for ietf-archive@ietf.org; Mon, 31 May 2004 03:47:47 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BUhVI-00049D-00; Mon, 31 May 2004 03:46:40 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BUhVI-0003aT-6Q; Mon, 31 May 2004 03:46:41 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BUhPf-0007wL-6S; Mon, 31 May 2004 03:40:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BUhNy-0007AD-Qg
	for ietf@megatron.ietf.org; Mon, 31 May 2004 03:39: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 DAA03291
	for <ietf@ietf.org>; Mon, 31 May 2004 03:38: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 1BUhNl-0001Ks-Tj
	for ietf@ietf.org; Mon, 31 May 2004 03:38:54 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUhMW-0000zc-00
	for ietf@ietf.org; Mon, 31 May 2004 03:37:37 -0400
Received: from 117.cust55.nsw.dsl.ozemail.com.au ([203.102.126.117]
	helo=nosense.org) by ietf-mx with esmtp (Exim 4.12)
	id 1BUhLr-0000YV-00
	for ietf@ietf.org; Mon, 31 May 2004 03:36:56 -0400
Received: from Dupy2.nosense.org (localhost.localdomain [127.0.0.1])
	by nosense.org (Postfix) with SMTP
	id B8B5A3F02A; Mon, 31 May 2004 17:06:23 +0930 (CST)
Date: Mon, 31 May 2004 17:06:23 +0930
From: Mark Smith <ietf@130c04165a5b40404e4440445758487a.nosense.org>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <20040531170623.3e14de2f.ietf@130c04165a5b40404e4440445758487a.nosense.org>
In-Reply-To: <200405310520.i4V5KnUH000935@calcite.rhyolite.com>
References: <20040531125952.18baac6b.ietf@130c04165a5b40404e4440445758487a.nosense.org>
	<200405310520.i4V5KnUH000935@calcite.rhyolite.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
Cc: ietf@ietf.org
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

On Sun, 30 May 2004 23:20:49 -0600 (MDT)
Vernon Schryver <vjs@calcite.rhyolite.com> wrote:

> > From: Mark Smith
> > <ietf@130c04165a5b40404e4440445758487a.nosense.org>
> 
> > > Yes, spam filtering can be quite effective.
> >
> > Not using spam filtering ... I don't like the chances of
> > false positives or negatives.
> 
> Today either you filter spam, or you get practically no mail
> from strangers.  If your address is exposed for legitimate mail
> from strangers, then lots of spam will be sent your way.  At
> least 50% and by some accounts more than 80% of all mail is
> spam.  If you get the 10 legitimate message/day typical of a
> non-technical user, and your spam load is 80%, then you also
> receive 40 spam/day.  My various layers of filters averaged 521
> spam/day for the last 40 days.
> 

My email addresses, eg this ietf one, are exposed to a lot of
strangers on a daily basis. I'm not getting any where near the
spam levels you suggest. In fact, since this ietf email account
has been subscribed to this IETF mailing list (2004-04-18), I
don't remember getting any spam to it at all.

I have another one for the IPv6 mailing list, and another one for
the Sylpheed MUA. I don't remember getting any spam to them
either.

I may have got some in the last couple of weeks and deleted it,
however, compared to the number of legimitate emails I receive
and then delete from each of these mailing lists, coping with
spam is less than a minor inconvenience. As I said, I can't
remember any.

> Either your computers filter using blacklists, whitelists,
> various content filters, and/or other mechanisms, or you filter
> spam manually. 40, not to mention 521 spam/day are too many to
> filter manually without frequently overlooking legitimate mail.
>  Those are false positives.
> Thus, if your mailbox is open to legitimate mail from
> strangers, then you have false positives, whether they are
> human or computer errors.
> 
> 
> > My idea is similar to the idea of abandoning a phone number
> > if you get too many prank calls. Similar to abandoning a
> > phone number, when I abandon an email address, I don't even
> > see the spam traffic - I'm not filtering it out.
> 
> On the contrary, legitimate messages sent to your abandoned
> mailboxes are false positives.  They are filtered out.
> 

Ok, I'd accept that.

Note that people I trust to send me email use a different
address. I'd tell it to you, but I don't know you well enough to
trust you with it ...

> 
> > > > I would find not be able to run my own MTA,
> > > > unfortunately on a dynamically assigned IP ADSL service,
> > > > as that is all I can afford, to be far more costly than
> > > > the very negligable reduction in spam I would receive if
> > > > TCP port 25 was blocked by ISPs.
> > > 
> > > I cannot understand that as other than a demand that I
> > > subsidize your Internet service.
> > > 
> > > If you think that everyone has the right to run their own
> > > MTAs, why don't you insist that Full Internet Connectivity
> > > be free?
> >
> > I struggle to understand how you make such a dramatic jump in
> > "position" (I can't think of a better way to describe it at
> > the moment). I can't see the logical progression from being
> > able to run an MTA, to getting Internet connectivity for
> > free. 
> 
> I thought you were repeating the too familiar whine that it
> would be Wrong and Evil to be forced to choose between paying
> for Full internet Connectivity and having port 25 blocked.  The
> familiar claims from others about unblocked port 25 for
> $30/month being a fundamental human right of communication are
> irritating.  Those making those claims want only a price they
> can afford, instead of the $0.00 price appropriate for a
> fundamental human right.
>     ................
> 
> 
> 
> } From: Mark Smith
> <ietf@130c04165a5b40404e4440445758487a.nosense.org>
> 
> } I'm just waiting for the next Outlook based (or
> alternatively, a} socially engineered executable based) worm
> that uses legitimate} email addresses and "legitimate" (in the
> sense of} "legitimate because TCP port 25 is not blocked") MTAs
> to send out} spam. 
> 
> That is such an obvious countermeasure that you must assume it
> it probably is already in use.
> 

I wasn't talking about a countermeasure. I'm talking about the
attack the spammers could come up with, once you prevent them
sending spam from, for example  dialup accounts, due to
outgoing TCP port 25 being blocked.

Block outgoing TCP port 25 on certain types of Internet access
effectively creates a low level "trusted" email infrastructure
ie. MTAs only being run by (supposably) competent ISPs or
organisations.

My point is that once that happens, spammers will then attempt to
exploit the trusted infrastructure, using techniques such as
taking advantages of flaws in scriptiable MUAs, using social
engineering attacks such as executable attachments, or attaching
to unprotected Wifi networks from a car in the street, and
sending spam via the "trusted" MTA that is inside the
organisation's firewall. 

> }       Blocking TCP port 25 on dialup accounts (or any other
> } Internet service) will have no effect in mitigating these
> types} of attacks. 
> 
> That is mistaken.  Spam, worms, and viruses sent through ISP
> mail systems can be filter.  I understand that worm and virus
> filtering is quite effective, but don't really know.  Filtering
> spam from an ISP's own customers can be extremely effective. 
> For example, an ISP can rate-limit customers to 10 or 20
> messages/day, and require customers to make arrangements for
> higher rates.
>

Would you want your ISP reading your false positives or
negatives private emails, to make up for the imperfections in
filtering software? I wouldn't.

I also wouldn't want to have to rely on them to do it in a timely
manner. My business might depend on it, and I'm sure I won't be
able to sue my ISP if I miss a business opportunity, as I'm
sure there would be an out clause in their terms of
service.

And finally, how do they know what is or isn't spam ? I wouldn't
want them making that judgement for me.

Regards,
Mark.

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


From ietf-bounces@ietf.org  Mon May 31 09:40: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 JAA20121
	for <ietf-archive@ietf.org>; Mon, 31 May 2004 09:40: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 1BUn1E-0003uk-ST
	for ietf-archive@ietf.org; Mon, 31 May 2004 09:40:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUn00-0003IP-00
	for ietf-archive@ietf.org; Mon, 31 May 2004 09:38:45 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BUmyX-0002NM-00; Mon, 31 May 2004 09:37:13 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BUmsD-0004uR-KI; Mon, 31 May 2004 09:30:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BUmnc-0004T3-DN
	for ietf@megatron.ietf.org; Mon, 31 May 2004 09:25: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 JAA19067
	for <ietf@ietf.org>; Mon, 31 May 2004 09:25:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BUmnb-0006LR-Oy
	for ietf@ietf.org; Mon, 31 May 2004 09:25:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUmmZ-0005xS-00
	for ietf@ietf.org; Mon, 31 May 2004 09:24:52 -0400
Received: from 206-169-2-196.gen.twtelecom.net ([206.169.2.196]
	helo=mail.optistreams.net) by ietf-mx with esmtp (Exim 4.12)
	id 1BUmlX-0005IO-00
	for ietf@ietf.org; Mon, 31 May 2004 09:23:47 -0400
Received: from [192.168.0.101] [68.42.70.186] by mail.optistreams.net with
	ESMTP (SMTPD32-8.04) id AC54239E0240; Mon, 31 May 2004 06:00:04 -0700
In-Reply-To: <200405310026.i4V0QX7u018576@calcite.rhyolite.com>
References: <E3D558B8-B28B-11D8-903D-000A9571873E@guppylake.com>
	<200405310026.i4V0QX7u018576@calcite.rhyolite.com>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <A9BABEFC-B305-11D8-903D-000A9571873E@guppylake.com>
Content-Transfer-Encoding: 7bit
From: Nathaniel Borenstein <nsb@guppylake.com>
Date: Mon, 31 May 2004 09:23:11 -0400
To: Vernon Schryver <vjs@calcite.rhyolite.com>
X-Mailer: Apple Mail (2.613)
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

On May 30, 2004, at 8:26 PM, Vernon Schryver wrote:

> I don't mind in the least if Mr. Borenstein has changed his mind but
> does not wish to say so.

To the best of my knowledge I haven't changed my mind about anything, 
but I'm done with this argument.  Anyone who chooses to re-read the 
thread will see that you, Vernon, are the one who keeps bringing up the 
issue of what people pay for Internet service.  I just don't care in 
this context, but you seem convinced that I do and that every comment I 
make is predicated upon the position *you* think I hold on pricing.  So 
you're not arguing with me, you're arguing with a straw man, and I've 
got better things to do.

For the record, I have no problem with charging extra for enabling port 
25, given the potential extra costs involved.  If I said anything to 
indicate otherwise, I apologize for the confusion.  I do object to most 
current blacklists, but my reasons have nothing to do with cost.  -- 
Nathaniel


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


From ietf-bounces@ietf.org  Mon May 31 16:15: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 QAA11907
	for <ietf-archive@ietf.org>; Mon, 31 May 2004 16:15: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 1BUtBe-0004GE-64
	for ietf-archive@ietf.org; Mon, 31 May 2004 16:15:10 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUtAd-0003s8-00
	for ietf-archive@ietf.org; Mon, 31 May 2004 16:14:08 -0400
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BUt9m-00038N-00; Mon, 31 May 2004 16:13:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BUt5U-0001UV-G9; Mon, 31 May 2004 16:08:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BUszI-0000t5-NO
	for ietf@megatron.ietf.org; Mon, 31 May 2004 16:02:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10856
	for <ietf@ietf.org>; Mon, 31 May 2004 16:02: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 1BUszH-0006jr-HE
	for ietf@ietf.org; Mon, 31 May 2004 16:02:23 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BUsxF-00062f-00
	for ietf@ietf.org; Mon, 31 May 2004 16:00:17 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx with esmtp (Exim 4.12) id 1BUswe-0005fM-00
	for ietf@ietf.org; Mon, 31 May 2004 15:59:41 -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 i4VJx61C098191
	for <ietf@ietf.org>; Mon, 31 May 2004 21:59:07 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v618)
In-Reply-To: <200405310520.i4V5KnUH000935@calcite.rhyolite.com>
References: <20040531125952.18baac6b.ietf@130c04165a5b40404e4440445758487a.nosense.org>
	<200405310520.i4V5KnUH000935@calcite.rhyolite.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <06756700-B33D-11D8-8F98-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Mon, 31 May 2004 21:59:29 +0200
To: ietf@ietf.org
X-Mailer: Apple Mail (2.618)
Content-Transfer-Encoding: 7bit
Subject: Re: spoofing email addresses
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Can this thread die, please?

On 31-mei-04, at 7:20, Vernon Schryver wrote:

>>> Yes, spam filtering can be quite effective.

>> Not using spam filtering ... I don't like the chances of false
>> positives or negatives.

[...]

> My various layers of filters averaged 521 spam/day for the last 40 
> days.

And how many false positives? Or don't you get to see these:

    ----- The following addresses had permanent fatal errors -----
<vjs@calcite.rhyolite.com>
     (reason: 553 5.3.0 go away)

Hanging up on people is pretty rude. You should at least give a reason.

> I thought you were repeating the too familiar whine that it would be
> Wrong and Evil to be forced to choose between paying for Full internet
> Connectivity and having port 25 blocked.

As I've said before: the fact that you apps guys can't get your act 
together isn't enough reason for me to do more work at layers 3 and 4. 
Stupid network, smart hosts, remember?

And again: please let this thread die. Even if blocking port 25 were a 
good idea it's no use as it needs to be done for 99%+ of all hosts 
connected to the internet to have any effect, and that's not going to 
happen any time soon. (Lots of people still don't do any anti-spoofing 
filtering even though that doesn't generate support calls and has been 
best practice for years.)


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


