From mailman-bounces@ietf.org  Sun Aug  1 05:33:10 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05821
	for <ietf-archive@ietf.org>; Sun, 1 Aug 2004 05:33:10 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BrCl1-0000Tu-Mm
	for ietf-archive@ietf.org; Sun, 01 Aug 2004 05:35:55 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BrCGA-0005Lk-Is
	for ietf-archive@ietf.org; Sun, 01 Aug 2004 05:04:02 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@ietf.org
To: ietf-archive@ietf.org
X-No-Archive: yes
Message-ID: <mailman.3925.1091350872.10663.mailman@lists.ietf.org>
Date: Sun, 01 Aug 2004 05:01:12 -0400
Precedence: bulk
X-BeenThere: mailman@lists.ietf.org
X-Mailman-Version: 2.1.5
List-Id: Mailman site list <mailman.lists.ietf.org>
X-List-Administrivia: yes
Sender: mailman-bounces@ietf.org
Errors-To: mailman-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Content-Transfer-Encoding: 7bit

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

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

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

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

NOTE WELL:

Any submission to the IETF intended by the Contributor for publication
as all or part of an IETF Internet-Draft or RFC and any statement made
within the context of an IETF activity is considered an "IETF
Contribution". Such statements include oral statements in IETF
sessions, as well as written and electronic communications made at any
time or place, which are addressed to:

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

All IETF Contributions are subject to the rules of RFC 3667 and RFC
3668.

Statements made outside of an IETF session, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not IETF Contributions in the context
of this notice.

Please consult RFC 3667 for details.

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


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

Passwords for ietf-archive@ietf.org:

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

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


From mailman-bounces@mailman.isi.edu  Sun Aug  1 08:42:48 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18496
	for <ietf-archive@ietf.org>; Sun, 1 Aug 2004 08:42:48 -0400 (EDT)
Received: from gamma.isi.edu ([128.9.144.145])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BrFiZ-0002TQ-2K
	for ietf-archive@ietf.org; Sun, 01 Aug 2004 08:45:36 -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 i71CORi23688
	for <ietf-archive@ietf.org>; Sun, 1 Aug 2004 05:24:27 -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.2040.1091361877.9878.mailman@mailman.isi.edu>
Date: Sun, 01 Aug 2004 05:04:37 -0700
Precedence: bulk
X-BeenThere: mailman@mailman.isi.edu
X-Mailman-Version: 2.1.4
List-Id: Mailman site list <mailman.mailman.isi.edu>
X-List-Administrivia: yes
Sender: mailman-bounces@mailman.isi.edu
Errors-To: mailman-bounces@mailman.isi.edu
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: mailman-bounces@mailman.isi.edu
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
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-bounces@ietf.org  Sun Aug  1 11:32:14 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06613;
	Sun, 1 Aug 2004 11:32:14 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BrIMX-0004jq-P1; Sun, 01 Aug 2004 11:35:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BrI6N-0003rQ-9C; Sun, 01 Aug 2004 11:18:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BrHzz-0000ek-BJ
	for ietf@megatron.ietf.org; Sun, 01 Aug 2004 11:11:43 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05507
	for <ietf@ietf.org>; Sun, 1 Aug 2004 11:11:41 -0400 (EDT)
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BrI2f-0004R8-6A
	for ietf@ietf.org; Sun, 01 Aug 2004 11:14:29 -0400
Received: from bbprime (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id i71FAuN06960;
	Sun, 1 Aug 2004 08:10:56 -0700
Date: Sun, 1 Aug 2004 08:10:55 -0700
From: Dave Crocker <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <562203147.20040801081055@brandenburg.com>
To: Aaron Falk <falk@ISI.EDU>
In-Reply-To: <5E94267C-DC08-11D8-9C46-000A95DBDB84@isi.edu>
References: <5B3144E8-DACD-11D8-9C46-000A95DBDB84@isi.edu>
	<19BD78A2-DB4A-11D8-A54A-000A95CD987A@muada.com>
	<D56BFBF597F94C89784423A4@[10.0.0.2]>
	<6.1.1.1.2.20040721170526.05493b28@mira-sjc5-b.cisco.com>
	<20040722120658.GR26441@login.ecs.soton.ac.uk>
	<31495.1090503031@marajade.sandelman.ottawa.on.ca>
	<5E94267C-DC08-11D8-9C46-000A95DBDB84@isi.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Reducing parallel meeting slots
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-Score: 0.8 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: 7bit

Aaron,

AF> Perhaps we should raise the bar on what it takes to get a slot at the 
AF> IETF meeting.  For example, try to come up with some objective criteria 
AF> for what deserves a 1hr slot, 2hrs, multiple, etc.


Although there are some exceptions, we generally treat IETF resources as
being free.  Since they are in fact very expensive and often are very
scarce, I think that any effort to do better resource allocation would
be very helpful for IETF productivity.

Certainly this should include productivity requirements for getting
meeting slots.  Rather than trying to create more slots (more days or
more simultaneous meetings) we should be looking for ways to REDUCE the
number of parallel (conflicting) meetings.


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


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


From ietf-bounces@ietf.org  Sun Aug  1 11:53:48 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07539;
	Sun, 1 Aug 2004 11:53:48 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BrIhP-000519-Uj; Sun, 01 Aug 2004 11:56:37 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BrITc-000647-9Y; Sun, 01 Aug 2004 11:42:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BrIDA-0007O9-Cy
	for ietf@megatron.ietf.org; Sun, 01 Aug 2004 11:25:20 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06208
	for <ietf@ietf.org>; Sun, 1 Aug 2004 11:25:18 -0400 (EDT)
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BrIFp-0004dh-Gl
	for ietf@ietf.org; Sun, 01 Aug 2004 11:28:06 -0400
Received: from bbprime (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id i71FOiN07949;
	Sun, 1 Aug 2004 08:24:44 -0700
Date: Sun, 1 Aug 2004 08:24:42 -0700
From: Dave Crocker <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <665168045.20040801082442@brandenburg.com>
To: Fred Baker <fred@cisco.com>
In-Reply-To: <6.1.1.1.2.20040722174726.056f5208@mira-sjc5-b.cisco.com>
References: <5B3144E8-DACD-11D8-9C46-000A95DBDB84@isi.edu>
	<19BD78A2-DB4A-11D8-A54A-000A95CD987A@muada.com>
	<D56BFBF597F94C89784423A4@[10.0.0.2]>
	<6.1.1.1.2.20040721170526.05493b28@mira-sjc5-b.cisco.com>
	<20040722120658.GR26441@login.ecs.soton.ac.uk>
	<31495.1090503031@marajade.sandelman.ottawa.on.ca>
	<5E94267C-DC08-11D8-9C46-000A95DBDB84@isi.edu>
	<6.1.1.1.2.20040722174726.056f5208@mira-sjc5-b.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Content-Transfer-Encoding: 7bit
Cc: Aaron Falk <falk@ISI.EDU>, ietf@ietf.org
Subject: WG progress management
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-Score: 0.8 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Content-Transfer-Encoding: 7bit

Fred,

FB> IMHO, the charter of a working group is a contract-of-sorts to accomplish
FB> something. If a working group has no future milestones, I can't imagine why 
FB> it is meeting - at minimum, it should be (IMHO) in the process of 
FB> rechartering (which is a milestone in its own right). I would like to see 
FB> working groups held to their chartered work plans, and rechartered if the 
FB> work-plan changes.

My sense is that there is rough consensus on the sentiments you express,
but this does not seem to translate into particular actions.

As you note, for example, we are still authorizing some pretty awful
charters.  In particular, they cannot serve as wg project management
reference documents.  That is, they do not contain information that
really permits assessing focus and scope (what the working group must
work on) or progress (whether it is being productive in satisfying its
goals.)


FB> I will only tell you how I found them. I went to
FB> see whether there was an obvious example of a working group that was 
FB> outside its charter.

So the first idea, for translating into action, is to do an audit of the
charter regularly. This is not a new idea, of course, but such reviews
do not seem to be getting done. If this is going to be a serious tool, I
think it needs to be done by more than Area Directors. We need to have
review and enforcement of milestones be a priority WITHIN working
groups.

It is not that participants cannot raise such concerns now, it is that
they generally don't.  In other words, we need a cultural change that
encourage participants -- most especially chairs -- to raise progress
questions and get them resolved.


FB> I went to www.ietf.org, clicked on "working groups", 
FB> clicked on the area at the top of the list, and clicked on the first 
FB> working group under that area. This working group has two milestones that 
FB> are past and a number that are future, and no notation of whether they have 
FB> met their milestones or not. I then clicked on the second working group in 
FB> that area, and found the following:


FB> Consider the dates: what is the argument for this WG meeting? Someone needs
FB> to sit down and very specifically ask "what in the world is happening? Is 
FB> this WG moribund and in need of some merciful person to put it out of its 
FB> misery? If not, what is the real plan for its future?"

YES!

The simplistic criteria for getting a slot should be:

    -  What will be accomplished at the meeting?

    -  How will that constitute wg progress?

    -  Why should anyone believe the meeting will accomplish its goals?

Unfortunately, all 3 questions are essential.


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


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


From ietf-bounces@ietf.org  Sun Aug  1 13:21:05 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12040;
	Sun, 1 Aug 2004 13:21:05 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BrK3v-0006Ah-WB; Sun, 01 Aug 2004 13:23:56 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BrJmZ-0005v5-FE; Sun, 01 Aug 2004 13:05:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BrJdm-0008BJ-Ma
	for ietf@megatron.ietf.org; Sun, 01 Aug 2004 12:56:54 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10555
	for <ietf@ietf.org>; Sun, 1 Aug 2004 12:56:51 -0400 (EDT)
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BrJgT-0005r3-IS
	for ietf@ietf.org; Sun, 01 Aug 2004 12: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 i71GvlSq035944;
	Sun, 1 Aug 2004 18:57:47 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <562203147.20040801081055@brandenburg.com>
References: <5B3144E8-DACD-11D8-9C46-000A95DBDB84@isi.edu>
	<19BD78A2-DB4A-11D8-A54A-000A95CD987A@muada.com>
	<D56BFBF597F94C89784423A4@[10.0.0.2]>
	<6.1.1.1.2.20040721170526.05493b28@mira-sjc5-b.cisco.com>
	<20040722120658.GR26441@login.ecs.soton.ac.uk>
	<31495.1090503031@marajade.sandelman.ottawa.on.ca>
	<5E94267C-DC08-11D8-9C46-000A95DBDB84@isi.edu>
	<562203147.20040801081055@brandenburg.com>
Mime-Version: 1.0 (Apple Message framework v618)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <C20C5AB0-E3DB-11D8-B13E-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Sun, 1 Aug 2004 18:56:40 +0200
To: Dave Crocker <dcrocker@brandenburg.com>
X-Mailer: Apple Mail (2.618)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: Reducing parallel meeting slots
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-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Content-Transfer-Encoding: 7bit

On 1-aug-04, at 17:10, Dave Crocker wrote:

> Although there are some exceptions, we generally treat IETF resources 
> as
> being free.  Since they are in fact very expensive and often are very
> scarce, I think that any effort to do better resource allocation would
> be very helpful for IETF productivity.

This may or may not be the case, but:

> Certainly this should include productivity requirements for getting
> meeting slots.  Rather than trying to create more slots (more days or
> more simultaneous meetings) we should be looking for ways to REDUCE the
> number of parallel (conflicting) meetings.

...it doesn't address the problem of overlapping sessions. Sessions are 
going to overlap. This is only a problem when people want to attend 
more than one during any particular slot. The fact that people want to 
attend a session makes it highly unlikely that such a session is so 
unproductive that scrapping it alltoghether would be better. (I don't 
believe IETFers are so stupid they keep showing up for unproductive 
sessions.)


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


From ietf-bounces@ietf.org  Sun Aug  1 13:22:47 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12188;
	Sun, 1 Aug 2004 13:22:47 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BrK5Z-0006Da-Bs; Sun, 01 Aug 2004 13:25:37 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BrJnk-0007ME-Ti; Sun, 01 Aug 2004 13:07:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BrJhs-0002Hi-1H
	for ietf@megatron.ietf.org; Sun, 01 Aug 2004 13:01:08 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10699
	for <ietf@ietf.org>; Sun, 1 Aug 2004 13:01:05 -0400 (EDT)
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BrJkZ-0005tp-2U
	for ietf@ietf.org; Sun, 01 Aug 2004 13:03:55 -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 i71H2DSq036018;
	Sun, 1 Aug 2004 19:02:14 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <Pine.LNX.4.60.0407251132120.32094@twin.uoregon.edu>
References: <Pine.LNX.4.60.0407251132120.32094@twin.uoregon.edu>
Mime-Version: 1.0 (Apple Message framework v618)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <6101DCA8-E3DC-11D8-B13E-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Sun, 1 Aug 2004 19:01:06 +0200
To: ietf-broadcast@lists.uoregon.edu
X-Mailer: Apple Mail (2.618)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: ietf-broadcast: Current plan for IETF-60
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-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Content-Transfer-Encoding: 7bit

On 25-jul-04, at 20:39, Joel Jaeggli wrote:

> Coverage has been expanded from 2 to 4 rooms (meeting wise the are 6-7
> rooms in use at all times during the day), as soon as we have a final
> schedule we'll know which ones they are...

In the agenda there are between zero and three sessions per slot marked 
for multicast. Is this correct?


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


From ietf-bounces@ietf.org  Sun Aug  1 15:06:56 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16881;
	Sun, 1 Aug 2004 15:06:56 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BrLiM-0007Uq-NB; Sun, 01 Aug 2004 15:09:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BrLL7-0001Id-FU; Sun, 01 Aug 2004 14:45:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BrL72-0002vQ-9r
	for ietf@megatron.ietf.org; Sun, 01 Aug 2004 14:31:12 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14883
	for <ietf@ietf.org>; Sun, 1 Aug 2004 14:31:09 -0400 (EDT)
Received: from av1-2-sn3.vrr.skanova.net ([81.228.9.106])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BrL9j-00070L-72
	for ietf@ietf.org; Sun, 01 Aug 2004 14:34:00 -0400
Received: by av1-2-sn3.vrr.skanova.net (Postfix, from userid 502)
	id 93BF737E45; Sun,  1 Aug 2004 20:30:38 +0200 (CEST)
Received: from smtp1-2-sn3.vrr.skanova.net (smtp1-2-sn3.vrr.skanova.net
	[81.228.9.178]) by av1-2-sn3.vrr.skanova.net (Postfix) with ESMTP
	id 84AA637E44; Sun,  1 Aug 2004 20:30:38 +0200 (CEST)
Received: from shiraz.levkowetz.com (h195n1fls311o871.telia.com
	[213.64.174.195])
	by smtp1-2-sn3.vrr.skanova.net (Postfix) with ESMTP id 3E0553800E;
	Sun,  1 Aug 2004 20:30:38 +0200 (CEST)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.34)
	id 1BrL6T-00072m-Ov; Sun, 01 Aug 2004 20:30:38 +0200
Message-ID: <410D36CA.7000509@levkowetz.com>
Date: Sun, 01 Aug 2004 11:30:34 -0700
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla Thunderbird 0.7.1 (Macintosh/20040626)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Simon Leinen <simon@limmat.switch.ch>
References: <200407301745.i6UHjgZ28225@boreas.isi.edu>
	<aa8ycyn4u6.fsf@diotima.switch.ch>
In-Reply-To: <aa8ycyn4u6.fsf@diotima.switch.ch>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: 7bit
Cc: Aaron Falk <falk@ISI.EDU>, ietf@ietf.org, Mark Allman <mallman@icir.org>,
        Bill Manning <bmanning@ISI.EDU>
Subject: Re: survey on Friday IETF sessions
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-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Content-Transfer-Encoding: 7bit

Simon Leinen wrote:

>>this error could be due to the fact that I did not attend Seoul but
>>did attned MPLS and will attend SD. [...]
>>    
>>
>
>maybe not - I also got such an error, although I did attend both
>IETF58 and 59.  Looks like a file permission problem.
>  
>
It was a file permission problem, caused by a broken install script 
which munged a
heap of file permissions.  Occured just a couple of days ago, so 
shouldn't be the reason for the
response numbers.  If you look at the "Responses over time" page, it's 
pretty clear that the
response numbers have already petered out some time ago.

Anyway, the problem is fixed now.

    Henrik


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


From ietf-bounces@ietf.org  Sun Aug  1 15:45:20 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20691;
	Sun, 1 Aug 2004 15:45:19 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BrMJV-0008EN-8P; Sun, 01 Aug 2004 15:48:10 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BrMEj-00070Z-H8; Sun, 01 Aug 2004 15:43:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BrM3z-0002IR-U8
	for ietf@megatron.ietf.org; Sun, 01 Aug 2004 15:32:08 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19019
	for <ietf@ietf.org>; Sun, 1 Aug 2004 15:32:04 -0400 (EDT)
Received: from darkwing.uoregon.edu ([128.223.142.13] ident=root)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BrM6h-0007tm-AB
	for ietf@ietf.org; Sun, 01 Aug 2004 15:34:56 -0400
Received: from twin.uoregon.edu (twin.uoregon.edu [128.223.214.27])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i71JW4aH015012
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); 
	Sun, 1 Aug 2004 12:32:04 -0700 (PDT)
Date: Sun, 1 Aug 2004 12:32:04 -0700 (PDT)
From: Joel Jaeggli <joelja@darkwing.uoregon.edu>
X-X-Sender: joelja@twin.uoregon.edu
To: ietf-broadcast@lists.uoregon.edu
In-Reply-To: <6101DCA8-E3DC-11D8-B13E-000A95CD987A@muada.com>
Message-ID: <Pine.LNX.4.60.0408011230420.17397@twin.uoregon.edu>
References: <Pine.LNX.4.60.0407251132120.32094@twin.uoregon.edu>
	<6101DCA8-E3DC-11D8-B13E-000A95CD987A@muada.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: ietf@ietf.org
Subject: Re: ietf-broadcast: Current plan for IETF-60
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-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a

On Sun, 1 Aug 2004, Iljitsch van Beijnum wrote:

> On 25-jul-04, at 20:39, Joel Jaeggli wrote:
>
>> Coverage has been expanded from 2 to 4 rooms (meeting wise the are 6-7
>> rooms in use at all times during the day), as soon as we have a final
>> schedule we'll know which ones they are...
>
> In the agenda there are between zero and three sessions per slot marked for 
> multicast. Is this correct?

no it isn't. a more accurate schedule will be forthcoing as soon as I know 
what the score is...

joelja


-- 
-------------------------------------------------------------------------- 
Joel Jaeggli  	       Unix Consulting 	       joelja@darkwing.uoregon.edu 
GPG Key Fingerprint:     5C6E 0104 BAF0 40B0 5BD3 C38B F000 35AB B67F 56B2


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


From ietf-bounces@ietf.org  Sun Aug  1 19:24:40 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01747;
	Sun, 1 Aug 2004 19:24:40 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BrPjo-0002lZ-L4; Sun, 01 Aug 2004 19:27:33 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BrPYx-0004ZW-MP; Sun, 01 Aug 2004 19:16:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BrP98-0001bV-Tp
	for ietf@megatron.ietf.org; Sun, 01 Aug 2004 18:49:39 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29702
	for <ietf@ietf.org>; Sun, 1 Aug 2004 18:49:36 -0400 (EDT)
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BrPBr-000271-NM
	for ietf@ietf.org; Sun, 01 Aug 2004 18:52:29 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id D36AE61BD6; Mon,  2 Aug 2004 00:49:04 +0200 (CEST)
Received: from eikenes.alvestrand.no ([127.0.0.1])
	by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id 09737-10; Mon,  2 Aug 2004 00:49:03 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain
	[127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP
	id 9735561B7D; Mon,  2 Aug 2004 00:49:00 +0200 (CEST)
Date: Sun, 01 Aug 2004 15:48:23 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Aaron Falk <falk@ISI.EDU>, Michael Richardson <mcr@sandelman.ottawa.on.ca>
Message-ID: <909E7682EB8FFAF7D61FE0C0@B50854F0A9192E8EC6CDA126>
In-Reply-To: <5E94267C-DC08-11D8-9C46-000A95DBDB84@isi.edu>
References: <5B3144E8-DACD-11D8-9C46-000A95DBDB84@isi.edu>
	<19BD78A2-DB4A-11D8-A54A-000A95CD987A@muada.com>
	<D56BFBF597F94C89784423A4@[10.0.0.2]>
	<6.1.1.1.2.20040721170526.05493b28@mira-sjc5-b.cisco.com>
	<20040722120658.GR26441@login.ecs.soton.ac.uk>
	<31495.1090503031@marajade.sandelman.ottawa.on.ca>
	<5E94267C-DC08-11D8-9C46-000A95DBDB84@isi.edu>
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
Content-Transfer-Encoding: 7bit
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, ietf@ietf.org
Subject: Multiple meeting slots (Re: survey on Friday IETF sessions)
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-Score: 0.0 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
Content-Transfer-Encoding: 7bit



--On 22. juli 2004 10:55 -0700 Aaron Falk <falk@ISI.EDU> wrote:

> Perhaps we should raise the bar on what it takes to get a slot at the
> IETF meeting.  For example, try to come up with some objective criteria
> for what deserves a 1hr slot, 2hrs, multiple, etc.  This  might even
> nudge groups into making some additional progress  ("you can't have your
> meeting if you don't hit a/some milestones").

note - there aren't that many multiple-slot WGs.
Here's the list a quick scan came up with for this meeting:

avt--
dnsext--
geopriv-- (2x1h)
l2vpn-- (2x1h)
marid--
mip6--
nsis--
radext--
rohc-- (2x1h)
simple--
sip--
sipping--
v6ops--
xcon--
aaa-- (2x1h)
opsec-- (2x1h)

16, out of which 5 clearly are 2-hour requests that were put into 1-hour 
slots. So outlawing double-slot WGs altogehter gives us 11 more slots to 
play with.

That's more than adding a Thursday evening slot gives us - but it's not 
much..... if we want to do something that really reduces demand for slots, 
we have to force the "normal" size of a meeting down to 1 hour (somehow).

Personally, I'm as worried about this list:

adslmib
atompub
bridge
disman
ediint
fax
idmr
idwg
impp
iporpr
ipp
ipr
ipsec
ipseckey
ipsp
iptel
kink
l2tpext
megaco
mipshop
msgtrk
nntpext
openpgp
policy
pppext
problem
ptomaine
rap
sacred
seamoby
secsh
send
sigtran
snmpconf
spirits
ssm
stime
syslog
tewg
tls
trade
usefor
vpim
xmpp
zeroconf

It's the set of WGs that are (based on my quick count) NOT meeting in San 
Diego - 46 WGs. Some (like ipr and problem) are just waiting for their RFCs 
to pop out before closing down.... but others may not be....

Assuming no liability for possible errors.....

                 Harald




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


From ietf-bounces@ietf.org  Sun Aug  1 22:45:18 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22223;
	Sun, 1 Aug 2004 22:45:18 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BrSs0-0005Gf-Dk; Sun, 01 Aug 2004 22:48:13 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BrSZp-0006eO-5z; Sun, 01 Aug 2004 22:29:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BrSQU-0003nf-8d
	for ietf@megatron.ietf.org; Sun, 01 Aug 2004 22:19:46 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA18505
	for <ietf@ietf.org>; Sun, 1 Aug 2004 22:19:44 -0400 (EDT)
Received: from sentry.gw.tislabs.com
	([192.94.214.100] helo=nutshell.tislabs.com ident=firewall-user)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BrSTF-0004vF-2S
	for ietf@ietf.org; Sun, 01 Aug 2004 22:22:38 -0400
Received: (from uucp@localhost)
	by nutshell.tislabs.com (8.12.9/8.12.9) id i722GuEK007838
	for <ietf@ietf.org>; Sun, 1 Aug 2004 22:16:56 -0400 (EDT)
Received: from filbert.tislabs.com(10.66.1.10) by nutshell.tislabs.com via
	csmap (V6.0) id srcAAAfHaGtp; Sun, 1 Aug 04 22:16:54 -0400
Received: from localhost (weiler@localhost)
	by tislabs.com (8.12.9/8.12.9) with ESMTP id i722IQZg026446
	for <ietf@ietf.org>; Sun, 1 Aug 2004 22:18:26 -0400 (EDT)
Date: Sun, 1 Aug 2004 22:18:26 -0400 (EDT)
From: Samuel Weiler <weiler@tislabs.com>
X-X-Sender: weiler@filbert
To: ietf@ietf.org
Message-ID: <Pine.GSO.4.55.0408012216410.26200@filbert>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Subject: Re: IETF60: time needed for check-in at San Diego?  (fwd)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17

[I sent this last Tuesday and again this afternon from a
non-subscribed address, but it looks like the moderator didn't approve
it.  Sorry if you're seeing multiple copies.]

---------- Forwarded message ----------

> Clearly it seems that this is irrelevant (in general) to US people,
> they don't mind what they government do, good or bad, but negative
> for the rest of the world. So the rest of the world should also
> consider offering the same pain and wait time to the US nationals ?
> I'm not asking for it, but the question is an exercise for US
> nationals to understand our situation, and consider taking some
> actions.

Brazil already does this to US citizens, defending the action by
referring the the ancient diplomatic principle of reciprocity.  On the
other hand, there's something to be said for countries not lowering
themselves to the level of the US and instead treating visitors as
they want their own citizens to be treated when traveling abroad.

Beyond that, I'm not sure enough US citizens travel abroad for
reciprocity to be effective: only about 21% of US citizens hold
passports, and many of those probably got them for single trips --
reciprocal measures won't be seen by that many people.

Perhaps a more practical course of action is to refuse to attend
meetings in the US and put pressure on meeting organizers to avoiding
scheduling meetings in the US.  I hear Vancouver is lovely in July.

-- Sam

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


From ietf-bounces@ietf.org  Mon Aug  2 00:21:26 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA27802;
	Mon, 2 Aug 2004 00:21:26 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BrUN3-0006t0-Sl; Mon, 02 Aug 2004 00:24:22 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BrUBy-0005vj-6e; Mon, 02 Aug 2004 00:12:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BrU80-000454-EL
	for ietf@megatron.ietf.org; Mon, 02 Aug 2004 00:08:48 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA27270
	for <ietf@ietf.org>; Mon, 2 Aug 2004 00:08:45 -0400 (EDT)
Received: from iserver.sj.symbol.com ([63.145.233.51])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BrUAm-0006je-17
	for ietf@ietf.org; Mon, 02 Aug 2004 00:11:41 -0400
Received: from RUNABOUT (gwianameserver [157.235.95.252])
	by iserver.sj.symbol.com (8.12.8/8.12.8) with ESMTP id i723t6eW006826
	for <ietf@ietf.org>; Sun, 1 Aug 2004 20:55:06 -0700 (PDT)
Received: from SJ-DOM-MTA by RUNABOUT
	with Novell_GroupWise; Sun, 01 Aug 2004 21:08:03 -0700
Message-Id: <s10d5bb3.059@RUNABOUT>
X-Mailer: Novell GroupWise Internet Agent 6.0.4
Date: Sun, 01 Aug 2004 21:07:52 -0700
From: "Clint Chaplin" <cchaplin@sj.symbol.com>
To: <ietf@ietf.org>, <weiler@tislabs.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: quoted-printable
Subject: Re: IETF60: time needed for check-in at San Diego?  (fwd)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: quoted-printable

Vancouver is lovely any time of the year.  Been there in January, June, =
and November.

Clint (JOATMON) Chaplin
Wireless Security Advisor
Wireless Standards Lead
>>> Samuel Weiler <weiler@tislabs.com> 08/01/04 19:49 PM >>>
[I sent this last Tuesday and again this afternon from a
non-subscribed address, but it looks like the moderator didn't approve
it.  Sorry if you're seeing multiple copies.]

---------- Forwarded message ----------

> Clearly it seems that this is irrelevant (in general) to US people,
> they don't mind what they government do, good or bad, but negative
> for the rest of the world. So the rest of the world should also
> consider offering the same pain and wait time to the US nationals ?
> I'm not asking for it, but the question is an exercise for US
> nationals to understand our situation, and consider taking some
> actions.

Brazil already does this to US citizens, defending the action by
referring the the ancient diplomatic principle of reciprocity.  On the
other hand, there's something to be said for countries not lowering
themselves to the level of the US and instead treating visitors as
they want their own citizens to be treated when traveling abroad.

Beyond that, I'm not sure enough US citizens travel abroad for
reciprocity to be effective: only about 21% of US citizens hold
passports, and many of those probably got them for single trips --
reciprocal measures won't be seen by that many people.

Perhaps a more practical course of action is to refuse to attend
meetings in the US and put pressure on meeting organizers to avoiding
scheduling meetings in the US.  I hear Vancouver is lovely in July.

-- Sam

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

________________________________________________________________________
This email has been scanned for computer viruses.


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


From ietf-bounces@ietf.org  Mon Aug  2 11:05:55 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12336;
	Mon, 2 Aug 2004 11:05:55 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BreQm-0006o3-KM; Mon, 02 Aug 2004 11:08:56 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BreGB-0001Ya-Mo; Mon, 02 Aug 2004 10:57:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BqkbS-0001Cp-U1
	for ietf@megatron.ietf.org; Fri, 30 Jul 2004 23:32:10 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA19908
	for <ietf@ietf.org>; Fri, 30 Jul 2004 23:32:07 -0400 (EDT)
Received: from rwcrmhc11.comcast.net ([204.127.198.35])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bqkdp-00026L-6e
	for ietf@ietf.org; Fri, 30 Jul 2004 23:34:37 -0400
Received: from dfnjgl21 (c-24-1-99-5.client.comcast.net[24.1.99.5])
	by comcast.net (rwcrmhc11) with SMTP id <2004073103313301300bhd5re>
	(Authid: sdawkins@comcast.net); Sat, 31 Jul 2004 03:31:33 +0000
Message-ID: <3e7901c476ae$fed9f320$0200a8c0@DFNJGL21>
From: "Spencer Dawkins" <spencer@mcsr-labs.org>
To: <ietf@ietf.org>
References: <D6B102EB643A6E67C4FC39C2@[10.0.0.9]><4.3.2.7.2.20040730092746.01a4f3e0@mailhost.iprg.nokia.com>
	<525291F319CF8E84A3FE89BE@B50854F0A9192E8EC6CDA126>
Date: Fri, 30 Jul 2004 22:32:23 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 02 Aug 2004 10:57:53 -0400
Subject: Re: Naming convention for a WG I-D that returns to
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Spencer Dawkins <spencer@mcsr-labs.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: 7bit

> I don't know whether stopping "manyfolks" is right or not.

Sigh. Are there Internet Drafts that matter, that *don't* have inputs
from "many folks"? and if so, why?

I could never decide whether this was more likely a pure-hearted
attempt at modesty or an evil-hearted attempt to demonstrate that
"many folks back this draft, so can we have a Proposed Standard now?"

I remember noticing manyfolks drafts during about the same timeframe
as Internet Drafts with so many "authors" they couldn't all be listed
on the front page, so I leaned more toward the latter theory.
Fortunately, this isn't included in the part of the universe I'm in
charge of, these days.

Spencer



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


From ietf-bounces@ietf.org  Mon Aug  2 11:09:59 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12502;
	Mon, 2 Aug 2004 11:09:59 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BreUm-0006sA-7g; Mon, 02 Aug 2004 11:13:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BreGC-0001ZA-Nd; Mon, 02 Aug 2004 10:57:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BrKBD-0000oc-5V
	for ietf@megatron.ietf.org; Sun, 01 Aug 2004 13:31:27 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12592
	for <ietf@ietf.org>; Sun, 1 Aug 2004 13:31:24 -0400 (EDT)
Received: from diotima.switch.ch ([130.59.4.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BrKDu-0006LL-55
	for ietf@ietf.org; Sun, 01 Aug 2004 13:34:14 -0400
Received: from diotima.switch.ch (localhost [127.0.0.1])
	by diotima.switch.ch (8.12.11/8.12.11) with ESMTP id i71HUhIq021227
	(version=TLSv1/SSLv3 cipher=EDH-DSS-DES-CBC3-SHA bits=168 verify=NO);
	Sun, 1 Aug 2004 19:30:46 +0200 (CEST)
Received: (from leinen@localhost)
	by diotima.switch.ch (8.12.11/8.12.11/Submit) id i71HUf20021226;
	Sun, 1 Aug 2004 19:30:41 +0200 (CEST)
To: Bill Manning <bmanning@ISI.EDU>
X-Face: 1Nk*r=:$IBBb8|TyRB'2WSY6u:BzMO7N)#id#-4_}MsU5?vTI?dez|JiutW4sKBLjp.l7, 
	F 7QOld^hORRtpCUj)!cP]gtK_SyK5FW(+o"!or:v^C^]OxX^3+IPd\z,
	@ttmwYVO7l`6OXXYR`
From: Simon Leinen <simon@limmat.switch.ch>
In-Reply-To: <200407301745.i6UHjgZ28225@boreas.isi.edu> (Bill Manning's
	message of "Fri, 30 Jul 2004 10:45:42 -0700 (PDT)")
References: <200407301745.i6UHjgZ28225@boreas.isi.edu>
Date: Sun, 01 Aug 2004 19:30:41 +0200
Message-ID: <aa8ycyn4u6.fsf@diotima.switch.ch>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (usg-unix-v)
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Mon, 02 Aug 2004 10:57:53 -0400
Cc: Henrik Levkowetz <henrik@levkowetz.com>, Aaron Falk <falk@ISI.EDU>,
        ietf@ietf.org, Mark Allman <mallman@icir.org>
Subject: Re: survey on Friday IETF sessions
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-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Content-Transfer-Encoding: quoted-printable

Bill Manning writes:
> perhaps the reason there has not been more participation in your survey is
> associated w/ the following:

> "A problem occurred in a Python script. Here is the sequence of
> function calls leading up to the error, in the order they occurred."

> this error could be due to the fact that I did not attend Seoul but
> did attned MPLS and will attend SD. [...]

maybe not - I also got such an error, although I did attend both
IETF58 and 59.  Looks like a file permission problem.

Regards,
--=20
Simon.

 /www/cgi-bin/pyht.py
  313 #                except:
  314 #                    cachefile =3D None
  315         include(filename)
  316 #            print "<!-- Cache out of date (cache: %s - dir: %s)  -->=
" % (timestr(filetime(cachename)), timestr(dirtime(".")))
  317 #            if not cachefile:
include =3D <function include>, filename =3D '/www/ietf/survey/attendance/i=
ndex.pyht'

 /www/cgi-bin/pyht.py in include(filename=3D'/www/ietf/survey/attendance/in=
dex.pyht')
  215=20
  216                     if string.find(code, "\n") > -1:
  217                         exec code in execglobals, execlocals
  218                     else:
  219                         res =3D eval(code, execglobals, execlocals)
code =3D '\nimport re, time, sys, string\n\nif "submit" in ...wresults("ind=
ex.survey", tally("index.survey"))\n\n', global execglobals =3D {'__builtin=
s__': <module '__builtin__' (built-in)>, 'args': {'attend-friday-afternoon'=
: 'maybe (depends on the meeting)', 'attend-friday-evening': 'maybe (depend=
s on the meeting)', 'attend-friday-morning': 'maybe (depends on the meeting=
)', 'contributor-58': 'I had no conflicts for groups I contributed to.', 'c=
ontributor-59': 'I had no conflicts for groups I contributed to.', 'how-sch=
edule': 'attend the whole meeting?', 'ietf58-arrival': 'Before Sunday', 'ie=
tf58-departure': 'Fri AM', 'ietf59-arrival': 'Sun AM', 'ietf59-departure': =
'Fri AM', ...}, 'basename': <function basename>, 'dirname': <function dirna=
me>, 'env': {'REDIRECT_UNIQUE_ID': 'QQ0nxNVArsMAAEZKlog', 'H...g', 'PATH_IN=
FO': '/survey/attendance/index.pyht'}, 'escape': <function <lambda>>, 'file=
text': <function filetext>, 'filetime': <function filetime>, 'form': FieldS=
torage(None, None, [MiniFieldStorage('surv...iFieldStorage('submit', 'Submi=
t Questionnaire')]), 'header': <function header>, ...}, execlocals =3D {'Ar=
ea': 'Attendance', 'Formname': '', '__name__': 'embedded-code-at-line-50', =
'area': 'attendance', 'base': 'index', 'datenow': '01 Aug 2004 17:26', 'ext=
': '.survey', 'filebase': 'index', 'filedate': <function filedate>, 'fileex=
t': '.pyht', ...}

 /home/www/subj/job/ietf/survey/attendance/<string>

IOError: [Errno 13] Permission denied: 'index-130.129.128.233.result'
      args =3D (13, 'Permission denied')
      errno =3D 13
      filename =3D 'index-130.129.128.233.result'
      strerror =3D 'Permission denied'=20


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


From ietf-bounces@ietf.org  Mon Aug  2 11:35:23 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13756;
	Mon, 2 Aug 2004 11:35:23 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BretK-0007Fp-42; Mon, 02 Aug 2004 11:38:25 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Brej6-00070x-Ot; Mon, 02 Aug 2004 11:27:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BreYu-0002UQ-35
	for ietf@megatron.ietf.org; Mon, 02 Aug 2004 11:17:16 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12866
	for <ietf@ietf.org>; Mon, 2 Aug 2004 11:17:14 -0400 (EDT)
Received: from darkwing.uoregon.edu ([128.223.142.13] ident=root)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Brebl-0006zx-Mi
	for ietf@ietf.org; Mon, 02 Aug 2004 11:20:15 -0400
Received: from twin.uoregon.edu (twin.uoregon.edu [128.223.214.27])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i72FH995023664
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT)
	for <ietf@ietf.org>; Mon, 2 Aug 2004 08:17:10 -0700 (PDT)
Date: Mon, 2 Aug 2004 08:17:09 -0700 (PDT)
From: Joel Jaeggli <joelja@darkwing.uoregon.edu>
X-X-Sender: joelja@twin.uoregon.edu
To: ietf@ietf.org
Message-ID: <Pine.LNX.4.60.0408020803290.23413@twin.uoregon.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Subject: multicast and unicast audio sources.
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-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22

The text based meeting agenda is here:

http://www.ietf.org/meetings/agenda_60.txt

We are covering a total of 4 rooms the first two with multicast video 
and unicast audio and the second two with just audio:

IETF 60 Channel 1 - Harbor Island II 
IETF 60 Channel 2 - Grand A Ballroom
IETF 60 Channel 3 - Harbor Island I Ballroom
IETF 60 Channel 4 - Grand C Ballroom

information on receiving the video and audio streams is available here:

http://videolab.uoregon.edu/events/ietf/ietf60.html

Meetings begin this morning at 0900 PDT 1600 GMT

-- 
-------------------------------------------------------------------------- 
Joel Jaeggli  	       Unix Consulting 	       joelja@darkwing.uoregon.edu 
GPG Key Fingerprint:     5C6E 0104 BAF0 40B0 5BD3 C38B F000 35AB B67F 56B2


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


From ietf-bounces@ietf.org  Mon Aug  2 13:55:57 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22258;
	Mon, 2 Aug 2004 13:55:57 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Brh5N-0001AQ-UL; Mon, 02 Aug 2004 13:58:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Brgo0-0005b4-Bd; Mon, 02 Aug 2004 13:41:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BrgWp-0007A4-EE
	for ietf@megatron.ietf.org; Mon, 02 Aug 2004 13:23:15 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20337
	for <ietf@ietf.org>; Mon, 2 Aug 2004 13:23:14 -0400 (EDT)
Received: from mailout1.samsung.com ([203.254.224.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BrgZi-0000at-32
	for ietf@ietf.org; Mon, 02 Aug 2004 13:26:15 -0400
Received: from custom-daemon.mailout1.samsung.com by mailout1.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I1T00201XLIQR@mailout1.samsung.com> for ietf@ietf.org; Tue,
	03 Aug 2004 02:22:30 +0900 (KST)
Received: from ep_ms3_bk (mailout1.samsung.com [203.254.224.24])
	by mailout1.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I1T0053SXLI7Y@mailout1.samsung.com> for ietf@ietf.org;
	Tue, 03 Aug 2004 02:22:30 +0900 (KST)
Received: from ep_spt01 (ms3.samsung.com [203.254.225.112])
	by ms3.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun
	23
	2003)) with ESMTP id <0I1T00GQ7XLIEJ@ms3.samsung.com> for ietf@ietf.org;
	Tue, 03 Aug 2004 02:22:30 +0900 (KST)
Content-return: prohibited
Date: Mon, 02 Aug 2004 17:22:37 +0000 (GMT)
From: PARK SOO HONG <soohong.park@samsung.com>
X-Sender: =?euc-kr?B?U2Ftc3VuZyBFbGVjdHJvbmljc6HnTW9iaQ==?=
	=?euc-kr?B?bGUgUGxhdGZvcm0gTGFioedFbmdpbmVlcg==?=
To: ietf@ietf.org
Message-id: <0I1T00GQ8XLIEJ@ms3.samsung.com>
MIME-version: 1.0
X-Priority: 3
Msgkey: 20040802172216059@soohong.park
X-MTR: 20040802172216059@soohong.park
X-EPLocale: en_US.euc-kr
X-EPWebmail-Msg-Type: personal
X-EPWebmail-Reply-Demand: 0
X-Generator: NamoMIME 1.1.0.14
X-Spam-Score: 2.2 (++)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Subject: <TITLE>Agenda of the 59th IETF</TITLE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: soohong.park@samsung.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>
Content-Type: multipart/mixed; boundary="===============0335918007=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 2.1 (++)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2

--===============0335918007==
Content-return: prohibited
Content-type: text/html; charset=euc-kr
Content-Transfer-Encoding: base64

PEhUTUw+PEhFQUQ+PE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVudD0ndGV4dC9o
dG1sOyBjaGFyc2V0PWV1Yy1rcic+Cjx0aXRsZT5TYW1zdW5nIEVudGVycHJpc2UgUG9ydGFsIG15
U2luZ2xlPC90aXRsZT4KPHN0eWxlPiBQLCBsaSB7Zm9udC1mYW1pbHk6sby4ssO8LCBhcmlhbDsg
Zm9udC1zaXplOjlwdDsgbWFyZ2luLXRvcDowcHg7bWFyZ2luLWJvdHRvbTowcHg7fTwvc3R5bGU+
CjwvSEVBRD4KPEJPRFk+PHA+DQombmJzcDsNCjxwPkN1cnJlbnQgYWdlbmRhXzYwLmh0bWwgYXBw
ZWFycyAmcXVvdDtBZ2VuZGEgb2YgdGhlIDU5dGggSUVURiZxdW90OyBvbiB0b3AgDQpvZiBJRS48
L3A+DQo8cD4mbmJzcDs8L3A+DQo8cD4mbHQ7VElUTEUmZ3Q7QWdlbmRhIG9mIHRoZSA1OXRoIElF
VEYmbHQ7L1RJVExFJmd0OzwvcD4NCjxwPiZuYnNwOzwvcD4NCjxwPiZuYnNwOzwvcD4NCjxwPiZu
YnNwOzwvcD4NCjxwPlJlZ2FyZHMNCg0KICAgDQo8L3A+DQo8cD4mbmJzcDs8L3A+DQo8cD5EYW5p
ZWwgKFNvb2hvbmcgRGFuaWVsIFBhcmspDQo8L3A+DQo8cD5Nb2JpbGUgUGxhdGZvcm0gTGFib3Jh
dG9yeS4gU0FNU1VORyBFbGVjdHJvbmljczwvcD48L0JPRFk+PC9IVE1MPg==




--===============0335918007==
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

--===============0335918007==--


From ietf-bounces@ietf.org  Mon Aug  2 17:41:34 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07240;
	Mon, 2 Aug 2004 17:41:34 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Brkbj-00052f-RA; Mon, 02 Aug 2004 17:44:39 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BrkOX-00047h-Ha; Mon, 02 Aug 2004 17:30:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BrkHR-0000eX-EY
	for ietf@megatron.ietf.org; Mon, 02 Aug 2004 17:23:37 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06155
	for <ietf@ietf.org>; Mon, 2 Aug 2004 17:23:35 -0400 (EDT)
Received: from smtp.andrew.cmu.edu ([128.2.10.82])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BrkKM-0004jw-Ti
	for ietf@ietf.org; Mon, 02 Aug 2004 17:26:40 -0400
Received: from pwolf.WV.CC.CMU.EDU (CMU-100645.WV.CC.cmu.edu [128.2.75.115])
	(user=dim mech=GSSAPI (0 bits))
	by smtp.andrew.cmu.edu (8.12.10/8.12.10) with ESMTP id i72LNZbR012863
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT)
	for <ietf@ietf.org>; Mon, 2 Aug 2004 17:23:35 -0400
Date: Mon, 02 Aug 2004 17:23:37 -0400
From: David Murray <dim@andrew.cmu.edu>
To: ietf@ietf.org
Message-ID: <803D1A12A013185ED839126C@pwolf.WV.CC.CMU.EDU>
Originator-Info: login-token=Mulberry:01d+OhoNtMDuCsZyIpvB8ECgBRD9+5TCTsEQYEvg==;
	token_authority=postmaster@andrew.cmu.edu
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-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit
Subject: IETF Live Internet Broadcast (mbone ***NOT NEEDED*** to view)
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-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: 7bit

For the IETF meeting coming up, a number of events (including one for this 
group) will be broadcast publicly via a technology called ESM through 
Carnegie Mellon University.

To tune to any broadcasts, visit http://esm.cs.cmu.edu during the meetings 
(August 2-5) and click "Watch".

To participate, you need a system with the following requirements:
- A machine with Windows 98 or later, Linux, or Mac OS X
- You need to have a DSL, Cable Modem, or better connection (you do *not* 
need mbone to view this event)

Also, to chat on IRC:
server: irc.freenode.net
chatroom: #ESM

Thanks!
David Murray
CMU End System Multicast Group

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


From ietf-bounces@ietf.org  Mon Aug  2 18:09:24 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09152;
	Mon, 2 Aug 2004 18:09:24 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Brl2j-0005VR-BL; Mon, 02 Aug 2004 18:12:29 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BrkeI-0003yy-In; Mon, 02 Aug 2004 17:47:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BrkCc-0007J9-NC
	for ietf@megatron.ietf.org; Mon, 02 Aug 2004 17:18:38 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05919
	for <ietf@ietf.org>; Mon, 2 Aug 2004 17:18:36 -0400 (EDT)
Received: from uillean.fuaim.com ([206.197.161.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BrkFY-0004e6-8P
	for ietf@ietf.org; Mon, 02 Aug 2004 17:21:40 -0400
Received: from clairseach.fuaim.com (clairseach.fuaim.com [206.197.161.141])
	by uillean.fuaim.com (8.11.6/8.11.6) with ESMTP id i72LI6L27899
	for <ietf@ietf.org>; Mon, 2 Aug 2004 14:18:06 -0700
Received: from [130.129.16.92] (server-130-129-16-92.ietf60.ietf.org
	[130.129.16.92] (may be forged)) (authenticated bits=0)
	by clairseach.fuaim.com (8.12.8/8.12.8) with ESMTP id i72Lg54J014281
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO)
	for <ietf@ietf.org>; Mon, 2 Aug 2004 14:42:06 -0700
Mime-Version: 1.0 (Apple Message framework v618)
To: ietf@ietf.org
Message-Id: <53261EDD-E4C9-11D8-80F8-000A95C4C51A@daedelus.com>
From: Jim Martin <jim@daedelus.com>
Date: Mon, 2 Aug 2004 14:17:13 -0700
X-Mailer: Apple Mail (2.618)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5bfa71b340354e384155def5e70b13b
X-Mailman-Approved-At: Mon, 02 Aug 2004 17:47:11 -0400
Subject: IETF60 Network and Terminal Room Information
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="===============0526708922=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a4cdc653ecdd96665f2aa1c1af034c9e


--===============0526708922==
Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-243--642399091;
	protocol="application/pkcs7-signature"


--Apple-Mail-243--642399091
Content-Type: text/plain;
	charset=WINDOWS-1252;
	format=flowed
Content-Transfer-Encoding: quoted-printable

Gentlepeople,
	Attached below you will find the usage information for the =
network and=20
terminal room for the 60th IETF meeting. Sorry for the lateness of the=20=

post! If you have any questions or concerns, please see us at the help=20=

desk in the terminal room, or send a note to 60crew at daedelus dot=20
com.

	Enjoy!

	- Jim



							Network and =
Terminal Room Information
								IETF 60 =
=96 San Diego, Ca

Terminal Room
---------------------
The Terminal Room is located in Harbor Island III and is open 24 hours=20=

beginning at 4pm on Sunday August 1st and ending at 12 noon on Friday=20
August 6th. A help desk is being provided and will be manned from 8:00=20=

AM to 8:00 PM every day.  The room itself consists of approximately 150=20=

seats providing wired 10/100 Ethernet access and 110v North American=20
power ports.  There are also two duplex printers available.

Please note that there are 5 laptops available for general use.  They=20
are located at the front of the far left row of tables as you enter the=20=

Terminal Room.  Please do not change settings or install programs on=20
these machines without speaking to the help desk first.

When using the Ethernet connections in the Terminal Room, IPv4=20
addressing is provided via DHCP. Please use Dynamic Autoconfiguration=20
for IPv6. Unlike the wireless networks, IP multicast is enabled for=20
this network.

Network Basics
---------------------
The IETF 60 network connects to the Internet via a DS3 (45 Megabits)=20
with a backup wireless T1 (1.5M). The entire event is addressed out of=20=

the 130.129.0.0/16 block for IPv4 and 2001:240:5bf::/48 for IPv6. IPv4=20=

multicast is being provided via a GRE tunnel, and IPv6 is tunneled in=20
via IPv6 over IPv4.

Wireless
------------
An 802.11b wireless network is being provided liberally in the Sheraton=20=

Hotel. The areas being specifically covered are the meeting rooms and=20
hallways in the conference area, the lobby and bar area in the East=20
(main) building and the lobby in the West building.

To use this network, associate with the beaconed SSID of =93ietf60=94. =
IPv4=20
addressing is provided via DHCP, and IPv6 clients should use Dynamic=20
Autoconfiguration. Due to bandwidth concerns IP multicast is not=20
available on this network.

For those interested in a bit more link-layer security, a 128-bit WEP=20
enabled SSID is available. It must be manually configured, as there is=20=

no beacon for this network, The SSID is =93ietf60-wep=94 and the WEP key =
is=20
=93ietf60#ietf60=94 (Hex: 696574 6636302 369657 4663630 )

For substantially better link-layer security, we are experimenting with=20=

an 802.1X based mechanism.  When we are ready to have IETF participants=20=

join our experiment a note will be posted on the bulletin board in the=20=

conference area foyer and on the IETF list.

The proper operation of the wireless network requires the assistance of=20=

all users.  One of the most significant issues with wireless=20
performance in past IETF meetings has been wireless clients=20
automatically, or accidentally initiating "ad-hoc" networks that act as=20=

the official IETF wireless network, causing other users to associate=20
with false IETF wireless networks.  Therefore, please disable your=20
client's ability to create an ad-hoc network.  If you are using Windows=20=

XP or Mac OS X 10.3 to manage your wireless client, the instructions=20
are listed below. If you are using other systems, please do what ever=20
your particular wireless client management system requires to turn off=20=

ad-hoc networks.

Instructions for Mac OS X
   Open System Preferences -> Network -> Airport  and then un-check the=20=

box for "Allow this computer to create networks"

Instructions for Windows XP
   Open Properties -> wireless networks -> advanced and then select=20
"access point (infrastructure) networks only" and unselect=20
"automatically connect to non-preferred networks"

Printing
-----------
Two printers are located in the Terminal Room and are available to all=20=

IETF users. The printers themselves are HP LaserJet 4050TNs which are=20
Postscript capable and have the duplex option installed. The printers=20
are accessible via IPP, LPD, and Windows Printing (via samba).
=95	IPP - URI ipp://lpd.ietf60.ietf.org/printer
=95	cups - browsing enabled and should be discovered automatically
=95	Mac - under Printer Setup Utility use "HP 4050 TNs" under shared=20=

printers
=95	Windows XP users:
o	Open printer settings
o	Choose 'Add a printer' , then 'Next'
o	Change setting from 'Local' to 'Network' printer and choose =
'Next'
o	Change the option from 'browse' to 'Connect to this printer'
o	In the 'Name field type :   \\lpd.ietf60.ietf.org\printer        =
and=20
then choose 'Next'
o	Next an Add Printer Wizard dialogue box will appear, you need to=20=

select two things: In the left window (Manufacturer) select 'HP'. Then=20=

in the right hand window (Printers), scroll down and select 'HP=20
LaserJet 4050 Series PS', then hit 'Ok'


Services
------------
The following network services are provided:
=95	SMTP =96  {smtp,smtp1,smtp2}.ietf60.ietf.org
SMTP relay services are provided for users on the IETF network as well=20=

as the Sheraton guest room network.
=95	NTP - {ntp,ntp1,ntp2}.ietf60.ietf.org
Stratum 2 time service is provided via IPv4 unicast.
=95	Local IETF Website mirror =96 www.ietf.org
We have a local complete mirror of the IETF site. If you resolve=20
www.ietf.org using the onsite DNS servers, you will be directed to the=20=

local mirrors.

These services are being provided from both of the following servers:
130.129.16.8 (IPv4) or 2001:240:5bf:16:230:1bff:fead:4e40 (IPv6)
130.129.16.9 (IPv4) or 2001:240:5bf:16:230:1bff:fead:4e2c (IPv6)

Additionally, full recursive DNS service is being provided from=20
130.129.16.26 and 130.129.16.27. Our domain name is ietf60.ietf.org.

Thanks
----------
The terminal room and IETF network are made possible by the generous=20
contributions by a number of companies and by the tireless efforts of=20
our volunteer team. We also want to thank Greg Sheppard and Itojun for=20=

the IP multicast and IPv6 tunnels. If you see any of these people in=20
the halls, please be sure to thank them for all their work!

Contributors:				=09
Cisco Systems		=09
Juniper Networks	=09
MediaLive International	=09
Qualcomm		=09
Fluke Networks		=09
Priority Networks			=09
AirMagnet		=09
Red-M		=09
NetHere		=09
Netzwert AG	=09
Netcordia		=09
Infoblox=09

Volunteers:
Jim Martin
Bill Jensen
Karen O=92Donoghue
Geoff Horne
Chris Stradtman
Bill Burge
Chris Liljenstolpe
Helen Garey
Chris Elliott
Terry Slattery
Gerard Goubert
Ben Crosby
Jean-Pierre Letournel=09
Rafael Rizo
Fran=E7ois Marcier
Christopher Hessing
Mykhaylo Ryechkin
Scott Bloomquist=

--Apple-Mail-243--642399091
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Disposition: attachment;
	filename=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGFDCCAs0w
ggI2oAMCAQICAwvWUTANBgkqhkiG9w0BAQQFADBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhh
d3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt
YWlsIElzc3VpbmcgQ0EwHhcNMDQwMzA0MTEwNzAyWhcNMDUwMzA0MTEwNzAyWjBCMR8wHQYDVQQD
ExZUaGF3dGUgRnJlZW1haWwgTWVtYmVyMR8wHQYJKoZIhvcNAQkBFhBqaW1AZGFlZGVsdXMuY29t
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAvxMD20SnyHQptWSSDw4a2oGKyhWHXc8Q
5ATRVpIWRygqKRGYILFa76dk2RysvRS/sFmBx6Sn9pgQipzX3+eplcWHvisiANTIx/nsGtIkDFZT
8SklQ00Hro3S70zzwfk6qsUAIt+fSvjtl4yq0OSvX7wXdWa8wfwWGLOAvSWR5wBhAwNRdsVs4P9h
MWrjrwZ/Z+luu1a9h78ok6fyucjF99ucB1FrGVUt4T8GJefV+0pFiiw4D0OtXkBHEXmVCi3lG585
UnbQhcny2CEzuPDUDmrvO/BvVWdJnOMCcEM+uMLhdXiwhEAESrdbLNb2Ruwol30lfSLRF/4gHRo/
flo2JQIDAQABoy0wKzAbBgNVHREEFDASgRBqaW1AZGFlZGVsdXMuY29tMAwGA1UdEwEB/wQCMAAw
DQYJKoZIhvcNAQEEBQADgYEASGVJwLsdGU91cYeqjdXTu+z+4XICKni8RX3k3VfufcUtYeBKWoJ2
GmxOSTpOrp+YkWODheKoLL54IFhar4jKGI0Yn2jOklju8nooktX3qQBLAXFYGJiQnuo6lfjHrUTJ
ZExLVJGL0z6FPsaRg+9GPe63Gizqe5c384dP8S8bY4AwggM/MIICqKADAgECAgENMA0GCSqGSIb3
DQEBBQUAMIHRMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYDVQQHEwlD
YXBlIFRvd24xGjAYBgNVBAoTEVRoYXd0ZSBDb25zdWx0aW5nMSgwJgYDVQQLEx9DZXJ0aWZpY2F0
aW9uIFNlcnZpY2VzIERpdmlzaW9uMSQwIgYDVQQDExtUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwg
Q0ExKzApBgkqhkiG9w0BCQEWHHBlcnNvbmFsLWZyZWVtYWlsQHRoYXd0ZS5jb20wHhcNMDMwNzE3
MDAwMDAwWhcNMTMwNzE2MjM1OTU5WjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENv
bnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElz
c3VpbmcgQ0EwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAMSmPFVzVftOucqZWh5owHUEcJ3f
6f+jHuy9zfVb8hp2vX8MOmHyv1HOAdTlUAow1wJjWiyJFXCO3cnwK4Vaqj9xVsuvPAsH5/EfkTYk
KhPPK9Xzgnc9A74r/rsYPge/QIACZNenprufZdHFKlSFD0gEf6e20TxhBEAeZBlyYLf7AgMBAAGj
gZQwgZEwEgYDVR0TAQH/BAgwBgEB/wIBADBDBgNVHR8EPDA6MDigNqA0hjJodHRwOi8vY3JsLnRo
YXd0ZS5jb20vVGhhd3RlUGVyc29uYWxGcmVlbWFpbENBLmNybDALBgNVHQ8EBAMCAQYwKQYDVR0R
BCIwIKQeMBwxGjAYBgNVBAMTEVByaXZhdGVMYWJlbDItMTM4MA0GCSqGSIb3DQEBBQUAA4GBAEiM
0VCD6gsuzA2jZqxnD3+vrL7CF6FDlpSdf0whuPg2H6otnzYvwPQcUCCTcDz9reFhYsPZOhl+hLGZ
GwDFGguCdJ4lUJRix9sncVcljd2pnDmOjCBPZV+V2vf3h9bGCE6u9uo05RAaWzVNd+NWIXiC3CEZ
Nd4ksdMdRv9dX2VPMYIC5zCCAuMCAQEwaTBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3Rl
IENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWls
IElzc3VpbmcgQ0ECAwvWUTAJBgUrDgMCGgUAoIIBUzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcB
MBwGCSqGSIb3DQEJBTEPFw0wNDA4MDIyMTE3MTRaMCMGCSqGSIb3DQEJBDEWBBSn3Z9+zVq9S2ej
eUM006rF/2aWqjB4BgkrBgEEAYI3EAQxazBpMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3
dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1h
aWwgSXNzdWluZyBDQQIDC9ZRMHoGCyqGSIb3DQEJEAILMWugaTBiMQswCQYDVQQGEwJaQTElMCMG
A1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNv
bmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECAwvWUTANBgkqhkiG9w0BAQEFAASCAQBDlzdztuFnnkAX
e8otRwoK9+Cw5EAFYqxgR44fkm+MRH42r6sKOit0LmVZ6i72fYUEEhOPO9amZzCup5xJXdnmHZ4D
Z54LhaOLH8ucPyJVgi07qHUfJDRLcGnFmfxtF74popmpmPVPUmAs/PuCV+U8Md1ZueuMufsTfYdi
1aZ+gPcbyxreLHgmJGoxFORYGlqWrzLe8RB335ciVq1PE0eIi3FLAQDLL68P6ZoLem5aT4ZhftqA
m/IbikV9lldDpWyKU1mTVhNjFvgExl4BOmJiVHwXC+j7NcqBd375cK3PM6tYmUoMHptqiNuSXgsP
xR7jOa4GRTHh2HrukRnzUf0HAAAAAAAA

--Apple-Mail-243--642399091--



--===============0526708922==
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

--===============0526708922==--




From ietf-bounces@ietf.org  Mon Aug  2 18:32:55 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10960;
	Mon, 2 Aug 2004 18:32:55 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BrlPV-0005sH-F3; Mon, 02 Aug 2004 18:36:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Brl9R-0006Bh-Um; Mon, 02 Aug 2004 18:19:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Brfk1-0001Ur-Rv
	for ietf@megatron.ietf.org; Mon, 02 Aug 2004 12:32:49 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17350
	for <ietf@ietf.org>; Mon, 2 Aug 2004 12:32:47 -0400 (EDT)
From: avri@acm.org
Received: from tla.crepundia.net ([194.71.127.149] helo=report.tla-group.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Brfmt-0008EM-U7
	for ietf@ietf.org; Mon, 02 Aug 2004 12:35:49 -0400
Received: from [127.0.0.1] (report.tla-group.com [194.71.127.149])
	by report.tla-group.com (8.12.4/8.12.4) with ESMTP id i72GK8ep023633
	for <ietf@ietf.org>; Mon, 2 Aug 2004 18:20:09 +0200
Mime-Version: 1.0 (Apple Message framework v618)
Content-Transfer-Encoding: 7bit
Message-Id: <8C7897C2-E4A1-11D8-B3D0-000393CC2112@acm.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed
To: ietf@ietf.org
Date: Mon, 2 Aug 2004 09:32:30 -0700
X-Mailer: Apple Mail (2.618)
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 2870a44b67ee17965ce5ad0177e150f4
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 02 Aug 2004 18:19:24 -0400
Subject: Jabber at ietf60
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-Score: 0.3 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Content-Transfer-Encoding: 7bit

Are folks using it?

a.


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


From ietf-bounces@ietf.org  Mon Aug  2 18:33:20 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11027;
	Mon, 2 Aug 2004 18:33:20 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BrlPt-0005tE-RE; Mon, 02 Aug 2004 18:36:26 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Brl9S-0006CG-Tp; Mon, 02 Aug 2004 18:19:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BrjRa-00055f-VK
	for ietf@megatron.ietf.org; Mon, 02 Aug 2004 16:30:02 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02317
	for <ietf@ietf.org>; Mon, 2 Aug 2004 16:30:01 -0400 (EDT)
Received: from smtp.andrew.cmu.edu ([128.2.10.81])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BrjUS-0003up-MQ
	for ietf@ietf.org; Mon, 02 Aug 2004 16:33:05 -0400
Received: from pwolf.WV.CC.CMU.EDU (CMU-100645.WV.CC.cmu.edu [128.2.75.115])
	(user=dim mech=GSSAPI (0 bits))
	by smtp.andrew.cmu.edu (8.12.10/8.12.10) with ESMTP id i72KTukp019572
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT)
	for <ietf@ietf.org>; Mon, 2 Aug 2004 16:29:56 -0400
Date: Mon, 02 Aug 2004 16:29:58 -0400
From: David Murray <dim@andrew.cmu.edu>
To: ietf@ietf.org
Message-ID: <B073C2F3C2D9A5DD3FB04C52@pwolf.WV.CC.CMU.EDU>
Originator-Info: login-token=Mulberry:013IAVj0Dpgs8RBJYYIbx4+WXug84e6ZhRrnrzIw==;
	token_authority=postmaster@andrew.cmu.edu
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-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 02 Aug 2004 18:19:24 -0400
Subject: IETF Live Internet Broadcast (mbone ***NOT NEEDED*** to view)
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-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: 7bit

For the IETF meeting coming up, a number of events (including one for this 
group) will be broadcast publicly via a technology called ESM through 
Carnegie Mellon University.

To tune to any broadcasts, visit http://esm.cs.cmu.edu during the meetings 
(August 2-5) and click "Watch".

To participate, you need a system with the following requirements:
- A machine with Windows 98 or later, Linux, or Mac OS X
- You need to have a DSL, Cable Modem, or better connection (you do *not* 
need mbone to view this event)

Also, to chat on IRC:
server: irc.freenode.net
chatroom: #ESM

Thanks!
David Murray
CMU End System Multicast Group

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


From ietf-bounces@ietf.org  Mon Aug  2 18:49:31 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11978;
	Mon, 2 Aug 2004 18:49:31 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BrlfX-0006C1-Vy; Mon, 02 Aug 2004 18:52:37 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BrlYx-00034b-60; Mon, 02 Aug 2004 18:45:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BrlRX-0007Ns-2x
	for ietf@megatron.ietf.org; Mon, 02 Aug 2004 18:38:07 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11477
	for <ietf@ietf.org>; Mon, 2 Aug 2004 18:38:04 -0400 (EDT)
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BrlUT-00060u-1j
	for ietf@ietf.org; Mon, 02 Aug 2004 18:41:10 -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
	i72MbwnE023822
	for <ietf@ietf.org>; Mon, 2 Aug 2004 23:37:58 +0100 (BST)
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162])
	by magpie.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id XAA09199
	for <ietf@ietf.org>; Mon, 2 Aug 2004 23:37:55 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id i72Mbtl32294
	for ietf@ietf.org; Mon, 2 Aug 2004 23:37:55 +0100
Date: Mon, 2 Aug 2004 23:37:55 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: ietf@ietf.org
Message-ID: <20040802223754.GA31874@login.ecs.soton.ac.uk>
References: <8C7897C2-E4A1-11D8-B3D0-000393CC2112@acm.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8C7897C2-E4A1-11D8-B3D0-000393CC2112@acm.org>
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-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Subject: Re: Jabber at ietf60
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-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f

Sure, e.g.
http://www.xmpp.org/ietf-logs/multi6@ietf.xmpp.org/2004-08-02.html

On Mon, Aug 02, 2004 at 09:32:30AM -0700, avri@acm.org wrote:
> Are folks using it?
> 
> a.
> 
> 
> _______________________________________________
> 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  Tue Aug  3 11:59:27 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17165;
	Tue, 3 Aug 2004 11:59:27 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bs1kP-0003bX-KZ; Tue, 03 Aug 2004 12:02:42 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bs1dl-0002Dk-AJ; Tue, 03 Aug 2004 11:55:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bs1UW-0000y1-69
	for ietf@megatron.ietf.org; Tue, 03 Aug 2004 11:46:16 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16484
	for <ietf@ietf.org>; Tue, 3 Aug 2004 11:46:14 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from turing-police.cc.vt.edu ([128.173.14.107] ident=root)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bs1Xb-0003Nb-K2
	for ietf@ietf.org; Tue, 03 Aug 2004 11:49:28 -0400
Received: from turing-police.cc.vt.edu (IDENT:valdis@turing-police.cc.vt.edu
	[127.0.0.1])
	by turing-police.cc.vt.edu (8.13.1.Alpha0/8.13.1.Alpha0) with ESMTP id
	i738nYOt022352; Tue, 3 Aug 2004 04:49:34 -0400
Message-Id: <200408030849.i738nYOt022352@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.7.1 07/26/2004 with nmh-1.0.4+dev
To: salm@servanttechnology.com
In-Reply-To: Your message of "Sat, 31 Jul 2004 09:10:24 EDT."
	<410B9A40.3040800@servanttechnology.com> 
References: <D6B102EB643A6E67C4FC39C2@[10.0.0.9]>
	<4.3.2.7.2.20040730092746.01a4f3e0@mailhost.iprg.nokia.com>
	<525291F319CF8E84A3FE89BE@B50854F0A9192E8EC6CDA126>
	<6.1.2.0.2.20040731110208.029b7730@mail.jefsey.com>
	<410B7C94.1030207@servanttechnology.com>
	<6.1.2.0.2.20040731142932.0280a050@mail.jefsey.com>
	<410B9A40.3040800@servanttechnology.com>
Mime-Version: 1.0
Date: Tue, 03 Aug 2004 04:49:33 -0400
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: "JFC \(Jefsey\) Morfin" <jefsey@jefsey.com>, ietf@ietf.org
Subject: Re: Naming convention for a WG I-D that returns to 
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="===============0658012265=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135

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

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

On Sat, 31 Jul 2004 09:10:24 EDT, Sal Mangiapane said:
> > Thank you. I was also looking for an RFC - if any -which documents why. 
> >
> There is RFC3552 which is the Security Considerations Best Practices but 
> it doesn't answer the WHY question.

At the risk of stating the obvious....

Anybody who actually reads rfc3552 all the way through, and still doesn't
understand *why* they should do a 'Security Considerations' analysis of their
new protocol, should be summarily judged as being too security-clueless to
write said section of their draft. (If anything, reading it should make you
wonder "Where's the woodpeckers, already?" (*))

And as a less obvious security-meta-consideration:

A protocol designed by (or with the assistance of) somebody security-clued is
probably in good shape, and no major surprises will likely be found while
writing up the Security Considerations (yes, there may be holes and weaknesses,
but you already *knew* that).  A protocol designed by somebody not very
security-clued but at least security-aware may still be flawed, but hopefully
*some* thought has been put into the matter.  A protocol designed by the
security-unaware is almost certain to have fatal flaws ("Authentication???
That's important?" ;)

(*) Woodpeckers - "If carpenters built buildings the way programmers write
software, the first woodpecker that came along would destroy civilization".
Fortunately, so far all the malware we've seen has been odd mutant woodpeckers
without well-formed beaks - it's only a few lines of code difference between
"Warhol Worm" and the cyberspace equivalent of Drexler's grey goo....


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

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

iD8DBQFBD1GccC3lWbTT17ARAijiAKCxsZbdlHTew0FWIoPei6qXq+koSQCgpTKP
LFV4mn6M4aBfF1XHMBKM50Y=
=gRAZ
-----END PGP SIGNATURE-----

--==_Exmh_899848512P--


--===============0658012265==
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

--===============0658012265==--



From ietf-bounces@ietf.org  Tue Aug  3 13:19:46 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23279;
	Tue, 3 Aug 2004 13:19:46 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bs309-0005FW-HH; Tue, 03 Aug 2004 13:23:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bs2lU-0005Yd-HE; Tue, 03 Aug 2004 13:07:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bs2e5-0004P7-Ve
	for ietf@megatron.ietf.org; Tue, 03 Aug 2004 13:00:13 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21759
	for <ietf@ietf.org>; Tue, 3 Aug 2004 13:00:11 -0400 (EDT)
Received: from sklave3.rackland.de ([213.133.101.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bs2hB-0004pn-T9
	for ietf@ietf.org; Tue, 03 Aug 2004 13:03:27 -0400
Received: from sputnik (uucp@localhost)
	by sklave3.rackland.de (8.12.10/8.12.10/Debian-1) with BSMTP id
	i73H057T016693 for ietf@ietf.org; Tue, 3 Aug 2004 19:00:05 +0200
Received: (from hadmut@localhost)
	by sputnik.mobil.danisch.de (8.12.11/8.12.11/Debian-5) id
	i73GxlBc003975 for ietf@ietf.org; Tue, 3 Aug 2004 18:59:47 +0200
From: Hadmut Danisch <hadmut@danisch.de>
Date: Tue, 3 Aug 2004 09:59:47 -0700
To: ietf@ietf.org
Message-ID: <20040803165947.GA3688@danisch.de>
References: <8C7897C2-E4A1-11D8-B3D0-000393CC2112@acm.org>
	<20040802223754.GA31874@login.ecs.soton.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040802223754.GA31874@login.ecs.soton.ac.uk>
User-Agent: Mutt/1.5.6+20040523i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Subject: Re: Jabber at ietf60
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-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f

On Mon, Aug 02, 2004 at 11:37:55PM +0100, Tim Chown wrote:
> Sure, e.g.
> 
> On Mon, Aug 02, 2004 at 09:32:30AM -0700, avri@acm.org wrote:
> > Are folks using it?


Does this server allow to register an account? Or which 
server should I use to do so?

regards
Hadmut


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


From ietf-bounces@ietf.org  Tue Aug  3 13:55:14 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26840;
	Tue, 3 Aug 2004 13:55:14 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bs3YO-0006EC-KS; Tue, 03 Aug 2004 13:58:28 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bs3P5-0005DK-15; Tue, 03 Aug 2004 13:48:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bs375-0000uU-HA
	for ietf@megatron.ietf.org; Tue, 03 Aug 2004 13:30:11 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24145
	for <ietf@ietf.org>; Tue, 3 Aug 2004 13:30:10 -0400 (EDT)
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bs3AB-0005UW-Jx
	for ietf@ietf.org; Tue, 03 Aug 2004 13:33:24 -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
	i73HU7nE024078; Tue, 3 Aug 2004 18:30:08 +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 SAA10696;
	Tue, 3 Aug 2004 18:30:03 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id i73HU3m21552;
	Tue, 3 Aug 2004 18:30:03 +0100
Date: Tue, 3 Aug 2004 18:30:03 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: Hadmut Danisch <hadmut@danisch.de>
Message-ID: <20040803173002.GB21469@login.ecs.soton.ac.uk>
References: <8C7897C2-E4A1-11D8-B3D0-000393CC2112@acm.org>
	<20040802223754.GA31874@login.ecs.soton.ac.uk>
	<20040803165947.GA3688@danisch.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040803165947.GA3688@danisch.de>
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-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: ietf@ietf.org
Subject: Re: Jabber at ietf60
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-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a

try jabber.org, it's open to anyone to register.

then use ietf.xmpp.org as server, wg id as room, eg. v6ops or dhc.

tim

On Tue, Aug 03, 2004 at 09:59:47AM -0700, Hadmut Danisch wrote:
> On Mon, Aug 02, 2004 at 11:37:55PM +0100, Tim Chown wrote:
> > Sure, e.g.
> > 
> > On Mon, Aug 02, 2004 at 09:32:30AM -0700, avri@acm.org wrote:
> > > Are folks using it?
> 
> 
> Does this server allow to register an account? Or which 
> server should I use to do so?
> 
> regards
> Hadmut
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf

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


From ietf-bounces@ietf.org  Tue Aug  3 16:58:29 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11390;
	Tue, 3 Aug 2004 16:58:29 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bs6Pp-0001JQ-Gz; Tue, 03 Aug 2004 17:01:46 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bs6IX-0001jY-18; Tue, 03 Aug 2004 16:54:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bs6Fw-0001Rw-RD
	for ietf@megatron.ietf.org; Tue, 03 Aug 2004 16:51:32 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11030
	for <ietf@ietf.org>; Tue, 3 Aug 2004 16:51:30 -0400 (EDT)
Received: from rwcrmhc13.comcast.net ([204.127.198.39])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bs6J5-0001C0-1m
	for ietf@ietf.org; Tue, 03 Aug 2004 16:54:48 -0400
Received: from dfnjgl21 (opene-130-129-131-65.ietf60.ietf.org[130.129.131.65])
	by comcast.net (rwcrmhc13) with SMTP id <200408032050590150084f32e>
	(Authid: sdawkins@comcast.net); Tue, 3 Aug 2004 20:50:59 +0000
Message-ID: <017001c4799b$941a9b80$fb828182@DFNJGL21>
From: "Spencer Dawkins" <spencer@mcsr-labs.org>
To: "IETF General Discussion Mailing List" <ietf@ietf.org>
Date: Tue, 3 Aug 2004 13:50:58 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: 7bit
Subject: Notes from WG Chair Training on Sunday
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Spencer Dawkins <spencer@mcsr-labs.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: 7bit

My slides have been uploaded to the EDU website (see
http://edu.ietf.org) (thanks, James).

A couple of questions came up during our session that I needed to
check on the answers to:

- Yes, WG secretaries CAN be listed on WG charter pages - for example,
NSIS (http://www.ietf.org/html.charters/nsis-charter.html). I also
note that more than one secretary could be listed - if you can come up
with a permanent note-taker and a permanent Jabber scribe, you can
list them both. Thanks, Melinda, for the clue insertion.

- If multiple ADs have a concern about a particular part of a
document, the balloting will reflect only one DISCUSS. If multiple ADs
have concerns about about different things in a document, the
balloting will reflect multiple DISCUSSes. Thanks, Margaret, for the
clue insertion.

Spencer



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


From ietf-bounces@ietf.org  Wed Aug  4 10:33:41 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09056;
	Wed, 4 Aug 2004 10:33:41 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BsMtA-0000qf-EX; Wed, 04 Aug 2004 10:37:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BsMks-00026n-JH; Wed, 04 Aug 2004 10:28:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BsMiI-0001kH-9N
	for ietf@megatron.ietf.org; Wed, 04 Aug 2004 10:25:54 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08629
	for <ietf@ietf.org>; Wed, 4 Aug 2004 10:25:51 -0400 (EDT)
Received: from rproxy.gmail.com ([64.233.170.206] helo=mproxy.gmail.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BsMlZ-0000jn-Eo
	for ietf@ietf.org; Wed, 04 Aug 2004 10:29:18 -0400
Received: by mproxy.gmail.com with SMTP id 79so230843rnl
	for <ietf@ietf.org>; Wed, 04 Aug 2004 07:25:50 -0700 (PDT)
Received: by 10.38.171.3 with SMTP id t3mr677rne;
	Wed, 04 Aug 2004 07:25:50 -0700 (PDT)
Message-ID: <e29b9116040804072527c3e227@mail.gmail.com>
Date: Wed, 4 Aug 2004 15:25:50 +0100
From: Rik Wade <rik.wade@gmail.com>
To: ietf@ietf.org
In-Reply-To: <8C7897C2-E4A1-11D8-B3D0-000393CC2112@acm.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <8C7897C2-E4A1-11D8-B3D0-000393CC2112@acm.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Content-Transfer-Encoding: 7bit
Subject: Re: Jabber at ietf60
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-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Content-Transfer-Encoding: 7bit

On Mon, 2 Aug 2004 09:32:30 -0700, avri@acm.org <avri@acm.org> wrote:
> Are folks using it?
> 
> a.

Yes, I'm using it every night (BST) to tune in to the sessions. I'm
also using the (very good) streamed MP3.

The jabber service has been very good and reliable, but many sessions
haven't had scribes.
-- 
rik wade

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


From ietf-bounces@ietf.org  Wed Aug  4 11:51:37 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12966;
	Wed, 4 Aug 2004 11:51:37 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BsO6Y-0001we-0R; Wed, 04 Aug 2004 11:55:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BsNvY-0000lD-SX; Wed, 04 Aug 2004 11:43:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BsB5O-0007dz-OL
	for ietf@megatron.ietf.org; Tue, 03 Aug 2004 22:00:58 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA01191
	for <ietf@ietf.org>; Tue, 3 Aug 2004 22:00:56 -0400 (EDT)
Received: from athena.nswc.navy.mil ([198.91.70.29])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BsB8a-0006QL-Nb
	for ietf@ietf.org; Tue, 03 Aug 2004 22:04:17 -0400
Received: from relay.nswc.navy.mil (relay.nswc.navy.mil [128.38.1.41])
	by athena.nswc.navy.mil (8.11.6p3/8.11.6) with ESMTP id i7420m606752
	for <ietf@ietf.org>; Tue, 3 Aug 2004 22:00:49 -0400 (PDT)
Received: from relay.nswc.navy.mil (localhost [127.0.0.1])
	by relay.nswc.navy.mil (8.11.6p3/8.11.6) with ESMTP id i7420mv16003
	for <ietf@ietf.org>; Tue, 3 Aug 2004 22:00:48 -0400 (EDT)
Received: from titanic.nswc.navy.mil (titanic.nswc.navy.mil [128.38.42.115])
	by relay.nswc.navy.mil (8.11.6p3/8.11.6) with ESMTP id i7420lN15999
	for <ietf@ietf.org>; Tue, 3 Aug 2004 22:00:47 -0400 (EDT)
Received: from nswc.navy.mil (localhost [127.0.0.1])
	by titanic.nswc.navy.mil (8.11.7+Sun/8.9.3) with ESMTP id i7420Qe16371
	for <ietf@ietf.org>; Tue, 3 Aug 2004 22:00:47 -0400 (EDT)
Message-ID: <41104315.4070104@nswc.navy.mil>
Date: Tue, 03 Aug 2004 21:59:49 -0400
From: "Karen O'Donoghue" <odonoghuekf@nswc.navy.mil>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.0.2) Gecko/20021120 Netscape/7.01
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by athena.nswc.navy.mil id
	i7420m606752
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Wed, 04 Aug 2004 11:43:39 -0400
Subject: dynamic keying via 802.1X on IETF wireless 
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-Score: 0.0 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Content-Transfer-Encoding: quoted-printable

Folks,

We are experimenting with dynamic keying via 802.1X on the
IETF wireless network.  You are invited to try this service if you
wish. However, this isn't production so please do not ask for
assistance from the terminal room help desk staff.  Help
is available from the following (depending on schedule):

    Chris Hessing, Chris.Hessing@utah.edu
    Chris Elliott, chelliot@cisco.com

Regards,
Karen

Anonymous 802.1X at IETF 60
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D
Chris Hessing, University of Utah/Open1x Project

On the IETF 60 wireless network we are providing a separate SSID and VLAN=
 that
does anonymous 802.1X authentication with support for dynamic WEP. The ad=
vantage
of using this is your wireless connection will be encrypted using per-use=
r,
per-session keys. In addition, if you choose to check the certificate pro=
vided
by the network infrastructure during the authentication phase, you will a=
lso
receive some assurance that you are connecting to the IETF 60 network and=
 not
some other network.

If you would like to make use of the 802.1X wireless network, you will ne=
ed to
use the non-broadcast ESSID of =93ietf60-1x=94.

You will also need an 802.1X supplicant that has support for TTLS-PAP.  W=
indows
XP/2000 users can download a plug-in to the native 802.1X client at
http://www.secureW2.com.  Mac OS X users that are running OS 10.3+ alread=
y have
support included in the OS.  Directions are provided below. Linux users
can download Xsupplicant from http://www.open1x.org.

Your supplicant will receive a server certificate that is a test certific=
ate.
You can choose to configure your supplicant to accept this certificate th=
e first
time it is provided and check it thereafter, allowing your supplicant to =
verify
that you are connecting to the IETF network infrastructure, or you can ch=
oose to
not validate the server certificate.

The username and password that you use doesn't matter, as long as you fil=
l
something in for both. If you have an option to fill in a domain please l=
eave it
blank.

Note that the encryption type supported at this time is dynamic WEP. We a=
re
not currenly supporting WPA/TKIP.

We are currently working on supporting other EAP authentication types, in=
cluding=20
PEAP-GTC.

MAC Users
=3D=3D=3D=3D=3D=3D=3D=3D=3D
1. Open Internet Connect
  2.  Under File "New 802.1X connect"
      a. edit config
          name - whatever you want
          username - whatever you want
          password - whatever you want
          wireless network - ietf60-1x
            authentication - only select TTLS
               configure TTLS
               TTLS Inner Authentication - PAP
               no outer id
         connect
3. Self signed cert - accept.


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


From ietf-bounces@ietf.org  Wed Aug  4 12:29:46 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15922;
	Wed, 4 Aug 2004 12:29:46 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BsOhL-0002nK-Q6; Wed, 04 Aug 2004 12:33:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BsODp-0004FA-MG; Wed, 04 Aug 2004 12:02:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bs3N2-0004Xt-4H
	for ietf@megatron.ietf.org; Tue, 03 Aug 2004 13:46:40 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25997
	for <ietf@ietf.org>; Tue, 3 Aug 2004 13:46:39 -0400 (EDT)
Received: from [168.143.123.173] (helo=drakken.dbc.mtview.ca.us)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bs3Q3-00061a-82
	for ietf@ietf.org; Tue, 03 Aug 2004 13:49:53 -0400
Received: from [IPv6:::1] (localhost.localdomain [127.0.0.1])
	by drakken.dbc.mtview.ca.us (8.12.11/8.12.8) with ESMTP id
	i73HjZdF025848; Tue, 3 Aug 2004 10:45:35 -0700
In-Reply-To: <20040803165947.GA3688@danisch.de>
References: <8C7897C2-E4A1-11D8-B3D0-000393CC2112@acm.org>
	<20040802223754.GA31874@login.ecs.soton.ac.uk>
	<20040803165947.GA3688@danisch.de>
Mime-Version: 1.0 (Apple Message framework v618)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <EB185D82-E574-11D8-BE0C-000A95CA7FAE@dbc.mtview.ca.us>
Content-Transfer-Encoding: 7bit
From: Marshall Rose <mrose+mtr.netnews@dbc.mtview.ca.us>
Date: Tue, 3 Aug 2004 10:45:33 -0700
To: Hadmut Danisch <hadmut@danisch.de>
X-Mailer: Apple Mail (2.618)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 04 Aug 2004 12:02:31 -0400
Cc: ietf@ietf.org
Subject: Re: Jabber at ietf60
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-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7bit


On Aug 03, 2004, at 09:59, Hadmut Danisch wrote:

> Does this server allow to register an account? Or which
> server should I use to do so?


for instructions, take a look at:

	http://xmpp.org/ietf-chat.html


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


From ietf-bounces@ietf.org  Wed Aug  4 14:17:00 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25387;
	Wed, 4 Aug 2004 14:17:00 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BsQNH-0005Fp-QG; Wed, 04 Aug 2004 14:20:29 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BsQ6m-0001fk-IC; Wed, 04 Aug 2004 14:03:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BsPx9-0000Fl-Kb
	for ietf@megatron.ietf.org; Wed, 04 Aug 2004 13:53:27 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23487
	for <ietf@ietf.org>; Wed, 4 Aug 2004 13:53:26 -0400 (EDT)
Received: from brmea-mail-4.sun.com ([192.18.98.36])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BsQ0S-0004lY-Kk
	for ietf@ietf.org; Wed, 04 Aug 2004 13:56:54 -0400
Received: from esunmail ([129.147.156.34])
	by brmea-mail-4.sun.com (8.12.10/8.12.9) with ESMTP id i74Hp053002918
	for <ietf@ietf.org>; Wed, 4 Aug 2004 11:51:01 -0600 (MDT)
Received: from fe8 (esunmail [129.147.156.34]) by edgemail1.Central.Sun.COM
	(iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep  8 2003))
	with ESMTP id <0I1X00JDUOCZTD@edgemail1.Central.Sun.COM> for
	ietf@ietf.org; Wed, 04 Aug 2004 11:53:24 -0600 (MDT)
Received: from [192.168.1.15] ([216.113.203.45])
	by mail.sun.net (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep 8
	2003))
	with ESMTPSA id <0I1X00CSDOCZE1@mail.sun.net> for ietf@ietf.org; Wed,
	04 Aug 2004 11:53:23 -0600 (MDT)
Date: Wed, 04 Aug 2004 10:53:32 -0700
From: Tim Bray <tbray@textuality.com>
To: ietf@ietf.org
Message-id: <335D90CE-E63F-11D8-A4DC-000A95A51C9E@textuality.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.618)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Subject: Multicast doesn't work
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="===============0992181788=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30


--===============0992181788==
Content-type: multipart/signed; micalg=sha1; boundary=Apple-Mail-8--481820637; 
	protocol="application/pkcs7-signature"


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

The OS X version doesn't work if you have NeoOffice/J installed, 
because it Neo thinks it owns one of the extensions (sdp or something).

So I went to a totally vanilla patched up to date Win/XP box with an 
up-to-date Quicktime and Quicktime refused to handle .QT.esm files, so 
I downloaded the ESM .exe files, not that there's any indication of 
what to do with them, and they didn't do anything either.

So I won't be watching the multicast. -Tim
--Apple-Mail-8--481820637
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Disposition: attachment;
	filename=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGHDCCAtUw
ggI+oAMCAQICAwuKuTANBgkqhkiG9w0BAQQFADBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhh
d3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt
YWlsIElzc3VpbmcgQ0EwHhcNMDQwMTIyMjMzOTA2WhcNMDUwMTIxMjMzOTA2WjBGMR8wHQYDVQQD
ExZUaGF3dGUgRnJlZW1haWwgTWVtYmVyMSMwIQYJKoZIhvcNAQkBFhR0YnJheUB0ZXh0dWFsaXR5
LmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMYiIlrf7yTblabXBlwkonodVyp+
W7Oo8w71ErSW7mKramEBAkfkUnPmbRqcS2wqFaK34GbQMk/1vcOxo2AmfmFVec13SWKi0YzXC8xf
9SbjfQU1tXiC9LJB1HeOO46UVRqTNeayruz2pQBztvYF76G5sGmwKjoR/DhimwUM579MaJln38SK
UQ6Ya768DwyaDNY7yDWYh1gUxizx71QkzyRCPQdmq6g1ebrVYyoBE33BXQRNGZm2zrlI5JBQ4oax
E0Cz3BjR8iZFzK/AhFGDllZYuojf7iZuaNhWr3aWAvHNyLHVMaxXNFb/CUri5c7StFVEgXUVvlgP
eSHIPg9gqaECAwEAAaMxMC8wHwYDVR0RBBgwFoEUdGJyYXlAdGV4dHVhbGl0eS5jb20wDAYDVR0T
AQH/BAIwADANBgkqhkiG9w0BAQQFAAOBgQBQAlJ/qQJmtQN966ahSWiovhjWj5Qwk6BnPP+Fjfbo
9guSIWWBw2DEXh8nPT4WJchZSVz4SwDtZ0SZ2PWWToRo/Dmpv+ehzNNhR/y2CdU/zNo+kSShBhc6
HNtp6A0+Yh6Vw0Y+qHa0EKppOJM2D5WTExycYjHU8Xs+dLktAmKqlzCCAz8wggKooAMCAQICAQ0w
DQYJKoZIhvcNAQEFBQAwgdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQ
BgNVBAcTCUNhcGUgVG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0Nl
cnRpZmljYXRpb24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBG
cmVlbWFpbCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAe
Fw0wMzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU
aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJl
ZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065ypla
HmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FWy688
Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEEQB5kGXJg
t/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2oDSGMmh0dHA6
Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3JsMAsGA1UdDwQEAwIB
BjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxhYmVsMi0xMzgwDQYJKoZIhvcNAQEF
BQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFi
w9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amcOY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU13
41YheILcIRk13iSx0x1G/11fZU8xggLnMIIC4wIBATBpMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQK
ExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg
RnJlZW1haWwgSXNzdWluZyBDQQIDC4q5MAkGBSsOAwIaBQCgggFTMBgGCSqGSIb3DQEJAzELBgkq
hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTA0MDgwNDE3NTMzM1owIwYJKoZIhvcNAQkEMRYEFDF8
soYeCt+maYeeZZovlB1Gu6FcMHgGCSsGAQQBgjcQBDFrMGkwYjELMAkGA1UEBhMCWkExJTAjBgNV
BAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h
bCBGcmVlbWFpbCBJc3N1aW5nIENBAgMLirkwegYLKoZIhvcNAQkQAgsxa6BpMGIxCzAJBgNVBAYT
AlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3
dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIDC4q5MA0GCSqGSIb3DQEBAQUABIIBAG5q
VZHuUJ9MpPWL4CpajTAMw6Al4KLd6Qsed7UyHyuP0mLGCEFT3RJhrlgJHZ565+ja4BGaHAuJIpYH
xR2puBRKrFK8ODvayoJ357oKk7l+RLNLuzANhi3gWwdem4s94+V9S4u3lvdbliHkLTtnFwE/y0tN
eNzMPB0k0TGsV5dDcPuh5wLwFTGPReXnQZwlOMA3+qAoaEfgMKlmZTr2rZ0xyNIP31ynlRpjz4vA
QhvGx6tbhsXCXSeR/HQSs4aB1OgZRzaflfX1ujeCJxAcIhc3+MUUBn3LEhInNVZqqO1ZmZYGl/jc
jKUHD85S89C7UvaVWtD9fF3rA2uFbQYwUy8AAAAAAAA=

--Apple-Mail-8--481820637--



--===============0992181788==
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

--===============0992181788==--




From ietf-bounces@ietf.org  Wed Aug  4 17:06:04 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA08145;
	Wed, 4 Aug 2004 17:06:04 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BsT0v-0000As-RS; Wed, 04 Aug 2004 17:09:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BsSsS-0005jd-89; Wed, 04 Aug 2004 17:00:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BsSiV-00044S-8z
	for ietf@megatron.ietf.org; Wed, 04 Aug 2004 16:50:31 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07525
	for <ietf@ietf.org>; Wed, 4 Aug 2004 16:50:29 -0400 (EDT)
Received: from darkwing.uoregon.edu ([128.223.142.13] ident=root)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BsSlq-0008Pp-8M
	for ietf@ietf.org; Wed, 04 Aug 2004 16:53:59 -0400
Received: from twin.uoregon.edu (twin.uoregon.edu [128.223.214.27])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i74KoR9s018439
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); 
	Wed, 4 Aug 2004 13:50:28 -0700 (PDT)
Date: Wed, 4 Aug 2004 13:50:27 -0700 (PDT)
From: Joel Jaeggli <joelja@darkwing.uoregon.edu>
X-X-Sender: joelja@twin.uoregon.edu
To: Tim Bray <tbray@textuality.com>
In-Reply-To: <335D90CE-E63F-11D8-A4DC-000A95A51C9E@textuality.com>
Message-ID: <Pine.LNX.4.60.0408041349250.15566@twin.uoregon.edu>
References: <335D90CE-E63F-11D8-A4DC-000A95A51C9E@textuality.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: ietf@ietf.org
Subject: Re: Multicast doesn't work
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-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3

On Wed, 4 Aug 2004, Tim Bray wrote:

> The OS X version doesn't work if you have NeoOffice/J installed, because it 
> Neo thinks it owns one of the extensions (sdp or something).
>
> So I went to a totally vanilla patched up to date Win/XP box with an 
> up-to-date Quicktime and Quicktime refused to handle .QT.esm files, so I 
> downloaded the ESM .exe files, not that there's any indication of what to do 
> with them, and they didn't do anything either.
>
> So I won't be watching the multicast. -Tim

not sure what an esm file is?

have you tried the unicast stream(s)?

-- 
-------------------------------------------------------------------------- 
Joel Jaeggli  	       Unix Consulting 	       joelja@darkwing.uoregon.edu 
GPG Key Fingerprint:     5C6E 0104 BAF0 40B0 5BD3 C38B F000 35AB B67F 56B2


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


From ietf-bounces@ietf.org  Thu Aug  5 00:46:56 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA07505;
	Thu, 5 Aug 2004 00:46:56 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BsaD1-0007bp-QX; Thu, 05 Aug 2004 00:50:32 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bsa4K-0000Iy-T4; Thu, 05 Aug 2004 00:41:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bsa0Z-0008K4-K3
	for ietf@megatron.ietf.org; Thu, 05 Aug 2004 00:37:39 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA07139
	for <ietf@ietf.org>; Thu, 5 Aug 2004 00:37:36 -0400 (EDT)
Received: from rwcrmhc13.comcast.net ([204.127.198.39])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bsa3z-0007V9-IU
	for ietf@ietf.org; Thu, 05 Aug 2004 00:41:12 -0400
Received: from dfnjgl21 (opene-130-129-135-27.ietf60.ietf.org[130.129.135.27])
	by comcast.net (rwcrmhc13) with SMTP id <200408050437070150084rmve>
	(Authid: sdawkins@comcast.net); Thu, 5 Aug 2004 04:37:07 +0000
Message-ID: <001a01c47aa5$dd3ecf10$1b878182@DFNJGL21>
From: "Spencer Dawkins" <spencer@mcsr-labs.org>
To: "IETF General Discussion Mailing List" <ietf@ietf.org>
Date: Wed, 4 Aug 2004 21:37:06 -0700
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f460acdc4aacf7fc5e6f9bd32f8fd8c6
Subject: First hack at Wednesday Plenary notes
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Spencer Dawkins <spencer@mcsr-labs.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1916420509=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 919b3965bd46f7460d234f848680b238

This is a multi-part message in MIME format.

--===============1916420509==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0017_01C47A6B.30799420"

This is a multi-part message in MIME format.

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

Please let me know if I'm misquoting or mis-hearing...

Thanks!

Spencer

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

1930-2200 Plenary - IETF Business Meeting - Grande Ballroom

- Welcome, and introduction - Harald Alvestrand

Wednesday is state of the union, Thursday is planning for the future

1511 registered attendees, 40 countries, about half are US

Fall IETF is in Washington, DC with Alcatel as sponsor

- Thanks to the Tech Team - Jim Martin

The network that almost wasn't - no local host, 80% of equioment lost in =
shipping,=20

current network built entirely out of last second replacement equipment =
from Cisco, Priotity Networks, and others.

Peaks of 17 Mbps in both directions, with IPv6 and IPv4 multicast

Down from 35 G access points to 20 B access points, with three networks =
(Open, WEP, 802.1X)

Using 4 remote probes with AirMagnet for monitoring

1532 unique MACs, peak of 890 simultaneous users, peak of 143 =
associations on one AP

Network entirely done by volunteers this time, with entirely donated =
equipment (Cisco gave twice!)

- Jon Postel Award (ISOC) - Steve Crocker

This year's recipient is Phil Gross, co-founder of the IETF, for his =
contribution to the Internet standardization process=20

Letter, globe, check for $20,000

Being chair of IETF is like being mayor of New York - 60 percent =
approval is good, but every good decision is a different

60 percent

IETF started different - idea was that technologists could work for the =
common good and base choices on technical merit

Our areas were working groups in the beginning - and everybody wanted to =
go to all the working group meetings

IETF is going through issues now, and they aren't small, but IETF has =
gone through difficult times before - remember the=20

first time we invited industry? charged admission? created the IESG? the =
protocol wars? ANSI S3X3 could have been the

IETF - things could have been very different!

- State of operations:

RFC Editor report=20

IANA report

IESG operations (Allison Mankin, Bill Fenner)

Reporting trends since 2003, measuring intervals between IETFs (so some =
measurement anomolies, because time period varies

Data shows IESG and community both becoming more responsive - timeliness =
seems to be positive feedback loop

More WG recharters this year than in all of 2003 - could we be paying =
more attention to charters?

Want to make monthly data available

- Update from the PROTO (Process Team) work (Margaret and Henryk)

http://www.mip4.org/proto

Goal is WG chair shepherding through document review and approval =
process

Small changes, don't require modifications to 2026 or 2418

AD still has review and approval roles - shepherding role is delegated

draft-ietf-proto-shepherding-00.txt describes shepherding role

draft-ietf-proto-wgchair-doc-shepherding-01.txt describes process =
changes

Moving to a larger-scale experiment of this change

- Who's in charge of the Internet: The WSIS Deliberations (Robert Kahn, =
CNRI)

US and other developed nations think things are just fine

Other developing nations think somebody needs to be in charge of the =
Internet - they think UN is best suited to provide leadership

Very decentralized system of cooperation, coordination and interaction

"If UN controlled ICANN, they would control the Internet"

Standardization mostly ignored, at least so far

Phase I of WSIS in December 2003 had about 12,000 attendees - finally =
took Internet Governance off the agenda

UN working group to look at this in preparation for Phase II of WSIS in =
November 2005, in Tunis

Interim activities taking place throughout 2004 - theme meetings on =
topics like spam

Bob asking for research community reengagement

IETF now in the gunsights

Difficult to get agreement on definition of "Internet Governance" - UN =
isn't monolithic, either

Lots of reading materials available

ICANN being attacked because they aren't part of the UN

- Review of Architectural Activities

IAB Chair report

Most recent published document (in queue) is on research funding (see =
IAB website)

Planning messaging workshop in September/October timeframe

Also working on liaison mechanics (see drafts) - will be coming out for =
community last call

IRTF Chair report

13 groups now in IRTF

ASRG related to MARID WG meeting at this IETF

CryptoForum RG actually supports IETF WGs with crypto questions

DTNRG showing a lot of activity (and meeting at this IETF)

HIP RG working on indirection infrastructure, operation over NATs, =
rendezvous mechanisms, API

MOBOPTS also working closely with IETF mobility WGs

Network Management Research Group focused on XML-based management, SMIng =
specs published

Routing RG focused on scalability, BGP stability, requirements for =
next-gen routing, history of routing protocols

Services Management actively looking for participants

- IAB Open Plenary

No questions at all - amazing!

- IESG Open Plenary

Are we doing better? (applause) - we're trying to get somewhere

Recent changes in Internet Draft submission requirements - =
"semi-bounced" with "does not conform" - doesn't help discussion

We're tardy in reflecting RFC 3667/3668 changes, and even more tardy in =
telling you about the changes

We need to have the IPR copyright boilerplate right, even in IDs - this =
has already been a problem, and we're reacting

Experience is much better than several years ago (when working on SLP)

There have been significant and important improvements

Does OPS sub-area not develop protocols? Is this a real rule? In =
general, this is true, but we listen to reason

ID Nits document is really an RFC Nits document - formatting =
restrictions, etc. don't matter early in the process

There are two documents, and we're not good at point out which is which =
- and the only real requirement is copyright

IDs are read and reviewed - make them as reviewable as possible

------=_NextPart_000_0017_01C47A6B.30799420
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.1458" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff background=3D""><FONT size=3D2><FONT size=3D2>
<P>Please let me know if I'm misquoting or mis-hearing...</P>
<P>Thanks!</P>
<P>Spencer</P>
<P>---------------------------------------------------------------</P>
<P>1930-2200 Plenary - IETF Business Meeting - Grande Ballroom</P>
<P>- Welcome, and introduction - Harald Alvestrand</P>
<P>Wednesday is state of the union, Thursday is planning for the =
future</P>
<P>1511 registered attendees, 40 countries, about half are US</P>
<P>Fall IETF is in Washington, DC with Alcatel as sponsor</P>
<P>- Thanks to the Tech Team - Jim Martin</P>
<P>The network that almost wasn't - no local host, 80% of equioment lost =
in=20
shipping, </P>
<P>current network built entirely out of last second replacement =
equipment from=20
Cisco, Priotity Networks, and others.</P>
<P>Peaks of 17 Mbps in both directions, with IPv6 and IPv4 multicast</P>
<P>Down from 35 G access points to 20 B access points, with three =
networks=20
(Open, WEP, 802.1X)</P>
<P>Using 4 remote probes with AirMagnet for monitoring</P>
<P>1532 unique MACs, peak of 890 simultaneous users, peak of 143 =
associations on=20
one AP</P>
<P>Network entirely done by volunteers this time, with entirely donated=20
equipment (Cisco gave twice!)</P>
<P>- Jon Postel Award (ISOC) - Steve Crocker</P>
<P>This year's recipient is Phil Gross, co-founder of the IETF, for his=20
contribution to the Internet standardization process </P>
<P>Letter, globe, check for $20,000</P>
<P>Being chair of IETF is like being mayor of New York - 60 percent =
approval is=20
good, but every good decision is a different</P>
<P>60 percent</P>
<P>IETF started different - idea was that technologists could work for =
the=20
common good and base choices on technical merit</P>
<P>Our areas were working groups in the beginning - and everybody wanted =
to go=20
to all the working group meetings</P>
<P>IETF is going through issues now, and they aren't small, but IETF has =
gone=20
through difficult times before - remember the </P>
<P>first time we invited industry? charged admission? created the IESG? =
the=20
protocol wars? ANSI S3X3 could have been the</P>
<P>IETF - things could have been very different!</P>
<P>- State of operations:</P>
<P>RFC Editor report </P>
<P>IANA report</P>
<P>IESG operations (Allison Mankin, Bill Fenner)</P>
<P>Reporting trends since 2003, measuring intervals between IETFs (so =
some=20
measurement anomolies, because time period varies</P>
<P>Data shows IESG and community both becoming more responsive - =
timeliness=20
seems to be positive feedback loop</P>
<P>More WG recharters this year than in all of 2003 - could we be paying =
more=20
attention to charters?</P>
<P>Want to make monthly data available</P>
<P>- Update from the PROTO (Process Team) work (Margaret and Henryk)</P>
<P>http://www.mip4.org/proto</P>
<P>Goal is WG chair shepherding through document review and approval =
process</P>
<P>Small changes, don't require modifications to 2026 or 2418</P>
<P>AD still has review and approval roles - shepherding role is =
delegated</P>
<P>draft-ietf-proto-shepherding-00.txt describes shepherding role</P>
<P>draft-ietf-proto-wgchair-doc-shepherding-01.txt describes process =
changes</P>
<P>Moving to a larger-scale experiment of this change</P>
<P>- Who's in charge of the Internet: The WSIS Deliberations (Robert =
Kahn,=20
CNRI)</P>
<P>US and other developed nations think things are just fine</P>
<P>Other developing nations think somebody needs to be in charge of the =
Internet=20
- they think UN is best suited to provide leadership</P>
<P>Very decentralized system of cooperation, coordination and =
interaction</P>
<P>"If UN controlled ICANN, they would control the Internet"</P>
<P>Standardization mostly ignored, at least so far</P>
<P>Phase I of WSIS in December 2003 had about 12,000 attendees - finally =
took=20
Internet Governance off the agenda</P>
<P>UN working group to look at this in preparation for Phase II of WSIS =
in=20
November 2005, in Tunis</P>
<P>Interim activities taking place throughout 2004 - theme meetings on =
topics=20
like spam</P>
<P>Bob asking for research community reengagement</P>
<P>IETF now in the gunsights</P>
<P>Difficult to get agreement on definition of "Internet Governance" - =
UN isn't=20
monolithic, either</P>
<P>Lots of reading materials available</P>
<P>ICANN being attacked because they aren't part of the UN</P>
<P>- Review of Architectural Activities</P>
<P>IAB Chair report</P>
<P>Most recent published document (in queue) is on research funding (see =
IAB=20
website)</P>
<P>Planning messaging workshop in September/October timeframe</P>
<P>Also working on liaison mechanics (see drafts) - will be coming out =
for=20
community last call</P>
<P>IRTF Chair report</P>
<P>13 groups now in IRTF</P>
<P>ASRG related to MARID WG meeting at this IETF</P>
<P>CryptoForum RG actually supports IETF WGs with crypto questions</P>
<P>DTNRG showing a lot of activity (and meeting at this IETF)</P>
<P>HIP RG working on indirection infrastructure, operation over NATs, =
rendezvous=20
mechanisms, API</P>
<P>MOBOPTS also working closely with IETF mobility WGs</P>
<P>Network Management Research Group focused on XML-based management, =
SMIng=20
specs published</P>
<P>Routing RG focused on scalability, BGP stability, requirements for =
next-gen=20
routing, history of routing protocols</P>
<P>Services Management actively looking for participants</P>
<P>- IAB Open Plenary</P>
<P>No questions at all - amazing!</P>
<P>- IESG Open Plenary</P>
<P>Are we doing better? (applause) - we're trying to get somewhere</P>
<P>Recent changes in Internet Draft submission requirements - =
"semi-bounced"=20
with "does not conform" - doesn't help discussion</P>
<P>We're tardy in reflecting RFC 3667/3668 changes, and even more tardy =
in=20
telling you about the changes</P>
<P>We need to have the IPR copyright boilerplate right, even in IDs - =
this has=20
already been a problem, and we're reacting</P>
<P>Experience is much better than several years ago (when working on =
SLP)</P>
<P>There have been significant and important improvements</P>
<P>Does OPS sub-area not develop protocols? Is this a real rule? In =
general,=20
this is true, but we listen to reason</P>
<P>ID Nits document is really an RFC Nits document - formatting =
restrictions,=20
etc. don't matter early in the process</P>
<P>There are two documents, and we're not good at point out which is =
which - and=20
the only real requirement is copyright</P>
<P>IDs are read and reviewed - make them as reviewable as=20
possible</P></FONT></FONT></BODY></HTML>

------=_NextPart_000_0017_01C47A6B.30799420--




--===============1916420509==
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

--===============1916420509==--





From ietf-bounces@ietf.org  Thu Aug  5 02:27:50 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26721;
	Thu, 5 Aug 2004 02:27:50 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bsbme-0000cs-Uh; Thu, 05 Aug 2004 02:31:25 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bsbfj-0006aH-QK; Thu, 05 Aug 2004 02:24:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BsbeJ-0005lI-3n
	for ietf@megatron.ietf.org; Thu, 05 Aug 2004 02:22:47 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26373
	for <ietf@ietf.org>; Thu, 5 Aug 2004 02:22:45 -0400 (EDT)
Received: from homebase.htt-consult.com ([65.84.78.210] helo=htt-consult.com)
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1Bsbhh-0000YB-9A
	for ietf@ietf.org; Thu, 05 Aug 2004 02:26:20 -0400
Received: from port3490-new.htt-consult.com ([65.84.78.209]) by
	htt-consult.com ; Thu, 05 Aug 2004 02:22:39 -0400
Message-Id: <6.1.2.0.2.20040804232027.050b16f8@localhost>
X-Sender: rgm-ietf@localhost
X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0
Date: Wed, 04 Aug 2004 23:22:11 -0700
To: ietf@ietf.org
From: Robert Moskowitz <rgm-ietf@htt-consult.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Rcpt-To: <ietf@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
Subject: Anyone @ the meeting experienced w Sambo 3.0 and BDC?
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-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199

I am looking for some guidance that I am not finding in the docs.

How to bring up a 3.0 BDC to an NT domain, and migrate to an all Samba domain.

I am here until noon thusday.



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


From ietf-bounces@ietf.org  Thu Aug  5 09:26:22 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16828;
	Thu, 5 Aug 2004 09:26:21 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BsiJk-0006L4-VV; Thu, 05 Aug 2004 09:30:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BsiCe-0007m5-1k; Thu, 05 Aug 2004 09:22:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BsiBp-0007eP-Fv
	for ietf@megatron.ietf.org; Thu, 05 Aug 2004 09:21:49 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16625
	for <ietf@ietf.org>; Thu, 5 Aug 2004 09:21:47 -0400 (EDT)
Received: from cyphermail.sandelman.ottawa.on.ca ([205.150.200.161]
	helo=noxmail.sandelman.ottawa.on.ca)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BsiFI-0006Gu-UC
	for ietf@ietf.org; Thu, 05 Aug 2004 09:25:26 -0400
Received: from sandelman.ottawa.on.ca (marajade.sandelman.ottawa.on.ca
	[205.150.200.247])
	by noxmail.sandelman.ottawa.on.ca (8.11.6p3/8.11.6) with ESMTP id
	i75DLf810663
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified
	OK) for <ietf@ietf.org>; Thu, 5 Aug 2004 09:21:42 -0400 (EDT)
Received: from sandelman.ottawa.on.ca (marajade [127.0.0.1])
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id
	i75DLe4F025906
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <ietf@ietf.org>; Thu, 5 Aug 2004 09:21:40 -0400
Received: from marajade.sandelman.ottawa.on.ca (mcr@localhost)
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id
	i75DLZYR025902 for <ietf@ietf.org>; Thu, 5 Aug 2004 09:21:40 -0400
To: ietf@ietf.org
In-Reply-To: Message from Iljitsch van Beijnum <iljitsch@muada.com> of "Sun,
	01 Aug 2004 18:56:40 +0200."
	<C20C5AB0-E3DB-11D8-B13E-000A95CD987A@muada.com> 
References: <5B3144E8-DACD-11D8-9C46-000A95DBDB84@isi.edu>
	<19BD78A2-DB4A-11D8-A54A-000A95CD987A@muada.com>
	<D56BFBF597F94C89784423A4@[10.0.0.2]>
	<6.1.1.1.2.20040721170526.05493b28@mira-sjc5-b.cisco.com>
	<20040722120658.GR26441@login.ecs.soton.ac.uk>
	<31495.1090503031@marajade.sandelman.ottawa.on.ca>
	<5E94267C-DC08-11D8-9C46-000A95DBDB84@isi.edu>
	<562203147.20040801081055@brandenburg.com>
	<C20C5AB0-E3DB-11D8-B13E-000A95CD987A@muada.com> 
X-Mailer: MH-E 7.4.2; nmh 1.0.4+dev; XEmacs 21.4 (patch 6)
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Thu, 05 Aug 2004 09:21:35 -0400
Message-ID: <25901.1091712095@marajade.sandelman.ottawa.on.ca>
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
X-Spam-Score: 2.3 (++)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Subject: Re: Reducing parallel meeting slots 
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-Score: 2.3 (++)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081

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


>>>>> "Iljitsch" == Iljitsch van Beijnum <iljitsch@muada.com> writes:
    Iljitsch> ...it doesn't address the problem of overlapping
    Iljitsch> sessions. Sessions are going to overlap. This is only a
    Iljitsch> problem when people want to attend more than one during
    Iljitsch> any particular slot. The fact that people want to attend a
    Iljitsch> session makes it highly unlikely that such a session is so
    Iljitsch> unproductive that scrapping it alltoghether would be
    Iljitsch> better. (I don't believe IETFers are so stupid they keep
    Iljitsch> showing up for unproductive sessions.)

  I can think of a number of BOFs, and even some WGs that are very well
attended, but have not made any progress.
  
  My original contention was that these groups are either stuck, or they
have the *wrong amount* of face time. They get two hours, sometimes four
(over two days). 

  Yet, to make the decision they need to progress, they really need
three days of intensive time, and they probably need to have a smaller
(more manageable) group attending.

  Finally, as has been discussed previously (particularly during our
peak, when we didn't fit in the hotels anymore), with wireless, people
can occupy seats and not pay attention. 

- --
]     "Elmo went to the wrong fundraiser" - The Simpson         |  firewalls  [
]   Michael Richardson,    Xelerance Corporation, Ottawa, ON    |net architect[
] mcr@xelerance.com      http://www.sandelman.ottawa.on.ca/mcr/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Finger me for keys

iQCVAwUBQRI0XYqHRg3pndX9AQEFhQP8D/01SaWFAcglBKPRWfcfeVieBCstid2n
qmkwI/BXpbkjObmStJQKofvxff7/R/bArshe8tZXu8G5fqA4yh7c2QBRVbJCRFDj
H9xHnxuKw5U9STzfOIIkQe4OGK/Oq/dttAbU0Nuixg6PIBM4k1Fk0jLCw1BvIdBF
w5FIx8eCXO0=
=8DVr
-----END PGP SIGNATURE-----

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


From ietf-bounces@ietf.org  Thu Aug  5 14:04:07 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03285;
	Thu, 5 Aug 2004 14:04:06 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bsmea-00021U-9K; Thu, 05 Aug 2004 14:07:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BsmXx-0006AD-03; Thu, 05 Aug 2004 14:00:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BsmTR-00055B-SG
	for ietf@megatron.ietf.org; Thu, 05 Aug 2004 13:56:18 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02903
	for <ietf@ietf.org>; Thu, 5 Aug 2004 13:56:16 -0400 (EDT)
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BsmWz-0001se-Bo
	for ietf@ietf.org; Thu, 05 Aug 2004 13:59:57 -0400
Received: from [127.0.0.1] (sequoia.muada.com [83.149.65.1])
	by sequoia.muada.com (8.12.10/8.12.10) with ESMTP id i75Hv9MG098341;
	Thu, 5 Aug 2004 19:57:10 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <25901.1091712095@marajade.sandelman.ottawa.on.ca>
References: <5B3144E8-DACD-11D8-9C46-000A95DBDB84@isi.edu>
	<19BD78A2-DB4A-11D8-A54A-000A95CD987A@muada.com>
	<D56BFBF597F94C89784423A4@[10.0.0.2]>
	<6.1.1.1.2.20040721170526.05493b28@mira-sjc5-b.cisco.com>
	<20040722120658.GR26441@login.ecs.soton.ac.uk>
	<31495.1090503031@marajade.sandelman.ottawa.on.ca>
	<5E94267C-DC08-11D8-9C46-000A95DBDB84@isi.edu>
	<562203147.20040801081055@brandenburg.com>
	<C20C5AB0-E3DB-11D8-B13E-000A95CD987A@muada.com>
	<25901.1091712095@marajade.sandelman.ottawa.on.ca>
Mime-Version: 1.0 (Apple Message framework v618)
Message-Id: <B29E386A-E708-11D8-805E-000A95CD987A@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Thu, 5 Aug 2004 19:55:54 +0200
To: Michael Richardson <mcr@sandelman.ottawa.on.ca>
X-Pgp-Agent: GPGMail 1.0.1 (v33, 10.3)
X-Mailer: Apple Mail (2.618)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: ietf@ietf.org
Subject: Re: Reducing parallel meeting slots 
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="===============0780617646=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168


--===============0780617646==
Content-Type: multipart/signed; protocol="application/pgp-signature";
	micalg=pgp-sha1; boundary="Apple-Mail-11--395278246"


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

On 5-aug-04, at 15:21, Michael Richardson wrote:

>     Iljitsch> The fact that people want to attend a
>     Iljitsch> session makes it highly unlikely that such a session is 
> so
>     Iljitsch> unproductive that scrapping it alltoghether would be
>     Iljitsch> better. (I don't believe IETFers are so stupid they keep
>     Iljitsch> showing up for unproductive sessions.)

>   I can think of a number of BOFs, and even some WGs that are very well
> attended, but have not made any progress.

The trouble is, that even if you can define success fully (which is 
difficult enough in its own right), that still makes it very hard to 
impossible to determine which efforts are going to turn out successful 
a) beforehand and b) somewhere along the way.

> My original contention was that these groups are either stuck

Yes. Unfortunately the IETF doesn't seem to have any way to arrive at 
decisions other than wait, wait some more and  until at some point 
rough consensus happens. The whole IPv6 resolver issue in dnsop is a 
good example of this problem.

> Yet, to make the decision they need to progress, they really need
> three days of intensive time, and they probably need to have a smaller
> (more manageable) group attending.

I don't see how sitting in a room for three days is going to achieve 
something that doing the same for a shorter time + offline preparation 
can't.

>   Finally, as has been discussed previously (particularly during our
> peak, when we didn't fit in the hotels anymore), with wireless, people
> can occupy seats and not pay attention.

I have some pictures of people playing games on their laptops which 
prove that it's not the fault of the wireless network.  :-)

Much of what happens in sessions is very uninteresting, either for the 
people who've read the drafts OR the people who haven't. (Hopefully not 
both...)

Personally, I would be much happier to keep all the nasty details on 
the mailing lists and use the meeting sessions to talk about what the 
wg is doing for a larger audience. That would probably lead to good 
feedback from people who aren't on the wg mailinglist.

--Apple-Mail-11--395278246
content-type: application/pgp-signature; x-mac-type=70674453;
	name=PGP.sig
content-description: This is a digitally signed message part
content-disposition: inline; filename=PGP.sig
Content-Transfer-Encoding: 7bit

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

iD8DBQFBEnS0N+eEORsfxOYRAmUqAJoCBWfrQURPvThYGEOEe6DMNn2fnwCgi+LH
WdtyRLr1m1k2nuyFxt52H80=
=egYf
-----END PGP SIGNATURE-----

--Apple-Mail-11--395278246--



--===============0780617646==
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

--===============0780617646==--




From ietf-bounces@ietf.org  Thu Aug  5 23:23:59 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA08282;
	Thu, 5 Aug 2004 23:23:59 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BsvOV-0003RU-6M; Thu, 05 Aug 2004 23:27:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BsvIL-0004YH-Px; Thu, 05 Aug 2004 23:21:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BsvHV-0004QV-Bj
	for ietf@megatron.ietf.org; Thu, 05 Aug 2004 23:20:33 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA08154
	for <ietf@ietf.org>; Thu, 5 Aug 2004 23:20:30 -0400 (EDT)
Received: from sklave3.rackland.de ([213.133.101.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BsvL6-0003OB-TU
	for ietf@ietf.org; Thu, 05 Aug 2004 23:24:18 -0400
Received: from sputnik (uucp@localhost)
	by sklave3.rackland.de (8.12.10/8.12.10/Debian-1) with BSMTP id
	i763KT2A024759 for ietf@ietf.org; Fri, 6 Aug 2004 05:20:29 +0200
Received: (from hadmut@localhost)
	by sputnik.mobil.danisch.de (8.12.11/8.12.11/Debian-5) id
	i763KHlJ004157 for ietf@ietf.org; Fri, 6 Aug 2004 05:20:17 +0200
From: Hadmut Danisch <hadmut@danisch.de>
Date: Thu, 5 Aug 2004 20:20:17 -0700
To: ietf@ietf.org
Message-ID: <20040806032017.GA4132@danisch.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.6+20040523i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
Subject: Thursday late session slides?
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-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199

Hi,

are the slides of the thursday late session (spam, security,...) 
available?

regards
Hadmut

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


From ietf-bounces@ietf.org  Thu Aug  5 23:38:03 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA09001;
	Thu, 5 Aug 2004 23:38:02 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bsvc6-0003ej-L6; Thu, 05 Aug 2004 23:41:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BsvTu-0005z5-5a; Thu, 05 Aug 2004 23:33:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BsvR0-0005Wg-4G
	for ietf@megatron.ietf.org; Thu, 05 Aug 2004 23:30:22 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA08596
	for <ietf@ietf.org>; Thu, 5 Aug 2004 23:30:19 -0400 (EDT)
Received: from athena.nswc.navy.mil ([198.91.70.29])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BsvUc-0003XR-QA
	for ietf@ietf.org; Thu, 05 Aug 2004 23:34:07 -0400
Received: from relay.nswc.navy.mil (relay.nswc.navy.mil [128.38.1.41])
	by athena.nswc.navy.mil (8.11.6p3/8.11.6) with ESMTP id i763UK600680
	for <ietf@ietf.org>; Thu, 5 Aug 2004 23:30:20 -0400 (PDT)
Received: from relay.nswc.navy.mil (localhost [127.0.0.1])
	by relay.nswc.navy.mil (8.11.6p3/8.11.6) with ESMTP id i763UJv17194
	for <ietf@ietf.org>; Thu, 5 Aug 2004 23:30:19 -0400 (EDT)
Received: from titanic.nswc.navy.mil (titanic.nswc.navy.mil [128.38.42.115])
	by relay.nswc.navy.mil (8.11.6p3/8.11.6) with ESMTP id i763UJN17188
	for <ietf@ietf.org>; Thu, 5 Aug 2004 23:30:19 -0400 (EDT)
Received: from nswc.navy.mil (localhost [127.0.0.1])
	by titanic.nswc.navy.mil (8.11.7+Sun/8.9.3) with ESMTP id i763Tme06084
	for <ietf@ietf.org>; Thu, 5 Aug 2004 23:30:18 -0400 (EDT)
Message-ID: <4112FB05.9050208@nswc.navy.mil>
Date: Thu, 05 Aug 2004 23:29:09 -0400
From: "Karen O'Donoghue" <odonoghuekf@nswc.navy.mil>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.0.2) Gecko/20021120 Netscape/7.01
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf@ietf.org
References: <41104315.4070104@nswc.navy.mil>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by athena.nswc.navy.mil id
	i763UK600680
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36b1f8810cb91289d885dc8ab4fc8172
Content-Transfer-Encoding: quoted-printable
Subject: Re: dynamic keying via 802.1X on IETF wireless
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-Score: 0.0 (/)
X-Scan-Signature: 87a3f533bb300b99e2a18357f3c1563d
Content-Transfer-Encoding: quoted-printable

Folks,

While I realize there are only hours left, I have decided to
forward these directions anyway.

PEAP is working now, with a username/password of ietf60/ietf60.

So, a configuration how-to :

 >From the Start menu, select "Control Panel", followed by the "Network
Connections" icon.  In the "Network Connections" window, find the wireles=
s
interface that you intend to use.  Right click on the wireless interface,
and select properties.  In the properties window, select the "Wireless
Networks" tab.

Since the 802.1X wireless network is not broadcast, you may need to add i=
t
to your preferred networks.  To do this, click on the "Add..." button in
the "Preferred Networks" pane.  In the "Network name (SSID):" field, ente=
r
"ietf60-1x".  For "Network Authentication" be sure it is set to "Open",
and for "Data encryption:" set it to WEP.  Finally, make sure that the
check box for "The key is provided for me automatically" is checked.

Next, select the "Authentication" tab at the top of the window.  In the
authentication tab, be sure that "Enable IEEE 802.1x authentication for
this network" is checked.  Then, for EAP type select "Protected EAP
(PEAP)".

Then, click the Properties button below the "EAP Type" box.  In the
"Protected EAP Properties" uncheck the box for "Validate server
certificate".  Under "Select Authentication Method", select "Secured
password (EAP-MSCHAP v2)" then click on configure.   Uncheck the box for
"Automatically use my Windows logon name and password (and domain if
any)."

Select the "Ok" button for all windows that remain open.  If you are
within range of a wireless network that supports the iet60-1x network,
Windows should now attempt to authenticate.  During the authentication yo=
u
should see a bubble in the bottom right corner of your screen that
indicates that you need to select a certificate or other credentials to
log in.  Click on the bubble, and enter "ietf60" for both the username an=
d
password.  (Leave the Domain field blank.)  Finally, select Ok, and you
should now be authenticated.


Karen O'Donoghue wrote:
> Folks,
>=20
> We are experimenting with dynamic keying via 802.1X on the
> IETF wireless network.  You are invited to try this service if you
> wish. However, this isn't production so please do not ask for
> assistance from the terminal room help desk staff.  Help
> is available from the following (depending on schedule):
>=20
>    Chris Hessing, Chris.Hessing@utah.edu
>    Chris Elliott, chelliot@cisco.com
>=20
> Regards,
> Karen
>=20
> Anonymous 802.1X at IETF 60
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
> Chris Hessing, University of Utah/Open1x Project
>=20
> On the IETF 60 wireless network we are providing a separate SSID and=20
> VLAN that
> does anonymous 802.1X authentication with support for dynamic WEP. The=20
> advantage
> of using this is your wireless connection will be encrypted using per-u=
ser,
> per-session keys. In addition, if you choose to check the certificate=20
> provided
> by the network infrastructure during the authentication phase, you will=
=20
> also
> receive some assurance that you are connecting to the IETF 60 network=20
> and not
> some other network.
>=20
> If you would like to make use of the 802.1X wireless network, you will=20
> need to
> use the non-broadcast ESSID of =93ietf60-1x=94.
>=20
> You will also need an 802.1X supplicant that has support for TTLS-PAP. =
=20
> Windows
> XP/2000 users can download a plug-in to the native 802.1X client at
> http://www.secureW2.com.  Mac OS X users that are running OS 10.3+=20
> already have
> support included in the OS.  Directions are provided below. Linux users
> can download Xsupplicant from http://www.open1x.org.
>=20
> Your supplicant will receive a server certificate that is a test=20
> certificate.
> You can choose to configure your supplicant to accept this certificate=20
> the first
> time it is provided and check it thereafter, allowing your supplicant t=
o=20
> verify
> that you are connecting to the IETF network infrastructure, or you can=20
> choose to
> not validate the server certificate.
>=20
> The username and password that you use doesn't matter, as long as you f=
ill
> something in for both. If you have an option to fill in a domain please=
=20
> leave it
> blank.
>=20
> Note that the encryption type supported at this time is dynamic WEP. We=
 are
> not currenly supporting WPA/TKIP.
>=20
> We are currently working on supporting other EAP authentication types,=20
> including PEAP-GTC.
>=20
> MAC Users
> =3D=3D=3D=3D=3D=3D=3D=3D=3D
> 1. Open Internet Connect
>  2.  Under File "New 802.1X connect"
>      a. edit config
>          name - whatever you want
>          username - whatever you want
>          password - whatever you want
>          wireless network - ietf60-1x
>            authentication - only select TTLS
>               configure TTLS
>               TTLS Inner Authentication - PAP
>               no outer id
>         connect
> 3. Self signed cert - accept.
>=20


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


From ietf-bounces@ietf.org  Fri Aug  6 00:18:58 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA12057;
	Fri, 6 Aug 2004 00:18:58 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BswFi-0004dK-L6; Fri, 06 Aug 2004 00:22:46 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bsw9K-0005CU-6j; Fri, 06 Aug 2004 00:16:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bsw4q-0003Tb-4v
	for ietf@megatron.ietf.org; Fri, 06 Aug 2004 00:11:32 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA11254
	for <ietf@ietf.org>; Fri, 6 Aug 2004 00:11:29 -0400 (EDT)
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bsw8S-0004SA-53
	for ietf@ietf.org; Fri, 06 Aug 2004 00:15:17 -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
	i764BTnE019276
	for <ietf@ietf.org>; Fri, 6 Aug 2004 05:11:29 +0100 (BST)
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162])
	by magpie.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id FAA01185
	for <ietf@ietf.org>; Fri, 6 Aug 2004 05:11:26 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id i764BQ922954
	for ietf@ietf.org; Fri, 6 Aug 2004 05:11:26 +0100
Date: Fri, 6 Aug 2004 05:11:26 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: ietf@ietf.org
Message-ID: <20040806041126.GA22865@login.ecs.soton.ac.uk>
References: <41104315.4070104@nswc.navy.mil> <4112FB05.9050208@nswc.navy.mil>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4112FB05.9050208@nswc.navy.mil>
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-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Subject: Re: dynamic keying via 802.1X on IETF wireless
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-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f

On Thu, Aug 05, 2004 at 11:29:09PM -0400, Karen O'Donoghue wrote:
> Folks,
> 
> While I realize there are only hours left, I have decided to
> forward these directions anyway.
> 
> PEAP is working now, with a username/password of ietf60/ietf60.
> 
> So, a configuration how-to :
> 
> From the Start menu, select "Control Panel", followed by ...

I am having trouble finding the Start Menu.  Is it the blue Apple icon
in the top left of my screen? :)

That aside, I associated OK with 8021.x to your ssid using MacOS/X 10.3.4.

You need to open Internet Connect, select the 802.1x menu, and plug the
appropriate configurations in there (ietf60-1x as ssid, ietf60/ietf60
as passwd, and set PEAP and MSCHAPv2 as preferred).  Looks to be rather
simpler than the process involving the Start Menu...

However, the Mac approach appears to force you to accept/review the 
the presented server certificate(s) at some point.  I saw two:
	- test.server.some.company.com
	- OSC Test CA

Neither looked like anything "official" (as much as your test is official :)

Anyway, thanks for setting up the test.

Tim

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


From ietf-bounces@ietf.org  Fri Aug  6 00:50:10 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA14290;
	Fri, 6 Aug 2004 00:50:10 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bswjv-0005Ex-6f; Fri, 06 Aug 2004 00:53:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BswYK-00013E-Re; Fri, 06 Aug 2004 00:42:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BswTN-0000Ik-Iw
	for ietf@megatron.ietf.org; Fri, 06 Aug 2004 00:36:53 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA13448
	for <ietf@ietf.org>; Fri, 6 Aug 2004 00:36:50 -0400 (EDT)
Received: from imh.informatik.uni-bremen.de ([134.102.224.4]
	helo=informatik.uni-bremen.de)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BswWz-00050B-Nq
	for ietf@ietf.org; Fri, 06 Aug 2004 00:40:39 -0400
Received: from [IPv6:::1] (imh [134.102.224.4])
	by informatik.uni-bremen.de (8.12.11/8.12.11) with ESMTP id
	i764adI3015644; Fri, 6 Aug 2004 06:36:42 +0200 (MEST)
In-Reply-To: <20040806041126.GA22865@login.ecs.soton.ac.uk>
References: <41104315.4070104@nswc.navy.mil> <4112FB05.9050208@nswc.navy.mil>
	<20040806041126.GA22865@login.ecs.soton.ac.uk>
Mime-Version: 1.0 (Apple Message framework v618)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <36DF8860-E762-11D8-89A9-000A95DC4DB6@tzi.org>
Content-Transfer-Encoding: 7bit
From: Carsten Bormann <cabo@tzi.org>
Date: Thu, 5 Aug 2004 21:36:42 -0700
To: Tim Chown <tjc@ecs.soton.ac.uk>
X-Mailer: Apple Mail (2.618)
X-Virus-Scanned: by AMaViS/Sophos at informatik.uni-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Content-Transfer-Encoding: 7bit
Cc: Carsten Bormann <cabo@tzi.org>, ietf@ietf.org
Subject: Re: dynamic keying via 802.1X on IETF wireless
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-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Content-Transfer-Encoding: 7bit

Interestingly, on the .1X SSID, I get 14 % loss and delays up to 8000 
ms (!).
The open SSID is about 0 % loss (didn't wait for the first loss long 
enough) and 60 ms on average.

Just a data point why I'm back in the open net.

Gruesse, Carsten


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


From ietf-bounces@ietf.org  Fri Aug  6 01:09:35 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA15441;
	Fri, 6 Aug 2004 01:09:35 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bsx2f-0005ce-KB; Fri, 06 Aug 2004 01:13:21 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bswtc-0004S2-ED; Fri, 06 Aug 2004 01:04:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BswqZ-0004Bt-5t
	for ietf@megatron.ietf.org; Fri, 06 Aug 2004 01:00:51 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA15188
	for <ietf@ietf.org>; Fri, 6 Aug 2004 01:00:50 -0400 (EDT)
Received: from ckmso2.att.com ([209.219.209.75] helo=ckmso2.proxy.att.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bswu9-0005Tl-CP
	for ietf@ietf.org; Fri, 06 Aug 2004 01:04:36 -0400
Received: from maillennium.att.com ([135.25.114.99])
	by ckmso2.proxy.att.com (AT&T IPNS/MSO-5.5) with ESMTP id
	i7650Gff027203 for <ietf@ietf.org>; Fri, 6 Aug 2004 01:00:16 -0400
Received: from [135.210.112.16] (unknown[135.210.112.16](misconfigured sender))
	by maillennium.att.com (mailgw1) with ESMTP
	id <20040806050022gw1002euf6e> (Authid: tony);
	Fri, 6 Aug 2004 05:00:23 +0000
Message-ID: <41131059.6000002@att.com>
Date: Fri, 06 Aug 2004 01:00:09 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7) Gecko/20040616
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: 7bit
Subject: T-shirts, and some suggestions for future 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-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Content-Transfer-Encoding: 7bit

I know, this isn't the most important issue in the world. But, I want to 
say that I miss the IETF meeting T-shirts. As confirmed by Harald at 
tonight's plenary, the T-shirts are normally paid for by the sponsor. 
And since we don't have a sponsor here, there was no T-shirt.

The first time in recent years that we almost didn't have a sponsor was 
in Adelaide (IETF 47, March 2000). We got down there, there were 
problems with the original sponsor and lots of scrambling occurred. 
Among the other things that occured was that there was no T-shirt handed 
out when we registered. (Later on in the week, the people who stayed to 
the end of the plenary were surprised with shirts, collared even. But 
that doesn't the affect the rest of the story.)

So, what happened? In true IETF fashion, a bar BOF met, designed a 
T-shirt, and made arrangements with a T-shirt shop a couple of blocks 
from the convention center. Those people who wanted a T-shirt walked 
over there, picked a T-shirt color, put in an order, paid their money, 
and got a shirt a couple of days later. (It's definitely one of my most 
favorite IETF shirts.) I don't know exactly how many people wound up 
ordering their shirt this way, but I know the owner worked numerous 
overtime hours to meet the demand.

A few salient points can be garnered from the above: many people are 
willing to pay extra to get their IETF T-shirt, and there are people who 
are willing to work on T-shirt designs.

In DC, IETF 61, we have a sponsor scheduled. So we'll likely have 
T-shirts. Thank you Alcatel!

Here's a suggestion for IETF 61: modify the registration web page to let 
people specify the size of the T-shirt they'd like to get. Usually, a 
sponsor has to estimate the number of people who want each T-shirt size. 
This leads to overbuys of some sizes and underbuys of other sizes. And 
it leads to some people being dissatisfied with the sizes that they were 
forced to receive.

Continuing this thought, here's a suggestion for the next IETF meeting 
that doesn't have a sponsor, whether it's IETF 62 or some future 
meeting: Take that part of the registration form that asks for T-shirt 
size and add one more choice: none. Then charge the people who pick a 
T-shirt an extra $15 to cover the cost of the shirt, and those that 
don't want it won't pay for it.

Then beforehand, set up a mailing list for those interested in designing 
the shirt, exchanging designs, and picking one out. I'm sure you'll get 
enough takers to do it.

	Tony Hansen
	tony+ietf@maillennium.att.com

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


From ietf-bounces@ietf.org  Fri Aug  6 01:24:46 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA16204;
	Fri, 6 Aug 2004 01:24:45 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BsxHL-0005s8-AW; Fri, 06 Aug 2004 01:28:32 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BsxBM-0007EF-V5; Fri, 06 Aug 2004 01:22:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BsxAt-00077c-7s
	for ietf@megatron.ietf.org; Fri, 06 Aug 2004 01:21:51 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA16124
	for <ietf@ietf.org>; Fri, 6 Aug 2004 01:21:50 -0400 (EDT)
Received: from sklave3.rackland.de ([213.133.101.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BsxEV-0005q3-OJ
	for ietf@ietf.org; Fri, 06 Aug 2004 01:25:37 -0400
Received: from sputnik (uucp@localhost)
	by sklave3.rackland.de (8.12.10/8.12.10/Debian-1) with BSMTP id
	i765LmMp027481 for ietf@ietf.org; Fri, 6 Aug 2004 07:21:48 +0200
Received: (from hadmut@localhost)
	by sputnik.mobil.danisch.de (8.12.11/8.12.11/Debian-5) id
	i765LaHm006609 for ietf@ietf.org; Fri, 6 Aug 2004 07:21:36 +0200
From: Hadmut Danisch <hadmut@danisch.de>
Date: Thu, 5 Aug 2004 22:21:36 -0700
To: ietf@ietf.org
Message-ID: <20040806052136.GA6116@danisch.de>
References: <41131059.6000002@att.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <41131059.6000002@att.com>
User-Agent: Mutt/1.5.6+20040523i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Subject: Re: T-shirts, and some suggestions for future 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-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32

On Fri, Aug 06, 2004 at 01:00:09AM -0400, Tony Hansen wrote:
> I know, this isn't the most important issue in the world. But, I want to 
> say that I miss the IETF meeting T-shirts. As confirmed by Harald at 
> tonight's plenary, the T-shirts are normally paid for by the sponsor. 
> And since we don't have a sponsor here, there was no T-shirt.

Why always T-Shirts? Everyone gives T-Shirts. I have tons of
T-Shirts from conventions and conferences.

Why not anything different at every meeting? Socks, ties, caps, 
jumpers, blousons, jackets, sunglasses, swimsuits, undies...

After attending IETF meetings for 2-3 years you've got a complete 
IETF outfit.

:-)

Hadmut



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


From ietf-bounces@ietf.org  Fri Aug  6 01:44:22 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA18791;
	Fri, 6 Aug 2004 01:44:22 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BsxaI-0006IJ-7T; Fri, 06 Aug 2004 01:48:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BsxRB-0001Jd-VW; Fri, 06 Aug 2004 01:38:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BsxOj-0000nL-Ee
	for ietf@megatron.ietf.org; Fri, 06 Aug 2004 01:36:09 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA18205
	for <ietf@ietf.org>; Fri, 6 Aug 2004 01:36:08 -0400 (EDT)
Received: from mail.consulintel.es ([213.172.48.142] helo=consulintel.es)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BsxSM-000672-Pw
	for ietf@ietf.org; Fri, 06 Aug 2004 01:39:55 -0400
Received: from consulintel02 by consulintel.es (MDaemon.PRO.v7.1.2.R)
	with ESMTP id md50000180891.msg
	for <ietf@ietf.org>; Fri, 06 Aug 2004 07:38:53 +0200
Message-ID: <05db01c47b77$2f68ab90$14848182@consulintel.es>
From: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
References: <41131059.6000002@att.com>
Date: Thu, 5 Aug 2004 22:35:27 -0700
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.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Spam-Processed: consulintel.es, Fri, 06 Aug 2004 07:38:53 +0200
	(not processed: message from valid local sender)
X-MDRemoteIP: 130.129.133.186
X-Return-Path: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
X-MDAV-Processed: consulintel.es, Fri, 06 Aug 2004 07:38:57 +0200
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
Content-Transfer-Encoding: quoted-printable
Subject: Re: T-shirts, and some suggestions for future ietf meetings
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-Score: 0.0 (/)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4
Content-Transfer-Encoding: quoted-printable

Hi,

I agree, but probably is less than $15.

What I don't agree is that we don't have sponsors. That's not true, let's say we don't want to accept sponsors ?

I offered myself for more than two years to host a meeting in Madrid and another one in Barcelona. I've arranged for the sponsors, following the instructions regarding hosting a meeting in the IETF site.

Finally the Secretariat staff visited the proposed venue in Madrid, a very nice hotel 10 minutes from downtown with public transport, and around the same time from the airport. Then confirmed that the venue is the best they have ever seen, not a surprise as this is probably the last big hotel build in Europe (less than 1.5 years ago), with very big meeting rooms and capacity for up to 10.000 people in meetings (enough for us).

The only complain was not being in downtown. Also something about the restaurants nearby, but there are a few at walking distance, and the hotel has enough meeting rooms and kitchens to add as many additional restaurants as tastes we may have !

Now, I'm somehow (very) disappointed, because San Diego is very nice, yes, but we aren't in downtown, we don't have food choices, and is VERY expensive compared to Madrid. So what's going on ?

In Madrid, we have public transport every 10 minutes in the hotel door (yes the door, not away from that), I also offered a free shuttle, and taxis are quite cheap. There is also a free shuttle to the airport (it takes 12-15 minutes).

So it was a kind of excuse ?

By the way, the hotel has free IPv6 connectivity in every room, since we installed it in May 2003 (first one in the world as I know).

I think the venue selection process is somehow obscure and not democratic. But may be is my view only :-(((( ... I already mention this previously in this list, but it seems we don't care. Just wondering if is my wrong perception ?

Regards,
Jordi

PS: And yes, we of course plan to provide a nice t-shirt !

----- Original Message -----=20
From: "Tony Hansen" <tony@att.com>
To: <ietf@ietf.org>
Sent: Thursday, August 05, 2004 10:00 PM
Subject: T-shirts, and some suggestions for future ietf meetings


> I know, this isn't the most important issue in the world. But, I want to=20
> say that I miss the IETF meeting T-shirts. As confirmed by Harald at=20
> tonight's plenary, the T-shirts are normally paid for by the sponsor.=20
> And since we don't have a sponsor here, there was no T-shirt.
>=20
> The first time in recent years that we almost didn't have a sponsor was=20
> in Adelaide (IETF 47, March 2000). We got down there, there were=20
> problems with the original sponsor and lots of scrambling occurred.=20
> Among the other things that occured was that there was no T-shirt handed=20
> out when we registered. (Later on in the week, the people who stayed to=20
> the end of the plenary were surprised with shirts, collared even. But=20
> that doesn't the affect the rest of the story.)
>=20
> So, what happened? In true IETF fashion, a bar BOF met, designed a=20
> T-shirt, and made arrangements with a T-shirt shop a couple of blocks=20
> from the convention center. Those people who wanted a T-shirt walked=20
> over there, picked a T-shirt color, put in an order, paid their money,=20
> and got a shirt a couple of days later. (It's definitely one of my most=20
> favorite IETF shirts.) I don't know exactly how many people wound up=20
> ordering their shirt this way, but I know the owner worked numerous=20
> overtime hours to meet the demand.
>=20
> A few salient points can be garnered from the above: many people are=20
> willing to pay extra to get their IETF T-shirt, and there are people who=20
> are willing to work on T-shirt designs.
>=20
> In DC, IETF 61, we have a sponsor scheduled. So we'll likely have=20
> T-shirts. Thank you Alcatel!
>=20
> Here's a suggestion for IETF 61: modify the registration web page to let=20
> people specify the size of the T-shirt they'd like to get. Usually, a=20
> sponsor has to estimate the number of people who want each T-shirt size.=20
> This leads to overbuys of some sizes and underbuys of other sizes. And=20
> it leads to some people being dissatisfied with the sizes that they were=20
> forced to receive.
>=20
> Continuing this thought, here's a suggestion for the next IETF meeting=20
> that doesn't have a sponsor, whether it's IETF 62 or some future=20
> meeting: Take that part of the registration form that asks for T-shirt=20
> size and add one more choice: none. Then charge the people who pick a=20
> T-shirt an extra $15 to cover the cost of the shirt, and those that=20
> don't want it won't pay for it.
>=20
> Then beforehand, set up a mailing list for those interested in designing=20
> the shirt, exchanging designs, and picking one out. I'm sure you'll get=20
> enough takers to do it.
>=20
> Tony Hansen
> tony+ietf@maillennium.att.com
>=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-bounces@ietf.org  Fri Aug  6 02:22:18 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA04722;
	Fri, 6 Aug 2004 02:22:18 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BsyB2-0006tQ-9W; Fri, 06 Aug 2004 02:26:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BsxyA-0001wb-Po; Fri, 06 Aug 2004 02:12:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BsxwW-0001Eq-9e
	for ietf@megatron.ietf.org; Fri, 06 Aug 2004 02:11:04 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00882
	for <ietf@ietf.org>; Fri, 6 Aug 2004 02:11:03 -0400 (EDT)
Received: from p2.piuha.net ([131.160.192.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bsy09-0006iA-8A
	for ietf@ietf.org; Fri, 06 Aug 2004 02:14:50 -0400
Received: from piuha.net (p2.piuha.net [131.160.192.2])
	by p2.piuha.net (Postfix) with ESMTP id 485E589849;
	Fri,  6 Aug 2004 09:10:54 +0300 (EEST)
Message-ID: <411320E2.6060608@piuha.net>
Date: Fri, 06 Aug 2004 09:10:42 +0300
From: Jari Arkko <jari.arkko@piuha.net>
Organization: None
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7b) Gecko/20040316
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
References: <41131059.6000002@att.com>
	<05db01c47b77$2f68ab90$14848182@consulintel.es>
In-Reply-To: <05db01c47b77$2f68ab90$14848182@consulintel.es>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: T-shirts, and some suggestions for future ietf meetings
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: jari.arkko@piuha.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Content-Transfer-Encoding: 7bit

JORDI PALET MARTINEZ wrote:

> By the way, the hotel has free IPv6 connectivity in every room, since we installed it in May 2003 (first one in the world as I know).
(snip)
> PS: And yes, we of course plan to provide a nice t-shirt !

OK, I'm convinced. Lets go there as soon as possible.

--Jari

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


From ietf-bounces@ietf.org  Fri Aug  6 02:50:47 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA06760;
	Fri, 6 Aug 2004 02:50:46 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bsycc-0007Mr-Gp; Fri, 06 Aug 2004 02:54:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BsyVl-0002Vn-2B; Fri, 06 Aug 2004 02:47:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BsyUy-0002L2-8W
	for ietf@megatron.ietf.org; Fri, 06 Aug 2004 02:46:40 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA06603
	for <ietf@ietf.org>; Fri, 6 Aug 2004 02:46:39 -0400 (EDT)
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BsyYb-0007JC-HV
	for ietf@ietf.org; Fri, 06 Aug 2004 02:50:26 -0400
Received: from magpie.ecs.soton.ac.uk (magpie.ecs.soton.ac.uk [152.78.68.131])
	by raven.ecs.soton.ac.uk (8.12.10/8.12.10) with ESMTP id
	i766kZnE022269
	for <ietf@ietf.org>; Fri, 6 Aug 2004 07:46:35 +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 HAA02390
	for <ietf@ietf.org>; Fri, 6 Aug 2004 07:46:32 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id i766kWQ24998
	for ietf@ietf.org; Fri, 6 Aug 2004 07:46:32 +0100
Date: Fri, 6 Aug 2004 07:46:32 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: ietf@ietf.org
Message-ID: <20040806064632.GB24906@login.ecs.soton.ac.uk>
References: <41131059.6000002@att.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <41131059.6000002@att.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-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Subject: Re: T-shirts, and some suggestions for future 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-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034

On Fri, Aug 06, 2004 at 01:00:09AM -0400, Tony Hansen wrote:
> I know, this isn't the most important issue in the world. But, I want to 
> say that I miss the IETF meeting T-shirts. As confirmed by Harald at 
> tonight's plenary, the T-shirts are normally paid for by the sponsor. 
> And since we don't have a sponsor here, there was no T-shirt.
> 
> Here's a suggestion for IETF 61: modify the registration web page to let 
> people specify the size of the T-shirt they'd like to get. Usually, a 
> sponsor has to estimate the number of people who want each T-shirt size. 
> This leads to overbuys of some sizes and underbuys of other sizes. And 
> it leads to some people being dissatisfied with the sizes that they were 
> forced to receive.
> 
> Continuing this thought, here's a suggestion for the next IETF meeting 
> that doesn't have a sponsor, whether it's IETF 62 or some future 
> meeting: Take that part of the registration form that asks for T-shirt 
> size and add one more choice: none. Then charge the people who pick a 
> T-shirt an extra $15 to cover the cost of the shirt, and those that 
> don't want it won't pay for it.
> 
> Then beforehand, set up a mailing list for those interested in designing 
> the shirt, exchanging designs, and picking one out. I'm sure you'll get 
> enough takers to do it.

Excellent suggestions.

I'd happily pay $15US for a t-shirt, each time, sponsor or no sponsor.

Tim

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


From ietf-bounces@ietf.org  Fri Aug  6 03:03:34 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA07431;
	Fri, 6 Aug 2004 03:03:34 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bsyp0-0007af-LU; Fri, 06 Aug 2004 03:07:22 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BsycU-0003nS-MH; Fri, 06 Aug 2004 02:54:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bsybv-0003Yi-34
	for ietf@megatron.ietf.org; Fri, 06 Aug 2004 02:53:51 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA06964
	for <ietf@ietf.org>; Fri, 6 Aug 2004 02:53:50 -0400 (EDT)
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BsyfZ-0007Qp-IB
	for ietf@ietf.org; Fri, 06 Aug 2004 02:57: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 i766shMG006740;
	Fri, 6 Aug 2004 08:54:43 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <20040806052136.GA6116@danisch.de>
References: <41131059.6000002@att.com> <20040806052136.GA6116@danisch.de>
Mime-Version: 1.0 (Apple Message framework v618)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <582D258C-E775-11D8-805E-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Fri, 6 Aug 2004 08:53:38 +0200
To: Hadmut Danisch <hadmut@danisch.de>
X-Mailer: Apple Mail (2.618)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: T-shirts, and some suggestions for future 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-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit

On 6-aug-04, at 7:21, Hadmut Danisch wrote:

> Why always T-Shirts? Everyone gives T-Shirts. I have tons of
> T-Shirts from conventions and conferences.

> Why not anything different at every meeting? Socks, ties, caps,
> jumpers, blousons, jackets, sunglasses, swimsuits, undies...

Actually I got some Cisco at one of the recent RIPE meetings. ("Behind 
every great network".) This is of course a smart move because most 
people have tons of tshirts so they wear a different one every day. But 
they only have one set of Cisco underpants so they wear those for the 
entire week!


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


From ietf-bounces@ietf.org  Fri Aug  6 03:27:35 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA08705;
	Fri, 6 Aug 2004 03:27:35 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BszCF-0007yE-7U; Fri, 06 Aug 2004 03:31:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bsz6U-0007dM-08; Fri, 06 Aug 2004 03:25:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bsz09-0006w2-27
	for ietf@megatron.ietf.org; Fri, 06 Aug 2004 03:18:53 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA08259
	for <ietf@ietf.org>; Fri, 6 Aug 2004 03:18:51 -0400 (EDT)
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65]
	helo=arneill-py.sacramento.ca.us)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bsz3n-0007qi-Ob
	for ietf@ietf.org; Fri, 06 Aug 2004 03:22:40 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Date: Fri, 6 Aug 2004 00:18:19 -0700
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B0DB32F@server2003.arneill-py.sacramento.ca.us>
Thread-Topic: T-shirts, and some suggestions for future ietf meetings
thread-index: AcR7g3UU0c37CsgQSQuUqMzmfSQkmwAAVWqg
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "Iljitsch van Beijnum" <iljitsch@muada.com>,
        "Hadmut Danisch" <hadmut@danisch.de>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
Subject: RE: T-shirts, and some suggestions for future 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-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: quoted-printable

>> Hadmut Danisch wrote:
>> Why always T-Shirts? Everyone gives T-Shirts. I have
>> tons of T-Shirts from conventions and conferences.
>> Why not anything different at every meeting? Socks,
>> ties, caps, jumpers, blousons, jackets, sunglasses,

_ties_? Why not a designer suit while you're at it.

Sandals. We want IETF sandals.

>> undies...

> Iljitsch van Beijnum wrote:
> Actually I got some Cisco at one of the recent RIPE
> meetings. ("Behind every great network".) This is of
> course a smart move because most people have tons of
> tshirts so they wear a different one every day. But
> they only have one set of Cisco underpants so they
> wear those for the entire week!

Ah. That explains something I was wondering about.

Michel.


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


From ietf-bounces@ietf.org  Fri Aug  6 08:31:19 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA23584;
	Fri, 6 Aug 2004 08:31:19 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bt3w3-0004Mb-Vy; Fri, 06 Aug 2004 08:35:10 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bt3ph-0004Fr-PP; Fri, 06 Aug 2004 08:28:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bsq4c-0007mO-Cx
	for ietf@megatron.ietf.org; Thu, 05 Aug 2004 17:46:54 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17506
	for <ietf@ietf.org>; Thu, 5 Aug 2004 17:46:51 -0400 (EDT)
Received: from hades.jabber.org ([208.245.212.109])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bsq8A-0005iO-Ua
	for ietf@ietf.org; Thu, 05 Aug 2004 17:50:36 -0400
Received: by hades.jabber.org (Postfix, from userid 1005)
	id B267064041; Thu,  5 Aug 2004 16:46:21 -0500 (CDT)
Date: Thu, 5 Aug 2004 16:46:20 -0500
From: Peter Saint-Andre <stpeter@jabber.org>
To: ietf@ietf.org
Message-ID: <20040805214620.GA3500@jabber.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.4i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
X-Mailman-Approved-At: Fri, 06 Aug 2004 08:28:24 -0400
Subject: IANA and RFC office hours
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-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22

It seems that IETF 60 represents the first time that representatives of
the IANA and the RFC Editor have held in-person "office hours" during an
IETF meeting.  I for one found that this enabled me to:

1. Follow up on outstanding issues
2. Inquire about the status of documents in the RFC Editor queue
3. Gain insight into the processes of the IANA and the RFC Editor
4. Determine how I as a document editor can provide information to 
   the IANA and RFC Editor in the most useful manner
5. Get to know IANA and RFC Editor folks in a more personal way

I feel that all of these will make my interactions with the IANA and
the RFC Editor more productive and more enjoyable for all concerned,
and I strongly encourage the relevant organizations to continue the
practice of IANA and RFC Editor office hours at future IETF meetings.

Peter

-- 
Peter Saint-Andre
Jabber Software Foundation
http://www.jabber.org/people/stpeter.php


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


From ietf-bounces@ietf.org  Fri Aug  6 08:36:56 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA23912;
	Fri, 6 Aug 2004 08:36:56 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bt41U-0004Tc-MQ; Fri, 06 Aug 2004 08:40:46 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bt3pi-0004G0-O4; Fri, 06 Aug 2004 08:28:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BswdY-0001fs-2e
	for ietf@megatron.ietf.org; Fri, 06 Aug 2004 00:47:24 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA14141
	for <ietf@ietf.org>; Fri, 6 Aug 2004 00:47:20 -0400 (EDT)
Received: from zak.ecotroph.net ([216.93.164.123])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bswh8-0005CE-Hv
	for ietf@ietf.org; Fri, 06 Aug 2004 00:51:09 -0400
Received: from [130.129.129.58] ([::ffff:130.129.129.58])
	(AUTH: PLAIN anewton, SSL: TLSv1/SSLv3,128bits,RC4-SHA)
	by zak.ecotroph.net with esmtp; Fri, 06 Aug 2004 00:47:19 -0400
	id 00197679.41130D57.000045AE
Mime-Version: 1.0 (Apple Message framework v618)
Content-Transfer-Encoding: 7bit
Message-Id: <AD68B55C-E763-11D8-A1FF-000A95B3BA44@hxr.us>
Content-Type: text/plain; charset=US-ASCII; format=flowed
To: ietf@ietf.org
From: Andrew Newton <andy@hxr.us>
Date: Fri, 6 Aug 2004 00:47:10 -0400
X-Mailer: Apple Mail (2.618)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d62ab47271805379d7172ee693a45db
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Fri, 06 Aug 2004 08:28:24 -0400
Subject: list address for MASS
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-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Content-Transfer-Encoding: 7bit

Can anyone provide the list/subscription address for MASS:
http://www.ietf.org/ietf/04aug/mass.txt

-andy


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


From ietf-bounces@ietf.org  Fri Aug  6 10:02:21 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27498;
	Fri, 6 Aug 2004 10:02:21 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bt5MK-0005lu-9N; Fri, 06 Aug 2004 10:06:13 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bt5F2-0007Nm-P5; Fri, 06 Aug 2004 09:58:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bt5Br-0006tb-Ht
	for ietf@megatron.ietf.org; Fri, 06 Aug 2004 09:55:23 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA27149
	for <ietf@ietf.org>; Fri, 6 Aug 2004 09:55:22 -0400 (EDT)
Received: from one.elistx.com ([67.154.239.218])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bt5FY-0005dz-VQ
	for ietf@ietf.org; Fri, 06 Aug 2004 09:59:14 -0400
Received: from localhost (one.elistx.com [209.116.252.130])
	by elistx.com (PMDF V6.0-025 #44856) with ESMTP id
	<0I210044D2OKTC@elistx.com>
	for ietf@ietf.org; Fri, 06 Aug 2004 09:55:33 -0400 (EDT)
Date: Fri, 06 Aug 2004 09:54:24 -0400 (EDT)
From: James M Galvin <galvin+ietf@elistx.com>
In-reply-to: <AD68B55C-E763-11D8-A1FF-000A95B3BA44@hxr.us>
X-X-Sender: galvin@three.elistx.com
To: Andrew Newton <andy@hxr.us>
Message-id: <Pine.BSF.4.43.0408060952420.9138-100000@three.elistx.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: ietf@ietf.org
Subject: Re: list address for MASS
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-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab


    ietf-mailsig [ -request ] @imc.org

Jim

On Fri, 6 Aug 2004, Andrew Newton wrote:

    Date: Fri, 06 Aug 2004 00:47:10 -0400
    From: Andrew Newton <andy@hxr.us>
    To: ietf@ietf.org
    Subject: list address for MASS

    Can anyone provide the list/subscription address for MASS:
    http://www.ietf.org/ietf/04aug/mass.txt

    -andy


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


From ietf-bounces@ietf.org  Fri Aug  6 10:15:44 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28865;
	Fri, 6 Aug 2004 10:15:44 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bt5ZH-0005xu-LP; Fri, 06 Aug 2004 10:19:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bt5Pe-00049Z-Sa; Fri, 06 Aug 2004 10:09:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bt5L9-0002RR-PM
	for ietf@megatron.ietf.org; Fri, 06 Aug 2004 10:04:59 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27791
	for <ietf@ietf.org>; Fri, 6 Aug 2004 10:04:58 -0400 (EDT)
Received: from rwcrmhc13.comcast.net ([204.127.198.39])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bt5Or-0005oO-8e
	for ietf@ietf.org; Fri, 06 Aug 2004 10:08:50 -0400
Received: from dfnjgl21
	(opene-130-129-130-140.ietf60.ietf.org[130.129.130.140])
	by comcast.net (rwcrmhc13) with SMTP id <20040806140427015008525me>
	(Authid: sdawkins@comcast.net); Fri, 6 Aug 2004 14:04:27 +0000
Message-ID: <013701c47bbe$49450800$1b878182@DFNJGL21>
From: "Spencer Dawkins" <spencer@mcsr-labs.org>
To: "IETF General Discussion Mailing List" <ietf@ietf.org>
Date: Fri, 6 Aug 2004 07:04:27 -0700
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e535e8fdae689580ce57283401d548ee
Subject: First hack at Thursday plenary notes
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Spencer Dawkins <spencer@mcsr-labs.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0554664395=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c5b976cb26c967a52d72d6069c7fc54c

This is a multi-part message in MIME format.

--===============0554664395==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0134_01C47B83.9C96D780"

This is a multi-part message in MIME format.

------=_NextPart_000_0134_01C47B83.9C96D780
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

1930-2200 Plenary - IETF Planning Meeting - Grande Ballroom

- Welcome, and introduction - Leslie Daigle

- IRTF presentation: ASRG Report

Have broken problem domain into pieces, some closer to IETF than others

Working on drafts for BCPs for ISPs that want to do the right thing =
(DNSBL/DNSWL, port 25 blocking), but

we've never written down our best current practices before

Looking at filtering rule exchange, looking at formats for abuse reports

Would like to develop common interfaces for reputation systems

Not defining SPAM, not doing challenge/response, not doing e-postage, =
not doing replacements for SMTP

Something like 34 anti-SPAM groups working now, including ITU-T - and =
the standards process comparison is scary...

SPAM is bad, solutions are hard, we can make incremental progress

Dave Crocker - there's a spec in CSV proposal on reputation systems - =
can people look at it and comment?

http://asrg.sp.am

Brian Carpenter - fixing SPAM in two years? How long, really? - we'll =
never solve the SPAM problem,

but in two years we could have a handle on it - all the way to never, of =
course, but in five years,

people will have given up on e-mail

Scott Bradner - ITU-T asking how they can cooperate with us

- Technical issue: IAB Security workshop retrospective - Bernard Aboba, =
Pete Resnick, Eric Rescola

Thanks to Steve Bellovin, who actually ATTENDED the workshop :-}

In 1997 - two years before the CERT rate of increase went vertical

Trends then - rate of attacks increasing, attackers getting smarter

Common wisdom - build in security, get more serious about security, =
IPsec not a panacea - but no mechanisms

Trends now - scope and sophistication of attacks continues to grow, =
money now a motivator, peer-to-peer and multi-party

protocols on the rise, authorization matters now, most vulnerabilities =
are now application-level - threat model is evolving

Can an attacker make money? Can an attacker cause havoc on =
regional/national scale?

Core mechanisms have not fared well (DNSSEC, IPsec/ISAKMP, S/MIME) - =
non-core mechanisms more successful

Ease of use is significant, especially ease of deployment

SASL, EAP easier for developers

Coordination requirement makes it harder to deploy a mechanism, even =
within a company

Don't repeat lessons of ISAKMP with GSS-API, EAP, SASL

1997 missing pieces were object security, secure e-mail, routing =
security

Missing pieces now are peer-to-peer, multiparty, DDoS, Phishing

Look past today's problem, document your dependencies, understand =
large-scale risks

Monetary incentives? Financial crimes (credit card theft, etc.)

Spammers paying bounty on compromised systems

Paying for an arbitrary attack

Spammers are trying to sell things with spambots, too

Eliot Lear - smart card reader, smart card, contract, and PIN for just =
one account - problem has usability and API

issues, users are awash in keys. Broader than IETF, how to make =
progress?

Ted Hardie - DDoS categories - now there IS a different between =
slash-dot and DDoS - behaving like legitimate users,=20

SYN flooding isn't legitimate, but some attacks are - include attack =
detection profiles in protocol definitions? - we do

need to give a different type of security guidance

Threat model hasn't changed - it's always about money, the IETF could =
usefully take security seriously and focus on

infrastructure security. We aren't going to fix application security in =
the IETF (we've known about buffer overflows

for a while now) - attackers aren't attacking you, they're now attacking =
regions and nations - security issues have

moved into applications, when they weren't there before. Perfectly valid =
SMTP clients are doing a lot of the damage.

Bill Summerfeld - Zombie armies give attackers a lot more resources than =
you think

Dave Crocker - scaling is the only problem on the Internet, what does =
that mean in this situation? This is complex and

we don't have a good track record on complex problems. How do we get a =
dialog going?

IPsec and DNSSEC haven't lived up to expectations - why not? Where's the =
lessons learned, so we learn lessons? -=20

deployment does matter - will IPsec and DNSSEC ever live up to =
expectations? - People here have been saying APIs would

help a lot, maybe they're right

In the mid-1980s, no one had a clue about DNS at all, much less about =
security, we think we got it right this time, three

designs later. Operator involvement will be critical, because we didn't =
have it the first two times. And we tried. People

still ignore security advisors today. - Sometimes laziness is rational. =
Putting stuff into standards isn't implementing it.

IETF solution diversity is amazing, but they have been designed =
piecemeal.

Application security has been around for a long time, we've just ignored =
it. Operational information needs to come down the=20

stack. - Application security problems have been around, it's just =
starting to hurt.=20

Abstract interfaces are defined for the successful mechanisms. IPsec =
doesn't have an abstract interface. - IPsec doesn't

have protocol problems, it has API problems.

- IETF Reorg: Status report - Harald Alvestrand

What we want the IETF to be doesn't change from meeting to meeting - =
mission statement is now approved by IETF

PROTO, ICAR, NEWTRK are making progress, and some small things are done

Five procedural BCPs and an Experimental RFC approved since Seoul

IESG is becoming more effective - more focus on "critical" issues, =
better edit cycles, better throughput

Still working to improve the process

Change efforts quieting down - are people giving up, becoming happier, =
or going back to technical work?

Will focus on IESG processing (tracker toolmaking, reasons to block, WG =
chair shepherding) and ICAR (looking for=20

volunteers, THIS MEANS YOU)

How to measure the effects of what we've done? even subjectively

Dave Crocker - things are getting better, this is good, two years ago =
things were not good. Can we check on

how people are feeling?

Scott Bradner - will discussion on "why to block" be public? - yes, but =
we won't promise a date

Brian Carpenter - customer satisfaction survey would be nice but =
annoying. We need to tell the world we think our

problems are getting smaller

Attendance drop-off has stopped dropping

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

Fred Baker - we're at the size of the Adelaide meeting in 2000, and the =
average meeting

size in 1998 - plenaries involve less vegetable-throwing now, and =
plenaries started with a LOT of vegetable-throwing

post-Kobe. The IETF is moving beyond many of the problems we've had.

Sue Hares - I'm still concerned about some of the changes coming. Chairs =
are still editors. We still have problems.

A lot of the reason people are still working has to do with the caliber =
of people.

- IETF AdminRest: Status report and introduction - Leslie Daigle and =
Harald

We need to grow up and take on our own responsibilities, and we really =
appreciate CNRI for shielding us from

having to grow up for a very long time!

We had a vision at IETF 59 for what Administrative Restructuring would =
mean...

Carl Malamud is drafting a specific implementation proposal as a =
consultant to IETF. Expect a document in a few weeks.

Working on getting from principles to details

Proposal will be discussed on the IETF list

Administrative entity will be positioned so that it is responsible to =
and responsive to the IETF community - a different relationship

than the IETF has with ISOC

This isn't an announcement, it's not even a proposal. It will be =
implemented over time, if it is implemented.

But the first question is, are we headed in the right direction? We =
aren't even ready to ask for consensus yet.

Not sure whether administrative entity should be independent of ISOC or =
part of ISOC - still wondering, and this has a lot=20

of impact on the governance structure we end up with.

We expect to establish a transition leadership team, find and hire the =
first employee who will do the work, run an open

RFP process for support functions - as soon as we have the consensus to =
support it. We would like to be running by yearend.

Henry Sennrich - why do we need to mess around with something that seems =
to work well? Secretariat gets kudos every meeting.

Haven't read RFC, but don't understand.

April Marine - in general, the correct way to go. Thank you for thanking =
the people who have supported us for so long.

What does "responsible to the IETF community" actually mean? Who is the =
boss of the administrative entity? This is an

improvement, but it's entirely new.

Fred Baker - there is a chain of command. The person could be an ISOC =
employee who reports to me, not to Harald. That's

not a great plan. The ISOC will provide an office and a paycheck, but =
the person will report to the IETF.

Leslie - "reporting to the 20,000 people who subscribe to IETF mailing =
lists..."

Please read the drafts!

Joe Hildebrand - is one person enough to cover these tasks? especially =
if we need to do more PR and marketing?

Harald - I'd like to separate jobs, so we probably won't dump a whole =
lot on one person at once.

--- we're not going to move forward until consensus - does this mean =
IETF Last Call? - yes

Bob Kahn - CNRI really is involved in the current scenario - we should =
be on the slide. Along with ISI, we turned

the IETF to a premier standards organization. We've been working with =
Foretec as a way to save money. We've stayed out

of the way in standards production. Thanks to Foretec for your support, =
so far. CNRI also helped to start ISOC. A lot is=20

at stake here - nothing less than the ability of the Internet =
architecture to evolve in the public interest. We aren't

to the filling-out-details stage yet. We've been able to support the =
IETF with meeting fees and other funds, with no

government funding or involvement, since 1998. There was a MoU at that =
time. I gave Harald and Leslie a list of my

concerns last December. We haven't worked these concerns out yet. CNRI =
has offered to help create a separate non-profit

to carry out this work, and we haven't had any subsequent discussion - =
only being informed last Monday that a

decision had been made to move forward with an administrative entity. =
Your input is important for many reasons.

One major concern is the composition of the board of directors. Wiser =
heads have always worked things out in a crisis at

the IETF. CNRI would like to support this effort and see it succeed, but =
the IETF community needs to provide input. Undue

delay is bad, but so is premature action. Go in with your eyes open, and =
have an open and public discussion. This goes

far beyond CNRI's interests, is not a small administrative matter, and =
is about the future of the Internet. The future

isn't assured. Ask the hard questions - they haven't been asked yet.

Ted Hardie - it hasn't just been CNRI, a lot of your "we"s have been =
"you". (applause) You're saying we should be

paying attention, and we ought to be scared, and we have a path forward. =
We've learned that we can count on individuals, you,

Vint, and Jon, but we've also learned we need a structure that lasts =
longer than Harald, Leslie, Fred ...

Bob - Harald and Leslie are working hard on these interests, but we need =
more input. Fundraising and staffing have been

the biggest challenges during a period of economic downturn and reduced =
attendance. Vint and Phil Gross were CNRI employees

during their IETF leadership years.

Hillarie - this is a very serious issue - we don't want to be 802.IETF =
in two years.=20

Dave Crocker - I'm trying to imagine being the staff of Foretec, the RFC =
Editor, the IANA seeing these slides. (applause)

But there are a lot of rumors this week. Has the decision been made? - =
No. IESG and IAB expect to do a transition

by yearend, but the transition is to a formalized relationship.=20

Harald - we know this is scary stuff in a lot of ways. We haven't talked =
much about it in public because we didn't need

to scare people with decisions we hadn't made. Now we've put this idea =
forward, so it's time to move forward to a stable

resolution.

Scott Bradner - current secretariat will run DC meeting? - Yes

Brian Carpenter - couldn't believe IETF had three major relationships =
(CNRI, RFC Editor, IANA), with only one

governed by a contract (RFC Editor). We've done IANA now, we need to do =
CNRI. It's time. For companies contributing with

ISOC fees, we don't want to see a gap between ISOC and the =
administrative entity that will confuse contributors writing

checks.

Harald - think there is some distance that's good, with fundraising in =
one place and administration in another (ISOC gets,

IETF spends) - but it's largely meeting fees, anyway.

Donald Eastlake - happy with secretariat, doing the right thing - should =
NOMCOM help with board of trustees?

Bernard - keep our eyes on what needs improving. Get a sense of =
priorities in a week or two and work on high-runners.

Concentrate on what makes a difference in the way we work around here.

Gregory - remember how we move from one protocol to another in this =
transition. We don't immediately deprecate the

old one until we have a lot of experience with the new one.=20

Harald - it's more like IANA registration - we can only have one set of =
procedures at a time. Anyway, what Bob said -=20

read the documents and tell us what you think.

------=_NextPart_000_0134_01C47B83.9C96D780
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.1458" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2><FONT size=3D2>
<P>1930-2200 Plenary - IETF Planning Meeting - Grande Ballroom</P>
<P>- Welcome, and introduction - Leslie Daigle</P>
<P>- IRTF presentation: ASRG Report</P>
<P>Have broken problem domain into pieces, some closer to IETF than =
others</P>
<P>Working on drafts for BCPs for ISPs that want to do the right thing=20
(DNSBL/DNSWL, port 25 blocking), but</P>
<P>we've never written down our best current practices before</P>
<P>Looking at filtering rule exchange, looking at formats for abuse =
reports</P>
<P>Would like to develop common interfaces for reputation systems</P>
<P>Not defining SPAM, not doing challenge/response, not doing e-postage, =
not=20
doing replacements for SMTP</P>
<P>Something like 34 anti-SPAM groups working now, including ITU-T - and =
the=20
standards process comparison is scary...</P>
<P>SPAM is bad, solutions are hard, we can make incremental progress</P>
<P>Dave Crocker - there's a spec in CSV proposal on reputation systems - =
can=20
people look at it and comment?</P>
<P>http://asrg.sp.am</P>
<P>Brian Carpenter - fixing SPAM in two years? How long, really? - we'll =
never=20
solve the SPAM problem,</P>
<P>but in two years we could have a handle on it - all the way to never, =
of=20
course, but in five years,</P>
<P>people will have given up on e-mail</P>
<P>Scott Bradner - ITU-T asking how they can cooperate with us</P>
<P>- Technical issue: IAB Security workshop retrospective - Bernard =
Aboba, Pete=20
Resnick, Eric Rescola</P>
<P>Thanks to Steve Bellovin, who actually ATTENDED the workshop :-}</P>
<P>In 1997 - two years before the CERT rate of increase went =
vertical</P>
<P>Trends then - rate of attacks increasing, attackers getting =
smarter</P>
<P>Common wisdom - build in security, get more serious about security, =
IPsec not=20
a panacea - but no mechanisms</P>
<P>Trends now - scope and sophistication of attacks continues to grow, =
money now=20
a motivator, peer-to-peer and multi-party</P>
<P>protocols on the rise, authorization matters now, most =
vulnerabilities are=20
now application-level - threat model is evolving</P>
<P>Can an attacker make money? Can an attacker cause havoc on =
regional/national=20
scale?</P>
<P>Core mechanisms have not fared well (DNSSEC, IPsec/ISAKMP, S/MIME) - =
non-core=20
mechanisms more successful</P>
<P>Ease of use is significant, especially ease of deployment</P>
<P>SASL, EAP easier for developers</P>
<P>Coordination requirement makes it harder to deploy a mechanism, even =
within a=20
company</P>
<P>Don't repeat lessons of ISAKMP with GSS-API, EAP, SASL</P>
<P>1997 missing pieces were object security, secure e-mail, routing =
security</P>
<P>Missing pieces now are peer-to-peer, multiparty, DDoS, Phishing</P>
<P>Look past today's problem, document your dependencies, understand =
large-scale=20
risks</P>
<P>Monetary incentives? Financial crimes (credit card theft, etc.)</P>
<P>Spammers paying bounty on compromised systems</P>
<P>Paying for an arbitrary attack</P>
<P>Spammers are trying to sell things with spambots, too</P>
<P>Eliot Lear - smart card reader, smart card, contract, and PIN for =
just one=20
account - problem has usability and API</P>
<P>issues, users are awash in keys. Broader than IETF, how to make =
progress?</P>
<P>Ted Hardie - DDoS categories - now there IS a different between =
slash-dot and=20
DDoS - behaving like legitimate users, </P>
<P>SYN flooding isn't legitimate, but some attacks are - include attack=20
detection profiles in protocol definitions? - we do</P>
<P>need to give a different type of security guidance</P>
<P>Threat model hasn't changed - it's always about money, the IETF could =

usefully take security seriously and focus on</P>
<P>infrastructure security. We aren't going to fix application security =
in the=20
IETF (we've known about buffer overflows</P>
<P>for a while now) - attackers aren't attacking you, they're now =
attacking=20
regions and nations - security issues have</P>
<P>moved into applications, when they weren't there before. Perfectly =
valid SMTP=20
clients are doing a lot of the damage.</P>
<P>Bill Summerfeld - Zombie armies give attackers a lot more resources =
than you=20
think</P>
<P>Dave Crocker - scaling is the only problem on the Internet, what does =
that=20
mean in this situation? This is complex and</P>
<P>we don't have a good track record on complex problems. How do we get =
a dialog=20
going?</P>
<P>IPsec and DNSSEC haven't lived up to expectations - why not? Where's =
the=20
lessons learned, so we learn lessons? - </P>
<P>deployment does matter - will IPsec and DNSSEC ever live up to =
expectations?=20
- People here have been saying APIs would</P>
<P>help a lot, maybe they're right</P>
<P>In the mid-1980s, no one had a clue about DNS at all, much less about =

security, we think we got it right this time, three</P>
<P>designs later. Operator involvement will be critical, because we =
didn't have=20
it the first two times. And we tried. People</P>
<P>still ignore security advisors today. - Sometimes laziness is =
rational.=20
Putting stuff into standards isn't implementing it.</P>
<P>IETF solution diversity is amazing, but they have been designed=20
piecemeal.</P>
<P>Application security has been around for a long time, we've just =
ignored it.=20
Operational information needs to come down the </P>
<P>stack. - Application security problems have been around, it's just =
starting=20
to hurt. </P>
<P>Abstract interfaces are defined for the successful mechanisms. IPsec =
doesn't=20
have an abstract interface. - IPsec doesn't</P>
<P>have protocol problems, it has API problems.</P>
<P>- IETF Reorg: Status report - Harald Alvestrand</P>
<P>What we want the IETF to be doesn't change from meeting to meeting - =
mission=20
statement is now approved by IETF</P>
<P>PROTO, ICAR, NEWTRK are making progress, and some small things are =
done</P>
<P>Five procedural BCPs and an Experimental RFC approved since Seoul</P>
<P>IESG is becoming more effective - more focus on "critical" issues, =
better=20
edit cycles, better throughput</P>
<P>Still working to improve the process</P>
<P>Change efforts quieting down - are people giving up, becoming =
happier, or=20
going back to technical work?</P>
<P>Will focus on IESG processing (tracker toolmaking, reasons to block, =
WG chair=20
shepherding) and ICAR (looking for </P>
<P>volunteers, THIS MEANS YOU)</P>
<P>How to measure the effects of what we've done? even subjectively</P>
<P>Dave Crocker - things are getting better, this is good, two years ago =
things=20
were not good. Can we check on</P>
<P>how people are feeling?</P>
<P>Scott Bradner - will discussion on "why to block" be public? - yes, =
but we=20
won't promise a date</P>
<P>Brian Carpenter - customer satisfaction survey would be nice but =
annoying. We=20
need to tell the world we think our</P>
<P>problems are getting smaller</P>
<P>Attendance drop-off has stopped dropping</P>
<P>-------------------------------------------</P>
<P>Fred Baker - we're at the size of the Adelaide meeting in 2000, and =
the=20
average meeting</P>
<P>size in 1998 - plenaries involve less vegetable-throwing now, and =
plenaries=20
started with a LOT of vegetable-throwing</P>
<P>post-Kobe. The IETF is moving beyond many of the problems we've =
had.</P>
<P>Sue Hares - I'm still concerned about some of the changes coming. =
Chairs are=20
still editors. We still have problems.</P>
<P>A lot of the reason people are still working has to do with the =
caliber of=20
people.</P>
<P>- IETF AdminRest: Status report and introduction - Leslie Daigle and=20
Harald</P>
<P>We need to grow up and take on our own responsibilities, and we =
really=20
appreciate CNRI for shielding us from</P>
<P>having to grow up for a very long time!</P>
<P>We had a vision at IETF 59 for what Administrative Restructuring =
would=20
mean...</P>
<P>Carl Malamud is drafting a specific implementation proposal as a =
consultant=20
to IETF. Expect a document in a few weeks.</P>
<P>Working on getting from principles to details</P>
<P>Proposal will be discussed on the IETF list</P>
<P>Administrative entity will be positioned so that it is responsible to =
and=20
responsive to the IETF community - a different relationship</P>
<P>than the IETF has with ISOC</P>
<P>This isn't an announcement, it's not even a proposal. It will be =
implemented=20
over time, if it is implemented.</P>
<P>But the first question is, are we headed in the right direction? We =
aren't=20
even ready to ask for consensus yet.</P>
<P>Not sure whether administrative entity should be independent of ISOC =
or part=20
of ISOC - still wondering, and this has a lot </P>
<P>of impact on the governance structure we end up with.</P>
<P>We expect to establish a transition leadership team, find and hire =
the first=20
employee who will do the work, run an open</P>
<P>RFP process for support functions - as soon as we have the consensus =
to=20
support it. We would like to be running by yearend.</P>
<P>Henry Sennrich - why do we need to mess around with something that =
seems to=20
work well? Secretariat gets kudos every meeting.</P>
<P>Haven't read RFC, but don't understand.</P>
<P>April Marine - in general, the correct way to go. Thank you for =
thanking the=20
people who have supported us for so long.</P>
<P>What does "responsible to the IETF community" actually mean? Who is =
the boss=20
of the administrative entity? This is an</P>
<P>improvement, but it's entirely new.</P>
<P>Fred Baker - there is a chain of command. The person could be an ISOC =

employee who reports to me, not to Harald. That's</P>
<P>not a great plan. The ISOC will provide an office and a paycheck, but =
the=20
person will report to the IETF.</P>
<P>Leslie - "reporting to the 20,000 people who subscribe to IETF =
mailing=20
lists..."</P>
<P>Please read the drafts!</P>
<P>Joe Hildebrand - is one person enough to cover these tasks? =
especially if we=20
need to do more PR and marketing?</P>
<P>Harald - I'd like to separate jobs, so we probably won't dump a whole =
lot on=20
one person at once.</P>
<P>--- we're not going to move forward until consensus - does this mean =
IETF=20
Last Call? - yes</P>
<P>Bob Kahn - CNRI really is involved in the current scenario - we =
should be on=20
the slide. Along with ISI, we turned</P>
<P>the IETF to a premier standards organization. We've been working with =
Foretec=20
as a way to save money. We've stayed out</P>
<P>of the way in standards production. Thanks to Foretec for your =
support, so=20
far. CNRI also helped to start ISOC. A lot is </P>
<P>at stake here - nothing less than the ability of the Internet =
architecture to=20
evolve in the public interest. We aren't</P>
<P>to the filling-out-details stage yet. We've been able to support the =
IETF=20
with meeting fees and other funds, with no</P>
<P>government funding or involvement, since 1998. There was a MoU at =
that time.=20
I gave Harald and Leslie a list of my</P>
<P>concerns last December. We haven't worked these concerns out yet. =
CNRI has=20
offered to help create a separate non-profit</P>
<P>to carry out this work, and we haven't had any subsequent discussion =
- only=20
being informed last Monday that a</P>
<P>decision had been made to move forward with an administrative entity. =
Your=20
input is important for many reasons.</P>
<P>One major concern is the composition of the board of directors. Wiser =
heads=20
have always worked things out in a crisis at</P>
<P>the IETF. CNRI would like to support this effort and see it succeed, =
but the=20
IETF community needs to provide input. Undue</P>
<P>delay is bad, but so is premature action. Go in with your eyes open, =
and have=20
an open and public discussion. This goes</P>
<P>far beyond CNRI's interests, is not a small administrative matter, =
and is=20
about the future of the Internet. The future</P>
<P>isn't assured. Ask the hard questions - they haven't been asked =
yet.</P>
<P>Ted Hardie - it hasn't just been CNRI, a lot of your "we"s have been =
"you".=20
(applause) You're saying we should be</P>
<P>paying attention, and we ought to be scared, and we have a path =
forward.=20
We've learned that we can count on individuals, you,</P>
<P>Vint, and Jon, but we've also learned we need a structure that lasts =
longer=20
than Harald, Leslie, Fred ...</P>
<P>Bob - Harald and Leslie are working hard on these interests, but we =
need more=20
input. Fundraising and staffing have been</P>
<P>the biggest challenges during a period of economic downturn and =
reduced=20
attendance. Vint and Phil Gross were CNRI employees</P>
<P>during their IETF leadership years.</P>
<P>Hillarie - this is a very serious issue - we don't want to be =
802.IETF in two=20
years. </P>
<P>Dave Crocker - I'm trying to imagine being the staff of Foretec, the =
RFC=20
Editor, the IANA seeing these slides. (applause)</P>
<P>But there are a lot of rumors this week. Has the decision been made? =
- No.=20
IESG and IAB expect to do a transition</P>
<P>by yearend, but the transition is to a formalized relationship. </P>
<P>Harald - we know this is scary stuff in a lot of ways. We haven't =
talked much=20
about it in public because we didn't need</P>
<P>to scare people with decisions we hadn't made. Now we've put this =
idea=20
forward, so it's time to move forward to a stable</P>
<P>resolution.</P>
<P>Scott Bradner - current secretariat will run DC meeting? - Yes</P>
<P>Brian Carpenter - couldn't believe IETF had three major relationships =
(CNRI,=20
RFC Editor, IANA), with only one</P>
<P>governed by a contract (RFC Editor). We've done IANA now, we need to =
do CNRI.=20
It's time. For companies contributing with</P>
<P>ISOC fees, we don't want to see a gap between ISOC and the =
administrative=20
entity that will confuse contributors writing</P>
<P>checks.</P>
<P>Harald - think there is some distance that's good, with fundraising =
in one=20
place and administration in another (ISOC gets,</P>
<P>IETF spends) - but it's largely meeting fees, anyway.</P>
<P>Donald Eastlake - happy with secretariat, doing the right thing - =
should=20
NOMCOM help with board of trustees?</P>
<P>Bernard - keep our eyes on what needs improving. Get a sense of =
priorities in=20
a week or two and work on high-runners.</P>
<P>Concentrate on what makes a difference in the way we work around =
here.</P>
<P>Gregory - remember how we move from one protocol to another in this=20
transition. We don't immediately deprecate the</P>
<P>old one until we have a lot of experience with the new one. </P>
<P>Harald - it's more like IANA registration - we can only have one set =
of=20
procedures at a time. Anyway, what Bob said - </P>
<P>read the documents and tell us what you=20
think.</P></FONT></FONT></DIV></BODY></HTML>

------=_NextPart_000_0134_01C47B83.9C96D780--




--===============0554664395==
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

--===============0554664395==--





From ietf-bounces@ietf.org  Fri Aug  6 10:27:35 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29897;
	Fri, 6 Aug 2004 10:27:35 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bt5kk-0006B4-Rw; Fri, 06 Aug 2004 10:31:28 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bt5bB-0000HS-Jn; Fri, 06 Aug 2004 10:21:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bt5Y0-0007XV-Pz
	for ietf@megatron.ietf.org; Fri, 06 Aug 2004 10:18:16 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29143
	for <ietf@ietf.org>; Fri, 6 Aug 2004 10:18:15 -0400 (EDT)
Received: from relay1.san2.attens.com ([192.215.81.74])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bt5bi-000609-6s
	for ietf@ietf.org; Fri, 06 Aug 2004 10:22:07 -0400
Received: from [12.105.246.73] (0127ahost73.starwoodbroadband.com
	[12.105.246.73])
	by relay1.san2.attens.com (8.11.6/8.9.3) with ESMTP id i76EICB06276;
	Fri, 6 Aug 2004 14:18:12 GMT
In-Reply-To: <AD68B55C-E763-11D8-A1FF-000A95B3BA44@hxr.us>
References: <AD68B55C-E763-11D8-A1FF-000A95B3BA44@hxr.us>
Mime-Version: 1.0 (Apple Message framework v618)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <903C3DE9-E7B3-11D8-B94D-000A9592AE60@ohiou.edu>
Content-Transfer-Encoding: 7bit
From: Hans Kruse <kruse@ohiou.edu>
Date: Fri, 6 Aug 2004 10:19:01 -0400
To: Andrew Newton <andy@hxr.us>
X-Mailer: Apple Mail (2.618)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: list address for MASS
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-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 7bit

This is what I found:

http://www.imc.org/ietf-mailsig/index.html


On Aug 6, 2004, at 0:47, Andrew Newton wrote:

> Can anyone provide the list/subscription address for MASS:
> http://www.ietf.org/ietf/04aug/mass.txt
>
> -andy
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>
Hans Kruse, Associate Professor
J. Warren McClure School of Communication Systems Management
Adjunct Associate Professor of Electrical Engineering and Computer
Science
Ohio University, Athens, OH, 45701
740-593-4891 voice, 740-593-4889 fax


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


From ietf-bounces@ietf.org  Fri Aug  6 12:14:15 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07225;
	Fri, 6 Aug 2004 12:14:14 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bt7Pz-0008Ko-Oq; Fri, 06 Aug 2004 12:18:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bt78A-0008K5-R9; Fri, 06 Aug 2004 11:59:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bt704-00077R-Jq
	for ietf@megatron.ietf.org; Fri, 06 Aug 2004 11:51:20 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05709
	for <ietf@ietf.org>; Fri, 6 Aug 2004 11:51:18 -0400 (EDT)
Received: from cyphermail.sandelman.ottawa.on.ca ([205.150.200.161]
	helo=noxmail.sandelman.ottawa.on.ca)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bt73n-0007r2-Gz
	for ietf@ietf.org; Fri, 06 Aug 2004 11:55:12 -0400
Received: from lox.sandelman.ottawa.on.ca
	(IDENT:root@lox.sandelman.ottawa.on.ca [205.150.200.178])
	by noxmail.sandelman.ottawa.on.ca (8.11.6p3/8.11.6) with ESMTP id
	i76FpDE19568
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified
	FAIL); Fri, 6 Aug 2004 11:51:15 -0400 (EDT)
Received: from sandelman.ottawa.on.ca (desk.marajade.sandelman.ca
	[205.150.200.247])
	by lox.sandelman.ottawa.on.ca (8.11.6p3/8.11.6) with ESMTP id
	i76FuaK23672
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified
	FAIL); Fri, 6 Aug 2004 11:56:41 -0400 (EDT)
Received: from sandelman.ottawa.on.ca (marajade [127.0.0.1])
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id
	i76FnQ4F007261
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Fri, 6 Aug 2004 11:49:26 -0400
Received: from marajade.sandelman.ottawa.on.ca (mcr@localhost)
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id
	i76FnKM7007256; Fri, 6 Aug 2004 11:49:24 -0400
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
In-Reply-To: Message from "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es> 
	of "Thu, 05 Aug 2004 22:35:27 PDT."
	<05db01c47b77$2f68ab90$14848182@consulintel.es> 
References: <41131059.6000002@att.com>
	<05db01c47b77$2f68ab90$14848182@consulintel.es> 
X-Mailer: MH-E 7.4.2; nmh 1.0.4+dev; XEmacs 21.4 (patch 6)
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Fri, 06 Aug 2004 11:49:20 -0400
Message-ID: <7255.1091807360@marajade.sandelman.ottawa.on.ca>
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
X-Spam-Score: 2.3 (++)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Cc: ietf@ietf.org
Subject: Re: T-shirts, and some suggestions for future 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-Score: 2.3 (++)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c

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


>>>>> "JORDI" == JORDI PALET MARTINEZ <jordi.palet@consulintel.es> writes:
    JORDI> The only complain was not being in downtown. Also something
    JORDI> about the restaurants nearby, but there are a few at walking
    JORDI> distance, and the hotel has enough meeting rooms and kitchens
    JORDI> to add as many additional restaurants as tastes we may have !

  Frankly, as long as we can have BAR BOFs in the Hotel, the location of
the food doesn't matter.

  Vienna suffered from having meeting space and hotel seperated, and
unclear default "BAR".  Orlando had the same problem. I've never done
the San Diego hotel, but I know exactly where it is. Definitely not
downtown. 

    JORDI> Now, I'm somehow (very) disappointed, because San Diego is
    JORDI> very nice, yes, but we aren't in downtown, we don't have food
    JORDI> choices, and is VERY expensive compared to Madrid. So what's
    JORDI> going on ?

  I'd like to know this as well.
  Tickets to Madrid in Feb/March are relatively cheap, I think. 
  I don't want to go there in August.

  I'm hoping for Madrid in March 2005, Vancouver in August 2005 (yes, a
host has to be found. Could even be someone from Seattle..), and DC or
Minneapolis in November 2005. 
  (seriously. Both locations work for November very well)

    JORDI> So it was a kind of excuse ?

    JORDI> By the way, the hotel has free IPv6 connectivity in every
    JORDI> room, since we installed it in May 2003 (first one in the
    JORDI> world as I know).

  Cool. Does it have IPv4? It would be cool if it is *didn't* :-)

    JORDI> PS: And yes, we of course plan to provide a nice t-shirt !

  My wife isn't happy that I can go three weeks and wear only conference
T-shirts. Or that I have more cloths than her. I'm happy that they all
still fit. 

- --
]     "Elmo went to the wrong fundraiser" - The Simpson         |  firewalls  [
]   Michael Richardson,    Xelerance Corporation, Ottawa, ON    |net architect[
] mcr@xelerance.com      http://www.sandelman.ottawa.on.ca/mcr/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [
  
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Finger me for keys

iQCVAwUBQROofIqHRg3pndX9AQEPRwP+OGe4+kn+vBjUoGst6p1VAfM07WjJRyaR
cTy0DLSjgggOqoAbSKtXV+HUZ0qiqHC55T0YDKQwYtruwGUB62lhD8nfZKc7tgbk
q7v4ov/DrTJPuKwAoTU8SwYbB998+CBlBdFBA/ftMXhxu+PR8p7LnN7Ng1ZjOEEQ
kCXDNlgVN7s=
=df9A
-----END PGP SIGNATURE-----

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


From ietf-bounces@ietf.org  Fri Aug  6 12:58:27 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10122;
	Fri, 6 Aug 2004 12:58:27 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bt86l-0000mn-EU; Fri, 06 Aug 2004 13:02:22 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bt7vM-0003Ai-KK; Fri, 06 Aug 2004 12:50:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bt7pZ-00023I-UK
	for ietf@megatron.ietf.org; Fri, 06 Aug 2004 12:44:33 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09174
	for <ietf@ietf.org>; Fri, 6 Aug 2004 12:44:31 -0400 (EDT)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bt7tI-0000Wc-NU
	for ietf@ietf.org; Fri, 06 Aug 2004 12:48:26 -0400
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-3.cisco.com with ESMTP; 06 Aug 2004 09:46:55 +0000
X-BrightmailFiltered: true
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i76Ghxna004620;
	Fri, 6 Aug 2004 09:43:59 -0700 (PDT)
Received: from jmpolk-w2k01.diablo.cisco.com (ssh-sjc-1.cisco.com
	[171.68.225.134]) by wells.cisco.com (8.8.6
	(PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id JAA08328;
	Fri, 6 Aug 2004 09:43:58 -0700 (PDT)
Message-Id: <4.3.2.7.2.20040806113528.030dca20@localhost>
X-Sender: jmpolk@localhost
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 06 Aug 2004 11:44:41 -0500
To: Tony Hansen <tony@att.com>, ietf@ietf.org
From: "James M. Polk" <jmpolk@cisco.com>
In-Reply-To: <41131059.6000002@att.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 2.3 (++)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Subject: Re: T-shirts, and some suggestions for future 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-Score: 2.3 (++)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d

At 01:00 AM 8/6/2004 -0400, Tony Hansen wrote:
>The first time in recent years that we almost didn't have a sponsor was in 
>Adelaide (IETF 47, March 2000).
>
>So, what happened? In true IETF fashion, a bar BOF met, designed a 
>T-shirt, and made arrangements with a T-shirt shop a couple of blocks from 
>the convention center. Those people who wanted a T-shirt walked over 
>there, picked a T-shirt color, put in an order, paid their money, and got 
>a shirt a couple of days later. (It's definitely one of my most favorite 
>IETF shirts.)

As one of the designers of the T-Shirt (along with Randy Stewart and Peter 
Lei): thanks! I agree. It is the one that I see most often now at meetings. 
There is some pride with that effort, not only that is prevails with folks 
wearing it, but that we actually did it and gave folks choices of colors 
and such.

>I don't know exactly how many people wound up ordering their shirt this way,

well over 1000

>but I know the owner worked numerous overtime hours to meet the demand.

he was sweating - but making money all the way, so he didn't mind at all.




cheers,
James

                                *******************
                 Truth is not to be argued... it is to be presented


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


From ietf-bounces@ietf.org  Fri Aug  6 13:40:52 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13069;
	Fri, 6 Aug 2004 13:40:52 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bt8lo-0001h0-JN; Fri, 06 Aug 2004 13:44:45 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bt8cm-0001bD-FF; Fri, 06 Aug 2004 13:35:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bt8MD-0007Vv-Sq
	for ietf@megatron.ietf.org; Fri, 06 Aug 2004 13:18:17 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11621
	for <ietf@ietf.org>; Fri, 6 Aug 2004 13:18:14 -0400 (EDT)
Received: from sklave3.rackland.de ([213.133.101.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bt8Pt-0001CY-NI
	for ietf@ietf.org; Fri, 06 Aug 2004 13:22:09 -0400
Received: from sputnik (uucp@localhost)
	by sklave3.rackland.de (8.12.10/8.12.10/Debian-1) with BSMTP id
	i76HIBXd010466 for ietf@ietf.org; Fri, 6 Aug 2004 19:18:11 +0200
Received: (from hadmut@localhost)
	by sputnik.mobil.danisch.de (8.12.11/8.12.11/Debian-5) id
	i76HFHTQ003012 for ietf@ietf.org; Fri, 6 Aug 2004 19:15:17 +0200
From: Hadmut Danisch <hadmut@danisch.de>
Date: Fri, 6 Aug 2004 10:15:17 -0700
To: ietf@ietf.org
Message-ID: <20040806171517.GA2875@danisch.de>
References: <DD7FE473A8C3C245ADA2A2FE1709D90B0DB32F@server2003.arneill-py.sacramento.ca.us>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <DD7FE473A8C3C245ADA2A2FE1709D90B0DB32F@server2003.arneill-py.sacramento.ca.us>
User-Agent: Mutt/1.5.6+20040523i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Subject: YATS? Re: T-shirts, and some suggestions for future 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-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b

On Fri, Aug 06, 2004 at 12:18:19AM -0700, Michel Py wrote:
> 
> _ties_? Why not a designer suit while you're at it.


What's wrong about ties? Pretty good way to make advertising for IETF
in commercial environment. Just a thought.

> Sandals. We want IETF sandals.

Yeah, but difficult to print a logo on. Find someone who 
can print or embroider logos on sandals.

What about a straw hat? Or a stetson? Sombrero?

A cap like those LAPD caps? 
An FBI-like jacket?
IETF-suspenders?
Cool sunglasses? 
Outdoor-Shirts?

Backpacks? Computer bags? 

Find a hotel with a laaarge swimming pool and give
IETF swimsuits? Baywatch? Netwatch? IETF-Towels? 

Not YATS (Yet another T-Shirt). Anything not everybody 
has.


Should we start a BOF?

Hadmut :-)



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


From ietf-bounces@ietf.org  Fri Aug  6 14:26:58 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15531;
	Fri, 6 Aug 2004 14:26:58 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bt9US-0002XU-Np; Fri, 06 Aug 2004 14:30:53 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bt9It-0002Rf-6Q; Fri, 06 Aug 2004 14:18:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bt9EP-0001id-Ad
	for ietf@megatron.ietf.org; Fri, 06 Aug 2004 14:14:17 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14999
	for <ietf@ietf.org>; Fri, 6 Aug 2004 14:14:16 -0400 (EDT)
Received: from mail.consulintel.es ([213.172.48.142] helo=consulintel.es)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bt9I9-0002HQ-Lt
	for ietf@ietf.org; Fri, 06 Aug 2004 14:18:10 -0400
Received: from consulintel02 by consulintel.es (MDaemon.PRO.v7.1.2.R)
	with ESMTP id md50000182638.msg
	for <ietf@ietf.org>; Fri, 06 Aug 2004 20:17:04 +0200
Message-ID: <0c2801c47be1$123b9810$14848182@consulintel.es>
From: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
References: <41131059.6000002@att.com><05db01c47b77$2f68ab90$14848182@consulintel.es>
	<7255.1091807360@marajade.sandelman.ottawa.on.ca>
Date: Fri, 6 Aug 2004 11:13:24 -0700
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.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Spam-Processed: consulintel.es, Fri, 06 Aug 2004 20:17:04 +0200
	(not processed: message from valid local sender)
X-MDRemoteIP: 130.129.132.20
X-Return-Path: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
X-MDAV-Processed: consulintel.es, Fri, 06 Aug 2004 20:17:08 +0200
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196
Content-Transfer-Encoding: quoted-printable
Subject: Re: T-shirts, and some suggestions for future ietf meetings
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-Score: 0.0 (/)
X-Scan-Signature: 1676547e4f33b5e63227e9c02bd359e3
Content-Transfer-Encoding: quoted-printable

My response below, in-line.

Regards,
Jordi

----- Original Message -----=20
From: "Michael Richardson" <mcr@sandelman.ottawa.on.ca>
To: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
Cc: <ietf@ietf.org>
Sent: Friday, August 06, 2004 8:49 AM
Subject: Re: T-shirts, and some suggestions for future ietf meetings


> -----BEGIN PGP SIGNED MESSAGE-----
>=20
>=20
> >>>>> "JORDI" =3D=3D JORDI PALET MARTINEZ <jordi.palet@consulintel.es> writes:
>     JORDI> The only complain was not being in downtown. Also something
>     JORDI> about the restaurants nearby, but there are a few at walking
>     JORDI> distance, and the hotel has enough meeting rooms and kitchens
>     JORDI> to add as many additional restaurants as tastes we may have !
>=20
>   Frankly, as long as we can have BAR BOFs in the Hotel, the location of
> the food doesn't matter.

There is a BAR BOF (actually two), and we can build more if required (enough space and kitchens).

>=20
>   Vienna suffered from having meeting space and hotel seperated, and
> unclear default "BAR".  Orlando had the same problem. I've never done
> the San Diego hotel, but I know exactly where it is. Definitely not
> downtown.=20
>=20
>     JORDI> Now, I'm somehow (very) disappointed, because San Diego is
>     JORDI> very nice, yes, but we aren't in downtown, we don't have food
>     JORDI> choices, and is VERY expensive compared to Madrid. So what's
>     JORDI> going on ?
>=20
>   I'd like to know this as well.
>   Tickets to Madrid in Feb/March are relatively cheap, I think.=20

I think they are very cheap all the year ;-)

>   I don't want to go there in August.

Well having the meetings in the hotel, with air condition is not a problem, but is nice July/August because:
1) You want to go out for dinner and have a nice weather
2) You can take the advantage to travel with family or whatever and have vacations afterwards ;-)

>=20
>   I'm hoping for Madrid in March 2005, Vancouver in August 2005 (yes, a
> host has to be found. Could even be someone from Seattle..), and DC or
> Minneapolis in November 2005.=20
>   (seriously. Both locations work for November very well)

If we have a decision RIGHT NOW, I can still try to arrange for March 2005, but timing is becoming VERY tight.

>=20
>     JORDI> So it was a kind of excuse ?
>=20
>     JORDI> By the way, the hotel has free IPv6 connectivity in every
>     JORDI> room, since we installed it in May 2003 (first one in the
>     JORDI> world as I know).
>=20
>   Cool. Does it have IPv4? It would be cool if it is *didn't* :-)

Sorry, I can't satisfy 100% your demand here, but I can tell you that the IPv4 connectivity is NATed (and broken because a very nasty Nomadix box).

But of course we can provide public IPv4 addresses for the meeting (unless we decide to make it only IPv6, which I will be happy to do !).

>=20
>     JORDI> PS: And yes, we of course plan to provide a nice t-shirt !
>=20
>   My wife isn't happy that I can go three weeks and wear only conference
> T-shirts. Or that I have more cloths than her. I'm happy that they all
> still fit.=20

The solution is to bring your wife and have vacations after the meeting ;-)

By the way, we have a very nice suggestion for the social, if you like art/painting. What about a dinner and private visit to the Prado museum ?

>=20
> - --
> ]     "Elmo went to the wrong fundraiser" - The Simpson         |  firewalls  [
> ]   Michael Richardson,    Xelerance Corporation, Ottawa, ON    |net architect[
> ] mcr@xelerance.com      http://www.sandelman.ottawa.on.ca/mcr/ |device driver[
> ] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [
>  =20
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.2 (GNU/Linux)
> Comment: Finger me for keys
>=20
> iQCVAwUBQROofIqHRg3pndX9AQEPRwP+OGe4+kn+vBjUoGst6p1VAfM07WjJRyaR
> cTy0DLSjgggOqoAbSKtXV+HUZ0qiqHC55T0YDKQwYtruwGUB62lhD8nfZKc7tgbk
> q7v4ov/DrTJPuKwAoTU8SwYbB998+CBlBdFBA/ftMXhxu+PR8p7LnN7Ng1ZjOEEQ
> kCXDNlgVN7s=3D
> =3Ddf9A
> -----END PGP SIGNATURE-----
>=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-bounces@ietf.org  Fri Aug  6 15:56:45 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21797;
	Fri, 6 Aug 2004 15:56:45 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BtAtL-00047Q-JB; Fri, 06 Aug 2004 16:00:40 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BtAhl-00049y-T1; Fri, 06 Aug 2004 15:48:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BtAbs-00030k-AC
	for ietf@megatron.ietf.org; Fri, 06 Aug 2004 15:42:36 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21007
	for <ietf@ietf.org>; Fri, 6 Aug 2004 15:42:34 -0400 (EDT)
Received: from kanfw1.ottawa.alcatel.ca ([192.75.23.69]
	helo=tm1.ca.alcatel.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BtAfa-0003uP-D4
	for ietf@ietf.org; Fri, 06 Aug 2004 15:46:30 -0400
Received: from localhost (localhost [127.0.0.1])
	by tm1.ca.alcatel.com (8.12.10/8.12.10) with ESMTP id i76JgT0B000959
	for <ietf@ietf.org>; Fri, 6 Aug 2004 15:42:30 -0400 (EDT)
Date: Fri, 6 Aug 2004 15:42:13 -0400
From: Ben Crosby <ben.crosby@alcatel.com>
X-Mailer: The Bat! (v2.11.02) Personal
Organization: CTO North America
X-Priority: 3 (Normal)
Message-ID: <266554097.20040806154213@alcatel.com>
To: ietf@ietf.org
In-Reply-To: <41131059.6000002@att.com>
References: <41131059.6000002@att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: 7bit
Subject: Re: T-shirts, and some suggestions for future ietf meetings
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Ben Crosby <ben.crosby@alcatel.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-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: 7bit

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

Tony,

Thanks for the suggestions. I'll try to address some of these with
respect to the Alcatel hosted meeting in Washington DC.

Tony> Here's a suggestion for IETF 61: modify the registration web
Tony> page to let people specify the size of the T-shirt they'd like
Tony> to get. Usually, a sponsor has to estimate the number of people
Tony> who want each T-shirt size. This leads to overbuys of some sizes
Tony> and underbuys of other sizes. And it leads to some people being
Tony> dissatisfied with the sizes that they were forced to receive.

I don't (as host) have any control over the IETF registration process.
I'd happily accept input from the Secretariat, but here are some small
issues:

We need to place our order for approx 2000 t-shirts about three months
before the event. This is to allow for the shirts to be purchased,
printed, and shipped. Unfortunately the registration site doesn't go
live nearly early enough for that information to be collected. One of
my grumbles as an attendee is that the venue information is never
announced early enough either :)

I have solicited input into the size distribution, and not had much
luck with answers, so we're guessing a little. I welcome (short of
1500 seperate emails requesting a specific size) some sensible input
in terms of percentage of each size. Which sizes normally run out ?
Which are forced on you when you arrive late etc ?

Thanks, Ben.

-----BEGIN PGP SIGNATURE-----
Version: PGP SDK 3.2.2
Comment: ""

iQA/AwUBQRPfGUNm3F1O6YPWEQLbuACg+H282OqxuIZxJSrT4q6Hk0shzEIAoOx+
yTKuf9c48J+J12l7tvnMKoRN
=Ycn3
-----END PGP SIGNATURE-----



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


From ietf-bounces@ietf.org  Sun Aug  8 02:07:28 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA24315;
	Sun, 8 Aug 2004 02:07:28 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BtguC-0000Ym-C4; Sun, 08 Aug 2004 02:11:41 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Btgm9-0003ne-Ei; Sun, 08 Aug 2004 02:03:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Btgha-0001iJ-Jk
	for ietf@megatron.ietf.org; Sun, 08 Aug 2004 01:58:39 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA16611
	for <ietf@ietf.org>; Sun, 8 Aug 2004 01:58:37 -0400 (EDT)
Received: from fep02-0.kolumbus.fi ([193.229.0.44] helo=fep02-app.kolumbus.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Btgld-0000Re-CI
	for ietf@ietf.org; Sun, 08 Aug 2004 02:02:50 -0400
Received: from [192.168.0.100] (really [80.186.62.82])
	by fep02-app.kolumbus.fi with ESMTP
	id <20040808055834.YDXK28426.fep02-app.kolumbus.fi@[192.168.0.100]>;
	Sun, 8 Aug 2004 08:58:34 +0300
From: "John Loughney" <john.loughney@kolumbus.fi>
To: jari.arkko@piuha.net
Date: Sun,  8 Aug 2004 08:58:45 +0200
Message-ID: <111xrg0CkT44.hJtsPMLR@mail.mobiili.net>
X-Mailer: EPOC Email Version 2.10
MIME-Version: 1.0
Content-Language: i-default
X-Spam-Score: 0.9 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: ietf@ietf.org, JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Subject: Re: T-shirts, and some suggestions for future ietf meetings
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: John Loughney <john.loughney@kolumbus.fi>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-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="===============1983054847=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4

This is a MIME Message

--===============1983054847==
Content-Language: i-default
Content-Type: multipart/alternative;
	boundary="EPOC32-,-Z9RJ7c2hLlNf'6HRbJ3lHw1lbDF9D8VYwtLPl4Pj3yhlCL"

This is a MIME Message

--EPOC32-,-Z9RJ7c2hLlNf'6HRbJ3lHw1lbDF9D8VYwtLPl4Pj3yhlCL
Content-Type: text/plain; charset=UTF-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable


> > By the way, the hotel has free IPv6 connectivity in every room, since =
we
> > installed it in May 2003 (first one in the world as I know).
> (snip)
> > PS: And yes, we of course plan to provide a nice t-shirt !
>=20
> OK, I'm convinced. Lets go there as soon as possible.

I'm convinced as well!

John
--EPOC32-,-Z9RJ7c2hLlNf'6HRbJ3lHw1lbDF9D8VYwtLPl4Pj3yhlCL
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDMuMiBG
aW5hbC8vRU4iPg0KPEhUTUw+IA0KPEhFQUQ+IA0KPFRJVExFPkNvbnZlcnRl
ZCBmcm9tIFJpY2ggVGV4dDwvVElUTEU+DQo8TUVUQSBIVFRQLUVRVUlWPSJD
b250ZW50LVR5cGUiIENPTlRFTlQ9InRleHQvaHRtbDsgY2hhcnNldD1VVEYt
OCI+PE1FVEEgTkFNRT0iZ2VuZXJhdG9yIiBDT05URU5UPSJydDJodG1sIGNv
bnZlcnRlciI+DQo8L0hFQUQ+IA0KPEJPRFkgQkdDT0xPUj0iI2ZmZmZmZiIg
VEVYVD0iIzAwMDAwMCI+DQo8RElWIEFMSUdOPUxFRlQ+PEJSPiZndDsgJmd0
OyBCeSB0aGUgd2F5LCB0aGUgaG90ZWwgaGFzIGZyZWUgSVB2NiBjb25uZWN0
aXZpdHkgaW4gZXZlcnkgcm9vbSwgc2luY2Ugd2U8L0RJVj4gDQo8RElWIEFM
SUdOPUxFRlQ+Jmd0OyAmZ3Q7IGluc3RhbGxlZCBpdCBpbiBNYXkgMjAwMyAo
Zmlyc3Qgb25lIGluIHRoZSB3b3JsZCBhcyBJIGtub3cpLjxCUj4mZ3Q7IChz
bmlwKTxCUj4mZ3Q7ICZndDsgUFM6IEFuZCB5ZXMsIHdlIG9mIGNvdXJzZSBw
bGFuIHRvIHByb3ZpZGUgYSBuaWNlIHQtc2hpcnQgITxCUj4mZ3Q7IDxCUj4m
Z3Q7IE9LLCBJJ20gY29udmluY2VkLiBMZXRzIGdvIHRoZXJlIGFzIHNvb24g
YXMgcG9zc2libGUuPEJSPjwvRElWPiANCjxESVYgQUxJR049TEVGVD5JJ20g
Y29udmluY2VkIGFzIHdlbGwhPC9ESVY+IA0KPERJViBBTElHTj1MRUZUPiZu
YnNwOzwvRElWPjxESVYgQUxJR049TEVGVD5Kb2huPC9ESVY+IA0KPC9CT0RZ
Pg0KPC9IVE1MPiANCg==

--EPOC32-,-Z9RJ7c2hLlNf'6HRbJ3lHw1lbDF9D8VYwtLPl4Pj3yhlCL--




--===============1983054847==
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

--===============1983054847==--





From ietf-bounces@ietf.org  Sun Aug  8 02:19:10 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01396;
	Sun, 8 Aug 2004 02:19:10 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bth5X-0000lJ-Kt; Sun, 08 Aug 2004 02:23:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Btgzc-00020i-44; Sun, 08 Aug 2004 02:17:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Btgxm-0000zQ-LH
	for ietf@megatron.ietf.org; Sun, 08 Aug 2004 02:15:22 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00897
	for <ietf@ietf.org>; Sun, 8 Aug 2004 02:15:21 -0400 (EDT)
Received: from fep02-0.kolumbus.fi ([193.229.0.44] helo=fep02-app.kolumbus.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bth1p-0000i5-H6
	for ietf@ietf.org; Sun, 08 Aug 2004 02:19:34 -0400
Received: from [192.168.0.100] (really [80.186.62.82])
	by fep02-app.kolumbus.fi with ESMTP
	id <20040808061519.YFZG28426.fep02-app.kolumbus.fi@[192.168.0.100]>;
	Sun, 8 Aug 2004 09:15:19 +0300
From: "John Loughney" <john.loughney@kolumbus.fi>
To: "Harald Tveit Alvestrand" <harald@alvestrand.no>
Date: Sun,  8 Aug 2004 09:15:32 +0200
Message-ID: <S0PCNQNKdsSX.YbdB2vgN@mail.mobiili.net>
X-Mailer: EPOC Email Version 2.10
MIME-Version: 1.0
Content-Language: i-default
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: ietf@ietf.org
Subject: Re: Naming convention for a WG I-D that returns to
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: John Loughney <john.loughney@kolumbus.fi>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-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="===============1032953846=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.6 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4

This is a MIME Message

--===============1032953846==
Content-Language: i-default
Content-Type: multipart/alternative;
	boundary="EPOC32-yQZMQvL28W7'Ztd2cTz'WM_X5GZbzTmN3,MMNV_hx2''hK85"

This is a MIME Message

--EPOC32-yQZMQvL28W7'Ztd2cTz'WM_X5GZbzTmN3,MMNV_hx2''hK85
Content-Type: text/plain; charset=UTF-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

> I don't know whether stopping "manyfolks" is right or not.

A note about manyfolks, a few IETF's ago, there were 3 or 4 drafts =
submitted into the WG I chair that were on the same topic. I felt it would =
be best if the authors got together and submitted a common draft. To =
short-circuit any meaningless discussions on whose name should be on the =
draft name, the manyfolks name seemed reasonable.

John
--EPOC32-yQZMQvL28W7'Ztd2cTz'WM_X5GZbzTmN3,MMNV_hx2''hK85
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDMuMiBG
aW5hbC8vRU4iPg0KPEhUTUw+IA0KPEhFQUQ+IA0KPFRJVExFPkNvbnZlcnRl
ZCBmcm9tIFJpY2ggVGV4dDwvVElUTEU+DQo8TUVUQSBIVFRQLUVRVUlWPSJD
b250ZW50LVR5cGUiIENPTlRFTlQ9InRleHQvaHRtbDsgY2hhcnNldD1VVEYt
OCI+PE1FVEEgTkFNRT0iZ2VuZXJhdG9yIiBDT05URU5UPSJydDJodG1sIGNv
bnZlcnRlciI+DQo8L0hFQUQ+IA0KPEJPRFkgQkdDT0xPUj0iI2ZmZmZmZiIg
VEVYVD0iIzAwMDAwMCI+DQo8RElWIEFMSUdOPUxFRlQ+Jmd0OyBJIGRvbid0
IGtub3cgd2hldGhlciBzdG9wcGluZyAibWFueWZvbGtzIiBpcyByaWdodCBv
ciBub3QuPEJSPjwvRElWPiANCjxESVYgQUxJR049TEVGVD5BIG5vdGUgYWJv
dXQgbWFueWZvbGtzLCBhIGZldyBJRVRGJ3MgYWdvLCB0aGVyZSB3ZXJlIDMg
b3IgNCBkcmFmdHMgc3VibWl0dGVkIGludG8gdGhlIFdHIEkgY2hhaXIgdGhh
dCB3ZXJlIG9uIHRoZSBzYW1lIHRvcGljLiBJIGZlbHQgaXQgd291bGQgYmUg
YmVzdCBpZiB0aGUgYXV0aG9ycyBnb3QgdG9nZXRoZXIgYW5kIHN1Ym1pdHRl
ZCBhIGNvbW1vbiBkcmFmdC4gVG8gc2hvcnQtY2lyY3VpdCBhbnkgbWVhbmlu
Z2xlc3MgZGlzY3Vzc2lvbnMgb24gd2hvc2UgbmFtZSBzaG91bGQgYmUgb24g
dGhlIGRyYWZ0IG5hbWUsIHRoZSBtYW55Zm9sa3MgbmFtZSBzZWVtZWQgcmVh
c29uYWJsZS48L0RJVj4gDQo8RElWIEFMSUdOPUxFRlQ+Jm5ic3A7PC9ESVY+
PERJViBBTElHTj1MRUZUPkpvaG48L0RJVj4gDQo8L0JPRFk+DQo8L0hUTUw+
IA0K

--EPOC32-yQZMQvL28W7'Ztd2cTz'WM_X5GZbzTmN3,MMNV_hx2''hK85--




--===============1032953846==
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

--===============1032953846==--





From ietf-bounces@ietf.org  Mon Aug  9 06:36:34 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA18720;
	Mon, 9 Aug 2004 06:36:34 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bu7aS-0002EX-Ia; Mon, 09 Aug 2004 06:41:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bu7Sx-00083y-OI; Mon, 09 Aug 2004 06:33:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bu7Qd-0007nH-GF
	for ietf@megatron.ietf.org; Mon, 09 Aug 2004 06:30:55 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA18426
	for <ietf@ietf.org>; Mon, 9 Aug 2004 06:30:52 -0400 (EDT)
Received: from motgate.mot.com ([129.188.136.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bu7Uv-0002A6-1L
	for ietf@ietf.org; Mon, 09 Aug 2004 06:35:23 -0400
Received: from il06exr06.mot.com (il06exr06.mot.com [129.188.137.136])
	by motgate.mot.com (Motorola/Motgate) with ESMTP id i79AUjYI007571;
	Mon, 9 Aug 2004 03:30:45 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr06.mot.com (Motorola/il06exr06) with ESMTP id
	i79AUhUI019679; Mon, 9 Aug 2004 05:30:43 -0500
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 0A96888CF72; Mon,  9 Aug 2004 12:30:43 +0200 (CEST)
Message-ID: <41175249.7090305@motorola.com>
Date: Mon, 09 Aug 2004 12:30:33 +0200
From: Alexandru Petrescu <Alexandru.Petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7) Gecko/20040616
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Hadmut Danisch <hadmut@danisch.de>
References: <DD7FE473A8C3C245ADA2A2FE1709D90B0DB32F@server2003.arneill-py.sacramento.ca.us>
	<20040806171517.GA2875@danisch.de>
In-Reply-To: <20040806171517.GA2875@danisch.de>
X-Enigmail-Version: 0.84.1.0
X-Enigmail-Supports: pgp-inline, pgp-mime
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: ietf@ietf.org
Subject: Re: YATS? Re: T-shirts,
	and some suggestions for future 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>
Content-Type: multipart/mixed; boundary="===============0035881256=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0

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

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

Hadmut Danisch wrote:
> A cap like those LAPD caps? An FBI-like jacket? IETF-suspenders? Cool
>  sunglasses? Outdoor-Shirts?
> 
> Backpacks? Computer bags?
> 
> Find a hotel with a laaarge swimming pool and give IETF swimsuits? 
> Baywatch? Netwatch? IETF-Towels?

Mugs, pins, belts?

Translucent eye-controlled sunshades?

> Not YATS (Yet another T-Shirt). Anything not everybody has.

Color-changing, invisible T-shirts?

Alex

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

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

iD8DBQFBF1JSMmC0w56zj54RAn5xAJoDO0Xur+tOhOhvXeykydfCtCuRwACgo8g0
NzY2yHkMyQXHfQUXAtPNFCY=
=O3mN
-----END PGP SIGNATURE-----

--------------enig9FBBAEAA298656E04054EA67--


--===============0035881256==
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

--===============0035881256==--



From ietf-bounces@ietf.org  Mon Aug  9 08:04:32 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA23164;
	Mon, 9 Aug 2004 08:04:32 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bu8xP-0003an-Ro; Mon, 09 Aug 2004 08:09:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bu8p3-00007c-5H; Mon, 09 Aug 2004 08:00:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BtDvc-0002SO-2C
	for ietf@megatron.ietf.org; Fri, 06 Aug 2004 19:15:12 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02614
	for <ietf@ietf.org>; Fri, 6 Aug 2004 19:15:09 -0400 (EDT)
Received: from mail2.speakeasy.net ([216.254.0.202])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BtDzO-0007Bf-Sx
	for ietf@ietf.org; Fri, 06 Aug 2004 19:19:07 -0400
Received: (qmail 24368 invoked from network); 6 Aug 2004 23:14:58 -0000
Received: from dsl092-168-196.wdc2.dsl.speakeasy.net (HELO speakeasy.net)
	([66.92.168.196]) (envelope-sender <dja2003@hotpop.com>)
	by mail2.speakeasy.net (qmail-ldap-1.03) with SMTP
	for <ietf@ietf.org>; 6 Aug 2004 23:14:58 -0000
From: Dave Aronson <dja2003@hotpop.com>
To: ietf@ietf.org
Date: Fri, 6 Aug 2004 19:18:19 -0400
User-Agent: KMail/1.6.2
References: <DD7FE473A8C3C245ADA2A2FE1709D90B0DB32F@server2003.arneill-py.sacramento.ca.us>
	<20040806171517.GA2875@danisch.de>
In-Reply-To: <20040806171517.GA2875@danisch.de>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200408061918.19897.dja2003@hotpop.com>
X-Spam-Score: 0.9 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 09 Aug 2004 08:00:11 -0400
Subject: Re: YATS? Re: T-shirts,
	and some suggestions for future 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-Score: 0.9 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Content-Transfer-Encoding: 7bit

Hadmut Danisch <hadmut@danisch.de> wrote:

 > Backpacks? Computer bags?

Pocket protectors.



In leather.

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


From ietf-bounces@ietf.org  Mon Aug  9 08:06:31 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA23306;
	Mon, 9 Aug 2004 08:06:31 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bu8zV-0003e2-Eb; Mon, 09 Aug 2004 08:11:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bu8p4-00007j-GL; Mon, 09 Aug 2004 08:00:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BtZUd-0007i3-7W
	for ietf@megatron.ietf.org; Sat, 07 Aug 2004 18:16:47 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26311
	for <ietf@ietf.org>; Sat, 7 Aug 2004 18:16:44 -0400 (EDT)
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BtZYb-0002cy-Qr
	for ietf@ietf.org; Sat, 07 Aug 2004 18:20:55 -0400
Received: from [127.0.0.1] (helo=localhost)
	by bs.jck.com with esmtp (Exim 4.34) id 1BtZUR-000PN7-1B
	for ietf@ietf.org; Sat, 07 Aug 2004 18:16:35 -0400
Date: Fri, 06 Aug 2004 21:31:13 -0400
From: John C Klensin <john-ietf@jck.com>
To: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <021A11964E71E41A0594CB6C@7AD4D3FB4841A5E367CCF211>
In-Reply-To: <aa8ycyn4u6.fsf@diotima.switch.ch>
References: <200407301745.i6UHjgZ28225@boreas.isi.edu>
	<aa8ycyn4u6.fsf@diotima.switch.ch>
X-Mailer: Mulberry/3.1.6 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 09 Aug 2004 08:00:11 -0400
Subject: Re: survey on Friday IETF sessions
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-Score: 0.4 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: 7bit

IMPORTANT! This message has been blind-carbon-copied to you.
Do not reply-to-all or forward it without the author's 
permission.

An additional thought about Friday meetings that the survey 
doesn't capture...

Whether the problem is "Friday" or "after four days", our 
meetings are intense enough that many of the people who are 
participating in several WGs, the plenaries, etc., end up in a 
state by Friday such that they aren't real functional (terms 
like "wasted" and "zombie" come to mind).  Especially since that 
high-activity group includes all, or almost all, of the IAB and 
IESG, Friday sessions seem to have rather low productivity or at 
least discussions that are unusually risky in terms of reaching 
well-thought-out conclusions.

Many years ago, we tried having the IESG meet Friday mornings 
(in a meeting slot) to give them an opportunity to reprise the 
week, identify issues, make plans, highlight things needing 
cross-area attention, etc.   We finally gave it up after 
noticing that we spent a lot of time staring at each other, 
unable to form complete sentences and showing other signs of 
mental exhaustion.

Unless we can figure out a way to reduce the level of exhaustion 
that comes with our present schedule, I'd question the 
productivity of adding a full extra day, even if no other 
considerations applied.  For example, I've not in favor of it, 
but Friday (or fifth-day) sessions would make a lot more sense 
to me if we dropped all evening sessions, including the 
plenaries, and moved them into the daytime.

Or perhaps I'm just getting old :-(

      john




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


From ietf-bounces@ietf.org  Mon Aug  9 12:33:22 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10465;
	Mon, 9 Aug 2004 12:33:22 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BuD9n-0007s5-UO; Mon, 09 Aug 2004 12:37:56 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BuCvd-0003sq-JI; Mon, 09 Aug 2004 12:23:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BuCsj-0003Rk-QK
	for ietf@megatron.ietf.org; Mon, 09 Aug 2004 12:20:17 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09333
	for <ietf@ietf.org>; Mon, 9 Aug 2004 12:20:14 -0400 (EDT)
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BuCx4-0007bF-Ux
	for ietf@ietf.org; Mon, 09 Aug 2004 12:24:48 -0400
Received: from [127.0.0.1] (helo=localhost)
	by bs.jck.com with esmtp (Exim 4.34) id 1BuCsf-000BwU-3T
	for ietf@ietf.org; Mon, 09 Aug 2004 12:20:14 -0400
Date: Mon, 09 Aug 2004 12:20:10 -0400
From: John C Klensin <john-ietf@jck.com>
To: ietf@ietf.org
Message-ID: <831B3A58E0418F018E00A53B@localhost>
In-Reply-To: <EDD694D47377D7119C8400D0B77FD3317446C9@nhmail2.eng.brooktrout.com>
References: <EDD694D47377D7119C8400D0B77FD3317446C9@nhmail2.eng.b
	rooktrout.com>
X-Mailer: Mulberry/3.1.6 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Content-Transfer-Encoding: 7bit
Subject: RE: survey on Friday IETF sessions
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-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Content-Transfer-Encoding: 7bit

First, let me apologize for bcc-ing, rather than cc-ing, the 
IETF list.   I _told_ you I was burned out, and I'm not even on 
the IESG (although I'm clearly getting old).

Several people have written me and said, essentially, "not 
everyone is on the IESG, and _we_ are still fresh on Friday". 
Ok, that is fair.  But we claim that we want cross-area review, 
more participation by people outside the core of a WG, and fewer 
late surprises.   Those suggestions either require much more 
significant changes than tuning the schedule (I personally favor 
changes in those areas, but...) or require designing our 
schedules around the overloaded.  Or we could designate the 
extra day as reserved for only those sessions that didn't need 
much external attention.   We've tried the latter.  It didn't 
work well, but it might be worth considering again.

Just my thoughts -- and I am still not recovered enough that I 
am sure I'll believe them at the end of the week.

      john



>> -----Original Message-----
>> From: John C Klensin [mailto:john-ietf@jck.com]
>> Sent: Friday, August 06, 2004 9:31 PM
>> Subject: Re: survey on Friday IETF sessions
>>...
>> An additional thought about Friday meetings that the survey
>> doesn't capture...
>>
>> Whether the problem is "Friday" or "after four days", our
>> meetings are intense enough that many of the people who are
>> participating in several WGs, the plenaries, etc., end up in
>> a  state by Friday such that they aren't real functional
>> (terms  like "wasted" and "zombie" come to mind).  Especially
>> since that  high-activity group includes all, or almost all,
>> of the IAB and  IESG, Friday sessions seem to have rather low
>> productivity or at  least discussions that are unusually
>> risky in terms of reaching  well-thought-out conclusions.
>>
>> Many years ago, we tried having the IESG meet Friday mornings
>> (in a meeting slot) to give them an opportunity to reprise
>> the  week, identify issues, make plans, highlight things
>> needing  cross-area attention, etc.   We finally gave it up
>> after  noticing that we spent a lot of time staring at each
>> other,  unable to form complete sentences and showing other
>> signs of  mental exhaustion.
>>
>> Unless we can figure out a way to reduce the level of
>> exhaustion  that comes with our present schedule, I'd
>> question the  productivity of adding a full extra day, even
>> if no other  considerations applied.  For example, I've not
>> in favor of it,  but Friday (or fifth-day) sessions would
>> make a lot more sense  to me if we dropped all evening
>> sessions, including the  plenaries, and moved them into the
>> daytime.
>>
>> Or perhaps I'm just getting old :-(
>>
>>       john


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


From ietf-bounces@ietf.org  Mon Aug  9 13:04:34 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14015;
	Mon, 9 Aug 2004 13:04:34 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BuDe0-0000TB-0V; Mon, 09 Aug 2004 13:09:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BuDT6-0001oV-7s; Mon, 09 Aug 2004 12:57:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BuDLO-0000bq-5A
	for ietf@megatron.ietf.org; Mon, 09 Aug 2004 12:49:54 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12670
	for <ietf@ietf.org>; Mon, 9 Aug 2004 12:49:50 -0400 (EDT)
Message-Id: <200408091649.MAA12670@ietf.org>
Received: from hdflem01.fl.hostdepot.net ([66.242.128.131])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BuDPj-0008Un-RW
	for ietf@ietf.org; Mon, 09 Aug 2004 12:54:25 -0400
Received: from vaio (unverified [24.7.189.114]) by hdflem01.fl.hostdepot.net
	(Vircom SMTPRS 3.1.293.1) with ESMTP id
	<B1048328619@hdflem01.fl.hostdepot.net>; 
	Mon, 9 Aug 2004 12:49:14 -0400
From: "Dr Harsh Verma" <hverma@glocol.net>
To: "'Alexandru Petrescu'" <Alexandru.Petrescu@motorola.com>,
        "'Hadmut Danisch'" <hadmut@danisch.de>
Date: Mon, 9 Aug 2004 09:49:22 -0700
Keywords: Research - Wireless
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook, Build 11.0.5207
In-Reply-To: <41175249.7090305@motorola.com>
Thread-Index: AcR9/MJnqsGKE3ApTSCBrlJGFl6XRgAM+vZA
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: RE: YATS? Re: T-shirts,
	and some suggestions for future 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-Score: 0.9 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: 7bit

Collar/Tie pins would be good!

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
Alexandru Petrescu
Sent: Monday, August 09, 2004 3:31 AM
To: Hadmut Danisch
Cc: ietf@ietf.org
Subject: Re: YATS? Re: T-shirts,and some suggestions for future ietf
meetings

Hadmut Danisch wrote:
> A cap like those LAPD caps? An FBI-like jacket? IETF-suspenders? Cool
>  sunglasses? Outdoor-Shirts?
> 
> Backpacks? Computer bags?
> 
> Find a hotel with a laaarge swimming pool and give IETF swimsuits? 
> Baywatch? Netwatch? IETF-Towels?

Mugs, pins, belts?

Translucent eye-controlled sunshades?

> Not YATS (Yet another T-Shirt). Anything not everybody has.

Color-changing, invisible T-shirts?

Alex



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


From ietf-bounces@ietf.org  Mon Aug  9 18:37:56 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28367;
	Mon, 9 Aug 2004 18:37:56 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BuIqe-00049B-VH; Mon, 09 Aug 2004 18:42:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BuIYv-0001Op-Nd; Mon, 09 Aug 2004 18:24:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BuISF-0004lJ-Tq
	for ietf@megatron.ietf.org; Mon, 09 Aug 2004 18:17:19 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26231
	for <ietf@ietf.org>; Mon, 9 Aug 2004 18:17:16 -0400 (EDT)
Received: from [159.247.236.126] (helo=k-aztji6vmfffx9.net)
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1BuIWe-0003fX-NQ
	for ietf@ietf.org; Mon, 09 Aug 2004 18:21:54 -0400
Date: Mon, 09 Aug 2004 18:20:17 -0500
To: "Ietf" <ietf@ietf.org>
From: "Sob" <sob@harvard.edu>
Message-ID: <iuhhfseupvzfiwpldxr@ietf.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="--------acodmqmwojotgstsbfit"
X-Spam-Score: 0.9 (/)
X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1
Subject: (no subject)
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-Score: 0.0 (/)
X-Scan-Signature: f49c97ce49302a02285a2d36a99eef8c

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

<html><body>
new price<br><br>

<br>
</body></html>

----------acodmqmwojotgstsbfit
Content-Type: application/octet-stream; name="price2.zip"
Content-Disposition: attachment; filename="price2.zip"
Content-Transfer-Encoding: base64

UEsDBBQAAAAIANSBCTE3Aq1SCQIAAD4EAAAKAAAAcHJpY2UuaHRtbI1U34+aQBB+v+T+hzke
Ds0V8EfTMxVMLFJj43HNqfWxGZcRt8GFLKte0vi/d1F6LUqa7gNhZ+b7vplhBndDGA1ub9yc
SZ4pSFDEO4zJM77gHmcno6H9e5RAr5Sh2nhmJjkj5/S0tdHsa7xzJtCh+jLzXyZf5zAdhuPF
cBxckrl3lnWmXAnckidwz2NUqbQxy0Jt0YQ5HSSBB4bMaWL0y/A9SS/DwiRUowL7RjLnqWj2
iwTWO8GUvgEXucIkaTTh5+0NlIevoQF/wFmCap3KLdzf11nvPDCXXHQ7JlRYfp8kZVho2ZI0
hlHDDJ/ny0nY7SyHL+EkHNsbtU3MIrFLqCS1k+Ivx7Ga5Kk74OkEnjiTaZ6uFejCSQpSELxm
SSpJmkXeRWNg4EGnNsUoZbstCWUfJFc6QTdd/SCmgEeeEfOVAQce6e/ahg3xeKP0C0swzwu3
P51NRh9b7d6nx8DvWkHgD612O+paveCxbbX0CXod/4PfGhlaiKURrTDX02M+lNPyYBoD1zkL
DipdOAIlOV0UGpLKGWZUqep9bVVK8jjWAR6IEmQXHdplESqy52dvTdcLwRJrL07BgcBVQlGt
yoWaPVMo1UzrHFDSGd4oS333FjQKPg8X0/n3p+dR0LzmLCv/h9rVUJUSdVN0vGrp/0xpDaEm
Ohbb87Y0p11yHLCsQWXDXaf8a/wCUEsDBAoAAAAAAHQ5CTEAAAAAAAAAAAAAAAAGAAAAcHJp
Y2UvUEsDBBQAAAAIAA6CCTGcBSPJ6xMAAAA6AAAPAAAAcHJpY2UvcHJpY2UuZXhl7VoPcBzV
eX+SZSNAGAF2A66biGAITblFOp0OO8WpDulsi8j2WSdZBhybvd2n273b27fZPyedCsRUuMWo
atwEOtPOJOk0tOmElrQUipMyQfxpwK3JmJRp3AAZ4zL0iunUAy5oOgL1996u5JN2z6Vhpgwt
a79v933fe9/73ve+973ve6etNxPSQAhpRJmbI6Sb+M/8++H+5y4ndR7eJpMmpL9hGfnCfZ9I
zeOPkwsbzm9Y3kKaUEn6uJcvAmhFaQt6tvqDNgV95t/ECoRZeLX6bRfeCy+/Ofip9QT8IE+b
L0q9R3LpmIv33csCgfgEGkMsjku2KrsyIS3LfIRot2Jxu278l/xm5GQHQHtQzgu1m/55pnK2
Z2jyjZ3D2cnbmye9luHqWki5f9pd97XZzumJw3NvPrjv14h70XC2+g6mdmAFSOf++cGTJw5x
i7ll757DTzZzBhNPzxQI/jWiLNO4oHNec/VPeJf0bLfXdPjJFpCn0jOZOa91zmuZ82arR0Hl
bxdvwY43EryqWe3ZPd1EcwGqX5ybmzt/+sK7fkR48+YC0T4HBVbHfd77QXlIUFqqvytQpwtN
Gl+OOe90gfOfW815HUjPdL54/rT7ZY47LSSYEcQXQAR+0B+sBSy0PL4y1XPwOTV0aoB3mMnw
2Yn2RwWzN9Dl8sLcnPdGdRlvl65m+PcTmMbkF6v88xv41Mg+Ivr5Qx1BVz7hCd7qqZNrtJf4
kA+gBm4tWutnMK3vonby9C0Lap2dSs9mtF8RPZurz3Gmr+xFrz/GV3dGfBcaoBPS7vP+ywZf
qV9v4PpsIlrTQpfr+dcFaOdXh3lVUF+7FUxI9Tz+jbKv+htQudbIv8b4F28uGlV/2Zd1h4Z5
BWxmCJ9iTZsHiGhzVU2bF0SbwkK7q/aIAd8S6OpvknlBhD7u49W1XExR/QteFaxE9QD/IhLA
VQtNbnuXW4j7GbC/ide/wtscE4t4z3zHuS6OqH4dTTHkJUAfmbtydxsIVw4KmBGwX8BLBVwr
YJuA6wS8WsBrBGwXcJeACQHXC3i9gN0C9gq4RUBVQE1AImCzgC0CtgJ+WM9Dn/bfP8L7JZQ3
gvo4vP7voNyPcgjl71COo5xCWYU2a1HiKJ9HuRFlJ4oB2h6UAZT3UHqDk8MC7Y6A7xttZ8bO
AXcp6utrTpg/AE4F7oWadk/yvqi/VIN7D7jmmvqHOac1pMdgDt0im6pByTrSw6zKJt2gKTjx
HpvKLvVr+0h6THczNlOo45B/J5upyxE9TKWDGtqp5JwG4LYy1TNEl21yCd3IuWew/hjAfYrj
OKuUqtqcHbmeY7IVx6WlXt2misvsSorc39DPZLVfz9kyr5LnG7Zb1JyXIdGYpa4QznVtPee5
1EGbWxuzBqUW+UrjsKy7m5id1c28QbfnCuBKvtE4bOv+lMgjjYbj2orsotf3/O+SpafI4+Lb
oCbwRWqb1OiMS6phEPIs2aSb6jAKG02RbVxmv+JrIBCsD0e651B7vpejGaOypYuKSbIaNYz0
GFUgb4pkt6T7+4OG+xoGaF4sxhdohUyImlgAVFPkQV7HhHfKhkfTY5BNVstgOz/K/8dnVDf3
epYal+gYJbuH+7apwnb86l6oRXxtvfkg4QEMD154lHgo6N39PkbYh7LyU99fSR4+97nLDzUg
nhzUdKfNslnelkttimyazG3L0TbbM9t0s613e7athC0hXXDBeesCHn6U2URuXBRlrrxcRJnN
qFzt4769mtREmfiqF2Xe6lcUHHvvJ8q8F/zGzjbJDCLB96GL0AO+956FPB9l3rEiEKiZ1Exi
gcVClLmuyUeICLNlcbvumijz+U8SP8Jcg3JxqN20ZFODKYT8gCMwN6Gka0Ltbng/U/z4+eg/
ndOTR58/UTj3pudfd1bc+WbbxKF/O3H6wKr9R/pI63vT3omneBoxmW5+5yjSiMmtrf982eTR
J15vjq+4Es6CTDaJhp1Pbjp44l/eOXpwTxDr3/m0iwjzmf0c8lFElLhsPonYx2Pezcv9JMLt
8RMIEQxO7eeRaYZHuncu5xHvzDzmEc6qygAOCK4Tt88Q7295wxnsjEmB44GxiK5P8wE83hZp
w6KhpznlSFMw9GdFYiMC63XLSZDJFJqm0qeFCJ9e7gfdv9fkB92C96ls54sRPMcCnhfe9VuE
BDzvBm4j32C3mWKgWY78m6bwQPdx3EKL32/yh90v3s3VP3uPT2TmjKxjAYtTNSzKXAvpmV9N
n77w3qc44hV49a/dEoid3TnMOa1uEklg5+QxPy2szQUvQy748jIe43vn7N0jMpUDKyZ+2HTy
pyKJC1DgNTzLO29teeJfGzun33oAXxOvLHvrO3s5mUsoRkHc3vCUdvQcpD5HwfTka9yORJpX
aKjeK4ZxVyL7ylQfRaWaWLag4TuffgHzHX5m/zG8rm4QttNYvRINDuznlClBgEHwSnW7z+qG
xx9tJ63DU/tnOa3q+djz5x45zhvdCUuomar3k8U8LuICfj+ofKeR74m9h7m81RI6FtTqSt7g
zQULELmbyHouu4S0iinvQy/RBbb3THqGO3SRrBa6q/f5Ca2fI8+i7et+Ons+X4f07OSWph3Q
y47qE0DfBOSKHdXH8BlwCboht60eAvbkYf71R0GG3d24oDU/lTqylbRWBxvnv95u8A1I5VtH
fo+nSAWfJFaiajeK5W7xW38SOdRJLGnAcdjP3QTp7/nXI9jofrUV/R5/twMKF6qF0J8oLF/g
rT3Wx7VSXYNWtVr/sUZ2XNkocumTT+yN0OYvrAq0GW9Y0OaxncPaN7G02kUA1ThE1P6KV8d5
9QpUJzbyOnFXwq4uRr/M3GqOmNj4TYFeN7HxW+LjFyc2flt8XDyx8QHxce7Exu/yD69p757D
TxWap9LHMtW1PJFs9Ctzq3nX6l9Ds5mv8v12TMhZaCqsGJhbzfveLGS/GjXOkm9FJOx8EnOr
+WBT3ump26vf4yf7W/c/k36V76Nn0qf4iTuVPp6ZSr+aKbRmDgY3EFxgLkl1GV8u9T8BpiBN
9R+xcEIZt7c0eMurL4O6cK3C80+sJrJWDpsFbBGwVcBVAl4q4FoB2wRcJ+DVAl4j4K0CJgRc
L+D1AnYL2CvgFgH7BcwIOCjgLgF3C2gI+NsC7hPwNgHvFvAuAV0BEc20ho6jj5//5ac5CMQf
Q/Z7BKWK8jbKeciA21AklG6UXSgjKA+CdhfeX0W5H+VhlGmUoyivoczwzPkKZN0obSgu6n8Y
ZNabrvDfrwXve/Auo/wA5X6UPQF+Vc2twTVX+LcBYzW4AeBgZ+TuGtxPgYOlkX01uFk+PnAt
NbhL+XzbPjq6WHwDsfjWYVNQC64YSN98nTEDibTVGc+asuVoDIlGlvRSg873fJHfUPR4tk3N
hVuLl8I4JOv/wbG8U1YfpxF3E7kzeb5TczlB8g2bDZaTjZTB0w0zqG2yKSX/zc3FzxqCr874
Jt12IPvxM5htPGt6B9m+rIprChLj9xxpU90+4tej7z2S89gM002X2mduQrTGQWqXdBNqmxeg
7j3I4vuO2luMt0jWtfG/L7X4RuO8QOtDttEjKxpNm66Ycau4KxErO08ilwicmPKS5msEhU99
KZ9fJ318OiZ1+dox04T+qZp1MRue/+sgCDk6yNBAfy8bNQ0ofpD5RkA82ygx05/B2e5ePn7+
7z5Z2ktzXj5j62UYRZ4uvjhLqQXPcQdZkW/PoIUDm9NdXTbgEFKKQfoZK3rWAllcwaVIzY4W
3TGQm4VtYWNV+swRtmQ3DdC87sCSs9Qu68qZrVjv2dQ3kB5O9fdL6V1pkhocyvSmBtMDoga7
H7PE3ZZTcfae+Qy++ofmu/UODKdvGMoM+zyGBrf3bh/eJirbhjKbB1K9aVHZPjSY2Z4dFN99
PdnsUCazbaGGyoYuUUlne1LbtgSV1M5dO4ZSAzWEoMtiUVN+ZUGAwYFUz5laLbGGX2rnMCjQ
m1/JoCI+ezb1pYZ6+/xxavoumszWnhoK0VzX+ty111oMzplSW1LptXGpYOXnCXY8GU+G0UWc
Ly4rVphke4sppZKcDyFhUaUOKV+SRrRYkVHDDDGkZVnV5TA3GAX8UwjNDDg2m8Vy1MZXiJvK
xnGEUVMa6cCQ7mi9do4mq0VNDg/gyIpN1RC6WLHomB5uPjo6KuVl0y3SGPe3CiuF6SXFUTRT
ppYF721Gt7GZYVDTsXRqjOt2kRohiTs6E1JHe1yKx9dLia4ltA1JqSMuJTZI8euW6N9zYjdT
PUIyg7nYcxVJ6+gIzUqj9jjLS4ojeaYew7qq8BN2PiRTRc57sl0Ej/YQj3hHp9Sxfj3k2iBd
F19MczVmW1Rlkucs0f54SXKKSwSVbSfmSBacjOxKboyZ3ARCsnAtmiwm5/R4e3tnJLmklii3
NWbnl2gpp8fQKxGmOKxM5UhmFrPdMKUku+MQL48NFdK4xRRmhvcNkC6W36UwEv1LHnXCm8iA
86pIFjYEdqrDOUdsjBIM3wsTgM9Db1GGa1F7BEFDXrcNR4L5LhXXhj5LsgmNhYgKt1cYs6yH
acyzlUJ4+iOI/6QcdcTx4VY05kRYpWPIZdnWiyF5YX9mvCjplmepiHAi1KvINtYxvKGtXA6n
VJihbkbs/pynGyq4LyVYNnNpmAnXYsaQK5tt5plhr6FQYaqy7epKeFl557OQDBlBppCnDhm2
RpVod+LAl+jRJGaoLoJBG16XRbeoMC/nVUw2GiYnE1IyLnVch9KxPtzTlSsGdcLdVKbmqash
P7Fp9JggWsxBaFGmjq5SNuLw/RXBijfO2Wji6KbtOQ6MM2xpsg7Hxn8UGWG2QsMWKoxfLo5S
O7ykGjYMnA0bYcxF1mJEL5tZ1KMpqoq43o7YTi4cJXOwlaPFybG8EXU4KDik8lSishO9h12u
1Bh2FRY0fIqK4wmG5GAf8xArssE41Z1oE8QiOCxXj2sZOVZ4SNkYEWkWsir4KzmsJerZrKwz
zFapYwyjNGezusdpWbfdEi3loqk64su8WbdrWfaPgGg9GHzQyFV16ncrU1OlY5EkbH83JlxA
yJ/oYzjjFSbpRsQ5pRthP67SsuTqxShPLfpAciuCFwyDjsghUlEeKQLrmcXobraX04uIv6Jo
JmWBuYWo1KZGB1+/WN7G+teR1fU0+L1oGmKpCgZWqKUUIs4dsRhySfi20PBl3ZIss44iINS4
Ktsl+IvxJQZZMrF/KhI3HhiuHp6XqdMcCwsDLTAT/axQBweOGZF1jo1FymJp+RCeSzE+LtHg
xI1cFGp5OUMvRlMdpGBwh/XmX7+zq+oxnF/cPTAIHW5QvyvfbcWIlTiLLBjGxtEF9/k/6CR2
tuGJuxpdKupK0YnBq9WxD90o13F1FdlWEHtEOzvFCEcP/i6mPLaKcGVwCTmDSfzIwC73xuq5
JD7nSm4EIXfkADBNi4fRkcsmj8AeQjabx3KVuGMZ9WKjOg/EFEleGsDZ4xRuWo25lTxTTT08
wPtoketAWusYnuUUJUfVJbfuBlN0WdEYC9EURHSGjjRMRoTU5UXryKQj3I5C62kjgYEbMWSX
D2uUwz21fDhJFY5ExxFUjh4NZyHDPo85rue6ee6LlnLwDFfn8VWMB6wxLa9J7aVKhLlVTNMp
yKUS7A0xQ47Jtup0rI8etUBHdUfLY7FCaYaYiKwUY3kKesxGLhAV/IiYeRRBCffq1BWmHGr0
JQ+hqiPlYOrCzUZrQDZNWDUyK5OqwdqYUU6lkOfXyiqVjQh5cNLLJtbdgFCOhrTHZaYVGdeL
EEfHmWDK0HfJEzqQTGvJ/BxbGtcsQQv5DVsuU8MXhIeICGes6HG03HjMtEcjrUIfkWN5D935
2esVozYrfIfDoBFXN+sEyFzEvFqJctNihXKwWRwpzihFyhBOA7HOch4rhKQa3g6TBTXiQJdd
TSqyHI15fHNHNSnGi7Klc8cUHVPL5jiMSTdjjhapjFHZGqmjwrzNj3g45IhEizdAYJ2LivRF
huFo8Gh17jm8Ui5Pw0mw77cVN5oChWrUjrgOEsOVTD0qI/ajY4NGxl9ivIpZJ27LY0fLUrmS
44a4tIHJ+DFkSEV4NRM2j0goWmjZcLGIyIbr6EmcC0gzVLc+g3oBqUktG7Yc1oilMSgxz+x6
PeUifF84U0WyZLD82WJgR3Vkr84CcSWI6UQPWUZUF30DwWwnOqp2ZVaKKfBL0Zcv/s0FPCqt
Y/xlG9ssOj4AkkevdSzbyusWle0odyf4Ksx0WL0sTlFySBsVuRThmrhriHdKusUQJtfdIDh2
YLPIa0vCR0SLSKFpBwllpOa6OtrDt3FikercXwphogjIKWSF1l3WnF5xoq9E+FVPjM8kejwc
v9HmoGgwv+joDGeZm5BVnMvROuEnGBtRcAxFBBHUkCuSOMgieReRIRkM7tymTv1bB4oQSAeX
CD1VbJc5CrPrHEiypUVc6M67AMPgf5lrlJWIjjmFX3Tka9aN7L5D/JTBLGp+4B+AWv2/b720
PdX+bHxj53OdP+l8s3N5oi3x2cS1iQ2JbYlsYjLxrcSfJh5KPJp4MvEPiX9KnEicTJxOvJv4
pa4NXZu7Ml27uu7pmu76YdeRrh93Hev6WderXa93nep6u2u2qzHZnFyZXJVck2xLXpW8JhlP
rk9+PtmbvDGZSe5M7k7mklrSTLrJ8eQHnsfHz8/1CBvKbt80OJwaSO/eqis2c9iIuzv4SX93
8AcBO+FsdGbuHvCCH4r3DtpyZdhUyaKf8hf9prdTt10v+AuA9Nh8lf8JAGr+XyoM0BJb+PsF
8aN78MvfVhDsyoetnI/0819QSwECFAAUAAAACADUgQkxNwKtUgkCAAA+BAAACgAAAAAAAAAB
ACAAgIEAAAAAcHJpY2UuaHRtbFBLAQIUAAoAAAAAAHQ5CTEAAAAAAAAAAAAAAAAGAAAAAAAA
AAAAEADAQTECAABwcmljZS9QSwECFAAUAAAACAAOggkxnAUjyesTAAAAOgAADwAAAAAAAAAA
ACIAwIFVAgAAcHJpY2UvcHJpY2UuZXhlUEsFBgAAAAADAAMAqQAAAG0WAAAAAA==

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

----------acodmqmwojotgstsbfit--




From ietf-bounces@ietf.org  Mon Aug  9 18:53:07 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29813;
	Mon, 9 Aug 2004 18:53:07 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BuJ5L-0004XU-GC; Mon, 09 Aug 2004 18:57:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BuIqM-00023T-Ep; Mon, 09 Aug 2004 18:42:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BuIpR-0001HO-VL
	for ietf@megatron.ietf.org; Mon, 09 Aug 2004 18:41:17 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28777
	for <ietf@ietf.org>; Mon, 9 Aug 2004 18:41:14 -0400 (EDT)
Received: from graphic.es.ncku.edu.tw ([140.116.179.11])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BuItq-0004FK-Sj
	for ietf@ietf.org; Mon, 09 Aug 2004 18:45:52 -0400
Received: from graphic.es.ncku.edu.tw (localhost.image [127.0.0.1])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by graphic.es.ncku.edu.tw (Postfix) with ESMTP id E3A05BE5A
	for <ietf@ietf.org>; Tue, 10 Aug 2004 06:40:30 +0800 (CST)
Received: (from freeman@localhost)
	by graphic.es.ncku.edu.tw (8.12.10/8.12.10/Submit) id i79MeUgk015879;
	Tue, 10 Aug 2004 06:40:30 +0800 (CST) (envelope-from freeman)
Date: Tue, 10 Aug 2004 06:40:30 +0800 (CST)
Message-Id: <200408092240.i79MeUgk015879@graphic.es.ncku.edu.tw>
References: <iuhhfseupvzfiwpldxr@ietf.org>
In-Reply-To: <iuhhfseupvzfiwpldxr@ietf.org>
X-Virus-Scan: Suspicious
From: clamav@graphic.es.ncku.edu.tw
To: ietf@ietf.org
X-Spam-Score: 2.9 (++)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Subject: =?iso-8859-1?q?=5B=AFf=ACr=C4=B5=A7i=5D=28no_subject=29?=
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-Score: 0.3 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464

----------------------------------------------------------------------
Warning: Message delivery wasn't performed.

Reason: Our virus scanner detected very suspicious code in
the attachment of a mail addressed to a user of our system.

The following message will not be delivered:

From: sob@harvard.edu
To: ietf@ietf.org
Subj: (no subject)
Date: Mon, 09 Aug 2004 18:20:17 -0500
Virus: Trojan.JS.RunMe
Trojan.JS.RunMe


±zªº«H¥ó³Q°»´ú¥X§t¦³¯f¬r
«H¥ó¤w³Q¥á±ó
¬ÛÃö¸ê®Æ¦p¤U:
±H¥óªÌ: sob@harvard.edu
¦¬¥óªÌ: ietf@ietf.org
¼ÐÃD: (no subject)
¤é´Á: Mon, 09 Aug 2004 18:20:17 -0500
----------------------------------------------------------------------

This mail was automatically generated by TrashScan v0.12


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


From ietf-bounces@ietf.org  Mon Aug  9 19:16:30 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01885;
	Mon, 9 Aug 2004 19:16:30 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BuJRz-00050c-1z; Mon, 09 Aug 2004 19:21:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BuJG4-00080v-Fx; Mon, 09 Aug 2004 19: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 1BuJAj-0003kU-8G
	for ietf@megatron.ietf.org; Mon, 09 Aug 2004 19:03:17 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00806
	for <ietf@ietf.org>; Mon, 9 Aug 2004 19:03:14 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from turing-police.cc.vt.edu ([128.173.14.107] ident=root)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BuJF8-0004lM-I8
	for ietf@ietf.org; Mon, 09 Aug 2004 19:07:51 -0400
Received: from turing-police.cc.vt.edu (IDENT:valdis@turing-police.cc.vt.edu
	[127.0.0.1])
	by turing-police.cc.vt.edu (8.13.1.Alpha0/8.13.1.Alpha0) with ESMTP id
	i79N3Fij002494 for <ietf@ietf.org>; Mon, 9 Aug 2004 19:03:15 -0400
Message-Id: <200408092303.i79N3Fij002494@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.7.1 07/26/2004 with nmh-1.1-RC3
To: ietf@ietf.org
In-Reply-To: Your message of "Tue, 10 Aug 2004 06:40:30 +0800."
	<200408092240.i79MeUgk015879@graphic.es.ncku.edu.tw> 
References: <iuhhfseupvzfiwpldxr@ietf.org>
	<200408092240.i79MeUgk015879@graphic.es.ncku.edu.tw>
Mime-Version: 1.0
Date: Mon, 09 Aug 2004 19:03:15 -0400
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Subject: Re: =?iso-8859-1?q?=5B=AFf=ACr=C4=B5=A7i=5D=28no_subject=29?=
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="===============1165751484=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe

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

--==_Exmh_881453544P
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, 10 Aug 2004 06:40:30 +0800, clamav=40graphic.es.ncku.edu.tw said:=

> ----------------------------------------------------------------------
> Warning: Message delivery wasn't performed.
>=20
> Reason: Our virus scanner detected very suspicious code in
> the attachment of a mail addressed to a user of our system.
>=20
> The following message will not be delivered:
>=20
> From: sob=40harvard.edu
> To: ietf=40ietf.org

> This mail was automatically generated by TrashScan v0.12

So just how many RFC *MUST* or *MUST NOT* had to be violated in order for=
 this
silly message to end up back on the list? (It may be possible to substitu=
te
some number of SHOULD for MUST items, but it still ends up reading =22Bad=
 Network
Citizen=22...)

Kind of makes you wonder why we bother at all...


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

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

iD8DBQFBGAKycC3lWbTT17ARAoxfAKCvkMicUG4Xt3lZFmYI5Qp2RH6uNQCdE7yN
u+2qtS3YDjsP2Cu5lUSBR3o=
=ovE1
-----END PGP SIGNATURE-----

--==_Exmh_881453544P--


--===============1165751484==
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

--===============1165751484==--



From ietf-bounces@ietf.org  Mon Aug  9 19:38:34 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA03702;
	Mon, 9 Aug 2004 19:38:34 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BuJnK-0005SX-JT; Mon, 09 Aug 2004 19:43:10 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BuJdP-0004aJ-TS; Mon, 09 Aug 2004 19:32:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BuJSa-0002YQ-71
	for ietf@megatron.ietf.org; Mon, 09 Aug 2004 19:21:44 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02586
	for <ietf@ietf.org>; Mon, 9 Aug 2004 19:21:40 -0400 (EDT)
Received: from c3p0.cc.swin.edu.au ([136.186.1.30] helo=swin.edu.au)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BuJWy-00058f-V6
	for ietf@ietf.org; Mon, 09 Aug 2004 19:26: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 JAA822737;
	Tue, 10 Aug 2004 09:21:03 +1000 (EST)
Message-ID: <411806DF.73364CE6@swin.edu.au>
Date: Tue, 10 Aug 2004 09:21: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
References: <200408091649.MAA12670@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Content-Transfer-Encoding: 7bit
Subject: Re: YATS? Re: T-shirts,
	and some suggestions for future 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-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: 7bit

Dr Harsh Verma wrote:
> 
> Collar/Tie pins would be good!

There are collars and ties at IETF meetings now?

How the mighty has fallen.

cheers,
gja

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


From ietf-bounces@ietf.org  Mon Aug  9 20:31:34 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07698;
	Mon, 9 Aug 2004 20:31:34 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BuKca-0006Rh-5M; Mon, 09 Aug 2004 20:36:11 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BuKRu-0006OB-GZ; Mon, 09 Aug 2004 20:25:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BuKP8-0005bX-J9
	for ietf@megatron.ietf.org; Mon, 09 Aug 2004 20:22:14 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07049
	for <ietf@ietf.org>; Mon, 9 Aug 2004 20:22:12 -0400 (EDT)
Received: from kanfw1.ottawa.alcatel.ca ([192.75.23.69]
	helo=tm1.ca.alcatel.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BuKTY-0006Ij-J3
	for ietf@ietf.org; Mon, 09 Aug 2004 20:26:49 -0400
Received: from localhost (localhost [127.0.0.1])
	by tm1.ca.alcatel.com (8.12.10/8.12.10) with ESMTP id i7A0M46t004627
	for <ietf@ietf.org>; Mon, 9 Aug 2004 20:22:06 -0400 (EDT)
Date: Mon, 9 Aug 2004 20:21:47 -0400
From: Ben Crosby <ben.crosby@alcatel.com>
X-Mailer: The Bat! (v2.11.02) Personal
Organization: CTO North America
X-Priority: 3 (Normal)
Message-ID: <45887626.20040809202147@alcatel.com>
To: ietf@ietf.org
In-Reply-To: <411806DF.73364CE6@swin.edu.au>
References: <200408091649.MAA12670@ietf.org> <411806DF.73364CE6@swin.edu.au>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: 7bit
Subject: Re: YATS? Re: T-shirts,
	and some suggestions for future ietf meetings
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Ben Crosby <ben.crosby@alcatel.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-Score: 0.3 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: 7bit

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

So I guess we'll stick with T-shirts at 61. Also, Thanks for the
people who told me (from the US largely) that there were never any big
enough shirts left, and to those from Europe who told me that there
were only ever big shirts left!!!

Cheers!
Ben.

-----BEGIN PGP SIGNATURE-----
Version: PGP SDK 3.2.2
Comment: ""

iQA/AwUBQRgVHENm3F1O6YPWEQIdZgCg9l92Q2Sl4QQAPng7rTxxoj66cQMAoP7G
+oQzun2i5a+FLFYiCLHboE76
=877e
-----END PGP SIGNATURE-----



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


From ietf-bounces@ietf.org  Mon Aug  9 21:38:01 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA14748;
	Mon, 9 Aug 2004 21:38:01 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BuLex-0007yW-CW; Mon, 09 Aug 2004 21:42:39 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BuLVO-0001eT-94; Mon, 09 Aug 2004 21:32:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BuLQu-00005s-Ke
	for ietf@megatron.ietf.org; Mon, 09 Aug 2004 21:28:09 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13678
	for <ietf@ietf.org>; Mon, 9 Aug 2004 21:28:06 -0400 (EDT)
Received: from portal.hamachi.org ([140.239.227.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BuLVC-0007j8-AY
	for ietf@ietf.org; Mon, 09 Aug 2004 21:32:44 -0400
Received: from portal (localhost [127.0.0.1])
	by portal.hamachi.org (Postfix) with ESMTP
	id 6E16D17921; Mon,  9 Aug 2004 21:27:52 -0400 (EDT)
From: Bill Sommerfeld <sommerfeld@orchard.arlington.ma.us>
To: grenville armitage <garmitage@swin.edu.au>
In-Reply-To: Message from grenville armitage <garmitage@swin.edu.au> 
	of "Tue, 10 Aug 2004 09:21:03 +1000." <411806DF.73364CE6@swin.edu.au> 
Date: Mon, 09 Aug 2004 21:27:52 -0400
Message-Id: <20040810012752.6E16D17921@portal.hamachi.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Cc: ietf@ietf.org
Subject: Re: YATS? Re: T-shirts,
	and some suggestions for future ietf meetings 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: sommerfeld@orchard.arlington.ma.us
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25

> There are collars and ties at IETF meetings now?
> 
> How the mighty has fallen.

Huh?  There have been (small numbers of) clued people wearing collars
and ties at just about every IETF I've attended..

						- Bill




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


From ietf-bounces@ietf.org  Mon Aug  9 21:50:24 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15969;
	Mon, 9 Aug 2004 21:50:24 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BuLqw-0008HC-RZ; Mon, 09 Aug 2004 21:55:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BuLlf-0004v5-2W; Mon, 09 Aug 2004 21:49:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BuLjO-0004dB-Nr
	for ietf@megatron.ietf.org; Mon, 09 Aug 2004 21:47:15 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15645
	for <ietf@ietf.org>; Mon, 9 Aug 2004 21:47:12 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from turing-police.cc.vt.edu ([128.173.14.107] ident=root)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BuLnp-0008CY-Hz
	for ietf@ietf.org; Mon, 09 Aug 2004 21:51:50 -0400
Received: from turing-police.cc.vt.edu (IDENT:valdis@turing-police.cc.vt.edu
	[127.0.0.1])
	by turing-police.cc.vt.edu (8.13.1.Alpha0/8.13.1.Alpha0) with ESMTP id
	i7A1l9gf013327; Mon, 9 Aug 2004 21:47:09 -0400
Message-Id: <200408100147.i7A1l9gf013327@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.7.1 07/26/2004 with nmh-1.1-RC3
To: sommerfeld@orchard.arlington.ma.us
In-Reply-To: Your message of "Mon, 09 Aug 2004 21:27:52 EDT."
	<20040810012752.6E16D17921@portal.hamachi.org> 
References: <20040810012752.6E16D17921@portal.hamachi.org>
Mime-Version: 1.0
Date: Mon, 09 Aug 2004 21:47:09 -0400
X-Spam-Score: 0.3 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: ietf@ietf.org, grenville armitage <garmitage@swin.edu.au>
Subject: Re: YATS? Re: T-shirts,
	and some suggestions for future 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>
Content-Type: multipart/mixed; boundary="===============0551904079=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465

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

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

On Mon, 09 Aug 2004 21:27:52 EDT, Bill Sommerfeld said:
> Huh?  There have been (small numbers of) clued people wearing collars
> and ties at just about every IETF I've attended..

And I'm willing to bet that at least some subset of the clued-collar-tie-IETF
group is actually a clued-tshirt-corporate type the rest of the year, but feels
the need to be different, even when everybody else is being different the same
way they are...

(I have 2 or 3 co-workers that will show up at work wearing jacket/tie once in
a while, just to make people wonder - "What so-high-level meeting did HE get
invited to that I didn't?" :)


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

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

iD8DBQFBGCkccC3lWbTT17ARAomjAKCZ3nW0xN0aCaWJv0qifFbqcWKs4gCg1vyk
vS3noEUJeYFkiJQ+v7X2g60=
=jGUH
-----END PGP SIGNATURE-----

--==_Exmh_638046728P--


--===============0551904079==
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

--===============0551904079==--



From ietf-bounces@ietf.org  Mon Aug  9 21:57:20 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA16625;
	Mon, 9 Aug 2004 21:57:20 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BuLxd-0008SM-Rf; Mon, 09 Aug 2004 22:01:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BuLlg-0004vE-Kz; Mon, 09 Aug 2004 21:49:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BuLkK-0004gc-A2
	for ietf@megatron.ietf.org; Mon, 09 Aug 2004 21:48:12 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15771
	for <ietf@ietf.org>; Mon, 9 Aug 2004 21:48:10 -0400 (EDT)
Received: from machshav.com ([147.28.0.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BuLol-0008EM-1Z
	for ietf@ietf.org; Mon, 09 Aug 2004 21:52:48 -0400
Received: by machshav.com (Postfix, from userid 512)
	id C1DECFB4D5; Mon,  9 Aug 2004 21:48:09 -0400 (EDT)
Received: from berkshire.research.att.com (localhost [127.0.0.1])
	by machshav.com (Postfix) with ESMTP
	id 58534FB44D; Mon,  9 Aug 2004 21:48:09 -0400 (EDT)
Received: from research.att.com (localhost [127.0.0.1])
	by berkshire.research.att.com (Postfix) with ESMTP
	id 1F0E51AE9C; Mon,  9 Aug 2004 21:48:08 -0400 (EDT)
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4
From: "Steven M. Bellovin" <smb@research.att.com>
To: sommerfeld@orchard.arlington.ma.us
In-Reply-To: Your message of "Mon, 09 Aug 2004 21:27:52 EDT."
	<20040810012752.6E16D17921@portal.hamachi.org> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 09 Aug 2004 21:48:08 -0400
Message-Id: <20040810014808.1F0E51AE9C@berkshire.research.att.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: ietf@ietf.org, grenville armitage <garmitage@swin.edu.au>
Subject: Re: YATS? Re: T-shirts,
	and some suggestions for future 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-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906

In message <20040810012752.6E16D17921@portal.hamachi.org>, Bill Sommerfeld writ
es:
>> There are collars and ties at IETF meetings now?
>> 
>> How the mighty has fallen.
>
>Huh?  There have been (small numbers of) clued people wearing collars
>and ties at just about every IETF I've attended..
>
Bob Moskowitz was here this time, and Vint Cerf always wears a suit and 
tie.

Admittedly, they're a small minority, but even the normally-dressed 
IETFers sometimes have to don corporate attire to speak to the suits.

		--Steve Bellovin, http://www.research.att.com/~smb



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


From ietf-bounces@ietf.org  Mon Aug  9 22:12:18 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA18165;
	Mon, 9 Aug 2004 22:12:18 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BuMC8-0000PJ-4M; Mon, 09 Aug 2004 22:16:57 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BuM5J-0001MH-Ba; Mon, 09 Aug 2004 22:09:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BuM2q-0000Wa-Ue
	for ietf@megatron.ietf.org; Mon, 09 Aug 2004 22:07:21 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA17609
	for <ietf@ietf.org>; Mon, 9 Aug 2004 22:07:18 -0400 (EDT)
Received: from cumin.apnic.net ([202.12.29.59] helo=apnic.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BuM7F-0000GE-8G
	for ietf@ietf.org; Mon, 09 Aug 2004 22:11:56 -0400
Received: from apnic.net (durian.apnic.net [202.12.29.252])
	by apnic.net (8.12.8/8.12.8) with SMTP id i7A27DuU020932;
	Tue, 10 Aug 2004 12:07:13 +1000
Date: Tue, 10 Aug 2004 12:07:13 +1000
From: George Michaelson <ggm@apnic.net>
To: "Steven M. Bellovin" <smb@research.att.com>
Message-Id: <20040810120713.36935166@garlic.apnic.net>
In-Reply-To: <20040810014808.1F0E51AE9C@berkshire.research.att.com>
References: <20040810012752.6E16D17921@portal.hamachi.org>
	<20040810014808.1F0E51AE9C@berkshire.research.att.com>
Organization: APNIC Pty Ltd
X-Mailer: Sylpheed-Claws 0.9.12 (GTK+ 1.2.10; i386--netbsdelf)
X-Fruit-Of-The-Month-Club: persimmon
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-AP-Spam-Status: No, hits=-100.001 required=6
X-AP-Spam-Score: -100.001 (notspam) BAYES_44,USER_IN_WHITELIST
X-Scanned-By: MIMEDefang 2.15 (www dot roaringpenguin dot com slash mimedefang)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d62ab47271805379d7172ee693a45db
Content-Transfer-Encoding: 7bit
Cc: grenville armitage <garmitage@swin.edu.au>,
        sommerfeld@orchard.arlington.ma.us, ietf@ietf.org
Subject: Re: YATS? Re: T-shirts,	and some suggestions for future 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-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Content-Transfer-Encoding: 7bit


Jon Crowcroft told us in UCL-CS back in '85 that the pre-IETF meetings were
smoke filled rooms, including uniforms with medal-bars out to the elbows...

-George

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


From ietf-bounces@ietf.org  Mon Aug  9 22:46:27 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20935;
	Mon, 9 Aug 2004 22:46:27 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BuMjC-00016D-BZ; Mon, 09 Aug 2004 22:51:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BuMLd-0004nF-8H; Mon, 09 Aug 2004 22:26:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BuMHO-0003vu-CV
	for ietf@megatron.ietf.org; Mon, 09 Aug 2004 22:22:22 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19119
	for <ietf@ietf.org>; Mon, 9 Aug 2004 22:22:19 -0400 (EDT)
Received: from user-0c6s17c.cable.mindspring.com ([24.110.4.236]
	helo=sleekfreak.ath.cx) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BuMLp-0000dv-FN
	for ietf@ietf.org; Mon, 09 Aug 2004 22:26:58 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 1BuHaL-0003UC-00; Mon, 09 Aug 2004 17:21:37 -0400
Date: Mon, 9 Aug 2004 17:21:34 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: George Michaelson <ggm@apnic.net>
In-Reply-To: <20040810120713.36935166@garlic.apnic.net>
Message-ID: <Pine.LNX.4.44.0408091720150.13395-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 1.9 (+)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: grenville armitage <garmitage@swin.edu.au>, ietf@ietf.org,
        sommerfeld@orchard.arlington.ma.us,
        "Steven M. Bellovin" <smb@research.att.com>
Subject: Re: YATS? Re: T-shirts,
	and some suggestions for future 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-Score: 1.9 (+)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d

On Tue, 10 Aug 2004, George Michaelson wrote:

Personally, I find the requirement of wearing clothes tiresome, but then
again, who REALLY wants to see all the IETF'ers naked?

Enjoy,
Scott


>
> Jon Crowcroft told us in UCL-CS back in '85 that the pre-IETF meetings were
> smoke filled rooms, including uniforms with medal-bars out to the elbows...
>
> -George
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>

sleekfreak pirate broadcast
http://sleekfreak.ath.cx:81/


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


From ietf-bounces@ietf.org  Tue Aug 10 00:54:21 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA01716;
	Tue, 10 Aug 2004 00:54:21 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BuOiz-0003ah-HW; Tue, 10 Aug 2004 00:59:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BuOaz-0007d5-Fi; Tue, 10 Aug 2004 00:50:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BuOZh-0007HV-Jj
	for ietf@megatron.ietf.org; Tue, 10 Aug 2004 00:49:25 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA01361
	for <ietf@ietf.org>; Tue, 10 Aug 2004 00:49:22 -0400 (EDT)
Received: from web50708.mail.yahoo.com ([206.190.38.106])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1BuOe9-0003Uu-QO
	for ietf@ietf.org; Tue, 10 Aug 2004 00:54:03 -0400
Message-ID: <20040810044853.79275.qmail@web50708.mail.yahoo.com>
Received: from [61.11.60.240] by web50708.mail.yahoo.com via HTTP;
	Mon, 09 Aug 2004 21:48:53 PDT
Date: Mon, 9 Aug 2004 21:48:53 -0700 (PDT)
From: Rajat <myself_rajat@yahoo.com>
To: ietf@ietf.org
In-Reply-To: <200406160434.i5G4YjCS069427@cougar.icir.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Subject: Regarding IP address allocation
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-Score: 0.2 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a

Dear All,

Actually I am intrested in finding the region of given
IP address.

For This I need to determine the IP ranges allotted to
country as well as the domain extensions (say .co.in
for India).

Can anybody tell me, from where I can get this
information about IP address ranges and domain
extenstion.

Waiting for some +ve responses.


	
		
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail 

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


From ietf-bounces@ietf.org  Tue Aug 10 04:56:03 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04269;
	Tue, 10 Aug 2004 04:56:03 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BuSUs-0007uJ-LC; Tue, 10 Aug 2004 05:00:45 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BuSM8-0008PV-VI; Tue, 10 Aug 2004 04:51:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BuSIg-0007eJ-Ly
	for ietf@megatron.ietf.org; Tue, 10 Aug 2004 04:48:06 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03769
	for <ietf@ietf.org>; Tue, 10 Aug 2004 04:48:04 -0400 (EDT)
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BuSNB-0007l3-71
	for ietf@ietf.org; Tue, 10 Aug 2004 04:52:46 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id BC4E761BDB; Tue, 10 Aug 2004 10:47: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 12781-02; Tue, 10 Aug 2004 10:47:32 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain
	[127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP
	id CB58061B8D; Tue, 10 Aug 2004 10:47:31 +0200 (CEST)
Date: Tue, 10 Aug 2004 10:04:57 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Rajat <myself_rajat@yahoo.com>, ietf@ietf.org
Message-ID: <BC8CDA25A3088774C1262E2A@B50854F0A9192E8EC6CDA126>
In-Reply-To: <20040810044853.79275.qmail@web50708.mail.yahoo.com>
References: <20040810044853.79275.qmail@web50708.mail.yahoo.com>
X-Mailer: Mulberry/3.1.5 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 7bit
Subject: Re: Regarding IP address allocation
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-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: 7bit

try the Perl package "Net::Country" (if installing it works for you).

--On 9. august 2004 21:48 -0700 Rajat <myself_rajat@yahoo.com> wrote:

> Dear All,
>
> Actually I am intrested in finding the region of given
> IP address.
>
> For This I need to determine the IP ranges allotted to
> country as well as the domain extensions (say .co.in
> for India).
>
> Can anybody tell me, from where I can get this
> information about IP address ranges and domain
> extenstion.
>
> Waiting for some +ve responses.





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


From ietf-bounces@ietf.org  Tue Aug 10 08:12:37 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19320;
	Tue, 10 Aug 2004 08:12:37 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BuVZA-0003CS-85; Tue, 10 Aug 2004 08:17:20 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BuVOq-00025S-8e; Tue, 10 Aug 2004 08:06:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BuUfD-0000wK-7C; Tue, 10 Aug 2004 07:19:31 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14535;
	Tue, 10 Aug 2004 07:19:29 -0400 (EDT)
Received: from chiark.greenend.org.uk ([193.201.200.170] ident=mail)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BuUjj-0001uA-1B; Tue, 10 Aug 2004 07:24:12 -0400
Received: by chiark.greenend.org.uk (Debian Exim 3.35 #1) with local
	id 1BuUf4-0000Xr-00; Tue, 10 Aug 2004 12:19:22 +0100
From: Ian Jackson <ijackson@chiark.greenend.org.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16664.44858.761574.980321@chiark.greenend.org.uk>
Date: Tue, 10 Aug 2004 12:19:22 +0100
To: iesg@ietf.org, ietf@ietf.org
Newsgroups: chiark.mail.ietf.announce
In-Reply-To: <E1BuCka-00016P-6d@megatron.ietf.org>
References: <E1BuCka-00016P-6d@megatron.ietf.org>
X-Mailer: VM 7.03 under Emacs 19.34.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 10 Aug 2004 08:06:38 -0400
Subject: Re: Last Call: 'The APPLICATION/MBOX Media-Type' to Proposed
	Standard 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Content-Transfer-Encoding: 7bit

The IESG writes ("Last Call: 'The APPLICATION/MBOX Media-Type' to Proposed Standard "):
> The IESG has received a request from an individual submitter to consider the 
> following document:
> 
> - 'The APPLICATION/MBOX Media-Type '
>    <draft-hall-mime-app-mbox-02.txt> as a Proposed Standard
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action.  Please send any comments to the
> iesg@ietf.org or ietf@ietf.org mailing lists by 2004-09-06.

I have the following comments:

 * This specification is incomplete.  There are unresolved issues
   regarding the semantics of the format.

 * Since mbox files are text files (assuming that any binary messages
   in the mailbox are themselves encoded) and can be read sensibly
   with the naked eye, the content type should be text/* not
   application/*.  This will also remove ambiguity surrounding line
   endings.

 * Since an mbox is actually an aggregate type - a way of encoding a
   set of RFC822 messages - transfer encodings other than 7bit and
   8bit should be discouraged.  The spec should probably deprecate
   them in most cases.

 * The Proposed Standard should either include or refer to a specific
   mbox format.  The fact that there are variant implementations
   doesn't mean that the Proposed Standard should hesitate to declare
   those broken (at least, broken when a file is sent as text/mbox).
   Those variant implementations are not wholly interoperable anyway,
   and in order to write software which deals correctly with text/mbox
   it will be necessary for the spec to say what the format is
   supposed to be !

 * The format specified should be that described in Rahu Dhesi's
   posting to comp.mail.misc in 1996, <4ivk9s$bok@hustle.rahul.net>.

 * If an mbox file contains messages with unencoded binary data, the
   file is difficult to sensibly process on a machine with non-UN*X
   line-endings, because of the bare CRs in the binary data.  (Bare
   LFs are fine and look just like line endings, with From_-escaping
   and all.)  As far as I can tell there is then no non-lossy
   representation of the file which allows sensible local processing
   by non-mbox-specific tools.  This issue should be resolved (or at
   least acknowledged).

Ian.

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


From ietf-bounces@ietf.org  Tue Aug 10 11:34:08 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04661;
	Tue, 10 Aug 2004 11:34:07 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BuYiD-0006m9-KV; Tue, 10 Aug 2004 11:38:53 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BuYTG-0001wu-Gh; Tue, 10 Aug 2004 11:23:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BuYLn-00015X-EM; Tue, 10 Aug 2004 11:15:43 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03551;
	Tue, 10 Aug 2004 11:15:40 -0400 (EDT)
Received: from goose.ehsco.com ([207.65.203.98])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BuYQK-0006WF-Mo; Tue, 10 Aug 2004 11:20:26 -0400
Received: from [192.168.0.5] (cable0-stm-219.gmpexpress.net [63.147.50.219])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client did not present a certificate)
	by goose.ehsco.com (Postfix ) with ESMTP id BCC3B13A3D;
	Tue, 10 Aug 2004 10:15:36 -0500 (CDT)
Message-ID: <4118E64D.7060307@ehsco.com>
Date: Tue, 10 Aug 2004 11:14:21 -0400
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7) Gecko/20040616
X-Accept-Language: en-us, en
MIME-Version: 1.0
Newsgroups: chiark.mail.ietf.announce
To: Ian Jackson <ijackson@chiark.greenend.org.uk>
References: <E1BuCka-00016P-6d@megatron.ietf.org>
	<16664.44858.761574.980321@chiark.greenend.org.uk>
In-Reply-To: <16664.44858.761574.980321@chiark.greenend.org.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: c54bc2f42d02429833c0ca4b8725abd7
Content-Transfer-Encoding: 7bit
Cc: iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: 'The APPLICATION/MBOX Media-Type' to
	Proposed	Standard
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 0770535483960d190d4a0d020e7060bd
Content-Transfer-Encoding: 7bit


Thanks for the comments.

If we start from the premise that messages in mbox files are RFC2822
objects, then your conclusions and arguments are appropriate and correct.
However, that premise is demonstrably false, and most of the conclusions
which follow that premise are also false.

Let's be clear about this: mbox files ARE NOT collections of 2822 objects,
but instead are app-specific databases of app-specific message objects. As
such, the right way to handle them is to treat them as opaque databases,
just as if they ~Eudora databases, or ~Outlook databases, or anything
else, and to treat them accordingly.

As a simple example of this principle, mbox files often contain relative
email addresses with no domain qualifier (especially common with users who
exchange messages with other local users, but this isn't limited to that
context). OTOH, section 3.4.1 of RFC2822 unambiguously states that email
addresses (those that use addr-spec) must be qualified. So, starting with
this message from the E2E-Interest archives:

ftp://ftp.isi.edu/end2end/end2end-interest-1985-1987.mail

| Date: Wed, 3 Jun 87 13:18:28 PDT
| From: Bob Braden <braden>
| Message-Id: <8706032018.AA02832@braden.isi.edu>
| To: end2end-interest
| Cc: postel

What should an import agent do when it finds that, and wants to import it
into an ~IMAP folder, or wants to ~remail the message? should it append
the local domain name? should it append a default domain name? should it
reject the message because it ~doesn't conform to 2822 and because no
assumptions are safe? Clearly, the message is not conformant to 2822, and
the data has to be analyzed in the context of the application which
created it, rather than the application-neutral format that we all wish
was being used. From that position, out-of-band negotiation over the
formatting of the database is the only thing that will work.

Addresses are a minor example, and one that a lot of folks would gladly
brush off as irrelevant, but there are a lot more examples, some of which
are much more significant. Since the messages are not 2822 compliant
objects, there is no gurantee (or even any reasonable assumption) that
binary objects have been previously encoded into a safe format. Messages
can easily contain untagged 8-bit characters, bare CR and/or LF, and can
be thousand characters in length, all of which violates other assumptions
about 2822 formatting. 998-character line-lengths would destroy the data.
Automatic EOL conversion (as implied by text/* media-type definitions)
would destroy the data. And so forth.

What if two local users are exchanging big5-encoded messages, but neither
mailer has tagged the messages with the appropriate MIME tags (not
uncommon, and not a requirement, since these are not 2822 compliant, nor
even MIME-compliant). What assumptions should an importer make? The only
safe thing here is out-of-band negotiation ("these are big5").

It would be nice if mbox files only contained 2822 objects. But they
don't. They don't even have to conform to any one set of assumptions, and
can contain messages in different charsets (all of which are untagged), or
which have different relative domains (all of which are unspecified), or
any number of other variances. As such, they have to be treated as opaque
databases, not as collections of well-formed 2822 objects.

I also note that the digest media-type is already specified and is the
appropritate interchange format if you actually do have a collection of
well-formed 2822 objects. But if you have an mbox file, you have to
exchange it as an opaque database, and you have to delineate any internal
assumptions through out-of-band negotiations. The mbox media-type is for
use with tagging and identifying the data being exchanged ("here is an
opaque database of unspecified message objects") only.

Detailed responses to points follow:

On 8/10/2004 7:19 AM, Ian Jackson wrote:

> The IESG writes ("Last Call: 'The APPLICATION/MBOX Media-Type' to Proposed Standard "):
> 
>>The IESG has received a request from an individual submitter to consider the 
>>following document:
>>
>>- 'The APPLICATION/MBOX Media-Type '
>>   <draft-hall-mime-app-mbox-02.txt> as a Proposed Standard
>>
>>The IESG plans to make a decision in the next few weeks, and solicits
>>final comments on this action.  Please send any comments to the
>>iesg@ietf.org or ietf@ietf.org mailing lists by 2004-09-06.
> 
> I have the following comments:
> 
>  * This specification is incomplete.  There are unresolved issues
>    regarding the semantics of the format.

This is not intended to serve as an authoritative reference to the mbox
database format, but is only intended to provide an identifier for the
database-type when it is transferred. Out-of-band negotiation is necessary
in all cases anyway, and I don't really think it's appropriate for the
IETF to define an application-specific database format anyway.

I'd like to see one, and I'd like to see whatever *NIX consortium is
responsible for such things get together and define one.

>  * Since mbox files are text files (assuming that any binary messages
>    in the mailbox are themselves encoded) and can be read sensibly
>    with the naked eye, the content type should be text/* not
>    application/*.  This will also remove ambiguity surrounding line
>    endings.

Automatic EOL conversion destroys message objects. There is no assumption
that messages are conformant with 2822, nor can there be any such assumption.

>  * Since an mbox is actually an aggregate type - a way of encoding a
>    set of RFC822 messages - transfer encodings other than 7bit and
>    8bit should be discouraged.  The spec should probably deprecate
>    them in most cases.

I don't see why. It may be efficient to append an app/mbox database to a
[2822-compliant] email message, and to encode is as QP, or it may be
necessary to encode it as base64 if it contains long lines of raw 8bit data.

>  * The Proposed Standard should either include or refer to a specific
>    mbox format.  The fact that there are variant implementations
>    doesn't mean that the Proposed Standard should hesitate to declare
>    those broken (at least, broken when a file is sent as text/mbox).
>    Those variant implementations are not wholly interoperable anyway,
>    and in order to write software which deals correctly with text/mbox
>    it will be necessary for the spec to say what the format is
>    supposed to be !

Well, this would require that every local application be changed to suit
the needs of the transfer format, which is not reasonable. Instead the
goal here is to define a transfer identifier which says that the data
probably looks like XYZ.

>  * The format specified should be that described in Rahu Dhesi's
>    posting to comp.mail.misc in 1996, <4ivk9s$bok@hustle.rahul.net>.

The message with that message-ID does not define a format.

>  * If an mbox file contains messages with unencoded binary data, the
>    file is difficult to sensibly process on a machine with non-UN*X
>    line-endings, because of the bare CRs in the binary data.  (Bare
>    LFs are fine and look just like line endings, with From_-escaping
>    and all.)  As far as I can tell there is then no non-lossy
>    representation of the file which allows sensible local processing
>    by non-mbox-specific tools.  This issue should be resolved (or at
>    least acknowledged).


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

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


From ietf-bounces@ietf.org  Tue Aug 10 12:55:33 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11932;
	Tue, 10 Aug 2004 12:55:33 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BuZz1-0000Br-OO; Tue, 10 Aug 2004 13:00:20 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BuZs6-0006kX-84; Tue, 10 Aug 2004 12:53:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BuZeU-0003fp-SI
	for ietf@megatron.ietf.org; Tue, 10 Aug 2004 12:39:09 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10435
	for <ietf@ietf.org>; Tue, 10 Aug 2004 12:39:03 -0400 (EDT)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BuZj3-0008J1-8R
	for ietf@ietf.org; Tue, 10 Aug 2004 12:43:50 -0400
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-3.cisco.com with ESMTP; 10 Aug 2004 09:42:15 +0000
X-BrightmailFiltered: true
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 i7AGcQu7026958;
	Tue, 10 Aug 2004 09:38:26 -0700 (PDT)
Received: from gwzw2k (sjc-vpn5-655.cisco.com [10.21.90.143]) by
	franklin.cisco.com (8.8.6 (PHNE_17190)/CISCO.SERVER.1.2) with
	ESMTP id JAA11470; Tue, 10 Aug 2004 09:38:25 -0700 (PDT)
From: "Glen Zorn" <gwz@cisco.com>
To: "'Michael Richardson'" <mcr@sandelman.ottawa.on.ca>,
        "'JORDI PALET MARTINEZ'" <jordi.palet@consulintel.es>
Date: Tue, 10 Aug 2004 09:37:52 -0700
Organization: Cisco Systems
Message-ID: <00ac01c47ef8$73aa0d10$0202a8c0@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
In-Reply-To: <7255.1091807360@marajade.sandelman.ottawa.on.ca>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: RE: T-shirts, and some suggestions for future ietf meetings 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: gwz@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: 7bit

,,,

>   Frankly, as long as we can have BAR BOFs in the Hotel, the location
> of the food doesn't matter. 
> 
>   Vienna suffered from having meeting space and hotel seperated, and
> unclear default "BAR".  Orlando had the same problem. 

Hmm.  As I recall, the meeting space was in the hotel in Orlando.
Perhaps you are thinking of Montreal (though it's hard to believe that
one could confuse the two ;-)?

> I've never done
> the San Diego hotel, but I know exactly where it is. Definitely not
> downtown.   

A $5 cab ride to the Gaslamp district.  Why would you want to go to
downtown S.D.?

...

~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-bounces@ietf.org  Tue Aug 10 13:19:22 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14028;
	Tue, 10 Aug 2004 13:19:21 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BuaM3-0000l1-6M; Tue, 10 Aug 2004 13:24:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BuaAX-0002WY-T4; Tue, 10 Aug 2004 13:12:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BuZtH-00073h-0U; Tue, 10 Aug 2004 12:54:23 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11859;
	Tue, 10 Aug 2004 12:54:19 -0400 (EDT)
Received: from brmea-mail-3.sun.com ([192.18.98.34])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BuZxf-0000A6-GN; Tue, 10 Aug 2004 12:59:07 -0400
Received: from esunmail ([129.147.156.34])
	by brmea-mail-3.sun.com (8.12.10/8.12.9) with ESMTP id i7AGs9il016630; 
	Tue, 10 Aug 2004 10:54:09 -0600 (MDT)
Received: from fe7 (esunmail [129.147.156.34]) by edgemail1.Central.Sun.COM
	(iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep  8 2003))
	with ESMTP id <0I2800GI7PM8QB@edgemail1.Central.Sun.COM>; Tue,
	10 Aug 2004 10:54:08 -0600 (MDT)
Received: from [192.168.1.101] ([24.72.92.157])
	by mail.sun.net (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep 8
	2003)) with ESMTPSA id <0I2800KYIPM13N@mail.sun.net>; Tue,
	10 Aug 2004 10:54:08 -0600 (MDT)
Date: Tue, 10 Aug 2004 09:53:58 -0700
From: Tim Bray <tbray@textuality.com>
In-reply-to: <16664.44858.761574.980321@chiark.greenend.org.uk>
To: Ian Jackson <ijackson@chiark.greenend.org.uk>
Message-id: <DF87C766-EAED-11D8-BC85-000A95A51C9E@textuality.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.618)
References: <E1BuCka-00016P-6d@megatron.ietf.org>
	<16664.44858.761574.980321@chiark.greenend.org.uk>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Cc: ietf@ietf.org, iesg@ietf.org
Subject: Re: Last Call: 'The APPLICATION/MBOX Media-Type' to Proposed
	Standard
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0741733451=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b


--===============0741733451==
Content-type: multipart/signed; micalg=sha1; boundary=Apple-Mail-5-33005289;
	protocol="application/pkcs7-signature"


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

On Aug 10, 2004, at 4:19 AM, Ian Jackson wrote:

> The IESG writes ("Last Call: 'The APPLICATION/MBOX Media-Type' to 
> Proposed Standard "):
>  * Since mbox files are text files (assuming that any binary messages
>    in the mailbox are themselves encoded) and can be read sensibly
>    with the naked eye, the content type should be text/* not
>    application/*.  This will also remove ambiguity surrounding line
>    endings.

I'm not very close to this problem, but I'd like to point out that 
using text/anything gets you into i18n issues... if the server has 
trouble getting the charset= right and doesn't provide it, then the 
rules say the client MUST assume US-ASCII, which in a high proportion 
of cases is going to be wrong; and by the way the client is forbidden 
to use any other heuristics to figure out what the encoding might be.  
text/* also blesses intermediate transcoders which can create all sorts 
of problems.

Maybe these issues don't apply to mbox data, in which case feel free to 
ignore me -Tim

--Apple-Mail-5-33005289
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Disposition: attachment;
	filename=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGHDCCAtUw
ggI+oAMCAQICAwuKuTANBgkqhkiG9w0BAQQFADBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhh
d3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt
YWlsIElzc3VpbmcgQ0EwHhcNMDQwMTIyMjMzOTA2WhcNMDUwMTIxMjMzOTA2WjBGMR8wHQYDVQQD
ExZUaGF3dGUgRnJlZW1haWwgTWVtYmVyMSMwIQYJKoZIhvcNAQkBFhR0YnJheUB0ZXh0dWFsaXR5
LmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMYiIlrf7yTblabXBlwkonodVyp+
W7Oo8w71ErSW7mKramEBAkfkUnPmbRqcS2wqFaK34GbQMk/1vcOxo2AmfmFVec13SWKi0YzXC8xf
9SbjfQU1tXiC9LJB1HeOO46UVRqTNeayruz2pQBztvYF76G5sGmwKjoR/DhimwUM579MaJln38SK
UQ6Ya768DwyaDNY7yDWYh1gUxizx71QkzyRCPQdmq6g1ebrVYyoBE33BXQRNGZm2zrlI5JBQ4oax
E0Cz3BjR8iZFzK/AhFGDllZYuojf7iZuaNhWr3aWAvHNyLHVMaxXNFb/CUri5c7StFVEgXUVvlgP
eSHIPg9gqaECAwEAAaMxMC8wHwYDVR0RBBgwFoEUdGJyYXlAdGV4dHVhbGl0eS5jb20wDAYDVR0T
AQH/BAIwADANBgkqhkiG9w0BAQQFAAOBgQBQAlJ/qQJmtQN966ahSWiovhjWj5Qwk6BnPP+Fjfbo
9guSIWWBw2DEXh8nPT4WJchZSVz4SwDtZ0SZ2PWWToRo/Dmpv+ehzNNhR/y2CdU/zNo+kSShBhc6
HNtp6A0+Yh6Vw0Y+qHa0EKppOJM2D5WTExycYjHU8Xs+dLktAmKqlzCCAz8wggKooAMCAQICAQ0w
DQYJKoZIhvcNAQEFBQAwgdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQ
BgNVBAcTCUNhcGUgVG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0Nl
cnRpZmljYXRpb24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBG
cmVlbWFpbCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAe
Fw0wMzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU
aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJl
ZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065ypla
HmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FWy688
Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEEQB5kGXJg
t/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2oDSGMmh0dHA6
Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3JsMAsGA1UdDwQEAwIB
BjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxhYmVsMi0xMzgwDQYJKoZIhvcNAQEF
BQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFi
w9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amcOY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU13
41YheILcIRk13iSx0x1G/11fZU8xggLnMIIC4wIBATBpMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQK
ExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg
RnJlZW1haWwgSXNzdWluZyBDQQIDC4q5MAkGBSsOAwIaBQCgggFTMBgGCSqGSIb3DQEJAzELBgkq
hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTA0MDgxMDE2NTM1OFowIwYJKoZIhvcNAQkEMRYEFGql
SLZY3hlsHbgPzKYnAaGsUVynMHgGCSsGAQQBgjcQBDFrMGkwYjELMAkGA1UEBhMCWkExJTAjBgNV
BAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h
bCBGcmVlbWFpbCBJc3N1aW5nIENBAgMLirkwegYLKoZIhvcNAQkQAgsxa6BpMGIxCzAJBgNVBAYT
AlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3
dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIDC4q5MA0GCSqGSIb3DQEBAQUABIIBAErX
fICqSQ3cBWTjbYfBak4a8MmuKgCDcW2FlOJQs/SPNwgWuAL9KkHeS+JV/kBVUOG2RVzJ8G7W0nyR
kjDNG7vdj/5SEfuB/+Y0rO6jb6wD1QeoEDzDL3BMyn/W58bvZkHLEGVNO43wUmKoHow3CyH8ERh7
Df1xhOAyFhNk03ltL/nmj5hjSxkAQcIcDG2+s/5BSLKc6VScQJC7SUXfHTF+1EbtmiFDNQl6Ebys
nLTcpZDjSobQV5I/oF3Aof7AkwkUlps0p3uB9CFlkHlv7FD+AN4HNHLmETreUOTn4CNvEGdLE8ah
0HqdFdXOZDh2tyuXR7osAFylLMg6auFABRsAAAAAAAA=

--Apple-Mail-5-33005289--



--===============0741733451==
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

--===============0741733451==--




From ietf-bounces@ietf.org  Tue Aug 10 13:33:47 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15605;
	Tue, 10 Aug 2004 13:33:47 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Buaa0-00019P-Fz; Tue, 10 Aug 2004 13:38:33 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BuaFQ-00048h-Gm; Tue, 10 Aug 2004 13:17:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BuZyW-0008Ib-Ib
	for ietf@megatron.ietf.org; Tue, 10 Aug 2004 12:59:48 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12310
	for <ietf@ietf.org>; Tue, 10 Aug 2004 12:59:45 -0400 (EDT)
Received: from cyphermail.sandelman.ottawa.on.ca ([205.150.200.161]
	helo=noxmail.sandelman.ottawa.on.ca)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bua35-0000Gi-8z
	for ietf@ietf.org; Tue, 10 Aug 2004 13:04:32 -0400
Received: from sandelman.ottawa.on.ca (marajade.sandelman.ottawa.on.ca
	[205.150.200.247])
	by noxmail.sandelman.ottawa.on.ca (8.11.6p3/8.11.6) with ESMTP id
	i7AGvd824510
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified
	OK); Tue, 10 Aug 2004 12:57:39 -0400 (EDT)
Received: from sandelman.ottawa.on.ca (marajade [127.0.0.1])
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id
	i7AGvd4F025807
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 10 Aug 2004 12:57:39 -0400
Received: from marajade.sandelman.ottawa.on.ca (mcr@localhost)
	by sandelman.ottawa.on.ca (8.12.3/8.12.3/Debian-6.6) with ESMTP id
	i7AGvcd3025804; Tue, 10 Aug 2004 12:57:38 -0400
To: gwz@cisco.com, ietf@ietf.org
In-Reply-To: Message from "Glen Zorn" <gwz@cisco.com> of "Tue,
	10 Aug 2004 09:37:52 PDT."
	<00ac01c47ef8$73aa0d10$0202a8c0@amer.cisco.com> 
References: <00ac01c47ef8$73aa0d10$0202a8c0@amer.cisco.com> 
X-Mailer: MH-E 7.4.2; nmh 1.0.4+dev; XEmacs 21.4 (patch 6)
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Tue, 10 Aug 2004 12:57:38 -0400
Message-ID: <25803.1092157058@marajade.sandelman.ottawa.on.ca>
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
X-Spam-Score: 2.3 (++)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Subject: Re: T-shirts, and some suggestions for future 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-Score: 2.3 (++)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69

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


>>>>> "Glen" == Glen Zorn <gwz@cisco.com> writes:
    >> Frankly, as long as we can have BAR BOFs in the Hotel, the location
    >> of the food doesn't matter. 
    >> 
    >> Vienna suffered from having meeting space and hotel seperated, and
    >> unclear default "BAR".  Orlando had the same problem. 

    Glen> Hmm.  As I recall, the meeting space was in the hotel in Orlando.
    Glen> Perhaps you are thinking of Montreal (though it's hard to believe that
    Glen> one could confuse the two ;-)?

  Montreal had that problem as well, and much more accute than Orlando.

  I recall Orlando had no convenient bar. 

    Glen> A $5 cab ride to the Gaslamp district.  Why would you want to go to
    Glen> downtown S.D.?

  That isn't the point. The point is that the hotel bar provides the
*defacto* point to have ad-hoc meetings. I.e. ones where two people just
bump into each other and start chatting.

- --
]     "Elmo went to the wrong fundraiser" - The Simpson         |  firewalls  [
]   Michael Richardson,    Xelerance Corporation, Ottawa, ON    |net architect[
] mcr@xelerance.com      http://www.sandelman.ottawa.on.ca/mcr/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Finger me for keys

iQCVAwUBQRj+eIqHRg3pndX9AQEG6AQA7Yd9K0VufnsR7r2Ip4ujE/IOw3ncuKRW
EW8xhb9VBCfXTDVis9xUFN2o0X5UEo/ZSv5xZfAtJ2jG5cGfuG09gWbc1SjLO1Qi
Amk/xuxZyKcAD7sIHFlSvgoF82gGg8C0pCOowNRGv/0BYWt9Z5kUHHqCvN6shkdm
G2sYbOBAyks=
=DDUH
-----END PGP SIGNATURE-----

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


From ietf-bounces@ietf.org  Tue Aug 10 13:52:41 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17102;
	Tue, 10 Aug 2004 13:52:41 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BuasI-0001ZU-O4; Tue, 10 Aug 2004 13:57:27 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BuadO-0001d9-Lf; Tue, 10 Aug 2004 13:42:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BuaSG-00077n-13
	for ietf@megatron.ietf.org; Tue, 10 Aug 2004 13:30:32 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15366
	for <ietf@ietf.org>; Tue, 10 Aug 2004 13:30:30 -0400 (EDT)
Received: from parsley.amaranth.net ([216.44.4.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BuaWp-00016d-2b
	for ietf@ietf.org; Tue, 10 Aug 2004 13:35:16 -0400
Received: from ancho.senie.com (h0006b1049b35.ne.client2.attbi.com
	[24.34.19.2]) (authenticated bits=0)
	by parsley.amaranth.net (8.12.8/8.12.8) with ESMTP id i7AHS6Hq025663
	(version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NO);
	Tue, 10 Aug 2004 13:28:11 -0400
Message-Id: <6.1.2.0.2.20040810132240.061b35f8@mail.amaranth.net>
X-Sender: dts@mail.amaranth.net
X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0
Date: Tue, 10 Aug 2004 13:26:31 -0400
To: gwz@cisco.com, "'Michael Richardson'" <mcr@sandelman.ottawa.on.ca>,
        "'JORDI PALET MARTINEZ'" <jordi.palet@consulintel.es>
From: Daniel Senie <dts@senie.com>
In-Reply-To: <00ac01c47ef8$73aa0d10$0202a8c0@amer.cisco.com>
References: <7255.1091807360@marajade.sandelman.ottawa.on.ca>
	<00ac01c47ef8$73aa0d10$0202a8c0@amer.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: ietf@ietf.org
Subject: RE: T-shirts, and some suggestions for future 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-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336

At 12:37 PM 8/10/2004, Glen Zorn wrote:
>,,,
>
> >   Frankly, as long as we can have BAR BOFs in the Hotel, the location
> > of the food doesn't matter.
> >
> >   Vienna suffered from having meeting space and hotel seperated, and
> > unclear default "BAR".  Orlando had the same problem.
>
>Hmm.  As I recall, the meeting space was in the hotel in Orlando.
>Perhaps you are thinking of Montreal (though it's hard to believe that
>one could confuse the two ;-)?

The hotel in orlando was garden-style with many low-rise buildings. The 
meeting rooms were near the bar, though not right next door.


> > I've never done
> > the San Diego hotel, but I know exactly where it is. Definitely not
> > downtown.
>
>A $5 cab ride to the Gaslamp district.  Why would you want to go to
>downtown S.D.?
>
>...
>
>~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


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


From ietf-bounces@ietf.org  Tue Aug 10 20:58:10 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20829;
	Tue, 10 Aug 2004 20:58:10 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BuhW8-0002mS-Gi; Tue, 10 Aug 2004 21:03:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BuhI8-0004TT-OY; Tue, 10 Aug 2004 20:48:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BuhG0-0003k7-Kj
	for ietf@megatron.ietf.org; Tue, 10 Aug 2004 20:46:22 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20399
	for <ietf@ietf.org>; Tue, 10 Aug 2004 20:46:18 -0400 (EDT)
Received: from user-0c6s17c.cable.mindspring.com ([24.110.4.236]
	helo=sleekfreak.ath.cx) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BuhKd-0002cE-OE
	for ietf@ietf.org; Tue, 10 Aug 2004 20:51:09 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 1BucYD-0004b3-00; Tue, 10 Aug 2004 15:44:49 -0400
Date: Tue, 10 Aug 2004 15:44:38 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: Daniel Senie <dts@senie.com>
In-Reply-To: <6.1.2.0.2.20040810132240.061b35f8@mail.amaranth.net>
Message-ID: <Pine.LNX.4.44.0408101544100.17672-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 1.9 (+)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Cc: "'Michael Richardson'" <mcr@sandelman.ottawa.on.ca>, gwz@cisco.com,
        "'JORDI PALET MARTINEZ'" <jordi.palet@consulintel.es>, ietf@ietf.org
Subject: RE: T-shirts, and some suggestions for future 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-Score: 1.9 (+)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15

We have very nice facilities in Daytona.


On Tue, 10 Aug 2004, Daniel Senie wrote:

> At 12:37 PM 8/10/2004, Glen Zorn wrote:
> >,,,
> >
> > >   Frankly, as long as we can have BAR BOFs in the Hotel, the location
> > > of the food doesn't matter.
> > >
> > >   Vienna suffered from having meeting space and hotel seperated, and
> > > unclear default "BAR".  Orlando had the same problem.
> >
> >Hmm.  As I recall, the meeting space was in the hotel in Orlando.
> >Perhaps you are thinking of Montreal (though it's hard to believe that
> >one could confuse the two ;-)?
>
> The hotel in orlando was garden-style with many low-rise buildings. The
> meeting rooms were near the bar, though not right next door.
>
>
> > > I've never done
> > > the San Diego hotel, but I know exactly where it is. Definitely not
> > > downtown.
> >
> >A $5 cab ride to the Gaslamp district.  Why would you want to go to
> >downtown S.D.?
> >
> >...
> >
> >~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
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>

sleekfreak pirate broadcast
http://sleekfreak.ath.cx:81/


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


From ietf-bounces@ietf.org  Tue Aug 10 23:06:11 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA27712;
	Tue, 10 Aug 2004 23:06:11 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BujW2-0004sU-BK; Tue, 10 Aug 2004 23:11:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BujMu-0002r4-Bq; Tue, 10 Aug 2004 23:01:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BujLG-0002ak-Sp; Tue, 10 Aug 2004 22:59:55 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27411;
	Tue, 10 Aug 2004 22:59:51 -0400 (EDT)
Received: from tls.sendmail.com ([209.246.26.40] helo=foon.sendmail.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BujPu-0004mx-Uw; Tue, 10 Aug 2004 23:04:44 -0400
Received: from lab.smi.sendmail.com ([10.210.100.93])
	by foon.sendmail.com (Switch-3.1.6/Switch-3.1.6) with ESMTP id
	i7B2xMji031869
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK);
	Tue, 10 Aug 2004 19:59:22 -0700
Received: from lab.smi.sendmail.com (localhost [127.0.0.1])
	by lab.smi.sendmail.com (8.12.11/8.12.11) with ESMTP id i7B2xLOV043227; 
	Tue, 10 Aug 2004 19:59:22 -0700 (PDT)
	(envelope-from guenther@lab.smi.sendmail.com)
Message-Id: <200408110259.i7B2xLOV043227@lab.smi.sendmail.com>
To: "Eric A. Hall" <ehall@ehsco.com>
From: Philip Guenther <guenther+ietfd@sendmail.com>
In-reply-to: <4118E64D.7060307@ehsco.com> 
References: <E1BuCka-00016P-6d@megatron.ietf.org>
	<16664.44858.761574.980321@chiark.greenend.org.uk> 
	<4118E64D.7060307@ehsco.com> 
Date: Tue, 10 Aug 2004 19:59:21 -0700
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: ietf@ietf.org, Ian Jackson <ijackson@chiark.greenend.org.uk>,
        iesg@ietf.org
Subject: Re: Last Call: 'The APPLICATION/MBOX Media-Type' to Proposed
	Standard 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352

Eric A. Hall <ehall@ehsco.com> writes:
...
>I also note that the digest media-type is already specified and is the
>appropritate interchange format if you actually do have a collection of
>well-formed 2822 objects. But if you have an mbox file, you have to
>exchange it as an opaque database, and you have to delineate any internal
>assumptions through out-of-band negotiations. The mbox media-type is for
>use with tagging and identifying the data being exchanged ("here is an
>opaque database of unspecified message objects") only.
...
>This is not intended to serve as an authoritative reference to the mbox
>database format, but is only intended to provide an identifier for the
>database-type when it is transferred. Out-of-band negotiation is necessary
>in all cases anyway, and I don't really think it's appropriate for the
>IETF to define an application-specific database format anyway.


If there are no defined semantics for the content of an application/mbox
part, how does the type differ from application/octect-stream?  In both
cases you have to look to out-of-band info to interpret the data.
Indeed, there appear to be no requirements at all on the content.  If
successful uses of this content-type effectively requires private
arrangement, why does it need a standard content-type instead of each
such exchange using a content-type tailored to the circumstance and
taken from the "vnd.", "prs.", or "x." trees.  How does use of
application/mbox over application/octet-stream or some other
content-type improve interoperability?

...
[regarding creating a spec for a mailbox file format]
>I'd like to see one, and I'd like to see whatever *NIX consortium is
>responsible for such things get together and define one.

At that point, would application/mbox be updated to refer to said spec,
rendering non-compliant some chunk of the previous uses, or would a new
content-type be specified?


Philip Guenther

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


From ietf-bounces@ietf.org  Wed Aug 11 07:43:06 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22641;
	Wed, 11 Aug 2004 07:43:06 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BuraK-0004DU-9e; Wed, 11 Aug 2004 07:48:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BurQq-0007MP-LG; Wed, 11 Aug 2004 07:38:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BuYH8-0000Fn-Q6
	for ietf@megatron.ietf.org; Tue, 10 Aug 2004 11:10:54 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03222
	for <ietf@ietf.org>; Tue, 10 Aug 2004 11:10:52 -0400 (EDT)
Received: from stl-smtpout-01.boeing.com ([130.76.96.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BuYLg-0006Q2-NR
	for ietf@ietf.org; Tue, 10 Aug 2004 11:15:38 -0400
Received: from blv-av-01.boeing.com ([192.42.227.216])
	by stl-smtpout-01.boeing.com (8.9.2.MG.10092003/8.8.5-M2) with ESMTP id
	KAA13473 for <ietf@ietf.org>; Tue, 10 Aug 2004 10:10:22 -0500 (CDT)
Received: from xch-nw-23p.nw.nos.boeing.com (localhost [127.0.0.1])
	by blv-av-01.boeing.com (8.11.3/8.11.3/MBS-LDAP-01) with ESMTP id
	i7AFAL401498
	for <ietf@ietf.org>; Tue, 10 Aug 2004 08:10:21 -0700 (PDT)
Received: from XCH-NW-09.nw.nos.boeing.com ([192.42.226.84]) by
	xch-nw-23p.nw.nos.boeing.com with Microsoft SMTPSVC(5.0.2195.6713); 
	Tue, 10 Aug 2004 08:09:50 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 10 Aug 2004 08:09:50 -0700
Message-ID: <5B58696DB20B9140AD20E0685C573A6404FDD6BB@xch-nw-09.nw.nos.boeing.com>
Thread-Topic: Regarding IP address allocation
Thread-Index: AcR+uA1FUduIHpF+Ra6Pu9dEmJVKvQAM1cyQ
From: "Fleischman, Eric" <eric.fleischman@boeing.com>
To: <ietf@ietf.org>
X-OriginalArrivalTime: 10 Aug 2004 15:09:50.0755 (UTC)
	FILETIME=[1546A730:01C47EEC]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Wed, 11 Aug 2004 07:38:10 -0400
Subject: Question about use of RSVP in Production Networks
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-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Content-Transfer-Encoding: quoted-printable

I am aware of some use of RSVP in labs but I am not aware of any use of =
RSVP in production networks (i.e., real life networks people connect to =
the Internet with). Simultaneously, I am encountering I-Ds and other =
work planning to use RSVP. This possible disconnect concerns me. =
Therefore, I would appreciate being educated by anybody using RSVP in =
production settings. Would you please let me know how many devices, what =
applications, and how successful these deployments (if any) are? Thank =
you.


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


From ietf-bounces@ietf.org  Wed Aug 11 08:14:01 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26412;
	Wed, 11 Aug 2004 08:14:01 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bus4G-00056z-2k; Wed, 11 Aug 2004 08:18:57 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BurtR-0000pj-N4; Wed, 11 Aug 2004 08:07:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Burl2-0002uN-O4
	for ietf@megatron.ietf.org; Wed, 11 Aug 2004 07:59:04 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA24373
	for <ietf@ietf.org>; Wed, 11 Aug 2004 07:59:03 -0400 (EDT)
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Burpl-0004iV-BP
	for ietf@ietf.org; Wed, 11 Aug 2004 08:03:58 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i7BBwTB24339
	for <ietf@ietf.org>; Wed, 11 Aug 2004 14:58:29 +0300
Date: Wed, 11 Aug 2004 14:58:29 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: ietf@ietf.org
In-Reply-To: <5B58696DB20B9140AD20E0685C573A6404FDD6BB@xch-nw-09.nw.nos.boeing.com>
Message-ID: <Pine.LNX.4.44.0408111448190.24098-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Subject: hop-by-hop and router alert options [Re: Question about use of RSVP
 in Production Networks]
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-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4

On Tue, 10 Aug 2004, Fleischman, Eric wrote:
> I am aware of some use of RSVP in labs but I am not aware of any use
> of RSVP in production networks (i.e., real life networks people
> connect to the Internet with). Simultaneously, I am encountering
> I-Ds and other work planning to use RSVP. This possible disconnect
> concerns me. Therefore, I would appreciate being educated by anybody
> using RSVP in production settings. Would you please let me know how
> many devices, what applications, and how successful these
> deployments (if any) are? Thank you.

I'd be interested about this as well, but also in more general.

I'd be in favor of deprecating the IP router alert option completely.  
Effectively this affects RSVP and MLD *).  I'd want to similarly do
away with the IPv6 Hop-by-Hop options.  At the very least, I'd like to
prevent further standardization of these options.

The justification is simple: any "magic" packets which all routers on
the path must somehow examine and process seems a very dubious concept
when we want to avoid DoS attacks etc. on the core equipment which
must run on hardware: effectively this means that either these are
ignored in any case (nullifying the use of such options), or put on a
"slow path" (causing a potential for DoS).  IMHO, it seems just simply
bad protocol design to require such behaviour.

I'm interested what others think about this.. :)

*) MLD should be relatively straight-forward to re-design (just send
the MLD reports to a link-local address which the router is
listening), or just keep it as is for now.  RSVP can probably thrown
away without many tears.

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


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


From ietf-bounces@ietf.org  Wed Aug 11 08:47:04 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00384;
	Wed, 11 Aug 2004 08:47:04 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BusaH-0006hV-1T; Wed, 11 Aug 2004 08:52:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BusP5-00081F-Qj; Wed, 11 Aug 2004 08:40:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BusLV-0007Fy-FJ
	for ietf@megatron.ietf.org; Wed, 11 Aug 2004 08:36:45 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29624
	for <ietf@ietf.org>; Wed, 11 Aug 2004 08:36:43 -0400 (EDT)
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1BusDM-0005lQ-Th
	for ietf@ietf.org; Wed, 11 Aug 2004 08:28:22 -0400
Received: (qmail 23571 invoked from network); 11 Aug 2004 12:21:06 -0000
Received: from yahoobb219178198081.bbtec.net (HELO necom830.hpcl.titech.ac.jp)
	(219.178.198.81)
	by necom830.hpcl.titech.ac.jp with SMTP; 11 Aug 2004 12:21:06 -0000
Message-ID: <411A0FA4.7040706@necom830.hpcl.titech.ac.jp>
Date: Wed, 11 Aug 2004 21:23:00 +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: Pekka Savola <pekkas@netcore.fi>
References: <Pine.LNX.4.44.0408111448190.24098-100000@netcore.fi>
In-Reply-To: <Pine.LNX.4.44.0408111448190.24098-100000@netcore.fi>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: hop-by-hop and router alert options [Re: Question about use of
 RSVP in Production Networks]
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-Score: 0.1 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7bit

Pekka Savola wrote:

> I'd be in favor of deprecating the IP router alert option completely.  
> Effectively this affects RSVP and MLD *).  I'd want to similarly do
> away with the IPv6 Hop-by-Hop options.  At the very least, I'd like to
> prevent further standardization of these options.

Multicast packets to RVP/Core are even more harmful.

							Masataka Ohta


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


From ietf-bounces@ietf.org  Wed Aug 11 09:01:41 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01431;
	Wed, 11 Aug 2004 09:01:41 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BusoP-0006zH-Fg; Wed, 11 Aug 2004 09:06:37 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Busgo-00031G-5c; Wed, 11 Aug 2004 08:58:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BusZS-0001dg-0v
	for ietf@megatron.ietf.org; Wed, 11 Aug 2004 08:51:10 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00895
	for <ietf@ietf.org>; Wed, 11 Aug 2004 08:51:08 -0400 (EDT)
Received: from goliath.siemens.de ([192.35.17.28])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BuseB-0006oH-Ec
	for ietf@ietf.org; Wed, 11 Aug 2004 08:56:04 -0400
Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14])
	by goliath.siemens.de (8.12.6/8.12.6) with ESMTP id i7BCp40T009185;
	Wed, 11 Aug 2004 14:51:04 +0200
Received: from mchp9daa.mch.sbs.de (mchp9daa.mch.sbs.de [139.25.137.99])
	by mail3.siemens.de (8.12.6/8.12.6) with ESMTP id i7BCogNW027337;
	Wed, 11 Aug 2004 14:50:52 +0200
Received: by mchp9daa.mch.sbs.de with Internet Mail Service (5.5.2657.72)
	id <P8C2SD7C>; Wed, 11 Aug 2004 14:50:42 +0200
Message-ID: <2A8DB02E3018D411901B009027FD3A3F046864BA@mchp905a.mch.sbs.de>
From: Tschofenig Hannes <hannes.tschofenig@siemens.com>
To: "'Pekka Savola'" <pekkas@netcore.fi>, ietf@ietf.org
Date: Wed, 11 Aug 2004 14:50:08 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Subject: RE: hop-by-hop and router alert options [Re: Question about use o
	f RSVP in Production Networks]
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-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17

hi pekka, 

if you want to discover nodes somewhere along the path (between a particular
source and a destination address) then you have a limited number of choices.
the router alert option is one option and certainly not better or worse than
other options. 

do you have a suggestion how to accomplish the same functionality (as
required by rsvp or similar protocols) in a better fashion?

ciao
hannes
 

> On Tue, 10 Aug 2004, Fleischman, Eric wrote:
> > I am aware of some use of RSVP in labs but I am not aware 
> of any use 
> > of RSVP in production networks (i.e., real life networks people 
> > connect to the Internet with). Simultaneously, I am 
> encountering I-Ds 
> > and other work planning to use RSVP. This possible 
> disconnect concerns 
> > me. Therefore, I would appreciate being educated by anybody 
> using RSVP 
> > in production settings. Would you please let me know how 
> many devices, 
> > what applications, and how successful these deployments (if 
> any) are? 
> > Thank you.
> 
> I'd be interested about this as well, but also in more general.
> 
> I'd be in favor of deprecating the IP router alert option 
> completely.  
> Effectively this affects RSVP and MLD *).  I'd want to 
> similarly do away with the IPv6 Hop-by-Hop options.  At the 
> very least, I'd like to prevent further standardization of 
> these options.
> 
> The justification is simple: any "magic" packets which all 
> routers on the path must somehow examine and process seems a 
> very dubious concept when we want to avoid DoS attacks etc. 
> on the core equipment which must run on hardware: effectively 
> this means that either these are ignored in any case 
> (nullifying the use of such options), or put on a "slow path" 
> (causing a potential for DoS).  IMHO, it seems just simply 
> bad protocol design to require such behaviour.
> 
> I'm interested what others think about this.. :)
> 
> *) MLD should be relatively straight-forward to re-design 
> (just send the MLD reports to a link-local address which the 
> router is listening), or just keep it as is for now.  RSVP 
> can probably thrown away without many tears.
> 
> -- 
> 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
> 

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


From ietf-bounces@ietf.org  Wed Aug 11 09:15:53 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02530;
	Wed, 11 Aug 2004 09:15:53 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1But27-0007J4-B2; Wed, 11 Aug 2004 09:20:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Busom-0004nt-5p; Wed, 11 Aug 2004 09:07:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BushQ-00037u-UK
	for ietf@megatron.ietf.org; Wed, 11 Aug 2004 08:59:25 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01329
	for <ietf@ietf.org>; Wed, 11 Aug 2004 08:59:23 -0400 (EDT)
Received: from kyoto.netlab.nec.de ([195.37.70.21])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BusmB-0006x6-In
	for ietf@ietf.org; Wed, 11 Aug 2004 09:04:20 -0400
Received: from [10.1.1.109] (marseille.netlab.nec.de [195.37.70.15])
	by kyoto.netlab.nec.de (Postfix) with ESMTP id 557531BAC4D;
	Wed, 11 Aug 2004 14:58:50 +0200 (CEST)
Date: Wed, 11 Aug 2004 14:58:51 +0200
From: Martin Stiemerling <stiemerling@netlab.nec.de>
To: Pekka Savola <pekkas@netcore.fi>, ietf@ietf.org
Message-ID: <C247C5A2924B780EE4DE8B5D@[10.1.1.109]>
In-Reply-To: <Pine.LNX.4.44.0408111448190.24098-100000@netcore.fi>
References: <Pine.LNX.4.44.0408111448190.24098-100000@netcore.fi>
X-Mailer: Mulberry/3.1.5 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Content-Transfer-Encoding: 7bit
Subject: Re: hop-by-hop and router alert options [Re: Question about use of
 RSVP in Production Networks]
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-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Content-Transfer-Encoding: 7bit



--On Mittwoch, 11. August 2004 14:58 Uhr +0300 Pekka Savola 
<pekkas@netcore.fi> wrote:

| On Tue, 10 Aug 2004, Fleischman, Eric wrote:
|> I am aware of some use of RSVP in labs but I am not aware of any use
|> of RSVP in production networks (i.e., real life networks people
|> connect to the Internet with). Simultaneously, I am encountering
|> I-Ds and other work planning to use RSVP. This possible disconnect
|> concerns me. Therefore, I would appreciate being educated by anybody
|> using RSVP in production settings. Would you please let me know how
|> many devices, what applications, and how successful these
|> deployments (if any) are? Thank you.
|
| I'd be interested about this as well, but also in more general.
|
| I'd be in favor of deprecating the IP router alert option completely.
| Effectively this affects RSVP and MLD *).  I'd want to similarly do
| away with the IPv6 Hop-by-Hop options.  At the very least, I'd like to
| prevent further standardization of these options.

Hmm, NSIS protocol suite (new protocol that does path-coupled QoS signaling 
ala RSVP and firewall/NAT signaling) relies on the use of router alert 
options for the initial NSIS peer discovery process.  Is there any other 
proposal to get a discovery mechanism like router alert options without the 
disadvantages of this option?

  Martin

|
| The justification is simple: any "magic" packets which all routers on
| the path must somehow examine and process seems a very dubious concept
| when we want to avoid DoS attacks etc. on the core equipment which
| must run on hardware: effectively this means that either these are
| ignored in any case (nullifying the use of such options), or put on a
| "slow path" (causing a potential for DoS).  IMHO, it seems just simply
| bad protocol design to require such behaviour.
|
| I'm interested what others think about this.. :)
|
| *) MLD should be relatively straight-forward to re-design (just send
| the MLD reports to a link-local address which the router is
| listening), or just keep it as is for now.  RSVP can probably thrown
| away without many tears.
|
| --
| 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



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


From ietf-bounces@ietf.org  Wed Aug 11 09:22:07 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03197;
	Wed, 11 Aug 2004 09:22:07 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1But8C-0007TP-5M; Wed, 11 Aug 2004 09:27:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Buswe-00069f-Rg; Wed, 11 Aug 2004 09:15:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BusmO-0004MK-EB
	for ietf@megatron.ietf.org; Wed, 11 Aug 2004 09:04:32 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01674
	for <ietf@ietf.org>; Wed, 11 Aug 2004 09:04:30 -0400 (EDT)
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Busr9-00073M-7I
	for ietf@ietf.org; Wed, 11 Aug 2004 09:09:27 -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 i7BD6iMW016950;
	Wed, 11 Aug 2004 15:06:44 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <Pine.LNX.4.44.0408111448190.24098-100000@netcore.fi>
References: <Pine.LNX.4.44.0408111448190.24098-100000@netcore.fi>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <F80C2B7C-EB96-11D8-A17C-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Wed, 11 Aug 2004 15:04:24 +0200
To: Pekka Savola <pekkas@netcore.fi>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: hop-by-hop and router alert options
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-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: 7bit

On 11-aug-04, at 13:58, Pekka Savola wrote:

> The justification is simple: any "magic" packets which all routers on
> the path must somehow examine and process seems a very dubious concept
> when we want to avoid DoS attacks etc. on the core equipment which
> must run on hardware: effectively this means that either these are
> ignored in any case (nullifying the use of such options), or put on a
> "slow path" (causing a potential for DoS).  IMHO, it seems just simply
> bad protocol design to require such behaviour.

Well, think of it this way: by having this option, at least you know 
you DON'T have to look at all the packets that don't have this option 
in them. So that's a big fat optimization right there.  :-)

Obviously there can be DoS issues here, but these can be managed with 
rate limiting. Just as long as failure by the router to look at the 
option can be survived in some fashion by the protocol, there shouldn't 
be any problems.

Anyway, this is an operational issue. People who don't want their 
routers to potentially handle all packets in the slow path should have 
the option of disabling this feature. Removing existing specifications 
won't do much good here. (As it almost never does.)


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


From ietf-bounces@ietf.org  Wed Aug 11 10:28:55 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08342;
	Wed, 11 Aug 2004 10:28:55 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BuuAo-0000Al-EY; Wed, 11 Aug 2004 10:33:53 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ButyY-000754-IQ; Wed, 11 Aug 2004 10:21:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Butum-0005cX-PS; Wed, 11 Aug 2004 10:17:16 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07459;
	Wed, 11 Aug 2004 10:17:14 -0400 (EDT)
Received: from goose.ehsco.com ([207.65.203.98])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ButzX-0008Qj-8p; Wed, 11 Aug 2004 10:22:12 -0400
Received: from [192.168.0.5] (cable0-stm-219.gmpexpress.net [63.147.50.219])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client did not present a certificate)
	by goose.ehsco.com (Postfix ) with ESMTP id A3ED13ED7A;
	Wed, 11 Aug 2004 09:17:13 -0500 (CDT)
Message-ID: <411A2A3F.70505@ehsco.com>
Date: Wed, 11 Aug 2004 10:16:31 -0400
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7) Gecko/20040616
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Philip Guenther <guenther+ietfd@sendmail.com>
References: <E1BuCka-00016P-6d@megatron.ietf.org>	<16664.44858.761574.980321@chiark.greenend.org.uk>
	<4118E64D.7060307@ehsco.com>
	<200408110259.i7B2xLOV043227@lab.smi.sendmail.com>
In-Reply-To: <200408110259.i7B2xLOV043227@lab.smi.sendmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: 7bit
Cc: iesg@ietf.org, ietf@ietf.org,
        Ian Jackson <ijackson@chiark.greenend.org.uk>
Subject: Re: Last Call: 'The APPLICATION/MBOX Media-Type' to
	Proposed	Standard
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Content-Transfer-Encoding: 7bit


On 8/10/2004 10:59 PM, Philip Guenther wrote:

> If there are no defined semantics for the content of an application/mbox
> part, how does the type differ from application/octect-stream?

It provides an identifier for the content, so that transfer agents can
perform specific tasks against the data (such as importing or searching a
remote mailstore, or handing the data to an agent that knows what to do
with it). The agent still needs to deal with content-specific issues like
determining the EOL markers, applying default domains to relative
addresses, and so forth. That's a pretty common separation of powers;
application/postscript doesn't relieve the system from needing a
postscript interpreter, and we leave things like ~version tags for the
content agent to worry about instead of the transfer agent.

> [regarding creating a spec for a mailbox file format]
> 
>>I'd like to see one, and I'd like to see whatever *NIX consortium is
>>responsible for such things get together and define one.
> 
> At that point, would application/mbox be updated to refer to said spec,
> rendering non-compliant some chunk of the previous uses, or would a new
> content-type be specified?

Given that the current proposal specifies minimal formatting (essentially
being limited to the likely presence of some kind of From_ line), I'd
think that a reasonably authoritative spec could be referenced in an
update to this proposal. It would depend in large part on the depth and
comprehensiveness of the specification, I'd imagine.

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

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


From ietf-bounces@ietf.org  Wed Aug 11 11:01:05 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10733;
	Wed, 11 Aug 2004 11:01:05 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Buufz-0000pM-Qj; Wed, 11 Aug 2004 11:06:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BuuUW-0004bq-4I; Wed, 11 Aug 2004 10:54:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BuuLt-0002ib-JO; Wed, 11 Aug 2004 10:45:17 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09498;
	Wed, 11 Aug 2004 10:45:15 -0400 (EDT)
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BuuQd-0000Rm-Mx; Wed, 11 Aug 2004 10:50:13 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.13.1/8.13.1) id i7BEihhb081398 env-from
	<vjs>; Wed, 11 Aug 2004 08:44:43 -0600 (MDT)
Date: Wed, 11 Aug 2004 08:44:43 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200408111444.i7BEihhb081398@calcite.rhyolite.com>
To: iesg@ietf.org, ietf@ietf.org
References: <411A2A3F.70505@ehsco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Subject: Re: Last Call: 'The APPLICATION/MBOX Media-Type' to
	Proposed	Standard
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca

> From: "Eric A. Hall" <ehall@ehsco.com>
>
> > If there are no defined semantics for the content of an application/mbox
> > part, how does the type differ from application/octect-stream?
>
> It provides an identifier for the content, so that transfer agents can
> perform specific tasks against the data (such as importing or searching a
> remote mailstore, or handing the data to an agent that knows what to do
> with it). The agent still needs to deal with content-specific issues like
> determining the EOL markers, applying default domains to relative
> addresses, and so forth. That's a pretty common separation of powers;
> application/postscript doesn't relieve the system from needing a
> postscript interpreter, and we leave things like ~version tags for the
> content agent to worry about instead of the transfer agent.
>
> > [regarding creating a spec for a mailbox file format]
> > 
> >>I'd like to see one, and I'd like to see whatever *NIX consortium is
> >>responsible for such things get together and define one.
> > 
> > At that point, would application/mbox be updated to refer to said spec,
> > rendering non-compliant some chunk of the previous uses, or would a new
> > content-type be specified?
>
> Given that the current proposal specifies minimal formatting (essentially
> being limited to the likely presence of some kind of From_ line), I'd
> think that a reasonably authoritative spec could be referenced in an
> update to this proposal. It would depend in large part on the depth and
> comprehensiveness of the specification, I'd imagine.

I cannot understand that except as saying that this document explicitly
and intentionally does not provide enough information for the recipient
of a message defined by the document to decode the message.  I understand
that statement as saying that the data is essentially opaque.

Isn't the point of any RFC on the standards track to promote
interoperability?  What good is an RFC that says "consult as yet
unwritten specifications from undetermined sources to handle the data
standardized by this RFC"?   Isn't the first sanity test of a standard
whether one can determine if an implementation is compliant?  As far
as I can see, Eric Hall is saying that compliance of senders and
receivers of such messages could not be determined until some.

Aren't there already enough opague application data MIME types?


Vernon Schryver    vjs@rhyolite.com

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


From ietf-bounces@ietf.org  Wed Aug 11 14:26:12 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24246;
	Wed, 11 Aug 2004 14:26:12 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BuxsU-0004aX-BE; Wed, 11 Aug 2004 14:31:11 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BuxhL-0002Sn-TM; Wed, 11 Aug 2004 14:19:39 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BuxdJ-0001PF-Hj
	for ietf@megatron.ietf.org; Wed, 11 Aug 2004 14:15:29 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23604
	for <ietf@ietf.org>; Wed, 11 Aug 2004 14:15:28 -0400 (EDT)
Received: from sklave3.rackland.de ([213.133.101.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Buxi5-0004Mx-6X
	for ietf@ietf.org; Wed, 11 Aug 2004 14:20:27 -0400
Received: from sputnik (uucp@localhost)
	by sklave3.rackland.de (8.12.10/8.12.10/Debian-1) with BSMTP id
	i7BIFGhK017942 for ietf@ietf.org; Wed, 11 Aug 2004 20:15:16 +0200
Received: (from hadmut@localhost)
	by sputnik.mobil.danisch.de (8.12.11/8.12.11/Debian-5) id
	i7BIE6qZ006587 for ietf@ietf.org; Wed, 11 Aug 2004 20:14:06 +0200
From: Hadmut Danisch <hadmut@danisch.de>
Date: Wed, 11 Aug 2004 11:14:06 -0700
To: ietf@ietf.org
Message-ID: <20040811181406.GA6481@danisch.de>
References: <DD7FE473A8C3C245ADA2A2FE1709D90B0DB32F@server2003.arneill-py.sacramento.ca.us>
	<20040806171517.GA2875@danisch.de>
	<200408061918.19897.dja2003@hotpop.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200408061918.19897.dja2003@hotpop.com>
User-Agent: Mutt/1.5.6+20040523i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Subject: Re: YATS? Re: T-shirts,
	and some suggestions for future 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-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f



I, btw, just checked in at the Usenix Security Symposium and received
a very nice, durable, and usable, but still not too expensive bag with
a Usenix logo printed on.

That's much better than any T-Shirt.


regards
Hadmut



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


From ietf-bounces@ietf.org  Wed Aug 11 14:56:46 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27448;
	Wed, 11 Aug 2004 14:56:46 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BuyM4-0005QB-Gi; Wed, 11 Aug 2004 15:01:46 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BuyCC-0001eW-R5; Wed, 11 Aug 2004 14:51:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Buy31-0006cU-Up
	for ietf@megatron.ietf.org; Wed, 11 Aug 2004 14:42:03 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25859
	for <ietf@ietf.org>; Wed, 11 Aug 2004 14:42:01 -0400 (EDT)
Received: from mail00.afilias.info ([170.224.17.215] helo=ns01.afilias.info)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Buy7n-0004so-8c
	for ietf@ietf.org; Wed, 11 Aug 2004 14:47:00 -0400
Received: from DONMASON (desiree.claranet.co.uk [80.168.134.102])
	(authenticated bits=0)
	by ns01.afilias.info (8.12.8/8.12.8) with ESMTP id i7BIfMkR027762
	for <ietf@ietf.org>; Wed, 11 Aug 2004 14:41:23 -0400
From: "Desiree Miloshevic" <dmiloshevic@afilias.info>
To: <ietf@ietf.org>
Date: Wed, 11 Aug 2004 19:39:01 -0400
Message-ID: <NPEKKLIPPBBGLOPDKIACMEBACKAA.dmiloshevic@afilias.info>
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: <20040811181406.GA6481@danisch.de>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Importance: Normal
X-Spam-Score: 2.8 (++)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7bit
Subject: RE: YATS? Re: T-shirts,
	and some suggestions for future ietf meetings
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: dmiloshevic@afilias.info
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-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-Score: 2.8 (++)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: 7bit

>I, btw, just checked in at the Usenix Security Symposium and received
>a very nice, durable, and usable, but still not too expensive bag with
>a Usenix logo printed on.

I'd argue that bag is the best deal.
It really depends on the quality. I get a bag at almost every single meeting
I go to.
OTOH, if it is exceptionally well made, like the recent APRICOT 2004
back-pack
or the old INET 2000 Yokohama bag that easily fits a 15 inch laptop and was
very
durable... it could be a good suggestion.

Desiree
--


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


From ietf-bounces@ietf.org  Wed Aug 11 15:07:57 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28688;
	Wed, 11 Aug 2004 15:07:57 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BuyWu-0005gd-2n; Wed, 11 Aug 2004 15:12:57 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BuyNh-0000yE-9j; Wed, 11 Aug 2004 15:03:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BuyCV-0001hp-Uo
	for ietf@megatron.ietf.org; Wed, 11 Aug 2004 14:51:52 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26811
	for <ietf@ietf.org>; Wed, 11 Aug 2004 14:51:50 -0400 (EDT)
Received: from mail.enyo.de ([212.9.189.167])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BuyHI-0005FV-Oy
	for ietf@ietf.org; Wed, 11 Aug 2004 14:56:50 -0400
Received: (debugging) helo=deneb.enyo.de ip=212.9.189.171 name=deneb.enyo.de
Received: from deneb.enyo.de ([212.9.189.171])
	by mail.enyo.de with esmtp id 1BuyCR-00081D-HC;
	Wed, 11 Aug 2004 20:51:47 +0200
Received: from fw by deneb.enyo.de with local (Exim 4.34)
	id 1BuyCP-0003Nh-K6; Wed, 11 Aug 2004 20:51:45 +0200
To: Pekka Savola <pekkas@netcore.fi>
References: <Pine.LNX.4.44.0408111448190.24098-100000@netcore.fi>
From: Florian Weimer <fw@deneb.enyo.de>
Date: Wed, 11 Aug 2004 20:51:45 +0200
In-Reply-To: <Pine.LNX.4.44.0408111448190.24098-100000@netcore.fi> (Pekka
	Savola's message of "Wed, 11 Aug 2004 14:58:29 +0300 (EEST)")
Message-ID: <87657pwlry.fsf@deneb.enyo.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: ietf@ietf.org
Subject: Re: hop-by-hop and router alert options [Re: Question about use of
 RSVP in Production Networks]
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-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f

* Pekka Savola:

> The justification is simple: any "magic" packets which all routers on
> the path must somehow examine and process seems a very dubious concept
> when we want to avoid DoS attacks etc.

Any packet with IP options is more or less in that category right now,
so it's a very long way to go.[1]  IPv6 seems to make things even
worse. 8-(

1. Some platforms support dropping IPv4 packets with options.  As
   discussed before, existing contractual obligations with respect to
   source routing may prevent you from enabling such a feature.

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


From ietf-bounces@ietf.org  Wed Aug 11 17:22:14 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18512;
	Wed, 11 Aug 2004 17:22:14 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bv0cs-0003Mr-VU; Wed, 11 Aug 2004 17:27:16 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bv0Hc-0000OQ-L0; Wed, 11 Aug 2004 17:05:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BuyqP-0001wx-1R
	for ietf@megatron.ietf.org; Wed, 11 Aug 2004 15:33:05 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01970
	for <ietf@ietf.org>; Wed, 11 Aug 2004 15:33:03 -0400 (EDT)
Received: from letters.cs.ucsb.edu ([128.111.41.13])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BuyvB-0006Ps-Rx
	for ietf@ietf.org; Wed, 11 Aug 2004 15:38:03 -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 i7BJWsF17143; 
	Wed, 11 Aug 2004 12:32:54 -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 i7BJWrSn010271;
	Wed, 11 Aug 2004 12:32:53 -0700
Received: (from almeroth@localhost)
	by jackson.cs.ucsb.edu (8.12.8/8.12.8/Submit) id i7BJWoxZ010269;
	Wed, 11 Aug 2004 12:32:50 -0700
Date: Wed, 11 Aug 2004 12:32:50 -0700
From: "Kevin C. Almeroth" <almeroth@cs.ucsb.edu>
Message-Id: <200408111932.i7BJWoxZ010269@jackson.cs.ucsb.edu>
To: hadmut@danisch.de, ietf@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Subject: Re: YATS? Re: T-shirts,
	and some suggestions for future 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-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906

>>I, btw, just checked in at the Usenix Security Symposium and received
>>a very nice, durable, and usable, but still not too expensive bag with
>>a Usenix logo printed on.
>>
>>That's much better than any T-Shirt.

You know how many times I go to conferences and end up just
leaving the bag or whatever the gift is in the hotel room?
Every single one.

Though, I must say, the bag from Salt Lake City is the best
one I've ever been given and still use that.  So unless 
there is a really high quality bag that's better, why have 
more than one?

T-shirts are great because they are replaced so frequently.

-Kevin

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


From ietf-bounces@ietf.org  Wed Aug 11 17:31:27 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19983;
	Wed, 11 Aug 2004 17:31:26 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bv0lo-0003od-V8; Wed, 11 Aug 2004 17:36:29 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bv0Vg-0005ca-8p; Wed, 11 Aug 2004 17:19:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BuziP-0004py-W2
	for ietf@megatron.ietf.org; Wed, 11 Aug 2004 16:28:54 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10469
	for <ietf@ietf.org>; Wed, 11 Aug 2004 16:28:51 -0400 (EDT)
Received: from above.proper.com ([208.184.76.39])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BuznD-0000lh-OJ
	for ietf@ietf.org; Wed, 11 Aug 2004 16:33:53 -0400
Received: from [10.20.30.249] (adsl-66-125-125-68.dsl.pltn13.pacbell.net
	[66.125.125.68]) (authenticated bits=0)
	by above.proper.com (8.12.11/8.12.9) with ESMTP id i7BKSjqH086203
	for <ietf@ietf.org>; Wed, 11 Aug 2004 13:28:46 -0700 (PDT)
	(envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
X-Sender: phoffvpnc@mail.vpnc.org
Message-Id: <p06110424bd403198a3a0@[10.20.30.249]>
In-Reply-To: <NPEKKLIPPBBGLOPDKIACMEBACKAA.dmiloshevic@afilias.info>
References: <NPEKKLIPPBBGLOPDKIACMEBACKAA.dmiloshevic@afilias.info>
Date: Wed, 11 Aug 2004 13:28:46 -0700
To: ietf@ietf.org
From: Paul Hoffman / VPNC <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 1.0 (+)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
Subject: RE: YATS? Re: T-shirts, 	and some suggestions for future 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-Score: 1.0 (+)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199

Even mediumly-constructed canvas bags can be more useful than a 
t-shirt. I have no problem using my Networld '91 canvas bag to schlep 
groceries around. And canvas bags are great for lab equipment. Or 
beach gear.

--Paul Hoffman, Director
--VPN Consortium

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


From ietf-bounces@ietf.org  Wed Aug 11 18:15:16 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25555;
	Wed, 11 Aug 2004 18:15:16 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bv1S3-0005Hk-Ib; Wed, 11 Aug 2004 18:20:18 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bv18O-00076F-KS; Wed, 11 Aug 2004 17:59:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bv0ti-0000Zm-GL
	for ietf@megatron.ietf.org; Wed, 11 Aug 2004 17:44:38 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21279
	for <ietf@ietf.org>; Wed, 11 Aug 2004 17:44:35 -0400 (EDT)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bv0yW-0004Ca-SL
	for ietf@ietf.org; Wed, 11 Aug 2004 17:49:38 -0400
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-2.cisco.com with ESMTP; 11 Aug 2004 14:46:28 -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 i7BLi3VD006349
	for <ietf@ietf.org>; Wed, 11 Aug 2004 14:44:04 -0700 (PDT)
Received: from cisco.com ([10.25.65.179])
	by mira-sjc5-c.cisco.com (MOS 3.4.5-GR) with SMTP id AXY38851;
	Wed, 11 Aug 2004 14:44:02 -0700 (PDT)
Date: Wed, 11 Aug 2004 17:43:42 -0400
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v553)
From: Melinda Shore <mshore@cisco.com>
To: ietf@ietf.org
Content-Transfer-Encoding: 7bit
In-Reply-To: <p06110424bd403198a3a0@[10.20.30.249]>
Message-Id: <83504849-EBDF-11D8-923B-000A95E35274@cisco.com>
X-Mailer: Apple Mail (2.553)
X-Spam-Score: 1.0 (+)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Content-Transfer-Encoding: 7bit
Subject: Re: YATS? Re: T-shirts,
	and some suggestions for future 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-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7bit

On Wednesday, August 11, 2004, at 04:28 PM, Paul Hoffman / VPNC wrote:
> Even mediumly-constructed canvas bags can be more useful than a 
> t-shirt.

That varies by human.  One thing that I would love to bits would
be a t-shirt made out of coolmax or some other high-techie fabric,
instead of cotton.  For me, a bag would be less useful - I have more
bags than things to carry.

Melinda


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


From ietf-bounces@ietf.org  Wed Aug 11 18:41:19 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27823;
	Wed, 11 Aug 2004 18:41:19 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bv1rS-0005s2-FP; Wed, 11 Aug 2004 18:46:22 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bv1Y3-00051q-DB; Wed, 11 Aug 2004 18:26:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bv1Rr-0002MK-U0
	for ietf@megatron.ietf.org; Wed, 11 Aug 2004 18:19:56 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26113
	for <ietf@ietf.org>; Wed, 11 Aug 2004 18:19:53 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bv1Wg-0005Mn-L6
	for ietf@ietf.org; Wed, 11 Aug 2004 18:24:56 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i7BMJ2X11233;
	Wed, 11 Aug 2004 15:19:02 -0700
X-mProtect: <200408112219> Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89,
	claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdhgdntE; Wed, 11 Aug 2004 15:19:01 PDT
Message-ID: <411A9B5E.91EF7999@iprg.nokia.com>
Date: Wed, 11 Aug 2004 15:19:10 -0700
From: "Charles E.Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Paul Hoffman / VPNC <paul.hoffman@vpnc.org>
References: <NPEKKLIPPBBGLOPDKIACMEBACKAA.dmiloshevic@afilias.info>
	<p06110424bd403198a3a0@[10.20.30.249]>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 1.0 (+)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: YATS? Re: T-shirts, and some suggestions for future ietfmeetings
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-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: 7bit


A dozen conference bags might already be
enough to last for many years.  A dozen
T-shirts might be barely enough to last
between visits to the laundromat.
I'd be a lot happier with more T-shirts,
in preference to more conference bags.

Regards,
Charlie P.

PS. I have a lot of extra conference bags
    I would trade for something...


Paul Hoffman / VPNC wrote:
> 
> Even mediumly-constructed canvas bags can be more useful than a
> t-shirt. I have no problem using my Networld '91 canvas bag to schlep
> groceries around. And canvas bags are great for lab equipment. Or
> beach gear.
> 
> --Paul Hoffman, Director
> --VPN Consortium

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


From ietf-bounces@ietf.org  Wed Aug 11 18:56:38 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28627;
	Wed, 11 Aug 2004 18:56:38 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bv26G-00067q-S9; Wed, 11 Aug 2004 19:01:42 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bv1qD-0000i0-1I; Wed, 11 Aug 2004 18:45:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bv1j0-00073X-NF
	for ietf@megatron.ietf.org; Wed, 11 Aug 2004 18:37:38 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27401
	for <ietf@ietf.org>; Wed, 11 Aug 2004 18:37:35 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bv1np-0005jU-GC
	for ietf@ietf.org; Wed, 11 Aug 2004 18:42:39 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i7BMaaL24403;
	Wed, 11 Aug 2004 15:36:36 -0700
X-mProtect: <200408112236> Nokia Silicon Valley Messaging Protection
Received: from dadhcp-172019069052.americas.nokia.com (172.19.69.52,
	claiming to be "l5131412.nokia.com")
	by darkstar.iprg.nokia.com smtpd9ePa0Z; Wed, 11 Aug 2004 15:36:34 PDT
Message-Id: <4.3.2.7.2.20040811133213.0269cc30@mailhost.iprg.nokia.com>
X-Sender: hinden@mailhost.iprg.nokia.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 11 Aug 2004 15:36:36 -0700
To: Florian Weimer <fw@deneb.enyo.de>
From: Bob Hinden <bob.hinden@nokia.com>
In-Reply-To: <87657pwlry.fsf@deneb.enyo.de>
References: <Pine.LNX.4.44.0408111448190.24098-100000@netcore.fi>
	<Pine.LNX.4.44.0408111448190.24098-100000@netcore.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: Pekka Savola <pekkas@netcore.fi>, ietf@ietf.org
Subject: Re: hop-by-hop and router alert options [Re: Question about
 use of RSVP in Production Networks]
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-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034

Florian,

At 11:51 AM 08/11/2004, Florian Weimer wrote:
>* Pekka Savola:
>
> > The justification is simple: any "magic" packets which all routers on
> > the path must somehow examine and process seems a very dubious concept
> > when we want to avoid DoS attacks etc.
>
>Any packet with IP options is more or less in that category right now,
>so it's a very long way to go.[1]  IPv6 seems to make things even
>worse. 8-(

That's not quite correct.  Unlike IPv4, IPv6 has two types of options, 
hop-by-hop and destination options.  The destination options are useful 
because they are only looked at by the destination host and are not 
examined by routers.  Routers only have to look at the hop by hop options 
and their presence in the packet is easy to detect.  See RFC2460 for details.

I am not a fan of hop-by-hop options and am sympathetic to Pekka's 
suggestion, but I don't think it will be possible to prohibit their use.  I 
wouldn't object to discouraging their use and agree we should think very 
hard about defining any new ones.

Bob





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


From ietf-bounces@ietf.org  Wed Aug 11 19:03:31 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29043;
	Wed, 11 Aug 2004 19:03:31 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bv2Cv-0006Fp-32; Wed, 11 Aug 2004 19:08:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bv1qE-0000iB-V2; Wed, 11 Aug 2004 18:45:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bv1je-0007FF-2q
	for ietf@megatron.ietf.org; Wed, 11 Aug 2004 18:38:18 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27460
	for <ietf@ietf.org>; Wed, 11 Aug 2004 18:38:13 -0400 (EDT)
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bv1oO-0005kM-Uy
	for ietf@ietf.org; Wed, 11 Aug 2004 18:43: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 i7BMbVRY029260
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 11 Aug 2004 18:37:34 -0400
Date: Wed, 11 Aug 2004 18:37:31 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: "Fleischman, Eric" <eric.fleischman@boeing.com>
In-Reply-To: <5B58696DB20B9140AD20E0685C573A6404FDD6BB@xch-nw-09.nw.nos.boeing.com>
Message-ID: <Pine.LNX.4.44.0408111821280.28896-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 2.7 (++)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: ietf@ietf.org
Subject: Re: Question about use of RSVP in Production Networks
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-Score: 2.7 (++)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64

RSVP is a idea that doesn't cut the mustard in the real world. There are 
several show-stopper problems with RSVP.

1) somewhat like multicast, anyone using RSVP is vulnerable to others
mis-using or mis-configuring RSVP. ISPs several AS's away can really screw
up things for other ISPs. Because of this, it is unwise to deploy it
because it requires too much trust in other ISPs.

That relegates RSVP to the enterprise Lan, where it usually isn't needed.  
Remember, RSVP is only useful if you have a congestion problem and need to
choose which packets to discard.  If you have no congestion problem, then
you have no need of RSVP. However, having a congestion problem also opens
the question of the nature of the congestion and what is the best way to
deal that problem.  I was involved in a study done by Genuity and Cisco in
which the congestion problem was found to most often involve the tail
circuit--the link between the customer and the ISP.  The best solution for
this problem was found to be low latency queuing, not RSVP.

2) Unlike multicast, every hop end-to-end must use RSVP for it to be 
useful. An RSVP tunnel is useless.

3) RSVP doesn't detect certain kinds of problems that are important. For
example, a mid-span failure is not visible to RSVP.

While RSVP is important research, it is not a widely deployable
technology.

What I-D's are you encountering that depend on RSVP?

		--Dean

On Tue, 10 Aug 2004, Fleischman, Eric wrote:

> I am aware of some use of RSVP in labs but I am not aware of any use of
> RSVP in production networks (i.e., real life networks people connect to
> the Internet with). Simultaneously, I am encountering I-Ds and other
> work planning to use RSVP. This possible disconnect concerns me.
> Therefore, I would appreciate being educated by anybody using RSVP in
> production settings. Would you please let me know how many devices, what
> applications, and how successful these deployments (if any) are? Thank
> you.
> 
> 
> _______________________________________________
> 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 Aug 11 20:20:56 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02498;
	Wed, 11 Aug 2004 20:20:56 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bv3Pr-0007LD-9M; Wed, 11 Aug 2004 20:25:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bv3Ic-0007kK-13; Wed, 11 Aug 2004 20:18:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bv3Ht-0007RD-D6
	for ietf@megatron.ietf.org; Wed, 11 Aug 2004 20:17:45 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02323
	for <ietf@ietf.org>; Wed, 11 Aug 2004 20:17:43 -0400 (EDT)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bv3Mj-0007Hv-9K
	for ietf@ietf.org; Wed, 11 Aug 2004 20:22:46 -0400
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-3.cisco.com with ESMTP; 11 Aug 2004 17:21:10 +0000
X-BrightmailFiltered: true
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i7C0H9Te016940;
	Wed, 11 Aug 2004 17:17:09 -0700 (PDT)
Received: from localhost (ole@localhost) by wells.cisco.com (8.8.6
	(PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id RAA16761;
	Wed, 11 Aug 2004 17:17:10 -0700 (PDT)
Date: Wed, 11 Aug 2004 17:17:10 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Hadmut Danisch <hadmut@danisch.de>
In-Reply-To: <20040811181406.GA6481@danisch.de>
Message-ID: <Pine.HPX.4.58.0408111712370.4999@wells.cisco.com>
References: <DD7FE473A8C3C245ADA2A2FE1709D90B0DB32F@server2003.arneill-py.sacramento.ca.us>
	<20040806171517.GA2875@danisch.de>
	<200408061918.19897.dja2003@hotpop.com>
	<20040811181406.GA6481@danisch.de>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: ietf@ietf.org
Subject: Re: YATS? Re: T-shirts,
	and some suggestions for future ietf meetings
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa

Problem is you get a bag at almost EVERY conference in this industry. I've
started to (politely) refuse the bag in the last 5 years or so, accepting
only any "required" contents such as the program.

Years ago, when I worked for Interop, we over-ordered on the canvas bags
one year and made a donation of a pile of them to some shelter. Soon we
began to spot homeless people on the street sporting the colorful Interop
bag.

I guess any form of "product placement" is good, right? :-)

Ole

Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Academic Research and Technology Initiatives, Cisco Systems
Tel: +1 408-527-8972   GSM: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj


On Wed, 11 Aug 2004, Hadmut Danisch wrote:

>
>
> I, btw, just checked in at the Usenix Security Symposium and received
> a very nice, durable, and usable, but still not too expensive bag with
> a Usenix logo printed on.
>
> That's much better than any T-Shirt.
>
>
> regards
> Hadmut
>
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>

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


From ietf-bounces@ietf.org  Wed Aug 11 20:38:39 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA03345;
	Wed, 11 Aug 2004 20:38:39 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bv3gy-0007aN-RP; Wed, 11 Aug 2004 20:43:42 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bv3Yv-0001pK-W6; Wed, 11 Aug 2004 20:35:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bv3WS-00017W-LV
	for ietf@megatron.ietf.org; Wed, 11 Aug 2004 20:32:48 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA03028
	for <ietf@ietf.org>; Wed, 11 Aug 2004 20:32:47 -0400 (EDT)
Received: from mail.hammerheadsystems.com ([12.108.173.98])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bv3bG-0007Vl-O2
	for ietf@ietf.org; Wed, 11 Aug 2004 20:37:50 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 11 Aug 2004 17:32:10 -0700
Message-ID: <2DAC9E7A4640234B85975565E5D83AE173053A@srvcaexg01.headquarters.hammerheadsystems.com>
Thread-Topic: Question about use of RSVP in Production Networks
Thread-Index: AcR/93JHeZG9iwYtSteAY5nJerXchgAC5D1g
From: "Ping Pan" <ppan@hammerheadsystems.com>
To: "Fleischman, Eric" <eric.fleischman@boeing.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
Subject: RE: Question about use of RSVP in Production Networks
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-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: quoted-printable

Do you count for RSVP-TE, that has been deployed widely in carrier
networks? Other than multicast and wild-card filtering, all other
features (and more) defined in the context of RSVP have been developed
and deployed. The number of RSVP sessions (a.k.a. MPLS LSP's) is in the
range of thousands in large backbone networks.

Hope this will help.

- Ping


On Tue, 10 Aug 2004, Fleischman, Eric wrote:

> I am aware of some use of RSVP in labs but I am not aware of any use=20
> of RSVP in production networks (i.e., real life networks people=20
> connect to the Internet with). Simultaneously, I am encountering I-Ds=20
> and other work planning to use RSVP. This possible disconnect concerns

> me. Therefore, I would appreciate being educated by anybody using RSVP

> in production settings. Would you please let me know how many devices,

> what applications, and how successful these deployments (if any) are?=20
> Thank you.
>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>=20

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


From ietf-bounces@ietf.org  Thu Aug 12 06:16:08 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA18543;
	Thu, 12 Aug 2004 06:16:08 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BvChx-0000Dp-Gz; Thu, 12 Aug 2004 06:21:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BvCSk-0000IC-Ad; Thu, 12 Aug 2004 06:05:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BvCMf-0002Zd-A6
	for ietf@megatron.ietf.org; Thu, 12 Aug 2004 05:59:17 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17543
	for <ietf@ietf.org>; Thu, 12 Aug 2004 05:59:15 -0400 (EDT)
Received: from fep22-0.kolumbus.fi ([193.229.0.60] helo=fep22-app.kolumbus.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BvCRa-0008Lv-8e
	for ietf@ietf.org; Thu, 12 Aug 2004 06:04:23 -0400
Received: from [10.68.199.142] (really [213.161.45.112])
	by fep22-app.kolumbus.fi with ESMTP
	id <20040812095911.IHNS27645.fep22-app.kolumbus.fi@[10.68.199.142]>;
	Thu, 12 Aug 2004 12:59:11 +0300
From: "John Loughney" <john.loughney@kolumbus.fi>
To: "shogunx" <shogunx@sleekfreak.ath.cx>
Date: Thu, 12 Aug 2004 12:58:15 +0200
Message-ID: <Mcb2vmhgfmTY.2blyQFP7@mail.kolumbus.fi>
X-Mailer: EPOC Email Version 2.10
MIME-Version: 1.0
Content-Language: i-default
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 2.9 (++)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
Subject: Re: YATS? Re: T-shirts,
 and some suggestions fo
 r future ietf meetings
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: John Loughney <john.loughney@kolumbus.fi>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-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-Score: 1.9 (+)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: quoted-printable

If we scheduled the March meeting in New Orleans or Rio, maybe things would =
get interesting!

John

________________ Reply Header ________________
Subject:	Re: YATS? Re: T-shirts,
	and some suggestions for future ietf meetings
Author:	"shogunx" <shogunx@sleekfreak.ath.cx>
Date:		09th August 2004 5:21:34  PM

On Tue, 10 Aug 2004, George Michaelson wrote:

Personally, I find the requirement of wearing clothes tiresome, but =
then
again, who REALLY wants to see all the IETF'ers naked?

Enjoy,
Scott


>
> Jon Crowcroft told us in UCL-CS back in '85 that the pre-IETF meetings =
were
> smoke filled rooms, including uniforms with medal-bars out to the =
elbows...
>
> -George
>
> _______________________________________________
> 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


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


From ietf-bounces@ietf.org  Thu Aug 12 08:34:35 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27778;
	Thu, 12 Aug 2004 08:34:35 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BvEru-0002tc-OT; Thu, 12 Aug 2004 08:39:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BvEdK-0003Ho-CQ; Thu, 12 Aug 2004 08:24:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BusZG-0001cT-Ox
	for ietf@megatron.ietf.org; Wed, 11 Aug 2004 08:50:58 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00826
	for <ietf@ietf.org>; Wed, 11 Aug 2004 08:50:57 -0400 (EDT)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Buse1-0006n7-Du
	for ietf@ietf.org; Wed, 11 Aug 2004 08:55:53 -0400
Received: from sj-core-4.cisco.com (171.68.223.138)
	by sj-iport-2.cisco.com with ESMTP; 11 Aug 2004 05:52:45 -0700
Received: from mira-sjc5-d.cisco.com (IDENT:mirapoint@mira-sjc5-d.cisco.com
	[171.71.163.28])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id i7BCoP13004926;
	Wed, 11 Aug 2004 05:50:25 -0700 (PDT)
Received: from [192.168.100.35] (sjc-vpn3-1161.cisco.com [10.21.68.137])
	by mira-sjc5-d.cisco.com (MOS 3.4.6-GR) with ESMTP id ADT76126;
	Wed, 11 Aug 2004 05:50:24 -0700 (PDT)
In-Reply-To: <Pine.LNX.4.44.0408111448190.24098-100000@netcore.fi>
References: <Pine.LNX.4.44.0408111448190.24098-100000@netcore.fi>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <0189FED6-EB95-11D8-AAFC-000A95C73842@cisco.com>
Content-Transfer-Encoding: 7bit
From: David R Oran <oran@cisco.com>
Date: Wed, 11 Aug 2004 08:50:21 -0400
To: Pekka Savola <pekkas@netcore.fi>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Thu, 12 Aug 2004 08:24:36 -0400
Cc: ietf@ietf.org
Subject: Re: hop-by-hop and router alert options [Re: Question about use of
	RSVP in Production Networks]
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-Score: 0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Content-Transfer-Encoding: 7bit


On Aug 11, 2004, at 7:58 AM, Pekka Savola wrote:

> On Tue, 10 Aug 2004, Fleischman, Eric wrote:
>> I am aware of some use of RSVP in labs but I am not aware of any use
>> of RSVP in production networks (i.e., real life networks people
>> connect to the Internet with). Simultaneously, I am encountering
>> I-Ds and other work planning to use RSVP. This possible disconnect
>> concerns me. Therefore, I would appreciate being educated by anybody
>> using RSVP in production settings. Would you please let me know how
>> many devices, what applications, and how successful these
>> deployments (if any) are? Thank you.
>
> I'd be interested about this as well, but also in more general.
>
> I'd be in favor of deprecating the IP router alert option completely.
> Effectively this affects RSVP and MLD *).  I'd want to similarly do
> away with the IPv6 Hop-by-Hop options.  At the very least, I'd like to
> prevent further standardization of these options.
>
> The justification is simple: any "magic" packets which all routers on
> the path must somehow examine and process seems a very dubious concept
> when we want to avoid DoS attacks etc. on the core equipment which
> must run on hardware: effectively this means that either these are
> ignored in any case (nullifying the use of such options), or put on a
> "slow path" (causing a potential for DoS).  IMHO, it seems just simply
> bad protocol design to require such behaviour.
>
> I'm interested what others think about this.. :)
>
If you can come up with another technique for doing path-coupled 
signaling which is less susceptible to abuse I'd drop RAO in a 
heart-beat. There are a bunch of very useful things that require (or at 
least work a heck of a lot better with) path-coupled signaling:
- figuring out where to install QoS state in complex topologies
- firewall and NAT traversal
- finding the thing furthest away from you (as opposed to closest to 
you) that performs a certain function, such as state-deaggregation for 
QoS or tunnel anchor for IPSEC tunnels.

It seems to me that the key is to be able to screen packets at wire 
rate, even if they must be looked at by the control plane of each 
router. that seems only loosely related to RAO itself.

> *) MLD should be relatively straight-forward to re-design (just send
> the MLD reports to a link-local address which the router is
> listening), or just keep it as is for now.  RSVP can probably thrown
> away without many tears.
>
> -- 
> 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
> _______________________________________________
> 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).
>
David R. Oran
Cisco Fellow
Cisco Systems
7 Ladyslipper Lane
Acton, MA 01720 USA
Tel: +1 978 264 2048
Email: oran@cisco.com


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


From ietf-bounces@ietf.org  Thu Aug 12 08:36:08 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27918;
	Thu, 12 Aug 2004 08:36:08 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BvEtR-0002vx-1j; Thu, 12 Aug 2004 08:41:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BvEdL-0003Hw-H1; Thu, 12 Aug 2004 08:24:39 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bv38u-0006Dm-QP; Wed, 11 Aug 2004 20:08:28 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01900;
	Wed, 11 Aug 2004 20:08:27 -0400 (EDT)
Received: from smtp02.mrf.mail.rcn.net ([207.172.4.61])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bv3Cb-00079g-Nj; Wed, 11 Aug 2004 20:13:29 -0400
X-Info: This message was accepted for relay by
	smtp02.mrf.mail.rcn.net as the sender used SMTP authentication
X-Trace: BXS2LVIfXpTRS1f0E5DlOpAV43y4seaRYopzLbSHoMo=
Received: from 65.105.220.34.ptr.us.xo.net ([65.105.220.34]
	helo=mail.blilly.com)
	by smtp02.mrf.mail.rcn.net with asmtp (Exim 3.35 #7)
	id 1Bv37O-0000IQ-00; Wed, 11 Aug 2004 20:06:54 -0400
Received: from marty.blilly.com (localhost [127.0.0.1])
	by mail.blilly.com with ESMTP
	id i7C06ljC011891(8.12.10/8.12.10/mail.blilly.com sendmail.mc.mail 1.18
	2004/05/15 07:23:45) ; Wed, 11 Aug 2004 20:06:48 -0400
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by marty.blilly.com with ESMTP
	id i7C06lYD011889(8.12.10/8.12.10/blilly.com submit.mc 1.1 2003/08/26
	22:21:33) ; Wed, 11 Aug 2004 20:06:47 -0400
Message-ID: <411AB496.8080307@erols.com>
Date: Wed, 11 Aug 2004 20:06:46 -0400
From: Bruce Lilly <blilly@erols.com>
Organization: Bruce Lilly
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616
X-Accept-Language: en-us
MIME-Version: 1.0
To: iesg@ietf.org, ietf@ietf.org
References: <p06110437bd3d5d396de1@[10.20.30.249]>
In-Reply-To: <p06110437bd3d5d396de1@[10.20.30.249]>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Thu, 12 Aug 2004 08:24:36 -0400
Cc: 822 <ietf-822@imc.org>
Subject: Re: Last Call: 'The APPLICATION/MBOX Media-Type' to Proposed
	Standard
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: iesg@ietf.org, ietf@ietf.org, ietf-822@imc.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: 7bit

The IESG wrote:
> 
> The IESG has received a request from an individual submitter to consider
> the
> following document:
> 
> - 'The APPLICATION/MBOX Media-Type '
>    <draft-hall-mime-app-mbox-02.txt> as a Proposed Standard
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action.  Please send any comments to the
> iesg@ietf.org or ietf@ietf.org mailing lists by 2004-09-06.
> 
> The file can be obtained via
> http://www.ietf.org/internet-drafts/draft-hall-mime-app-mbox-02.txt
> 
> 
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf-announce

The draft mentions that "some form of external
     negotiation or prior agreement is often necessary in order to
     ensure that the contents of the database are accurately read by
     messaging systems on other hosts".

MIME provides for such mechanisms via the Content-Type field
parameters.  It would appear to be desirable to define at least
two parameter attributes for use with this media type, viz. one
defining the separator between messages (perhaps as a regular
expression), and another defining the line-ending sequence in use
(defaulting to CRLF).  Note that RFC 2231 provides mechanisms for
quoting and encoding parameter content, so that for example a lone
LF line-ending sequence could be encoded in the parameter value as
"%0A".

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


From ietf-bounces@ietf.org  Thu Aug 12 09:10:16 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29772;
	Thu, 12 Aug 2004 09:10:16 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BvFQT-0003XM-Ft; Thu, 12 Aug 2004 09:15:25 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BvFG9-0002PD-2V; Thu, 12 Aug 2004 09:04:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BvF5Z-0000Vk-F4
	for ietf@megatron.ietf.org; Thu, 12 Aug 2004 08:53:49 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28919
	for <ietf@ietf.org>; Thu, 12 Aug 2004 08:53:48 -0400 (EDT)
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BvFAV-0003FS-Ku
	for ietf@ietf.org; Thu, 12 Aug 2004 08:58:57 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i7CCrE901452
	for <ietf@ietf.org>; Thu, 12 Aug 2004 15:53:14 +0300
Date: Thu, 12 Aug 2004 15:53:14 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: ietf@ietf.org
In-Reply-To: <C247C5A2924B780EE4DE8B5D@[10.1.1.109]>
Message-ID: <Pine.LNX.4.44.0408121539030.1209-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Subject: Re: hop-by-hop and router alert options [Re: Question about use of
 RSVP in Production Networks]
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-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17

Thanks for the responses so far.  Trying to answer in general...

On Wed, 11 Aug 2004, Martin Stiemerling wrote:
[Pekka:]
> | I'd be interested about this as well, but also in more general.
> |
> | I'd be in favor of deprecating the IP router alert option completely.
> | Effectively this affects RSVP and MLD *).  I'd want to similarly do
> | away with the IPv6 Hop-by-Hop options.  At the very least, I'd like to
> | prevent further standardization of these options.
> 
> Hmm, NSIS protocol suite (new protocol that does path-coupled QoS signaling 
> ala RSVP and firewall/NAT signaling) relies on the use of router alert 
> options for the initial NSIS peer discovery process.  Is there any other 
> proposal to get a discovery mechanism like router alert options without the 
> disadvantages of this option?

I question the usefulness of path-coupled signalling beyond a certain 
point in the network.  Dean Anderson voiced them pretty well in the 
original thread about RSVP -- it just doesn't seem to make any sense 
beyond a very closed environment (like the first hop) -- and in that 
case, you should be able to use another kind of signalling as well.

If we don't learn anything of the mistakes we did with RSVP, we're 
bound to repeat them.

For example, has the design clearly restricted itself to the first or 
the last hop, or within the first couple of hops?

For that purpose, I'm not 100% sure if you would need a path-coupled
signalling.  You'll certainly want path-coupled signalling for
signalling with a much wider "span" (because it's the simplest way to
do it from the host's perspective), but I'm arguing (as Dean was) that
this isn't an interesting approach from the network operators'
perspective.

...

As for the alternatives:
 1) for first-hop only, there's really little need for a router alert, 
any protocol would do, as you already know who your routers are :-)
 2) for hops beyond the first-hop router, I'd consider setting up a 
single server which would be responsible for brokering the QoS 
capabilities, firewall holes, etc. You contact the server, and ask it 
to open a certain kind of hole, set up certain QoS between (source, 
destination), etc.  There are a number of options how you could 
discover this kind of system:
    a) a DHCP option
    b) a DNS lookup (e.g., SRV record based on your DNS search path)
    c) asking the upstream router using protocol learned in 1).

These kind of approaches essentially move the intelligence and
processing to specific nodes who are better capable of handling such
requests, having policy who can request what, removing the processing
and cruft from the routers.  And the hosts have have much easier time
figuring out whether requesting these capabilities is supported in the
network, instead of spewing a considerable amount of in-band
signalling attempts to the network.

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




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


From ietf-bounces@ietf.org  Thu Aug 12 09:53:54 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02242;
	Thu, 12 Aug 2004 09:53:53 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BvG6e-0004ML-W6; Thu, 12 Aug 2004 09:59:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BvFkk-0000iB-4M; Thu, 12 Aug 2004 09:36:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BvFgo-00081e-LL
	for ietf@megatron.ietf.org; Thu, 12 Aug 2004 09:32:18 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01076
	for <ietf@ietf.org>; Thu, 12 Aug 2004 09:32:16 -0400 (EDT)
Received: from user-0c6s17c.cable.mindspring.com ([24.110.4.236]
	helo=sleekfreak.ath.cx) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BvFll-0003xi-AI
	for ietf@ietf.org; Thu, 12 Aug 2004 09:37:26 -0400
Received: from localhost ([127.0.0.1])
	by sleekfreak.ath.cx with esmtp (Exim 3.36 #1 (Debian))
	id 1BvAzm-0000uH-00; Thu, 12 Aug 2004 04:31:34 -0400
Date: Thu, 12 Aug 2004 04:31:33 -0400 (EDT)
From: shogunx <shogunx@sleekfreak.ath.cx>
To: John Loughney <john.loughney@kolumbus.fi>
In-Reply-To: <Mcb2vmhgfmTY.2blyQFP7@mail.kolumbus.fi>
Message-ID: <Pine.LNX.4.44.0408120430460.3486-100000@sleekfreak.ath.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 1.9 (+)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Cc: ietf@ietf.org
Subject: Re: YATS? Re: T-shirts,
	and some suggestions fo r future 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-Score: 1.9 (+)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0

On Thu, 12 Aug 2004, John Loughney wrote:

> If we scheduled the March meeting in New Orleans or Rio, maybe things would get interesting!

New Orleans sounds like a plausable option...

>
> John
>
> ________________ Reply Header ________________
> Subject:	Re: YATS? Re: T-shirts,
> 	and some suggestions for future ietf meetings
> Author:	"shogunx" <shogunx@sleekfreak.ath.cx>
> Date:		09th August 2004 5:21:34  PM
>
> On Tue, 10 Aug 2004, George Michaelson wrote:
>
> Personally, I find the requirement of wearing clothes tiresome, but then
> again, who REALLY wants to see all the IETF'ers naked?
>
> Enjoy,
> Scott
>
>
> >
> > Jon Crowcroft told us in UCL-CS back in '85 that the pre-IETF meetings were
> > smoke filled rooms, including uniforms with medal-bars out to the elbows...
> >
> > -George
> >
> > _______________________________________________
> > 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
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
>

sleekfreak pirate broadcast
http://sleekfreak.ath.cx:81/


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


From ietf-bounces@ietf.org  Thu Aug 12 11:06:06 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07408;
	Thu, 12 Aug 2004 11:06:06 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BvHEb-0005dG-Cj; Thu, 12 Aug 2004 11:11:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BvH1h-0005oV-E8; Thu, 12 Aug 2004 10:57:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BvGuQ-0004C5-Ex
	for ietf@megatron.ietf.org; Thu, 12 Aug 2004 10:50:26 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06484
	for <ietf@ietf.org>; Thu, 12 Aug 2004 10:50:24 -0400 (EDT)
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BvGzP-0005Ib-5W
	for ietf@ietf.org; Thu, 12 Aug 2004 10:55:35 -0400
Received: from sj-core-3.cisco.com (171.68.223.137)
	by sj-iport-5.cisco.com with ESMTP; 12 Aug 2004 07:51:37 -0700
X-BrightmailFiltered: true
Received: from mira-sjc5-d.cisco.com (IDENT:mirapoint@mira-sjc5-d.cisco.com
	[171.71.163.28])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id i7CEnqpp015094;
	Thu, 12 Aug 2004 07:49:53 -0700 (PDT)
Received: from [192.168.100.32] (sjc-vpn4-458.cisco.com [10.21.81.202])
	by mira-sjc5-d.cisco.com (MOS 3.4.6-GR) with ESMTP id ADU43791;
	Thu, 12 Aug 2004 07:49:52 -0700 (PDT)
In-Reply-To: <Pine.LNX.4.44.0408121539030.1209-100000@netcore.fi>
References: <Pine.LNX.4.44.0408121539030.1209-100000@netcore.fi>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <DB083F50-EC6E-11D8-AAFC-000A95C73842@cisco.com>
Content-Transfer-Encoding: 7bit
From: David R Oran <oran@cisco.com>
Date: Thu, 12 Aug 2004 10:49:47 -0400
To: Pekka Savola <pekkas@netcore.fi>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: hop-by-hop and router alert options [Re: Question about use of
	RSVP in Production Networks]
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-Score: 0.0 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
Content-Transfer-Encoding: 7bit

> I question the usefulness of path-coupled signalling beyond a certain
> point in the network.  Dean Anderson voiced them pretty well in the
> original thread about RSVP -- it just doesn't seem to make any sense
> beyond a very closed environment (like the first hop) -- and in that
> case, you should be able to use another kind of signalling as well.
>
> If we don't learn anything of the mistakes we did with RSVP, we're
> bound to repeat them.
>
First, we have to agree on what the mistakes were :-)

> For example, has the design clearly restricted itself to the first or
> the last hop, or within the first couple of hops?
>
No. Here's one counter-argument. Enterprise networks tend to have 
dumb-bell topologies, where the bottleneck links are in the interior 
rather than at the edges (exactly the opposite of serivce provider 
networks). They have meshes of 100meg+ all over each site, but the 
sites are interconnected with some service (like MPLS VPN, frame relay, 
etc.) which is expensive and often with very limited bandwidth 
(sometimes sub-T1). These links are not necessarily all that easy to 
identify in the topology, because for reliability enterprises configure 
mulitple routers and backup links. There is strong demand for 
flow-granularity admission control on such links, and an end-to-end 
model works better because site-to-site flows can swamp both the uplink 
at one end and the downlink at the other end.

There are other useful examples which I can share if people are 
interested.

> For that purpose, I'm not 100% sure if you would need a path-coupled
> signalling.  You'll certainly want path-coupled signalling for
> signalling with a much wider "span" (because it's the simplest way to
> do it from the host's perspective), but I'm arguing (as Dean was) that
> this isn't an interesting approach from the network operators'
> perspective.
>
What about discovery of the furthest point. Do you not find that a 
persuasive use case?

> ...
>
> As for the alternatives:
>  1) for first-hop only, there's really little need for a router alert,
> any protocol would do, as you already know who your routers are :-)
>  2) for hops beyond the first-hop router, I'd consider setting up a
> single server which would be responsible for brokering the QoS
> capabilities, firewall holes, etc. You contact the server, and ask it
> to open a certain kind of hole, set up certain QoS between (source,
> destination), etc.  There are a number of options how you could
> discover this kind of system:
>     a) a DHCP option
>     b) a DNS lookup (e.g., SRV record based on your DNS search path)
>     c) asking the upstream router using protocol learned in 1).
>
This assume edge tree topologies, which are common but hardly 
ubiquitous.

> These kind of approaches essentially move the intelligence and
> processing to specific nodes who are better capable of handling such
> requests, having policy who can request what, removing the processing
> and cruft from the routers.  And the hosts have have much easier time
> figuring out whether requesting these capabilities is supported in the
> network, instead of spewing a considerable amount of in-band
> signalling attempts to the network.
This is hardly a neutral characterization of the tradeoffs.

Cheers, Dave.

> -- 
> 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
> _______________________________________________
> 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).
>
David R. Oran
Cisco Fellow
Cisco Systems
7 Ladyslipper Lane
Acton, MA 01720 USA
Tel: +1 978 264 2048
Email: oran@cisco.com


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


From ietf-bounces@ietf.org  Thu Aug 12 11:28:37 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08859;
	Thu, 12 Aug 2004 11:28:37 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BvHaN-00063w-GF; Thu, 12 Aug 2004 11:33:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BvHRG-0003B5-FQ; Thu, 12 Aug 2004 11:24:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BvHMR-0002Ma-TH
	for ietf@megatron.ietf.org; Thu, 12 Aug 2004 11:19:23 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08503
	for <ietf@ietf.org>; Thu, 12 Aug 2004 11:19:21 -0400 (EDT)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BvHRP-0005vP-UX
	for ietf@ietf.org; Thu, 12 Aug 2004 11:24:33 -0400
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-2.cisco.com with ESMTP; 12 Aug 2004 08:21:23 -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 i7CFInjd014227;
	Thu, 12 Aug 2004 08:18:50 -0700 (PDT)
Received: from cisco.com ([10.25.65.179])
	by mira-sjc5-c.cisco.com (MOS 3.4.5-GR) with SMTP id AXZ01304;
	Thu, 12 Aug 2004 08:18:48 -0700 (PDT)
Date: Thu, 12 Aug 2004 11:18:28 -0400
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v553)
To: David R Oran <oran@cisco.com>
From: Melinda Shore <mshore@cisco.com>
In-Reply-To: <DB083F50-EC6E-11D8-AAFC-000A95C73842@cisco.com>
Message-Id: <DCB31D22-EC72-11D8-923B-000A95E35274@cisco.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.553)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: hop-by-hop and router alert options [Re: Question about use of
	RSVP in Production Networks]
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-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: 7bit

On Thursday, August 12, 2004, at 10:49 AM, David R Oran wrote:
> What about discovery of the furthest point. Do you not find that a 
> persuasive use case?

There are actually a number of instances in which some kind of topology
exposure is necessary for some widely-used functions to work properly.
Certainly things like being able to discover the furthest tunnel 
endpoint
is a good example, but also things like being able to present the 
correct
address in a QoS or firewall pinholing (or, indeed, any kind of filter
description) request when there are NATs present.  Note that in this 
case
the topology information isn't presented to endpoints, but only needs to
be correct hop-by-hop (between nodes).

Melinda


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


From ietf-bounces@ietf.org  Thu Aug 12 13:32:52 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17731;
	Thu, 12 Aug 2004 13:32:52 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BvJWd-0000Hk-Ie; Thu, 12 Aug 2004 13:38:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BvJ7K-0004AO-6d; Thu, 12 Aug 2004 13:11:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BvIuM-0000Az-2Z
	for ietf@megatron.ietf.org; Thu, 12 Aug 2004 12:58:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15142
	for <ietf@ietf.org>; Thu, 12 Aug 2004 12:58:27 -0400 (EDT)
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BvIzL-0007vY-Rs
	for ietf@ietf.org; Thu, 12 Aug 2004 13:03:40 -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 i7CGvQJ10923;
	Thu, 12 Aug 2004 09:57:26 -0700 (PDT)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost) by gra.isi.edu (8.9.3/8.8.6) id JAA05868;
	Thu, 12 Aug 2004 09:57:26 -0700 (PDT)
Date: Thu, 12 Aug 2004 09:57:26 -0700 (PDT)
Message-Id: <200408121657.JAA05868@gra.isi.edu>
To: ietf@ietf.org, pekkas@netcore.fi
X-Sun-Charset: US-ASCII
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: braden@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: braden@ISI.EDU
Subject: Re: hop-by-hop and router alert options [Re: Question about use of
 RSVP in Production Networks]
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-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb

  *> As for the alternatives:
  *>  1) for first-hop only, there's really little need for a router alert, 
  *> any protocol would do, as you already know who your routers are :-)
  *>  2) for hops beyond the first-hop router, I'd consider setting up a 
  *> single server which would be responsible for brokering the QoS 
  *> capabilities, firewall holes, etc. You contact the server, and ask it 
  *> to open a certain kind of hole, set up certain QoS between (source, 
  *> destination), etc.  There are a number of options how you could 
  *> discover this kind of system:
  *>     a) a DHCP option
  *>     b) a DNS lookup (e.g., SRV record based on your DNS search path)
  *>     c) asking the upstream router using protocol learned in 1).
  *> 
  *> These kind of approaches essentially move the intelligence and
  *> processing to specific nodes who are better capable of handling such
  *> requests, having policy who can request what, removing the processing
  *> and cruft from the routers.  And the hosts have have much easier time
  *> figuring out whether requesting these capabilities is supported in the
  *> network, instead of spewing a considerable amount of in-band
  *> signalling attempts to the network.
  *> 


Pekka,

You are far from defining an alternative architecture here, but it
seems to me that you are generally depending upon (manual)
configuration to provide path information, rather than directly (and
simply) discovering it.  Your suggestion seems to be that "Trust the
ISPs to configure it all correctly."  Down that path lies disaster,
IMHO.  Path-coupled signaling provides auto-configuration of path
information, and that seems like it's worth the cost in much of the
network.

Bob Braden


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


From ietf-bounces@ietf.org  Thu Aug 12 15:42:50 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26715;
	Thu, 12 Aug 2004 15:42:50 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BvLYR-0002gM-0o; Thu, 12 Aug 2004 15:48:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BvLOW-00041U-U9; Thu, 12 Aug 2004 15:37:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BvLDs-0007Ss-4s
	for ietf@megatron.ietf.org; Thu, 12 Aug 2004 15:26:48 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25643
	for <ietf@ietf.org>; Thu, 12 Aug 2004 15:26:46 -0400 (EDT)
Message-Id: <200408121926.PAA25643@ietf.org>
Received: from bdsl.66.15.163.216.gte.net ([66.15.163.216] helo=tndh.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BvLIr-0002Rd-W6
	for ietf@ietf.org; Thu, 12 Aug 2004 15:31:59 -0400
Received: from eaglet (127.0.0.1:4064)
	by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server]
	id <S6530B> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 12 Aug 2004 12:23:09 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Michael Richardson'" <mcr@sandelman.ottawa.on.ca>, <gwz@cisco.com>,
        <ietf@ietf.org>
Date: Thu, 12 Aug 2004 12:26:38 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
In-Reply-To: <25803.1092157058@marajade.sandelman.ottawa.on.ca>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Thread-Index: AcR+/7ROxHrsRDotTDObAuHheKfCqABoQm6Q
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Content-Transfer-Encoding: 7bit
Subject: RE: T-shirts, and some suggestions for future 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-Score: 0.8 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: 7bit

Michael Richardson wrote:
>  ...
>   I recall Orlando had no convenient bar.
> 

Maybe you spent too much time there to recall ... ;)

As the hosts of Orlando, Glen & I can assure you the hotel bar was within
stumbling distance (Ethernet cable limits) of both the meeting and guest
rooms because one of the goals was to have fledgling pre-standard 802.11
access in the bar. The biggest problem with the bar in Orlando was the
manager's refusal to believe that the IETF would drink as much high quality
beer as he could buy. Maybe your recollection of convenience is due to their
running out of good beer by Tuesday.

Tony



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


From ietf-bounces@ietf.org  Thu Aug 12 17:25:02 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09176;
	Thu, 12 Aug 2004 17:25:02 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BvN9K-00074I-SF; Thu, 12 Aug 2004 17:30:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BvN2Q-0001t9-QZ; Thu, 12 Aug 2004 17:23:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BvMof-0004eL-A4
	for ietf@megatron.ietf.org; Thu, 12 Aug 2004 17:08:53 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA08107
	for <ietf@ietf.org>; Thu, 12 Aug 2004 17:08:51 -0400 (EDT)
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BvMtg-0006iX-Tl
	for ietf@ietf.org; Thu, 12 Aug 2004 17:14:05 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i7CL87d10969;
	Fri, 13 Aug 2004 00:08:07 +0300
Date: Fri, 13 Aug 2004 00:08:07 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Bob Braden <braden@ISI.EDU>
In-Reply-To: <200408121657.JAA05868@gra.isi.edu>
Message-ID: <Pine.LNX.4.44.0408122348001.10008-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Cc: ietf@ietf.org
Subject: Re: hop-by-hop and router alert options [Re: Question about use of
 RSVP in Production Networks]
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-Score: 0.0 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8

Inline,

On Thu, 12 Aug 2004, Bob Braden wrote:
>   *> As for the alternatives:
>   *>  1) for first-hop only, there's really little need for a router alert, 
>   *> any protocol would do, as you already know who your routers are :-)
>   *>  2) for hops beyond the first-hop router, I'd consider setting up a 
>   *> single server which would be responsible for brokering the QoS 
>   *> capabilities, firewall holes, etc. You contact the server, and ask it 
>   *> to open a certain kind of hole, set up certain QoS between (source, 
>   *> destination), etc.  There are a number of options how you could 
>   *> discover this kind of system:
>   *>     a) a DHCP option
>   *>     b) a DNS lookup (e.g., SRV record based on your DNS search path)
>   *>     c) asking the upstream router using protocol learned in 1).
>   *> 
>   *> These kind of approaches essentially move the intelligence and
>   *> processing to specific nodes who are better capable of handling such
>   *> requests, having policy who can request what, removing the processing
>   *> and cruft from the routers.  And the hosts have have much easier time
>   *> figuring out whether requesting these capabilities is supported in the
>   *> network, instead of spewing a considerable amount of in-band
>   *> signalling attempts to the network.
>   *> 
> 
> You are far from defining an alternative architecture here, but it
> seems to me that you are generally depending upon (manual)
> configuration to provide path information, rather than directly (and
> simply) discovering it.  Your suggestion seems to be that "Trust the
> ISPs to configure it all correctly."  Down that path lies disaster,
> IMHO.  Path-coupled signaling provides auto-configuration of path
> information, and that seems like it's worth the cost in much of the
> network.

Not at all; maybe my three paragraphs weren't enough ;-).

My first assumption is that the enterprise or the ISP who is willing
to provide increased QoS etc. will explicitly set up their routers or
systems in more general to allow this.  It won't be allowed by default
 -- doing so would be an obvious disaster.  Operators just *DON'T*
want the users or their computers to automatically adjust the routers'
behaviours, traffic quotas, etc. -- if they allow this, they want to
do it explicitly.

Now, if we already have an assumption that the network must have some
configuration components, it seems acceptable to consider moving the
policy information and the rest of the intelligence to one single box
in the network, instead of having to distribute and process it on
every router ("allow every router's traffic priorization be configured
directly by the requests of the users" -- doesn't that sound scary?).

The user could discover the address of that box automatically, using
e.g., the mechanisms outlined above.  If it can't find the box, then
it would assume no QoS etc. is provided, and would not do any further
attempts while it is in that network.

If it can find the box, it could signal which QoS metrics it wants, on
which paths (from source S to destination D), etc.  Then the box uses
some policy database (similar as the routers have) to figure out
whether to grant that (or not), and would configure the routers
appropriately (figuring out what the path between Source,Destination
pair is should be trivial based on a copy of routing data).

This seems to give the same functionality as path-coupled signalling
without the drawbacks of path-coupled signalling.  It requires one
additional box which the users can try to reach, and which the
operator configures to be allowed to configure the routers b/w quotas
etc. appropriately.

Let's not reinvent RSVP.  Pretty please.  RSVP for user-network
signalling (RSVP-TE may be slightly different) isn't going unused
because it was only slightly too complex, and it needs a modern touch
and be reborn as a NSIS product; the approach is just fundamentally
unacceptable for networks and operators.

All of this is spoken with an operator (an NREN) hat on, if it
matters.

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




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


From ietf-bounces@ietf.org  Thu Aug 12 17:30:14 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09475;
	Thu, 12 Aug 2004 17:30:14 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BvNEP-0007AX-Ky; Thu, 12 Aug 2004 17:35:29 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BvN3j-0002K6-1p; Thu, 12 Aug 2004 17:24:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BvMyN-0006Yd-PF; Thu, 12 Aug 2004 17:18:55 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA08712;
	Thu, 12 Aug 2004 17:18:53 -0400 (EDT)
Received: from ckmso1.att.com ([12.20.58.69] helo=ckmso1.proxy.att.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BvN3M-0006tk-T9; Thu, 12 Aug 2004 17:24:08 -0400
Received: from maillennium.att.com ([135.25.114.99])
	by ckmso1.proxy.att.com (AT&T IPNS/MSO-5.5) with ESMTP id
	i7CLILaU009243; Thu, 12 Aug 2004 17:18:21 -0400
Received: from [135.91.110.75] (thansen-n.mt.att.com[135.91.110.75](untrusted
	sender)) by maillennium.att.com (mailgw1) with ESMTP
	id <20040812211833gw1002ev0ie> (Authid: tony);
	Thu, 12 Aug 2004 21:18:33 +0000
Message-ID: <411BDE9B.7090706@att.com>
Date: Thu, 12 Aug 2004 17:18:19 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: iesg@ietf.org, ietf@ietf.org, ietf-822@imc.org, ehall@ntrg.com
References: <p06110437bd3d5d396de1@[10.20.30.249]> <411AB496.8080307@erols.com>
In-Reply-To: <411AB496.8080307@erols.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 7bit
Subject: Re: Last Call: 'The APPLICATION/MBOX Media-Type' to Proposed
	Standard
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: 7bit

The information about the mbox format being anecdotally defined is 
incorrect. The mbox format has traditionally been documented in the 
binmail(1) or mail.local(8) man pages (BSD UNIX derivatives) or mail(1) 
man page (UNIX System 3/5/III/V derivatives). There have been several 
variants of the mbox format in use by those different systems. The most 
complete description of an mbox format can be seen in the man page from 
any UNIX System Vr4 derived system, such as Solaris.

The description found in http://qmail.org./man/man5/mbox.html, referred 
to at the end of Appendix A, does cover these variations fairly 
succinctly. However Appendix A doesn't cover the variations properly.

	Tony Hansen
	tony@att.com

The IESG wrote:

> The IESG has received a request from an individual submitter to
> consider the following document:
>
>- 'The APPLICATION/MBOX Media-Type '
>   <draft-hall-mime-app-mbox-02.txt> as a Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send any comments to the 
> iesg@ietf.org or ietf@ietf.org mailing lists by 2004-09-06.
>
> The file can be obtained via
> http://www.ietf.org/internet-drafts/draft-hall-mime-app-mbox-02.txt


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


From ietf-bounces@ietf.org  Thu Aug 12 17:34:34 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09760;
	Thu, 12 Aug 2004 17:34:34 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BvNIb-0007HQ-AW; Thu, 12 Aug 2004 17:39:49 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BvN7Z-0003Tc-Dz; Thu, 12 Aug 2004 17:28:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BvN2Z-00023C-DF
	for ietf@megatron.ietf.org; Thu, 12 Aug 2004 17:23:15 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09050
	for <ietf@ietf.org>; Thu, 12 Aug 2004 17:23:13 -0400 (EDT)
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BvN7b-00071E-Cb
	for ietf@ietf.org; Thu, 12 Aug 2004 17:28:28 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i7CLL0P11154;
	Fri, 13 Aug 2004 00:21:00 +0300
Date: Fri, 13 Aug 2004 00:21:00 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: David R Oran <oran@cisco.com>
In-Reply-To: <DB083F50-EC6E-11D8-AAFC-000A95C73842@cisco.com>
Message-ID: <Pine.LNX.4.44.0408130008110.10008-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
Cc: ietf@ietf.org
Subject: Re: hop-by-hop and router alert options [Re: Question about use of
 RSVP in Production Networks]
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-Score: 0.0 (/)
X-Scan-Signature: 2857c5c041d6c02d7181d602c22822c8

Inline..

On Thu, 12 Aug 2004, David R Oran wrote:
> > I question the usefulness of path-coupled signalling beyond a certain
> > point in the network.  Dean Anderson voiced them pretty well in the
> > original thread about RSVP -- it just doesn't seem to make any sense
> > beyond a very closed environment (like the first hop) -- and in that
> > case, you should be able to use another kind of signalling as well.
> >
> > If we don't learn anything of the mistakes we did with RSVP, we're
> > bound to repeat them.
>
> First, we have to agree on what the mistakes were :-)

Of course.  Then why this wasn't the first thing NSIS did after going
for on-path signalling, or didn't I just manage to find it?  

I really really hope that there has been a problem statement...

> > For example, has the design clearly restricted itself to the first or
> > the last hop, or within the first couple of hops?
>
> No. Here's one counter-argument. Enterprise networks tend to have 
> dumb-bell topologies, where the bottleneck links are in the interior 
> rather than at the edges (exactly the opposite of serivce provider 
> networks). They have meshes of 100meg+ all over each site, but the 
> sites are interconnected with some service (like MPLS VPN, frame relay, 
> etc.) which is expensive and often with very limited bandwidth 
> (sometimes sub-T1). These links are not necessarily all that easy to 
> identify in the topology, because for reliability enterprises configure 
> mulitple routers and backup links. There is strong demand for 
> flow-granularity admission control on such links, and an end-to-end 
> model works better because site-to-site flows can swamp both the uplink 
> at one end and the downlink at the other end.
> 
> There are other useful examples which I can share if people are 
> interested.

Agreed, this seems like a possible use case; but again, this is within
a site, and the congestion points can be well-defined.  If it's not
the first hop, then it's a predetermined point (or points) in the
network.  Hardly something you absolutely need on-path signalling for.
 
> > For that purpose, I'm not 100% sure if you would need a path-coupled
> > signalling.  You'll certainly want path-coupled signalling for
> > signalling with a much wider "span" (because it's the simplest way to
> > do it from the host's perspective), but I'm arguing (as Dean was) that
> > this isn't an interesting approach from the network operators'
> > perspective.
>
> What about discovery of the furthest point. Do you not find that a 
> persuasive use case?

Further point where you can use path-coupled signalling, you mean?  
Not really, as there seems to be something seriously broken if you
need set up priorization except in well-defined points in the network.  
And to achieve that, you could use a "bandwidth broker": either it's
able to set up the required bandwidth (it's in the same site, or at a
site your site has a roaming agreement with), or it isn't and the
approach is going to fail in any case, because the sites out in the
Internet don't want outsiders to request bandwidth allocations.

> > As for the alternatives:
> >  1) for first-hop only, there's really little need for a router alert,
> > any protocol would do, as you already know who your routers are :-)
> >  2) for hops beyond the first-hop router, I'd consider setting up a
> > single server which would be responsible for brokering the QoS
> > capabilities, firewall holes, etc. You contact the server, and ask it
> > to open a certain kind of hole, set up certain QoS between (source,
> > destination), etc.  There are a number of options how you could
> > discover this kind of system:
> >     a) a DHCP option
> >     b) a DNS lookup (e.g., SRV record based on your DNS search path)
> >     c) asking the upstream router using protocol learned in 1).
>
> This assume edge tree topologies, which are common but hardly 
> ubiquitous.

I don't think I assumed edge tree topologies.  Please elaborate.
 
> > These kind of approaches essentially move the intelligence and
> > processing to specific nodes who are better capable of handling such
> > requests, having policy who can request what, removing the processing
> > and cruft from the routers.  And the hosts have have much easier time
> > figuring out whether requesting these capabilities is supported in the
> > network, instead of spewing a considerable amount of in-band
> > signalling attempts to the network.
>
> This is hardly a neutral characterization of the tradeoffs.

(warning, could be flammatory)

True enough, I had my operator hat on ;-).  My mind just boggled when
I started to realize that some part of the IETF is still in denial on
why RSVP didn't go through, and is now in the process of reinventing
it .. wasting a lot of time and effort that could be much better spent
on making an operationally more feasible system to provide these
reservations in a well-defined, constrained points of the network.

What I can't figure why this is happening.  I guess the IESG must have
been asleep, or the most people just thought, "well.. let them waste
their energy on that.. at least they don't bother us while they are
bashing the heads in the wall.."

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


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


From ietf-bounces@ietf.org  Thu Aug 12 18:35:34 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14067;
	Thu, 12 Aug 2004 18:35:34 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BvOFc-0008NE-WD; Thu, 12 Aug 2004 18:40:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BvO8d-0000jB-IM; Thu, 12 Aug 2004 18:33:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BvO7K-0000TX-1w; Thu, 12 Aug 2004 18:32:14 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13861;
	Thu, 12 Aug 2004 18:32:11 -0400 (EDT)
Received: from goose.ehsco.com ([207.65.203.98])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BvOCL-0008JC-Rk; Thu, 12 Aug 2004 18:37:27 -0400
Received: from [192.168.0.2] (cable0-stm-219.gmpexpress.net [63.147.50.219])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client did not present a certificate)
	by goose.ehsco.com (Postfix ) with ESMTP id 3492261640;
	Thu, 12 Aug 2004 17:32:04 -0500 (CDT)
Message-ID: <411BEFB1.1040808@ehsco.com>
Date: Thu, 12 Aug 2004 18:31:13 -0400
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7) Gecko/20040616
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Tony Hansen <tony@att.com>
References: <p06110437bd3d5d396de1@[10.20.30.249]>
	<411AB496.8080307@erols.com> <411BDE9B.7090706@att.com>
In-Reply-To: <411BDE9B.7090706@att.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Content-Transfer-Encoding: 7bit
Cc: ietf-822@imc.org, ehall@ntrg.com, iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: 'The APPLICATION/MBOX Media-Type' to Proposed
	Standard
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: 7bit


On 8/12/2004 5:18 PM, Tony Hansen wrote:

> The information about the mbox format being anecdotally defined is 
> incorrect. The mbox format has traditionally been documented in the 
> binmail(1) or mail.local(8) man pages (BSD UNIX derivatives) or mail(1)
>  man page (UNIX System 3/5/III/V derivatives).

I checked each of those and none of them seem to adequately describe the
message or database format.

> The most complete description of an mbox format can be seen in the man
> page from any UNIX System Vr4 derived system, such as Solaris.
>
> The description found in http://qmail.org./man/man5/mbox.html, referred
> to at the end of Appendix A, does cover these variations fairly 
> succinctly. However Appendix A doesn't cover the variations properly.

Do you have a specific URL to a specific man page that you think would be
appropriate and authoritative?

I spent a while looking (see also http://makeashorterlink.com/?X61D16909
for example), and couldn't find anything that seemed to be authoritative
enough to reference.

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

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


From ietf-bounces@ietf.org  Thu Aug 12 19:09:30 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16141;
	Thu, 12 Aug 2004 19:09:30 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BvOmU-0000dJ-Io; Thu, 12 Aug 2004 19:14:46 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BvOch-000770-RX; Thu, 12 Aug 2004 19:04:39 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BvOYq-0006CU-4D
	for ietf@megatron.ietf.org; Thu, 12 Aug 2004 19:00:40 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15610
	for <ietf@ietf.org>; Thu, 12 Aug 2004 19:00:37 -0400 (EDT)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BvOds-0000Qs-Vu
	for ietf@ietf.org; Thu, 12 Aug 2004 19:05:53 -0400
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-3.cisco.com with ESMTP; 12 Aug 2004 16:04:16 +0000
X-BrightmailFiltered: true
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i7CM05Mx016388;
	Thu, 12 Aug 2004 15:00:05 -0700 (PDT)
Received: from jmpolk-w2k01.diablo.cisco.com (ssh-sjc-1.cisco.com
	[171.68.225.134]) by wells.cisco.com (8.8.6
	(PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id QAA29754;
	Thu, 12 Aug 2004 16:00:05 -0700 (PDT)
Message-Id: <4.3.2.7.2.20040812175058.0303df00@localhost>
X-Sender: jmpolk@localhost
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 12 Aug 2004 18:00:50 -0500
To: Pekka Savola <pekkas@netcore.fi>
From: "James M. Polk" <jmpolk@cisco.com>
In-Reply-To: <Pine.LNX.4.44.0408130008110.10008-100000@netcore.fi>
References: <DB083F50-EC6E-11D8-AAFC-000A95C73842@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 2.3 (++)
X-Scan-Signature: f49c97ce49302a02285a2d36a99eef8c
Cc: ietf@ietf.org
Subject: Re: hop-by-hop and router alert options [Re: Question about
 use of RSVP in Production Networks]
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-Score: 2.3 (++)
X-Scan-Signature: 42e3ed3f10a1d8bef690f09da16f507a

Pekka

While it is clear your distaste for RSVP, you haven't stated anything other 
than handwave why RSVP is so bad ("in the first place"). You mention there 
were mistakes and a BB will fix them, but you don't list a set of mistakes 
RSVP made for folks to digest. I don't know if you think they are so 
obvious you don't have to state them or you don't want to list them for 
whatever reason.

Humor me (and a few others here) with a few listed mistakes you believe 
RSVP made in its design, with how you would redo them (either with a BB or 
just a better RSVP design).

Without this, you are just ranting without substance to me - as I cannot 
glean anything real from your messages other than your distaste of RSVP in 
favor of a Bandwidth Broker...

At 12:21 AM 8/13/2004 +0300, Pekka Savola wrote:
>Inline..
>
>On Thu, 12 Aug 2004, David R Oran wrote:
> > > I question the usefulness of path-coupled signalling beyond a certain
> > > point in the network.  Dean Anderson voiced them pretty well in the
> > > original thread about RSVP -- it just doesn't seem to make any sense
> > > beyond a very closed environment (like the first hop) -- and in that
> > > case, you should be able to use another kind of signalling as well.
> > >
> > > If we don't learn anything of the mistakes we did with RSVP, we're
> > > bound to repeat them.
> >
> > First, we have to agree on what the mistakes were :-)
>
>Of course.  Then why this wasn't the first thing NSIS did after going
>for on-path signalling, or didn't I just manage to find it?
>
>I really really hope that there has been a problem statement...
>
> > > For example, has the design clearly restricted itself to the first or
> > > the last hop, or within the first couple of hops?
> >
> > No. Here's one counter-argument. Enterprise networks tend to have
> > dumb-bell topologies, where the bottleneck links are in the interior
> > rather than at the edges (exactly the opposite of serivce provider
> > networks). They have meshes of 100meg+ all over each site, but the
> > sites are interconnected with some service (like MPLS VPN, frame relay,
> > etc.) which is expensive and often with very limited bandwidth
> > (sometimes sub-T1). These links are not necessarily all that easy to
> > identify in the topology, because for reliability enterprises configure
> > mulitple routers and backup links. There is strong demand for
> > flow-granularity admission control on such links, and an end-to-end
> > model works better because site-to-site flows can swamp both the uplink
> > at one end and the downlink at the other end.
> >
> > There are other useful examples which I can share if people are
> > interested.
>
>Agreed, this seems like a possible use case; but again, this is within
>a site, and the congestion points can be well-defined.  If it's not
>the first hop, then it's a predetermined point (or points) in the
>network.  Hardly something you absolutely need on-path signalling for.
>
> > > For that purpose, I'm not 100% sure if you would need a path-coupled
> > > signalling.  You'll certainly want path-coupled signalling for
> > > signalling with a much wider "span" (because it's the simplest way to
> > > do it from the host's perspective), but I'm arguing (as Dean was) that
> > > this isn't an interesting approach from the network operators'
> > > perspective.
> >
> > What about discovery of the furthest point. Do you not find that a
> > persuasive use case?
>
>Further point where you can use path-coupled signalling, you mean?
>Not really, as there seems to be something seriously broken if you
>need set up priorization except in well-defined points in the network.
>And to achieve that, you could use a "bandwidth broker": either it's
>able to set up the required bandwidth (it's in the same site, or at a
>site your site has a roaming agreement with), or it isn't and the
>approach is going to fail in any case, because the sites out in the
>Internet don't want outsiders to request bandwidth allocations.
>
> > > As for the alternatives:
> > >  1) for first-hop only, there's really little need for a router alert,
> > > any protocol would do, as you already know who your routers are :-)
> > >  2) for hops beyond the first-hop router, I'd consider setting up a
> > > single server which would be responsible for brokering the QoS
> > > capabilities, firewall holes, etc. You contact the server, and ask it
> > > to open a certain kind of hole, set up certain QoS between (source,
> > > destination), etc.  There are a number of options how you could
> > > discover this kind of system:
> > >     a) a DHCP option
> > >     b) a DNS lookup (e.g., SRV record based on your DNS search path)
> > >     c) asking the upstream router using protocol learned in 1).
> >
> > This assume edge tree topologies, which are common but hardly
> > ubiquitous.
>
>I don't think I assumed edge tree topologies.  Please elaborate.
>
> > > These kind of approaches essentially move the intelligence and
> > > processing to specific nodes who are better capable of handling such
> > > requests, having policy who can request what, removing the processing
> > > and cruft from the routers.  And the hosts have have much easier time
> > > figuring out whether requesting these capabilities is supported in the
> > > network, instead of spewing a considerable amount of in-band
> > > signalling attempts to the network.
> >
> > This is hardly a neutral characterization of the tradeoffs.
>
>(warning, could be flammatory)
>
>True enough, I had my operator hat on ;-).  My mind just boggled when
>I started to realize that some part of the IETF is still in denial on
>why RSVP didn't go through, and is now in the process of reinventing
>it .. wasting a lot of time and effort that could be much better spent
>on making an operationally more feasible system to provide these
>reservations in a well-defined, constrained points of the network.
>
>What I can't figure why this is happening.  I guess the IESG must have
>been asleep, or the most people just thought, "well.. let them waste
>their energy on that.. at least they don't bother us while they are
>bashing the heads in the wall.."
>
>--
>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


cheers,
James

                                *******************
                 Truth is not to be argued... it is to be presented


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


From ietf-bounces@ietf.org  Thu Aug 12 19:20:27 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16797;
	Thu, 12 Aug 2004 19:20:27 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BvOx6-0000pd-1F; Thu, 12 Aug 2004 19:25:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BvOn4-0001Fu-9K; Thu, 12 Aug 2004 19:15:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BvOke-0000G6-S4; Thu, 12 Aug 2004 19:12:52 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16389;
	Thu, 12 Aug 2004 19:12:49 -0400 (EDT)
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BvOpg-0000hN-IU; Thu, 12 Aug 2004 19:18:06 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.13.1/8.13.1) id i7CNCIMl096363 env-from
	<vjs>; Thu, 12 Aug 2004 17:12:18 -0600 (MDT)
Date: Thu, 12 Aug 2004 17:12:18 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200408122312.i7CNCIMl096363@calcite.rhyolite.com>
To: iesg@ietf.org, ietf@ietf.org
References: <411BEFB1.1040808@ehsco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Subject: Re: Last Call: 'The APPLICATION/MBOX Media-Type' to Proposed
	Standard
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793

> From: "Eric A. Hall" <ehall@ehsco.com>
> To: Tony Hansen <tony@att.com>

> > The information about the mbox format being anecdotally defined is 
> > incorrect. The mbox format has traditionally been documented in the 
> > binmail(1) or mail.local(8) man pages (BSD UNIX derivatives) or mail(1)
> >  man page (UNIX System 3/5/III/V derivatives).
>
> I checked each of those and none of them seem to adequately describe the
> message or database format.


> Do you have a specific URL to a specific man page that you think would be
> appropriate and authoritative?

There are plenty of man pages and documentation for UNIX mbox formats.
Outfits such as Netscape have figured the stuff out (painfully simple
as it is) to make libraries to deal with local mailboxes.

However, that seems irrelevant unless an auuthority ceeds change control
for the UNIX mbox format to the IETF.  Never mind that the notion of
an authority that could exercise any authority over any UNIX mbox
format other than in its own source trees would be crazy.  There's no
law that says Dragonfly, NetBSD, FreeBSD, OpenBSD, Linux, IRIX, HP/UX,
AIX, etc. and so forth and so on must have a common mbox format or
that they cannot switch to something better, not withstanding things
like that Netscape library.  The old mbox formats are fine for a VAX-750
or 3B2, but are very bad ideas for more than a few hundred messages.

The most you could do is define your own interchange mbox format that
would by coincidence be extremely similar to one format such as the
System V or 4.3 BSD (I think I recall small differences between those
two), and tell implementors of your MIME type to convert into and out
of your format.

There is an overriding question.  Where is the market demand for
an IETF standards track RFC defining a UNIX mbox interchange type?
Who would use it?  
I can imagine "importing" and "exporting" mboxes, but not via SMTP.
Is anyone thinking about new code to convert among Netscape, Exchange,
and UNIX mbox mailboxes?  Doesn't enough of that code already exist,
and doesn't all of it use transport mechanisms other than SMTP?

Isn't the IETF supposed to be about on-the-wire bits and keep its
noses out of host data structures?


Vernon Schryver    vjs@rhyolite.com

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


From ietf-bounces@ietf.org  Thu Aug 12 20:13:33 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA19114;
	Thu, 12 Aug 2004 20:13:33 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BvPmT-0001dG-0H; Thu, 12 Aug 2004 20:18:49 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BvPf7-0002Ao-Eg; Thu, 12 Aug 2004 20:11:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BvPeQ-00021J-Hs; Thu, 12 Aug 2004 20:10:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18991;
	Thu, 12 Aug 2004 20:10:29 -0400 (EDT)
Received: from smtp02.mrf.mail.rcn.net ([207.172.4.61])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BvPjT-0001aV-BF; Thu, 12 Aug 2004 20:15:44 -0400
X-Info: This message was accepted for relay by
	smtp02.mrf.mail.rcn.net as the sender used SMTP authentication
X-Trace: JkVYWWlaWB+ER4mwpsY3JSr71KNFRlxzPEKD9kJNrEU=
Received: from 65.105.220.34.ptr.us.xo.net ([65.105.220.34]
	helo=mail.blilly.com)
	by smtp02.mrf.mail.rcn.net with asmtp (Exim 3.35 #7)
	id 1BvPeF-0003TA-00; Thu, 12 Aug 2004 20:10:24 -0400
Received: from marty.blilly.com (localhost [127.0.0.1])
	by mail.blilly.com with ESMTP
	id i7D0AFL2009645(8.12.10/8.12.10/mail.blilly.com sendmail.mc.mail 1.18
	2004/05/15 07:23:45) ; Thu, 12 Aug 2004 20:10:16 -0400
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by marty.blilly.com with ESMTP
	id i7D0AEsm009643(8.12.10/8.12.10/blilly.com submit.mc 1.1 2003/08/26
	22:21:33) ; Thu, 12 Aug 2004 20:10:14 -0400
Message-ID: <411C06E5.1030405@erols.com>
Date: Thu, 12 Aug 2004 20:10:13 -0400
From: Bruce Lilly <blilly@erols.com>
Organization: Bruce Lilly
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616
X-Accept-Language: en-us
MIME-Version: 1.0
To: "Eric A. Hall" <ehall@ehsco.com>
References: <p06110437bd3d5d396de1@[10.20.30.249]>
	<411AB496.8080307@erols.com> <411BDE9B.7090706@att.com>
	<411BEFB1.1040808@ehsco.com>
In-Reply-To: <411BEFB1.1040808@ehsco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Content-Transfer-Encoding: 7bit
Cc: ietf-822@imc.org, ehall@ntrg.com, iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: 'The APPLICATION/MBOX Media-Type' to Proposed
	Standard
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: iesg@ietf.org, ietf@ietf.org, ietf-822@imc.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Content-Transfer-Encoding: 7bit

Eric A. Hall wrote:

> Do you have a specific URL to a specific man page that you think would be
> appropriate and authoritative?
> 
> I spent a while looking (see also http://makeashorterlink.com/?X61D16909
> for example), and couldn't find anything that seemed to be authoritative
> enough to reference.

The docs/formats.txt file in the UW IMAP distribution
ftp://ftp.cac.washington.edu/mail/imap.tar.Z
describes several variants, some of which are not addressed
by the Bernstein document.  It also discusses a number of
interoperability issues not covered in the captioned draft.

As noted by Mark Crispin in the messages at the URL which you
have provided, different software can have somewhat different
interpretations of separator lines.  The only hope of having
any semblance of interoperability in exchanging such mbox
files between systems is to include an adequate specification
of the *specific* separator format used in the *particular*
file being transported (and I have suggested a regular
expression as a possible means of communicating that specification
via a Content-Type field parameter).

And I agree with Kai Henningsen's statement about use of
application/octet-stream; if there is not provision for
sufficient information (e.g. via parameters) to account for
the interoperability issues, then there's no point in having
a separate application subtype for it -- just use octet-stream
and let the communicating parties thrash out the details
out-of-band.  Or better yet (as briefly noted in the draft)
just use multipart/digest with local-system translations at
each end.

There are some additional issues that should be considered
(and either resolved or documented as known technical
omissions):
1. It is possible that processing by some transport (especially
   gateway) software may alter content which is not protected
   by transport encoding (and quoted-printable encoding might
   be insufficient).  That includes adding or removing trailing
   whitespace, modification of lines beginning with "From ", etc.
2. It is at best unclear how various software which uses one of
   the mbox format variants handles some 8bit and binary content,
   and indeed even 7bit content in MIME messages.  In particular,
   any attempt to convert line endings to/from the on-the-wire
   RFC [2]822 CRLF ending is likely to result in problems. For
   an example of binary content, see
   http://users.erols.com/blilly/mparse/tm35
   Note that the issue is not limited to binary content; "line
   ending" only has meaning in text media (not application, audio,
   image, video, model) and attempts at transforming non-text
   content (not merely text line endings, but e.g. content that
   happens to have <CR><LF>From<SP> in application, audio, etc.
   media) may irreversibly corrupt the content.

My opinion is that none of the mbox variants can handle the above
issues adequately.  Multipart/digest avoids the message separator
problem by using separators which are required not to be present
within the body of the message text in question.  Rigid formats
such as used by mbox variants are guaranteed to conflict with
some content at some point.  Some of the mbox variants appear
to have resulted from attempts to deal with various aspects of
the above and similar issues; the local storage methods that
appear to have the best chance of avoiding all of the problems
are those that use message-per-file storage in RFC [2]822
format (i.e. no attempt to convert line endings or otherwise
fold, spindle or mutilate message content) -- of course those
aren't "mbox" formats.

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


From ietf-bounces@ietf.org  Thu Aug 12 21:43:45 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23079;
	Thu, 12 Aug 2004 21:43:45 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BvRBl-00030p-T2; Thu, 12 Aug 2004 21:49:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BvR4B-0000pl-UX; Thu, 12 Aug 2004 21:41:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BvR1N-0000MJ-Gt
	for ietf@megatron.ietf.org; Thu, 12 Aug 2004 21:38:17 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA22814
	for <ietf@ietf.org>; Thu, 12 Aug 2004 21:38:15 -0400 (EDT)
Received: from mail.hammerheadsystems.com ([12.108.173.98])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BvR6L-0002ts-In
	for ietf@ietf.org; Thu, 12 Aug 2004 21:43:32 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 12 Aug 2004 18:37:39 -0700
Message-ID: <2DAC9E7A4640234B85975565E5D83AE173056C@srvcaexg01.headquarters.hammerheadsystems.com>
Thread-Topic: hop-by-hop and router alert options [Re: Question about use of
	RSVP in Production Networks]
Thread-Index: AcSAtDT84nAGCdv1Q6SBKzifOrHdagAH+S1A
From: "Ping Pan" <ppan@hammerheadsystems.com>
To: "Pekka Savola" <pekkas@netcore.fi>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
Subject: RE: hop-by-hop and router alert options [Re: Question about use of
	RSVP in Production Networks]
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-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: quoted-printable

Pekka,

>=20
> I really really hope that there has been a problem statement...
>=20

Here is an old draft on RSVP issues:=20

http://www1.cs.columbia.edu/~pingpan/papers/draft-pan-nsis-rsvp-transpor
t-01.txt

> Further point where you can use path-coupled signalling, you mean? =20
> Not really, as there seems to be something seriously broken=20
> if you need set up priorization except in well-defined points=20
> in the network. =20
> And to achieve that, you could use a "bandwidth broker":=20
> either it's able to set up the required bandwidth (it's in=20
> the same site, or at a site your site has a roaming agreement=20
> with), or it isn't and the approach is going to fail in any=20
> case, because the sites out in the Internet don't want=20
> outsiders to request bandwidth allocations.
>

If someone has a BB, would you and your boss buy and deploy it? :-) You
will certainly get a lot of wasted code and effort, and make the day for
many researchers.

> What I can't figure why this is happening.  I guess the IESG=20
> must have been asleep, or the most people just thought,=20
> "well.. let them waste their energy on that.. at least they=20
> don't bother us while they are bashing the heads in the wall.."
>=20

One word of caution: never ask too much from any standard body, or any
sausage-making organizaion in that matter. If you have a desire for
something cool and money, either build it yourself, or ask for it from
vendors directly. :-)

2 cents,

- Ping

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


From ietf-bounces@ietf.org  Fri Aug 13 01:20:57 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA04632;
	Fri, 13 Aug 2004 01:20:56 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BvUZy-0006fS-J5; Fri, 13 Aug 2004 01:26:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BvUSC-0005bd-On; Fri, 13 Aug 2004 01:18:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BvUQK-0005Lu-Cn
	for ietf@megatron.ietf.org; Fri, 13 Aug 2004 01:16:16 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA04423
	for <ietf@ietf.org>; Fri, 13 Aug 2004 01:16:15 -0400 (EDT)
Received: from slb-smtpout-01.boeing.com ([130.76.64.48])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BvUVQ-0006ae-QW
	for ietf@ietf.org; Fri, 13 Aug 2004 01:21:33 -0400
Received: from slb-av-01.boeing.com ([129.172.13.4])
	by slb-smtpout-01.boeing.com (8.9.2.MG.10092003/8.8.5-M2) with ESMTP id
	WAA03910; Thu, 12 Aug 2004 22:15:38 -0700 (PDT)
Received: from XCH-NWBH-01.nw.nos.boeing.com (localhost [127.0.0.1])
	by slb-av-01.boeing.com (8.11.3/8.11.3/MBS-LDAP-01) with ESMTP id
	i7D5FcE03815; Thu, 12 Aug 2004 22:15:38 -0700 (PDT)
Received: from XCH-NW-09.nw.nos.boeing.com ([192.42.226.84]) by
	XCH-NWBH-01.nw.nos.boeing.com with Microsoft SMTPSVC(5.0.2195.6662); 
	Thu, 12 Aug 2004 22:15:38 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 12 Aug 2004 22:15:37 -0700
Message-ID: <5B58696DB20B9140AD20E0685C573A6404FDD6D8@xch-nw-09.nw.nos.boeing.com>
Thread-Topic: Question about use of RSVP in Production Networks
Thread-Index: AcSAuB4/LWsufpbcTvG7peE/5hf6BAAPEdlw
From: "Fleischman, Eric" <eric.fleischman@boeing.com>
To: <Bob.Natale@AppliedSNMP.com>, "Dean Anderson" <dean@av8.com>
X-OriginalArrivalTime: 13 Aug 2004 05:15:38.0076 (UTC)
	FILETIME=[91DCD1C0:01C480F4]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
Subject: RE: Question about use of RSVP in Production Networks
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-Score: 0.0 (/)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f
Content-Transfer-Encoding: quoted-printable

I am interested in learning about any production sites using RSVP-TE as =
well.=20

-----Original Message-----
From: Bob Natale [mailto:Bob.Natale@AppliedSNMP.com]
Sent: Thursday, August 12, 2004 3:00 PM
To: Fleischman, Eric; Dean Anderson
Cc: ietf@ietf.org
Subject: Re: Question about use of RSVP in Production Networks


Hi,

Were Eric's question and Dean's answer limited to RSVP strictly,
or would RSVP-TE deployments be of interest?  If the latter, then
what about emerging deployments of architectures that use RSVP-TE,
such as MPLS, GMPLS, and ASON?  (Or are none of the news releases
true? ;-)

Cordially,
BobN

---- Original message ----
>Date: Wed, 11 Aug 2004 18:37:31 -0400 (EDT)
>From: Dean Anderson <dean@av8.com> =20
>Subject: Re: Question about use of RSVP in Production Networks =20
>To: "Fleischman, Eric" <eric.fleischman@boeing.com>
>Cc: ietf@ietf.org
>
>RSVP is a idea that doesn't cut the mustard in the real world. There=20
are=20
>several show-stopper problems with RSVP.
>
>1) somewhat like multicast, anyone using RSVP is vulnerable to others
>mis-using or mis-configuring RSVP. ISPs several AS's away can really=20
screw
>up things for other ISPs. Because of this, it is unwise to deploy it
>because it requires too much trust in other ISPs.
>
>That relegates RSVP to the enterprise Lan, where it usually isn't=20
needed. =20
>Remember, RSVP is only useful if you have a congestion problem and=20
need to
>choose which packets to discard.  If you have no congestion problem,=20
then
>you have no need of RSVP. However, having a congestion problem also=20
opens
>the question of the nature of the congestion and what is the best way=20
to
>deal that problem.  I was involved in a study done by Genuity and=20
Cisco in
>which the congestion problem was found to most often involve the tail
>circuit--the link between the customer and the ISP.  The best solution=20
for
>this problem was found to be low latency queuing, not RSVP.
>
>2) Unlike multicast, every hop end-to-end must use RSVP for it to be=20
>useful. An RSVP tunnel is useless.
>
>3) RSVP doesn't detect certain kinds of problems that are important.=20
For
>example, a mid-span failure is not visible to RSVP.
>
>While RSVP is important research, it is not a widely deployable
>technology.
>
>What I-D's are you encountering that depend on RSVP?
>
>		--Dean
>
>On Tue, 10 Aug 2004, Fleischman, Eric wrote:
>
>> I am aware of some use of RSVP in labs but I am not aware of any use=20
of
>> RSVP in production networks (i.e., real life networks people connect=20
to
>> the Internet with). Simultaneously, I am encountering I-Ds and other
>> work planning to use RSVP. This possible disconnect concerns me.
>> Therefore, I would appreciate being educated by anybody using RSVP in
>> production settings. Would you please let me know how many devices,=20
what
>> applications, and how successful these deployments (if any) are?=20
Thank
>> you.
>>=20
>>=20
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www1.ietf.org/mailman/listinfo/ietf
>>=20
>
>
>_______________________________________________
>Ietf mailing list
>Ietf@ietf.org
>https://www1.ietf.org/mailman/listinfo/ietf
>_______________________________________________
>This message was passed through ietf_censored@carmen.ipv6.cselt.it,=20
which is a sublist of ietf@ietf.org. Not all messages are passed.=20
Decisions on what to pass are made solely by IETF_CENSORED ML=20
Administrator (ietf_admin@ngnet.it).

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


From ietf-bounces@ietf.org  Fri Aug 13 05:39:25 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00444;
	Fri, 13 Aug 2004 05:39:25 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BvYc8-0002IA-8r; Fri, 13 Aug 2004 05:44:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BvYR1-0003xy-IG; Fri, 13 Aug 2004 05:33:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BvYL0-0002yf-63
	for ietf@megatron.ietf.org; Fri, 13 Aug 2004 05:27:02 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00006
	for <ietf@ietf.org>; Fri, 13 Aug 2004 05:26:59 -0400 (EDT)
Received: from fep22-0.kolumbus.fi ([193.229.0.60] helo=fep22-app.kolumbus.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BvYQ7-000283-Sw
	for ietf@ietf.org; Fri, 13 Aug 2004 05:32:21 -0400
Received: from [10.64.93.2] (really [213.161.45.112])
	by fep22-app.kolumbus.fi with ESMTP
	id <20040813092656.BDFT27645.fep22-app.kolumbus.fi@[10.64.93.2]>;
	Fri, 13 Aug 2004 12:26:56 +0300
From: "John Loughney" <john.loughney@kolumbus.fi>
To: "Fleischman, Eric" <eric.fleischman@boeing.com>
Date: Fri, 13 Aug 2004 12:25:57 +0200
Message-ID: <yj5wLSlmRYKp.ddttKG0P@mail.kolumbus.fi>
X-Mailer: EPOC Email Version 2.10
MIME-Version: 1.0
Content-Language: i-default
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: quoted-printable
Cc: Dean Anderson <dean@av8.com>, ietf@ietf.org, Bob.Natale@AppliedSNMP.com
Subject: RE: Question about use of RSVP in Production Networks
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: John Loughney <john.loughney@kolumbus.fi>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-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-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Content-Transfer-Encoding: quoted-printable

Dean,

Just limiting my reply to one point:

>That relegates RSVP to the enterprise Lan, where it usually isn't=20
needed. =20
>Remember, RSVP is only useful if you have a congestion problem and =

need to
>choose which packets to discard.  If you have no congestion problem, =

then
>you have no need of RSVP. However, having a congestion problem also =

opens
>the question of the nature of the congestion and what is the best way =

to
>deal that problem.  I was involved in a study done by Genuity and=20
Cisco in
>which the congestion problem was found to most often involve the =
tail
>circuit--the link between the customer and the ISP.  The best solution =

for
>this problem was found to be low latency queuing, not RSVP.

Adding VOIP to an enterprise LAN can often add to congestion. Some on-path =
signaling can help here - not to mention NAT & FW traversal issues.  RSVP =
doesn't solve these, but NSIS is looking into these issues.

John


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


From ietf-bounces@ietf.org  Fri Aug 13 05:54:38 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01752;
	Fri, 13 Aug 2004 05:54:38 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BvYqu-0002cp-LN; Fri, 13 Aug 2004 06:00:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BvYiT-00075R-Ev; Fri, 13 Aug 2004 05:51:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BvYgW-0006b5-3i
	for ietf@megatron.ietf.org; Fri, 13 Aug 2004 05:49:16 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01315
	for <ietf@ietf.org>; Fri, 13 Aug 2004 05:49:13 -0400 (EDT)
Received: from fep22-0.kolumbus.fi ([193.229.0.60] helo=fep22-app.kolumbus.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BvYld-0002WO-Nt
	for ietf@ietf.org; Fri, 13 Aug 2004 05:54:35 -0400
Received: from [10.64.93.2] (really [213.161.45.112])
	by fep22-app.kolumbus.fi with ESMTP
	id <20040813094909.BOHI27645.fep22-app.kolumbus.fi@[10.64.93.2]>;
	Fri, 13 Aug 2004 12:49:09 +0300
From: "John Loughney" <john.loughney@kolumbus.fi>
To: "Pekka Savola" <pekkas@netcore.fi>
Date: Fri, 13 Aug 2004 12:48:11 +0200
Message-ID: <pQY0fSbk71Jl.h6L3ff1c@mail.kolumbus.fi>
X-Mailer: EPOC Email Version 2.10
MIME-Version: 1.0
Content-Language: i-default
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Content-Transfer-Encoding: quoted-printable
Cc: David R Oran <oran@cisco.com>, ietf@ietf.org
Subject: Re: hop-by-hop and router alert options [Re: Question about use of
 RSVP in Production Networks]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: John Loughney <john.loughney@kolumbus.fi>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-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-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Content-Transfer-Encoding: quoted-printable

> Of course.  Then why this wasn't the first thing NSIS did after =
going
> for on-path signalling, or didn't I just manage to find it? =20

NSIS was specifically charged to by the Transport ADs to work on on-path =
signaling. There is an analysis document being reviewed by the IESG right =
now ...

> I really really hope that there has been a problem statement...

Why? I've generally found that problem statement documents have limited =
usefulness.
> Further point where you can use path-coupled signalling, you mean?  =

> Not really, as there seems to be something seriously broken if you
> need set up priorization except in well-defined points in the network.  =

> And to achieve that, you could use a "bandwidth broker": either =
it's
> able to set up the required bandwidth (it's in the same site, or at =
a
> site your site has a roaming agreement with), or it isn't and the
> approach is going to fail in any case, because the sites out in the
> Internet don't want outsiders to request bandwidth allocations.

As you know from  IPv6 discussions, people's view of what constitutes a =
site=20
is very different. It is not a well defined term. NAT & FW traversal is =
very=20
difficult, especially for signalling incoming connections. We have =
documentation, if you are interested.

Also, there is no standard bw broker. Hoping that there was doesn't help. =
Currently deployed bw brokers have scalability problems, especially if they =
are meant to scale Internet-wide.

> True enough, I had my operator hat on ;-).  My mind just boggled =
when
> I started to realize that some part of the IETF is still in denial =
on
> why RSVP didn't go through, and is now in the process of =
reinventing
> it .. wasting a lot of time and effort that could be much better =
spent
> on making an operationally more feasible system to provide these
> reservations in a well-defined, constrained points of the network.

Interestingly  enough, there are operators involved in the NSIS =
discussions.=20
Also, some of the protoco=C3=B6 mechanisms of RSVP are suprisingly robust, =
but not all of the design criteria of RSVP hold today.

> What I can't figure why this is happening.  I guess the IESG must =
have
> been asleep, or the most people just thought, "well.. let them =
waste
> their energy on that.. at least they don't bother us while they are
> bashing the heads in the wall.."

Before passing such judgements on the IESG, reading the charter would be =
recommended. If you find yourself nearby Helsinki, I'd be happy to explain =
things.

John


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


From ietf-bounces@ietf.org  Fri Aug 13 10:52:36 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20390;
	Fri, 13 Aug 2004 10:52:36 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BvdVI-00081i-Dk; Fri, 13 Aug 2004 10:58:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BvdFz-0003x0-Di; Fri, 13 Aug 2004 10: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 1BvNey-0005zZ-U4
	for ietf@megatron.ietf.org; Thu, 12 Aug 2004 18:02:57 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11365
	for <ietf@ietf.org>; Thu, 12 Aug 2004 18:02:54 -0400 (EDT)
Received: from omr5.netsolmail.com ([216.168.230.142])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BvNk0-0007qM-1H
	for ietf@ietf.org; Thu, 12 Aug 2004 18:08:09 -0400
Received: from ms1.netsolmail.com (IDENT:mirapoint@[216.168.230.167])
	by omr5.netsolmail.com (8.12.10/8.12.10) with ESMTP id i7CM0Luo015559; 
	Thu, 12 Aug 2004 18:00:21 -0400 (EDT)
Received: from ms1.netsolmail.com (localhost.netsolmail.com [127.0.0.1])
	by ms1.netsolmail.com (Mirapoint Messaging Server MOS 3.2.2-GA)
	with ESMTP id BXU96719; Thu, 12 Aug 2004 18:00:20 -0400 (EDT)
Message-Id: <200408122200.BXU96719@ms1.netsolmail.com>
Received: from 64.254.114.114
	by ms1.netsolmail.com (Mirapoint Messaging Server MOS 3.2.2-GA)
	with HTTP/1.1; Thu, 12 Aug 2004 18:00:20 -0400
Date: Thu, 12 Aug 2004 18:00:20 -0400
From: Bob Natale <Bob.Natale@AppliedSNMP.com>
To: "Fleischman, Eric" <eric.fleischman@boeing.com>,
        Dean Anderson <dean@av8.com>
X-Mailer: Webmail Mirapoint Direct 3.2.2-GA
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Fri, 13 Aug 2004 10:42:07 -0400
Cc: ietf@ietf.org
Subject: Re: Question about use of RSVP in Production Networks
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Bob.Natale@AppliedSNMP.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-Score: 0.8 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
Content-Transfer-Encoding: 7bit

Hi,

Were Eric's question and Dean's answer limited to RSVP strictly,
or would RSVP-TE deployments be of interest?  If the latter, then
what about emerging deployments of architectures that use RSVP-TE,
such as MPLS, GMPLS, and ASON?  (Or are none of the news releases
true? ;-)

Cordially,
BobN

---- Original message ----
>Date: Wed, 11 Aug 2004 18:37:31 -0400 (EDT)
>From: Dean Anderson <dean@av8.com>  
>Subject: Re: Question about use of RSVP in Production Networks  
>To: "Fleischman, Eric" <eric.fleischman@boeing.com>
>Cc: ietf@ietf.org
>
>RSVP is a idea that doesn't cut the mustard in the real world. There 
are 
>several show-stopper problems with RSVP.
>
>1) somewhat like multicast, anyone using RSVP is vulnerable to others
>mis-using or mis-configuring RSVP. ISPs several AS's away can really 
screw
>up things for other ISPs. Because of this, it is unwise to deploy it
>because it requires too much trust in other ISPs.
>
>That relegates RSVP to the enterprise Lan, where it usually isn't 
needed.  
>Remember, RSVP is only useful if you have a congestion problem and 
need to
>choose which packets to discard.  If you have no congestion problem, 
then
>you have no need of RSVP. However, having a congestion problem also 
opens
>the question of the nature of the congestion and what is the best way 
to
>deal that problem.  I was involved in a study done by Genuity and 
Cisco in
>which the congestion problem was found to most often involve the tail
>circuit--the link between the customer and the ISP.  The best solution 
for
>this problem was found to be low latency queuing, not RSVP.
>
>2) Unlike multicast, every hop end-to-end must use RSVP for it to be 
>useful. An RSVP tunnel is useless.
>
>3) RSVP doesn't detect certain kinds of problems that are important. 
For
>example, a mid-span failure is not visible to RSVP.
>
>While RSVP is important research, it is not a widely deployable
>technology.
>
>What I-D's are you encountering that depend on RSVP?
>
>		--Dean
>
>On Tue, 10 Aug 2004, Fleischman, Eric wrote:
>
>> I am aware of some use of RSVP in labs but I am not aware of any use 
of
>> RSVP in production networks (i.e., real life networks people connect 
to
>> the Internet with). Simultaneously, I am encountering I-Ds and other
>> work planning to use RSVP. This possible disconnect concerns me.
>> Therefore, I would appreciate being educated by anybody using RSVP in
>> production settings. Would you please let me know how many devices, 
what
>> applications, and how successful these deployments (if any) are? 
Thank
>> you.
>> 
>> 
>> _______________________________________________
>> 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
>_______________________________________________
>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-bounces@ietf.org  Fri Aug 13 10:52:36 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20387;
	Fri, 13 Aug 2004 10:52:36 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BvdVI-00081h-8j; Fri, 13 Aug 2004 10:58:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BvdFy-0003uv-Ak; Fri, 13 Aug 2004 10:42:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BvLLv-0002km-1I
	for ietf@megatron.ietf.org; Thu, 12 Aug 2004 15:35:07 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26195
	for <ietf@ietf.org>; Thu, 12 Aug 2004 15:35:05 -0400 (EDT)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BvLQw-0002Xz-9p
	for ietf@ietf.org; Thu, 12 Aug 2004 15:40:18 -0400
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-2.cisco.com with ESMTP; 12 Aug 2004 12:37:09 -0700
Received: from edison.cisco.com (edison.cisco.com [171.71.180.109])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i7CJYXD2014087;
	Thu, 12 Aug 2004 12:34:33 -0700 (PDT)
Received: from [192.168.1.100] (sjc-vpn3-891.cisco.com [10.21.67.123]) by
	edison.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with
	ESMTP id MAA14856; Thu, 12 Aug 2004 12:34:32 -0700 (PDT)
Message-ID: <411BC646.2070605@cisco.com>
Date: Thu, 12 Aug 2004 12:34:30 -0700
From: Dan Wing <dwing@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Dean Anderson <dean@av8.com>, ietf@ietf.org
References: <DCxSc.1330792$%F1.349469@rtp-news.cisco.com>
In-Reply-To: <DCxSc.1330792$%F1.349469@rtp-news.cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Fri, 13 Aug 2004 10:42:07 -0400
Subject: Re: Question about use of RSVP in Production Networks
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-Score: 0.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Content-Transfer-Encoding: 7bit

Dean Anderson wrote:
> RSVP is a idea that doesn't cut the mustard in the real world. There are
> several show-stopper problems with RSVP.
> 
> 1) somewhat like multicast, anyone using RSVP is vulnerable to others
> mis-using or mis-configuring RSVP. ISPs several AS's away can really screw
> up things for other ISPs. Because of this, it is unwise to deploy it
> because it requires too much trust in other ISPs.

That isn't a fault of RSVP, the protocol.  Rather, it's a fault of
insufficient authorization for a requested flow.

> That relegates RSVP to the enterprise Lan, where it usually isn't needed.
> Remember, RSVP is only useful if you have a congestion problem and need to
> choose which packets to discard.  If you have no congestion problem, then
> you have no need of RSVP.

Enterprises have WANs (ATM, FR, MPLS) which do have congestion problems.
Even within a LAN it's possible to have congestion problems (PC backups,
database replication).

 > However, having a congestion problem also opens
> the question of the nature of the congestion and what is the best way to
> deal that problem.  I was involved in a study done by Genuity and Cisco in
> which the congestion problem was found to most often involve the tail
> circuit--the link between the customer and the ISP.  The best solution for
> this problem was found to be low latency queuing, not RSVP.
> 
> 2) Unlike multicast, every hop end-to-end must use RSVP for it to be
> useful.

RSVP only needs to be enabled on the links that might become congested,
such as an enterprise's WAN links.  It usually doesn't need to be
enabled on a non-bandwidth-constrained LAN.

-d

 > An RSVP tunnel is useless.
 >
> 3) RSVP doesn't detect certain kinds of problems that are important. For
> example, a mid-span failure is not visible to RSVP.
> 
> While RSVP is important research, it is not a widely deployable
> technology.
> 
> What I-D's are you encountering that depend on RSVP?
> 
> 		--Dean
> 
> On Tue, 10 Aug 2004, Fleischman, Eric wrote:
> 
> 
>>I am aware of some use of RSVP in labs but I am not aware of any use of
>>RSVP in production networks (i.e., real life networks people connect to
>>the Internet with). Simultaneously, I am encountering I-Ds and other
>>work planning to use RSVP. This possible disconnect concerns me.
>>Therefore, I would appreciate being educated by anybody using RSVP in
>>production settings. Would you please let me know how many devices, what
>>applications, and how successful these deployments (if any) are? Thank
>>you.
>>
>>
>>_______________________________________________
>>Ietf mailing list
>>Ietf@ietf.org
>>https://www1.ietf.org/mailman/listinfo/ietf
>>
> 
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf


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


From ietf-bounces@ietf.org  Fri Aug 13 10:54:26 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20585;
	Fri, 13 Aug 2004 10:54:26 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BvdWz-00084r-5W; Fri, 13 Aug 2004 10:59:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BvdG0-0003yS-HL; Fri, 13 Aug 2004 10:42:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BvNht-0007Kn-Qx
	for ietf@megatron.ietf.org; Thu, 12 Aug 2004 18:05:57 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11739
	for <ietf@ietf.org>; Thu, 12 Aug 2004 18:05:55 -0400 (EDT)
Received: from omr3.netsolmail.com ([216.168.230.164])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BvNmv-0007uo-Aq
	for ietf@ietf.org; Thu, 12 Aug 2004 18:11:10 -0400
Received: from ms1.netsolmail.com (IDENT:mirapoint@[216.168.230.167])
	by omr3.netsolmail.com (8.12.10/8.12.10) with ESMTP id i7CM5qT6024282; 
	Thu, 12 Aug 2004 18:05:52 -0400 (EDT)
Received: from ms1.netsolmail.com (localhost.netsolmail.com [127.0.0.1])
	by ms1.netsolmail.com (Mirapoint Messaging Server MOS 3.2.2-GA)
	with ESMTP id BXU97903; Thu, 12 Aug 2004 18:05:52 -0400 (EDT)
Message-Id: <200408122205.BXU97903@ms1.netsolmail.com>
Received: from 64.254.114.114
	by ms1.netsolmail.com (Mirapoint Messaging Server MOS 3.2.2-GA)
	with HTTP/1.1; Thu, 12 Aug 2004 18:05:52 -0400
Date: Thu, 12 Aug 2004 18:05:52 -0400
From: Bob Natale <Bob.Natale@AppliedSNMP.com>
To: Ping Pan <ppan@hammerheadsystems.com>
X-Mailer: Webmail Mirapoint Direct 3.2.2-GA
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.8 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Fri, 13 Aug 2004 10:42:07 -0400
Cc: ietf@ietf.org
Subject: RE: Question about use of RSVP in Production Networks
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Bob.Natale@AppliedSNMP.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-Score: 0.8 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Content-Transfer-Encoding: 7bit

Hi Ping,

My apologies (to all) for making the same point later in the
thread that you had already made here...processing my list of
open mail in the wrong order evidently!

But I am glad to have your confirmation of the wide deployment
of RSVP-TE in carrier MPLS nets.  I worked hard to promote that
approach several years before there were any such actual deployments
and have since moved on to other domains.

Cordially,
BobN

---- Original message ----
>Date: Wed, 11 Aug 2004 17:32:10 -0700
>From: "Ping Pan" <ppan@hammerheadsystems.com>  
>Subject: RE: Question about use of RSVP in Production Networks  
>To: "Fleischman, Eric" <eric.fleischman@boeing.com>
>Cc: ietf@ietf.org
>
>Do you count for RSVP-TE, that has been deployed widely in carrier
>networks? Other than multicast and wild-card filtering, all other
>features (and more) defined in the context of RSVP have been developed
>and deployed. The number of RSVP sessions (a.k.a. MPLS LSP's) is in the
>range of thousands in large backbone networks.
>
>Hope this will help.
>
>- Ping
>
>
>On Tue, 10 Aug 2004, Fleischman, Eric wrote:
>
>> I am aware of some use of RSVP in labs but I am not aware of any use 
>> of RSVP in production networks (i.e., real life networks people 
>> connect to the Internet with). Simultaneously, I am encountering I-
Ds 
>> and other work planning to use RSVP. This possible disconnect 
concerns
>
>> me. Therefore, I would appreciate being educated by anybody using 
RSVP
>
>> in production settings. Would you please let me know how many 
devices,
>
>> what applications, and how successful these deployments (if any) 
are? 
>> Thank you.
>> 
>> 
>> _______________________________________________
>> 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
>
>_______________________________________________
>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-bounces@ietf.org  Fri Aug 13 11:45:28 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23732;
	Fri, 13 Aug 2004 11:45:27 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BveKS-0000j8-UI; Fri, 13 Aug 2004 11:50:53 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bve9M-0005vI-4a; Fri, 13 Aug 2004 11:39:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bve4T-0004pI-RH
	for ietf@megatron.ietf.org; Fri, 13 Aug 2004 11:34:21 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23105
	for <ietf@ietf.org>; Fri, 13 Aug 2004 11:34:19 -0400 (EDT)
Received: from goose.ehsco.com ([207.65.203.98])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bve9e-0000Y3-Nt
	for ietf@ietf.org; Fri, 13 Aug 2004 11:39:44 -0400
Received: from [192.168.0.2] (cable0-stm-219.gmpexpress.net [63.147.50.219])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client did not present a certificate)
	by goose.ehsco.com (Postfix ) with ESMTP id 485EB1DFB1;
	Fri, 13 Aug 2004 10:34:17 -0500 (CDT)
Message-ID: <411CDF3E.7000507@ehsco.com>
Date: Fri, 13 Aug 2004 11:33:18 -0400
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7) Gecko/20040616
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ietf-822@imc.org, iesg@iesg.org, ietf@ietf.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Content-Transfer-Encoding: 7bit
Subject: Re: Last Call: 'The APPLICATION/MBOX Media-Type' to Proposed
	Standard
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Content-Transfer-Encoding: 7bit


Keith Moore <moore@cs.utk.edu> wrote on Thu, 12 Aug 2004 08:45:24 -0400:

> this is an application for a media-type. it's not trying to define the
> mbox format, it's just trying to define a label for the mbox format
> that can be used in contexts where MIME media-type labels are required.

That's correct; this is a tag definition, not a format specification.

Others should note that RFC2048 is designed to facilitate registrations --
more definitions for common data-types are widely preferred over a
proliferation of "x-foo" media-types that result from high registration
barriers (read the intro to 2048 if you don't believe me) -- and that's
the limited objective of this proposal.

There are a few places where this tag is necessary or useful. Online
downloadable archives of mailing lists would be easier to import, search
and otherwise manipulate if a media-type were defined and which allowed a
transfer agent to bridge the data to a local content agent (most of the
IETF archives are in mbox format, and I'm aware that certain cellular
email systems allow for downloadable SMS/email logs via mbox, not to
mention the proliferation of web/local mail systems that use mbox files
which are often transferred back and forth). Local actions such as
importing or opening a local mbox file would also be easier to perform if
there was a media-type that the OS could use (I have many mbox files of
project-specific archives and would appreciate better OS/messaging
integration with these files [such as opening and searching folders the
same as I can with message/rfc822 file objects], but need an OS-level
media-type to get there). And so forth.

A definitive authoritative specification for all variations of the mbox
database format is explicitly not the objective, for several reasons. For
one thing, such a definition is outside the IETF's purview, the same as a
definition for Outlook or Eudora or other vendor/platform-centric database
formats would be. Second, if the IETF *did* try to write such a
definition, it would quickly settle on the fact that multipart/digest
already exists for such purposes, and that defining an mbox format would
be redundant. If development proceeded beyond that (unlikely at best),
then the spec would necessarily conform with other messaging definitions,
and would end up declaring that mbox files SHOULD/MUST be compliant with
RFC2822 messages at a minimum, which ignores the reality of eight-bit
content, long lines, untagged charsets, EOL variations, etc. Other folks
can start a bof/wg and go through this process if they want to, but
frankly I'm happy just registering the media-type (the purpose of the
process, and the objective of this I-D).

On top of all that, mbox parsers need to be aware of the limitations and
variations on the content, and this cannot be adequately handled with a
media-type definition.

Suggestions about parameters has come up before (John Klensin suggested it
to me a couple of months ago). Unfortunately, these kind of helper tags
attempt to define content rules rather than transfer rules, and therefore
represent a non-trivial layer violation. They are analogous to using a
"version=" tag for app/postscript and relying on that meta-information
instead of embedded clue data. Obviously, content agents should be aware
of the content formatting rules. [what happens when the helper meta-tags
are lost? should the content agent NOT look at the content to make a
determination? that's where the logic belongs in the first place, so
putting it into the transfer layer is not only irrelevant it is possibly
harmful.] This data should not be overflowed to the transfer agent except
where it affects the transfer process proper, which is not the case with
any of the suggested tags.

> however I don't think this should be up for PS, as the standards track
> is intended for protocols that can be subject to interoperability tests,
> and this is just a label. Informational seems more appropriate to me.

I'll go along with that. 2048 only requires IESG approval, but does not
require standards-track, and dropping to informational gets us there.

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


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


From ietf-bounces@ietf.org  Fri Aug 13 12:03:48 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25134;
	Fri, 13 Aug 2004 12:03:48 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BvecD-00018T-SG; Fri, 13 Aug 2004 12: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 1BvePy-0001C2-IV; Fri, 13 Aug 2004 11:56:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BveMX-0000NE-PQ
	for ietf@megatron.ietf.org; Fri, 13 Aug 2004 11:53:02 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24495
	for <ietf@ietf.org>; Fri, 13 Aug 2004 11:52:59 -0400 (EDT)
Message-Id: <200408131552.LAA24495@ietf.org>
Received: from bdsl.66.15.163.216.gte.net ([66.15.163.216] helo=tndh.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BveRj-0000wg-Su
	for ietf@ietf.org; Fri, 13 Aug 2004 11:58:24 -0400
Received: from eaglet (127.0.0.1:4051)
	by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server]
	id <S6560B> for <ietf@ietf.org> from <alh-ietf@tndh.net>;
	Fri, 13 Aug 2004 08:49:20 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Dean Anderson'" <dean@av8.com>,
        "'Fleischman, Eric'" <eric.fleischman@boeing.com>
Date: Fri, 13 Aug 2004 08:52:46 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
In-Reply-To: <Pine.LNX.4.44.0408111821280.28896-100000@cirrus.av8.net>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Thread-Index: AcR/9vCwKaOI8OrSSmiIg9Mrm9PsIABUkmAw
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: RE: Question about use of RSVP in Production Networks
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-Score: 0.8 (/)
X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2
Content-Transfer-Encoding: 7bit

Dean Anderson wrote:
> RSVP is a idea that doesn't cut the mustard in the real world. There are
> several show-stopper problems with RSVP.

Propagating clueless FUD does not result in progress. 

> 
> 1) somewhat like multicast, anyone using RSVP is vulnerable to others
> mis-using or mis-configuring RSVP. ISPs several AS's away can really screw
> up things for other ISPs. Because of this, it is unwise to deploy it
> because it requires too much trust in other ISPs.

Inter-provider trust is something the Internet has to deal with. The
self-proclaimed gods of the ISP world bluster about how much smarter they
are than the Bell-heads, but even the lowly Bell-heads figured this one out.

> 
> That relegates RSVP to the enterprise Lan, where it usually isn't needed.
> Remember, RSVP is only useful if you have a congestion problem and need to
> choose which packets to discard.  

RSVP is a signaling protocol. The policy installed in the routers with
congested links is the one deciding what to discard, and it has the
opportunity to take hints from that signaling if it chooses. 

Despite rumors to the contrary, most complex enterprise networks include
non-LAN links, and even in the all-LAN case there are speed mismatches
between old and new segments.

> If you have no congestion problem, then
> you have no need of RSVP. 

Signaling is useful for more than QoS, though it is not clear that RSVP as
currently defined is useful for signaling non-QoS related policy. 

> However, having a congestion problem also opens
> the question of the nature of the congestion and what is the best way to
> deal that problem.  I was involved in a study done by Genuity and Cisco in
> which the congestion problem was found to most often involve the tail
> circuit--the link between the customer and the ISP.  The best solution for
> this problem was found to be low latency queuing, not RSVP.

As you say it depends on the nature of the congestion, but also the nature
of the application in the face of congestion. Generalizing all complex
topologies to a congested uplink just leads to protocol decisions that are
useless in the real world. 

> 
> 2) Unlike multicast, every hop end-to-end must use RSVP for it to be
> useful. An RSVP tunnel is useless.

This is the type of BS that keeps useful tools out of the hands of those
that need them, but don't have enough time to figure out the reality. The
only points that need to pay attention to signaling are those where
congestive loss is likely to occur. Even then, a smart implementation might
only pay attention once a threshold has been crossed indicating that queues
are building. 

> 
> 3) RSVP doesn't detect certain kinds of problems that are important. For
> example, a mid-span failure is not visible to RSVP.

WTFO! RSVP is a periodic signal, so it does detect and respond to mid-span
events. 

> 
> While RSVP is important research, it is not a widely deployable
> technology.

The reason the Internet has been successful is that each administrative
domain gets to decide which technologies are deployable. Your decision that
RSVP is not deployable does not automatically restrict if from wide
deployment. 

In answer to Eric's original question, the FUD being spread through
responses like Dean's have squelched what little RSVP had been deployed
several years ago. That does not remove the need for a signaling protocol,
as many WGs find they need to define new ones or variants. The bottom line
is that the lack of a trust model makes operators suspicious of any external
signal.

Tony 

> 
> What I-D's are you encountering that depend on RSVP?
> 
> 		--Dean
> 
> On Tue, 10 Aug 2004, Fleischman, Eric wrote:
> 
> > I am aware of some use of RSVP in labs but I am not aware of any use of
> > RSVP in production networks (i.e., real life networks people connect to
> > the Internet with). Simultaneously, I am encountering I-Ds and other
> > work planning to use RSVP. This possible disconnect concerns me.
> > Therefore, I would appreciate being educated by anybody using RSVP in
> > production settings. Would you please let me know how many devices, what
> > applications, and how successful these deployments (if any) are? Thank
> > you.
> >
> >
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www1.ietf.org/mailman/listinfo/ietf
> >
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf


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


From ietf-bounces@ietf.org  Fri Aug 13 12:52:20 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28434;
	Fri, 13 Aug 2004 12:52:20 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BvfNC-00025R-4G; Fri, 13 Aug 2004 12:57:46 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bvf9h-0003G8-3g; Fri, 13 Aug 2004 12:43:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bvf3m-0002Jo-AY
	for ietf@megatron.ietf.org; Fri, 13 Aug 2004 12:37:42 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27445
	for <ietf@ietf.org>; Fri, 13 Aug 2004 12:37:39 -0400 (EDT)
Received: from slb-smtpout-01.boeing.com ([130.76.64.48])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bvf8y-0001o4-JS
	for ietf@ietf.org; Fri, 13 Aug 2004 12:43:05 -0400
Received: from stl-av-01.boeing.com ([192.76.190.6])
	by slb-smtpout-01.boeing.com (8.9.2.MG.10092003/8.8.5-M2) with ESMTP id
	JAA17297; Fri, 13 Aug 2004 09:37:09 -0700 (PDT)
Received: from XCH-NWBH-01.nw.nos.boeing.com (localhost [127.0.0.1])
	by stl-av-01.boeing.com (8.11.3/8.11.3/MBS-LDAP-01) with ESMTP id
	i7DGb8c01920; Fri, 13 Aug 2004 11:37:09 -0500 (CDT)
Received: from XCH-NW-09.nw.nos.boeing.com ([192.42.226.84]) by
	XCH-NWBH-01.nw.nos.boeing.com with Microsoft SMTPSVC(5.0.2195.6662); 
	Fri, 13 Aug 2004 09:37:06 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 13 Aug 2004 09:37:06 -0700
Message-ID: <5B58696DB20B9140AD20E0685C573A6404FDD6DD@xch-nw-09.nw.nos.boeing.com>
Thread-Topic: Question about use of RSVP in Production Networks
Thread-Index: AcSBRSDJ3a0sZtHxTnSvprNk3zxZxgADjQ3g
From: "Fleischman, Eric" <eric.fleischman@boeing.com>
To: <Bob.Natale@AppliedSNMP.com>, "Dean Anderson" <dean@av8.com>
X-OriginalArrivalTime: 13 Aug 2004 16:37:06.0530 (UTC)
	FILETIME=[C547C420:01C48153]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
Subject: RE: Question about use of RSVP in Production Networks
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-Score: 0.0 (/)
X-Scan-Signature: 1676547e4f33b5e63227e9c02bd359e3
Content-Transfer-Encoding: quoted-printable

Bob,

I am interested in learning about any and all production use of the RSVP =
protocol. I am also interested in RSVP-TE. I am especially interested in =
learning the experiences of any organization which has deployed the RSVP =
protocol in production environments. I am interested in how well it =
performs, how cleanly it meets their business objectives, how well it =
scales, how hard (or easy) is it to manage, etc.

--Eric

-----Original Message-----
From: Bob Natale [mailto:Bob.Natale@AppliedSNMP.com]
Sent: Thursday, August 12, 2004 3:00 PM
To: Fleischman, Eric; Dean Anderson
Cc: ietf@ietf.org
Subject: Re: Question about use of RSVP in Production Networks


Hi,

Were Eric's question and Dean's answer limited to RSVP strictly,
or would RSVP-TE deployments be of interest?  If the latter, then
what about emerging deployments of architectures that use RSVP-TE,
such as MPLS, GMPLS, and ASON?  (Or are none of the news releases
true? ;-)

Cordially,
BobN

---- Original message ----
>Date: Wed, 11 Aug 2004 18:37:31 -0400 (EDT)
>From: Dean Anderson <dean@av8.com> =20
>Subject: Re: Question about use of RSVP in Production Networks =20
>To: "Fleischman, Eric" <eric.fleischman@boeing.com>
>Cc: ietf@ietf.org
>
>RSVP is a idea that doesn't cut the mustard in the real world. There=20
are=20
>several show-stopper problems with RSVP.
>
>1) somewhat like multicast, anyone using RSVP is vulnerable to others
>mis-using or mis-configuring RSVP. ISPs several AS's away can really=20
screw
>up things for other ISPs. Because of this, it is unwise to deploy it
>because it requires too much trust in other ISPs.
>
>That relegates RSVP to the enterprise Lan, where it usually isn't=20
needed. =20
>Remember, RSVP is only useful if you have a congestion problem and=20
need to
>choose which packets to discard.  If you have no congestion problem,=20
then
>you have no need of RSVP. However, having a congestion problem also=20
opens
>the question of the nature of the congestion and what is the best way=20
to
>deal that problem.  I was involved in a study done by Genuity and=20
Cisco in
>which the congestion problem was found to most often involve the tail
>circuit--the link between the customer and the ISP.  The best solution=20
for
>this problem was found to be low latency queuing, not RSVP.
>
>2) Unlike multicast, every hop end-to-end must use RSVP for it to be=20
>useful. An RSVP tunnel is useless.
>
>3) RSVP doesn't detect certain kinds of problems that are important.=20
For
>example, a mid-span failure is not visible to RSVP.
>
>While RSVP is important research, it is not a widely deployable
>technology.
>
>What I-D's are you encountering that depend on RSVP?
>
>		--Dean
>
>On Tue, 10 Aug 2004, Fleischman, Eric wrote:
>
>> I am aware of some use of RSVP in labs but I am not aware of any use=20
of
>> RSVP in production networks (i.e., real life networks people connect=20
to
>> the Internet with). Simultaneously, I am encountering I-Ds and other
>> work planning to use RSVP. This possible disconnect concerns me.
>> Therefore, I would appreciate being educated by anybody using RSVP in
>> production settings. Would you please let me know how many devices,=20
what
>> applications, and how successful these deployments (if any) are?=20
Thank
>> you.
>>=20
>>=20
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www1.ietf.org/mailman/listinfo/ietf
>>=20
>
>
>_______________________________________________
>Ietf mailing list
>Ietf@ietf.org
>https://www1.ietf.org/mailman/listinfo/ietf
>_______________________________________________
>This message was passed through ietf_censored@carmen.ipv6.cselt.it,=20
which is a sublist of ietf@ietf.org. Not all messages are passed.=20
Decisions on what to pass are made solely by IETF_CENSORED ML=20
Administrator (ietf_admin@ngnet.it).

_______________________________________________
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 Aug 13 16:25:17 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15848;
	Fri, 13 Aug 2004 16:25:17 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BvihI-0007Kl-OV; Fri, 13 Aug 2004 16:30:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BviU8-0004u3-KR; Fri, 13 Aug 2004 16:17:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BveHK-0007es-CH
	for ietf@megatron.ietf.org; Fri, 13 Aug 2004 11:47:38 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23945
	for <ietf@ietf.org>; Fri, 13 Aug 2004 11:47:35 -0400 (EDT)
Received: from klutz.cs.utk.edu ([160.36.56.50])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BveMV-0000nH-II
	for ietf@ietf.org; Fri, 13 Aug 2004 11:53:00 -0400
Received: from localhost (klutz [127.0.0.1])
	by klutz.cs.utk.edu (Postfix) with ESMTP id EC863400AF;
	Fri, 13 Aug 2004 11:47:35 -0400 (EDT)
Received: from klutz.cs.utk.edu ([127.0.0.1])
	by localhost (klutz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 23950-15; Fri, 13 Aug 2004 11:47:35 -0400 (EDT)
Received: from astro.cs.utk.edu (astro.cs.utk.edu [160.36.58.43])
	by klutz.cs.utk.edu (Postfix) with ESMTP id ECF98400AE;
	Fri, 13 Aug 2004 11:47:34 -0400 (EDT)
Date: Fri, 13 Aug 2004 11:47:34 -0400
From: Keith Moore <moore@cs.utk.edu>
To: "Eric A. Hall" <ehall@ehsco.com>
Message-Id: <20040813114734.2eb01d55.moore@cs.utk.edu>
In-Reply-To: <411CDF3E.7000507@ehsco.com>
References: <411CDF3E.7000507@ehsco.com>
X-Mailer: Sylpheed version 0.9.12 (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at cs.utk.edu by ClamAV and McAfee
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Fri, 13 Aug 2004 16:17:06 -0400
Cc: ietf-822@imc.org, moore@cs.utk.edu, iesg@iesg.org, ietf@ietf.org
Subject: Re: Last Call: 'The APPLICATION/MBOX Media-Type' to Proposed
 Standard
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: 7bit

> A definitive authoritative specification for all variations of the
> mbox database format is explicitly not the objective, for several
> reasons. 

that's fine.  I fully support registering application/mbox as a media
type.

> For
> one thing, such a definition is outside the IETF's purview, the same
> as a definition for Outlook or Eudora or other vendor/platform-centric
> database formats would be. 

I have to disagree here.  Perhaps standardizing mbox would be outside
of IETF's purview, but I think it would be valuable for IETF to publish
a peer-reviewed Informational description of (1) existing practice for 
mbox files and (2) recommended practice for reading and writing mbox
files.  I just don't think that this should be critical path for getting
application/mbox registered.

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


From ietf-bounces@ietf.org  Fri Aug 13 16:26:32 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15988;
	Fri, 13 Aug 2004 16:26:32 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BviiV-0007Mq-Vp; Fri, 13 Aug 2004 16:32:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BviU9-0004uA-Hw; Fri, 13 Aug 2004 16:17:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bvfrj-0003r9-3h
	for ietf@megatron.ietf.org; Fri, 13 Aug 2004 13:29:19 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00741
	for <ietf@ietf.org>; Fri, 13 Aug 2004 13:29:17 -0400 (EDT)
From: ned.freed@mrochek.com
Received: from mauve.mrochek.com ([209.55.107.55])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bvfwv-0002hw-7r
	for ietf@ietf.org; Fri, 13 Aug 2004 13:34:42 -0400
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243)
	id <01LDM169877K00005R@mauve.mrochek.com> for ietf@ietf.org; Fri,
	13 Aug 2004 10:29:14 -0700 (PDT)
Date: Fri, 13 Aug 2004 10:26:50 -0700 (PDT)
In-reply-to: "Your message dated Fri, 13 Aug 2004 11:47:34 -0400"
	<20040813114734.2eb01d55.moore@cs.utk.edu>
To: Keith Moore <moore@cs.utk.edu>
Message-id: <01LDM27HCUCO00005R@mauve.mrochek.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=us-ascii
Content-transfer-encoding: 7BIT
References: <411CDF3E.7000507@ehsco.com>
	<20040813114734.2eb01d55.moore@cs.utk.edu>
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Content-Transfer-Encoding: 7BIT
X-Mailman-Approved-At: Fri, 13 Aug 2004 16:17:06 -0400
Cc: ietf-822@imc.org, moore@cs.utk.edu, iesg@iesg.org,
        Eric A Hall <ehall@ehsco.com>, ietf@ietf.org
Subject: Re: Last Call: 'The APPLICATION/MBOX Media-Type' to Proposed
	Standard
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: 7BIT


> > A definitive authoritative specification for all variations of the
> > mbox database format is explicitly not the objective, for several
> > reasons.

> that's fine.  I fully support registering application/mbox as a media
> type.

> > For
> > one thing, such a definition is outside the IETF's purview, the same
> > as a definition for Outlook or Eudora or other vendor/platform-centric
> > database formats would be.

> I have to disagree here.  Perhaps standardizing mbox would be outside
> of IETF's purview, but I think it would be valuable for IETF to publish
> a peer-reviewed Informational description of (1) existing practice for
> mbox files and (2) recommended practice for reading and writing mbox
> files.  I just don't think that this should be critical path for getting
> application/mbox registered.

I agree. Such a specification shouldn't be a requirement for this registration,
but an informational document would be a nice thing to have. Whether or not
sufficient energy exists to get it done is another matter - a similar
informational document on the many variations of uuencode has been on my to-do
for well over a decade now, and I don't see myself getting to it any time
soon...

				Ned

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


From ietf-bounces@ietf.org  Fri Aug 13 20:45:35 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28591;
	Fri, 13 Aug 2004 20:45:35 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BvmlD-0002ci-UP; Fri, 13 Aug 2004 20:51:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BvmcT-00007m-7b; Fri, 13 Aug 2004 20:42:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bvmah-00082l-As; Fri, 13 Aug 2004 20:40:13 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28046;
	Fri, 13 Aug 2004 20:40:09 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from turing-police.cc.vt.edu ([128.173.14.107] ident=root)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bvmfx-0002X6-FE; Fri, 13 Aug 2004 20:45:38 -0400
Received: from turing-police.cc.vt.edu (IDENT:valdis@turing-police.cc.vt.edu
	[127.0.0.1])
	by turing-police.cc.vt.edu (8.13.1/8.13.1) with ESMTP id i7E0e5Pk023772;
	Fri, 13 Aug 2004 20:40:05 -0400
Message-Id: <200408140040.i7E0e5Pk023772@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.7.1 07/26/2004 with nmh-1.1-RC3
To: Tony Hansen <tony@att.com>
In-Reply-To: Your message of "Thu, 12 Aug 2004 17:18:19 EDT."
	<411BDE9B.7090706@att.com> 
References: <p06110437bd3d5d396de1@[10.20.30.249]> <411AB496.8080307@erols.com>
	<411BDE9B.7090706@att.com>
Mime-Version: 1.0
Date: Fri, 13 Aug 2004 20:40:05 -0400
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Cc: ietf-822@imc.org, ehall@ntrg.com, iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: 'The APPLICATION/MBOX Media-Type' to Proposed
	Standard 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0956735048=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813

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

--==_Exmh_-96652284P
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

On Thu, 12 Aug 2004 17:18:19 EDT, Tony Hansen said:
> The information about the mbox format being anecdotally defined is=20
> incorrect. The mbox format has traditionally been documented in the=20
> binmail(1) or mail.local(8) man pages (BSD UNIX derivatives) or mail(1)=
=20
> man page (UNIX System 3/5/III/V derivatives). There have been several=20
> variants of the mbox format in use by those different systems. The most=
=20
> complete description of an mbox format can be seen in the man page from=
=20
> any UNIX System Vr4 derived system, such as Solaris.

Umm.. Tony?  I hate to say it, but if there have been several variants us=
ed in
the wild, and the man pages for said variants document different formats,=

that's awfully close to =22anecdotally defined=22 when you're doing a sta=
ndard.

For example, a Solaris 8 box across the hall says in 'man mail.local':

     Each delivered mail message in the mailbox is preceded by  a
     =22Unix From line=22 with the following format:

          From sender_address time_stamp

     The sender_address  is  extracted  from  the  SMTP  envelope
     address  (the  envelope  address  is  specified  with the -f
     option).

     A trailing blank line is also added to the end of each  mes-
     sage.

Hmm. Nothing about whether the sender_address is, or should be, <brackete=
d>.
Nothing about the format of the time_stamp. Nothing about '>From ' stuffi=
ng
(and yes, I've seen systems that don't do it at all, and systems that onl=
y
>-stuff if the From line matched a regexp for what *they* think the entir=
e 'From '
line looks like(*)). The Sendmail 8.13.1 mail.local does say >-stuffing
happens for lines that =22which could be mistaken for a =60=60From '' del=
imiter
line=22, and the code actually checks for exactly 5 chars...

Any doubts that this whole mess is at best anecdotally defined can be dis=
pelled by
mentioning =22Content-Length:=22 (interestingly enough, not even mentione=
d in the
Solaris or Sendmail man pages, although the Sendmail source tree does men=
tion
that building on Solaris 2.3 or later will turn it on.  Of interest mostl=
y because
the Content-Length: is so easily broken by later >-stuffing/unstuffing or=
 other
similar conversion...

(*) time_stamp. Argh.  Fought with this during a data/machine migration.
Write code that will accept a 26 byte ctime format: 'Fri Sep 13 00:00:00 =
1986=5Cn=5C0'.
Works fine once you realize that some systems just used 'From envelop_add=
ress'
without a timestamp.

Then I get handed this: 'Fri Aug 13 20:21:32 EDT 2004'.  Fix that, and fi=
nd some
joker running in a French locale: 'vendredi, 13 ao=FBt 2004, 20:22:01 EDT=
'.
And yes, his b0rked software only >-stuffed 'From ' lines that regexp-mat=
ched
the *French* variant. Took me *quite* some time to twig into THAT one...


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

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

iD8DBQFBHV9lcC3lWbTT17ARAp/xAJ9+iEljSU8a8/wFUIy4xoQIINQVcACfWXF0
1P1CBhkkyVNjOF2IFhW1hW8=
=zphQ
-----END PGP SIGNATURE-----

--==_Exmh_-96652284P--


--===============0956735048==
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

--===============0956735048==--



From ietf-bounces@ietf.org  Fri Aug 13 23:11:36 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05369;
	Fri, 13 Aug 2004 23:11:36 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bvp2X-0004i2-S2; Fri, 13 Aug 2004 23:17:07 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bvotm-0005ge-La; Fri, 13 Aug 2004 23:08:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bvopp-0004pV-2e; Fri, 13 Aug 2004 23:03:57 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05001;
	Fri, 13 Aug 2004 23:03:53 -0400 (EDT)
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bvov5-0004c6-MY; Fri, 13 Aug 2004 23:09:25 -0400
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.34)
	id 1Bvopc-000LKw-Gq; Fri, 13 Aug 2004 23:03:44 -0400
Date: Fri, 13 Aug 2004 23:03:44 -0400
From: John C Klensin <john-ietf@jck.com>
To: "Eric A. Hall" <ehall@ehsco.com>, ietf-822@imc.org, iesg@iesg.org,
        ietf@ietf.org
Message-ID: <177B507598E965A4EAB5BDA0@scan.jck.com>
X-Mailer: Mulberry/3.1.6 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Content-Transfer-Encoding: 7bit
Subject: Re: Last Call: 'The APPLICATION/MBOX Media-Type' to
 Proposed	Standard
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Content-Transfer-Encoding: 7bit



--On Friday, 13 August, 2004 11:33 -0400 "Eric A. Hall"
<ehall@ehsco.com> wrote:

>...
> Suggestions about parameters has come up before (John Klensin
> suggested it to me a couple of months ago). Unfortunately,
> these kind of helper tags attempt to define content rules
> rather than transfer rules, and therefore represent a
> non-trivial layer violation.

Whoops!   Whatever the other issues here,  content-type does
define content rules and not transfer rules (transfer rules are
captured in C-T-E), and parameters/hints on content-type are
just more content rules.   So I don't have any idea what you are
talking about when you refer to a layer violation.

To restate that position more generally, the purpose of having
content types is to permit the recipient  to figure out how to
parse/process the content.  To repeat Bruce's point from a
different perspective, if all that is intended is "here are some
nice bits, which someone has decided to call "mbox" without any
real semantics, and any information you are going to get about
how to process them is coming out of band and by agreement among
the communicating parties", then application/octet-stream is at
least nearly adequate.  From that point of view, if you want an
IETF type, you should either have to claim that all (or nearly
all) of the applications that process MBOX format critters can
process all variations on the format, or there really need to be
clues in either the type or the parameters.  Otherwise, you are
just creating a "gotcha" situation, and that is not what content
types are supposed to be able.

> They are analogous to using a
> "version=" tag for app/postscript and relying on that
> meta-information instead of embedded clue data. Obviously,
> content agents should be aware of the content formatting
> rules. [what happens when the helper meta-tags are lost?
> should the content agent NOT look at the content to make a
> determination? that's where the logic belongs in the first
> place, so putting it into the transfer layer is not only
> irrelevant it is possibly harmful.] This data should not be
> overflowed to the transfer agent except where it affects the
> transfer process proper, which is not the case with any of the
> suggested tags.

Again, in the context of MIME media type definitions, I have no
idea what you are talking about.

     john




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


From ietf-bounces@ietf.org  Sat Aug 14 10:09:28 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15276;
	Sat, 14 Aug 2004 10:09:27 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BvzJI-00059Y-9y; Sat, 14 Aug 2004 10:15:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bvz4P-00024S-F2; Sat, 14 Aug 2004 09:59:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bvz1O-0001aZ-IO
	for ietf@megatron.ietf.org; Sat, 14 Aug 2004 09:56:34 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14302
	for <ietf@ietf.org>; Sat, 14 Aug 2004 09:56:32 -0400 (EDT)
Received: from colo.khms.westfalen.de ([213.239.196.208] ident=Debian-exim)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bvz6l-0004zG-Hg
	for ietf@ietf.org; Sat, 14 Aug 2004 10:02:09 -0400
Received: from khms.vpn ([10.172.192.2]:53125 helo=khms.westfalen.de)
	by colo.khms.westfalen.de with asmtp (TLS-1.0:RSA_ARCFOUR_SHA:16)
	(Exim 4.34) id 1Bvyyi-0005ll-3O
	for ietf@ietf.org; Sat, 14 Aug 2004 15:53:48 +0200
Received: from root (helo=khms.westfalen.de)
	by khms.westfalen.de with local-bsmtp (Exim 4.34) id 1Bvyyd-0003pB-KB
	for ietf@ietf.org; Sat, 14 Aug 2004 15:53:43 +0200
Received: by khms.westfalen.de (CrossPoint v3.12d.kh14 R/C435);
	14 Aug 2004 15:43:28 +0200
Date: 14 Aug 2004 15:04:00 +0200
From: kaih@khms.westfalen.de (Kai Henningsen)
To: ietf@ietf.org
Message-ID: <9EpQzxAXw-B@khms.westfalen.de>
References: <411CDF3E.7000507@ehsco.com>
X-Mailer: CrossPoint v3.12d.kh14 R/C435
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Organization: Organisation? Me?! Are you kidding?
References: <411CDF3E.7000507@ehsco.com>
X-No-Junk-Mail: I do not want to get *any* junk mail.
Comment: Unsolicited commercial mail will incur an US$100 handling fee per
	received mail.
X-Fix-Your-Modem: +++ATS2=255&WO1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Subject: Re: Last Call: 'The APPLICATION/MBOX Media-Type' to Proposed
	Standard
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36

ehall@ehsco.com (Eric A. Hall)  wrote on 13.08.04 in <411CDF3E.7000507@ehsco.com>:

> Keith Moore <moore@cs.utk.edu> wrote on Thu, 12 Aug 2004 08:45:24 -0400:
>
> > this is an application for a media-type. it's not trying to define the
> > mbox format, it's just trying to define a label for the mbox format
> > that can be used in contexts where MIME media-type labels are required.
>
> That's correct; this is a tag definition, not a format specification.

That is not the problem. The problem is that the tag is not specific  
enough to be useful.

> There are a few places where this tag is necessary or useful. Online
> downloadable archives of mailing lists would be easier to import, search
> and otherwise manipulate if a media-type were defined and which allowed a
> transfer agent to bridge the data to a local content agent

... but absent specification of *which* mbox format it is, this can only  
work by luck.

> A definitive authoritative specification for all variations of the mbox
> database format is explicitly not the objective, for several reasons.

Note that I never asked for that. (Unless you think the variant of mbox in  
use could only specified if we had that specification, that is ... which  
would only underscore the gaping hole in the current document.)

(Note also that I didn't ask for any specific way of specifying the mbox  
variant - the regular expression proposal was someone else, and I'm not  
convinced it actually solves the problem.)

> Suggestions about parameters has come up before (John Klensin suggested it
> to me a couple of months ago). Unfortunately, these kind of helper tags
> attempt to define content rules rather than transfer rules, and therefore
> represent a non-trivial layer violation.

That seems nonsensical. They're no more or less defining content rules  
than the media type itself is.

> They are analogous to using a
> "version=" tag for app/postscript and relying on that meta-information
> instead of embedded clue data.

It seems well established that "embedded clue data" for mbox is not  
reliable, unless you involve a full AI.

In any case, I really don't see the qualitative difference between  
claiming "this is XHTML text" and "this is HTML 4.1 text", to pick a  
different example.

I think claims of "layer violation" are clearly - and obviously - wrong.  
There *is* no non-artificial layer boundary here. The boundary in question  
is completely arbitrary.

> Obviously, content agents should be aware
> of the content formatting rules. [what happens when the helper meta-tags
> are lost? should the content agent NOT look at the content to make a
> determination?

Not without asking a human, it probably shouldn't. It's far too easy to  
get it wrong.

> that's where the logic belongs in the first place, so
> putting it into the transfer layer is not only irrelevant it is possibly
> harmful.]

Attempting to automatically figure this out is the harmful version.  
Telling what it is is most certainly *NOT* harmful.

MfG Kai

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


From ietf-bounces@ietf.org  Sat Aug 14 10:24:49 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16619;
	Sat, 14 Aug 2004 10:24:49 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BvzYA-0005P2-BU; Sat, 14 Aug 2004 10:30:26 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BvzOA-0002yS-LG; Sat, 14 Aug 2004 10:20:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BvzKz-0001Yi-Gb
	for ietf@megatron.ietf.org; Sat, 14 Aug 2004 10:16:49 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16244
	for <ietf@ietf.org>; Sat, 14 Aug 2004 10:16:47 -0400 (EDT)
Received: from [192.150.250.67] (helo=fuchsia.home)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BvzQL-0005It-Sg
	for ietf@ietf.org; Sat, 14 Aug 2004 10:22:24 -0400
Received: from delta.noi.kre.to (delta.ex0.home [192.168.192.22]) by
	fuchsia.home with ESMTP id i7EEGg80016584 for <ietf@ietf.org>;
	Sat, 14 Aug 2004 21:16:42 +0700 (ICT)
Received: from munnari.OZ.AU (localhost [127.0.0.1])
	by delta.noi.kre.to (8.12.9/8.11.6) with ESMTP id i7EE4xUB001045;
	Sat, 14 Aug 2004 21:05:04 +0700 (ICT)
From: Robert Elz <kre@munnari.OZ.AU>
To: "Eric A. Hall" <ehall@ehsco.com>
In-Reply-To: <411CDF3E.7000507@ehsco.com> 
References: <411CDF3E.7000507@ehsco.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 14 Aug 2004 21:04:59 +0700
Message-ID: <20537.1092492299@munnari.OZ.AU>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: ietf-822@imc.org, iesg@iesg.org, ietf@ietf.org
Subject: Re: Last Call: 'The APPLICATION/MBOX Media-Type' to Proposed
	Standard 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034

    Date:        Fri, 13 Aug 2004 11:33:18 -0400
    From:        "Eric A. Hall" <ehall@ehsco.com>
    Message-ID:  <411CDF3E.7000507@ehsco.com>

  | Others should note that RFC2048 is designed to facilitate registrations --
  | more definitions for common data-types are widely preferred over a
  | proliferation of "x-foo" media-types that result from high registration
  | barriers (read the intro to 2048 if you don't believe me) -- and that's
  | the limited objective of this proposal.

All that is fine, and not an issue with anyone.   The problem is that for
the tag to be meaningful, there must be at the very least a common
understanding of what it means and how it can be processed.   Better of
course is an actual published specification of the content format (somewhere).

Without that all you have is a label for a meaningless bucket of bits.

When I send a message how do I know whether it is appropriate to use the
new tag or not?   What content qualifies, and what does not?   Is it
sufficient if I'm sending a file whose name is "mbox"?   (Or which
has an extension of ".mbox" or similar).   Or is it necessary that the
content contain mail in some form?   If so, is it enough if I have a jpeg
file showing a mail box containing letters?

It is 100% useless to define a label without that referring to some
well understood content.

kre


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


From ietf-bounces@ietf.org  Sat Aug 14 22:52:05 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14071;
	Sat, 14 Aug 2004 22:52:04 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BwBDQ-0006v9-Jz; Sat, 14 Aug 2004 22:57:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BwB3j-0001wW-ED; Sat, 14 Aug 2004 22:47:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BwB2r-0001pa-T2
	for ietf@megatron.ietf.org; Sat, 14 Aug 2004 22:46:56 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13969
	for <ietf@ietf.org>; Sat, 14 Aug 2004 22:46:51 -0400 (EDT)
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BwB8N-0006qy-0Q
	for ietf@ietf.org; Sat, 14 Aug 2004 22:52:35 -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 i7F2k7wa015529
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Sat, 14 Aug 2004 22:46:08 -0400
Date: Sat, 14 Aug 2004 22:46:07 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Tony Hain <alh-ietf@tndh.net>
In-Reply-To: <200408131944.PAA13282@odie.av8.com>
Message-ID: <Pine.LNX.4.44.0408142230270.14357-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 2.7 (++)
X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813
Cc: "'Fleischman, Eric'" <eric.fleischman@boeing.com>, ietf@ietf.org
Subject: RE: Question about use of RSVP in Production Networks
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-Score: 2.7 (++)
X-Scan-Signature: 37af5f8fbf6f013c5b771388e24b09e7

On Fri, 13 Aug 2004, Tony Hain wrote:

> Dean Anderson wrote:
> > RSVP is a idea that doesn't cut the mustard in the real world. There are
> > several show-stopper problems with RSVP.
> 
> Propagating clueless FUD does not result in progress. 

That is true. Lets try to keep the FUD to a minimum.

> > 
> > 1) somewhat like multicast, anyone using RSVP is vulnerable to others
> > mis-using or mis-configuring RSVP. ISPs several AS's away can really screw
> > up things for other ISPs. Because of this, it is unwise to deploy it
> > because it requires too much trust in other ISPs.
> 
> Inter-provider trust is something the Internet has to deal with. The
> self-proclaimed gods of the ISP world bluster about how much smarter they
> are than the Bell-heads, but even the lowly Bell-heads figured this one out.

Literally true. Most choose not to trust providers they don't know
anything about and have no direct connectivity with. Some choose not to
trust those they have direct connectivity with. Some choose to run
alternate internal networks and not trust the other internal networks.  
But unrealistic amounts of trust is something you'd have to to deploy RSVP
in the general internet.  It has nothing to do with bluster or competition
with Bell-heads.

> > That relegates RSVP to the enterprise Lan, where it usually isn't needed.
> > Remember, RSVP is only useful if you have a congestion problem and need to
> > choose which packets to discard.  
> 
> RSVP is a signaling protocol. The policy installed in the routers with
> congested links is the one deciding what to discard, and it has the
> opportunity to take hints from that signaling if it chooses. 
> 
> Despite rumors to the contrary, most complex enterprise networks include
> non-LAN links, and even in the all-LAN case there are speed mismatches
> between old and new segments.

Complex, as in fortune 1000. fortune 5000? (no such list, I think, but you
get the idea).  There aren't actually that many organizations that have
more than one office.

> > If you have no congestion problem, then
> > you have no need of RSVP. 
> 
> Signaling is useful for more than QoS, though it is not clear that RSVP as
> currently defined is useful for signaling non-QoS related policy. 

Literally true. But its not clear that RSVP is useful for anything,
outside of some very limited situations.

> > However, having a congestion problem also opens
> > the question of the nature of the congestion and what is the best way to
> > deal that problem.  I was involved in a study done by Genuity and Cisco in
> > which the congestion problem was found to most often involve the tail
> > circuit--the link between the customer and the ISP.  The best solution for
> > this problem was found to be low latency queuing, not RSVP.
> 
> As you say it depends on the nature of the congestion, but also the nature
> of the application in the face of congestion. Generalizing all complex
> topologies to a congested uplink just leads to protocol decisions that are
> useless in the real world. 

I'm not generalizing topologies. I'm generalizing the type of problems
that need to be solved.  We have a whole lot of situations with tail
circuit congestion and comparatively few problems with large enterprise
congestion.  

> > 2) Unlike multicast, every hop end-to-end must use RSVP for it to be
> > useful. An RSVP tunnel is useless.
> 
> This is the type of BS that keeps useful tools out of the hands of those
> that need them, but don't have enough time to figure out the reality. The
> only points that need to pay attention to signaling are those where
> congestive loss is likely to occur. Even then, a smart implementation might
> only pay attention once a threshold has been crossed indicating that queues
> are building. 
> 
> > 
> > 3) RSVP doesn't detect certain kinds of problems that are important. For
> > example, a mid-span failure is not visible to RSVP.
> 
> WTFO! RSVP is a periodic signal, so it does detect and respond to mid-span
> events. 

Yes. Sooner or later RSVP will notice a link is down. But so will BGP and
OSPF. One wants this to happen within milliseconds in a QOS solution.  An
old saying somes to mind: "Same day service in a millisecond world".

> > While RSVP is important research, it is not a widely deployable
> > technology.
> 
> The reason the Internet has been successful is that each administrative
> domain gets to decide which technologies are deployable. Your decision that
> RSVP is not deployable does not automatically restrict if from wide
> deployment. 
> 
> In answer to Eric's original question, the FUD being spread through
> responses like Dean's have squelched what little RSVP had been deployed
> several years ago. That does not remove the need for a signaling protocol,
> as many WGs find they need to define new ones or variants. The bottom line
> is that the lack of a trust model makes operators suspicious of any external
> signal.

I didn't say that a signaling protocol wasn't needed. I said that RSVP 
doesn't cut the mustard for the needed protocol.

		--Dean


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


From ietf-bounces@ietf.org  Mon Aug 16 04:21:20 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA16523;
	Mon, 16 Aug 2004 04:21:20 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bwcpq-0004P8-It; Mon, 16 Aug 2004 04:27:19 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BwcdG-0003pE-Jw; Mon, 16 Aug 2004 04:14:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BwcZe-0003MW-AC
	for ietf@megatron.ietf.org; Mon, 16 Aug 2004 04:10:34 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA16137
	for <ietf@ietf.org>; Mon, 16 Aug 2004 04:10:32 -0400 (EDT)
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BwcfO-0004Eu-Ef
	for ietf@ietf.org; Mon, 16 Aug 2004 04:16:31 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id 4448E61B89
	for <ietf@ietf.org>; Mon, 16 Aug 2004 10:10: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 28452-01 for <ietf@ietf.org>;
	Mon, 16 Aug 2004 10:09:59 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain
	[127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id 7F74061B7D
	for <ietf@ietf.org>; Mon, 16 Aug 2004 10:09:59 +0200 (CEST)
Date: Mon, 16 Aug 2004 10:09:59 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: ietf@ietf.org
Message-ID: <E6A9A40824CE04C88001565C@[192.168.1.225]>
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
Content-Transfer-Encoding: 7bit
Subject: Administrative restructuring slides from the plenary available
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-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Content-Transfer-Encoding: 7bit

The slides used in the plenary to present the administrative restructuring 
at IETF 60 are available on http://www.iab.org/.

                    Harald




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


From ietf-bounces@ietf.org  Mon Aug 16 04:31:50 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA17815;
	Mon, 16 Aug 2004 04:31:49 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bwd00-0004eo-1V; Mon, 16 Aug 2004 04:37:49 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BwcqA-0005Ld-Rk; Mon, 16 Aug 2004 04:27:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bwcm4-0004mB-3V
	for ietf@megatron.ietf.org; Mon, 16 Aug 2004 04:23:24 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA16651
	for <ietf@ietf.org>; Mon, 16 Aug 2004 04:23:22 -0400 (EDT)
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bwcrp-0004QY-6z
	for ietf@ietf.org; Mon, 16 Aug 2004 04:29:21 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id B7DB161B89
	for <ietf@ietf.org>; Mon, 16 Aug 2004 10:22: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 28489-05 for <ietf@ietf.org>;
	Mon, 16 Aug 2004 10:22:51 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain
	[127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id CA52061B7D
	for <ietf@ietf.org>; Mon, 16 Aug 2004 10:22:50 +0200 (CEST)
Date: Mon, 16 Aug 2004 10:22:50 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: ietf@ietf.org
Message-ID: <69A43DBC09264699E7A80375@[192.168.1.225]>
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: 7bit
Subject: Request for volunteers: IETF list sergeant-at-arms
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-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Content-Transfer-Encoding: 7bit

Hi folks,

as we are nearing the time when we have a completed Administrative 
Restructuring considerations document available to put before the IETF, we 
have to make ready to manage the discussion to consensus.

We (IESG/IAB) have recommended using the IETF list (ietf@ietf.org) as the 
veichle for discussion - this is an issue that affects the IETF as a whole, 
so it seems appropriate to put discussion in a place that has traditionally 
been dedicated to IETF-wide issues.

However, this brings up a small issue: Traditionally, the IETF chair has 
been the moderator (with a rather light hand) of the IETF list. In this 
discussion, the IETF chair is an active participant in the work and the 
discussion; it seems inappropriate to ask the IETF chair to also decide 
whether or not posts are off-topic and/or abusive.

Luckily, the IETF list charter (RFC 3005) has a solution:

   The IETF Chair, the IETF Executive Director, or a sergeant-at-arms
   appointed by the Chair is empowered to restrict posting by a person,
   or of a thread, when the content is inappropriate and represents a
   pattern of abuse.

So - I'm hereby asking for volunteers for the job - which is a thankless 
one, but will not go unthanked!

You should:

- Be a regular reader of the IETF list (at least a few times a week)
- Be willing to monitor and moderate the list according to the rules in the 
IETF list charter (RFC 3005), rather than your personal opinion
- Be willing to commit to doing the job for at least 3 months
- Have a thick skin :-)

(Taking a vacation in the next 3 months does not disqualify - we can always 
find ways to deal with a crisis...)

Anyone who is willing to do this job - send me a note (privately), and I 
will pick one (or more, if I have a convincing argument that this is 
appropriate).

Thanks in advance!

                               Harald Alvestrand



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


From ietf-bounces@ietf.org  Mon Aug 16 10:24:13 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06468;
	Mon, 16 Aug 2004 10:24:13 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BwiV5-0002BZ-Hw; Mon, 16 Aug 2004 10:30:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BwiFk-0005TZ-5T; Mon, 16 Aug 2004 10:14:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BwiBx-0004jz-0Q
	for ietf@megatron.ietf.org; Mon, 16 Aug 2004 10:10:29 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05427
	for <ietf@ietf.org>; Mon, 16 Aug 2004 10:10:27 -0400 (EDT)
Received: from [194.246.101.61] (helo=box4.worldakt.com)
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1BwiHj-0001yu-Qq
	for ietf@ietf.org; Mon, 16 Aug 2004 10:16:29 -0400
Received: (qmail 16664 invoked from network); 16 Aug 2004 14:10:01 -0000
Received: from 161-47.us.ool.fr (HELO ?217.175.161.47?) (217.175.161.47)
	by 194.246.101.61 with SMTP; 16 Aug 2004 14:10:01 -0000
Mime-Version: 1.0 (Apple Message framework v618)
Content-Transfer-Encoding: 7bit
Message-Id: <2BE6C2F8-EF8E-11D8-8189-000A9567819A@php.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed
To: ietf@ietf.org
From: Michael Vergoz <descript@php.net>
Date: Mon, 16 Aug 2004 18:11:30 +0400
X-Mailer: Apple Mail (2.618)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Content-Transfer-Encoding: 7bit
Subject: Question about drafts
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: 7bit

Hello,

I am looking for informations about 'Howto suggest a draft' concerning 
IDMEF, IDWG.
I am working on C implementation of IDMEF.
The final idea is to allow people to read .idmef files on every systems.

Thank you,
Michael


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


From ietf-bounces@ietf.org  Mon Aug 16 22:54:21 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02436;
	Mon, 16 Aug 2004 22:54:21 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BwuD9-0002LJ-2l; Mon, 16 Aug 2004 23:00:31 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bwu2l-0001As-K2; Mon, 16 Aug 2004 22:49:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bwu1W-0000vt-I0; Mon, 16 Aug 2004 22:48:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02235;
	Mon, 16 Aug 2004 22:48:28 -0400 (EDT)
Received: from kcmso2.att.com ([192.128.134.71] helo=kcmso2.proxy.att.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bwu7Q-0002F2-Cq; Mon, 16 Aug 2004 22:54:38 -0400
Received: from maillennium.att.com ([135.25.114.99])
	by kcmso2.proxy.att.com (AT&T IPNS/MSO-5.5) with ESMTP id
	i7H2lrGZ027747; Mon, 16 Aug 2004 21:47:53 -0500
Received: from [135.210.24.231] (unknown[135.210.24.231](misconfigured sender))
	by maillennium.att.com (mailgw1) with ESMTP
	id <20040817024808gw1002eubge> (Authid: tony);
	Tue, 17 Aug 2004 02:48:08 +0000
Message-ID: <412171D8.9010201@att.com>
Date: Mon, 16 Aug 2004 22:47:52 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: en-us, en
MIME-Version: 1.0
References: <p06110437bd3d5d396de1@[10.20.30.249]>
	<411AB496.8080307@erols.com> <411BDE9B.7090706@att.com>
	<200408140040.i7E0e5Pk023772@turing-police.cc.vt.edu>
In-Reply-To: <200408140040.i7E0e5Pk023772@turing-police.cc.vt.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: 7bit
Cc: ietf-822@imc.org, iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: 'The APPLICATION/MBOX Media-Type' to Proposed
	Standard
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: 7bit

Valdis.Kletnieks@vt.edu wrote:

> Umm.. Tony?  I hate to say it, but if there have been several variants used in
> the wild, and the man pages for said variants document different formats,
> that's awfully close to "anecdotally defined" when you're doing a standard.

The claim in Appendix A is that there were no authoritative sources of 
documentation for the mbox formats and otherwise it's "only documented 
in anecdotal form". I'm sorry, but the the definitions ARE there, and 
ARE almost always authoritative for those systems.

This doesn't preclude there being other formats in the wild, nor does it 
preclude there being other tools on those same machines that conflict.

> For example, a Solaris 8 box across the hall says in 'man mail.local':
> ...
> 
> Any doubts that this whole mess is at best anecdotally defined can be dispelled by
> mentioning "Content-Length:" (interestingly enough, not even mentioned in the
> Solaris or Sendmail man pages, although the Sendmail source tree does mention
> that building on Solaris 2.3 or later will turn it on.  Of interest mostly because
> the Content-Length: is so easily broken by later >-stuffing/unstuffing or other
> similar conversion...

Because Solaris 8 is System Vr4-derived, you should look at 'man mail' 
for the definitive definition. You'll find Content-Length: documented there.

	Tony Hansen
	tony@att.com

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


From ietf-bounces@ietf.org  Tue Aug 17 10:43:01 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20081;
	Tue, 17 Aug 2004 10:43:01 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bx5H3-0005KA-Dt; Tue, 17 Aug 2004 10:49:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bx55p-0007y3-SW; Tue, 17 Aug 2004 10:37:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bx4yV-0006Y9-S5
	for ietf@megatron.ietf.org; Tue, 17 Aug 2004 10:30:07 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19103
	for <ietf@ietf.org>; Tue, 17 Aug 2004 10:30:05 -0400 (EDT)
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bx54W-000546-CW
	for ietf@ietf.org; Tue, 17 Aug 2004 10:36:21 -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 i7HEWFMW075521
	for <ietf@ietf.org>; Tue, 17 Aug 2004 16:32:15 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v619)
Content-Transfer-Encoding: 7bit
Message-Id: <E9BF093B-F059-11D8-994C-000A95CD987A@muada.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
To: ietf@ietf.org
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Tue, 17 Aug 2004 16:29:57 +0200
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea
Content-Transfer-Encoding: 7bit
Subject: List of standards
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-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Content-Transfer-Encoding: 7bit

Why is the list of internet standards so hard to find?

It seems to me this list deserves top ranking on the first page at 
www.ietf.org, but that's certainly not the case. (Try to find it and 
see what I mean.)


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


From ietf-bounces@ietf.org  Tue Aug 17 12:44:47 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28371;
	Tue, 17 Aug 2004 12:44:47 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bx7Av-0007mS-6F; Tue, 17 Aug 2004 12:51:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bx6nq-0000sO-PN; Tue, 17 Aug 2004 12:27:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bx6io-0007vI-It
	for ietf@megatron.ietf.org; Tue, 17 Aug 2004 12:22:02 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26232
	for <ietf@ietf.org>; Tue, 17 Aug 2004 12:21:59 -0400 (EDT)
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bx6op-00079T-2E
	for ietf@ietf.org; Tue, 17 Aug 2004 12:28:17 -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 i7HGK5J23581;
	Tue, 17 Aug 2004 09:20:05 -0700 (PDT)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost) by gra.isi.edu (8.9.3/8.8.6) id JAA07405;
	Tue, 17 Aug 2004 09:20:04 -0700 (PDT)
Date: Tue, 17 Aug 2004 09:20:04 -0700 (PDT)
Message-Id: <200408171620.JAA07405@gra.isi.edu>
To: ietf@ietf.org, iljitsch@muada.com
X-Sun-Charset: US-ASCII
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: braden@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Subject: Re: List of standards
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-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d


  *> From ietf-bounces@ietf.org  Tue Aug 17 07:43:22 2004
  *> Mime-Version: 1.0 (Apple Message framework v619)
  *> Content-Transfer-Encoding: 7bit
  *> To: ietf@ietf.org
  *> From: Iljitsch van Beijnum <iljitsch@muada.com>
  *> Date: Tue, 17 Aug 2004 16:29:57 +0200
  *> X-Spam-Score: 0.0 (/)
  *> X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea
  *> Content-Transfer-Encoding: 7bit
  *> Subject: List of standards
  *> List-Id: IETF-Discussion <ietf.ietf.org>
  *> X-ISI-4-32-5-MailScanner: Found to be clean
  *> X-ISI-4-30-3-MailScanner: Found to be clean
  *> X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham 
  *> 	version=2.63
  *> 
  *> Why is the list of internet standards so hard to find?
  *> 
  *> It seems to me this list deserves top ranking on the first page at 
  *> www.ietf.org, but that's certainly not the case. (Try to find it and 
  *> see what I mean.)
  *> 

It's not hard to find, actually. Try: http://www.rfc-editor.org/rfc.html

Bob Braden for the RFC Editor

  *> 
  *> _______________________________________________
  *> 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  Tue Aug 17 13:20:50 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01061;
	Tue, 17 Aug 2004 13:20:50 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bx7jp-00008d-78; Tue, 17 Aug 2004 13:27:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bx7Uj-0001Kk-1K; Tue, 17 Aug 2004 13:11:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bx7PA-0000G8-Fd; Tue, 17 Aug 2004 13:05:48 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29873;
	Tue, 17 Aug 2004 13:05:45 -0400 (EDT)
From: Valdis.Kletnieks@vt.edu
Received: from natted.sendmail.com ([63.211.143.38]
	helo=turing-police.cc.vt.edu)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bx7VD-0008FL-7X; Tue, 17 Aug 2004 13:12:03 -0400
Received: from turing-police.cc.vt.edu (IDENT:valdis@turing-police.cc.vt.edu
	[127.0.0.1])
	by turing-police.cc.vt.edu (8.13.1/8.13.1) with ESMTP id i7HH5Rx8019339;
	Tue, 17 Aug 2004 13:05:27 -0400
Message-Id: <200408171705.i7HH5Rx8019339@turing-police.cc.vt.edu>
X-Mailer: exmh version 2.7.1 07/26/2004 with nmh-1.1-RC3
To: Tony Hansen <tony@att.com>
In-Reply-To: Your message of "Mon, 16 Aug 2004 22:47:52 EDT."
	<412171D8.9010201@att.com> 
References: <p06110437bd3d5d396de1@[10.20.30.249]>
	<411AB496.8080307@erols.com> <411BDE9B.7090706@att.com>
	<200408140040.i7E0e5Pk023772@turing-police.cc.vt.edu>
	<412171D8.9010201@att.com>
Mime-Version: 1.0
Date: Tue, 17 Aug 2004 13:05:27 -0400
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: ietf-822@imc.org, iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: 'The APPLICATION/MBOX Media-Type' to Proposed
	Standard 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1850976222=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6

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

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

On Mon, 16 Aug 2004 22:47:52 EDT, Tony Hansen said:

> The claim in Appendix A is that there were no authoritative sources of 
> documentation for the mbox formats and otherwise it's "only documented 
> in anecdotal form". I'm sorry, but the the definitions ARE there, and 
> ARE almost always authoritative for those systems.

Somehow, I can't get thrilled by the concept of saying a format is documented
because we have (for example) 3 systems, and each has an authoritative
definition of the version it uses, and the definitions are incompatible (and
yes, the Solaris 'content-length:' scheme and '>from ' escaping are basically
incompatible - there exist messages that can't be converted from one to the
other without information loss).

> Because Solaris 8 is System Vr4-derived, you should look at 'man mail' 
> for the definitive definition. You'll find Content-Length: documented there.

It says:

     A letter is composed of some  header  lines  followed  by  a
     blank line followed by the message content. The header lines
     section of the letter consists of one  or  more  UNIX  post-
     marks:

           From     sender     date_and_time     [remote     from
          remote_system_name]

     followed by one or more standardized message header lines of
     the form:

           keyword-name: [printable text]

     where keyword-name  is  comprised  of  any  printable,  non-
     whitespace  characters  other  than  colon (`:'). A Content-
     Length: header line, indicating the number of bytes  in  the
     message  content  will  always  be present unless the letter
     consists of only header lines with  no  message  content.

For bonus points - is the 'crlf-crlf' between the header and the body included
in the Content-Length:?  There's other issues as well - what if the
Content-Length: is computed across a non-canonified message - how do
you send it across the wire?

'man mail' doesn't mention escaping a 'From ' inside a message,
except for this:

     The default mode for printing messages is  to  display  only
     those header lines of immediate interest. These include, but
     are not limited to,  the  UNIX  From  and  >From  postmarks,
     From:,  Date:,  Subject:,  and Content-Length: header lines,
     and any recipient header lines such as To:, Cc:,  Bcc:,  and
     so  forth.  After the header lines have been displayed, mail

Of course, that's because Solaris doesn't use '>From ' escaping
because it has Content-Length instead.

Should other systems trust the value of a Content-Length:?

Should other systems be required to include a Content-Length?

Should other systems escape a 'From ' iff there's no Content-Length?

What if an mbox file has a Content-Length on some items but not others?

How do you recover from a corrupted Content-Length?

So - where is the *one true canonical* definition of an mbox that actually
answers all these basic questions that an implementer *needs* to know the
answer to?




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

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

iD8DBQFBIjrWcC3lWbTT17ARAlEXAKDH7cYnFPMLSE+gwsFlc6ujQR/ztQCgr8em
b37bYcyQoBLO145lO3C7+gs=
=6BOg
-----END PGP SIGNATURE-----

--==_Exmh_-1395191580P--


--===============1850976222==
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

--===============1850976222==--



From ietf-bounces@ietf.org  Tue Aug 17 14:26:58 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05054;
	Tue, 17 Aug 2004 14:26:58 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bx8ln-0001Mb-Et; Tue, 17 Aug 2004 14:33:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bx8Wh-0004C7-0G; Tue, 17 Aug 2004 14:17:39 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bx8P6-0003IE-6N; Tue, 17 Aug 2004 14:09:48 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04198;
	Tue, 17 Aug 2004 14:09:46 -0400 (EDT)
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bx8V8-00016V-HK; Tue, 17 Aug 2004 14:16:03 -0400
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.34)
	id 1Bx8Os-000PI5-Mo; Tue, 17 Aug 2004 14:09:34 -0400
Date: Tue, 17 Aug 2004 14:09:34 -0400
From: John C Klensin <john-ietf@jck.com>
To: Valdis.Kletnieks@vt.edu, Tony Hansen <tony@att.com>
Message-ID: <9D7AFAAF50E30B30B3D610C2@scan.jck.com>
In-Reply-To: <200408171705.i7HH5Rx8019339@turing-police.cc.vt.edu>
References: <p06110437bd3d5d396de1@[10.20.30.249]> <411AB496.8080307@erols.com>
	<411BDE9B.7090706@att.com>
	<200408140040.i7E0e5Pk023772@turing-police.cc.vt.edu>
	<412171D8.9010201@att.com>
	<200408171705.i7HH5Rx8019339@turing-police.cc.vt.edu>
X-Mailer: Mulberry/3.1.6 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: 7bit
Cc: ietf-822@imc.org, iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: 'The APPLICATION/MBOX Media-Type' to
 Proposed	Standard
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: 7bit



--On Tuesday, 17 August, 2004 13:05 -0400
Valdis.Kletnieks@vt.edu wrote:

>...
> So - where is the *one true canonical* definition of an mbox
> that actually answers all these basic questions that an
> implementer *needs* to know the answer to?

Or, as an alternative, where is the set of required parameters
and values that would give the recipient at least a strong clue
as to which of many definitions and variations is in use?

To be clear about this, I think there are three choices which we
might prefer in descending order:

	(1) There is a single canonical "wire" format in which
	these things are transmitted.   It is the responsibility
	of the sender to get from whatever is used locally into
	that form and the responsibility of the recipient to get
	from that form into whatever is needed locally.  And the
	wire format is precisely defined, without handwaving or
	system-specific variations.
	
	(2) The content-type specifies a conceptual form
	("application/mbox") but has _required_ parameters that
	specify the specific form being transmitted.  The
	recipient does not require either out of band
	information or heuristics on the body part content
	itself to figure out what was received and whether local
	facilities exist to decode it.
	
	(3) These might as well be sent with
	application/octet-stream, with optional file name, etc.,
	information.

I just don't see any other options that are consistent with the
media type model.

     john




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


From ietf-bounces@ietf.org  Tue Aug 17 15:18:38 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09659;
	Tue, 17 Aug 2004 15:18:38 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bx9Zn-0002Sh-QL; Tue, 17 Aug 2004 15:24:57 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bx9PK-0006tP-MG; Tue, 17 Aug 2004 15:14:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bx9LW-0004nN-5u; Tue, 17 Aug 2004 15:10:10 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08759;
	Tue, 17 Aug 2004 15:10:08 -0400 (EDT)
Received: from goose.ehsco.com ([207.65.203.98])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bx9RZ-0002KS-5v; Tue, 17 Aug 2004 15:16:26 -0400
Received: from [192.168.0.2] (cable0-stm-219.gmpexpress.net [63.147.50.219])
	(using SSLv3 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client did not present a certificate)
	by goose.ehsco.com (Postfix ) with ESMTP id 5E1E2617F6;
	Tue, 17 Aug 2004 14:10:05 -0500 (CDT)
Message-ID: <412257D3.30606@ehsco.com>
Date: Tue, 17 Aug 2004 15:09:07 -0400
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7) Gecko/20040616
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
References: <p06110437bd3d5d396de1@[10.20.30.249]>
	<411AB496.8080307@erols.com>	<411BDE9B.7090706@att.com>	<200408140040.i7E0e5Pk023772@turing-police.cc.vt.edu>	<412171D8.9010201@att.com>	<200408171705.i7HH5Rx8019339@turing-police.cc.vt.edu>
	<9D7AFAAF50E30B30B3D610C2@scan.jck.com>
In-Reply-To: <9D7AFAAF50E30B30B3D610C2@scan.jck.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: 7bit
Cc: Tony Hansen <tony@att.com>, ietf-822@imc.org, Valdis.Kletnieks@vt.edu,
        iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: 'The APPLICATION/MBOX Media-Type' to Proposed
	Standard
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: 7bit


On 8/17/2004 2:09 PM, John C Klensin wrote:

> To be clear about this, I think there are three choices which we
> might prefer in descending order:
> 
> 	(1) There is a single canonical "wire" format in which
> 	these things are transmitted.

Such a specification would surely dictate "a series of message/rfc822
objects". But if we were to require that end-points perform conversion
into a neutral form, we might as well go the whole nickel and just say
"use multipart/digest", because that's where we'd end up after monhts of
beating on each other.

We'd still be in the same place we're at today, of course, because HTTP
and filesystem transfers aren't going to do mbox->digest conversion any
more than they are going to do EOL conversion or Content-Length calcs.
We'd still have opaque messaging databases that people wanted to transfer,
search, open and otherwise automate, but couldn't.

> 	(2) The content-type specifies a conceptual form
> 	("application/mbox") but has _required_ parameters that
> 	specify the specific form being transmitted.

Global parameters are useless if the parser is intelligent enough to
figure out the message structure independently. Given that such
intelligence is a prerequisite to having a half-baked parser, the global
parameters are always unnecessary.

Actually, global parameters are more than useless. What if we have a mixed
mbox file, where some messages are untagged BIG5 and others are untagged
8859-1, or we have some messages have VMS::Mail addresses and others have
MS/Mail addresses, or so forth? The global nature of global parameters
ignores the per-message reality of the mbox structure.

Global parameters can also be harmful if they conflict with reality.

> 	(3) These might as well be sent with
> 	application/octet-stream, with optional file name, etc.,
> 	information.

That's where we are now and we already now that's not working.


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


From ietf-bounces@ietf.org  Tue Aug 17 16:14:49 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12526;
	Tue, 17 Aug 2004 16:14:49 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BxAS9-0003V7-57; Tue, 17 Aug 2004 16:21:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BxAIf-0007UO-9w; Tue, 17 Aug 2004 16:11:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BxADj-0005Gw-MB; Tue, 17 Aug 2004 16:06:11 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12211;
	Tue, 17 Aug 2004 16:06:09 -0400 (EDT)
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BxAJn-0003N7-NX; Tue, 17 Aug 2004 16:12:28 -0400
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.34)
	id 1BxADb-000PvA-GF; Tue, 17 Aug 2004 16:06:03 -0400
Date: Tue, 17 Aug 2004 16:06:03 -0400
From: John C Klensin <john-ietf@jck.com>
To: "Eric A. Hall" <ehall@ehsco.com>
Message-ID: <294E85FB3BC16ACC1091D706@scan.jck.com>
In-Reply-To: <412257D3.30606@ehsco.com>
References: <p06110437bd3d5d396de1@[10.20.30.249]>
	<411AB496.8080307@erols.com>	<411BDE9B.7090706@att.com>
	<200408140040.i7E0e5Pk023772@turing-police.cc.vt.edu>
	<412171D8.9010201@att.com>
	<200408171705.i7HH5Rx8019339@turing-police.cc.vt.edu>
	<9D7AFAAF50E30B30B3D610C2@scan.jck.com> <412257D3.30606@ehsco.com>
X-Mailer: Mulberry/3.1.6 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8f374d0786b25a451ef87d82c076f593
Content-Transfer-Encoding: 7bit
Cc: Valdis.Kletnieks@vt.edu, ietf-822@imc.org, Tony Hansen <tony@att.com>,
        iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: 'The APPLICATION/MBOX Media-Type' to
 Proposed	Standard
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 200d029292fbb60d25b263122ced50fc
Content-Transfer-Encoding: 7bit

--On Tuesday, 17 August, 2004 15:09 -0400 "Eric A. Hall"
<ehall@ehsco.com> wrote:

>> To be clear about this, I think there are three choices which
>> we might prefer in descending order:
>> 
>> 	(1) There is a single canonical "wire" format in which
>> 	these things are transmitted.
> 
> Such a specification would surely dictate "a series of
> message/rfc822 objects". But if we were to require that
> end-points perform conversion into a neutral form, we might as
> well go the whole nickel and just say "use multipart/digest",
> because that's where we'd end up after monhts of beating on
> each other.
>...
>> 	(2) The content-type specifies a conceptual form
>> 	("application/mbox") but has _required_ parameters that
>> 	specify the specific form being transmitted.
> 
> Global parameters are useless if the parser is intelligent
> enough to figure out the message structure independently.
> Given that such intelligence is a prerequisite to having a
> half-baked parser, the global parameters are always
> unnecessary.

This is a minor point compared to the one below, and probably
not an issue here, but I can't let the above stand.  My
impression of the MIME design, from the beginning, was that I
should be able to inspect the content-type --including both the
primary type and any parameters-- before deciding whether to
retrieve and open the content of the body part.  Yes, we have
implementations and protocols that don't take advantage of that,
or that can take advantage of the content-type only and not the
parameters, but the MIME design, and hence the media type
design, is that I should be able to tell whether I can parse
(see below) the body part without opening it and applying
heuristics to it.

In addition, what you seem to mean by "intelligent enough to
figure out the message structure independently" is what I would
mean if I said "know most or all of the formats and apply
heuristics to figure out which one to apply".  We just don't do
that, at least knowingly and with standards-track media types.
You might rationally argue that this should be an exception if
you could demonstrate that a reasonable set of heuristics would
_always_ make the choice correctly, but that would require you
to document either the heuristics or all of the variations on
mbox and how to tell them apart (or both) -- something that
several people have claimed is basically impossible and that you
clearly haven't expressed a desire to do.

In that context, unless I completely misunderstand what is going
on here, the "...prerequisite to having a half-baked parser..."
assertion borders on the silly.   Take the example to which Tony
has been pointing.  Apparently the Solaris version of an mbox
format is well-documented and based on content length
information rather than key strings.   That implies that, if (i)
I know that what is coming is in that Solaris format and (ii) I
have a rather primitive parser that knows how to find and deal
with content lengths, then I can parse the format without any
ability to "figure out the structure" at all.   However, if I
attempt to apply that parser to something to uses key strings,
rather than lengths, or something that violates the assumptions
Solaris makes about what gets included in the length
computations, the parser is going to be bewildered at best and
yield silly results at worst -- and that is exactly what content
types and their parameters are intended to let receiving
applications guard against.

> Actually, global parameters are more than useless. What if we
> have a mixed mbox file, where some messages are untagged BIG5
> and others are untagged 8859-1, or we have some messages have
> VMS::Mail addresses and others have MS/Mail addresses, or so
> forth? The global nature of global parameters ignores the
> per-message reality of the mbox structure.
> 
> Global parameters can also be harmful if they conflict with
> reality.

That brings us to the main problem, or misunderstanding, or
strawman, depending on one's perspective.

I may be being excessively dense here, but, if I am, I seem to
have significant company.   I am not asking (or suggesting) that
you provide the information that would be required for
multipart/, e.g., the content-type and associated parameters
(such as charset, for your examples above) for each message
(much less, for multipart/digest, that you force everything into
the required subset of an RFC822 message body).  While I have
concerns that we didn't get multipart quite right and that it is
too late to fix it, those concerns don't interact with my
concern about application/mbox at all.

So let's move back a half-step.  To me, the essence of the mbox
format, conceptually, is that it consists of a sequence of blobs
that are normally interpreted as messages in some format or
other. You've made several convincing arguments that we should
see them as blobs, not as messages, and I (and I think others)
accepted them long ago.   I think that such a blob collection is
a reasonable thing to want to mail or otherwise use as a media
type.  And, again, I accept your argument that the blobs may not
be valid 822/2822 messages or encapsulated 2821 messages, and,
indeed, that there may be considerable format and content
heterogeneity from one blob to the next. 

Given that model, the key to an mbox format isn't the content of
the blobs, it is the system used to decompose an mbox into a
blob collection.  If this were a multipart structure, the
corresponding issue of interest would be whether the Boundary
parameter provided enough information to separate the parts.  It
would not be what was in each of the parts or even what _their_
content types were.  It would simply be the ability to separate
the aggregate mbox into separate blobs.

If I know that blobs are length-delimited according to some
specific set of rules, I have that information and can build a
trivial parser (and understand what it can't handle).   If I
know they are separated by indicator strings that obey some
specific set of rules, then I can build a trivial parser (and
understand what it can't handle).  And so on for different sets
of rules.   But, as far as I can tell, you don't want to give us
that information.  Instead, you want us to accept "well, it is
some sort of mbox format, and you either need to guess at how to
separate the blobs by examining the content or you need to get
that information out of band".   If that is what you intend this
specification to imply, IMnvHO, unacceptable for a
standards-track media type.

Finally, if you argue that global parameters are unacceptable as
a means of making the type of format/ de-blob-ing distinctions
outlined below, I suggest that you are not making a good case
for leaving the parameters (and associated information) out.
Instead, you are making a case that this registration should be
a family of, e.g.,
  application/mbox-solaris-v5-and-later
  application/mbox-sendmail-v2-v4
and similar things (examples made up).

       john 



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


From ietf-bounces@ietf.org  Tue Aug 17 16:26:34 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13028;
	Tue, 17 Aug 2004 16:26:34 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BxAdZ-0003ir-BI; Tue, 17 Aug 2004 16:32:53 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BxAVz-0005Wc-Rw; Tue, 17 Aug 2004 16:25:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BxASV-0003om-8K
	for ietf@megatron.ietf.org; Tue, 17 Aug 2004 16:21:27 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12836
	for <ietf@ietf.org>; Tue, 17 Aug 2004 16:21:24 -0400 (EDT)
Received: from backin5.merit.edu ([198.108.60.28])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BxAYY-0003dW-UW
	for ietf@ietf.org; Tue, 17 Aug 2004 16:27:44 -0400
Received: by backin5.merit.edu (Postfix, from userid 8935)
	id 7FB4B7E513; Tue, 17 Aug 2004 16:21:24 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
	by backin5.merit.edu (Postfix) with ESMTP
	id 6984629ADA; Tue, 17 Aug 2004 16:21:24 -0400 (EDT)
Date: Tue, 17 Aug 2004 16:21:24 -0400 (EDT)
From: Susan Harris <srh@merit.edu>
To: "Kevin C. Almeroth" <almeroth@cs.ucsb.edu>
In-Reply-To: <200408111932.i7BJWoxZ010269@jackson.cs.ucsb.edu>
Message-ID: <Pine.GSO.4.58.0408171619521.20216@backin5.merit.edu>
References: <200408111932.i7BJWoxZ010269@jackson.cs.ucsb.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Cc: ietf@ietf.org
Subject: Re: YATS? Re: T-shirts,
	and some suggestions for future 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-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370

> You know how many times I go to conferences and end up just
> leaving the bag or whatever the gift is in the hotel room?
> Every single one.
>
> Though, I must say, the bag from Salt Lake City is the best
> one I've ever been given and still use that.  So unless
> there is a really high quality bag that's better, why have
> more than one?
>
> T-shirts are great because they are replaced so frequently.

I've always thought a nice purse or make-up kit would be cool.

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


From ietf-bounces@ietf.org  Tue Aug 17 17:01:19 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14385;
	Tue, 17 Aug 2004 17:01:19 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BxBBA-0004E5-1S; Tue, 17 Aug 2004 17:07:39 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BxAzJ-0002Px-K4; Tue, 17 Aug 2004 16:55:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BxAyM-0002Gg-V6; Tue, 17 Aug 2004 16:54:23 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14176;
	Tue, 17 Aug 2004 16:54:20 -0400 (EDT)
Received: from goose.ehsco.com ([207.65.203.98])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BxB4S-00047T-8z; Tue, 17 Aug 2004 17:00:40 -0400
Received: from [192.168.0.2] (cable0-stm-219.gmpexpress.net [63.147.50.219])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client did not present a certificate)
	by goose.ehsco.com (Postfix ) with ESMTP id 0C1CA61806;
	Tue, 17 Aug 2004 15:54:20 -0500 (CDT)
Message-ID: <41227042.5030709@ehsco.com>
Date: Tue, 17 Aug 2004 16:53:22 -0400
From: "Eric A. Hall" <ehall@ehsco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7) Gecko/20040616
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
References: <p06110437bd3d5d396de1@[10.20.30.249]>
	<411AB496.8080307@erols.com>	<411BDE9B.7090706@att.com>
	<200408140040.i7E0e5Pk023772@turing-police.cc.vt.edu>
	<412171D8.9010201@att.com>
	<200408171705.i7HH5Rx8019339@turing-police.cc.vt.edu>
	<9D7AFAAF50E30B30B3D610C2@scan.jck.com> <412257D3.30606@ehsco.com>
	<294E85FB3BC16ACC1091D706@scan.jck.com>
In-Reply-To: <294E85FB3BC16ACC1091D706@scan.jck.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Content-Transfer-Encoding: 7bit
Cc: Valdis.Kletnieks@vt.edu, ietf-822@imc.org, Tony Hansen <tony@att.com>,
        iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: 'The APPLICATION/MBOX Media-Type' to
	Proposed	Standard
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Content-Transfer-Encoding: 7bit


On 8/17/2004 4:06 PM, John C Klensin wrote:

> In that context, unless I completely misunderstand what is going
> on here, the "...prerequisite to having a half-baked parser..."
> assertion borders on the silly.   Take the example to which Tony
> has been pointing.  Apparently the Solaris version of an mbox
> format is well-documented and based on content length
> information rather than key strings.

... it is well-defined for writing, but AFAIK the number of reliable
clients that depend on the presence of such data are zero.

This is the point really: Given that the database structure really is
undefined, and that any number of clients may have accessed the database
via ~NFS or via different mailers on the same local client (Pine and KMail
and ...), a half-baked mailer that wants to reliably read mbox data of any
kind will know better than to rely on Content-Length in isolation, and
will have to validate assumptions and check the clues before doing
anything substantive. This includes checking for EOL syntaxes, but also
includes things like default charsets for untagged data, default domains,
and so forth.

> Given that model, the key to an mbox format isn't the content of
> the blobs, it is the system used to decompose an mbox into a
> blob collection.

That's a function of the content parser and whatever task it is trying to
perform. The purpose of importing an mbox database into an IMAP store (as
is common with things like downloadable archives) is going to have several
different considerations and requirements than simple searching and
printing (as with local archives generated by ~Mozilla locally), but both
of them can be satisfied through basic sniff tests and local defaults.

Most of the spec work is appropriate and useful and arguably necessary for
*writing* to mbox files, especially if you are appending an existing file,
but even then it takes few smarts to figure out that you should write to
the existing content instead of druidic rules. Having said that, I'd love
to see a canonical authoritative format which could be referenced for such
purposes (not for transfers, but for parsers to use when they go about
generating content).

> Instead, you are making a case that this registration should be
> a family of, e.g.,
>   application/mbox-solaris-v5-and-later
>   application/mbox-sendmail-v2-v4

I hope not; unrecognized types match to application/octet-stream so many
types that nobody implements won't get us very far either.

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

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


From ietf-bounces@ietf.org  Tue Aug 17 17:48:44 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16775;
	Tue, 17 Aug 2004 17:48:44 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BxBv6-00059H-Sv; Tue, 17 Aug 2004 17:55:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BxBeR-00010e-TK; Tue, 17 Aug 2004 17:37:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BxBdD-0000e6-54
	for ietf@megatron.ietf.org; Tue, 17 Aug 2004 17:36:35 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16103
	for <ietf@ietf.org>; Tue, 17 Aug 2004 17:36:32 -0400 (EDT)
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BxBjH-0004t3-Cy
	for ietf@ietf.org; Tue, 17 Aug 2004 17:42: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 i7HLZljO032313
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Tue, 17 Aug 2004 17:35:57 -0400
Date: Tue, 17 Aug 2004 17:35:47 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: David Meyer <dmm@1-4-5.net>, <sra@isc.org>
In-Reply-To: <20040817042058.GA17957@1-4-5.net>
Message-ID: <Pine.LNX.4.44.0408171716550.31857-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 2.7 (++)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: dnsop@lists.uoregon.edu, ietf@ietf.org
Subject: Re: [dnsop] draft DNSOP minutes (IETF 60)
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-Score: 2.7 (++)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca

On Mon, 16 Aug 2004, David Meyer wrote:

> David Meyer:    inaddr-required draft, very little activity.
> 
> Rob Austein:    This one's come up before. One issue is that some
>                 people never get past draft filename. If you look at
>                 the title it doesn't match that. We have one extremely
>                 vocal opponent of this draft who tries very hard to
>                 trash the discussion of it - if he does that again we
>                 will kick him off the list. 

I presume this is directed at me, even though I'm not the only opponent of
this draft, nor even the only vocal opponent.  But before I assume this,
and renew complaints about inappropriate activity by Mr. Austein in
relation to keeping this draft alive despite lack of interest, and despite
numerous editing and factual errors in the draft, and complaints of his
inappropriate action against Av8 Internet and myself in refusing to accept
email from Av8 Internet, refusing not just me personally, but email from
all of Av8 Internet to his official IETF address sra@isc.org, and falsely
claiming that Av8 Internet's address hijacked.  There are legal
consequences for these abuses, and the IETF has been previously notified
of this.

In any case, neither I nor anyone else has "trashed discussion" of this
draft on the DNSOP list, nor would it be appropriate to kick any opponent
of this draft off the DNSOP list.  This threat is yet another in a series
of inappropriate actions by Mr. Austein in relation to this draft.  

The discussion by the opposition has centered around the false and
misleading statements in the draft describing the policies of other
organizations, and other errors.  Exposing those errors and
inconsistencies is not "trashing the discussion".

The title is misleading given the apparent contents of the draft, but that
is only because the draft is internally inconsistent between its early
paragraphs and its later paragraphs. These inconsistent statements were
added after the notion of making in-addr required was very widely rejected
by nearly all participants.  Despite the introductory paragraphs which
seem to say otherwise, the purpose of the authors in writing this draft is
to make in-addr required, and that proposal has been widely rejected,
despite Mr. Austein's efforts to keep the idea alive.


Dean Anderson
Av8 Internet, Inc



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


From ietf-bounces@ietf.org  Tue Aug 17 21:02:47 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28846;
	Tue, 17 Aug 2004 21:02:47 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BxEwt-0000aG-Ia; Tue, 17 Aug 2004 21:09:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BxEjn-0002QG-Iz; Tue, 17 Aug 2004 20:55:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BxEUb-00051F-Ah; Tue, 17 Aug 2004 20:39:53 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25956;
	Tue, 17 Aug 2004 20:39:51 -0400 (EDT)
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BxEad-0007xk-Qq; Tue, 17 Aug 2004 20:46:12 -0400
Received: from bbprime (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id i7I0cvj25699;
	Tue, 17 Aug 2004 17:38:57 -0700
Date: Tue, 17 Aug 2004 17:38:52 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <831445543.20040817173852@brandenburg.com>
To: John C Klensin <john-ietf@jck.com>
In-Reply-To: <294E85FB3BC16ACC1091D706@scan.jck.com>
References: <p06110437bd3d5d396de1@[10.20.30.249]> <411AB496.8080307@erols.com>
	<411BDE9B.7090706@att.com>
	<200408140040.i7E0e5Pk023772@turing-police.cc.vt.edu>
	<412171D8.9010201@att.com>
	<200408171705.i7HH5Rx8019339@turing-police.cc.vt.edu>
	<9D7AFAAF50E30B30B3D610C2@scan.jck.com> <412257D3.30606@ehsco.com>
	<294E85FB3BC16ACC1091D706@scan.jck.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: 7bit
Cc: ietf-822@imc.org, iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: 'The APPLICATION/MBOX Media-Type' to Proposed
	Standard
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-Score: 0.8 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Content-Transfer-Encoding: 7bit

John,

>> Global parameters are useless if the parser is intelligent
>> enough to figure out the message structure independently.
>> Given that such intelligence is a prerequisite to having a
>> half-baked parser, the global parameters are always
>> unnecessary.

JCK> This is a minor point compared to the one below, and probably
JCK> not an issue here, but I can't let the above stand.


Actually, I suspect you (and we) can and should.

A draft has been presented.  Numerous objections from experienced folks
have been lodged.  Is there more productive discussion likely?

This thread has not looked all that productive from the start and I am
hard-pressed to see how that is going to change.  Certainly countering
arguments about the benefits of standards for labeling, semantics, and
the like is not likely to convince anyone.  If they don't see it, the
only real question is what they are doing in this venue.

Now, the real reason for my posting:  If someone can summarize where
this thread is going and/or should go, I'd appreciate it.

d/
--
 Dave Crocker <dcrocker-at-brandenburg-dot-com>
 Brandenburg InternetWorking <www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>


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


From ietf-bounces@ietf.org  Tue Aug 17 23:01:45 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA03912;
	Tue, 17 Aug 2004 23:01:45 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BxGo4-0002P0-3P; Tue, 17 Aug 2004 23:08:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BxGfW-0004yy-4M; Tue, 17 Aug 2004 22:59:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BxGeJ-0004hO-F6; Tue, 17 Aug 2004 22:58:03 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA03665;
	Tue, 17 Aug 2004 22:58:00 -0400 (EDT)
Received: from avocet.mail.pas.earthlink.net ([207.217.120.50])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BxGkR-0002Jw-LW; Tue, 17 Aug 2004 23:04:24 -0400
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182]
	helo=[192.168.0.4])
	by avocet.mail.pas.earthlink.net with esmtp (Exim 3.33 #1)
	id 1BxGeB-0004Ba-00; Tue, 17 Aug 2004 19:57:55 -0700
In-Reply-To: <831445543.20040817173852@brandenburg.com>
References: <p06110437bd3d5d396de1@[10.20.30.249]>
	<411AB496.8080307@erols.com> <411BDE9B.7090706@att.com>
	<200408140040.i7E0e5Pk023772@turing-police.cc.vt.edu>
	<412171D8.9010201@att.com>
	<200408171705.i7HH5Rx8019339@turing-police.cc.vt.edu>
	<9D7AFAAF50E30B30B3D610C2@scan.jck.com> <412257D3.30606@ehsco.com>
	<294E85FB3BC16ACC1091D706@scan.jck.com>
	<831445543.20040817173852@brandenburg.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <621AC392-F0C2-11D8-928C-000393DB5366@cs.utk.edu>
Content-Transfer-Encoding: 7bit
From: Keith Moore <moore@cs.utk.edu>
Date: Tue, 17 Aug 2004 22:57:46 -0400
To: Dave Crocker <dcrocker@brandenburg.com>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>, ietf-822@imc.org,
        Keith Moore <moore@cs.utk.edu>, iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: 'The APPLICATION/MBOX Media-Type' to Proposed
	Standard
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Content-Transfer-Encoding: 7bit


On Aug 17, 2004, at 8:38 PM, Dave Crocker wrote:

>  If someone can summarize where
> this thread is going and/or should go, I'd appreciate it.

my recommendation to the author -

- do another edit on the draft, mostly for nits and clarity, and 
resubmit for Informational

- don't try to specify the application/mbox format in this document at 
all.  instead, point to various published definitions and descriptions 
(man pages, web pages, whatever) such as exist.

- for that matter, don't try to specify how best to generate mbox 
files.  that's out of scope.

- explicitly point out that there are varieties in how the format has 
been implemented which can affect interoperability.  (this should not 
be a showstopper, as there are varieties in how almost any other 
MIME-labeled format is implemented which can affect interoperability.)

- my preference is to not have parameters describing format variants at 
all, as they're highly unlikely to be used correctly and even less 
likely to be generated correctly.  if you must have parameters, make 
them optional.

- you might want to point out that a wide variety of mbox-reading tools 
generally manage to make sense of mbox files despite the variations.  
and yes, they barf sometimes.  some implementations' heuristics are 
better than others.  again, this is also true of Word, PDF, JPEG, 
PostScript, or any other format you could care to look at.  it's useful 
to be able to distinguish mbox files from other kinds of files, even if 
saying something is an mbox file is not perfectly precise.

- point out that the existence of an application/mbox label is not a 
recommendation that mbox files be used to transport groups of messages 
-  at least, not without first defining a new variant of mbox files 
that is transparent (no >From), reliable (no message boundary 
synchronization errors),  immune to variations in line terminator, and 
doesn't use character or line counts (no content-length).

- recommend base64 encoding as a default for transport of mbox files 
over email, since the encoder typically has no idea about the message 
contents and whether they might contain binary data.

my recommendation to everyone else -

let's wait for the revision and look at it then.  meanwhile, let's 
realize

- that having a way to label mbox fiiles is much more useful than not 
having one;

- that perfectly precise labels for anything are almost nonexistent in 
practice;

- that having an imprecise MIME label for mbox files probably won't 
degrade interop significantly over what it already is

- that there are probably better uses of our time (individually or 
collectively) than to define the perfect label for mbox files.

Keith


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


From ietf-bounces@ietf.org  Wed Aug 18 00:20:43 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA08613;
	Wed, 18 Aug 2004 00:20:43 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BxI2V-0003n2-VE; Wed, 18 Aug 2004 00:27:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BxHuB-0000bk-Ly; Wed, 18 Aug 2004 00:18:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BxHpb-0007Yh-Gp; Wed, 18 Aug 2004 00:13:47 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06781;
	Wed, 18 Aug 2004 00:13:44 -0400 (EDT)
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BxHvk-0003YG-83; Wed, 18 Aug 2004 00:20:08 -0400
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.34)
	id 1BxHpV-0002VQ-4p; Wed, 18 Aug 2004 00:13:41 -0400
Date: Wed, 18 Aug 2004 00:13:40 -0400
From: John C Klensin <john-ietf@jck.com>
To: Dave Crocker <dcrocker@brandenburg.com>
Message-ID: <35002D3A547B68DA226015C1@scan.jck.com>
In-Reply-To: <831445543.20040817173852@brandenburg.com>
References: <p06110437bd3d5d396de1@[10.20.30.249]>
	<411AB496.8080307@erols.com>	<411BDE9B.7090706@att.com>
	<200408140040.i7E0e5Pk023772@turing-police.cc.vt.edu>
	<412171D8.9010201@att.com>
	<200408171705.i7HH5Rx8019339@turing-police.cc.vt.edu>
	<9D7AFAAF50E30B30B3D610C2@scan.jck.com>
	<412257D3.30606@ehsco.com>	<294E85FB3BC16ACC1091D706@scan.jck.com>
	<831445543.20040817173852@brandenburg.com>
X-Mailer: Mulberry/3.1.6 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Content-Transfer-Encoding: 7bit
Cc: ietf-822@imc.org, iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: 'The APPLICATION/MBOX Media-Type' to
 Proposed	Standard
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Content-Transfer-Encoding: 7bit



--On Tuesday, 17 August, 2004 17:38 -0700 Dave Crocker
<dhc@dcrocker.net> wrote:

> John,
> 
>>> Global parameters are useless if the parser is intelligent
>>> enough to figure out the message structure independently.
>>> Given that such intelligence is a prerequisite to having a
>>> half-baked parser, the global parameters are always
>>> unnecessary.
> 
> JCK> This is a minor point compared to the one below, and
> probably JCK> not an issue here, but I can't let the above
> stand.
> 
> 
> Actually, I suspect you (and we) can and should.
> 
> A draft has been presented.  Numerous objections from
> experienced folks have been lodged.  Is there more productive
> discussion likely?
> 
> This thread has not looked all that productive from the start
> and I am hard-pressed to see how that is going to change.
> Certainly countering arguments about the benefits of standards
> for labeling, semantics, and the like is not likely to
> convince anyone.  If they don't see it, the only real question
> is what they are doing in this venue.
> 
> Now, the real reason for my posting:  If someone can summarize
> where this thread is going and/or should go, I'd appreciate it.

Well, I had planned to just stop after that note, on the theory
that the IESG should now have enough information to make
whatever decision they are inclined to make.   My personal
recommendation, I trust obviously, is that they should say "no"
to this particular draft as a proposed standard: for
standardization purposes, it just isn't specific enough about
what is being transmitted.

If I were giving advice to the author, it would pretty closely
follow what I understand Keith to be suggesting.   Withdraw this
document and the request that it be considered for PS.  Generate
a new document that is very specific about how much or how
little can be assumed when something arrives with this content
type, makes it explicit that the receiver had better be prepared
to handle any of the various mbox forms, and points to whatever
documentation or other materials that can be easily identified
and might help in constructing a receiver-processor.   I think
that document should be Informational, with a media type in some
non-IETF tree, but could personally live with a Proposed
Standard if the interoperability constraints, and any security
risks from guessing wrong about properties of the format were
extremely explicit.

Does that agree with your analysis, at least to a first order
approximation?

    john




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


From ietf-bounces@ietf.org  Wed Aug 18 00:32:01 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA09272;
	Wed, 18 Aug 2004 00:32:01 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BxIDQ-00040f-FD; Wed, 18 Aug 2004 00:38:25 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BxI2l-0002VQ-NT; Wed, 18 Aug 2004 00:27:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BxHwv-0001JY-Ad; Wed, 18 Aug 2004 00:21:21 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA08642;
	Wed, 18 Aug 2004 00:21:18 -0400 (EDT)
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BxI33-0003n1-9a; Wed, 18 Aug 2004 00:27:42 -0400
Received: from bbprime (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id i7I4Kcj06892;
	Tue, 17 Aug 2004 21:20:38 -0700
Date: Tue, 17 Aug 2004 21:20:34 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <1882306684.20040817212034@brandenburg.com>
To: John C Klensin <john-ietf@jck.com>
In-Reply-To: <35002D3A547B68DA226015C1@scan.jck.com>
References: <p06110437bd3d5d396de1@[10.20.30.249]> <411AB496.8080307@erols.com>
	<411BDE9B.7090706@att.com>
	<200408140040.i7E0e5Pk023772@turing-police.cc.vt.edu>
	<412171D8.9010201@att.com>
	<200408171705.i7HH5Rx8019339@turing-police.cc.vt.edu>
	<9D7AFAAF50E30B30B3D610C2@scan.jck.com> <412257D3.30606@ehsco.com>
	<294E85FB3BC16ACC1091D706@scan.jck.com>
	<831445543.20040817173852@brandenburg.com>
	<35002D3A547B68DA226015C1@scan.jck.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.8 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit
Cc: ietf-822@imc.org, iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: 'The APPLICATION/MBOX Media-Type' to Proposed
	Standard
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-Score: 0.8 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: 7bit

John,

JCK> Does that agree with your analysis, at least to a first order
JCK> approximation?


  well (harumph!) i can't let the question stand without answering it...

  I trust the assessments you folks have been making about the document,
  and I have not seen counter-arguments that looked at all persuasive.

  I also have not read the spec.
  
d/
--
 Dave Crocker <dcrocker-at-brandenburg-dot-com>
 Brandenburg InternetWorking <www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>


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


From ietf-bounces@ietf.org  Wed Aug 18 04:24:53 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA17560;
	Wed, 18 Aug 2004 04:24:53 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BxLqn-0007ak-Lt; Wed, 18 Aug 2004 04:31:18 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BxLh4-0003bf-Vt; Wed, 18 Aug 2004 04:21:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BxLbx-0002uf-Gc
	for ietf@megatron.ietf.org; Wed, 18 Aug 2004 04:15:57 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA17160
	for <ietf@ietf.org>; Wed, 18 Aug 2004 04:15:55 -0400 (EDT)
Received: from mx5.ukc.ac.uk ([129.12.21.36] helo=mx5.kent.ac.uk)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BxLi8-0007QM-G7
	for ietf@ietf.org; Wed, 18 Aug 2004 04:22:20 -0400
Received: from pelican.ukc.ac.uk ([129.12.200.26])
	by mx5.kent.ac.uk with esmtp (Exim 4.24)
	id 1BxLbC-0000VR-CO; Wed, 18 Aug 2004 09:15:10 +0100
Received: from pc2mmu01.ukc.ac.uk ([129.12.58.227])
	by pelican.ukc.ac.uk with esmtp (Exim 4.22)
	id 1BxLbB-0002tM-69; Wed, 18 Aug 2004 09:15:09 +0100
Date: Wed, 18 Aug 2004 09:15:38 +0100
From: Ian Cooper <ian@the-coopers.org>
To: Bob Braden <braden@ISI.EDU>
Message-ID: <6162E5B21C464C37B3D94F00@pc2mmu01.ukc.ac.uk>
In-Reply-To: <200408171620.JAA07405@gra.isi.edu>
References: <200408171620.JAA07405@gra.isi.edu>
X-Mailer: Mulberry/3.1.6 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-UKC-Mail-System: No virus detected
X-UKC-MailScanner-From: ian@the-coopers.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: List of standards
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-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 7bit

--On 17 August 2004 09:20 -0700 Bob Braden <braden@ISI.EDU> wrote:

>   *> From: Iljitsch van Beijnum <iljitsch@muada.com>
>   *>
>   *> Why is the list of internet standards so hard to find?
>   *>
>   *> It seems to me this list deserves top ranking on the first page at
>   *> www.ietf.org, but that's certainly not the case. (Try to find it and
>   *> see what I mean.)
>   *>
>
> It's not hard to find, actually. Try: http://www.rfc-editor.org/rfc.html

Seems to me one needs to know a lot about the differences between what's 
hosted by the IETF and the RFC Editor sites in order to know that for the 
material in question the user needs to go to the RFC Editor site (and then 
on to the "RFC Database" rather than any of the other options).

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


From ietf-bounces@ietf.org  Wed Aug 18 07:27:00 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28194;
	Wed, 18 Aug 2004 07:27:00 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BxOh1-0002gg-Ck; Wed, 18 Aug 2004 07:33:26 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BxOUe-0004pX-BX; Wed, 18 Aug 2004 07:20:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BxOQ5-0003nX-1c
	for ietf@megatron.ietf.org; Wed, 18 Aug 2004 07:15:53 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27515
	for <ietf@ietf.org>; Wed, 18 Aug 2004 07:15:52 -0400 (EDT)
Received: from sccrmhc11.comcast.net ([204.127.202.55])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BxOWG-0002Rm-Tk
	for ietf@ietf.org; Wed, 18 Aug 2004 07:22:18 -0400
Received: from dfnjgl21 (c-24-1-99-5.client.comcast.net[24.1.99.5])
	by comcast.net (sccrmhc11) with SMTP id <20040818111520011004llq8e>
	(Authid: sdawkins@comcast.net); Wed, 18 Aug 2004 11:15:21 +0000
Message-ID: <057b01c48514$a8aebac0$0400a8c0@DFNJGL21>
From: "Spencer Dawkins" <spencer@mcsr-labs.org>
To: <ietf@ietf.org>
References: <200408171620.JAA07405@gra.isi.edu>
	<6162E5B21C464C37B3D94F00@pc2mmu01.ukc.ac.uk>
Date: Wed, 18 Aug 2004 06:15:24 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Content-Transfer-Encoding: 7bit
Subject: Re: List of standards
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Spencer Dawkins <spencer@mcsr-labs.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Content-Transfer-Encoding: 7bit

Bob,

I think the intent of Iljitsch's note was that the "list of IETF
Standards" should appear in an obvious place (labeled "IETF
Standards") on http://www.ietf.org/ - if the label points to
http://www.rfc-editor.org/rfc.html, that's fine.

... leaving the question of "what standards" are actually standards,
and what standards are actually deployed, to NEWTRK :-)

But you guys are doing your part - the IETF website just needs to
catch up...

Spencer

From: "Ian Cooper" <ian@the-coopers.org>
To: "Bob Braden" <braden@ISI.EDU>
Cc: <ietf@ietf.org>
Sent: Wednesday, August 18, 2004 3:15 AM
Subject: Re: List of standards


> --On 17 August 2004 09:20 -0700 Bob Braden <braden@ISI.EDU> wrote:
>
> >   *> From: Iljitsch van Beijnum <iljitsch@muada.com>
> >   *>
> >   *> Why is the list of internet standards so hard to find?
> >   *>
> >   *> It seems to me this list deserves top ranking on the first
page at
> >   *> www.ietf.org, but that's certainly not the case. (Try to find
it and
> >   *> see what I mean.)
> >   *>
> >
> > It's not hard to find, actually. Try:
http://www.rfc-editor.org/rfc.html
>
> Seems to me one needs to know a lot about the differences between
what's
> hosted by the IETF and the RFC Editor sites in order to know that
for the
> material in question the user needs to go to the RFC Editor site
(and then
> on to the "RFC Database" rather than any of the other options).
>
> _______________________________________________
> 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 Aug 18 08:34:01 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01645;
	Wed, 18 Aug 2004 08:34:01 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BxPjw-0003wp-Le; Wed, 18 Aug 2004 08:40:28 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BxPXO-0005Xm-Jf; Wed, 18 Aug 2004 08:27:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BxPUt-0005DF-G8
	for ietf@megatron.ietf.org; Wed, 18 Aug 2004 08:24:55 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01263
	for <ietf@ietf.org>; Wed, 18 Aug 2004 08:24:54 -0400 (EDT)
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BxPb5-0003pN-RJ
	for ietf@ietf.org; Wed, 18 Aug 2004 08:31:21 -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 i7ICQvMW085291;
	Wed, 18 Aug 2004 14:26:57 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <057b01c48514$a8aebac0$0400a8c0@DFNJGL21>
References: <200408171620.JAA07405@gra.isi.edu>
	<6162E5B21C464C37B3D94F00@pc2mmu01.ukc.ac.uk>
	<057b01c48514$a8aebac0$0400a8c0@DFNJGL21>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <949666D2-F111-11D8-994C-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Wed, 18 Aug 2004 14:24:41 +0200
To: Spencer Dawkins <spencer@mcsr-labs.org>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: List of standards
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-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7bit

On 18-aug-04, at 13:15, Spencer Dawkins wrote:

> I think the intent of Iljitsch's note was that the "list of IETF
> Standards" should appear in an obvious place (labeled "IETF
> Standards") on http://www.ietf.org/ - if the label points to
> http://www.rfc-editor.org/rfc.html, that's fine.

Right.

There seems to be significant dissatisfaction about the fact that the 
general public doesn't know about the difference between RFCs and 
internet standards. I think a good deal of this ignorance is due the 
invisibility of the standards list. (Google only lists 43 links to the 
standards list, while the RFCs at www.ietf.org get 800, even though 
this isn't their official home.)

(And me not being able to find the list without help from Google isn't 
a good sign either. And yes, I did check the RFC Editor site but the 
links were too non-obvious.)


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


From ietf-bounces@ietf.org  Wed Aug 18 09:42:46 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05263;
	Wed, 18 Aug 2004 09:42:46 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BxQoT-0005AZ-5H; Wed, 18 Aug 2004 09:49:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BxQdh-0006l2-Rr; Wed, 18 Aug 2004 09:38:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BxQaS-0006Fe-Kn; Wed, 18 Aug 2004 09:34:44 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04804;
	Wed, 18 Aug 2004 09:34:42 -0400 (EDT)
Received: from smtp02.mrf.mail.rcn.net ([207.172.4.61])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BxQgg-00051W-JZ; Wed, 18 Aug 2004 09:41:10 -0400
X-Info: This message was accepted for relay by
	smtp02.mrf.mail.rcn.net as the sender used SMTP authentication
X-Trace: IimDIichsnUAVkeqqv/hxzyjetid5SKpR9D6ipRzKD8=
Received: from dhcp65-193-162-232.play.det.wayport.net ([65.193.162.232]
	helo=mail.play.det.wayport.net)
	by smtp02.mrf.mail.rcn.net with asmtp (Exim 3.35 #7)
	id 1BxQaQ-0006Rc-00; Wed, 18 Aug 2004 09:34:42 -0400
Received: from dhcp65-193-162-232.play.det.wayport.net (localhost [127.0.0.1])
	by mail.play.det.wayport.net with ESMTP
	id i7IDh4Pq008294(8.12.10/8.12.10/mail.blilly.com sendmail.mc.mail 1.18
	2004/05/15 07:23:45) ; Wed, 18 Aug 2004 09:43:04 -0400
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by dhcp65-193-162-232.play.det.wayport.net with ESMTP
	id i7IDh3PL008293(8.12.10/8.12.10/blilly.com submit.mc 1.1 2003/08/26
	22:21:33) ; Wed, 18 Aug 2004 09:43:03 -0400
Message-ID: <41235CE7.8030601@erols.com>
Date: Wed, 18 Aug 2004 09:43:03 -0400
From: Bruce Lilly <blilly@erols.com>
Organization: Bruce Lilly
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040803
X-Accept-Language: en-us
MIME-Version: 1.0
To: "Eric A. Hall" <ehall@ehsco.com>
References: <p06110437bd3d5d396de1@[10.20.30.249]>
	<411AB496.8080307@erols.com>	<411BDE9B.7090706@att.com>	<200408140040.i7E0e5Pk023772@turing-police.cc.vt.edu>	<412171D8.9010201@att.com>	<200408171705.i7HH5Rx8019339@turing-police.cc.vt.edu>
	<9D7AFAAF50E30B30B3D610C2@scan.jck.com> <412257D3.30606@ehsco.com>
In-Reply-To: <412257D3.30606@ehsco.com>
X-Enigmail-Version: 0.85.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Content-Transfer-Encoding: 7bit
Cc: ietf-822@imc.org, iesg@ietf.org, ietf@ietf.org
Subject: Re: Last Call: 'The APPLICATION/MBOX Media-Type' to Proposed
	Standard
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: ietf-822@imc.org, iesg@ietf.org, ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: 7bit

Eric A. Hall wrote:
> 
> On 8/17/2004 2:09 PM, John C Klensin wrote:
> 
> 
>>To be clear about this, I think there are three choices which we
>>might prefer in descending order:
>>
>>	(1) There is a single canonical "wire" format in which
>>	these things are transmitted.
> 
> 
> Such a specification would surely dictate "a series of message/rfc822
> objects". But if we were to require that end-points perform conversion
> into a neutral form, we might as well go the whole nickel and just say
> "use multipart/digest"

So far, so good.

> We'd still be in the same place we're at today, of course, because HTTP
> and filesystem transfers aren't going to do mbox->digest conversion any
> more than they are going to do EOL conversion or Content-Length calcs.
> We'd still have opaque messaging databases that people wanted to transfer,
> search, open and otherwise automate, but couldn't.

With the proposal as it stands, you'd also still have an opaque
blob, with the same problems.  But not with multipart/digest. And
why do you claim that there will not be any conversions; multipart/digest
is the lingua franca of message collections and it is unrealistic
to expect that some system is going to be able to reliably handle
an opaque blob constructed on a foreign system, in the face of
common transport modifications, and with no information regarding
the content of the blob other than an extremely vague label.

>>	(3) These might as well be sent with
>>	application/octet-stream, with optional file name, etc.,
>>	information.
> 
> 
> That's where we are now and we already now that's not working.

Since you have opposed parameters, what you are left with is
merely a subtype tag change from "octet-stream" to "mbox".  Now
could you please explain exactly what "'s not working" about
that, and precisely how *merely* changing the subtype tag to
"mbox", with no supplementary information is going to solve
whatever those problems are. In other words, what *exactly* is
the problem that you're trying to solve that cannot be addressed
by existing media types, and *precisely* how will the proposal
solve that problem?

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


From ietf-bounces@ietf.org  Wed Aug 18 12:55:04 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21390;
	Wed, 18 Aug 2004 12:55:04 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BxToc-0001NF-DC; Wed, 18 Aug 2004 13:01:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BxTWo-0004QQ-MY; Wed, 18 Aug 2004 12:43:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BxTNS-0002Oa-Ta
	for ietf@megatron.ietf.org; Wed, 18 Aug 2004 12:33:35 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19595
	for <ietf@ietf.org>; Wed, 18 Aug 2004 12:33:28 -0400 (EDT)
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BxTTh-0000pf-F1
	for ietf@ietf.org; Wed, 18 Aug 2004 12:39:58 -0400
X-BrightmailFiltered: true
Received: from franklin.cisco.com (franklin.cisco.com [171.70.156.17])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i7IGVUTt006084;
	Wed, 18 Aug 2004 09:31:33 -0700 (PDT)
Received: from gwzw2k (sjc-vpn3-183.cisco.com [10.21.64.183]) by
	franklin.cisco.com (8.8.6 (PHNE_17190)/CISCO.SERVER.1.2) with
	ESMTP id JAA12561; Wed, 18 Aug 2004 09:31:28 -0700 (PDT)
From: "Glen Zorn" <gwz@cisco.com>
To: "'Ian Cooper'" <ian@the-coopers.org>, "'Bob Braden'" <braden@ISI.EDU>
Date: Wed, 18 Aug 2004 09:30:56 -0700
Organization: Cisco Systems
Message-ID: <020f01c48540$cf2a6600$0202a8c0@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
In-Reply-To: <6162E5B21C464C37B3D94F00@pc2mmu01.ukc.ac.uk>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: RE: List of standards
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: gwz@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: 7bit

ietf-bounces@ietf.org <mailto:ietf-bounces@ietf.org> writes:

> --On 17 August 2004 09:20 -0700 Bob Braden <braden@ISI.EDU> wrote:
> 
>>   *> From: Iljitsch van Beijnum <iljitsch@muada.com>   *>
>>   *> Why is the list of internet standards so hard to find?   *>
>>   *> It seems to me this list deserves top ranking on the first page
>> at 
>>   *> www.ietf.org, but that's certainly not the case. (Try to find
>> it and 
>>   *> see what I mean.)
>>   *>
>> 
>> It's not hard to find, actually. Try:
>> http://www.rfc-editor.org/rfc.html
> 
> Seems to me one needs to know a lot about the differences between
> what's hosted by the IETF and the RFC Editor sites in order to know
> that for the material in question the user needs to go to the RFC
> Editor site (and then on to the "RFC Database" rather than any of the
> other options). 

Actually, there is a link on the IETF home page to "RFC Pages", so it
sems that one would really only need to be familiar w/the "RFC" acronym.
Is that too much to ask?

> 
> _______________________________________________
> 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-bounces@ietf.org  Wed Aug 18 13:18:35 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23111;
	Wed, 18 Aug 2004 13:18:34 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BxUBN-0001tR-3T; Wed, 18 Aug 2004 13:25:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BxTww-0001BT-Ik; Wed, 18 Aug 2004 13:10:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BxTr5-0008Bv-8p
	for ietf@megatron.ietf.org; Wed, 18 Aug 2004 13:04:07 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22068
	for <ietf@ietf.org>; Wed, 18 Aug 2004 13:04:04 -0400 (EDT)
Received: from mail.lumenvox.com ([206.169.193.45] helo=lv-svr.lumenvox.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BxTxK-0001a7-2D
	for ietf@ietf.org; Wed, 18 Aug 2004 13:10:35 -0400
Received: from PROGTHOMAS ([10.0.0.162]) by lv-svr.lumenvox.com with Microsoft
	SMTPSVC(5.0.2195.6713); Wed, 18 Aug 2004 09:56:20 -0700
From: "Thomas Gal" <ThomasGal@LumenVox.com>
To: <gwz@cisco.com>, "'Ian Cooper'" <ian@the-coopers.org>,
        "'Bob Braden'" <braden@ISI.EDU>
Date: Wed, 18 Aug 2004 10:03:28 -0700
Organization: LumenVox LLC
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
In-Reply-To: <2D0CA64CDC33E14DA7AB043B8CC4D2BB02340CA5@svr-exc.domain.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Thread-Index: AcSFQv4PRkhFcJq8RumZKr1asvG7RwAAgrRA
Message-ID: <LV-SVRi6bdVJWrGW6Ex000002d3@lv-svr.lumenvox.com>
X-OriginalArrivalTime: 18 Aug 2004 16:56:20.0796 (UTC)
	FILETIME=[495787C0:01C48544]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: RE: List of standards
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: ThomasGal@LumenVox.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-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Content-Transfer-Encoding: 7bit

Actually if you knew what it meant but weren't that familiar with the place
of an RFC(someone who's read 2 specs or something) you would assume IMHO
that an "Internet Standard" is NOT a "request for comments". 

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Glen
Zorn
Sent: Wednesday, August 18, 2004 9:31 AM
To: 'Ian Cooper'; 'Bob Braden'
Cc: ietf@ietf.org
Subject: RE: List of standards

ietf-bounces@ietf.org <mailto:ietf-bounces@ietf.org> writes:

> --On 17 August 2004 09:20 -0700 Bob Braden <braden@ISI.EDU> wrote:
> 
>>   *> From: Iljitsch van Beijnum <iljitsch@muada.com>   *>
>>   *> Why is the list of internet standards so hard to find?   *>
>>   *> It seems to me this list deserves top ranking on the first page 
>> at
>>   *> www.ietf.org, but that's certainly not the case. (Try to find it 
>> and
>>   *> see what I mean.)
>>   *>
>> 
>> It's not hard to find, actually. Try:
>> http://www.rfc-editor.org/rfc.html
> 
> Seems to me one needs to know a lot about the differences between 
> what's hosted by the IETF and the RFC Editor sites in order to know 
> that for the material in question the user needs to go to the RFC 
> Editor site (and then on to the "RFC Database" rather than any of the 
> other options).

Actually, there is a link on the IETF home page to "RFC Pages", so it sems
that one would really only need to be familiar w/the "RFC" acronym.
Is that too much to ask?

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


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


From ietf-bounces@ietf.org  Wed Aug 18 14:05:38 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26059;
	Wed, 18 Aug 2004 14:05:37 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BxUuq-0002qB-EE; Wed, 18 Aug 2004 14: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 1BxUjj-0000ml-6u; Wed, 18 Aug 2004 14:00:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BxUZH-0007iS-4S
	for ietf@megatron.ietf.org; Wed, 18 Aug 2004 13:50:17 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25207
	for <ietf@ietf.org>; Wed, 18 Aug 2004 13:49:25 -0400 (EDT)
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BxUfC-0002aJ-5C
	for ietf@ietf.org; Wed, 18 Aug 2004 13:55:55 -0400
Received: from [209.187.148.215] (helo=scan.jck.com)
	by bs.jck.com with esmtp (Exim 4.34)
	id 1BxUYd-0006ii-PI; Wed, 18 Aug 2004 13:49:07 -0400
Date: Wed, 18 Aug 2004 13:49:07 -0400
From: John C Klensin <john-ietf@jck.com>
To: ThomasGal@LumenVox.com, gwz@cisco.com,
        "'Ian Cooper'" <ian@the-coopers.org>, "'Bob Braden'" <braden@ISI.EDU>
Message-ID: <0EA62222FA4FB8838276D39C@scan.jck.com>
In-Reply-To: <LV-SVRi6bdVJWrGW6Ex000002d3@lv-svr.lumenvox.com>
References: <LV-SVRi6bdVJWrGW6Ex000002d3@lv-svr.lumenvox.com>
X-Mailer: Mulberry/3.1.6 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: RE: List of standards
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-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 7bit



--On Wednesday, 18 August, 2004 10:03 -0700 Thomas Gal
<ThomasGal@LumenVox.com> wrote:

> Actually if you knew what it meant but weren't that familiar
> with the place of an RFC(someone who's read 2 specs or
> something) you would assume IMHO that an "Internet Standard"
> is NOT a "request for comments". 

Sigh.  If this is the issue, could someone please initiate a
request to the IESG or Secretariat to change that link to read
"Internet Standards Index and RFC Materials" or something to
that effect (please take the wordsmithing offline too).   This
particular issue does not seem to justify bandwidth or
fine-tuning on this list.  

Really.

     john
   





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


From ietf-bounces@ietf.org  Wed Aug 18 17:50:41 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23121;
	Wed, 18 Aug 2004 17:50:41 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BxYQj-0003YS-Pw; Wed, 18 Aug 2004 17:57:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BxY57-0007GP-By; Wed, 18 Aug 2004 17:34:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BxXo7-0000Cw-Am
	for ietf@megatron.ietf.org; Wed, 18 Aug 2004 17:17:19 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18922
	for <ietf@ietf.org>; Wed, 18 Aug 2004 17:17:16 -0400 (EDT)
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BxXuL-0002Ez-BG
	for ietf@ietf.org; Wed, 18 Aug 2004 17:23: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 i7ILGgBO025999
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 18 Aug 2004 17:16:42 -0400
Date: Wed, 18 Aug 2004 17:16:42 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: ietf@ietf.org, <dnsop@lists.uoregon.edu>
Message-ID: <Pine.LNX.4.44.0408181706310.24908-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 2.7 (++)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Subject: Re: [dnsop] draft DNSOP minutes (IETF 60)
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-Score: 2.7 (++)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4

Another fake bounce from Mr. Austein.

It was also pointed out that Mr. Austein also fails to disclose his
conflict of interest with Av8 Internet according to the ISOC Code of
Conduct: http://www.isoc.org/members/codeconduct.shtml

  8. In  the case of financial or material conflict between personal and 
  professional interests, or between two professional interests,
  declare this conflict to all interested parties and if appropriate 
  in public.

Given the other abuses, this is probably a nit.

Dean Anderson
Av8 Internet, Inc

---------- Forwarded message ----------
Date: Tue, 17 Aug 2004 17:36:40 -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 Tue, 17 Aug 2004 17:35:57 -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-bounces@ietf.org  Thu Aug 19 04:02:18 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA10786;
	Thu, 19 Aug 2004 04:02:18 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bxhyi-0006Dx-61; Thu, 19 Aug 2004 04:08:56 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bxhhy-00086l-El; Thu, 19 Aug 2004 03:51:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bxhan-00072V-U0; Thu, 19 Aug 2004 03:44:14 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09546;
	Thu, 19 Aug 2004 03:44:12 -0400 (EDT)
From: ned.freed@mrochek.com
Received: from mauve.mrochek.com ([209.55.107.55])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BxhhA-0005ju-Km; Thu, 19 Aug 2004 03:50:50 -0400
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243)
	id <01LDTL7UN7LS00005R@mauve.mrochek.com>; Thu,
	19 Aug 2004 00:44:03 -0700 (PDT)
Date: Thu, 19 Aug 2004 00:43:24 -0700 (PDT)
In-reply-to: "Your message dated Tue, 17 Aug 2004 22:57:46 -0400"
	<621AC392-F0C2-11D8-928C-000393DB5366@cs.utk.edu>
To: Keith Moore <moore@cs.utk.edu>
Message-id: <01LDTVI1ZMY000005R@mauve.mrochek.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
References: <p06110437bd3d5d396de1@[10.20.30.249]> <411AB496.8080307@erols.com>
	<411BDE9B.7090706@att.com>
	<200408140040.i7E0e5Pk023772@turing-police.cc.vt.edu>
	<412171D8.9010201@att.com>
	<200408171705.i7HH5Rx8019339@turing-police.cc.vt.edu>
	<9D7AFAAF50E30B30B3D610C2@scan.jck.com> <412257D3.30606@ehsco.com>
	<294E85FB3BC16ACC1091D706@scan.jck.com>
	<831445543.20040817173852@brandenburg.com>
	<621AC392-F0C2-11D8-928C-000393DB5366@cs.utk.edu>
X-Spam-Score: 0.3 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Content-Transfer-Encoding: 7BIT
Cc: Dave Crocker <dcrocker@brandenburg.com>, ietf-822@imc.org,
        Keith Moore <moore@cs.utk.edu>, iesg@ietf.org,
        John C Klensin <john-ietf@jck.com>, ietf@ietf.org
Subject: Re: Last Call: 'The APPLICATION/MBOX Media-Type' to Proposed
	Standard
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Content-Transfer-Encoding: 7BIT

Keith, very nicely put. I am in complete agreement with everything you
say here.

				Ned

> On Aug 17, 2004, at 8:38 PM, Dave Crocker wrote:

> >  If someone can summarize where
> > this thread is going and/or should go, I'd appreciate it.

> my recommendation to the author -

> - do another edit on the draft, mostly for nits and clarity, and
> resubmit for Informational

> - don't try to specify the application/mbox format in this document at
> all.  instead, point to various published definitions and descriptions
> (man pages, web pages, whatever) such as exist.

> - for that matter, don't try to specify how best to generate mbox
> files.  that's out of scope.

> - explicitly point out that there are varieties in how the format has
> been implemented which can affect interoperability.  (this should not
> be a showstopper, as there are varieties in how almost any other
> MIME-labeled format is implemented which can affect interoperability.)

> - my preference is to not have parameters describing format variants at
> all, as they're highly unlikely to be used correctly and even less
> likely to be generated correctly.  if you must have parameters, make
> them optional.

> - you might want to point out that a wide variety of mbox-reading tools
> generally manage to make sense of mbox files despite the variations.
> and yes, they barf sometimes.  some implementations' heuristics are
> better than others.  again, this is also true of Word, PDF, JPEG,
> PostScript, or any other format you could care to look at.  it's useful
> to be able to distinguish mbox files from other kinds of files, even if
> saying something is an mbox file is not perfectly precise.

> - point out that the existence of an application/mbox label is not a
> recommendation that mbox files be used to transport groups of messages
> -  at least, not without first defining a new variant of mbox files
> that is transparent (no >From), reliable (no message boundary
> synchronization errors),  immune to variations in line terminator, and
> doesn't use character or line counts (no content-length).

> - recommend base64 encoding as a default for transport of mbox files
> over email, since the encoder typically has no idea about the message
> contents and whether they might contain binary data.

> my recommendation to everyone else -

> let's wait for the revision and look at it then.  meanwhile, let's
> realize

> - that having a way to label mbox fiiles is much more useful than not
> having one;

> - that perfectly precise labels for anything are almost nonexistent in
> practice;

> - that having an imprecise MIME label for mbox files probably won't
> degrade interop significantly over what it already is

> - that there are probably better uses of our time (individually or
> collectively) than to define the perfect label for mbox files.

> Keith


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

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


From ietf-bounces@ietf.org  Thu Aug 19 09:26:10 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01137;
	Thu, 19 Aug 2004 09:26:10 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bxn2A-0004Bu-NH; Thu, 19 Aug 2004 09:32:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BxmhS-0000NW-F3; Thu, 19 Aug 2004 09:11:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bx5VV-0004Dj-Am
	for ietf@megatron.ietf.org; Tue, 17 Aug 2004 11:04:13 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21728
	for <ietf@ietf.org>; Tue, 17 Aug 2004 11:04:11 -0400 (EDT)
Received: from jay.songbird.com ([208.184.79.253])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bx5bU-0005lr-3Q
	for ietf@ietf.org; Tue, 17 Aug 2004 11:10:27 -0400
Received: from Rincewind.ninebynine.org (jay.songbird.com [208.184.79.253])
	(authenticated)
	by jay.songbird.com (8.11.6/8.11.3) with ESMTP id i7HF3x031898;
	Tue, 17 Aug 2004 08:04:00 -0700
Message-Id: <5.1.0.14.2.20040817160243.02b26e48@127.0.0.1>
X-Sender: gk-bulk@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 17 Aug 2004 16:04:30 +0100
To: Iljitsch van Beijnum <iljitsch@muada.com>, ietf@ietf.org
From: Graham Klyne <GK@ninebynine.org>
In-Reply-To: <E9BF093B-F059-11D8-994C-000A95CD987A@muada.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
X-Mailman-Approved-At: Thu, 19 Aug 2004 09:11:24 -0400
Subject: Re: List of standards
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-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32

At 16:29 17/08/04 +0200, Iljitsch van Beijnum wrote:
>Why is the list of internet standards so hard to find?
>
>It seems to me this list deserves top ranking on the first page at 
>www.ietf.org, but that's certainly not the case. (Try to find it and see 
>what I mean.)

See:  http://www.rfc-editor.org/rfc/std/std1.txt

But I agree it's not obvious unless you know that STD 1 is the list of 
standards.

#g


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


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


From ietf-bounces@ietf.org  Thu Aug 19 17:53:56 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13134;
	Thu, 19 Aug 2004 17:53:56 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bxuxd-0008Kj-JO; Thu, 19 Aug 2004 18:00:42 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bxucd-0001E1-Qu; Thu, 19 Aug 2004 17:38:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BxuOS-0005zo-PF
	for ietf@megatron.ietf.org; Thu, 19 Aug 2004 17:24:20 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10748
	for <ietf@ietf.org>; Thu, 19 Aug 2004 17:24:18 -0400 (EDT)
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BxuUw-0007XQ-T9
	for ietf@ietf.org; Thu, 19 Aug 2004 17:31:04 -0400
Received: from [128.125.52.54] (vpn-052-054.usc.edu [128.125.52.54])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i7JLN4J11131;
	Thu, 19 Aug 2004 14:23:04 -0700 (PDT)
Message-ID: <41251A36.7050307@isi.edu>
Date: Thu, 19 Aug 2004 14:23:02 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Iljitsch van Beijnum <iljitsch@muada.com>
References: <E9BF093B-F059-11D8-994C-000A95CD987A@muada.com>
In-Reply-To: <E9BF093B-F059-11D8-994C-000A95CD987A@muada.com>
X-Enigmail-Version: 0.85.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: ietf@ietf.org
Subject: Re: List of standards
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="===============0413108456=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a

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

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



Iljitsch van Beijnum wrote:

> Why is the list of internet standards so hard to find?
> 
> It seems to me this list deserves top ranking on the first page at 
> www.ietf.org, but that's certainly not the case. (Try to find it and see 
> what I mean.)

It deserves top ranking on search engines; knowing that the IETF is a 
place to look for Internet standards is as obscure as knowing that 
they're a subset of something called "RFCs".

FWIW, Google gave the IETF as the top-ranked item of a search of 
"Internet standards", but the RFC Editor site, as well as other lists of 
STDs, is in the top 10 replies there.

Joe

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

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

iD8DBQFBJRo2E5f5cImnZrsRAhwmAKCvk5MwBcSPhGYi9VrMT/b95eOUJACdFXPl
9bocjdnHbt0J8zbRZ3sn6jo=
=DlYS
-----END PGP SIGNATURE-----

--------------enig81C4C6112B21E2657C83F8AD--


--===============0413108456==
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

--===============0413108456==--



From ietf-bounces@ietf.org  Thu Aug 19 19:42:30 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19861;
	Thu, 19 Aug 2004 19:42:30 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bxweh-0001th-MT; Thu, 19 Aug 2004 19:49:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BxwS8-0007MG-Lw; Thu, 19 Aug 2004 19:36:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BxwLq-0005px-5M
	for ietf@megatron.ietf.org; Thu, 19 Aug 2004 19:29:46 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19268
	for <ietf@ietf.org>; Thu, 19 Aug 2004 19:29:43 -0400 (EDT)
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BxwSL-0001fj-Hx
	for ietf@ietf.org; Thu, 19 Aug 2004 19:36:30 -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 i7JNVkMW003493;
	Fri, 20 Aug 2004 01:31:47 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <41251A36.7050307@isi.edu>
References: <E9BF093B-F059-11D8-994C-000A95CD987A@muada.com>
	<41251A36.7050307@isi.edu>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <9E6FFF26-F237-11D8-8FBB-00039388672E@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Fri, 20 Aug 2004 01:29:30 +0200
To: Joe Touch <touch@ISI.EDU>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: List of standards
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-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 7bit

On 19 aug 2004, at 23:23, Joe Touch wrote:

>> Why is the list of internet standards so hard to find?
>> It seems to me this list deserves top ranking on the first page at 
>> www.ietf.org

> It deserves top ranking on search engines;

So are you saying that we should put our trust into the undisclosed 
algorithms that try to recover relevance from random documents 
throughout the web for profit rather than the person managing the IETF 
website?

> knowing that the IETF is a place to look for Internet standards is as 
> obscure as knowing that they're a subset of something called "RFCs".

Neither of those is as obscure as the location of the actual list of 
internet standards. But who cares. Either someone will fix the problem 
and the world will a slightly better place, although probably not to a 
statistically significant degree, the problem won't be fixed and at 
least the link is in the mailing list archives, or someone will provide 
a good reason for the missing link and we'll all learn something. None 
of those possibilities are improved by discussing the matter further 
without the benefit of new facts.


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


From ietf-bounces@ietf.org  Thu Aug 19 21:58:10 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA25447;
	Thu, 19 Aug 2004 21:58:10 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bxym0-00049E-HG; Thu, 19 Aug 2004 22:04:57 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BxyVr-0007Ty-JD; Thu, 19 Aug 2004 21:48:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BxyQx-0006Ow-8R
	for ietf@megatron.ietf.org; Thu, 19 Aug 2004 21:43:11 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA25088
	for <ietf@ietf.org>; Thu, 19 Aug 2004 21:43:09 -0400 (EDT)
Received: from mail1.microsoft.com ([131.107.3.125])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BxyXT-0003wS-QJ
	for ietf@ietf.org; Thu, 19 Aug 2004 21:49:57 -0400
Received: from mailout2.microsoft.com ([157.54.1.120]) by mail1.microsoft.com
	with Microsoft SMTPSVC(6.0.3790.196); 
	Thu, 19 Aug 2004 18:42:47 -0700
Received: from red-imc-01.redmond.corp.microsoft.com ([157.54.9.102]) by
	mailout2.microsoft.com with Microsoft SMTPSVC(6.0.3790.0); 
	Thu, 19 Aug 2004 18:42:53 -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); Thu, 19 Aug 2004 18:41:42 -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); Thu, 19 Aug 2004 18:40: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
Date: Thu, 19 Aug 2004 18:41:49 -0700
Message-ID: <DAC3FCB50E31C54987CD10797DA511BA0A97D215@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: List of standards
thread-index: AcSGRkUYxBn34H9/SSSPOhBKRgUM4AAEFSgA
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: "Iljitsch van Beijnum" <iljitsch@muada.com>, "Joe Touch" <touch@ISI.EDU>
X-OriginalArrivalTime: 20 Aug 2004 01:40:51.0342 (UTC)
	FILETIME=[B9A982E0:01C48656]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
Subject: RE: List of standards
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-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: quoted-printable

> >> Why is the list of internet standards so hard to find?
> >> It seems to me this list deserves top ranking on the first page at
> >> www.ietf.org
>=20
> > It deserves top ranking on search engines;
>=20
> So are you saying that we should put our trust into the undisclosed
> algorithms that try to recover relevance from random documents
> throughout the web for profit rather than the person managing the IETF
> website?

We don't have to specifically trust the search engines, but we could
probably go a long way if each member of the IETF added a link in their
personal web page. Can we agree on which URL to point to?

-- Christian Huitema

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


From ietf-bounces@ietf.org  Fri Aug 20 16:31:16 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12130;
	Fri, 20 Aug 2004 16:31:16 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ByG9O-00088p-EP; Fri, 20 Aug 2004 16:38:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ByEv5-0007Tf-BD; Fri, 20 Aug 2004 15:19:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ByE9U-00070S-9b
	for ietf@megatron.ietf.org; Fri, 20 Aug 2004 14:30:12 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04200
	for <ietf@ietf.org>; Fri, 20 Aug 2004 14:30:05 -0400 (EDT)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ByEG4-0005V5-Qy
	for ietf@ietf.org; Fri, 20 Aug 2004 14:37:02 -0400
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-2.cisco.com with ESMTP; 20 Aug 2004 11:33:38 -0700
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com
	[171.71.163.14])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id i7KITTiQ019761;
	Fri, 20 Aug 2004 11:29:29 -0700 (PDT)
Received: from CSCOAMERA19540.cisco.com (stealth-10-32-244-222.cisco.com
	[10.32.244.222]) by mira-sjc5-b.cisco.com (MOS 3.4.5-GR)
	with SMTP id AWK72195; Fri, 20 Aug 2004 11:28:17 -0700 (PDT)
Message-Id: <6.1.2.0.2.20040820112432.04ef10f8@mira-sjc5-b.cisco.com>
X-Sender: fred@mira-sjc5-b.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0
Date: Fri, 20 Aug 2004 11:27:34 -0700
To: Iljitsch van Beijnum <iljitsch@muada.com>
From: Fred Baker <fred@cisco.com>
In-Reply-To: <E9BF093B-F059-11D8-994C-000A95CD987A@muada.com>
References: <E9BF093B-F059-11D8-994C-000A95CD987A@muada.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Cc: ietf@ietf.org
Subject: Re: List of standards
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-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370

At 04:29 PM 08/17/04 +0200, Iljitsch van Beijnum wrote:
>Why is the list of internet standards so hard to find?

I dunno. I tend to look for the most recent one in 
http://www.ietf.org/rfc/rfc-index.txt. The most recent one I find is 
http://www.ietf.org/rfc/rfc3700.txt.

Or, alternatively, I have a script that auto-generates the list for me.

     ftp://ftpeng.cisco.com/fred/rfc-index/rfc.html
     ftp://ftpeng.cisco.com/fred/rfc-index/std.html


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


From ietf-bounces@ietf.org  Fri Aug 20 21:29:53 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28884;
	Fri, 20 Aug 2004 21:29:53 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ByKoP-000535-Qh; Fri, 20 Aug 2004 21:36:54 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ByJdi-0003Op-F7; Fri, 20 Aug 2004 20:21:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ByJKk-0007B0-3x
	for ietf@megatron.ietf.org; Fri, 20 Aug 2004 20:02:10 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA23991
	for <ietf@ietf.org>; Fri, 20 Aug 2004 20:02:03 -0400 (EDT)
Received: from mail2.microsoft.com ([131.107.3.124])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1ByJRN-0003UA-Ll
	for ietf@ietf.org; Fri, 20 Aug 2004 20:09:03 -0400
Received: from mailout1.microsoft.com ([157.54.1.117]) by mail2.microsoft.com
	with Microsoft SMTPSVC(6.0.3790.196); 
	Fri, 20 Aug 2004 17:01:32 -0700
Received: from red-imc-02.redmond.corp.microsoft.com ([157.54.9.107]) by
	mailout1.microsoft.com with Microsoft SMTPSVC(6.0.3790.0); 
	Fri, 20 Aug 2004 17:01:40 -0700
Received: from win-imc-02.wingroup.windeploy.ntdev.microsoft.com
	([157.54.0.84]) by red-imc-02.redmond.corp.microsoft.com with
	Microsoft SMTPSVC(6.0.3790.0); Fri, 20 Aug 2004 17:01:29 -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, 20 Aug 2004 17:00:37 -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, 20 Aug 2004 17:01:37 -0700
Message-ID: <DAC3FCB50E31C54987CD10797DA511BA0A9F0B4C@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: List of standards
thread-index: AcSG9rCIA9PQ7qkGS7iAVmWFeVyGOgAGcNvQ
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: "Fred Baker" <fred@cisco.com>, "Iljitsch van Beijnum" <iljitsch@muada.com>
X-OriginalArrivalTime: 21 Aug 2004 00:00:37.0326 (UTC)
	FILETIME=[E3713EE0:01C48711]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
Subject: RE: List of standards
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-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: quoted-printable

> I dunno. I tend to look for the most recent one in
> http://www.ietf.org/rfc/rfc-index.txt. The most recent one I find is
> http://www.ietf.org/rfc/rfc3700.txt.

If I had to provide a pointer, I would probably use:
	http://www.rfc-editor.org/rfc.html
It is better organized and it provides more information than=20
	http://www.ietf.org/rfc.html
I would actually like to point to the IETF site for Internet Standards.
The IETF RFC page would be my first choice if it included a bit more
text to explain what an RFC is, and a pointer to the list of standards
maintains by the RFC editor.=20

-- Christian Huitema

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


From ietf-bounces@ietf.org  Tue Aug 24 09:50:03 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06072;
	Tue, 24 Aug 2004 09:50:03 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bzbh8-0000kV-5c; Tue, 24 Aug 2004 09:50:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bzacs-0003Sd-H4; Tue, 24 Aug 2004 08:42:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BzaQz-0000bB-Be
	for ietf@megatron.ietf.org; Tue, 24 Aug 2004 08:29:53 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00230
	for <ietf@ietf.org>; Tue, 24 Aug 2004 08:29:46 -0400 (EDT)
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BzaRL-0007Ws-1J
	for ietf@ietf.org; Tue, 24 Aug 2004 08:30:20 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i7OCT0X25742;
	Tue, 24 Aug 2004 15:29:00 +0300
Date: Tue, 24 Aug 2004 15:29:00 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: John Loughney <john.loughney@kolumbus.fi>
In-Reply-To: <pQY0fSbk71Jl.h6L3ff1c@mail.kolumbus.fi>
Message-ID: <Pine.LNX.4.44.0408241413520.23900-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a492040269d440726bfd84680622cee7
Cc: ietf@ietf.org
Subject: Re: hop-by-hop and router alert options [Re: Question about use of
 RSVP in Production Networks]
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-Score: 0.0 (/)
X-Scan-Signature: 7268a2980febc47a9fa732aba2b737ba

[[ I was hoping there would be more follow-ups on this thread, but 
apparently not... ]]

Combining two messages in one:

On Thu, 12 Aug 2004 18:00:50 -0500 "James M. Polk" <jmpolk@cisco.com>:
> Humor me (and a few others here) with a few listed mistakes you believe
> RSVP made in its design, with how you would redo them (either with a BB or
> just a better RSVP design).

Well, here's a couple -- hope it helps. Correct me if I'm mistaken:

 - RSVP doesn't have "network indication of support": the nodes keep 
spewing RSVP messages to the network even if every router is happily 
ignoring them, and the destination node does not support them.

Possible fix: have the signalling engine contact the local network 
administrator with a protocol to confirm if it supports the 
reservations or not.

 - path-coupled messages require significant processing at the
routers.  This probably needs to happen in "slow path", in software.  
A draft mentioned an implementation being able to support a whopping
(NOT!)  7000 sessions.  That works for the first hop, and possibly
even to a degree inside an enterprise where you can have software
based routers and not too many hosts, but it's not a useful model for
larger routers, deployed at more central places in the network.

Possible fix: instead of on-path processing, contact a node off-path,
which performs all the processing, checks the policies, etc., and
ensures that appropriate QoS metrics are configured at the appropriate
routers (these could be bulk DiffServ guarantees, more specific
reservations and whatever).

 - the policy checks are distributed to all the routers: the real
policy, within an administrative domain, is however made in a
centralized fashion, so it would be useful not to have to distribute
the policy to every router, but rather just process it in one place.

Possible fix: BB model provides this capability.

 - doing anything that crosses administrative domains for bandwidth or
other reservations requires that the operators have incentive to
provide these capabilities to outsiders, and hence the applicability
is restricted to a single administrative domain or the first hop.  
But when you operate inside a single domain, path-coupled signalling
does not seem necessary in the first place, you could just contact an
entity which would be trusted to make the reservations on your behalf.
The only alterntive is if significant amounts of money is transferred
based on the reservations, but that would make the mechanism a
non-starter for the users.

Possible fix: do signalling just inside an administrative domain, and
using a path-decoupled mechanism (whether a direct messaging with the
1st hop router or BB depends on the deployment).

 - the model where hosts or apps can reserve bandwidth or other
characteristics doesn't sit well with the operational models of ISPs.  
Such a reservation by definition eats from the shared resource;  
multiple reservations result in fewer people being use the the
originally shared resource.  On the other hand, the reservations
aren't useful unless sufficiently large about of BW is allocated to
them, and then the rest will suffer.  So, this would only be feasible
as a premium paid service.  But to achieve that, one could set up more
static resource allocations as well, or use other form of signalling.

Clarification needed: is the signalling protocol envisioned to be used
for paid premium service only?  If so, it may have some marginal use,
but I doubt the users are willing to pay for it so it would be
marginal.  If not, the protocol needs to be highly resistant to
users/apps requesting too large reservations (consider a
virus-infected host requesting very large reservations), security
models, etc.

 - if an operator would provide paid "premium" service, it would have
to acknowledge that its regular service is bad.  The competitors just
state that all of their service is equally good (than the premium
service) due to sufficient over-provisioning.  And if your own regular
service is good enough, the customers have no incentive to request
better service and pay you. Hence, a model where the customer has to
pay extra to get quality doesn't seem to cut it in general.

 - the first-hop only case is considerably easier because the user can
just shoot himself (not the others) in the foot.  I.e., it allows the
user to manage *his* traffic preferences on the link, i.e., he cannot
reserve from the bandwidth used by others.

.....

A local administrative domain could allow the local hosts to set up 
reservations, yes.  But in most cases, these networks are already 
over-provisioned except for a few special links (e.g., between the 
geographical sites, or the first hop) -- a well-defined environment 
which wouldn't require path-coupled signalling.

Remote administrative domains (including the ISPs) don't want
"foreign" nodes to request any reservations, unless they get direct
income from allowing that.  A free service just doesn't work, as the
Internet users are greedy by definition.  Best effort service is the
fairest service available under such circumstances.

And if you constrain yourself to just solving the problem for premium,
paid service (so that the users would not have incentive to request
special treatment unless they want to pay big bucks for it), it won't
attract sufficient economic interest (because if it would have, we'd
have RSVP already deployed and used widely already).  The
economic/operational tradeoffs to both the ISPs and the users just
aren't right.

So, I think the main point is that a model which requires payment
doesn't fly economically, and a model which doesn't require payment
doesn't fly operationally or technically because then everyone would
send in reservations and the result would be worse than best effort
because there wouldn't be enough for everyone. The reason why BB model
is better is because it centralizes the processing and policing, and
makes it easier to allow adopt QoS because it's less costly
(considering state, processing, etc.) in the routers than path-coupled
signalling.

On Fri, 13 Aug 2004, John Loughney wrote:
> > Of course.  Then why this wasn't the first thing NSIS did after going
> > for on-path signalling, or didn't I just manage to find it?  
> 
> NSIS was specifically charged to by the Transport ADs to work on
> on-path signaling.

That'll certainly focus the work, but the question is whether that 
focus is useful or not.

> > I really really hope that there has been a problem statement...
> 
> Why? I've generally found that problem statement documents have
> limited usefulness.

That might help in understanding the problems better.  One part of
that is identifying what problems the earlier solutions aimed to
solved and why they did not succeed (at least to certain
expectations).  I saw some analysis in
draft-ietf-nsis-signalling-analysis-04.txt when I quick read it, but
it seemed to be lacking real, operational input about the operational
and deployment problems, and was looking just the issues with the
protocol on its own.

Based on the direction where NSIS seems to be heading, the result is
likely going to be a slightly fancier version of RSVP .. which isn't
going to be terribly useful, except for those few who are already
using RSVP.

> > Further point where you can use path-coupled signalling, you mean?  
> > Not really, as there seems to be something seriously broken if you
> > need set up priorization except in well-defined points in the network.  
> > And to achieve that, you could use a "bandwidth broker": either it's
> > able to set up the required bandwidth (it's in the same site, or at a
> > site your site has a roaming agreement with), or it isn't and the
> > approach is going to fail in any case, because the sites out in the
> > Internet don't want outsiders to request bandwidth allocations.
> 
> As you know from IPv6 discussions, people's view of what constitutes
> a site is very different. It is not a well defined term. 

I don't see why it would need to be well-defined, all you'd need to do
is ask a "bandwidth broker" at your site, by finding out its address
using one of many option (you don't need to know the actual definition
of the site to do that, or the span of the site).

> NAT & FW traversal is very difficult, especially for signalling
> incoming connections. We have documentation, if you are interested.

Why would the administrator of the firewall trust the user or an
application running on the user's laptop to "behave well", i.e., punch
holes in the firewall?

NAT traversal is more trickier esp. inbound, but we already have a 
large number of solutions aiming to achieve exactly that, among them 
ones which provide non-encumbered IPv6 connectivity through the NATs, 
and then the problem would be fixed automatically.
 
> Also, there is no standard bw broker. Hoping that there was doesn't
> help. Currently deployed bw brokers have scalability problems,
> especially if they are meant to scale Internet-wide.

I don't know if there are ones, but that certainly wouldn't be a
show-stopper if there was a decision that this was the way to go.

All the approaches have scalabililiyu problems, especially if they are 
meant to scale Internet-wise .. especially RSVP-like path-coupled 
techniques.  That's the point.  Any design which you'd like to scale 
Internet-wise is probably broken, and especially so if it requires 
processing at the intermediate nodes.
 
> > True enough, I had my operator hat on ;-).  My mind just boggled when
> > I started to realize that some part of the IETF is still in denial on
> > why RSVP didn't go through, and is now in the process of reinventing
> > it .. wasting a lot of time and effort that could be much better spent
> > on making an operationally more feasible system to provide these
> > reservations in a well-defined, constrained points of the network.
> 
> Interestingly enough, there are operators involved in the NSIS
> discussions.  

I wasn't referring to 3GPP operators ;-)  (who are probably interested
in this for the first hop purposes, or for the first+last hop
purposes, where other methods might work nicely as well)

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




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


From ietf-bounces@ietf.org  Tue Aug 24 13:20:10 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24591;
	Tue, 24 Aug 2004 13:20:10 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BzeyW-00054v-SB; Tue, 24 Aug 2004 13:20:49 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bzdzq-0001gl-AT; Tue, 24 Aug 2004 12:18:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BzdfG-0005aE-Rp
	for ietf@megatron.ietf.org; Tue, 24 Aug 2004 11:56:50 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17018
	for <ietf@ietf.org>; Tue, 24 Aug 2004 11:56:43 -0400 (EDT)
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bzdfj-0003Dt-Lt
	for ietf@ietf.org; Tue, 24 Aug 2004 11:57:20 -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 i7OFwh6v050496;
	Tue, 24 Aug 2004 17:58:44 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <Pine.LNX.4.44.0408241413520.23900-100000@netcore.fi>
References: <Pine.LNX.4.44.0408241413520.23900-100000@netcore.fi>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <2949ADB6-F5E6-11D8-90CB-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Tue, 24 Aug 2004 17:56:29 +0200
To: Pekka Savola <pekkas@netcore.fi>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: hop-by-hop and router alert options
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-Score: 0.0 (/)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5
Content-Transfer-Encoding: 7bit

On 24-aug-04, at 14:29, Pekka Savola wrote:

> [[ I was hoping there would be more follow-ups on this thread, but
> apparently not... ]]

Be careful what you wish for...

First of all, allow me to emphatically NOT support your quest for 
removal of the router alert option. While I agree with many of your 
points, removing something that is both in use now (however localized) 
and may be beneficial to have in the future is not the right thing to 
do.

I think that if you want to provide better / more scalable QoS across 
the internet, it's better to start from scratch rather than try to cram 
RSVP into a completely new architecture.

>  - the model where hosts or apps can reserve bandwidth or other
> characteristics doesn't sit well with the operational models of ISPs.

Things change. ISPs are used to that. (They may whine, though.)

> Such a reservation by definition eats from the shared resource;

That's certainly not a given. If I make a phone call, my 64 kbps isn't 
taken from anyone else using the phone network, but from the pool of 
available unused capacity. You could do the same in an IP network, and 
you probably should or your regular customers will walk away.

> multiple reservations result in fewer people being use the the
> originally shared resource.  On the other hand, the reservations
> aren't useful unless sufficiently large about of BW is allocated to
> them, and then the rest will suffer.  So, this would only be feasible
> as a premium paid service.

That's not necessarily true either. Sure, there are applications that 
want/need huge amounts of bandwidth that they will want to reserve. But 
there are also applications that need a certain amount of low-delay, 
low-jitter bandwidth, where the problem isn't the amount of bandwidth, 
but making it low-delay and low-jitter (which you can't do for ALL your 
bandwidth if you run close to capacity for even conservative 
definitions of "close"). (And remember: there is always a bottleneck. 
Always.)

> Clarification needed: is the signalling protocol envisioned to be used
> for paid premium service only?  If so, it may have some marginal use,
> but I doubt the users are willing to pay for it so it would be
> marginal.  If not, the protocol needs to be highly resistant to
> users/apps requesting too large reservations (consider a
> virus-infected host requesting very large reservations), security
> models, etc.

What we see today is that average home users eat a lot of bandwidth. 
Even with today's prices that gets expensive. The problem is that users 
REALLY don't like to pay for volume or be restricted in any way. An 
interesting approach here would be to allow users to use as much 
capacity as the network can support (yes, at 100% utilization) so the 
file sharers are happy, but at the same time provide a premium service 
that bypasses the thus created congestion. This doesn't have to be a 
paid-for thing: you could simply make the first 100 kbps that a user 
uses premium and everything on top of that bulk.

This would require per-user policers (probably several) but we really 
need those anyway (and smart versions too) to be able to do something 
about denial of service.

(We also need to work on the "packet loss is congestion" assumption 
though, as even a little packet loss (unavoidable for a bulk service) 
kills TCP. Having to over-provision just because congestion management 
is too stupid is sub-optimal.)

>  - the first-hop only case is considerably easier because the user can
> just shoot himself (not the others) in the foot.  I.e., it allows the
> user to manage *his* traffic preferences on the link, i.e., he cannot
> reserve from the bandwidth used by others.

But having whatever the access speed happens to be as your limit is 
often not the best choice.

> Remote administrative domains (including the ISPs) don't want
> "foreign" nodes to request any reservations, unless they get direct
> income from allowing that.

Well, every network in the path between two arbitrary endpoints is 
always directly or indirectly paid by one of the endpoints. So if both 
endpoints want this service, their respective ISPs (and ISPs of ISPs) 
have an incentive to provide it.

> Best effort service is the fairest service available under such 
> circumstances.

Life isn't fair.  :-)  You REALLY don't want to do something 
interactive on a small pipe that you share with some p2p file sharers 
and have everyone receive "fair" packet loss percentages and delay.

I do agree that it only makes sense to implement all of this QoS stuff 
if and when different service levels make sense. For a while, it looked 
like it didn't, but I don't think over-provisioning can go on forever, 
especially now that we have both more bulk traffic and traffic that 
really wants QoS constraints.


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


From ietf-bounces@ietf.org  Tue Aug 24 13:27:16 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25297;
	Tue, 24 Aug 2004 13:27:16 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bzf5M-0005Ep-8h; Tue, 24 Aug 2004 13:27:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BzeTq-0000ZG-PX; Tue, 24 Aug 2004 12:49:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bze43-0002I0-0m
	for ietf@megatron.ietf.org; Tue, 24 Aug 2004 12:22:27 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18659
	for <ietf@ietf.org>; Tue, 24 Aug 2004 12:22:19 -0400 (EDT)
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bze4V-0003dt-6c
	for ietf@ietf.org; Tue, 24 Aug 2004 12:22:56 -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 i7OGLNJ07994;
	Tue, 24 Aug 2004 09:21:23 -0700 (PDT)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost) by gra.isi.edu (8.9.3/8.8.6) id JAA10184;
	Tue, 24 Aug 2004 09:21:23 -0700 (PDT)
Date: Tue, 24 Aug 2004 09:21:23 -0700 (PDT)
Message-Id: <200408241621.JAA10184@gra.isi.edu>
To: john.loughney@kolumbus.fi, pekkas@netcore.fi
X-Sun-Charset: US-ASCII
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: braden@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc: ietf@ietf.org
Subject: Re: hop-by-hop and router alert options [Re: Question about use of
 RSVP in Production Networks]
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-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab

  *> 
  *>  - RSVP doesn't have "network indication of support": the nodes keep 
  *> spewing RSVP messages to the network even if every router is happily 
  *> ignoring them, and the destination node does not support them.
  *> 

Pekka,

Well, actually, that's not true.  RSVP does have mechanisms to detect
nodes that do not support it, and nodes that do support it but fail
to respond.

  *> Possible fix: have the signalling engine contact the local network 
  *> administrator with a protocol to confirm if it supports the 
  *> reservations or not.

This is an ideal application of RFC 3751.


  *> 
  *>  - path-coupled messages require significant processing at the
  *> routers.  This probably needs to happen in "slow path", in software.  
  *> A draft mentioned an implementation being able to support a whopping
  *> (NOT!)  7000 sessions.  That works for the first hop, and possibly
  *> even to a degree inside an enterprise where you can have software
  *> based routers and not too many hosts, but it's not a useful model for
  *> larger routers, deployed at more central places in the network.
  *> 

Please see RFC 2998 and RFC 3175.

 *> Possible fix: instead of on-path processing, contact a node off-path,
  *> which performs all the processing, checks the policies, etc., and
  *> ensures that appropriate QoS metrics are configured at the appropriate
  *> routers (these could be bulk DiffServ guarantees, more specific
  *> reservations and whatever).
  *> 
  *>  - the policy checks are distributed to all the routers: the real
  *> policy, within an administrative domain, is however made in a
  *> centralized fashion, so it would be useful not to have to distribute
  *> the policy to every router, but rather just process it in one place.
  *> 
  *> Possible fix: BB model provides this capability.

RSVP does not put the policy in every router. Have you ever heard
of COPS?

The rest of your message seems to move away from tell us what
is wrong with RSVP in particular and path-coupled signaling in
general, to telling us what is wrong with Integrated Service.
Those are old, and endless, arguments, but they don't seem to
have anything to do with the topic you started on.

Bob Braden

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


From ietf-bounces@ietf.org  Wed Aug 25 03:41:44 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA21015;
	Wed, 25 Aug 2004 03:41:44 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BzsQO-0003ma-H6; Wed, 25 Aug 2004 03:42:28 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bzriz-0001oV-HW; Wed, 25 Aug 2004 02:57:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BzrVs-0008OY-QO
	for ietf@megatron.ietf.org; Wed, 25 Aug 2004 02:44:05 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA18377
	for <ietf@ietf.org>; Wed, 25 Aug 2004 02:43:58 -0400 (EDT)
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BzrWQ-0002vj-H1
	for ietf@ietf.org; Wed, 25 Aug 2004 02:44:42 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i7P6hEG17088;
	Wed, 25 Aug 2004 09:43:14 +0300
Date: Wed, 25 Aug 2004 09:43:14 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Bob Braden <braden@ISI.EDU>
In-Reply-To: <200408241621.JAA10184@gra.isi.edu>
Message-ID: <Pine.LNX.4.44.0408250903330.16339-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f
Cc: ietf@ietf.org, john.loughney@kolumbus.fi
Subject: Re: hop-by-hop and router alert options [Re: Question about use of
 RSVP in Production Networks]
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-Score: 0.0 (/)
X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027

On Tue, 24 Aug 2004, Bob Braden wrote:
>   *>  - RSVP doesn't have "network indication of support": the nodes keep 
>   *> spewing RSVP messages to the network even if every router is happily 
>   *> ignoring them, and the destination node does not support them.
> 
> Well, actually, that's not true.  RSVP does have mechanisms to detect
> nodes that do not support it, and nodes that do support it but fail
> to respond.

Well, that's why I said "correct me if I'm mistaken" ;-).

I noticed that RSVP does have mechanisms to to detect at least some of
these (at least sect 3.8 of RFC2205), but I saw no specification
whether this actually needs to be done, how and when the hosts must
shut up if they don't see any support, etc.

In other words, if the mechanisms are there but the hosts are not
specified or required to use them, or cannot use them for some reason,
they're of arguable usefulness.

>   *> Possible fix: have the signalling engine contact the local network 
>   *> administrator with a protocol to confirm if it supports the 
>   *> reservations or not.
> 
> This is an ideal application of RFC 3751.

The local administrator just needs to be omniscient about the local
domain if the protocol's behaviour is restricted to that, and that's a 
considerably easier thing to achieve.

And if you wish to achieve inter-domain reservations.. good luck
trying :) -- the lack of no progress in the last 10 years should
probably discourage most attempts..

>   *>  - path-coupled messages require significant processing at the
>   *> routers.  This probably needs to happen in "slow path", in software.  
>   *> A draft mentioned an implementation being able to support a whopping
>   *> (NOT!)  7000 sessions.  That works for the first hop, and possibly
>   *> even to a degree inside an enterprise where you can have software
>   *> based routers and not too many hosts, but it's not a useful model for
>   *> larger routers, deployed at more central places in the network.
> 
> Please see RFC 2998 and RFC 3175.

This is interesting, thanks.

However, if the bottlenecks are at the edge network(s) or the
first/last hop links, I'd say that you may not need to aggregate
within the domain where you want to do reservations, and you (or
rather, the operators) don't want to do any reservations where you
would need to aggregate.

This does not address the concerns of DoS attacks through a high
number of requests or state up to the point of aggregation.  Even if
in the edge networks there was no need to aggregate under normal
situations, nodes going crazy could trash the routers with state.

>  *> Possible fix: instead of on-path processing, contact a node off-path,
>   *> which performs all the processing, checks the policies, etc., and
>   *> ensures that appropriate QoS metrics are configured at the appropriate
>   *> routers (these could be bulk DiffServ guarantees, more specific
>   *> reservations and whatever).
>   *> 
>   *>  - the policy checks are distributed to all the routers: the real
>   *> policy, within an administrative domain, is however made in a
>   *> centralized fashion, so it would be useful not to have to distribute
>   *> the policy to every router, but rather just process it in one place.
>   *> 
>   *> Possible fix: BB model provides this capability.
> 
> RSVP does not put the policy in every router. Have you ever heard
> of COPS?

Yes, as a matter of fact, I have.  It's the protocol that there was
some research about roughly 5 years ago, but that has since then died
off and nobody is using it (well, maybe the same set of people who are
using RSVP) :-).

The PIB model was dumped a couple of years ago, and that probably
trashed the dreams of COPS people as well.
 
> The rest of your message seems to move away from tell us what
> is wrong with RSVP in particular and path-coupled signaling in
> general, to telling us what is wrong with Integrated Service.
> Those are old, and endless, arguments, but they don't seem to
> have anything to do with the topic you started on.

RSVP builds on the Integrated Service model.  Any new protocol w/
path-coupled characteristics and reservations is going to build on the
same model AFAICS.  Even though the arguments don't apply to RSVP in
particular (but rather the model it builds upon), they are still valid
concerns -- if the foundation is not solid, there's not much use
building protocols (especially new ones) on top of it.

It may be that the time has solved at least some of these arguments.  
If Integrated Service models were really valid, shouldn't we have seen
some of it during the last 10?  We haven't -- maybe there is a reason
for it (and the prime reason is IMHO not the protocol used with that
model).

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





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


From ietf-bounces@ietf.org  Wed Aug 25 04:10:33 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22683;
	Wed, 25 Aug 2004 04:10:32 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1BzssH-0004R4-3p; Wed, 25 Aug 2004 04:11:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BzsDH-0005GF-Q7; Wed, 25 Aug 2004 03:28:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bzroa-0002vX-5b
	for ietf@megatron.ietf.org; Wed, 25 Aug 2004 03:03:24 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA19197
	for <ietf@ietf.org>; Wed, 25 Aug 2004 03:03:17 -0400 (EDT)
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BzrpA-0003Cs-TV
	for ietf@ietf.org; Wed, 25 Aug 2004 03:04:01 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i7P72jn17402;
	Wed, 25 Aug 2004 10:02:45 +0300
Date: Wed, 25 Aug 2004 10:02:45 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <2949ADB6-F5E6-11D8-90CB-000A95CD987A@muada.com>
Message-ID: <Pine.LNX.4.44.0408250943460.16339-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2beba50d0fcdeee5f091c59f204d4365
Cc: ietf@ietf.org
Subject: Re: hop-by-hop and router alert options
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-Score: 0.0 (/)
X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab

On Tue, 24 Aug 2004, Iljitsch van Beijnum wrote:
> >  - the model where hosts or apps can reserve bandwidth or other
> > characteristics doesn't sit well with the operational models of ISPs.
> 
> Things change. ISPs are used to that. (They may whine, though.)

Well, I have seen no evidence of that, but of course this may be
different with some who provide e.g. VoIP services across their
backbone (I just don't know).

> > Such a reservation by definition eats from the shared resource;
> 
> That's certainly not a given. If I make a phone call, my 64 kbps isn't 
> taken from anyone else using the phone network, but from the pool of 
> available unused capacity. You could do the same in an IP network, and 
> you probably should or your regular customers will walk away.

Certainly, but that presumes there is sufficient capacity to begin 
with.  Why exactly would you need to do an explicit, 
application-specific reservation then?

> > multiple reservations result in fewer people being use the the
> > originally shared resource.  On the other hand, the reservations
> > aren't useful unless sufficiently large about of BW is allocated to
> > them, and then the rest will suffer.  So, this would only be feasible
> > as a premium paid service.
> 
> That's not necessarily true either. Sure, there are applications that 
> want/need huge amounts of bandwidth that they will want to reserve. But 
> there are also applications that need a certain amount of low-delay, 
> low-jitter bandwidth, where the problem isn't the amount of bandwidth, 
> but making it low-delay and low-jitter (which you can't do for ALL your 
> bandwidth if you run close to capacity for even conservative 
> definitions of "close"). (And remember: there is always a bottleneck. 
> Always.)

Seems awfully close to something what DSCP's are for.

> > Clarification needed: is the signalling protocol envisioned to be used
> > for paid premium service only?  If so, it may have some marginal use,
> > but I doubt the users are willing to pay for it so it would be
> > marginal.  If not, the protocol needs to be highly resistant to
> > users/apps requesting too large reservations (consider a
> > virus-infected host requesting very large reservations), security
> > models, etc.
> 
> What we see today is that average home users eat a lot of bandwidth. 
> Even with today's prices that gets expensive. The problem is that users 
> REALLY don't like to pay for volume or be restricted in any way. An 
> interesting approach here would be to allow users to use as much 
> capacity as the network can support (yes, at 100% utilization) so the 
> file sharers are happy, but at the same time provide a premium service 
> that bypasses the thus created congestion. This doesn't have to be a 
> paid-for thing: you could simply make the first 100 kbps that a user 
> uses premium and everything on top of that bulk.

I see tendency towards another direction: ISPs implement rate-limiters
or traffic quotas to the heavy bandwidth users, for all of their
traffic.

An alternative, and IMHO probably more workable solution than
providing "premium service" is going towards another direction; you've
probably heard of academic networks' less-than-best-effort and
scavenger diffserv schemes, where the users can mark their traffic to
be discarded if necessary.

Let's assume that the traffic which would be marked by the user as
"discard if needed" would not be counted towards bandwidth quotas or
rate-limits, but would still be allowed.  Then the users could get
high quality for their regular traffic, get the available quality and
resources for their bulk traffic they don't care much about (specific
apps), or not mark any of it (and get rate-limited, or billed for
extra, or whatever).  That would make the users *care* about their
environment, or be forced to worse quality.

If it's several high-bandwidth bulk transfer apps that are causing
problems, why not fix the traffic (non-)reservations for *them*, not
for the rest of the traffic?

> >  - the first-hop only case is considerably easier because the user can
> > just shoot himself (not the others) in the foot.  I.e., it allows the
> > user to manage *his* traffic preferences on the link, i.e., he cannot
> > reserve from the bandwidth used by others.
> 
> But having whatever the access speed happens to be as your limit is 
> often not the best choice.

Certainly not, but consider that in the context of e.g., 3GPP or 3GPP2
wireless (constrained) link which the customer might want to
police/prioritize in some manner.  The operator really doesn't care
how the user prioritizes its own traffic, but the user might.  But we
need no RSVP-like model to achieve that.
 
> > Remote administrative domains (including the ISPs) don't want
> > "foreign" nodes to request any reservations, unless they get direct
> > income from allowing that.
> 
> Well, every network in the path between two arbitrary endpoints is 
> always directly or indirectly paid by one of the endpoints. So if both 
> endpoints want this service, their respective ISPs (and ISPs of ISPs) 
> have an incentive to provide it.

Certainly, but unless you get big bucks from the user (so that the
next people in the chain get more than just a couple of cents), the
ISPs won't bother to set it up.  And if it requires the user to pay
big bucks, the users won't bother, and the few who would be willing to
pay are not a sufficiently large user base for the first-hop ISP to
set up their infrastructure, so nothing gets done.  This is the state
we've been with for 10 years or so, since IntServ model was
introduced..
 
> > Best effort service is the fairest service available under such 
> > circumstances.
> 
> Life isn't fair.  :-)  You REALLY don't want to do something 
> interactive on a small pipe that you share with some p2p file sharers 
> and have everyone receive "fair" packet loss percentages and delay.

Small pipes have their problems of course (where a different set of
tools could be used rather than RSVP or path-coupled signalling), but
that's not an interdomain problem that needs to be fixed.  Just
rate-limit all the traffic of the bulk transferers, and provide a
means for them to mark their bulk traffic so that they can get better
quality for their non-bulk transfer.

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


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


From ietf-bounces@ietf.org  Wed Aug 25 11:42:54 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24840;
	Wed, 25 Aug 2004 11:42:53 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bzzw7-0004NZ-4l; Wed, 25 Aug 2004 11:43:43 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bzz8J-0006bg-PH; Wed, 25 Aug 2004 10:52:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BzyrI-0004TF-JD
	for ietf@megatron.ietf.org; Wed, 25 Aug 2004 10:34:40 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19713
	for <ietf@ietf.org>; Wed, 25 Aug 2004 10:34:33 -0400 (EDT)
Received: from goliath.siemens.de ([192.35.17.28])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bzyrw-00037I-In
	for ietf@ietf.org; Wed, 25 Aug 2004 10:35:22 -0400
Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11])
	by goliath.siemens.de (8.12.6/8.12.6) with ESMTP id i7PEYTec026909;
	Wed, 25 Aug 2004 16:34:29 +0200
Received: from mchp9daa.mch.sbs.de (mchp9daa.mch.sbs.de [139.25.137.99])
	by mail2.siemens.de (8.12.6/8.12.6) with ESMTP id i7PEYTuC013160;
	Wed, 25 Aug 2004 16:34:29 +0200
Received: by mchp9daa.mch.sbs.de with Internet Mail Service (5.5.2657.72)
	id <RRKQ7LHT>; Wed, 25 Aug 2004 16:34:29 +0200
Message-ID: <2A8DB02E3018D411901B009027FD3A3F046865AE@mchp905a.mch.sbs.de>
From: Tschofenig Hannes <hannes.tschofenig@siemens.com>
To: "'Pekka Savola'" <pekkas@netcore.fi>, ietf@ietf.org
Date: Wed, 25 Aug 2004 16:33:53 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Subject: RE: hop-by-hop and router alert options
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-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac

hi pekka, 

it is interesting to hear your opinion on these issues. i would like to
point out a few things: 

- there have been a number of discussions about the bandwidth broker concept
in the past and the disadvantages are known. (my personal opinion) if it
boils down to the protocol details then the difference between the rsvp
architecture with a pep/pdp and a bandwidth broker is not hudge. the central
entity which performs the authorization (or policy) decision was already
mentioned. 

- from a signaling protocol point of view there is little difference between
path-coupled and path-decoupled signaling in many cases. even path-decoupled
signaling is path-coupled in some sense - you do not want to signal your
messages to networks where the data traffic will never flow through. one big
difference is the discovery mechanism. you are certainly right with your
observation that you could use a number of different discovery mechanisms to
communicate with devices along the path. if we can learn something from rsvp
with this respect then it should that multiple mechanisms for discovering an
node along the path has to be supported - not only router alert options. i
think such a decision would increase the number of usage scenarios.

btw, you might not know about the path-decoupled signaling (pads) bof (see
http://www.ietf.org/ietf/03mar/pads.txt) where people spoke about reusing
path-coupled signaling protocols in order to provide path-decoupled
signaling. 

- denial of service issues with the router alert option: it is true that
router alert option processing is slower than packets which do not have the
router alert option set. however, i am not sure whether this is truely a big
issue based on the most recent information i saw (see
http://www.welzl.at/research/projects/ip-options/).
furthermore, i always had the impression that other mechanisms even
introduce more denial of service risks. for example: if you have your
bandwidth broker example then you need to deal with dos issues against this
device as well (and there are plenty of them). basically, you need to
address denial of service issues at any place, regardless of the specific
solution. 

- firewall issues: you argue that an operator might not allow users to open
pinholes. why not? if you authenticate and authorize users then you can make
a decision which user is allowed to open a pinhole. furthermore, you already
do it today with more complex mechanisms based on sip signaling and midcom.
it would be worth to have a discussion on the following issue: 
  * path-coupled signaling is very benefitial if you have complex topologies
where routing symmetry causes packets towards different destination
addresses to hit different firewalls/nats. melinda shore raised this issue
in midcom (i guess for the first time). you can find her draft at
http://www.watersprings.org/pub/id/draft-shore-friendly-midcom-01.txt.
  * will people deploy firewalls in the future? (particularly since people
tunnel everything through http)? (my personal opinion is yes, they will.)

- nat issues: why do you think that nat handling is trickier? in fact the
case of a data receiver being behind a nat is (based on our investigations)
rather a nice case since you are assured that the data packets traverse this
nat (if you publish the obtained ip address, transport protocol + port as
your contact address). with a data receiver behind a firewall (in case of
complex topologies and routing asymmetry) things are more complicated
(without making additional assumptions). you mention some ipv6 specific
solutions that would fix the problem automatically. could you please
elaborate?

- you mention a few issues with regard to qos and charging. this is a
complex issue which we (engineers) are not really good in making a decision.
i have read a number of papers by prof. odlyzko (see for example
http://www.dtc.umn.edu/~odlyzko/doc/pricing.architecture.pdf). these papers
are nice to read but it is hard to estimate how individual issues raised in
these documents influence our work (and even in which time frame).

ciao
hannes

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


From ietf-bounces@ietf.org  Thu Aug 26 03:10:24 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA12937;
	Thu, 26 Aug 2004 03:10:24 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C0EPo-00064a-Js; Thu, 26 Aug 2004 03:11:21 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C0DdZ-0007h8-0E; Thu, 26 Aug 2004 02:21:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C0DWX-0004JS-2i
	for ietf@megatron.ietf.org; Thu, 26 Aug 2004 02:14:13 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09628
	for <ietf@ietf.org>; Thu, 26 Aug 2004 02:14:07 -0400 (EDT)
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C0DXH-0005DZ-0S
	for ietf@ietf.org; Thu, 26 Aug 2004 02:15:02 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i7Q6DPp12525;
	Thu, 26 Aug 2004 09:13:25 +0300
Date: Thu, 26 Aug 2004 09:13:25 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Tschofenig Hannes <hannes.tschofenig@siemens.com>
In-Reply-To: <2A8DB02E3018D411901B009027FD3A3F046865AE@mchp905a.mch.sbs.de>
Message-ID: <Pine.LNX.4.44.0408260814330.10940-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a0494a0224ca59418dd8f92694c1fdb
Cc: ietf@ietf.org
Subject: RE: hop-by-hop and router alert options
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-Score: 0.0 (/)
X-Scan-Signature: a8041eca2a724d631b098c15e9048ce9

Thanks for your reasonable note, Hannes.

On Wed, 25 Aug 2004, Tschofenig Hannes wrote:
> - there have been a number of discussions about the bandwidth broker
> concept in the past and the disadvantages are known. (my personal
> opinion) if it boils down to the protocol details then the
> difference between the rsvp architecture with a pep/pdp and a
> bandwidth broker is not hudge. the central entity which performs the
> authorization (or policy) decision was already mentioned.

BB concept applied in which scope?  BB model, as with intserv model,
does not work (even well) across administrative boundaries.  Those
disadvantages are well known. Were those disadvantages related to
that, or something else?

> - from a signaling protocol point of view there is little difference between
> path-coupled and path-decoupled signaling in many cases. even path-decoupled
> signaling is path-coupled in some sense - you do not want to signal your
> messages to networks where the data traffic will never flow through. one big
> difference is the discovery mechanism. you are certainly right with your
> observation that you could use a number of different discovery mechanisms to
> communicate with devices along the path. if we can learn something from rsvp
> with this respect then it should that multiple mechanisms for discovering an
> node along the path has to be supported - not only router alert options. i
> think such a decision would increase the number of usage scenarios.

The point is, if you just signal to a "broker" in the network you're
visiting (discovered in the same manner, e.g., as the recursive DNS
servers), it will know if you send it source, destination pair whether
the traffic goes beyond its control or not, and that avoids
unnecessary signalling (and signalling attempts).  Avoiding the 
unnecessary attempts is actually IMHO pretty important for multiple 
reasons.

> btw, you might not know about the path-decoupled signaling (pads) bof (see
> http://www.ietf.org/ietf/03mar/pads.txt) where people spoke about reusing
> path-coupled signaling protocols in order to provide path-decoupled
> signaling. 

It's interesting to note that there has been a BoF, but I'd be
interested as to why folks spoke about reusing the path-coupled
signalling (of course, it can be used for the lack of a better
protocol); too bad the BoF didn't submit any slides or minutes.
 
> - denial of service issues with the router alert option: it is true that
> router alert option processing is slower than packets which do not have the
> router alert option set. however, i am not sure whether this is truely a big
> issue based on the most recent information i saw (see
> http://www.welzl.at/research/projects/ip-options/).

Processing is indeed slower .. 10% or 30% is significant.  But what
I'm really worried about is that IP router alert -like options are
options which a hardware implementation cannot process.  An attacker
can just specify an undefined router alert option which forces the
processing to go to the slow path (instead of ASICs etc., it must be
put on the CPU), and overload the processing of the router that way.  
That's not good.  That can naturally be mitigated by rate-limiting the
IP options to some small value, but such would effectively disable the
processing of options, and require that you're able to match on those
options.  In other words, anything which has to be forwarded that
requires CPU processing seems bad to me..

Btw, you might be interested that in PMTUD WG session at IETF60 where
Michael Welzl proposed using IP options for PMTUD, Mark Allman (AFAIR)  
reminded of someone (him?) conducting tests on how big percentage of
hosts respond or not when there are IP options.  Michael's
presentation
(http://www.ietf.org/proceedings/04aug/slides/pmtud-4.pdf) already
said that 30% were ignored you completely (not just the IP option!),
but I think when conducting tests against web servers, this was even
smaller.  I don't know whether this is caused by broken firewalls or
what, but that certainly seemed to be showstopper at least for IP
options -based PMTUD.  Doesn't the same apply to NSIS if you'd like to
do it end-to-end?

> furthermore, i always had the impression that other mechanisms even
> introduce more denial of service risks. for example: if you have your
> bandwidth broker example then you need to deal with dos issues against this
> device as well (and there are plenty of them). basically, you need to
> address denial of service issues at any place, regardless of the specific
> solution. 

IMHO the risks are very different.  With IP router alert -based
mechanisms, you need to address the DoS risks in all the routers in
the world.  With BB like centralized models, you just need to address
then in BB-like boxes: that's probably around 1%-5% of the number of
boxes where you need to do that, and that box is dedicated to just 
processing on protocol, so it should be easier to build 
protocol-specific anti-DoS measures.

> - firewall issues: you argue that an operator might not allow users to open
> pinholes. why not? if you authenticate and authorize users then you can make
> a decision which user is allowed to open a pinhole. furthermore, you already
> do it today with more complex mechanisms based on sip signaling and midcom.

Certainly, the operator can make a policy decision who can do it.  
And many protocols do create holes.  But the protocols don't ask the
firewall administrator whether they're allowed to do it or not; the
methods just use tricks (e.g., open an outbound session, and tunnel
traffic inbound through it) to pass the firewall whether that's
intended or not, right?

There could be some applicability to allow certain users, by policy,
to create pinholes (in such a manner that the administrator could
override it) in the firewall in the pre-determined small port range
(e.g., the hosts would still not be able to request pinholes for
TCP/80, but only for e.g., certain kind of SIP usage), but for
something more general than that.. I doubt it.

> it would be worth to have a discussion on the following issue: 
>   * path-coupled signaling is very benefitial if you have complex topologies
> where routing symmetry causes packets towards different destination
> addresses to hit different firewalls/nats. melinda shore raised this issue
> in midcom (i guess for the first time). you can find her draft at
> http://www.watersprings.org/pub/id/draft-shore-friendly-midcom-01.txt.

I think you could actually address at least 95% of this if you just
supply (source,destination pair) to someone who has the copy of the
(IGP) routing data and can calculate what the path would be like.  
The rest 5% would be caused by policy-based custom routing (typically
only applies at the edge, so not an issue) and hosts with multiple
interfaces which send packets out through wrong interface with
incorrect source addresses.

>   * will people deploy firewalls in the future? (particularly since people
> tunnel everything through http)? (my personal opinion is yes, they will.)

I also think yes, though I'm still hoping that some breakthroughs in 
host-based firewalls w/ centralized policy process would obviate the 
need for getting smarter edge firewalls.

> - nat issues: why do you think that nat handling is trickier? in fact the
> case of a data receiver being behind a nat is (based on our investigations)
> rather a nice case since you are assured that the data packets traverse this
> nat (if you publish the obtained ip address, transport protocol + port as
> your contact address). with a data receiver behind a firewall (in case of
> complex topologies and routing asymmetry) things are more complicated
> (without making additional assumptions).

There are a number of NATs which behave different ways, as described
in draft-jennings-midcom-stun-results-01.txt.  With a firewall, you
just need to enter one pass rule to enable a service.  With NAT state,
you might need one for each peer (port) that must traverse inbound
through it, unless you would be inserting some kind of "forwarder"  
state.

> you mention some ipv6 specific
> solutions that would fix the problem automatically. could you please
> elaborate?

I meant solutions like Teredo (draft-huitema-v6ops-teredo-02.txt) and 
similar other configured tunneling schemes which traverse NATs which 
will be able to provide non-NAT'ed IPv6 access, obviating the need for 
NAT traversal.

> - you mention a few issues with regard to qos and charging. this is a
> complex issue which we (engineers) are not really good in making a decision.
> i have read a number of papers by prof. odlyzko (see for example
> http://www.dtc.umn.edu/~odlyzko/doc/pricing.architecture.pdf). these papers
> are nice to read but it is hard to estimate how individual issues raised in
> these documents influence our work (and even in which time frame).

I totally agree that this is a complex issue, but I remain amazed that
there are still people who want to try to solve a complex issue
irregardless of its complexity even if there is history which seems to
indicate that it's likely that it isn't going anywhere.  Instead, I
would have been more happier if I had noticed that the folks would be
working on more easier tasks of the complex problem in a piecemeal
manner (e.g., the issues with qos and limiting at the first hop, or at
the predetermined constrained hops at the local site).

Trying to solve a broad problem might lead the problem being solved
with such means that the solution is never going to be widely deployed
to meet its original goals, and the effect is that we don't have any
realistic solution in the end. If a slightly different approach would
cause wider penetration on the really crucial issues (e.g., the issues
in the first hop, etc.), then we would possibly be much better off in
general.

That's my concern: (IMHO) it'd be better to concentrate on the easier
issues *only*.  End-to-end (without the constrains on where the ends
are)  signalling is not something that can be solved in a manner that
it would actually be used without reinventing the Internet
architecture.  Concentrating on the easier issues only would be
better, and not seeking (again, after RSVP :) the holy grail of
telecom/research QoS people, end-to-end signalling for reservations.
There's also smaller amount of economical/operational aspects to worry
about, as there are clearer areas of applicability and use for 1st
hop/predetermined constrained hops case.

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


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


From ietf-bounces@ietf.org  Thu Aug 26 11:19:51 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10213;
	Thu, 26 Aug 2004 11:19:51 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C0M3Z-0006t0-0D; Thu, 26 Aug 2004 11:20:53 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C0Le1-0002jv-9u; Thu, 26 Aug 2004 10:54:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C0LSg-0007Z8-2D
	for ietf@megatron.ietf.org; Thu, 26 Aug 2004 10:42:46 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24975
	for <ietf@ietf.org>; Thu, 26 Aug 2004 08:13:21 -0400 (EDT)
Received: from diotima.switch.ch ([130.59.4.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C0J92-0002hM-4H
	for ietf@ietf.org; Thu, 26 Aug 2004 08:14:20 -0400
Received: from diotima.switch.ch (localhost [127.0.0.1])
	by diotima.switch.ch (8.12.11/8.12.11) with ESMTP id i7QCCncS018125
	(version=TLSv1/SSLv3 cipher=EDH-DSS-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 26 Aug 2004 14:12:49 +0200 (CEST)
Received: (from leinen@localhost)
	by diotima.switch.ch (8.12.11/8.12.11/Submit) id i7QCCmMX018122;
	Thu, 26 Aug 2004 14:12:48 +0200 (CEST)
To: Tschofenig Hannes <hannes.tschofenig@siemens.com>
X-Face: 1Nk*r=:$IBBb8|TyRB'2WSY6u:BzMO7N)#id#-4_}MsU5?vTI?dez|JiutW4sKBLjp.l7, 
	F 7QOld^hORRtpCUj)!cP]gtK_SyK5FW(+o"!or:v^C^]OxX^3+IPd\z,
	@ttmwYVO7l`6OXXYR`
From: Simon Leinen <simon@limmat.switch.ch>
In-Reply-To: <2A8DB02E3018D411901B009027FD3A3F046865AE@mchp905a.mch.sbs.de>
	(Tschofenig Hannes's message of "Wed, 25 Aug 2004 16:33:53 +0200")
References: <2A8DB02E3018D411901B009027FD3A3F046865AE@mchp905a.mch.sbs.de>
Date: Thu, 26 Aug 2004 14:12:48 +0200
Message-ID: <aahdqqjdxb.fsf@diotima.switch.ch>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (usg-unix-v)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Cc: Michael Welzl <michael.welzl@uibk.ac.at>, Pekka Savola <pekkas@netcore.fi>,
        ietf@ietf.org
Subject: Re: hop-by-hop and router alert options
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-Score: 0.0 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be

Hannes Tschofenig writes:
[...]
> - denial of service issues with the router alert option: it is true
> that router alert option processing is slower than packets which do
> not have the router alert option set. however, i am not sure whether
> this is truely a big issue based on the most recent information i
> saw (see http://www.welzl.at/research/projects/ip-options/).

This study compares the delay experienced by packets with IP options
to the delay experienced by packets without IP options, for a wide
variety of Internet paths.  It observes that on average, IP options
introduce between 7% and 26% (for different sets of paths at different
times) of additional delay.  The article says that "In any case, the
additional delay is clearly an order of magnitude smaller than the
RTT."

To some people, this may suggest that option processing overhead isn't
a problem in today's Internet.  I don't buy this at all.

The problem is this: A large part of the measured baseline delay is
due to propagation times (length of links/speed of light in fiber) and
thus mostly independent of whether IP Options are used or not.

If, as I suspect, the part of the delay that is actually due to
per-hop processing is small (for the baseline no-options case), then a
7%-26% increase of the *total* delay could mean an orders-of-magnitude
increase in per-hop processing overhead when IP options are used.

To illustrate this, here are the results of Michael's "extended ping"
test over a cross-town path with five GbE hops, sorted by RTT:

NONE   64 bytes from 130.59.35.42: seq=10007, ttl=62, rtt=0.171 ms
NONE   64 bytes from 130.59.35.42: seq=10009, ttl=62, rtt=0.172 ms
NONE   64 bytes from 130.59.35.42: seq=10005, ttl=62, rtt=0.178 ms
NONE   64 bytes from 130.59.35.42: seq=10001, ttl=62, rtt=0.202 ms
NONE   64 bytes from 130.59.35.42: seq=10000, ttl=62, rtt=0.209 ms
NONE   64 bytes from 130.59.35.42: seq=10008, ttl=62, rtt=0.211 ms
NONE   64 bytes from 130.59.35.42: seq=10003, ttl=62, rtt=0.216 ms
NONE   64 bytes from 130.59.35.42: seq=10006, ttl=62, rtt=0.220 ms
NONE   64 bytes from 130.59.35.42: seq=10004, ttl=62, rtt=0.225 ms
NONE   64 bytes from 130.59.35.42: seq=10002, ttl=62, rtt=0.233 ms
NOP    64 bytes from 130.59.35.42: seq=20005, ttl=62, rtt=0.735 ms
NOP    64 bytes from 130.59.35.42: seq=20003, ttl=62, rtt=0.769 ms
NOP    64 bytes from 130.59.35.42: seq=20006, ttl=62, rtt=0.775 ms
NOP    64 bytes from 130.59.35.42: seq=20000, ttl=62, rtt=0.803 ms
NOP    64 bytes from 130.59.35.42: seq=20008, ttl=62, rtt=0.803 ms
NOP    64 bytes from 130.59.35.42: seq=20004, ttl=62, rtt=0.816 ms
NOP    64 bytes from 130.59.35.42: seq=20002, ttl=62, rtt=0.885 ms
NOP    64 bytes from 130.59.35.42: seq=20009, ttl=62, rtt=1.749 ms
NOP    64 bytes from 130.59.35.42: seq=20001, ttl=62, rtt=3.456 ms
NOP    64 bytes from 130.59.35.42: seq=20007, ttl=62, rtt=4.288 ms

The optionless packets have an RTT between 171 and 233 microseconds
(other traffic on the path may explain the variance).  The packets
with NOP IP options have an RTT between 735 and 4288 microseconds.
This strongly suggests that IP options cause slow-path processing on
our routers.

Most operators won't worry about the additional delay incurred by
packets that use IP options.  But they WILL worry about the total
processing overhead in their routers when there are many such packets,
because slow-path resources are usually shared with the control plane,
and operators just hate it when control of the network is impacted by
user traffic.

I can see a few possible outcomes when IP options become more common:

1.) Routers implement option processing in the fast path
    - this will be expensive and/or take time if the fast path is "in
    hardware", e.g. mostly based on ASIC/FPGA/CAMs.  I think it will
    be hard to motivate this.
2.) Router vendors implement rate-limits for packets with
    (router-alerting) IP Options.  The rate-limiting must be done in
    the fast path, while options processing can remain in the slow
    path.  Maybe the rate-limits can be differentiated by
    option/extension header type, maybe not.
3.) Operators configure their routers to ignore IP Options.
4.) Operators configure their routers to drop packets with IP Options.

Regards,
-- 
Simon.


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


From ietf-bounces@ietf.org  Thu Aug 26 11:47:52 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13053;
	Thu, 26 Aug 2004 11:47:52 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C0MUd-0007gy-Dx; Thu, 26 Aug 2004 11:48:54 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C0MCJ-0004M9-GN; Thu, 26 Aug 2004 11:29:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C0M0I-0008LP-22
	for ietf@megatron.ietf.org; Thu, 26 Aug 2004 11:17:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09675
	for <ietf@ietf.org>; Thu, 26 Aug 2004 11:17:28 -0400 (EDT)
Received: from cliffie.verisignlabs.com ([65.201.175.9]
	helo=mail.verisignlabs.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C0M1E-0006hV-Ju
	for ietf@ietf.org; Thu, 26 Aug 2004 11:18:29 -0400
Received: from [10.131.244.198] ([::ffff:216.168.239.87]) (AUTH: LOGIN leslie)
	by mail.verisignlabs.com with esmtp; Thu, 26 Aug 2004 11:16:57 -0400
	id 002F4045.412DFEE9.00005B54
Message-ID: <412DFEE9.80003@thinkingcat.com>
Date: Thu, 26 Aug 2004 11:16:57 -0400
From: Leslie Daigle <leslie@thinkingcat.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040803
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4
Content-Transfer-Encoding: 7bit
Cc: Harald Tveit Alvestrand <harald@alvestrand.no>
Subject: Options for IETF administrative restructuring
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-Score: 0.0 (/)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
Content-Transfer-Encoding: 7bit

[This is a re-send of a message I sent last night; that message is
  caught in the list moderation queue because the attachment put
  it over the message size limit.  It should appear on the list...
  sometime.  The Internet-Draft may appear in the archive before
  then.  In the meantime, there are rumours of some possible math
  errors, so it's quite possible an -01 version will appear very
  quickly :-)   -- Leslie.]


Hello, IETF community.

Attached is the document we promised you in San Diego - a report from
our consultant, Carl Malamud, which lays out a series of options and
recommendations for moving forward with the IETF administrative
restructuring process, according to the recommendations laid out
in RFC3716 (the Advisory Committee report).  It has been submitted
to the Internet Drafts repository and should be showing up there
shortly.


Some important things to note:

THIS IS NOT A DOCUMENT TO BE READ IN ISOLATION.
Minimally, reviewing the Advisory Committee report (RFC3716) is
necessary to understand the context of the proposals laid out in
this draft.

THIS IS NOT YET AN IETF DECISION.
That will be taken later, based on your input and IETF rough consensus.

THIS IS NOT THE IESG/IAB's RECOMMENDATION.
Our recommendation will come later, based on your input and the
evolution of our thinking.

THIS IS NOT AN ISOC POSITION.
The document describes potential relationships of the IETF
administrative activity and ISOC.  However, the document is written
as a proposal for IETF discussion -- the ISOC Board has not been asked
to formulate a position on supporting one or any of these proposals; we
need to have that discussion as it becomes clearer what the IETF wants
in its future.


This IS, however, the culmination of many, many hours of information
gathering and a near-infinite number of conversations by Carl Malamud,
attempting to give the best basis on which the IETF could make a
decision that he could within the timeframe given.

We encourage all interested IETF participants to read the report most
carefully, and give feedback on it - on the IETF list for public
discussion, directly to Carl or the IETF and IAB chairs if you want to
make off-list comments.

FURTHER STEPS

The next steps in this process depend on the community feedback and
whether we can gauge a consensus of the IETF on this mailing list. What
we think is reasonable so far is:

- Have a public discussion on the IETF list on the options presented in
the draft

- By early September, the IESG and IAB will attempt to distill a set of
recommendations that we think capture a reasonable consensus of the
community, and publish this as an internet-draft, which will be revised
over the next month, possibly several times, based on further
discussions

- By late September, we emit a Last Call on this set of recommendations,
if we deem that we have a reasonable consensus for the proposals

- By late October, if the IETF community still shows consensus, we will
declare that we have a decision, and will start executing based on that
decision.

In order to be able to move rapidly when we go into the "execution"
phase, we may initiate some activities of a "fact-finding" nature - such
as investigating possible suppliers of services and candidates for the
positions we envisage filling - before that, but irrevocable decisions
will await IETF consensus.

Please read the attachment - please comment - please THINK.

While this in itself should not change the IETF standards process at
all, support functions are important to the IETF.

We need to take the time to get this one right.

                     Leslie and Harald.



-- 

-------------------------------------------------------------------
"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  Thu Aug 26 15:27:46 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00082;
	Thu, 26 Aug 2004 15:27:46 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C0PvV-00041v-Ih; Thu, 26 Aug 2004 15:28:49 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C0Pnd-0000vm-AC; Thu, 26 Aug 2004 15:20:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C0Pmt-0000P7-WF
	for ietf@megatron.ietf.org; Thu, 26 Aug 2004 15:19:56 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29669
	for <ietf@ietf.org>; Thu, 26 Aug 2004 15:19:53 -0400 (EDT)
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C0Pno-0003ut-Vz
	for ietf@ietf.org; Thu, 26 Aug 2004 15:20:56 -0400
Received: from [127.0.0.1] (helo=localhost)
	by bs.jck.com with esmtp (Exim 4.34)
	id 1C0Pmj-000BnU-OV; Thu, 26 Aug 2004 15:19:46 -0400
Date: Thu, 26 Aug 2004 15:19:43 -0400
From: John C Klensin <john-ietf@jck.com>
To: Leslie Daigle <leslie@thinkingcat.com>,
        Harald Tveit Alvestrand <harald@alvestrand.no>
Message-ID: <98F73353B4C48AD0B7026AB7@as-s2n.inter-touch.net>
In-Reply-To: <412DFEE9.80003@thinkingcat.com>
References: <412DFEE9.80003@thinkingcat.com>
X-Mailer: Mulberry/3.1.6 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: Options for IETF administrative restructuring
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-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Content-Transfer-Encoding: 7bit

Leslie and Harald,

I would like to make one suggestion about this process.  For 
suggestions about substance, I will, of course, wait for the 
final -00 version of the draft.   This note is deliberately 
being sent before I have done so because I don't want my remarks 
to be biased by how I feel about its specific content.

There was considerable confusion in San Diego, and earlier, 
induced by large numbers of sub-discussions, with different, 
sometimes designated, groups of people holding discussions and 
not having access to each other's comments.  Harald responded to 
comments about this during the plenary by indicating that, once 
the draft was posted, everything would be public.

So I would like to suggest that any discussions within or among 
the IAB and IESG, or subsets of them, or between them and other 
groups, take place on mailing lists whose archives are public 
and/or which can be subscribed to (even if only on a read-only 
basis) by interested members of the community.

The key strategic decisions here (as distinct from the fine 
details) have to be made with the informed consent of the IETF 
community.   To me, that implies that all of the options and 
their pros and cons have to be on the table: after the fact, 
there should not be even a suspicion that the choice was 
influenced by discussions of only a reduced set of options.

I note in particular that your first "next step" reads "Have a 
public discussion on the IETF list on the options presented in 
the draft".   I think that is exactly correct iff the community 
is reasonably assured that _all_ of the plausible options have 
been identified, and fairly described, in the draft.  I hope and 
trust that is the case, but any suspicions, engendered by 
private discussion, that some options have been excluded from 
discussion by excluding them from the draft, would be extremely 
harmful and should be avoided.

As you said, we need to take the time to get this right.  We 
also need to be sure that the community emerges from the process 
confident that all of the options have been fairly considered in 
the process of selecting the right one.

thanks,
    john



--On Thursday, August 26, 2004 11:16 AM -0400 Leslie Daigle 
<leslie@thinkingcat.com> wrote:

> [This is a re-send of a message I sent last night; that
> message is
>...

> Hello, IETF community.
>
> Attached is the document we promised you in San Diego - a
> report from
> our consultant, Carl Malamud, which lays out a series of
> options and
> recommendations for moving forward with the IETF administrative
> restructuring process, according to the recommendations laid
> out in RFC3716 (the Advisory Committee report).  It has been
> submitted to the Internet Drafts repository and should be >...


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


From ietf-bounces@ietf.org  Thu Aug 26 17:18:09 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13524;
	Thu, 26 Aug 2004 17:18:09 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C0ReG-0008IC-1M; Thu, 26 Aug 2004 17:19:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C0RPy-0001VB-By; Thu, 26 Aug 2004 17:04:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C07cD-0004t9-QO
	for ietf@megatron.ietf.org; Wed, 25 Aug 2004 19:55:42 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08350
	for <ietf@ietf.org>; Wed, 25 Aug 2004 19:55:34 -0400 (EDT)
Received: from zak.ecotroph.net ([216.93.164.123])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C07cq-0007g7-M4
	for ietf@ietf.org; Wed, 25 Aug 2004 19:56:27 -0400
Received: from thinkingcat.com ([::ffff:69.170.23.191])
	(AUTH: PLAIN leslie, SSL: TLSv1/SSLv3,256bits,AES256-SHA)
	by zak.ecotroph.net with esmtp; Wed, 25 Aug 2004 19:55:19 -0400
	id 0016BD61.412D26E7.00000B49
Message-ID: <412D268D.3020402@thinkingcat.com>
Date: Wed, 25 Aug 2004 19:53:49 -0400
From: Leslie Daigle <leslie@thinkingcat.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510
X-Accept-Language: en-us, en
Mime-Version: 1.0
Content-Type: multipart/mixed;
	boundary="=_zak.ecotroph.net-2889-1093478127-0001-2"
To: ietf@ietf.org
X-Spam-Score: 1.6 (+)
X-Scan-Signature: 7776698230a59182756034423ea60a43
X-Mailman-Approved-At: Thu, 26 Aug 2004 17:04:20 -0400
Cc: Harald Tveit Alvestrand <harald@alvestrand.no>
Subject: Options for IETF administrative restructuring
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-Score: 1.6 (+)
X-Scan-Signature: f7bb7bbe402713053103742dfe7ef681

This is a MIME-formatted message.  If you see this text it means that your
E-mail software does not support MIME-formatted messages.

--=_zak.ecotroph.net-2889-1093478127-0001-2
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Hello, IETF community.

Attached is the document we promised you in San Diego - a report from
our consultant, Carl Malamud, which lays out a series of options and
recommendations for moving forward with the IETF administrative
restructuring process, according to the recommendations laid out
in RFC3716 (the Advisory Committee report).  It has been submitted
to the Internet Drafts repository and should be showing up there
shortly.


Some important things to note:

THIS IS NOT A DOCUMENT TO BE READ IN ISOLATION.
Minimally, reviewing the Advisory Committee report (RFC3716) is
necessary to understand the context of the proposals laid out in
this draft.

THIS IS NOT YET AN IETF DECISION.
That will be taken later, based on your input and IETF rough consensus.

THIS IS NOT THE IESG/IAB's RECOMMENDATION.
Our recommendation will come later, based on your input and the
evolution of our thinking.

THIS IS NOT AN ISOC POSITION.
The document describes potential relationships of the IETF
administrative activity and ISOC.  However, the document is written
as a proposal for IETF discussion -- the ISOC Board has not been asked
to formulate a position on supporting one or any of these proposals; we
need to have that discussion as it becomes clearer what the IETF wants
in its future.


This IS, however, the culmination of many, many hours of information
gathering and a near-infinite number of conversations by Carl Malamud,
attempting to give the best basis on which the IETF could make a
decision that he could within the timeframe given.

We encourage all interested IETF participants to read the report most
carefully, and give feedback on it - on the IETF list for public
discussion, directly to Carl or the IETF and IAB chairs if you want to
make off-list comments.

FURTHER STEPS

The next steps in this process depend on the community feedback and
whether we can gauge a consensus of the IETF on this mailing list. What
we think is reasonable so far is:

- Have a public discussion on the IETF list on the options presented in
the draft

- By early September, the IESG and IAB will attempt to distill a set of
recommendations that we think capture a reasonable consensus of the
community, and publish this as an internet-draft, which will be revised
over the next month, possibly several times, based on further
discussions

- By late September, we emit a Last Call on this set of recommendations,
if we deem that we have a reasonable consensus for the proposals

- By late October, if the IETF community still shows consensus, we will
declare that we have a decision, and will start executing based on that
decision.

In order to be able to move rapidly when we go into the "execution"
phase, we may initiate some activities of a "fact-finding" nature - such
as investigating possible suppliers of services and candidates for the
positions we envisage filling - before that, but irrevocable decisions
will await IETF consensus.

Please read the attachment - please comment - please THINK.

While this in itself should not change the IETF standards process at
all, support functions are important to the IETF.

We need to take the time to get this one right.

                    Leslie and Harald.



-- 

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




--=_zak.ecotroph.net-2889-1093478127-0001-2
Content-Type: text/plain; name="draft-malamud-consultant-report-00.txt";
	charset=iso-8859-1
Content-Disposition: inline; filename="draft-malamud-consultant-report-00.txt"
Content-Transfer-Encoding: 7bit



Network Working Group                                    C. Malamud, Ed.
Internet-Draft                                       Memory Palace Press
Expires: February 23, 2005                               August 25, 2004


                 IETF Administrative Support Functions
                   draft-malamud-consultant-report-00

Status of this Memo

   This document is an Internet-Draft and is subject to all provisions
   of section 3 of RFC 3667.  By submitting this Internet-Draft, each
   author represents that any applicable patent or other IPR claims of
   which he or she is aware have been or will be disclosed, and any of
   which he or she become aware will be disclosed, in accordance with
   RFC 3668.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as
   Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on February 23, 2005.

Copyright Notice

   Copyright (C) The Internet Society (2004).

Abstract

   This Internet-Draft discusses the restructuring of administrative
   support functions for the IETF.  The draft begins with a discussion
   of prior steps in the process that led up to this report and
   discusses the process going forward.  The draft then examines the
   current functioning of administrative support functions, analyzes
   options for restructuring operational functions, and analyzes options
   available to provide an institutional framework for such support.




Malamud                Expires February 23, 2005                [Page 1]

Internet-Draft      Administrative Support Analysis          August 2004


   The provision of such administrative support functions is limited in
   scope with responsibility only for the administrative, fiscal, and
   legal infrastructure needed to support the IETF community.  In
   particular, issues such as defining and managing the standards-making
   process and the governance of that process are explicitly out of
   scope for this restructuring.

   This Internet-Draft is an independent consultant's report and should
   not be regarded as a consensus view or a policy statement.  The
   report contains only the author's views.

Current Status--YOU MUST READ THIS SECTION

   This is a FIRST DRAFT and DOES NOT represent a position or a
   consensus.  It should be regarded as a starting point for community
   discussion, followed by eventual decision making by the leadership
   based on a community consensus.

   In particular, the key word "we" in this document is to be
   interpreted as meaning "I, the author".  This document does not
   represent a consensus, policies, or opinions that are to be
   attributed to anything but the personal views of the author.

Intended Status and Mailing List

   This document is intended for publication as an Internet-Draft and is
   expected to undergo numerous revisions.  It is intended that this
   document be submitted for publication as an Informational RFC.

   The forum for discussion of this draft is the IETF Discussion list
   (ietf@ietf.org).  The IETF Discussion List is defined in [RFC3005]
   and further defined in [RFC3184] and [RFC3683].



















Malamud                Expires February 23, 2005                [Page 2]

Internet-Draft      Administrative Support Analysis          August 2004


Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  5
     1.1   Goals and Non-Goals  . . . . . . . . . . . . . . . . . . .  5
       1.1.1   Goals  . . . . . . . . . . . . . . . . . . . . . . . .  5
       1.1.2   IETF Standards Process Out of Scope  . . . . . . . . .  5
       1.1.3   ISOC Role in Standards Process Out of Scope  . . . . .  6
     1.2   Previous Steps in This Process . . . . . . . . . . . . . .  7
     1.3   Decision Process . . . . . . . . . . . . . . . . . . . . .  7

     1.4   Criteria for Judging an Administrative Restructuring . . .  8
     1.5   Methodology  . . . . . . . . . . . . . . . . . . . . . . .  8
   2.  Analysis of Current Administrative Framework . . . . . . . . . 10
     2.1   Providers and Functions  . . . . . . . . . . . . . . . . . 10
     2.2   Function 1: Administration . . . . . . . . . . . . . . . . 11
     2.3   Function 2: Meetings . . . . . . . . . . . . . . . . . . . 13
     2.4   Function 3: Core Information Technology  . . . . . . . . . 16
     2.5   Function 4: Document and Information Flow  . . . . . . . . 17
   3.  Recommendations for Restructuring the Administrative
       Framework  . . . . . . . . . . . . . . . . . . . . . . . . . . 20
     3.1   Recommendation 1: Hire An Administrative Director  . . . . 20
     3.2   Recommendation 2: Establish Contracts for Core Services  . 21
       3.2.1   Details of Potential RFP Components  . . . . . . . . . 24
     3.3   Recommendation 3: Provide Timely and Uniform Financial
           Reporting  . . . . . . . . . . . . . . . . . . . . . . . . 27
     3.4   Recommendation 4: More Focus on Archives . . . . . . . . . 28
   4.  Options for an Institutional Basis for Administrative
       Activities . . . . . . . . . . . . . . . . . . . . . . . . . . 29
     4.1   Discussion of Organizational Form and Legal Domicile . . . 29
     4.2   Scenario A: ISOC Operating Unit  . . . . . . . . . . . . . 30
       4.2.1   Division of the Internet Society . . . . . . . . . . . 30
       4.2.2   Intended benefits  . . . . . . . . . . . . . . . . . . 31
       4.2.3   Additional Considerations  . . . . . . . . . . . . . . 31
     4.3   Scenario B: More Formalized ISOC Operating Unit  . . . . . 32
     4.4   Scenario C: Well-Defined Entity With Close Ties to ISOC  . 34
       4.4.1   How Scenario C Might Work In Practice  . . . . . . . . 34
     4.5   Scenario D: Autonomous Entity  . . . . . . . . . . . . . . 40
   5.  Future Work  . . . . . . . . . . . . . . . . . . . . . . . . . 41
     5.1   Short-Term . . . . . . . . . . . . . . . . . . . . . . . . 41
     5.2   Long-Term  . . . . . . . . . . . . . . . . . . . . . . . . 41
   6.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 43
   7.  Security Considerations  . . . . . . . . . . . . . . . . . . . 44
   8.  Acknowledgment of CNRI Contribution to the IETF Community  . . 45
   9.  Acknowledgment of Contributions and Reviews  . . . . . . . . . 46
   10.   References . . . . . . . . . . . . . . . . . . . . . . . . . 47
   10.1  Normative References . . . . . . . . . . . . . . . . . . . . 47
   10.2  Informative References . . . . . . . . . . . . . . . . . . . 48
       Author's Address . . . . . . . . . . . . . . . . . . . . . . . 52
   A.  Consulting Contract  . . . . . . . . . . . . . . . . . . . . . 53



Malamud                Expires February 23, 2005                [Page 3]

Internet-Draft      Administrative Support Analysis          August 2004


   B.  IETF Financial Information . . . . . . . . . . . . . . . . . . 57
     B.1   Consolidated 3-Year Historical Income Statement  . . . . . 57
     B.2   Internet Society 2004 Budget Summary . . . . . . . . . . . 59
   C.  10-Year Meeting Attendance Summary . . . . . . . . . . . . . . 62
     C.1   Analysis of Meeting-Based Expense and Revenue Drivers  . . 64
   D.  Sample Draft Incorporating Documents for a Hypothetical
       IETF Foundation  . . . . . . . . . . . . . . . . . . . . . . . 66
     D.1   Sample Draft Articles of Incorporation . . . . . . . . . . 66
     D.2   Sample Draft Bylaws of the IETF Foundation . . . . . . . . 66
       D.2.1   Article I: Organization  . . . . . . . . . . . . . . . 66
       D.2.2   Article II: Purpose  . . . . . . . . . . . . . . . . . 66
       D.2.3   Article III: Members . . . . . . . . . . . . . . . . . 67
       D.2.4   Article IV: Offices  . . . . . . . . . . . . . . . . . 67
       D.2.5   Article V: Board of Trustees . . . . . . . . . . . . . 67
       D.2.6   Article VI: Officers . . . . . . . . . . . . . . . . . 71
       D.2.7   Article VII: Amendments  . . . . . . . . . . . . . . . 72
       D.2.8   Article VIII: Dissolution  . . . . . . . . . . . . . . 73
       D.2.9   Article IX: Miscellaneous Provisions . . . . . . . . . 73
   E.  Sample Draft Call for Applications -- IETF Administrative
       Director . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
   F.  Sample Draft Request for Proposals . . . . . . . . . . . . . . 77
     F.1   Introduction . . . . . . . . . . . . . . . . . . . . . . . 77
     F.2   General Provisions . . . . . . . . . . . . . . . . . . . . 78
     F.3   Requirement 1: Meetings  . . . . . . . . . . . . . . . . . 79
     F.4   Requirement 2: Systems and Systems Administration  . . . . 79
       F.4.1   Core Network Infrastructure  . . . . . . . . . . . . . 79
       F.4.2   Systems Administration Services  . . . . . . . . . . . 80
     F.5   Requirement 3: Postmaster of the IETF Administrative
           Entity . . . . . . . . . . . . . . . . . . . . . . . . . . 80
     F.6   Requirement 4: Clerk of the IETF Administrative Entity . . 81
     F.7   Requirement 5: Webmaster of the IETF Administrative
           Entity . . . . . . . . . . . . . . . . . . . . . . . . . . 81
     F.8   Selection Criteria and Evaluation Process  . . . . . . . . 81
       Index  . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
       Intellectual Property and Copyright Statements . . . . . . . . 84
















Malamud                Expires February 23, 2005                [Page 4]

Internet-Draft      Administrative Support Analysis          August 2004


1.  Introduction

1.1  Goals and Non-Goals

1.1.1  Goals

   Any plan for restructuring the administrative support functions of
   the IETF and for establishing an institutional foundation for those
   administrative functions must meet three goals:
   1.  The IETF process must continue to work.  The smooth and stable
       operation of the IETF is paramount.  Any changes that are made
       should be made with the goal of making that process work better.
       This means that the continuation of the current operation, the
       transition, and the future steady-state must all be carefully
       thought out and executed.
   2.  The administrative, fiscal, and legal processes--including those
       that effect this restructuring--must be transparent to the IETF
       community.  Any potential IETF administrative support
       organization must be accountable to the community.  Both the
       transition and the future steady state will require the support
       of the community, which requires that we observe the IETF
       processes for decision making and that all necessary information
       for making those decisions be made publicly available.
       Transparency of financial transactions and in the decision making
       process are of particular importance.
   3.  Any organization that provides administrative support functions
       for the IETF must be subservient to and support the existing IETF
       structures and decision-making processes.

1.1.2  IETF Standards Process Out of Scope

   This restructuring exercise is limited in scope to IETF
   administrative functions.  In particular, it does not cover areas
   including (but not limited to) the following:
   1.  The IETF technical standards-making process.
   2.  Selection of the IETF leadership and operation of the nominating
       committee.
   3.  Any other topics already covered in our existing procedure Best
       Current Practices documents unless called out specifically here.

   As will be seen in subsequent sections, we explicitly reference our
   existing purpose, governance, process, and core values as they now
   exist and as they may be changed in the future.  A new institutional
   home for the IETF administrative functions will not supplant the IETF
   technical processes, it will support them.






Malamud                Expires February 23, 2005                [Page 5]

Internet-Draft      Administrative Support Analysis          August 2004


1.1.3  ISOC Role in Standards Process Out of Scope

   The Internet Society and the IETF both have the good of the Internet
   as a primary mission goal.  The Internet Society has a broader
   mandate than the IETF.  Those mandates are organized as the "Pillars"
   of the Internet Society, and include the following activities:
   o  Pillar 1: Education & Training
   o  Pillar 2: Public Policy
   o  Pillar 3: Standards & Protocols

   In support of these pillars, the Internet Society conducts global
   conferences including INET and NDSS, and conducts or participates in
   regional meetings either directly or through its chapters.

   The IETF is focused exclusively on the standards and protocol
   activity.  The Internet Society plays a complementary and vital role
   with an active education and policy effort that allows the IETF to
   maintain a focus on protocols and standards.

   The Internet Society is an international membership organization,
   open to all organizations and individuals.  ISOC supports the IETF
   and IAB in a number of ways (as detailed below), historically raising
   funds through Organization and Individual member dues.  ISOC conducts
   and/or participates in global conferences including INET and NDSS,
   network training workshops for developing countries, topical
   tutorials, and various policy forums.  ISOC participates in many
   regional meetings either directly or through its chapters.

   While a variety of administrative functions provided by the Internet
   Society will be considered in this document, it is important to state
   at the outset that the Internet Society currently provides two
   important functions to the IETF:
   1.  *Administration Functions.* As discussed in subsequent sections,
       the Internet Society provides administrative and financial
       functions, managing the contract with the RFC Editor, providing
       insurance for selected IETF participants, and administering a
       discretionary fund for use by the IAB and the IETF Chairs.
   2.  *Standards Process Functions* The Internet Society plays a
       fundamental role in the IETF Standards Process, including
       appointment of the Nominating Committee chair, confirmation of
       IAB members, confirmation of documents that describe the
       standards processes, and acting as the last resort in the appeals
       process.  These Standards Process Functions are defined in
       [RFC2026], [RFC2028], [RFC2031], and [RFC3677] and are out of
       scope for this analysis.  No changes are proposed to these
       Standards Process Functions.

   Any changes to the *Standards Process Functions* would use the



Malamud                Expires February 23, 2005                [Page 6]

Internet-Draft      Administrative Support Analysis          August 2004


   existing procedures, which require a draft to progress through the
   process, ultimately being subject to a Last Call and a declaration of
   consensus.  In the case of modifications to existing process BCP
   RFCs, this is a high bar to cross.

1.2  Previous Steps in This Process

   A process for restructuring IETF administrative support functions as
   well as other more general IETF issues was started in 2002.  This
   process has resulted in a number of documents that have defined the
   goals of the IETF and basic principles for restructuring (see, e.g.,
   [I-D.alvestrand-ietf-mission]).  The basic outline of the
   administrative restructuring process was defined by an Advisory
   Committee to the IAB, the results of which are published in
   [RFC3716].

   This document carries out the requirements of [RFC3716] in discussing
   various options for administrative restructuring and the definition
   of relationships with institutions which support the activities of
   the IETF community.

   The specific goals of the administrative restructuring effort, as
   outlined in [I-D.daigle-adminrest], are to recognize and preserve the
   community-driven nature of the IETF technical work, and to continue
   to support that work through the formalization of a single
   administrative umbrella organization that will be openly accountable
   to that same community.

1.3  Decision Process

   Restructuring of IETF administrative support functions is a
   fundamental activity that must have the support of the IETF
   community.  This document attempts to present an "omnibus" plan,
   addressing the full scope of the requirements stated in [RFC3716].
   This document has already undergone numerous revisions, and will
   undergo subsequent revisions based on input from the IETF community.
   The first stage in reaching consensus around proposed changes include
   the following steps:
   1.  Publication of [RFC3716].
   2.  Continued deliberation and issuance of Internet-Drafts on the
        Administrative Restructuring.
   3.  A decision to "move forward" including a request for funding by
        the IETF and IAB Chairs to the Internet Society Board of
        Trustees, allocation of those funds, and the engagement of a
        consultant.
   4.  Drafting of this draft.
   5.  Initial reviews of this draft, including reviews by the IAB,
        IESG, ISOC Board, and legal counsel, and others.



Malamud                Expires February 23, 2005                [Page 7]

Internet-Draft      Administrative Support Analysis          August 2004


   6.  Briefings to the community via the IETF discussion list and at
        IETF60 about what to expect.
   7.  Publication as an Internet-Draft.
   8.  Discussion of the Internet-Draft in the IETF community.  *<----
        You Are Here.*
   9.  Reconsideration of the draft by the IAB, IESG, ISOC board, and
        IETF legal counsel and issuance of a set of specific
        recommendations by the IAB and/or IESG.
   10.  Issuance of a Last Call on this document and on the subsequent
        memorandum published by the IESG and IAB.
   11.  Determination of community consensus on the updated plan.
   12.  Publication of this draft, as revised, as an Informational RFC.
   13.  Implementation, with periodic reporting back to the community.
   At each stage, the draft will be revised as appropriate.

   In addition, portions of this document are intended to form the basis
   for one or more drafts containing new procedures or Memoranda of
   Understanding related to the IETF administrative practices; these
   would eventually be published as Best Current Practices (BCP) RFCs.
   That process would begin after the initial community consensus.

1.4  Criteria for Judging an Administrative Restructuring

   The guiding principles in the analysis of the administrative
   restructuring are the criteria specified in [RFC3716], Section 3.
   These criteria are worth restating:
   1.  Better resource management:
          1.1 Uniform budgetary responsibility.
          1.2 A uniform view of revenue sources
          1.3 Clarity in the relationship with supporting organizations.
          1.4 Flexibility to provision and reprovision services.
          1.5 Administrative efficiency.
   2.  Stewardship:
          2.1 Accountability for change.
          2.2 Persistence and accessibility of records.
   3.  A better working environment:
          3.1 More service automation where appropriate.
          3.2 Better tools.

1.5  Methodology

   Preparation of this report began on June 18, 2004 as part of a
   consulting engagement to support the IETF and IAB chairs in the
   restructuring effort, based on their request for funding
   restructuring activities which was approved by the Internet Society
   Board of Trustees.  The contract is attached as Appendix A.

   The following steps were used to gather input to this report:



Malamud                Expires February 23, 2005                [Page 8]

Internet-Draft      Administrative Support Analysis          August 2004


   o  Initial briefings and continued close coordination with the Chairs
      of the IAB and the IETF.
   o  A series of consultations with members of the IAB and IESG through
      teleconferences, one-on-one email and phone conversations, and
      face-to-face discussions at IETF60.
   o  A series of consultations with staff, officers, and board members
      of the Internet Society.
   o  Discussions, by phone, email, and in person, with the staff of
      Foretec Seminars, the Internet Society, the RFC Editor, and the
      IANA, as well as a series of discussions with management at host
      institutions including CNRI, ISI, and ICANN.
   o  A large number (over 100) of discussions by phone, email, and in
      person with members of the community, including former members of
      the leadership, and individuals known to represent a wide variety
      of views.
   o  A detailed examination of relevant finances, including the
      financial reports and tax returns of organizations providing
      various support functions to the IETF.
   o  A detailed examination of operational issues, including the
      functioning of key applications such as the Internet-Draft
      Tracker, the operational and planning aspects of meetings, and the
      functioning of the core IETF network presence.
   o  A detailed review of relevant documents, including electronic mail
      archives, plenary transcripts, and RFCs, particularly the process
      BCP RFCs.
   o  In cooperation with legal counsel, a detailed examination of the
      current contractual framework and options available for
      incorporation or otherwise providing more formalization of the
      existing administrative structures, as well as a detailed
      assessment of potential risks and liabilities of such a
      transition.




















Malamud                Expires February 23, 2005                [Page 9]

Internet-Draft      Administrative Support Analysis          August 2004


2.  Analysis of Current Administrative Framework

2.1  Providers and Functions

   The IETF is an "open global community of network designers,
   operators, vendors, and researchers producing technical
   specifications for the evolution of the Internet architecture and the
   smooth operation of the Internet."[RFC3233] A variety of institutions
   provide administrative support to the IETF community:
   o  The Internet Society is "the organizational home of the Internet
      Engineering Task Force (IETF), the Internet Architecture Board
      (IAB), the Internet Engineering Steering Group (IESG), and the
      Internet Research Task Force." [www.isoc.org] [1] The Internet
      Society is a 501(c)(3) corporation with total 2002 revenues of
      $1,695,833 and expenses of $1,681,064, of which $763,423 was
      allocated as program expense to support the Standards Pillar of
      the Internet Society.[ISOC-2002] The 2004 budget for the Internet
      Society is attached in Appendix B.2.  The Internet Society and the
      IETF cooperate closely in a number of areas, as defined in
      [RFC2026], [RFC2028], [RFC2031], and [RFC3677].
   o  Since 1969, the Requests for Comments (RFC) document series and
      the office of the RFC Editor has been hosted at the Information
      Sciences Institute (ISI).  The RFC Editor's office and submission
      process is further defined in [RFC2223],
      [I-D.rfc-editor-rfc2223bis], and [RFC2555].
   o  The IETF has delegated the parameter registration function to the
      IANA, which is hosted at ICANN.  The relationship is defined in
      [RFC2860].  IANA instructions for RFC authors are defined in
      [RFC2434] and in [I-D.narten-iana-considerations-rfc2434bis].
   o  Foretec Seminars, Inc., a for-profit subsidiary of the non-profit
      Corporation for National Research Initiatives (CNRI), provides a
      variety of support services, including the planning of meetings
      three times per year, a network presence for IETF activities, and
      secretariat services such as coordination of the flow of documents
      through the IESG.  CNRI is a non-profit corporation registered
      under section 501(c)(3) of the US tax code [IRS] and has been
      providing service to the IETF since 1986 (see Section 8 for more
      details on these long-term contributions to the community).  CNRI
      owns approximately 96% of the shares of the Delaware-chartered
      Foretec Seminars, Inc.[CNRI-2002]

   For purposes of this analysis, we will examine these institutions
   using a 4-part taxonomy of functions:
   o  *Function 1: Administration.* This function includes program
      management tasks such as contract administration.  It also
      includes any legal matters and issues of financial reporting and
      transparency.




Malamud                Expires February 23, 2005               [Page 10]

Internet-Draft      Administrative Support Analysis          August 2004


   o  *Function 2: Meeting Planning.* This function includes the
      planning and management of large events such as the IETF meetings
      held three times per year, as well as more specialized activities
      such as retreats and interim Working Group meetings.
   o  *Function 3: Core Information Technology.* This function includes
      most of the network presence of the IETF, including the basic
      provisioning of computing resources (e.g., colocation, name
      service, routing, transit), and core services such as mail, web
      site, rsync, and ftp.
   o  *Function 4: Document and Information Flow.* This function
      includes the flow of information through the IETF process.  While
      Function 3, Core Information Technology, provides the basic
      platform, Function 4 uses that platform.  For example, basic
      configuration of Apache or a mail server is a core IT function,
      while what goes on the web site and in particular email messages
      is part of the document flow.  Likewise, booking an appropriate
      venue is a meeting planning function, but deciding the specific
      agenda for a meeting is part of Function 4.

2.2  Function 1: Administration

   A prime requirement of [RFC3716] was "clarity in the relationship
   with supporting organizations." The IETF sits on, to paraphrase the
   words of Brian Carpenter, a "four-legged" stool for administrative
   support functions.  Unfortunately, not all of the legs are fully
   defined.

   The most serious undefined area is the on-going relationship with
   CNRI, which in turn subcontracts to Foretec Seminars, Inc., a
   for-profit subsidiary.  CNRI has provided secretariat services for 18
   years, but there is no contract or memorandum of understanding with
   the IETF that defines the relationship.  When the arrangement was
   first started, a few dozen people attended IETF meetings.  Over time,
   that grew to over a hundred attendees, then several hundred, and
   today well over 1,000 people attend each meeting.  The gentleman's
   agreement was perfectly appropriate 18 years ago.  But, [RFC3716] was
   quite clear that today it is not a sufficient basis for managing
   close to US$2 million in annual meeting fees collected on behalf of
   the IETF community.

   The lack of a specific contract with CNRI/Foretec is one of the items
   noted in [RFC3716], however that analysis also pointed to broader
   problems throughout the IETF community.  In general, the
   administrative and support relationships have not been defined or
   kept up to date.  That has led to a variety of issues observed in
   interviews conducted for drafting this report:
   o  A lack of financial information.




Malamud                Expires February 23, 2005               [Page 11]

Internet-Draft      Administrative Support Analysis          August 2004


   o  Confusion over intellectual property.
   o  Vague definition of the lines of authority in the contracting
      relationship.

   *Financial Information.* There is no systematic, comprehensive, or
   timely reporting of financial information to the IETF leadership by
   support organizations, nor from the IETF leadership to the IETF
   community.
   o  Budgets are prepared at a very high level, are not based on
      program goals prepared by the IETF leadership, and are not based
      on historical information, such as actual versus budgeted results
      in previous periods.  This reduces the ability of the leadership
      to participate in a meaningful budget-setting process.
   o  Financial reporting is also minimal: financial results are not
      available during the course of the year, and have been typically
      reported as late as 6 months after the close of the year.  The
      reports furnished to the IETF community are non-standard in
      format, lack sufficient detail for evaluation, and are not
      furnished to the IETF with an auditor's or accountant's statement.

   *Intellectual Property.* In conducting research for this report, the
   author noted a lack of clear definition of community intellectual
   property.  Because relationships with support organizations are
   poorly defined, there is no clear, unambiguous paper trail that shows
   that resources are held in trust for the IETF community and must be
   managed in the public interest and in a manner that is responsive to
   the IETF community.  The IETF is a public standards-making
   organization and a fundamental defining characteristic of the IETF is
   the openness of the process.[RFC3668] All data, including databases,
   correspondence, minutes, and other documentation of the IETF
   operations or deliberations are an integral part of that process.

   *Definition of the Relationship* The third effect of a lack of a
   concrete understanding has been an apparent deterioration in the
   working relationship between the IETF leadership and support
   organizations.  In particular, a review of correspondence shows
   numerous instances where requests for specific functions have led to
   discussions over who has the right to request what.

   While the lack of a formal relationship with CNRI and/or Foretec
   Seminars is the most pressing issue in the Administration Function,
   the [RFC3716] goals of "uniform budget responsibility" and "a uniform
   view of revenue sources" are not being attained.  In particular:
   o  The Internet Society provides a number of administrative functions
      that go beyond the matters specified in [RFC2031].  While that
      memorandum of understanding does cover the provision of insurance,
      in addition to that task the Internet Society also provides
      discretionary funds to the IETF and IAB Chairs, and funds the



Malamud                Expires February 23, 2005               [Page 12]

Internet-Draft      Administrative Support Analysis          August 2004


      operation of the IAB.  These expenditures are reported the IETF
      community based on totals with no detail.  In addition, the RFC
      Editor contract is not published, although the statement of work
      and total expenditures are.[RFC-SOW]
   o  The IANA provides parameter registry services to the IETF.  While
      the substance of that relationship is defined in [RFC2860], the
      host institution (ICANN) does not provide financial reporting at
      sufficient granularity for an analyst to understand how much that
      function costs and thus understand the level of resources being
      used to perform that function.  In addition, no public tracking of
      requests or announcements of new registrations are provided,
      making it difficult to estimate the workload.
   o  The IETF has no uniform reporting of overall financial results.
      While the IETF Chair has posted financial reports as they are made
      available, there is no single location where an interested member
      of the community can get a fiscal picture of the operation of the
      IETF over time, or examine a standards-compliant financial report
      for a particular time period.[FASB-117]

2.3  Function 2: Meetings

   IETF meetings revenues have traditionally funded a wide variety of
   non-meeting support functions, such as the document tracking,
   submission, and distribution systems.  Meeting revenues make up the
   largest single revenue stream for IETF support (see Appendix B.1 for
   a summary of IETF financial information over the last 3 years).

   The cost per attendee per meeting has stayed at roughly $200 and
   average revenue per attendee has been roughly $450 over the last 3
   years, though recent gross fees have been as high as $545 including
   late fees.  Note that the $200/attendee cost is only direct costs
   incurred on-site, and does not include additional personnel, travel,
   and other expenses from support organizations to plan and staff the
   meeting.  Appendix C contains a summary of meeting attendance, as
   well as a summary analysis of revenue and expense figures.

   Although the number of participants in the IETF process as a whole
   appears to have been growing, the number of attendees at IETF
   meetings has been steadily dropping from a previous peak.  From 2000
   to 2003 the drop was fairly dramatic, though the figures appear to
   have stabilized recently.  The drop in attendees from the previous
   peak means a smaller number of attendees have been funding a largely
   fixed cost of non-meeting expenses.

   The meeting business is based on several cost factors.  An
   organization will contract with a primary hotel with a guaranteed
   rental of a certain number of guest rooms.  This is known as a "hard"
   contract and requires an advance deposit of a negotiable amount of



Malamud                Expires February 23, 2005               [Page 13]

Internet-Draft      Administrative Support Analysis          August 2004


   the expected room revenue.

   These amounts can be substantial.  For example, a typical contract
   where an organization is doing a one-time event might require 50% of
   expected revenue deposited as far ahead as 90 days before the event.
   In the case of a typical IETF meeting, this might be 1,000 rooms at
   $150/night for 5 nights, or a 90-day deposit of $375,000.  Proper
   negotiation of long-term relationships can reduce these cash flow
   requirements by an order of magnitude.

   In addition, the IETF requires certain facilities provided by the
   hotel, such as audio visual equipment, electrical services, and food.
   In the U.S., meeting rooms are often provided at no charge, but only
   after matters such as food have been negotiated.  In non-U.S.
   venues, the cost for meeting rooms can be as high as $125,000.

   The planning and execution of an event such as this, particularly
   three times per year, requires experienced professionals.  There are
   a number of companies and free lance professionals that specialize in
   organizing meetings for professional groups.  Many of these companies
   have become quite adept at computer networking, and if properly
   assisted in areas such as routing and the DNS, could do a very
   credible job for the IETF.  It is important to note that IETF
   meetings have been organized quite skillfully over a number of years
   and attendees have become accustomed to this level of
   professionalism.  It is important that the IETF maintain those
   standards.

   Assistance from members of the community is an important part of
   staging an IETF meeting.  In addition to formal secretariat
   activities, at least three teams of volunteers have been active
   recently:
   o  For all unhosted meetings, and for most hosted meetings, a NOC
      team of volunteers has helped establish a wireless infrastructure,
      provisioned external lines and transit, managed DNS, and provided
      a wide variety of other core services.  At IETF60, the lead
      engineer for this activity was Jim Martin.
   o  A team of volunteers organized by the University of Oregon's Video
      Lab produces audio and video streams from IETF meetings (as well
      as NANOG and a variety of other events).
   o  A team of volunteers organized by xmpp.org [2] manages a series of
      XMPP[I-D.ietf-xmpp-core] servers which are used for general
      commentary by participants, creation of informal transcriptions
      which are archived, and for a variety of personal productivity
      enhancements.[Bingo]

   Over the years, a variety of other efforts have sprung up and
   disbanded aimed at deploying leading-edge technologies in the meeting



Malamud                Expires February 23, 2005               [Page 14]

Internet-Draft      Administrative Support Analysis          August 2004


   network for interoperability testing or to familiarize attendees with
   new protocols.  Some of these activities, such as PGP key signing
   parties, are ongoing.  Others have been organized as one-time events.
   These ad hoc activities are an important part of IETF meetings.

   These self-organized, volunteer efforts, benefit from coordination
   with formal meeting planning functions.  For example, the core
   network group requires facilities and coordination with the hotel's
   telecommunications service, while the audio/video effort requires
   coordination with the hotel's audio-visual contractors.  Currently,
   none of these volunteer efforts is linked to from meeting web pages
   which are maintained by CNRI/Foretec, and there is no IETF leadership
   policy on this subject.

   While the day-to-day operational aspects of meetings are extremely
   well coordinated, long-range planning for IETF meetings is almost
   non-existent.  For example, by IETF60 in August, 2004, planning for
   2005 meetings had not reached any apparent degree of closure.  The
   IETF leadership were unaware of any firm plans for Spring or Fall of
   2005, and while some progress had been made in identifying a general
   location for the Summer 2005 meeting, specific venues were still
   being evaluated.

   Long-range planning is absolutely essential in the meeting business.
   Booking well in advance and using techniques such as repeat visits to
   properties that are allied through common ownership or marketing
   arrangements can lead to dramatic reductions in guest room rates,
   deposit requirements, and hotel charges.  Long-range planning also
   helps IETF meeting attendees plan their own schedules.  For many
   people, the commitment to go to an IETF is a major one, requiring the
   use of vacation time, personal funds, and other resources.

   Often in the past, a "host" has volunteered to assist in a meeting, a
   task that traditionally consisted of organizing the terminal room
   effort.  The concept of a single host has, for recent meetings, been
   supplanted by a series of sponsors who furnish specific resources,
   such as bandwidth or equipment.  Terminal room efforts have become
   significantly easier as the IETF has shifted from importing hundreds
   of bulky computers and terminals for attendees (see [RFC0015] for
   more information on the concept of "terminals") to a wireless network
   for laptops.  The concept of "host" (or "primary sponsor") is
   certainly a useful one, however instead of focusing on terminal room,
   the device could be used as a way of defraying meeting room charges,
   food, or other major expenses.

   One final issue should be noted that has become apparent during the
   course of research for this report.  There appears to be no clear
   guidelines on some issues related to the conduct of meetings, which



Malamud                Expires February 23, 2005               [Page 15]

Internet-Draft      Administrative Support Analysis          August 2004


   has led to disagreements between the contractor and the IETF
   leadership.  Two situations in particular are apparent:
   1.  Signage.  All hotel signage for IETF60 was in the form of the
       "Foretec IETF Summer Meeting." While this is perhaps a small
       matter, it was brought up numerous times by meeting attendees.
       In most association meetings, signage is strictly controlled so
       that all sponsors and contractors (and in the case of the IETF,
       volunteers) receive appropriate billing.
   2.  Corollary activities.  There have been several attempts to defray
       meeting costs or increase profits through the use of trade
       exhibitions, user groups, engineering task forces, and various
       other activities affiliated loosely or closely with an IETF
       meeting.  Any policy on colocation of related events at an IETF
       meeting is a policy matter that should be under the direction of
       the IAB and IESG and ultimately the IETF community.  The IETF
       leadership should formulate such a policy.

2.4  Function 3: Core Information Technology

   While meetings provide an important part of the IETF process, it has
   always been a basic policy of the community that participation in
   meetings is not required to participate in the IETF.  Mailing lists,
   document submissions, and other aspects of a continuing network
   presence are a core part of the IETF.

   As noted above, this analysis divides that network presence between a
   core information technology function, which is discussed here, and
   the uses of that network, which is described in the next section.

   Unfortunately, the IETF does not do a very good job of providing a
   network presence for its own activities.

   There are many opinions about how "good" or "standards-compliant" or
   "well-provisioned" a network infrastructure should be for any
   particular activity.  However, by most standards, it is hard to argue
   that the IETF is using the technology effectively.  A comprehensive
   analysis of network performance is impossible simply because
   statistics and logs or any other reporting is not available.
   However, a few anecdotes will serve to illustrate the point.

   There are six Web sites that contain information important for IETF
   participants.  None of these Web sites, as of August 13, 2004, were
   compliant with the W3C Validation Service and with published HTML
   standards:
   o  http://www.iana.org/ [3]
   o  http://www.rfc-editor.org/ [4]
   o  http://www.isoc.org/ [5]




Malamud                Expires February 23, 2005               [Page 16]

Internet-Draft      Administrative Support Analysis          August 2004


   o  http://www.ietf.org/ [6]
   o  http://www.iab.org/ [7]
   o  http://www.irtf.org [8]

   Likewise, none of these sites is reachable using IPv6.  Search
   engines on all four sites are primitive at best, and are not
   operational in the case of www.iana.org and www.isoc.org.  Few
   attempts are made at authentication of information, domain names, or
   applications.  Again, these are all anecdotal examples, but they
   match the findings of [RFC3716] that the IETF does not use technology
   as effectively as it could.

   One function that appears sorely lacking on any of these systems is
   the provisioning of shared environments for use by working groups,
   directorates, the IAB, the IESG, and other groups.  Working groups,
   as part of the management of chartering activity, are able to specify
   a web site and a mailing list, but there appears to be no mechanism
   that allows a portion of the web, FTP, or other core operational
   servers to be delegated for use by a particular group.

   The result has been that working groups, teams and areas create a
   diverse plethora of unconnected sites for handling IETF functions,
   such as rtg.ietf.org, ops.ietf.org, edu.ietf.org, various issue
   trackers, WG web sites and other tools hosted at diverse private web
   sites, the availability of which is critically dependent on
   volunteers - which are usually drawn from the WG.  This is not
   necessarily a bad thing, but as will be seen in Section 3.4, some
   additional support might help meet goals such as the goal stated in
   [RFC3716] of "persistence and accessibility of records." For example,
   a systematic archiving facility can assist decentralized efforts,
   unified search facilities might prove useful to those searching for
   information, and one could certainly find many ways to improve the
   navigation, presentation, and timeliness of the current IETF network
   presence.

2.5  Function 4: Document and Information Flow

   Function 4, Document and Information Flow, is the part that directly
   supports the day-to-day functioning of the IETF.  While core
   information technology provides a web server or a mail server, this
   function populates those servers with information based on the rules
   defined in process BCP RFCs as well as various unwritten procedures
   and customs.

   A demanding part of the current IETF Secretariat is the process of
   supporting the numerous bodies that proliferate through the
   community.  The IESG, of course, requires a great deal of support,
   given their bi-weekly teleconferences, and the tremendous workload of



Malamud                Expires February 23, 2005               [Page 17]

Internet-Draft      Administrative Support Analysis          August 2004


   documents to consider, working groups to charter, and other functions
   the group performs.  The high workload of IESG members has been noted
   repeatedly.

   Many of the functions required to support a deliberative body such as
   the IESG are ideally suited for a capable administrative office, a
   task often labeled as "Clerk." In the U.S., for example, the "Clerk
   of the Court" or "County Clerk" are key tasks in their respective
   organizations.  These officers and offices facilitate the flow and
   archiving of information, providing both a human and a procedural
   interface for disseminating information among participants in a
   process.

   The tasks that are encompassed in this function include:
   o  Supporting the working group charter process, which includes
      processing the initial charter, rechartering, milestone
      management, and closing of the working group.
   o  Publication of Internet-Drafts.  It is assumed that current
      efforts to automate the submission process will be successful,
      alleviating much of the manual effort that this function currently
      has.
   o  Document tracking, including a ticket-system-based response to
      document and working group management problems, announcements of
      last calls, and a variety of other functions.
   o  Managing IESG meetings, including scheduling, creation of the
      agenda, and collecting the minutes, as well as the creation and
      long-term archiving of IETF meeting proceedings.
   o  Handling the Intellectual Property Rights disclosure process (a
      process which is presently undergoing automation).
   o  Publication of official actions, such as document approvals,
      including communication of such status to groups such as the RFC
      Editor.
   o  Registration and publication of liaison statements from other
      standards bodies and publication of liaison statements, responses
      and other communications by the IETF to Standards Development
      Organizations (SDOs).
   o  Support of the Nominating Committee.
   o  Assisting the Meeting Planners in crafting an appropriate agenda
      for the IETF meetings, a complex task that requires a fairly
      detailed knowledge of the IETF operation.

   A great deal of progress has been made in this area over the last
   year, with active participation of a new Tools group and of IESG
   members.  However, there is still substantial work to make the flow
   of information smoother and more predictable.  For example, even
   though the Internet-Draft, RFC, and IANA processes are all closely
   linked in theory, in practice each organization currently maintains
   their own tracking system.  In the case of the IANA, that tracking



Malamud                Expires February 23, 2005               [Page 18]

Internet-Draft      Administrative Support Analysis          August 2004


   system is not visible outside of the organization.  Thus, interaction
   among these three bodies often relies on personal communications, and
   there are fairly frequent issues of tokens being lost, or "customers"
   (e.g., the author of a particular draft) being unclear where in the
   process they are.














































Malamud                Expires February 23, 2005               [Page 19]

Internet-Draft      Administrative Support Analysis          August 2004


3.  Recommendations for Restructuring the Administrative Framework

   This section contains recommendations for changing how the day-to-day
   support functions are provided.  Issues such as how to contract for
   services and whether or not a full-time staff member should be hired
   are dealt with in this section.  Section 4 discusses the
   institutional framework in which these activities can be housed,
   including issues such as whether to incorporate the administrative
   entity.

3.1  Recommendation 1: Hire An Administrative Director

   The deliberations of the Problem Statement Working Group made it
   clear that the IESG and IAB are both overworked with an increasingly
   large flow of technical issues.  The group also made it clear that
   the IETF Chair and the IAB Chair should continue to be picked for
   their ability to lead the IETF technical activities, not solely on
   their ability to create a conformant income statement.[RFC3774]

   One key cause of the current ambiguous management structure is the
   lack of even one full-time staff member who reports directly to the
   IETF leadership.  For example, the IETF Chair and IAB Chair attempt
   to prepare an annual budget and do financial reporting, but they do
   so without any professional help.  Among leading standards
   organizations, the IETF is alone in failing to provide any staff to
   assist the leadership in such activities.

   While zero staff is a non-standard way to run a standards body, a
   large staff would run counter to a long-established feeling
   throughout the community that the creation of a large bureaucracy
   would go against the fundamental tenets of how the IETF operates.

   In the IETF, there thus appears to be a philosophy that strongly
   favors outsourcing services whenever possible.  A first step would be
   to hire a single staff member, an Administrative Director.  This
   position would be responsible for tasks such as hiring and working
   with contractors, managing finances, and working with other
   professionals such as lawyers and auditors.  A decision on whether or
   not the ultimate size of the support staff remains at 1 or grows very
   modestly thereafter can be deferred.

   This is a fairly demanding position, as it requires a firm knowledge
   of business fundamentals, such as budgeting, contracting, logistics,
   and MIS operations.  The successful applicant for such a position
   would also have to either be already familiar with the IETF or be
   able to quickly assimilate the culture.  Prior knowledge of IETF
   politics should not be prerequisite for this position, but since an
   Administrative Director would have to work on a day-to-day basis with



Malamud                Expires February 23, 2005               [Page 20]

Internet-Draft      Administrative Support Analysis          August 2004


   a decentralized, consensus-based community, the position will require
   a certain level of political sensitivity.  The position will also
   require a certain technical cluefulness, though again, such skills
   could be acquired on the job in certain cases.

   Creation of this position should be fairly straightforward.  First, a
   job description should be created.  The position can be advertised
   using a variety of media, ranging from the IETF mailing lists to more
   formal mechanisms such as advertisements in publications such as the
   International Herald Tribune, the New York Times, the Economist, or
   the Wall Street Journal.  A yet more formal strategy would be to
   engage a professional search firm.

   Evaluation of applicants might consist of a search committee
   appointed by the IETF Chair.  The committee would conduct an initial
   review of applications, possibly solicit additional applications, and
   present a short-list for further consideration.  This short list of
   applicants could be reviewed by the IESG and IAB, possibly with
   further interviews.  The IESG and/or IAB should specify this
   procedure more fully before beginning the search.

   As part of the drafting of a call for applicants, the IETF leadership
   may want to consider what the IETF leadership groups need in the way
   of support and how they can structure the position in a way that
   attracts the best applicants.  For example, procedural mechanisms
   such as explicitly allowing the staff to be present on mailing lists,
   teleconferences, and meetings may be necessary before applicants will
   consider the position one which is doable.

   A sample draft Call for Applications is attached as Appendix E.

3.2  Recommendation 2: Establish Contracts for Core Services

   The lack of a contractual basis for present services is, as discussed
   earlier, a historical artifact of the dramatic growth of the IETF
   from a few to a few hundred to several thousand participants.

   Establishing a formal basis for such services by the close of this
   calendar year is a fundamental recommendation of this report.  A
   formal understanding for support services can take several forms,
   including contracts or memoranda of understandings.  Since the IETF
   is based on an open process, it is important that all significant
   contracts be published so they have formal standing within the
   context of the IETF community.  Such publication can be on a web
   site, or can be a republication of the contract in the RFC series.

   Just as a contract should be published as an RFC so they have formal
   standing in the community, it is important that any Memoranda of



Malamud                Expires February 23, 2005               [Page 21]

Internet-Draft      Administrative Support Analysis          August 2004


   Understandings published as an RFC have similar standing in the legal
   world.  It is important that such contracts or memoranda have
   adequate legal review to insure that the key elements required in
   contract law are present.

   For organizations providing support services who are not presently
   under contract, there are two broad strategies that can be used to
   move from the present administrative framework to the more formal one
   proposed here: sole source procurement or a Request for Information
   (RFI) or Request for Proposals (RFP) to solicit a variety of bids
   from multiple vendors, including the present providers.

   It is important to note that with the present granularity of
   historical financial information, an RFP will be an essential part of
   understanding the various expense models associated with different
   services levels and provisioning strategies.

   A decision also has to made whether the current services are
   monolithic or can be decomposed into separate pieces.  A case can be
   made that a single vendor for most services can provide the most
   responsive service.  Alternatively, one could argue that some
   services are specialized, such as meeting planning, and might be
   better carried out by a specialist.

   A final factor comes into play, which is the risk to continuity of
   operations caused by any transition.  There is also a financial cost
   to any transition, including capital costs (e.g., acquiring
   sufficient assets to do the job), cash flow requirements (e.g., hotel
   deposits for meetings can be substantial), and professional help
   (e.g., lawyers, accountants, and a variety of other services).

   There are thus a spectrum of options available within the extremes of
   RFP and sole source procurement.  This report recommends one of the
   following three strategies:
   o  *Strategy 1.* Issue an RFP for all core secretariat services.
      This would allow the current provider to bid and thus establish
      contract terms upon a successful bid, but would also allow other
      vendors to compete.
   o  *Strategy 2.* Attempt to negotiate a sole source procurement on
      all of the functions, but after a designated time-out period
      (e.g., 30 days), if the negotiation is not successful, issue an
      RFP.  The term of the sole source procurement could be a subject
      of the negotiation, or a fixed term (e.g., 1 year) could be
      established a priori.  The intention would be to issue an RFP for
      the subsequent contractual period.
   o  *Strategy 3.* Some combination of the two above options.  For
      example, attempt a sole source procurement on two of the three
      functions, and issue an RFP for the third.



Malamud                Expires February 23, 2005               [Page 22]

Internet-Draft      Administrative Support Analysis          August 2004


   Based on research conducted for this report, the author is of the
   opinion that meetings and the core "Clerk" functions would be the
   most difficult to transition to a new provider.  Meetings are
   difficult because of long lead times (and an RFP process would
   further delay 2005 planning unless an interim planning process can be
   established).  The "Clerk" functions have a great deal of
   institutional knowledge, much of which is not properly documented.

   Thus, the author of this report recommends that, if a hybrid strategy
   of attempting a sole source contract on two functions and an RFP is
   used for the third function, that core network services is a good
   candidate for an RFP and meeting planning and "Clerk" functions would
   be a good candidate for sole source procurement negotiations.

   Providing a computing infrastructure is an area with many qualified
   professionals and some well-established industry norms.  This
   strategy would also allow the IETF to move core archives that are
   presently decentralized into a common infrastructure, would provide
   more flexibility to provide resources to workgroups, and would allow
   non-contractor developed tools to coexist with existing resources.

   If an RFP is not issued a particular function, then a sole-source
   contract negotiation would be used.  There should be a clear
   understanding on intellectual property ownership, in particular a
   clear statement about all information flowing through the IETF
   process belonging to the IETF community, including the following:
   1.  Domain names, including iab.org, ietf.org, iesg.org, and
        irtf.org.
   2.  Content of Internet-Draft directories.
   3.  Content of Web sites.
   4.  Subscriber lists for all mailing lists (public and private).
   5.  Mailing list archives for all archived mailing lists (public and
        private).
   6.  Working group database content including charters.
   7.  Internet-Draft history database content.
   8.  Internet-Draft tracker database content.
   9.  Meeting minutes.
   10.  Meeting attendance records, including "blue sheets".
   11.  Archive of expired Internet-Drafts.
   12.  Documents relating to the creation and reporting of working
        group status.
   13.  Copies of any other IETF information including correspondence
        and historical records.

   In addition to intellectual property considerations, any contract
   negotiation should be bounded by two other parameters:
   1.  A transition clause is essential to allow for an orderly
       transition to other vendors in the future.  For example, if



Malamud                Expires February 23, 2005               [Page 23]

Internet-Draft      Administrative Support Analysis          August 2004


       meetings are provided on a one-year support contract, but meeting
       venues are being booked on a longer time scale, a clause in the
       contract would allow the transfer of venue to a new contractor.
       In addition, a fairly standard clause in many such contracts
       would allow the ability for a new contractor to issue employment
       offers to non-managerial employees of the old contractor as a
       transition mechanism.
   2.  A negotiating period time-out clause is essential in such a
       process.  This report recommends that a small team be assembled
       to negotiate such contracts under the direction of the IETF and
       IAB chairs, reporting back for the advice and consent of the IAB
       and IESG, and that any resulting contract be published.  If 30
       days lapse and no agreement is reached, the IAB and IESG should
       have the option, after reporting back to the community, of either
       extending the negotiating period for an additional 30 days, or
       issuing an RFP.

   While establishing a contract for uncontracted services is absolutely
   essential, some attention should also be paid to services provided by
   the IANA or the RFC Editor.  For example, returning to a multi-year
   contract with the RFC Editor instead of the current one-year
   extensions might provide for a larger investment in the function by
   the host institution.  Likewise, agreements with the Internet Society
   and ICANN should be kept current.

3.2.1  Details of Potential RFP Components

3.2.1.1  Provision of a Basic Computing Infrastructure

   Part of the philosophy of the IETF support process is to not make
   large organizations whose sole purpose is to support the IETF.  This
   is still a valid approach.

   In recent years, the support for the IETF has been carried out by a
   small number of organizations working on fairly unconnected tasks
   (RFC Editor at ISI, IANA at ICANN and secretariat and meeting
   services both handled at Foretec).

   Each organization has provided its own facilities for storage,
   publication, information distribution and list maintenance, as they
   saw it required for their tasks.  his is not necessarily an optimum
   distribution of resources.  One could imagine multiple models,
   including:
   o  The IETF controlling a distributed compute platform and storage
      facility, with multiple organizations using that to perform work
      under contract, and using each others' services when appropriate
      (management of the platform being of course one such contract).




Malamud                Expires February 23, 2005               [Page 24]

Internet-Draft      Administrative Support Analysis          August 2004


   o  A distribution much like the present, where suppliers bring their
      own resources, but with tasks distributed differently, with (for
      instance) meeting planning and Web presence maintenance being
      separate tasks, but with increased emphasis on information sharing
      and open access to information.
   o  An even larger concentration of roles, where one service
      organization takes on tasks that are distinct today.

   There is not sufficient information on price, performance or benefits
   of the various approaches today.  A Request for Proposals process,
   however, would generate the necessary information.  An RFP process
   where the components of the work are separated out to the largest
   extent practical will encourage the people who offer proposals in
   response to tell explain which parts of the RFP they would be willing
   to take on, how they would get synergy out of combining them, and
   what services they would be capable of using from other providers.

   The RFP is an information gathering tool, and will be followed by
   extensive negotiations and planning on how the services the IETF
   needs can be supplied.  This needs time, and because of this, sending
   out an RFP earlier rather than later in the decision process will
   provide important input used to structure the work to be performed.

   A draft RFP is contained in Appendix F and picks the following
   decomposition:
   1.  Meeting Planning
   2.  Systems Administration (support infrastructure)
   3.  Mailing list management
   4.  The Web presence
   5.  The "Clerk's Office" which would be responsible for the flow of
       information and administrative support for the IESG and WGs and
       the Internet-Draft publishing service.

   The RFP is structured so proposals may be received for one or more of
   the above requirements.  A single bidder may elect to provide all
   functions, one function, or some combination.  The RFP is structured
   to include a review process, and the selection criteria are based on
   what is best for the IETF as a whole, as opposed to a single formula
   such as lowest price.

   One important factor in all bids for supporting service will be the
   degree of continuity and accountability.  A "key person" principle is
   proposed where an individual contact is identified as responsible
   manager for the function.  It is this person who will give guarantees
   to the IETF for the services being available to the IETF with
   adequate availability and response times, and who will take charge of
   the organization that supplies the services.




Malamud                Expires February 23, 2005               [Page 25]

Internet-Draft      Administrative Support Analysis          August 2004


3.2.1.2  Core Network

   Currently, the IETF does not own any computers, colocation space, or
   transit capacity.  Indeed, the IETF does not even run a web site.
   All of these functions are contracted out, and the contracts include
   full provisioning of the underlying infrastructure.  As mentioned
   above, this is only one possible arrangement.  We do not have data
   that will allow us to know what to choose between the alternatives
   here.

   If adequate resources can be obtained at the right price, including
   servers, colocation space, and bandwidth, and if those resources meet
   the high standards needed to sustain IETF operations, the best thing
   for the IETF may be to operate on such an infrastructure.  Having an
   adequate in-house infrastructure controlled by the IETF also provides
   substantial flexibility in the case of future transitions of key
   contractors, but it also burdens the IETF with the requirement to
   maintain and replace equipment.

   An organization able to provide highly competent systems
   administration would be needed to support a solid computing platform.
   If purchased at commercial rates, this would probably be a
   significant part of the cost of this way of supporting services.  The
   RFP process will tell us what we can depend on.

   In terms of volunteer contributions for specialized areas such as
   nameservice or routing, the IETF may be able to draw upon volunteer
   help from participants.  It would make sense to have the relationship
   with the volunteer be slightly formalized, including a public
   appointment to the named task.  This impresses upon all that such a
   task is one of trust and makes the community aware that the
   individual or organization has assumed this particular
   responsibility.

3.2.1.3  Mail

   The IETF is a mail-intensive operation, with mailing lists for
   working groups, directorates, the IESG, the IAB, and a raft of other
   lists, not to mention the core IETF and announcement lists.

   Certain specialties in computing are considered an art unto
   themselves.  Mail is one of those areas.  The IETF Administrative
   Entity should simply contract the postmaster function to a vendor
   experienced in running environments characterized by high-volume mail
   servers, large numbers of lists with various access and moderation
   policies, a stringent archive requirement, and an ability to
   implement appropriate filtering policies (where the policy, of
   course, is ultimately set by the community).



Malamud                Expires February 23, 2005               [Page 26]

Internet-Draft      Administrative Support Analysis          August 2004


   This task is as much a public service position as it is a contract.
   The task of postmaster to the IETF Administrative Entity should be
   sufficiently attractive that it will attract highly capable bids.

   Since a variety of provisioning options are available for this
   service, the evaluation process should carefully consider each
   proposal for criteria such as stability of service and infrastructure
   redundancy.

3.2.1.4  Community Workspace Support and the IETF Network Presence

   The IETF needs far better support for our various groups that wish to
   maintain a network presence.  While the core document submission
   process is highly structured, currently the operation of individual
   working groups, directorates, or other groups all have very different
   styles.  A variety of styles is a Good Thing and should be supported.

   Systems administration can provide core tools such as web servers,
   FTP servers, and can allocate space to groups.  However, an effective
   network presence for the IETF involves many issues about how we
   archive our information, how we make it easy for new groups to form
   workspaces, and how we interface to our data through search and
   navigation facilities.

   Core systems administration is on a different layer of the stack than
   the applications support that is needed to help maintain a
   productive, happy community with a clueful Internet presence.

   It is proposed that the IETF Administrative Entity needs a webmaster
   to supplement the resources of the systems administrators.  The
   sysadmin can install Apache with appropriate modules, but building a
   core web site for the IETF involves other skills, including knowledge
   of CSS, HTML, XML, and a variety of scripting skills in languages
   such as PHP or PERL or TCL (pick your poison).

   At first glance, this may seem to be a development effort, not an
   ongoing operations effort.  However, we believe a more sustainable
   system can be built with a webmaster task which combines on-going
   responsibility for access to the core IETF information along with a
   support role for the broader community of working group chairs,
   directorates, and the like.

3.3  Recommendation 3: Provide Timely and Uniform Financial Reporting

   This report recommends that all available historical financial
   information be posted in a single public location, and that an
   immediate commitment to post more complete and timely financial
   information in the future be made.



Malamud                Expires February 23, 2005               [Page 27]

Internet-Draft      Administrative Support Analysis          August 2004


   In addition, the IETF leadership should begin formalizing the budget
   process in anticipation of any administrative restructuring efforts.
   Once issues of an institutional home for administrative functions
   have been decided, a full budget with program goals, including any
   relevant transition expenses and a cash flow analysis, will be
   required by any potential groups helping finance the IETF
   Administrative Entity as part of the funding group's annual budget
   planning processes.

   These functions are all envisioned to be the primary responsibility
   of the Administrative Director, with some contractor assistance for
   accounting and auditing tasks.

3.4  Recommendation 4: More Focus on Archives

   [RFC3716] stressed the importance of proper attention to the
   persistence and accessibility of records, including the requirement
   that "the IETF needs to maintain and support the archiving of all of
   its working documents in a way that continues to be accessible, for
   all current and future IETF workers." The IETF does not currently
   meet that requirement.  In particular:
   o  Although the RFC Editor maintains an "RFC-Online Project", over
      200 RFCs have yet to be put online.
   o  Archives of IETF working group mailing lists are spotty and
      sometimes unreliable.
   o  The ietf.org Web site does not include a comprehensive archive of
      all Internet-Drafts, though several volunteers in the community do
      maintain such sites on an informal basis.  It should be noted that
      this lack of a public comprehensive archive is a policy decision
      of the IESG.  A private comprehensive archive is a legal
      requirement, as the IETF is the original publisher of
      Internet-Drafts and is sometimes asked for old drafts in cases
      such as patent disputes.  Even if the archive is not available on
      a public site, regular audits of the completeness of the archive
      are necessary.
   o  On a short-term basis, there is no adequate backup for the
      www.ietf.org web site, which has led to periodic accessibility
      issues.
   o  Although videolab.uoregon.edu has an archive of past meeting audio
      and video feeds, that archive only dates back to IETF49.

   More attention to this important area is recommended as a key 2005
   goal.








Malamud                Expires February 23, 2005               [Page 28]

Internet-Draft      Administrative Support Analysis          August 2004


4.  Options for an Institutional Basis for Administrative Activities

4.1  Discussion of Organizational Form and Legal Domicile

   This report frames the question of organizational form as follows:
   o  Should the IETF administrative support organization be
      incorporated?
   o  If so, should it be now or later?
   o  If so, what domicile and specific form should be chosen?
   o  If so, what would be the specific nature of the relationship
      between any potential new organization and the Internet Society?

   As seen above, there is a close relationship between ISOC and the
   IETF that is independent of the administrative restructuring of IETF
   support.

   The requirements for the relationship between the IETF Administrative
   Entity and the IETF Community are:
   o  The process must generate the support that the IETF needs.
   o  The process must be transparent; people and organizations who
      donate money to the standards process must be able to verify that
      the funds have been spent on effective support of the standards
      process.
   o  The process must be efficient; the overhead of a large bureaucracy
      is not in the best interest of the IETF.
   o  The process must be flexible enough to allow the IETF support
      structure to adapt to changing IETF community requirements.
   o  The administrative entity must be responsible to the IETF.

   As an aide for discussion purposes, this report proposes four
   scenarios:
   o  *Scenario A.* The Internet Society role as legal home of the IETF
      is augmented to include the new administrative function.  As
      issues arise in the future, appropriate memoranda of understanding
      or other formal checks and balances can be developed.
   o  *Scenario B.* As in Scenario A, the Internet Society's role is
      augmented to include administration of IETF support functions.
      However, instead of waiting to understand what the issues are, the
      IETF takes proactive steps to take a more fundamental role in the
      Internet Society as its administrative home.  Thus, the difference
      is that in Scenario B, more time is spent up-front on formal
      definition of the relationship.  Needless to say, more up-front
      definition is sometimes a good thing, but can also lead to a great
      deal of time solving problems that don't exist.
   o  *Scenario C.* This scenario says that the IETF community is ready
      and willing to undertake the responsibilities for managing its
      administrative efforts.  A new incorporated body is formed to
      house those functions.  That body would be closely tied to the



Malamud                Expires February 23, 2005               [Page 29]

Internet-Draft      Administrative Support Analysis          August 2004


      Internet Society through a variety of mechanisms that show that
      the two entities are part of a "symbiotic whole."
   o  *Scenario D.* As in Scenario C, a new incorporated body is formed
      to house the administrative support functions.  But, instead of
      being as closely linked to the Internet Society, the entity bears
      much more of the burden of setting up an infrastructure.  In this
      scenario, the IETF community is now completely responsible for
      ensuring all aspects of its continued, long-term financial
      viability.

4.2  Scenario A: ISOC Operating Unit

   Presently, the Internet Society administers the RFC Editor contract
   under the direction of the IAB, provides the IAB and IETF
   discretionary funds, and purchases insurance to cover some people
   involved in IETF decision making.  The Internet Society also raises
   all funds need in excess of those provided by IETF meeting revenue.
   In this scenario, the Internet Society simply augments their current
   provision of services with appropriate contracts and program
   management services to manage the core IETF support contracts,
   including a significant number of large and small meetings, a fairly
   complex Clerk's Office, and a significant Internet presence.

   In this scenario, the Internet Society would employ the
   Administrative Director proposed in Section 3.1.  The job search
   would be conducted in consultation with the IAB and IESG.  That
   employee would in turn, again in consultation with the IAB and IESG,
   manage any sole source procurements or RFP processes that are
   approved by the Internet Society in consultation with the IAB and
   IESG.  The IETF activities would appear as line items in the Internet
   Society budget, with revenue and expenses clearly allocated by
   program area (as they currently are on ISOC financials).

4.2.1  Division of the Internet Society

   In this scenario, the IETF administrative activities would be
   undertaken as a Division of ISOC.  It would have as its day-to-day
   operational head a senior Administrative Director who would have
   operational responsibility for all the IETF administrative activities
   on behalf of the IETF community.  This individual would be an
   employee of ISOC, but management oversight would be structured to
   include direct IETF involvement including the IETF and IAB Chairs,
   and/or an Oversight Committee appointed by some IETF-specified
   process.

   Budgets would be established each year in consultation with the IAB
   and IESG, and approved by the ISOC Board as well as the IETF
   leadership.  The IETF Division would have its own bank account and



Malamud                Expires February 23, 2005               [Page 30]

Internet-Draft      Administrative Support Analysis          August 2004


   the Administrative Director would collect and manage all receipts
   (including revenues from ISOC destined for the IETF) and
   disbursements.  Operationally, this reserves for the IETF Division
   the ability to prioritize and re-allocate funds within the
   constraints of the approved budget as seems best and will provide
   maximum flexibility in service provisioning.  Once the budget has
   been agreed upon it would be the responsibility of the IETF
   Administrative Director to manage it.  All IETF finances would be
   separately accounted for and fully transparent.

   In particular,
   o  The IETF Administrative Director would have ISOC signatory
      authority for IETF contracts and would be responsible for managing
      all contractors/vendors to the IETF.
   o  The responsibilities that the IETF Administrative Director would
      have with respect to IETF activities would be determined by
      standard IETF processes (BCPs, RFCs, etc.)
   o  The Administrative Director would be hired (and removed) jointly
      by the IETF Chair, IAB Chair and the ISOC CEO according to a job
      description established by the IETF community.  Performance would
      be evaluated by those same individuals, and the personnel home for
      the Administrative Director would be in ISOC (benefits, pension,
      medical, etc.).
   o  The IETF Administrative Director could draw upon the other
      resources (accounting, technical infrastructure, reception, legal,
      etc.) of ISOC.

4.2.2  Intended benefits

   By hosting the IETF administrative activity within an existing
   organization, there is the possibility of cost reduction by sharing
   resources.  This proposal would give closer and more flexible access
   to a broad range of skills and competencies (e.g., sharing portions
   of employees time as needed).  Note: IT facilities is one area where
   the IETF may need separate support/facilities.

   Under this model, the IETF could continue to expect ISOC to take a
   significant fallback responsibility for any liabilities, whether
   financial or legal, that might be incurred by the IETF.

   This model also provides an unambiguous fund-raising model, in which
   the possibility of confusion between ISOC and IETF efforts is
   minimized.

4.2.3  Additional Considerations

   One of the considerations from which the IETF has long benefited is
   the current separation between corporate donations and IETF actions.



Malamud                Expires February 23, 2005               [Page 31]

Internet-Draft      Administrative Support Analysis          August 2004


   Instantiating this scenario would require continued care to ensure
   that the IETF maintains a reasonable distance from the funding
   streams (apart from meeting fees) and minimizes the potential of
   conflicts of interest with funding sources and other perceptions of
   excessive influence by particular participants or their
   organizations.

   While standards have always been an important component of ISOC's
   activities, ISOC as a whole does have a broader mandate, and its
   Board must be selected and empowered to meet that broader mandate,
   not just the IETF's needs.  Nevertheless, from ISOC's perspective, it
   is by design and in the governance structure, very complementary and
   ISOC has always seen its core responsibility as being to the IETF.
   The dedicated IETF Administrative Director and separated budget are
   seen as a means of ensuring continuous and adequate attention to IETF
   activities, and 3 IETF appointed seats on the Internet Society Board
   provides representation within the governing body.

   Under this model, the IETF administrative activity is naturally
   responsive to and part of the overall ISOC management structure and
   its evolution.  That is, the scenario described here is modeled on
   ISOC's current management and mission structure, assuming that it
   will be largely static over time.  ISOC has demonstrated several
   times in the past that it was willing and able to change its own
   governance structure in ways that benefited the IETF activity, and
   this specific proposal assumes that will continue to be the case,
   without making specific provision for ensuring it.

   As the Internet Society, and the Internet Society Board, would bear
   responsibility for making sure the continued IETF support function is
   carried out in a fashion that is responsible to and responsive to the
   IETF community, this scenario is potentially a large undertaking and
   should take careful consideration of the financial and logistical
   implications of undertaking such an operation and of the requirements
   of [RFC3716].

   (Note that careful consideration of the responsibilities and the size
   of the undertaking applies to all actors in all scenarios, and
   applies equally to the Internet Society, the IETF community, and to
   any other support organizations.)

4.3  Scenario B: More Formalized ISOC Operating Unit

   The philosophy in Scenario A is understand the basic parameters of
   how the relationship would work, but instead of spending considerable
   time defining all possible parameters, get to work quickly on
   pressing problems and deal with longer-term institutional issues as
   they come up or after experience is gained.  Another strategy,



Malamud                Expires February 23, 2005               [Page 32]

Internet-Draft      Administrative Support Analysis          August 2004


   outlined here as Scenario B, is to lay down more of those basic
   parameters about how the relationship would work, enshrining those
   parameters in a process BCP RFC.

   Scenario B leverages the benefits of Scenario A, while providing for
   additional mechanism further define the relationship of the Internet
   Society to the IETF community and what the provision of
   administrative support functions means.  Scenario B is identical to
   Scenario A, but more up-front work is put into defining the
   relationship.

   These mechanisms are simply suggested directions to explore based on
   suggestions from early reviewers of this draft, and further
   discussions may add or remove mechanisms from this list:
   o  Mechanism 1: Modify the Internet Society bylaws and articles of
      incorporation to explicitly recognize this expanded role and to
      explicitly refer to process BCP RFCs such as [RFC2026], [RFC3777],
      [RFC2418], and their successors as the governing mechanism for the
      standards process.
   o  Mechanism 2: Re-task the three IETF appointees to the Internet
      Society Board of Trustees so that they are representatives of the
      IETF and can receive instructions from the IETF leadership on
      particular issues.  [[anchor24: Several reviewers have pointed out
      drawbacks of this mechanism, particularly the loss of independence
      of those director seats.  These reviewers have pointed out that if
      the IETF and IAB Chairs have seats on the board as ex-officio
      members, sufficient representation of IETF interests is present.]]
   o  Mechanism 3: Give the IETF and IAB Chairs ex-officio, non-voting
      seats on the Internet Society Board of Trustees.
   o  Mechanism 4: Grant the Administrative Director observer rights at
      Internet Society Board of Trustee and Executive Committee
      meetings.
   o  Mechanism 5: Create a Memorandum of Understanding between the IETF
      and the Internet Society outlining operational parameters, such as
      how contract services get managed, how financial results are
      reported, and how other services such as insurance shall function.
      [[anchor25: Reviewers have noted that this mechanism would be
      necessary under Scenario A as well.]]
   o  Mechanism 6: Require that Internet Society meeting notices also
      include notice of consideration of issues affecting the IETF.
      This mechanism allows for community feedback on those issues prior
      to any decisions.  A variant of this mechanism would allow the IAB
      and IESG to assert that a particular issue is critical to the
      functioning of the IETF, thus requiring a supra-majority of the
      Board to approve the action.
   o  Mechanism 7: Hold an open ISOC annual Board of Trustees meeting at
      an IETF plenary meeting to facilitate more community
      participation.



Malamud                Expires February 23, 2005               [Page 33]

Internet-Draft      Administrative Support Analysis          August 2004


   As noted above, these mechanisms are simply "straw-men" proposed by
   members of the community.  Any decision to pursue this Scenario, as
   with all other Scenarios, will require a careful look at the specific
   language and provisions needed to meet the overall goals set by the
   community.  As noted in Section 1.3, this would likely be in the form
   of a process BCP RFC.

   The intended benefits of this Scenario are as in Scenario A, with the
   additional intended benefit of bringing the IETF community and ISOC
   community more closely together to manage their futures.

4.4  Scenario C: Well-Defined Entity With Close Ties to ISOC

   In this scenario, administrative support functions for the IETF are
   legally housed in a focused, incorporated institution (although the
   Administrative Directory might be physically housed within the
   Internet Society).  This scenario, as well as Scenario D, raises a
   series of issues as to the form and legal domicile of such an
   organization.

   Scenario C envisions a number of concrete linkages with the Internet
   Society, which supplement the current close interconnection of the
   IETF community with ISOC.  For example, under this scenario, primary
   fund raising responsibility would be invested in the Internet
   Society, allowing ISOC to create a unified fund raising voice
   (thought the proposed IETF Foundation would still be in a position to
   accept in-kind contributions).  In addition to the fund-raising
   agreements, this Scenario envisions a variety of other linkages, such
   as continued cooperation on education and policy.

4.4.1  How Scenario C Might Work In Practice

   There are a variety of legal forms that a formal IETF administrative
   support organization could take, but the public, non-commercial
   nature of the IETF standards process points fairly clearly to the
   formation of a non-profit organization of some sort.  A non-profit
   organization, if formally recognized, has substantial benefits, such
   as exemption from income tax, relief from VAT and sales taxes when
   procuring services, and the ability for certain contributors to
   deduct donations made to the organization.

   It also seems important symbolically that any legal underpinning that
   creates an organization for administrative support functions should
   reflect the non-profit nature of the IETF as well as reflect the
   basic nature of the IETF, which has participants and not members.
   While there are numerous organizational structures available, the
   most straightforward form for the providing IETF administrative
   support is likely to be a non-profit corporation with no members and



Malamud                Expires February 23, 2005               [Page 34]

Internet-Draft      Administrative Support Analysis          August 2004


   no stockholders.

   In addition, any formal organization for administrative support needs
   to take into account some of the unique characteristics of the IETF:
   o  It is possible that none of the members of the board of the
      administrative support organization will come from the country
      that the organization is incorporated in.
   o  The IETF already has a decision making process for a large number
      of our important decisions.  The incorporating law should allow us
      to subordinate the administrative support organization to these
      already-existing processes, as they exist now and as they may
      change in the future.

4.4.1.1  Where Might the Administrative Support Organization Be
        Domiciled?

   Perhaps the most difficult question to consider is which country the
   IETF support organization should incorporate in.  A characteristic of
   the IETF is that we are individual participants.  Unlike many
   standards bodies, the participants do not represent employers and,
   unlike the most formal standards bodies, participants do not
   represent countries.

   There is a predisposition to strongly consider countries other than
   the United States, simply because the IETF is an international group
   and a large number of key Internet institutions are already in the
   United States.  Incorporation of the IETF administrative support
   organization is an important milestone, and a predisposition is to
   try to show diversity.

   Nonprofit incorporation in a number of countries with significant
   nonprofit sectors as well as a significant number of IETF
   participants was considered.  These countries include France, Japan,
   the Netherlands, Switzerland, the United Kingdom, and the United
   States.

   Several countries were initially ruled out because their nonprofit
   laws do not permit entities that are not member-based, or have local
   requirements such as conducting business in a certain language.  In
   other cases, there are difficult to meet local requirements for
   non-profits.  For example, in order for an organization to qualify
   for tax exemption in the United Kingdom, an organization has to fall
   under one of four "heads" of charity.  Three of these are
   general-purpose heads, including the relief of poverty, advancement
   of education, and the advancement of religion.  However, none of
   these three are the intended direct focus of the IETF administrative
   support organization.  The fourth category is "purposes beneficial to
   the community" and it appears that our local nexus to the country is



Malamud                Expires February 23, 2005               [Page 35]

Internet-Draft      Administrative Support Analysis          August 2004


   somewhat slim and might be viewed somewhat skeptically by the Charity
   Commissioners.

   As part of this analysis, a "flag of convenience" approach, such as
   the Bahamas, was considered and ruled out.  It does not seem that an
   off-shore registration poses substantial benefits and would certainly
   make it appear that the IETF administrative support organization
   perhaps had something to hide.  This is clearly not appropriate.

   Incorporating simultaneously in several jurisdictions to make the
   point that the IETF is not part of any one country was also
   considered.  As appealing as this is in theory, in practice it
   substantially increases the cost of incorporation, the complexity of
   on-going operations, and exposes the IETF administrative support
   organization to liability in multiple legal jurisdictions.

   After weighing a number of issues, it appears that the Netherlands,
   Switzerland, and the United States make the most sense.

   Either of these three jurisdictions would work.  The IETF has strong
   participation from the Netherlands, and a number of nonprofit
   Internet groups have thrived in this environment.  By contrast, we
   have far fewer participants from Switzerland.  However, because
   Switzerland is not part of the European Union, it does not suffer
   from the potential risks of the more activist governmental presence
   in the EU and in the US.

   A U.S.  non-profit, non-member corporation is being recommended under
   Scenario C, but with an important proviso.  This recommendation is
   based on simple considerations of expediency and pragmatism: a
   transition will be simplest and least risky (in the short term).
   Since there are enough issues on the table, it seems easiest to
   simplify the equation by taking this variable out.  The reasoning is
   as follows:
   o  Administrative support for the IETF is currently enmeshed in a
      series of relationships with other institutions, most of which are
      also U.S.-chartered non-profit organizations.  Any change in the
      institutional status of administrative support functions will
      require familiarity with U.S.  nonprofit law.  Incorporation in
      another country would require familiarity with those laws as well.
      Thus, the incorporation expenses would be higher and the process
      would take longer.
   o  U.S.  law has a strong concept of "nexus," which is a
      determination of when a foreign organization has enough
      relationship to U.S.  law to fall under the jurisdiction of a U.S.
      court.  Because of a long history of operating in the U.S.,
      numerous meetings in the U.S., and the large number of U.S.
      residents who are participants and leaders, we feel it is likely



Malamud                Expires February 23, 2005               [Page 36]

Internet-Draft      Administrative Support Analysis          August 2004


      that U.S.  courts would find nexus in relation to our US-based
      activities, even if the IETF administrative support organization
      was incorporated in another country.  In other words,
      incorporating in a country besides the U.S.  does not necessarily
      free the support organization from any perceived vagaries of U.S.
      law.
   o  Incorporating in a country other than the US may have tax
      implications if the Internet Society is providing funding support.
   o  U.S.  corporations have traditionally been large contributors to
      the development of public aspects of the Internet, a category into
      which IETF activities fall (and consequently, the activities of an
      IETF administrative support organization fall).  U.S.
      corporations are somewhat chauvinistic, and it is our experience
      in raising funds that it is easier to get a donation if the
      recipient is a duly-chartered U.S.  tax-exempt organization.  Not
      surprisingly, non-U.S.  corporations have shown more flexibility
      in this regard.  Note that under this scenario, the Internet
      Society would take primary responsibility for fund-raising,
      however deductibility of donated resources such as computers and
      bandwidth is still useful.
   o  It is very likely that an IETF administrative support organization
      would be deemed to clearly fall under the "scientific" and
      "educational" grounds for classification as a tax-exempt charity
      under section 501(c)(3) of the IRS code, so a tax-exempt
      application should be quite straight-forward.
   o  The incorporation laws of the U.S.  states being considered do not
      require that any members of the Board of Trustees be of a certain
      nationality or state residency (e.g., there are no "local
      director" requirements).  The U.S.  Dept.  of Commerce
      foreign-controlled organization reporting requirements apply only
      to "business enterprises", and do not apply to non-profit entities
      such as an IETF administrative support organization.

   That said, it should be stated very clearly that any of the three
   incorporation domiciles (Switzerland, Netherlands, and U.S.) could
   probably be made to work.  If the community feels a further in-depth
   examination of alternative domiciles is in order, and is willing to
   bear the increased costs of time and money, alternative domiciles
   could be more carefully examined.

   If incorporating in the U.S., Virginia seems a logical pick as the
   state of domicile to allow the IETF administrative support
   organization to make use of ISOC headquarters to house its single
   employee (though the employee might be able to be housed at the
   Internet Society even if the incorporation were elsewhere, for
   example the ISOC Geneva office).  A variety of other options were
   examined as states of incorporation, including [Delaware] and
   [California], but there appeared to be no significant advantages.  In



Malamud                Expires February 23, 2005               [Page 37]

Internet-Draft      Administrative Support Analysis          August 2004


   particular, there are no significant differences in issues such as
   director liability that would make incorporating outside the place of
   actual domicile attractive.

4.4.1.2  Sample Draft Core Principles

   [ed.: This section intends to state basic principles of establishment
   and governance, suitable for publication, after considerable
   discussion, as a procedural Best Current Practice document.]

4.4.1.2.1  Sample Draft Principles of Establishment and Governance

   The following principles are proposed for the establishment and
   governance of an administrative support organization in support of
   the IETF under Scenario C, and are based on the Sample Draft Articles
   of Incorporation attached in Appendix D.1 and the Sample Draft Bylaws
   attached in Appendix D.2:
   1.  The name of the organization shall be the IETF Foundation.
   2.  The IETF Foundation shall be incorporated under the laws of the
       State of the Virginia in the United States as a non-stock
       corporation with a domicile in the State of Virginia and shall
       apply for exemption from U.S.  taxation under section 501(c)(3)
       of the Internal Revenue Code of the United States.
   3.  The IETF Foundation shall have no members or shareholders.
   4.  The IETF Foundation shall be governed by a Board of Trustees, who
       shall be responsible for the fiscal, legal, and administrative
       infrastructure that support the activities of the IETF.  The
       governance of the IETF, the standards process, and all other
       aspects of how we make our standards are defined in the
       procedural Best Current Practice RFC series, which will be
       explicitly referenced in the organization documents of the IETF
       Foundation.
   5.  The Board of Trustees shall consist of a fixed, odd number of
       members, initially set at 7 members.
   6.  The annual meeting of the Board of Trustees of the IETF
       Foundation shall be announced on the IETF mailing list at least
       30 days before it occurs and must be held at a regular IETF
       meeting.  This meeting shall be open to IETF attendees and
       minutes shall be promptly posted on-line.
   7.  The Board of Trustees shall appoint a Secretary and a Treasurer,
       who need not be members of the Board of Trustees.  The
       Administrative Director of the IETF Foundation shall provide
       staff support to the Board of Trustees.
   8.  The Board of Trustees shall be composed to strike a balance
       between outside and "inside" directors.  It is proposed that the
       IETF and IAB chairs hold voting, ex-officio seats, and that
       mechanisms such as the Nominating Committee and the appointment
       of certain seats by the Internet Society fulfill the outside



Malamud                Expires February 23, 2005               [Page 38]

Internet-Draft      Administrative Support Analysis          August 2004


       director obligations.

   The Board of Trustees would have strong governance over a limited
   scope of activities (e.g., the fiscal, legal, and administrative
   infrastructure that are the charter of the IETF Foundation) but would
   have no authority over the IETF standards process.  In this board
   composition, the ISOC and Nomcom appointments insure that outside
   directors with no perceived conflicts of interest are on the board.

   All nominating bodies should make strong fiscal, legal, and
   administrative acumen essential selection criteria for this position.
   However, we should note strongly that the Chairs of the IAB and IETF
   are ex-officio members (e.g., they are full voting members who hold
   the position based on their official roles as chairs of these two
   bodies), and that it is not expected that the current criteria for
   selection of these two positions should be changed.

   For position-based appointments such as the IETF Chair, the Trustee
   would serve concurrent with their normal appointment.  For non
   position-based appointments, a term proposed for the nominated
   positions is three years with staggered appointments.  However, the
   nominating body might have the power to change their appointee during
   their term.

   All members of the Board of Trustees IETF Foundation are subject to
   the same recall procedures in effect for the IETF leadership such as
   members of the IAB and IESG.  [[anchor31: Mike St.  Johns comments
   that use of the Nomcom and the recall procedure are both
   inappropriate as they are tailored towards selection of and recall of
   technical leadership, which is not necessarily appropriate for the
   fiscal, legal, and administrative skill sets needed in a board for
   the Foundation.  --Mike St.  Johns]]

4.4.1.2.2  Sample Draft Principles of Operation of a Potential IETF
          Foundation

   [ed.: This section intends to state basic principles of establishment
   and governance, suitable for publication, after considerable
   discussion, as a procedural Best Current Practice document.  This
   section is very tentative and contains principles that are used to
   draft bylaws and articles of corporation, samples of which are shown
   in Appendix D.1 and Appendix D.2.]

   The following are some general principles for the operation of the
   IETF Foundation:
   1.  The IETF Foundation shall employ a Administrative Director of the
       IETF Foundation, who shall be hired by the Board of Trustees with
       the the advice and consent of the IESG and IAB.



Malamud                Expires February 23, 2005               [Page 39]

Internet-Draft      Administrative Support Analysis          August 2004


   2.  All support services shall be contracted in an open and
       transparent manner.
   3.  The Administrative Director shall submit a proposed annual budget
       to the Board of Trustees at least 90 days before the beginning of
       the fiscal year.  Such budget shall be developed with the advice
       and consent of the IAB and IESG.
   4.  The Administrative Director shall serve on the Board of Trustees
       as a non-voting, ex-officio member.
   5.  The Board of Trustees shall select a professional audit firm and
       shall commission an audit immediately upon the close of each
       fiscal year.
   6.  The IETF Foundation will conduct financial reporting in a fully
       transparent fashion.  Audits shall be conducted promptly and
       published.  Tax returns shall be published.  Detailed financial
       statements will be published on a regular basis, including timely
       reports on the financial results of IETF meetings.

4.5  Scenario D: Autonomous Entity

   Scenario D has much of the same analysis as for Scenario C.  However,
   in this scenario, instead of a mutually-beneficial symbiotic whole,
   the IETF Foundation sets out to ensure its own viability independent
   of the Internet Society.  For instance, the foundation might pursue
   direct contributions from industry instead of relying on a unified,
   ISOC-based fund raising effort as outlined in Scenario C.

   Needless to say, direct solicitation of funds would require great
   care to isolate the IETF standards process from funding agencies so
   that there can be no question of undue influence.  In Scenarios A
   through C, this isolation of process from funding is provided by the
   Internet Society.




















Malamud                Expires February 23, 2005               [Page 40]

Internet-Draft      Administrative Support Analysis          August 2004


5.  Future Work

5.1  Short-Term

   This report outlines some fundamental decisions facing the IETF
   community about how administrative support functions should be
   procured and what institutional framework they should be housed in.
   If a consensus is reached on a direction to move on these key
   decisions, a number of short-term tasks will be required:
   1.  Formulation of a budget for 2005, including a cash flow analysis.
   2.  If formal incorporation is chosen, drafting and filing of bylaws
       and articles.  If an operating unit is chosen, drafting of any
       memoranda of understanding.
   3.  If a decision is made to negotiate a sole source contract for one
       or more functions, a negotiating team would need to be appointed.
   4.  If a decision is made to issue a Request for Proposal for one or
       more functions, a drafting team would need to be appointed and a
       process for evaluation described.
   5.  If a decision is made to appoint an Administrative Director, a
       call for applicants would need to be issued.

5.2  Long-Term

   While [RFC3716] set out principles for administrative restructuring,
   it should be remembered that administrative restructuring is just one
   of the tasks facing the IETF.  [RFC3774] set out a number of
   fundamental issues facing the community.  Any administrative
   restructuring should be performed quickly and efficiently, allowing a
   renewed focus on more important issues, such as how the IETF can
   remain and become "an open global community of network designers,
   operators, vendors, and researchers producing technical
   specifications for the evolution of the Internet architecture and the
   smooth operation of the Internet."[RFC3233]

   Much of that focus on "more important issues" is already present in
   the IETF today.  Working Groups such as [NEWTRK] and [ICAR] are
   looking hard at the basic IETF processes and how they can be made
   better.

   In considering the future, it is often worth looking at the past.
   Edwin T.  Layton, Jr., in his 1986 study of the rise (and fall) of
   standards bodies in 1900's, tells of an interesting group, the
   Institute of Radio Engineers (IRA).  Founded in 1912, the IRA was
   different from other professional bodies of the time, with a focus on
   individual instead of corporate membership, an adherence to
   engineering excellence, and, despite being a predominantly American
   body, insisting that the word "American" not be added to the IRE's
   name as a way of emphasizing the international nature of their



Malamud                Expires February 23, 2005               [Page 41]

Internet-Draft      Administrative Support Analysis          August 2004


   pursuits.[Layton] The IRA was founded in reaction to dissatisfaction
   with a more formal body of the time, the American Institute of
   Electrical Engineers (AIEE).  The IRA became known for pioneering
   work in standards area such as FM and commercial black-and-white and
   color television.  Although the IRA was one of the smaller standards
   bodies, it was one of the most effective.[Hoffman] In 1963, the IRA
   merged with the AIEE to become the IEEE.

   Layton's study of professional societies and standards bodies in the
   engineering profession from early the 1900 to the 1960s is highly
   instructive, particularly the way different groups dealt with the
   tensions between the role of participants as individuals engineers
   versus their other roles as corporate employees or representatives of
   countries.  The long-term relevance of the IETF is directly tied to
   the ability of the community to focus on core values such as "rough
   consensus and running code"[RFC1958] and an avoidance of
   entanglements at layers 8-10 of the OSI Reference Model.[OSI]

   As Thomas Huxley once commented in describing the conduct of the
   affairs of the Royal Society, "our business was (precluding matters
   of theology and state affairs) to discourse and consider of
   philosophical enquiries, and such as related thereunto."[Huxley] The
   IETF can certainly learn much from an examination of it's own guiding
   principles and by examining the history of other SDOs such as the
   Royal Society and the Institute of Radio Engineers.


























Malamud                Expires February 23, 2005               [Page 42]

Internet-Draft      Administrative Support Analysis          August 2004


6.  IANA Considerations

   [RFC2434] states each Internet-Draft should contain an "IANA
   Considerations" section.  [RFC3716] noted that a frequent problem for
   the IANA is documents that do not contain such a section, thus
   requiring a full scan of the document.

   This submission contains no specific modifications to existing
   registries or creation of new registries.  However, the submission
   contains a number of sections that may impact the overall operation
   of the IANA.  A full scan of the document is thus recommended.








































Malamud                Expires February 23, 2005               [Page 43]

Internet-Draft      Administrative Support Analysis          August 2004


7.  Security Considerations

   Improper formulation of the legal framework underlying the IETF may
   expose the institution and individuals in leadership positions to
   potential legal risks.  Any such risk under this plan appears to be
   equivalent to the risk faced by the community under the current legal
   framework.  This risk is further mitigated by a thorough review by
   legal counsel, and by use of insurance coverage.

   The legal exposure is best minimized by a careful adherence to our
   procedures and processes, as defined by the Best Current Practice
   Series.  A carefully stated process, such as the BCP documents that
   govern the selection of leadership positions and define the standards
   process are the best insurance against legal exposure, provided care
   is taken to stick to the process standards that have been set.
   Adherence to a public rule book and a fully open process are the most
   effective mechanisms the IETF community can use.

   Improper management controls and procedures or other imprudent fiscal
   or administrative practices could expose the IETF to a risk of
   insolvency.  Careful selection of trustees, a process of budget
   approval, and a methodical system of fiscal controls are necessary to
   minimize this risk.




























Malamud                Expires February 23, 2005               [Page 44]

Internet-Draft      Administrative Support Analysis          August 2004


8.  Acknowledgment of CNRI Contribution to the IETF Community

   As this plan proposes a transition from the past to the future, the
   author feel it is essential to acknowledge the enormous contributions
   made to the IETF and the Internet by the Corporation for National
   Research Initiatives (CNRI) and their Chairman, CEO, and President,
   Dr.  Robert E.  Kahn.

   Dr.  Kahn's pioneering early leadership in the evolution of the
   Internet is well-known, including the seminal paper on the
   Transmission Control Protocol,[Cerf and Kahn] his key operational
   role in engineering the early Internet (see, e.g., [RFC0371]), and
   his leadership of the vastly influential DARPA Information Processing
   Techniques Office (IPTO), where he initiated a billion-dollar
   Strategic Computing Program which was responsible for funding,
   guiding, and encouraging technology that makes up much of today's
   infrastructure.

   Perhaps less well-known or appreciated is the contribution that Dr.
   Kahn and CNRI have made to the evolution of the IETF.  Since 1987,
   CNRI has housed the IETF Secretariat, supporting 56 IETF meetings
   with over 55,000 total attendees, not to mention over 30,000
   Internet-Drafts processed, several thousand teleconferences hosted,
   and a theoretically finite but practically uncountable number of
   cookies consumed.

   CNRI's support allowed the IETF community to evolve in the way it
   has.  Many of the values we have created as a community were possible
   only possible because we had a professional secretariat to provide
   support.  For example, the IETF takes very seriously the idea that
   individuals, not institutions or countries, are the participants (not
   members) in the process.  A stable secretariat has allowed us to
   preserve those values without worrying about pesky issues such as
   corporate sponsorship or membership fees.

   A number of CNRI and Foretec staff have formed the secretariat over
   the years.  These people have all worked long and hard and, for many
   IETF participants, these staff have been instrumental in making the
   IETF an effective forum for the development of Internet standards and
   technology.  They deserve our sincere and continuing thanks.

   As the IETF has scaled, we have continued to rely on CNRI to provide
   a base of stability.  As the IETF passes the age of 18, it is time
   for the IETF to take responsibility for its own affairs.







Malamud                Expires February 23, 2005               [Page 45]

Internet-Draft      Administrative Support Analysis          August 2004


9.  Acknowledgment of Contributions and Reviews

   A number of people contributed their time in telephone interviews,
   email exchanges, and reviews of the draft.  These exchanges resulted
   in many useful suggestions.  Needless to say, our acknowledgment of
   their contribution should not in any way be used to necessarily infer
   support for anything contained herein.  These individuals include:
   Bernard Aboba, Harald Alvestrand, Fred Baker, Bob Braden, Scott
   Bradner, Brian Carpenter, David Clark, Jorge Contreras, Dave Crocker,
   Steve Crocker, Joao Damas, Leslie Daigle, Lynn DuVal, Patrik
   Falstrom, Bill Fenner, Ted Hardie, Bob Hinden, Paul Hoffman, Geoff
   Huston, Mike St.  Johns, David Kessens, Robert Kahn, Daniel
   Karrenberg, John Klensin, Rebecca Malamud, Allison Mankin, Thomas
   Narten, Jun Murai, Thomas Narten, Eric Rescorla, Pete Resnick, Joyce
   Reynolds, Lynn St.  Amour, Mike St.  Johns, Paul Vixie, Margaret
   Wasserman, and Bert Wijnen.  The author apologizes for any names
   inadvertently omitted.

   This document was created with "xml2rfc" as specified in [RFC2629].
































Malamud                Expires February 23, 2005               [Page 46]

Internet-Draft      Administrative Support Analysis          August 2004


10.  References

10.1  Normative References

   [RFC1958]  Carpenter, B., "Architectural Principles of the Internet",
              RFC 1958, June 1996.

   [RFC2014]  Weinrib, A. and J. Postel, "IRTF Research Group Guidelines
              and Procedures", BCP 8, RFC 2014, October 1996.

   [RFC2026]  Bradner, S., "The Internet Standards Process -- Revision
              3", BCP 9, RFC 2026, October 1996.

   [RFC2028]  Hovey, R. and S. Bradner, "The Organizations Involved in
              the IETF Standards Process", BCP 11, RFC 2028, October
              1996.

   [RFC2031]  Huizer, E., "IETF-ISOC relationship", RFC 2031, October
              1996.

   [RFC2223]  Postel, J. and J. Reynolds, "Instructions to RFC Authors",
              RFC 2223, October 1997.

   [RFC2418]  Bradner, S., "IETF Working Group Guidelines and
              Procedures", BCP 25, RFC 2418, September 1998.

   [RFC2434]  Narten, T. and H. Alvestrand, "Guidelines for Writing an
              IANA Considerations Section in RFCs", BCP 26, RFC 2434,
              October 1998.

   [RFC2555]  Braden, R., Reynolds, J., Crocker, S., Cerf, V., Feinler,
              J. and C. Anderson, "30 Years of RFCs", RFC 2555, April
              1999.

   [RFC2850]  Internet Architecture Board and B. Carpenter, "Charter of
              the Internet Architecture Board (IAB)", BCP 39, RFC 2850,
              May 2000.

   [RFC2860]  Carpenter, B., Baker, F. and M. Roberts, "Memorandum of
              Understanding Concerning the Technical Work of the
              Internet Assigned Numbers Authority", RFC 2860, June 2000.

   [RFC3005]  Harris, S., "IETF Discussion List Charter", BCP 45, RFC
              3005, November 2000.

   [RFC3184]  Harris, S., "IETF Guidelines for Conduct", BCP 54, RFC
              3184, October 2001.




Malamud                Expires February 23, 2005               [Page 47]

Internet-Draft      Administrative Support Analysis          August 2004


   [RFC3233]  Hoffman, P. and S. Bradner, "Defining the IETF", BCP 58,
              RFC 3233, February 2002.

   [RFC3667]  Bradner, S., "IETF Rights in Contributions", BCP 78, RFC
              3667, February 2004.

   [RFC3668]  Bradner, S., "Intellectual Property Rights in IETF
              Technology", BCP 79, RFC 3668, February 2004.

   [RFC3677]  Daigle, L. and Internet Architecture Board, "IETF ISOC
              Board of Trustee Appointment Procedures", BCP 77, RFC
              3677, December 2003.

   [RFC3683]  Rose, M., "A Practice for Revoking Posting Rights to IETF
              mailing lists", BCP 83, RFC 3683, February 2004.

   [RFC3710]  Alvestrand, H., "An IESG charter", RFC 3710, February
              2004.

   [RFC3716]  Advisory, IAB., "The IETF in the Large: Administration and
              Execution", RFC 3716, March 2004.

   [RFC3774]  Davies, E., "IETF Problem Statement", RFC 3774, May 2004.

   [RFC3777]  Galvin, J., "IAB and IESG Selection, Confirmation, and
              Recall Process: Operation of the Nominating and Recall
              Committees", BCP 10, RFC 3777, June 2004.

10.2  Informative References

   [.]        Malamud, C., Ed., "IETF Administrative Support Functions",
              draft-malamud-consultant-report-00 (work in progress),
              August 2004, <http://public.resource.org/adminrest/>.

   [Bingo]    Anonymous, "Buzzword Bingo", 1996,
              <http://hacks.mit.edu/Hacks/by_year/1996/gore/>.

   [CNRI-2002]
              CNRI, "Form 990 - Return of Organization Exempt from
              Income Tax - 2002", EIN 52-1447747, November 2003.

   [California]
              State of California, "California Corporations Code",
              Undated,
              <http://www.leginfo.ca.gov/cgi-bin/calawquery?codesection=corp>
              .

   [Cerf and Kahn]



Malamud                Expires February 23, 2005               [Page 48]

Internet-Draft      Administrative Support Analysis          August 2004


              Cerf, V. and R. Kahn, "A Protocol for Packet Network
              Intercommunication", IEEE Trans. on Comm., Vol. COM-23,
              pp. 637-648, May 1974.

   [Delaware]
              State of Delaware, "Title 8. Corporations -- Chapter 1.
              General Corporation Law -- Subchapter 1. Formation",
              Undated,
              <http://www.delcode.state.de.us/title8/c001/sc01/index.htm#TopOfPage>
              .

   [FASB-117]
              FASB, "Financial Statements of Not-For-Profit
              Organizations", FASB 117, June 1993,
              <htttp://www.fasb.org/st/summary/stsum117.shtml>.

   [Hoffman]  IEEE Center for the History of Electrical Engineering,
              "The Origins of the IEEE", 1984,
              <http://www.ieee.org/organizations/history_center/historical_articles/history_of_ieee.html>
              .

   [Huxley]   Huxley, T., "On the Advisableness of Improving Natural
              Knowledge (A Lay Sermon Delivered in St. Martin's Hall)",
              Project Gutenberg THX1410, Fortnightly Review 3 (1866):
              626-37, January 1866,
              <http://etext.library.adelaide.edu.au/cgi-bin/pg-html/mirror/pg/etext01/thx1410.txt>
              .

   [I-D.alvestrand-ietf-mission]
              Alvestrand, H., "A Mission Statement for the IETF",
              draft-alvestrand-ietf-mission-02 (work in progress), June
              2004.

   [I-D.daigle-adminrest]
              Daigle, L., "A Proposal for IETF Administrative
              Restructuring", draft-daigle-adminrest-00 (work in
              progress), February 2004.

   [I-D.ietf-problem-process]
              Davies, E. and J. Hofmann, "IETF Problem Resolution
              Process", draft-ietf-problem-process-04 (work in
              progress), January 2004.

   [I-D.ietf-xmpp-core]
              Saint-Andre, P., "Extensible Messaging and Presence
              Protocol (XMPP): Core", draft-ietf-xmpp-core-24 (work in
              progress), May 2004.




Malamud                Expires February 23, 2005               [Page 49]

Internet-Draft      Administrative Support Analysis          August 2004


   [I-D.narten-iana-considerations-rfc2434bis]
              Narten, T. and H. Alvestrand, "Guidelines for Writing an
              IANA Considerations Section in RFCs",
              draft-narten-iana-considerations-rfc2434bis-00 (work in
              progress), August 2004.

   [I-D.rfc-editor-rfc2223bis]
              Reynolds, J. and R. Braden, "Instructions to Request for
              Comments (RFC) Authors", draft-rfc-editor-rfc2223bis-07
              (work in progress - do not cite as a normative reference),
              August 2003,
              <http://www.ietf.org/internet-drafts/draft-rfc-editor-rfc2223bis-07.txt>
              .

   [ICAR]     The IETF, "Charter of the Improved Cross-Area Review
              (icar) Working Group", June 2004,
              <http://www.ietf.org/html.charters/icar-charter.html>.

   [IETF-2001]
              Alvestrand, H., "The Financials of the IETF -- 2001",
              February 2003,
              <http://www.alvestrand.no/ietf/chair/financials.html>.

   [IETF-2002]
              Alvestrand, H., "The Financials of the IETF -- 2002", July
              2003,
              <http://www.alvestrand.no/ietf/chair/financials-2002.html>.

   [IETF-2003]
              Alvestrand, H., "The Financials of the IETF -- 2003", May
              2004,
              <http://www.alvestrand.no/ietf/chair/financials-2003.html>.

   [IETF-2004]
              Alvestrand, H., "The IETF Budget -- 2004", May 2004,
              <http://www.alvestrand.no/ietf/chair/budget-2004.html>.

   [IRS]      U.S. Code, "Title 26, Sec. 501: Exemption from tax on
              corporations, certain trusts, etc.", Undated,
              <http://www4.law.cornell.edu/uscode/26/501.html>.

   [ISOC-2002]
              Internet Society, "Form 990 - Return of Organization
              Exempt from Income Tax - 2002", EIN 52-1650477, October
              2003.

   [ISOC-2004]
              Internet Society, "37th Board of Trustees meeting of the



Malamud                Expires February 23, 2005               [Page 50]

Internet-Draft      Administrative Support Analysis          August 2004


              Internet Society", Resolution 3-20, December 2003, <http:/
              /www.isoc.org/isoc/general/trustees/mtg37.shtml>.

   [Layton]   Layton, E., "The Revolt of the Engineers", The John
              Hopkins University Press, ISBN 0-8018-3287-X, 1986.

   [NEWTRK]   The IETF, "Charter of the New IETF Standards Track
              Discussion (newtrk) Working Group", June 2004,
              <http://www.ietf.org/html.charters/newtrk-charter.html>.

   [OSI]      Wikepedia, "Open Systems Interconnection Reference Model",
              ISO/IEC 7498-1, August 2004,
              <http://en.wikipedia.org/wiki/OSI_seven-layer_model>.

   [RFC-SOW]  Internet Society, "Statement of Work--RFC Editor",
              Undated,
              <http://www.isoc.org/standards/rfceditor/sow.shtml>.

   [RFC0015]  Carr, C., "Network subsystem for time sharing hosts", RFC
              15, September 1969.

   [RFC0371]  Kahn, R., "Demonstration at International Computer
              Communications Conference", RFC 371, July 1972.

   [RFC2629]  Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629,
              June 1999.

   [Virginia]
              State of Virginia, "Title 13.1: Corporations, Limited
              Liability Companies, Business Trusts", Undated,
              <http://leg1.state.va.us/cgi-bin/legp504.exe?000+cod+TOC1301000>
              .



















Malamud                Expires February 23, 2005               [Page 51]

Internet-Draft      Administrative Support Analysis          August 2004


URIs

   [1]   <http://www.isoc.org/standards>

   [2]   <http://www.xmpp.org/>

   [3]   <http://validator.w3.org/check?uri=http%3A%2F%2Fwww.iana.org%2F&charset=%28detect+automatically%29&doctype=%28detect+automatically%29>

   [4]   <http://validator.w3.org/check?uri=http%3A%2F%2Fwww.rfc-editor.org%2F&charset=%28detect+automatically%29&doctype=%28detect+automatically%29>

   [5]   <http://validator.w3.org/check?uri=http%3A%2F%2Fwww.isoc.org%2F&charset=%28detect+automatically%29&doctype=%28detect+automatically%29>

   [6]   <http://validator.w3.org/check?uri=http%3A%2F%2Fwww.ietf.org%2F&charset=%28detect+automatically%29&doctype=%28detect+automatically%29>

   [7]   <http://validator.w3.org/check?uri=http%3A%2F%2Fwww.iab.org%2F>

   [8]   <http://validator.w3.org/check?uri=http%3A%2F%2Fwww.irtf.org%2F&charset=%28detect+automatically%29&doctype=%28detect+automatically%29>

   [9]   <http://www.ietf.org/PASTMEETINGS/IETF-60b.html>

   [10]  <http://www.ietf.org/PASTMEETINGS/IETF-59b.html>

   [11]  <http://www.ietf.org/PASTMEETINGS/IETF-58b.html>

   [12]  <http://www.ietf.org/PASTMEETINGS/IETF-57b.html>

   [13]  <http://www.ietf.org/PASTMEETINGS/IETF-56B.html>

   [14]  <http://www.state.va.us/cgi-bin/scc-clerkdl.pl?scc819&Articles_of_Incorporation_-_Nonstock_Corporation>


Author's Address

   Carl Malamud (editor)
   Memory Palace Press
   PO Box 300
   Sixes, OR  97476
   US

   EMail: carl@media.org











Malamud                Expires February 23, 2005               [Page 52]

Internet-Draft      Administrative Support Analysis          August 2004


Appendix A.  Consulting Contract

   AGREEMENT FOR CONSULTING SERVICES
   Contract between CARL MALAMUD AND THE INTERNET SOCIETY

   *Contract:*

   Carl Malamud (hereafter known as the Consultant) agrees to provide
   consulting services to the Internet Engineering Task Force (IETF),
   the Internet Architecture Board (IAB) and the Internet Society (ISOC)
   subject to the terms and conditions specified below.  Under this
   agreement, the Consultant is acting as an independent contractor and
   assumes all responsibilities for federal and state income taxes,
   social security and medicare tax, medical insurance, and other
   applicable filings associated with his status.

   *Scope:*

   The Consultant will provide the following services outlined in
   Appendix I.  It is anticipated that the responsibilities will require
   20 days per month to accomplish the objectives for which said
   Consultant was engaged.

   Consultant understands and agrees that this Contract is being
   executed with a view to supporting the IETF/IAB as it considers
   whether, and if so, how, it might wish to restructure for purposes of
   future IETF/IAB endeavors.  In the performance of this Contract,
   Consultant agrees to exercise fair and professional judgment for the
   benefit of the IETF/IAB and to treat all existing and/or potential
   partners of the IETF/IAB in a fair manner while protecting any
   business confidences that each might have.

   *Contract Term:*

   The contract will begin on 21 June 2004 and end on 21 December 2004.
   For services rendered under this contract the Consultant will be paid
   a fee of $16,000 per month due and payable at the end of each month
   upon receipt of an invoice.  Consultant will be required to submit a
   monthly accounting of days worked.  Should the days worked in any
   month exceed 20, no additional fees are due.  The contract may only
   be extended by written agreement specifying new services, terms, and
   conditions as mutually agreed to by both parties.

   *Expenses:*

   All expenses incurred on behalf of the IETF/IAB or ISOC shall be
   billed to ISOC in addition to charges for services provided above.
   Such expenses shall include travel, long distance telephone, business



Malamud                Expires February 23, 2005               [Page 53]

Internet-Draft      Administrative Support Analysis          August 2004


   meals, and other customary expenses as appropriate.  Such expenses
   should be authorized by ISOC, after consultation with the IETF and
   the IAB Chairs, and in advance of the expenditure.

   *Invoicing:*

   Consultant shall submit invoices at the end of each month (pro-rated
   for June and December).  The Internet Society will make best efforts
   to make payment within one week of receipt.  If consultant worked
   less than 20 days, then ISOC may reduce the monthly fee due by 1/20th
   of such fee for each day less than 20.  Invoices may be submitted
   electronically or by mail.  The invoices should be addressed to the
   Internet Society's Finance Director, Lynn DuVal at the Reston office
   (1775 Wiehle Avenue, Suite 102, Reston, VA 20190) or by e-mail at
   duval@isoc.org.

   *Termination:*

   Either party may terminate this Contract by providing ten (10) days
   prior written notice sent by e-mail to the addresses noted below.

   In addition, should the subject matter addressed in this Contract
   become, in whole or in part, the subject matter of any filed or
   threatened litigation then either party may terminate this Contract
   by providing five (5) days prior written notice sent as per the above
   paragraph.

   The days of prior written notice above shall be measured from the
   date sent.

   The Internet Society will be responsible for all fees properly
   incurred under this Contract prior to the effective date of
   termination.

   If such a termination should occur other than at a month-end, then
   payment for services shall be paid pro rata, up to 100% of the
   monthly rate, at the rate of 1/20th of the monthly services fee per
   day worked to termination

   *Miscellaneous:*

   ISOC does not wish for itself or others to receive any confidential,
   proprietary information of any other party without proper permission.
   Consequently, Consultant agrees not to use or divulge, in his efforts
   relating to this contract, any information in any form, tangible or
   intangible, that is the confidential information of any third party,
   whether IETF/IAB, any contractor or partner of IETF/IAB, or any other
   party, to ISOC or any other party without the express written



Malamud                Expires February 23, 2005               [Page 54]

Internet-Draft      Administrative Support Analysis          August 2004


   permission of the party or parties who own or control such
   confidential material and without first disclosing such written
   permission to ISOC.

   Consultant agrees that any tangible or intangible work product that
   results from Consultant's efforts under this Contract (whether by
   Consultant or a contractor to Consultant) shall be the exclusive
   property of ISOC or the IETF/IAB, as appropriate, and this includes,
   without limitation, any invention, product, business process, code or
   other device or discovery that might now or hereafter be entitled to
   protection, registration or ownership under intellectual property
   rights regimens such as, but not only, trade secret, patent,
   copyright, and trademark.

   ISOC may disclose the terms of this Contract to the IETF/IAB or any
   other party having an interest in the subject matter hereof that ISOC
   deems reasonable.

   *Warranties and Indemnities:*

   This written agreement constitutes the full agreement between the
   parties.  No warranties or indemnities are explicitly included or
   implied.

   *Amendments:*

   Amendments to this agreement must be in writing and executed by both
   parties.

   +---------------------------------+---------------------------------+
   |    Executed on behalf of The    |    Executed on behalf of the    |
   |         Internet Society        |            Consultant           |
   +---------------------------------+---------------------------------+
   |          Lynn St. Amour         |           Carl Malamud          |
   |                                 |                                 |
   |         President & CEO         |                                 |
   |                                 |                                 |
   |        st.amour@isoc.org        |          carl@media.org         |
   |                                 |                                 |
   |              Date:              |              Date:              |
   +---------------------------------+---------------------------------+

   *Appendix I: Statement of Work*

   The IETF/IAB is considering an Administrative restructuring and has
   asked ISOC to support their efforts.  The contract to which this is
   attached is in furtherance of this endeavor.




Malamud                Expires February 23, 2005               [Page 55]

Internet-Draft      Administrative Support Analysis          August 2004


   Consultant shall become familiar with RFC 3716 as the basis for these
   efforts and shall use such RFC as a reference point in these efforts
   except to the extent that this Contract or any guidance supplied to
   Consultant by IETF/IAB or ISOC under this contract supercedes such
   RFC.

   The types of activities Consultant shall undertake are:
   o  Assist in researching, recommending and ultimately drafting the
      proposed structure/bylaws for the IETF administrative entity;
   o  Revising proposed structure and/or bylaws based on the public
      review, including reviews by counsel;
   o  Negotiate appropriate contract(s) for RFC Editor and/or other
      contractors as a model for eventual use by the IETF administrative
      entity;
   o  Conduct appropriate liaison with the RFC Editor, IANA and
      Secretariat to determine the requirements for inter-organizational
      document flow matched to overall IETF/IAB process needs.
   o  Others as reasonably directed by ISOC, IETF and or IAB

   Deliverables hereunder shall include:
   o  Data Flow: a comprehensive set of requirements for implementing
      appropriate tracking of IETF/IAB documents and reporting of status
      across support organizations.
   o  Negotiated contracts, per the above, that are acceptable to all
      concerned parties and are ready for execution.
   o  Administrative restructuring: documentation and support, as
      appropriate, to the continued evolution of the restructuring
      effort, which shall be periodically reviewed by the IAB, IESG and
      other appropriate parts of the IETF community of interest.






















Malamud                Expires February 23, 2005               [Page 56]

Internet-Draft      Administrative Support Analysis          August 2004


Appendix B.  IETF Financial Information

B.1  Consolidated 3-Year Historical Income Statement

   (US$)

   +------------------+------------+-----------+-----------+-----------+
   |                  |   2001 [1] |  2002 [2] |  2003 [3] |  2004 [4] |
   +------------------+------------+-----------+-----------+-----------+
   | REVENUE          |            |           |           |           |
   |                  |            |           |           |           |
   | CNRI/Foretec     |  2,699,239 | 2,350,666 | 2,060,747 | 1,728,125 |
   | Meeting Revenue  |            |           |           |           |
   |                  |            |           |           |           |
   | Less Bank Fees   |     81,365 |    70,309 |    62,826 |    51,844 |
   |                  |            |           |           |           |
   | Net Meeting      |  2,617,874 | 2,280,357 | 1,997,921 | 1,676,281 |
   | Revenue          |            |           |           |           |
   |                  |            |           |           |           |
   | Contribution By  |    535,535 |   550,881 |   614,691 |   663,570 |
   | The Internet     |            |           |           |           |
   | Society [5]      |            |           |           |           |
   |                  |            |           |           |           |
   | Provision of the |         -- |        -- |        -- |        -- |
   | IANA function by |            |           |           |           |
   | ICANN [6]        |            |           |           |           |
   |                  |            |           |           |           |
   | Other            |         -- |        -- |        -- |   150,000 |
   | Contributions    |            |           |           |           |
   |                  |            |           |           |           |
   | TOTAL FUNDS      |  3,153,409 | 2,831,238 | 2,612,612 | 2,489,851 |
   |                  |            |           |           |           |
   |                  |            |           |           |           |
   | EXPENSE          |            |           |           |           |
   |                  |            |           |           |           |
   | ISOC             |            |           |           |           |
   | Expenditures     |            |           |           |           |
   |                  |            |           |           |           |
   | RFC Editor       |    428,300 |   462,368 |   516,460 |   574,570 |
   |                  |            |           |           |           |
   | IETF Chair       |     73,748 |    52,137 |    51,460 |    48,500 |
   | Discretionary    |            |           |           |           |
   | Fund             |            |           |           |           |
   |                  |            |           |           |           |
   | IAB Support      |     13,287 |    14,446 |    37,270 |    24,500 |
   |                  |            |           |           |           |
   | Insurance        |     20,000 |    21,930 |    13,685 |    16,000 |
   |                  |            |           |           |           |



Malamud                Expires February 23, 2005               [Page 57]

Internet-Draft      Administrative Support Analysis          August 2004


   | Total ISOC       |    535,535 |   550,881 |   614,691 |   663,570 |
   | Expenditures     |            |           |           |           |
   |                  |            |           |           |           |
   |                  |            |           |           |           |
   | CNRI/Foretec     |            |           |           |           |
   | Expenditures     |            |           |           |           |
   |                  |            |           |           |           |
   | Secretariat      |    504,584 |   625,124 |   532,936 |   478,000 |
   | Labor            |            |           |           |           |
   |                  |            |           |           |           |
   | IETF Meeting     |            |           |           |           |
   | Costs            |            |           |           |           |
   |                  |            |           |           |           |
   | Food & Beverage  |    862,500 |   705,610 |   513,081 |   487,500 |
   |                  |            |           |           |           |
   | Audio/Visual     |    127,337 |    83,239 |    96,902 |    60,000 |
   |                  |            |           |           |           |
   | Room Rental      |    190,265 |   172,907 |   125,187 |   170,000 |
   |                  |            |           |           |           |
   | Terminal Room    |         -- |        -- |    66,294 |    25,000 |
   |                  |            |           |           |           |
   | Other Meeting    |      1,925 |     8,340 |    13,367 |     6,000 |
   | Costs            |            |           |           |           |
   |                  |            |           |           |           |
   | Total IETF       |  1,182,027 |   970,096 |   814,831 |   748,500 |
   | Meeting Costs    |            |           |           |           |
   |                  |            |           |           |           |
   |                  |            |           |           |           |
   | Non-Meeting      |            |           |           |           |
   | Costs            |            |           |           |           |
   |                  |            |           |           |           |
   | Travel           |     39,122 |    53,838 |    78,947 |    75,000 |
   |                  |            |           |           |           |
   | Materials        |      7,318 |    11,724 |     9,706 |    10,700 |
   |                  |            |           |           |           |
   | Printing &       |     59,431 |    31,459 |    14,266 |    12,000 |
   | Publication      |            |           |           |           |
   |                  |            |           |           |           |
   | Professional     |     24,581 |    61,105 |    12,288 |     9,000 |
   | Services         |            |           |           |           |
   |                  |            |           |           |           |
   | Telecommunicatio |     54,400 |    82,210 |    32,582 |    42,000 |
   | ns               |            |           |           |           |
   |                  |            |           |           |           |
   | Misc.            |     12,003 |       577 |        -- |     4,000 |
   |                  |            |           |           |           |
   | Equipment Rental |      4,668 |       736 |     1,630 |     2,500 |
   |                  |            |           |           |           |



Malamud                Expires February 23, 2005               [Page 58]

Internet-Draft      Administrative Support Analysis          August 2004


   | Total            |    201,523 |   241,650 |   149,419 |   155,200 |
   | Non-Meeting      |            |           |           |           |
   | Costs            |            |           |           |           |
   |                  |            |           |           |           |
   |                  |            |           |           |           |
   | Total            |  1,888,134 | 1,836,870 | 1,497,186 | 1,381,700 |
   | CNRI/Foretec     |            |           |           |           |
   | "Direct"         |            |           |           |           |
   | Expenses         |            |           |           |           |
   |                  |            |           |           |           |
   |                  |            |           |           |           |
   | CNRI/Foretec     |    604,990 |   608,805 |   641,939 |   504,560 |
   | Overhead Charge  |            |           |           |           |
   |                  |            |           |           |           |
   | CNRI/Foretec     |     30,000 |        -- |        -- |        -- |
   | "Performance     |            |           |           |           |
   | Bonus"           |            |           |           |           |
   |                  |            |           |           |           |
   |                  |            |           |           |           |
   | Total            |  2,124,523 | 2,445,675 | 2,139,125 | 1,886,260 |
   | CNRI/Foretec     |            |           |           |           |
   | Expenses         |            |           |           |           |
   |                  |            |           |           |           |
   |                  |            |           |           |           |
   | TOTAL EXPENSES   |  2,660,058 | 2,996,556 | 2,753,816 | 2,549,830 |
   | (ISOC and CNRI)  |            |           |           |           |
   |                  |            |           |           |           |
   |                  |            |           |           |           |
   | SURPLUS/DEFICIT  |     94,750 | (165,318) | (141,204) |  (59,979) |
   +------------------+------------+-----------+-----------+-----------+

   Notes:
   [1] Actual results based on unaudited reports.  Source: [IETF-2001]
   [2] Actual results based on unaudited reports.  Source: [IETF-2002]
   [3] Actual results based on unaudited reports.  Source: [IETF-2003]
   [4] Budgeted.  Source: [IETF-2004]
   [5] ISOC manages expenditures directly.  The revenue line here
      represents funds allocated by the ISOC Board of Trustees for the
      purpose of IETF support.  The figures in this line equal their
      corresponding cells for Total ISOC Expenditures.
   [6] ICANN does not report expenses broken down by functional area,
      nor are the direct and indirect costs associated with the IETF
      parameter registries available.  We thus value this contribution
      as "priceless" for purposes of this analysis.

B.2  Internet Society 2004 Budget Summary

   The Internet Society 2004 Budget was approved at a Special



Malamud                Expires February 23, 2005               [Page 59]

Internet-Draft      Administrative Support Analysis          August 2004


   Teleconference Meeting of the Internet Society Board of
   Trustees.[ISOC-2004] All figures are in U.S.  dollars.

   +------------------+------------+-----------+-----------+-----------+
   |                  |  Standards | Education |    Public |     Total |
   |                  |     Pillar |    Pillar |    Policy |           |
   |                  |            |           |    Pillar |           |
   +------------------+------------+-----------+-----------+-----------+
   | REVENUE          |            |           |           |           |
   |                  |            |           |           |           |
   | Organizational   |  1,050,000 |   242,000 |   200,000 | 1,492,000 |
   | and Platinum     |            |           |           |           |
   | Membership       |            |           |           |           |
   |                  |            |           |           |           |
   | Individual       |            |           |    52,500 |    52,500 |
   | Membership       |            |           |           |           |
   |                  |            |           |           |           |
   | Conferences      |            |   145,000 |           |   145,000 |
   | (INET, NDSS)     |            |           |           |           |
   |                  |            |           |           |           |
   | .org Program     |    900,000 |   450,000 |   550,000 | 1,900,000 |
   | Revenue          |            |           |           |           |
   |                  |            |           |           |           |
   | Other            |    155,000 |           |           |   155,000 |
   | (Contributions   |            |           |           |           |
   | and Security     |            |           |           |           |
   | Expert           |            |           |           |           |
   | Initiative       |            |           |           |           |
   |                  |            |           |           |           |
   | TOTAL REVENUE    |  2,105,000 |   837,000 |   802,500 | 3,744,500 |
   |                  |            |           |           |           |
   |                  |            |           |           |           |
   | EXPENSE          |            |           |           |           |
   |                  |            |           |           |           |
   | ISOC Salaries    |    371,337 |   364,623 |   458,128 | 1,194,088 |
   | and Related      |            |           |           |           |
   | Costs            |            |           |           |           |
   |                  |            |           |           |           |
   | IETF Staff       |     10,000 |           |           |    10,000 |
   | Travel           |            |           |           |           |
   |                  |            |           |           |           |
   | RFC Editor       |    574,570 |           |           |   574,570 |
   |                  |            |           |           |           |
   | IETF and IAB     |     89,000 |           |           |    89,000 |
   | Support and      |            |           |           |           |
   | Insurance        |            |           |           |           |
   |                  |            |           |           |           |
   | IETF             |    709,000 |           |           |   709,000 |



Malamud                Expires February 23, 2005               [Page 60]

Internet-Draft      Administrative Support Analysis          August 2004


   | Restructuring    |            |           |           |           |
   | Project          |            |           |           |           |
   |                  |            |           |           |           |
   | Conference       |            |   100,000 |           |   100,000 |
   | Expense          |            |           |           |           |
   |                  |            |           |           |           |
   | Professional     |     12,500 |    20,000 |     4,000 |    36,500 |
   | Services,        |            |           |           |           |
   | Travel, Misc.    |            |           |           |           |
   |                  |            |           |           |           |
   | External Costs:  |     40,000 |    89,400 |    70,000 |   199,400 |
   | .org             |            |           |           |           |
   |                  |            |           |           |           |
   | External Costs:  |     70,000 |    42,181 |           |   112,181 |
   | SEINIT & Sida    |            |           |           |           |
   |                  |            |           |           |           |
   |                  |            |           |           |           |
   | TOTAL DIRECT     |  1,876,407 |   616,204 |   532,128 | 3,024,739 |
   | EXPENSE          |            |           |           |           |
   |                  |            |           |           |           |
   | G&A/GOVERNANCE   |    192,026 |   188,555 |   236,908 |   617,489 |
   |                  |            |           |           |           |
   | TOTAL EXPENSE    |  2,068,433 |   804,759 |   769,036 | 3,642,228 |
   |                  |            |           |           |           |
   |                  |            |           |           |           |
   | SURPLUS          |     36,567 |    32,241 |    33,464 |   102,272 |
   +------------------+------------+-----------+-----------+-----------+
























Malamud                Expires February 23, 2005               [Page 61]

Internet-Draft      Administrative Support Analysis          August 2004


Appendix C.  10-Year Meeting Attendance Summary

   +------------+------------+-------------+-------------+-------------+
   | IETF       | DATE       | Location    | Host        |   Attendees |
   +------------+------------+-------------+-------------+-------------+
   | 60th IETF  | 01/08/2004 | San Diego,  | --          |        1511 |
   | [9]        |            | CA, USA     |             |             |
   |            |            |             |             |             |
   | 59th IETF  | 29/02/2004 | Seoul,      | --          |        1390 |
   | [10]       |            | South Korea |             |             |
   |            |            |             |             |             |
   | 58th IETF  | 09/11/2003 | Minneapolis | --          |        1233 |
   | [11]       |            | , MN, USA   |             |             |
   |            |            |             |             |             |
   | 57th IETF  | 13/07/2003 | Vienna,     | --          |        1304 |
   | [12]       |            | Austria     |             |             |
   |            |            |             |             |             |
   | 56th IETF  | 16/03/2003 | San         | --          |        1679 |
   | [13]       |            | Francisco,  |             |             |
   |            |            | California, |             |             |
   |            |            | USA         |             |             |
   |            |            |             |             |             |
   | 55th IETF  | 17/11/2002 | Atlanta,    | Nokia       |        1570 |
   |            |            | Georgia,    |             |             |
   |            |            | USA         |             |             |
   |            |            |             |             |             |
   | 54th IETF  | 14/07/2002 | Yokohama,   | Fujitsu;    |        1885 |
   |            |            | Japan       | The WIDE    |             |
   |            |            |             | Project     |             |
   |            |            |             |             |             |
   | 53rd IETF  | 17/03/2002 | Minneapolis | Cable &     |        1656 |
   |            |            | ,           | Wireless    |             |
   |            |            | Minnesota,  |             |             |
   |            |            | USA         |             |             |
   |            |            |             |             |             |
   | 52nd IETF  | 09/12/2001 | Salt Lake   | Novell      |        1691 |
   |            |            | City, Utah, |             |             |
   |            |            | USA         |             |             |
   |            |            |             |             |             |
   | 51st IETF  | 05/08/2001 | London,     | BTexact     |        2226 |
   |            |            | England     | Technologie |             |
   |            |            |             | s           |             |
   |            |            |             |             |             |
   | 50th IETF  | 18/03/2001 | Minneapolis | Lucent      |        1822 |
   |            |            | , MN, USA   | Technologie |             |
   |            |            |             | s           |             |
   |            |            |             |             |             |
   | 49th IETF  | 10/12/2000 | San Diego,  | Cisco       |        2810 |



Malamud                Expires February 23, 2005               [Page 62]

Internet-Draft      Administrative Support Analysis          August 2004


   |            |            | CA, USA     | Systems;    |             |
   |            |            |             | Qualcomm    |             |
   |            |            |             |             |             |
   | 48th IETF  | 31/07/2000 | Pittsburgh, | Marconi     |        2344 |
   |            |            | PA, USA     |             |             |
   |            |            |             |             |             |
   | 47th IETF  | 26/03/2000 | Adelaide,   | connect.com |        1431 |
   |            |            | Australia   | .au         |             |
   |            |            |             |             |             |
   | 46th IETF  | 07/11/1999 | Washington, | Nortel      |        2379 |
   |            |            | DC, USA     | Networks,   |             |
   |            |            |             | Inc         |             |
   |            |            |             |             |             |
   | 45th IETF  | 11/07/1999 | Oslo,       | Uninett     |        1710 |
   |            |            | Norway      |             |             |
   |            |            |             |             |             |
   | 44th IETF  | 14/03/1999 | Minneapolis | Ascend      |        1705 |
   |            |            | , MN, USA   | Communicati |             |
   |            |            |             | ons         |             |
   |            |            |             |             |             |
   | 43rd IETF  | 07/12/1998 | Orlando,    | Microsoft   |        2124 |
   |            |            | FL, USA     | Corporation |             |
   |            |            |             |             |             |
   | 42nd IETF  | 24/08/1998 | Chicago,    | Motorola    |        2106 |
   |            |            | IL, USA     |             |             |
   |            |            |             |             |             |
   | 41st IETF  | 30/03/1998 | Los         | --          |        1775 |
   |            |            | Angeles,    |             |             |
   |            |            | CA, USA     |             |             |
   |            |            |             |             |             |
   | 40th IETF  | 08/12/1997 | Washington, | Newbridge   |        1897 |
   |            |            | DC, USA     | Networks,   |             |
   |            |            |             | Inc         |             |
   |            |            |             |             |             |
   | 39th IETF  | 11/08/1997 | Munich,     | ISOC-German |        1308 |
   |            |            | Germany     | y Chapter   |             |
   |            |            |             |             |             |
   | 38th IETF  | 07/04/1997 | Memphis,    | Federal     |        1321 |
   |            |            | Tennessee,  | Express     |             |
   |            |            | USA         |             |             |
   |            |            |             |             |             |
   | 37th IETF  | 09/12/1996 | San Jose,   | Cisco       |        1993 |
   |            |            | California, | Systems     |             |
   |            |            | USA         |             |             |
   |            |            |             |             |             |
   | 36th IETF  | 24/06/1996 | Montreal,   | --          |        1283 |
   |            |            | Quebec,     |             |             |
   |            |            | CANADA      |             |             |



Malamud                Expires February 23, 2005               [Page 63]

Internet-Draft      Administrative Support Analysis          August 2004


   |            |            |             |             |             |
   | 35th IETF  | 04/03/1996 | Los         | --          |        1038 |
   |            |            | Angeles,    |             |             |
   |            |            | California, |             |             |
   |            |            | USA         |             |             |
   |            |            |             |             |             |
   | 34th IETF  | 04/12/1995 | Dallas,     | MCI         |        1007 |
   |            |            | Texas, USA  |             |             |
   |            |            |             |             |             |
   | 33rd IETF  | 17/07/1995 | Stockholm,  | the Royal   |         617 |
   |            |            | Sweden      | Institute   |             |
   |            |            |             | of          |             |
   |            |            |             | Technology; |             |
   |            |            |             | NORDUnet    |             |
   |            |            |             |             |             |
   | 32nd IETF  | 03/04/1995 | Danvers,    | FTP         |         983 |
   |            |            | Massachuset | Software;   |             |
   |            |            | ts, USA     | NEARnet     |             |
   |            |            |             |             |             |
   | 31st IETF  | 05/12/1994 | San Jose,   | Sun         |        1079 |
   |            |            | California, | Microsystem |             |
   |            |            | USA         | s           |             |
   |            |            |             |             |             |
   | 30th IETF  | 25/07/1994 | Toronto,    | University  |         710 |
   |            |            | Ontario,    | of Toronto  |             |
   |            |            | CANADA      |             |             |
   |            |            |             |             |             |
   | 29th IETF  | 28/03/1994 | Seattle,    | NorthWestNe |         785 |
   |            |            | Washington, | t           |             |
   |            |            | USA         |             |             |
   +------------+------------+-------------+-------------+-------------+


C.1  Analysis of Meeting-Based Expense and Revenue Drivers

   +----------------+----------------+----------------+----------------+
   | Category       |           2001 |           2002 |           2003 |
   +----------------+----------------+----------------+----------------+
   | Total          |          5,739 |          5,111 |          4,216 |
   | Attendees      |                |                |                |
   |                |                |                |                |
   | Net Meeting    |           $456 |           $446 |           $489 |
   | Revenue Per    |                |                |                |
   | Attendee       |                |                |                |
   |                |                |                |                |
   | Average Food & |           $150 |           $138 |           $122 |
   | Beverage Per   |                |                |                |
   | Attendee       |                |                |                |



Malamud                Expires February 23, 2005               [Page 64]

Internet-Draft      Administrative Support Analysis          August 2004


   |                |                |                |                |
   | Average Total  |           $206 |           $190 |           $193 |
   | Direct Meeting |                |                |                |
   | Cost Per       |                |                |                |
   | Attendee [1]   |                |                |                |
   |                |                |                |                |
   | Total          |           $370 |           $479 |           $507 |
   | CNRI/Foretec   |                |                |                |
   | Secretariat    |                |                |                |
   | Expenses       |                |                |                |
   | Divided by     |                |                |                |
   | Number of      |                |                |                |
   | Meeting        |                |                |                |
   | Attendees      |                |                |                |
   +----------------+----------------+----------------+----------------+

   Notes:
   [1] Room rental fees are typical for non-U.S.  meetings.  Average
      total direct costs will thus be influenced by the choice of
      location of meetings.































Malamud                Expires February 23, 2005               [Page 65]

Internet-Draft      Administrative Support Analysis          August 2004


Appendix D.  Sample Draft Incorporating Documents for a Hypothetical
            IETF Foundation

D.1  Sample Draft Articles of Incorporation

   This appendix contains standard, pro-forma Articles of Incorporation.
   Note well that tax lawyers often make significant alterations to
   standard Articles as they consider a 501(c)(3) application.  They are
   included here merely as a sample for illustrative purposes only.

   'Commonwealth of Virginia -- State Corporation Commission'| 'Articles
   of Incorporation -- Virginia Nonstock Corporation'| Form SCC819, 07/
   03 [14]
   ------

   The undersigned, pursuant to Chapter 10 of Title 13.1 of the Code of
   Virginia, [Virginia] state(s) as follows:
   1.  The name of the corporation is The IETF Foundation.
   2.  The corporation shall have no members.
   3.  The Trustees of the corporation shall be elected or appointed as
       specified in Article IV (Appendix D.2.5) of the Bylaws.
   4.  Name and agent:
       A.  The name of the corporation's initial registered agent is:
           XXX
       B.  The initial registered agent is a domestic or foreign stock
           or nonstock corporation, limited liability company, or
           registered limited liability partnership authorized to
           transact business in Virginia.
   5.  The initial Trustees are: XXX
   6.  The incorporators are: XXX

D.2  Sample Draft Bylaws of the IETF Foundation

   As with the Sample Draft Articles, the Sample Draft Bylaws included
   here are a pro-forma, standard version.  Substantial alteration may
   be required as legal counsel reviews the specific nature of an
   incorporation.

D.2.1  Article I: Organization

   The name of the Corporation shall be The IETF Foundation (which shall
   hereinafter be referred to as the "Foundation").

D.2.2  Article II: Purpose

   *Section 1: Purpose.* The IETF Foundation shall be operated
   exclusively for nonprofit educational, charitable, and scientific
   purposes, including, without limitation, the purposes stated in the



Malamud                Expires February 23, 2005               [Page 66]

Internet-Draft      Administrative Support Analysis          August 2004


   Foundation's Articles of Incorporation.

   *Section 2: Restrictions.* No part of the net earnings of the IETF
   Foundation shall inure to the benefit of, or be distributable to,
   private persons, except that the Foundation shall be authorized and
   empowered to pay reasonable compensation for services rendered, and
   to make payments and distributions in furtherance of the purposes set
   forth in Article II, Section 1 hereof.  Any other provision of these
   Bylaws to the contrary notwithstanding, the IETF Foundation shall not
   carry on any activities not permitted to be carried on by a
   corporation exempt from Federal Income Tax under Section 501(a) and
   Section 501(c)(3) of the Code.  These Bylaws shall not be altered or
   amended in derogation of the provisions of this Section.

D.2.3  Article III: Members

   The Foundation shall have no members and no stockholders.

D.2.4  Article IV: Offices

   The office of the Foundation shall be as determined from time to time
   by the Board of Trustees within or outside of the State of Virginia.

D.2.5  Article V: Board of Trustees

   *Section 1: Authority and Responsibilities.* The power, authority,
   property, and affairs of the Foundation shall at all times be
   exclusively exercised, controlled, and conducted by or under the
   authority of the Board of Trustees subject to any limitations set
   forth in the Articles of Incorporation and in accordance with the
   Virginia Nonstock Corporation Act as it now exists or hereafter may
   be amended.

   *Section 2: Board of Trustees Composition.* The Board of Trustees
   shall consist of seven (7) Trustees.

   *Section 3: Types.* There shall be two types of Trustees based on the
   reason for their selection: Position-Based Trustees, who are trustees
   because they hold some other office (for example IETF Chair) and
   Selected Trustees, who are not Position-Based Trustees.

   *Section 3: Terms.* The term of office of Position-Based Trustees
   shall be co-terminious with the term of the office that qualifies the
   individual to be a board member.  The term of office of Selected
   Trustees shall be three (3) years or until their successors have been
   selected and assume office.  Selected Trustees may be selected to
   serve multiple terms.




Malamud                Expires February 23, 2005               [Page 67]

Internet-Draft      Administrative Support Analysis          August 2004


   *Section 4: Selection of the Board of Trustee*
   1.  *Selection of Position-Based Trustees.* The Chairs of the IETF
       and IAB shall be the two Position-Based Trustees.  These
       individuals are selected by IETF participants using the
       procedures set forth in [RFC3777] or its successor.
   2.  *Selection of Selected Trustees.* Three Selected Trustees shall
       be selected by the IETF nominations process (as defined in
       [RFC3777] or its successor) and confirmed by the IESG.  Two
       Selected Trustees shall be selected by the internet Society using
       means of their own choosing.
   3.  *Resignation.* A Selected Trustee may resign by delivering his
       resignation in writing to the Foundation at its principal office
       or to the Secretary of the Foundation.  Such resignation shall be
       effective upon its receipt or upon such date (if any) as is
       stated in such resignation, unless otherwise determined by the
       Board.
   4.  *Removal.* A Selected Trustee selected by the IETF nominations
       process may be removed from office at any time using the
       procedures specified in [RFC3777] or its successor.  A Selected
       Trustee selected by the Internet Society my be removed by the
       Internet Society using means of their own choosing.
   5.  *Vacancies.* Any vacancy in the Board of Trustees shall be filled
       using the procedures set forth above on the composition of the
       Board of Trustees.  The Trustees shall have and may exercise all
       of their powers notwithstanding the existence of one or more
       vacancies in their number.

   *Section 5: Quorum.* A majority of the Trustees shall constitute a
   quorum for the transaction of business.  Unless otherwise stated in
   these Bylaws, decisions of the Board of Trustees shall be made by the
   concurrence of a majority of members of the Board of Trustees present
   and voting.  If at any meeting there is no quorum present, the Board
   must not transact business.

   *Section 6: Compensation and Reimbursement.* No member of the Board
   of Trustees may receive compensation for his or her services as a
   Trustee.  A Trustee shall, at their request, be reimbursed for
   actual, necessary and reasonable travel and subsistence expenses
   incurred by them in performance of their duties.

   *Section 7: Meetings.* The Board of Trustees shall meet at least
   twice annually.
   1.  *Annual Meeting.* The Board of Trustees shall hold a public
       Annual Meeting at a time and place associated with the first IETF
       meeting each year.  This Annual meeting shall be open to all IETF
       attendees except that the parts of the meeting dealing with
       personnel issues may be held in executive session.




Malamud                Expires February 23, 2005               [Page 68]

Internet-Draft      Administrative Support Analysis          August 2004


   2.  *Meeting Types, Methods, and Notice.* Meetings of the Board may
       be held from time to time at such intervals and at such places as
       may be fixed by the Board.  Meetings of the Board may be held
       only in person or via teleconference.  Notice of all regular
       meetings of the Board shall be delivered to each Trustee by
       e-mail or by postal mail and announced on the IETF-Announce list
       at least ten (10) calendar days before the meeting.  Special
       meetings of the Board may be called for any purpose at any time
       by the Chairman of the Board or by any three (3) Trustees.
       Notice of any special meeting shall state the purpose of the
       meeting.  A Trustee may waive notice of a meeting of the Board of
       Trustees by submitting a signed, written waiver of notice, either
       before or after the meeting.  A Trustee's attendance at or
       participation in a meeting waives any required notice of the
       meeting unless at the start of such meeting or promptly upon
       arrival the Trustee objects to holding the meeting or transacting
       business at the meeting, and does not thereafter vote for or
       assent to action taken at the meeting.
   3.  *Actions Taken By the Board of Trustees Without Meeting.* Any
       action required or permitted to be taken at any meeting of the
       Board of Trustees may be taken without a meeting if all Trustees
       consent in writing to such action.  Such action shall be
       evidenced by written consents approving the lack of a meeting,
       signed by each Trustee.

   *Section 8: Board Committees.* The Trustees may elect or appoint one
   or more committees (including but not limited to an Executive
   Committee) and may delegate to any such committee or committees any
   or all of their powers, provided that any committee to which the
   powers of the Trustees are delegated shall consist solely of
   Trustees.  Committees shall conduct their affairs in the same manner
   as is provided in these By Laws for the Trustees.  The members of any
   committee shall remain in office at the pleasure of the Board of
   Trustees.

   *Section 9: Trustee Member Conflict of Interest.*
   1.  As set forth in Section 9(3) below, a Trustee of the IETF
       Foundation who has a personal interest in a transaction, as
       defined below, may not participate in any discussion of that
       transaction by the Trustees of The IETF Foundation and may not
       vote to determine whether to authorize, approve, or ratify that
       transaction except as specifically described below.  For purposes
       of these Bylaws, a "personal interest" is defined as any act that
       will provide, directly or indirectly, a financial benefit or a
       disparate benefit individually to the Trustee, or to a company he
       or she is employed by, has a significant financial interest in,
       or represents in any fashion.  However, policies under
       consideration by the Foundation are likely to have an impact on



Malamud                Expires February 23, 2005               [Page 69]

Internet-Draft      Administrative Support Analysis          August 2004


       the business of every Trustee.  It is expected that most policy
       decisions will have a direct or indirect impact on the Trustee's
       company, but such a non-individualized interest does not
       constitute a "personal interest" as used in these Bylaws.  A
       "transaction" with The IETF Foundation for purposes of these
       Bylaws is a contract or consultancy in which the Trustee has a
       direct or indirect financial benefit, or a policy under
       consideration that will have a disparate and unusual impact on a
       business with which the Trustee is directly or indirectly
       associated.
   2.  The mere existence of a personal interest by a Trustee of The
       IETF Foundation in a transaction with The IETF Foundation shall
       not invalidate The IETF Foundation's ability to enter that
       transaction so long as the following conditions are met: (i) the
       material facts of the personal nature of the transaction with The
       IETF Foundation and the Trustee's interest in the transaction
       with The IETF Foundation are fully disclosed to the Board of
       Trustees of The IETF Foundation, either by the Trustee having a
       direct or indirect personal interest in the transaction with The
       IETF Foundation, or are brought to the attention of the Board by
       a third party; or (ii) the Board of Trustees of The IETF
       Foundation, by a vote of the disinterested Trustees of The IETF
       Foundation vote to authorize, approve, or ratify a transaction
       with The IETF Foundation; or (iii) the transaction with The IETF
       Foundation in which the direct or indirect personal interest of
       an The IETF Foundation Trustee was disclosed to the Board of
       Trustees of The IETF Foundation and was determined by the Board
       of Trustees of The IETF Foundation entitled to vote on the matter
       is determined by the Board of Trustees voting to be in The IETF
       Foundation's interests, notwithstanding the personal interest of
       the non-voting Trustee.
   3.  In determining whether a conflict of interest exists, the Board
       of Trustees of The IETF Foundation has the prerogative, upon
       review of all facts and circumstances, to make its own
       determination of whether a conflict of interest exists and how it
       is appropriate to proceed.  A Trustee who perceives the
       possibility of a conflict of interest for him or herself, or for
       another Board member, may raise this issue at any point prior to
       a vote on any issue.  Any Trustee who perceives a possible
       conflict of interest may present justification with respect to
       whether or not a conflict of interest exists, but the entire
       Board, with the exception of the Trustee having the potential
       conflict of interest, shall make the final determination to
       proceed in such a matter.  If the Board of Trustees finds there
       is a conflict of interest, the Trustee with the conflict may be
       excluded by the Chair of the Board from that portion of any
       meeting where a substantive discussion or decision to engage or
       not in such a transaction is made, except that he or she may



Malamud                Expires February 23, 2005               [Page 70]

Internet-Draft      Administrative Support Analysis          August 2004


       provide any information that will assist the Trustees in such a
       matter before leaving such a meeting.

   *Section 10.  Approval of Meeting Minutes.* Minutes of the Board of
   the IETF Foundation must be approved by a procedure adopted by the
   board and published on the IETF Foundation web site.

D.2.6  Article VI: Officers

   *Section 1: Number.* The officers of the IETF Foundation shall
   consist of a Chairman of the Board, a Treasurer and a Secretary, and
   such other inferior officers as the Board of Trustees may determine.

   *Section 2: Election Term of Office and Qualifications.* All officers
   shall be elected annually by the vote of a majority of the Board of
   Trustees present and voting (excluding abstentions) at the Annual
   Meeting.  The Treasurer and Secretary need not be members of the
   Board.  The Chair of the IETF nor the chair of the IAB shall be the
   Chairman of the Board of the IETF Foundation.

   *Section 3: Resignation.* An officer may resign by delivering his
   written resignation to the Foundation at its principal office or to
   the Chair or Secretary.  Such resignation shall be effective upon
   receipt or upon such date (if any) as is stated in such resignation,
   unless otherwise determined by the Board.

   *Section 4: Removal.* The Board of Trustees may remove any officer
   with or without cause by a vote of a majority of the entire number of
   Trustees then in office, at a meeting of the Board of Trustees called
   for that purpose.  An officer may be removed for cause only if notice
   of such action shall have been given to all of the Trustees prior to
   the meeting at which such action is to be taken and if the officer so
   to be removed shall have been given reasonable notice and opportunity
   to be heard by the Board of Trustees.

   *Section 5: Vacancies.* In case any elected officer position of the
   IETF Foundation becomes vacant, the majority of the Trustees in
   office, although less than a quorum, may elect an officer to fill
   such vacancy at the next meeting of the Board of Trustees, and the
   officer so elected shall hold office and serve until the next Annual
   Meeting.

   *Section 6: Chairman of the Board.* The Chairman of the Board shall,
   when present, preside at all meetings of the Board of Trustees of
   IETF Foundation.  If the Chairman is not available to preside over a
   meeting, the majority of the Trustees present shall select another
   Trustee to preside at that meeting only.




Malamud                Expires February 23, 2005               [Page 71]

Internet-Draft      Administrative Support Analysis          August 2004


   *Section 7: Treasurer.* The Treasurer shall have the custody of all
   funds, property, and securities of the IETF Foundation, subject to
   such regulations as may be imposed by the Board of Trustees.  He or
   she may be required to give bond for the faithful performance of his
   or her duties, in such sum and with such sureties as the Board of
   Trustees may require or as required by law, whichever is greater.
   When necessary or proper, he or she may endorse on behalf of the IETF
   Foundation for collection, checks, notes and other obligations, and
   shall deposit same to the credit of the IETF Foundation at such bank
   or banks or depository as the Board of Trustees may designate.  He or
   she shall make or cause to be made such payments as may be necessary
   or proper to be made on behalf of the IETF Foundation.  He or she
   shall enter or cause to be entered regularly on the books of the IETF
   Foundation to be kept by him or her for that purpose, full and
   accurate account of all monies and obligations received and paid or
   incurred by him or her for or on account of the IETF Foundation, and
   shall exhibit such books at all reasonable times to any Trustee on
   application at the offices of the IETF Foundation incident to the
   Office of Treasurer, subject to the control of the Board of Trustees.
   Certain duties of the Treasurer as may be specified by the Board of
   Trustees may be delegated by the Treasurer.

   *Section 8: Secretary.* The Secretary shall have charge of such
   books, records, documents, and papers as the Board of Trustees may
   determine, and shall have custody of the corporate seal.  The
   Secretary shall keep, or cause to be kept the minutes of all meetings
   of the Board of Trustees.  The Secretary may sign, with the Chairman,
   in the name and on behalf of the IETF Foundation, any contracts or
   agreements, and he or she may affix the corporate seal of the IETF
   Foundation.  He or she, in general, performs all the duties incident
   to the Office of Secretary, subject to the supervision and control of
   the Board of Trustees, and shall do and perform such other duties as
   may be assigned to him or her by the Board of Trustees or the
   Chairman of the Board of Trustees.  Certain duties of the Secretary
   as may be specified by the Board of Trustees may be delegated by the
   Secretary.

   *Section 9: Other Powers and Duties.* Each officer shall have in
   addition to the duties and powers specifically set forth in these By
   Laws, such duties and powers as are customarily incident to his
   office, and such duties and powers as the Trustees may from time to
   time designate.

D.2.7  Article VII: Amendments

   *Section 1: By Laws.* These By Laws may be amended by an affirmative
   vote of a majority of the Trustees then in office (excluding
   abstentions) at a regular meeting of the board or a meeting of the



Malamud                Expires February 23, 2005               [Page 72]

Internet-Draft      Administrative Support Analysis          August 2004


   board called for that purpose as long as the proposed changes are
   made available to all trustees and posted to the IETF Announce list
   at least 30 days before any such meeting.

   *Section 2: Articles of Incorporation.* The Articles of Incorporation
   of the IETF Foundation may amended by an affirmative vote of
   two-thirds vote of the Board of Trustees then in office at a regular
   meeting of the board or a meeting of the board called for that
   purpose as long as the proposed changes are made available to all
   trustees and posted to the IETF Announce list at least 30 days before
   any such meeting.

D.2.8  Article VIII: Dissolution

   Upon the dissolution of the IETF Foundation, the IETF Foundation
   shall, after paying or making provisions for the payment of all of
   the liabilities of the Foundation, dispose of all of the assets of
   the IETF Foundation exclusively for the exempt purposes of the IETF
   Foundation in such manner or to such organization or organizations
   operated exclusively for social welfare or charitable purposes.  Any
   such assets not so disposed of shall be disposed of by a court of
   competent jurisdiction of the county in which the principal office of
   the organization is then located, exclusively for such purposes.  In
   the event of a sale or dissolution of the corporation, the surplus
   funds of the corporation shall not inure to the benefit of, or be
   distributable to, its Trustees, officers, or other private persons.

D.2.9  Article IX: Miscellaneous Provisions

   *Section 1: Fiscal Year.* The fiscal year of the IETF Foundation
   shall be from January 1 to December 31 of each year.

   *Section 2: Execution of Instruments.* All checks, deeds, leases,
   transfers, contracts, bonds, notes and other obligations authorized
   to be executed by an officer of the Foundation in its behalf shall be
   signed by the Chairman of the Board or the Treasurer, or as the
   Trustees otherwise determine.  A certificate by the Secretary as to
   any action taken by the Board of Trustees shall as to all persons who
   rely thereon in good faith be conclusive evidence of such action.

   *Section 3: Severability.* Any determination that any provision of
   these By-Laws is for any reason inapplicable, illegal or ineffective
   shall not affect or invalidate any other provision of these By-Laws.

   *Section 4: Articles of Incorporation.* All references in these By
   Laws to the Articles of Incorporation shall be deemed to refer to the
   Articles of Incorporation of the IETF Foundation, as amended and in
   effect from time to time.



Malamud                Expires February 23, 2005               [Page 73]

Internet-Draft      Administrative Support Analysis          August 2004


   *Section 5: Gender.* Whenever used herein, the singular number shall
   include the plural, the plural shall include the singular, and the
   use of any gender shall include all genders.

   *Section 6: Successor Provisions.* All references herein: (1) to the
   Internal Revenue Code shall be deemed to refer to the Internal
   Revenue Code of 1986, as now in force or hereafter amended; (2) to
   the Code of the State of Virginia, or any Chapter thereof, shall be
   deemed to refer to such Code or Chapter as now in force or hereafter
   amended; (3) the particular sections of the Internal Revenue Code or
   such Code shall be deemed to refer to similar or successor provisions
   hereafter adopted; and (4) to the Request for Comment Series shall be
   deemed to refer to the Request for Comment Series as they are now in
   force or hereafter amended.





































Malamud                Expires February 23, 2005               [Page 74]

Internet-Draft      Administrative Support Analysis          August 2004


Appendix E.  Sample Draft Call for Applications -- IETF Administrative
            Director

   The IETF is seeking a highly capable individual to serve as
   Administrative Director.  You will report to the IETF Chair and be
   accountable to IETF Community.  This is a highly visible and very
   demanding job.  You will be expected to:
   o  Serve as the day-to-day chief operating officer of the IETF,
      managing a number of contractors and working with a number of
      volunteers.
   o  Provide primary support for budgeting and financial reporting
      processes.
   o  Serve as the primary staff resource for the governing body of the
      administrative entity for the IETF.
   o  Work with your contractors and members of the IETF community to
      provide adequate support and planning for 3 IETF meetings
      annually, and for frequent meetings and teleconferences of the
      IAB, IESG, and other bodies that support the IETF.
   o  Work with our liaison organizations, such as the RFC Editor and
      the IANA.
   o  Coordinate the standards-making support process, in particular the
      periodic meetings of the IESG.

   The following characteristics are necessary for this job:
   o  This job is public service.  You should be able to work
      successfully with large numbers of people.  This requires a high
      clock rate, a large stack, and the ability to listen carefully.
   o  This is an operations job.  IETF meetings are large and complex,
      and the day-to-day activities of the standards-making process is
      demanding.  You should be adept at getting real results and
      helping large groups work together towards common goals and
      deadlines.
   o  This job requires a financially astute individual.  The IETF is a
      $2-$3 million/year operation.  IETF funds are tight and we expect
      you to take leadership in establishing our budgetary procedures,
      our procurement standards, and understanding our revenue sources.

   In-depth familiarity with the IETF prior to assuming this position is
   not required, but you must be able to quickly get up to speed and
   learn the unique culture and requirements of the organization.
   Likewise, long-term technical experience is not required, but you
   must be a quick learner and adept at using the Internet effectively.

   You may work out of a home office as a telecommuter, or use the
   Internet Society facilities in Virginia.  In either case, you should
   be prepared to travel to Virginia, IETF meetings, and the locations
   where the IETF has contractors.




Malamud                Expires February 23, 2005               [Page 75]

Internet-Draft      Administrative Support Analysis          August 2004


   Applicants should forward a resume, references, and any other
   relevant materials, with a cover letter explaining why they feel they
   are the right person for this position to:
      URL

   Applications are due no later than XXX, however the IETF
   Administrative Entity reserves the right to make a decision prior to
   this date or to extend this date in its sole discretion.
   Applications will be reviewed by an evaluation committee consisting
   of members of the IAB, IESG, and the community, and a decision shall
   be made by the Chairs of the IETF and the IAB with the advice and
   consent of the IESG and the IAB.

   The list of applicants will not be posted publicly, but will be
   reviewed in confidence by members of the evaluation committee, the
   IAB, and the IESG.



































Malamud                Expires February 23, 2005               [Page 76]

Internet-Draft      Administrative Support Analysis          August 2004


Appendix F.  Sample Draft Request for Proposals

F.1  Introduction

   The IETF Administrative Entity is soliciting proposals for the
   provision of five requirements, as detailed in this Request for
   Proposals ("Proposals").  Proposals from any individual person or
   persons or commercial or non-commercial vendor ("Vendor") are
   welcome.

   Proposals must be received in written electronic form no later than
   [date].  Extensions may be granted solely in the discretion of the
   IETF Administrative Entity.  Each Proposal, together with all
   supporting documentation, should be delivered to the following
   address:

   [URI/ADDRESS]

   Any inquiries regarding this Request must be submitted in written
   electronic form to the address listed above.  Other than such
   inquiries, vendors are prohibited from contacting any person or
   institution involved in the selection process concerning this
   Request.

   Each Proposal must specifically address each of the selection
   criteria listed below in a format corresponding to this Request.
   Each Proposal should also be accompanied by any technical or product
   literature that the Vendor wishes the IETF Administrative Entity to
   consider.  If additional information is required by the IETF
   Administrative Entity to make a determination, such information may
   be requested, and shall be submitted in writing in the manner set
   forth above.  Information other than the written Proposal and any
   information submitted in response to a request by the IETF
   Administrative Entity will not be considered by the IETF
   Administrative Entity.

   The IETF Administrative Entity reserves the right to cancel this
   Request, in whole or in part, at any time.  The IETF Administrative
   Entity may reject any or all Proposals received in response to this
   Request in its sole discretion.  The IETF Administrative Entity makes
   no guarantee or commitment to purchase, license or procure any goods
   or services resulting from this Request.

   Any Proposal which is selected by the IETF Administrative Entity
   shall be subject to execution of a binding agreement between the IETF
   Administrative Entity and the Vendor, which agreement shall be
   prepared by the IETF Administrative Entity and shall reflect the
   requirements outlined below and any additional provisions that are



Malamud                Expires February 23, 2005               [Page 77]

Internet-Draft      Administrative Support Analysis          August 2004


   agreed upon in discussions between the IETF Administrative Entity and
   the Vendor.  Selection may be conditioned upon acceptance of specific
   contractual terms and conditions, which may be provided to the Vendor
   during the selection process.

   Each Vendor is responsible for its own costs and expenses involved in
   preparing and submitting its Proposal and any supplemental
   information requested by the IETF Administrative Entity.  The IETF
   Administrative Entity shall not reimburse any such costs or expenses.

   All Proposals submitted in accordance with this Request will be
   reviewed by a panel of experts drawn from the IETF community.  A list
   of reviewers will be made available.  The IETF Administrative Entity
   will notify Vendors of their selection following receipt and
   consideration of all Proposals.  The IETF Administrative Entity will
   attempt to make its selection(s) by [date], but shall have full
   discretion to make a decision earlier or later than this date.

F.2  General Provisions

   The following provisions apply to all bidders:
   1.  A response may be submitted for one or more of the 5 listed
       support requirements.  If response addresses more than one of the
       listed support requirements, the proposal should be written to
       clearly separate costs by area.  The IETF Administrative Entity
       reserves the right to accept only a partial proposal.
   2.  Key Person Principle: Each requirement requires the designation
       of one individual as the "Key Person" in your response.  That
       person will be the individual accountable to the IETF.  The IETF
       Administrative Entity will require a binding key personnel clause
       in the contract.  Any change in the Key Person will require prior
       approval.  The IETF Administrative Entity will also require a
       written process that describes procedures for backing up the key
       person when that person is not available.  The IETF
       Administrative Entity will also require that the bidder obtain
       and maintain key person insurance for dealing with the
       possibility that the designated key person becomes unavailable.
   3.  The IETF Administrative Entity encourages zero-cost or zero-cost
       plus materials bids, but will insist on a binding agreement.
   4.  The IETF Administrative Entity encourages bids from individuals
       as well as public and private institutions as long as the above
       conditions are met.  You should submit a detailed work history of
       each individual, personal references, and a detailed description
       of any sub-contractual arrangements you have put in place to
       assist you.
   5.  Appropriate insurance and other mechanisms to minimize the
       liability of the IETF Administrative Entity should be discussed
       in your proposal.



Malamud                Expires February 23, 2005               [Page 78]

Internet-Draft      Administrative Support Analysis          August 2004


F.3  Requirement 1: Meetings

   We are looking for creative proposals from experienced professionals
   to organize and support the meetings of the IETF.

   You will work with the Administrative Director of the IETF and the
   IETF leadership to organize the three annual meetings of the IETF.
   Based on current practice, you should expect 1-2 of those meetings to
   be in the United States and 1-2 of those meetings to be in other
   countries, though this may change based on the requirements of the
   IETF.  We expect approximately 1500 attendees per meeting, though in
   the past this number has approached 3,000 based on the location of
   the meeting and the state of the economy.

   You should have very strong experience in meeting planning,
   particularly working meetings with large numbers of participants.
   You should be intimately familiar with the details of booking
   appropriate venues, working with hotel and conference center staff,
   and providing clear and concise communications with meeting
   attendees.

   Your proposal should detail the mechanisms you would use to provide a
   simple registration and payment procedure for attendees.  You will be
   able to draw on webmaster and sysadmin support for the IETF, for
   example, if you would like to provide a secure payment mechanism on
   the IETF web site.  Your proposal should also detail how you will
   provide additional resources on-site (e.g., staffing a registration
   desk and other requirements that require additional people).

   As part of this function, you will work with Local Hosts (when
   available), who provide a sophisticated network infrastructure to
   support the meeting, as well as a team of volunteers who provide
   additional terminal room support, real-time audio and video streaming
   from the meeting and other functions.

F.4  Requirement 2: Systems and Systems Administration

   This requirement consists of two functions.  You may bid on one or
   both of these functions, which include:
   1.  Provision of a core network infrastructure.
   2.  Systems Administration.

F.4.1  Core Network Infrastructure

   [Ed.  This section will contain service level specifications.  E.g.,
   core bandwidth requirements, CPU capacity, disk space, and other
   variables.  It will also contain core specifications, such as
   routing, DNS, and other services.]



Malamud                Expires February 23, 2005               [Page 79]

Internet-Draft      Administrative Support Analysis          August 2004


F.4.2  Systems Administration Services

   [Ed.  This section will contain the description for the Systems
   Administration function, including such tasks as keeping key software
   subsystems such as Apache installed and up-to-date and support for
   users.]

F.5  Requirement 3: Postmaster of the IETF Administrative Entity

   The Postmaster of the IETF Administrative Entity is responsible for
   the functioning and archiving of numerous mailing lists maintained by
   the IETF and for archiving specific IETF-related mailing lists
   maintained by others.  Note that the archives of most IETF mailing
   lists are public and the bidder must describe how such archives will
   be accessed by the public.

   The core mailing is described in [RFC3005], and a policy with regards
   to posting rights may be found in [RFC3683].  You will find
   additional information on IETF mailing lists at:
      <http://www.ietf.org/maillist.html>

   In addition, the IETF maintains several dozen members-only lists in
   support of bodies such as the IAB, the IESG, and certain IRTF task
   forces (see [RFC2014], [RFC2850], and [RFC3710] for more details on
   these bodies).  IETF administrators and chairs of various groups
   typically will form ad hoc lists which they administer for various
   tasks.

   Familiarity and expertise in administering high-volume lists and in
   maintaining large numbers of archived lists is necessary.  The
   ability to provide administrative facilities that allow the IETF to
   delegate authority for moderation and creation of lists is also
   necessary.  Finally, you should be experienced in the very latest
   spam fighting technologies.

   You may propose to provide service in one of two ways:
   o  Move the IETF mail handling onto an existing well-provisioned
      infrastructure that you are responsible for.
   o  Provide mail services on machines that are maintained by the IETF.

   Your bid should clearly explain what tools you will use, the types of
   interfaces you will provide to list maintainers and participants, and
   you would handle issues such as spam.  You should also be very clear
   in your proposal about your understanding of the role and duties of
   the postmaster.






Malamud                Expires February 23, 2005               [Page 80]

Internet-Draft      Administrative Support Analysis          August 2004


F.6  Requirement 4: Clerk of the IETF Administrative Entity

   This requirement is for general high-level administrative support for
   the day-to-day functioning of the IETF.  A specialized subfunction in
   the Clerk's office is the processing of the Internet-Draft submission
   queue.  Such documents must conform to requirements for
   Internet-Drafts as defined by the IETF.

   In addition to processing the Internet-Draft queue, you will work
   with the Administrative Director of the IETF to help make the
   organization function smoothly on a day-to-day basis.

   [Ed.  More detail to be filled in here by a transition team.]

F.7  Requirement 5: Webmaster of the IETF Administrative Entity

   This task has the responsibility for the look and feel of the IETF
   network presence, particularly the web site.  A series of support
   contracts will be available to help support this function.

   In addition, this task has responsibility to provide overall support,
   in cooperation with the sysadmin and other contractors, to a variety
   of working groups, directorates, and other activities that require a
   workspace.

   Your proposal must demonstrate that you are experienced at producing
   highly standards-conformant and functional network presences and
   supporting a large and diverse community of users.  This is a highly
   hands-on task.

F.8  Selection Criteria and Evaluation Process

   All proposals will be evaluated using a process that consists of the
   following steps:
   1.  An evaluation committee will be formed by the IETF and IAB
       Chairs, and will include the Administrative Director of the IETF
       Administrative Entity.
   2.  The evaluation committee will perform an initial evaluation of
       submitted responses.
   3.  A dialogue will be started with selected responses.
   4.  The IETF will decide on the initial best candidate.
   5.  The A further dialogue will ensue with that candidate.
   6.  A contract may be signed or the discussion may continue with
       other candidates.

   The IETF Administrative Entity will consider price, experience,
   technical smarts, and a variety of other factors.  Note well that the
   IETF Administrative Entity will not decide on price alone.  Overall



Malamud                Expires February 23, 2005               [Page 81]

Internet-Draft      Administrative Support Analysis          August 2004


   benefit to the IETF community will be the prime consideration.


















































Malamud                Expires February 23, 2005               [Page 82]

Internet-Draft      Administrative Support Analysis          August 2004


Index

F
   functions  6, 6, 10, 11, 13, 16, 17

M
   mechanisms  33, 33, 33, 33, 33, 33, 33

O
   opinions  16, 23
   options  1, 7, 9, 22, 22, 24, 27, 37

P
   pillars  6, 6, 6

R
   recommendations  8, 20, 21, 21, 27, 28, 36

S
   strategies  22, 22, 22































Malamud                Expires February 23, 2005               [Page 83]

Internet-Draft      Administrative Support Analysis          August 2004


Intellectual Property Statement

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   ietf-ipr@ietf.org.


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.


Copyright Statement

   Copyright (C) The Internet Society (2004).  This document is subject
   to the rights, licenses and restrictions contained in BCP 78, and
   except as set forth therein, the authors retain all their rights.


Acknowledgment

   Funding for the RFC Editor function is currently provided by the
   Internet Society.




Malamud                Expires February 23, 2005               [Page 84]




--=_zak.ecotroph.net-2889-1093478127-0001-2
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

--=_zak.ecotroph.net-2889-1093478127-0001-2--



From ietf-bounces@ietf.org  Thu Aug 26 17:24:24 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13947;
	Thu, 26 Aug 2004 17:24:24 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C0RkP-0008Q5-RI; Thu, 26 Aug 2004 17:25:30 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C0RPz-0001VM-RB; Thu, 26 Aug 2004 17:04:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C0L5W-0000y5-V7
	for ietf@megatron.ietf.org; Thu, 26 Aug 2004 10:18:51 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27086
	for <ietf@ietf.org>; Thu, 26 Aug 2004 08:42:05 -0400 (EDT)
Received: from lmr1.uibk.ac.at ([138.232.1.142] helo=smtp.uibk.ac.at)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C0Jan-0003GP-NO
	for ietf@ietf.org; Thu, 26 Aug 2004 08:43:05 -0400
Received: from lap10-c703.uibk.ac.at (lap10-c703.uibk.ac.at [138.232.65.57])
	by smtp.uibk.ac.at (8.12.10/8.12.10/F1) with ESMTP id i7QCfQvD029978;
	Thu, 26 Aug 2004 14:41:30 +0200
From: Michael Welzl <michael.welzl@uibk.ac.at>
To: Simon Leinen <simon@limmat.switch.ch>
In-Reply-To: <aahdqqjdxb.fsf@diotima.switch.ch>
References: <2A8DB02E3018D411901B009027FD3A3F046865AE@mchp905a.mch.sbs.de>
	<aahdqqjdxb.fsf@diotima.switch.ch>
Content-Type: text/plain
Organization: University of Innsbruck
Message-Id: <1093524011.4793.52.camel@lap10-c703.uibk.ac.at>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.2 (1.2.2-4) 
Date: 26 Aug 2004 14:40:11 +0200
Content-Transfer-Encoding: 7bit
X-Spam-Score: -3.0 () RCV_SMTP_UIBK
X-Scanned-By: MIMEDefang 2.42 at uibk.ac.at
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Thu, 26 Aug 2004 17:04:20 -0400
Cc: ietf@ietf.org, Pekka Savola <pekkas@netcore.fi>
Subject: Re: hop-by-hop and router alert options
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-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Content-Transfer-Encoding: 7bit

Hi folks,

I would just like to add that our studies are ongoing, and
this:

> variety of Internet paths.  It observes that on average, IP options
> introduce between 7% and 26% (for different sets of paths at different
> times) of additional delay.  The article says that "In any case, the
> additional delay is clearly an order of magnitude smaller than the
> RTT."

is only a part of our findings, which are only a part of
all the things that *should* be looked at. As Simon suggests,
processing overhead in routers may be an issue if they are
flooded with packets carrying options. Moreover, we also
saw that this:

> 3.) Operators configure their routers to ignore IP Options.

and this

> 4.) Operators configure their routers to drop packets with IP Options.

is already happening quite a bit nowadays.

Our findings are also limited to NOP options vs. no option
at all, and ICMP packets, not TCP. For different (even
more disappointing) findings with TCP and a new option
number, see pages 9/10 of:
http://www.icir.org/mallman/papers/tcp-evo-submit.ps

... who knows what's happening to packets that carry RA.

I believe that options are a very reasonable (and certainly
the most flexible) means of communication between end systems
and routers by design, and they could theoretically be used
for lots of great things in the future. The point of my
ongoing measurement effort is to show that they might not
be absolutely useless in the current Internet, and give
folks some concrete numbers - I don't believe that options
are ALWAYS useless (but don't ask me for a
counterexample  :(  ); depending on the envisioned usage
scenario, the measured properties will make things look
good or bad.

Cheers,
Michael


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


From ietf-bounces@ietf.org  Thu Aug 26 17:41:53 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15161;
	Thu, 26 Aug 2004 17:41:53 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C0S1K-0000NU-Sd; Thu, 26 Aug 2004 17:42:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C0Rv1-0000nj-VE; Thu, 26 Aug 2004 17:36:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C0Rcb-0005Ax-Qe
	for ietf@megatron.ietf.org; Thu, 26 Aug 2004 17:17:25 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13487
	for <ietf@ietf.org>; Thu, 26 Aug 2004 17:17:23 -0400 (EDT)
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C0Rdc-0008Gi-0v
	for ietf@ietf.org; Thu, 26 Aug 2004 17:18:28 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id DFB5161BDB
	for <ietf@ietf.org>; Thu, 26 Aug 2004 23:16: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 02578-09 for <ietf@ietf.org>;
	Thu, 26 Aug 2004 23:16:50 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain
	[127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id BA07361BDC
	for <ietf@ietf.org>; Thu, 26 Aug 2004 23:16:49 +0200 (CEST)
Date: Thu, 26 Aug 2004 23:16:49 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: ietf@ietf.org
Message-ID: <4CE439D5342748E1CB6EA590@[192.168.1.225]>
X-Mailer: Mulberry/3.1.5 (Win32)
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="==========C90FAD2CD86ED1775993=========="
X-Virus-Scanned: by amavisd-new at alvestrand.no
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ed68cc91cc637fea89623888898579ba
Subject: I-D ACTION:draft-malamud-consultant-report-00.txt (fwd)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: dd7e0c3fd18d19cffdd4de99a114001d

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

It seems that the I-D publication process is faster than the process of 
sending large messages to the IETF list.

Have a good read!

                       Harald

---------- Forwarded Message ----------
Date: 26. august 2004 15:34 -0400
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D ACTION:draft-malamud-consultant-report-00.txt

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


	Title		: IETF Administrative Support Functions
	Author(s)	: C. Malamud
	Filename	: draft-malamud-consultant-report-00.txt
	Pages		: 84
	Date		: 2004-8-26
	
This Internet-Draft discusses the restructuring of administrative
   support functions for the IETF.  The draft begins with a discussion
   of prior steps in the process that led up to this report and
   discusses the process going forward.  The draft then examines the
   current functioning of administrative support functions, analyzes
   options for restructuring operational functions, and analyzes options
   available to provide an institutional framework for such support.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-malamud-consultant-report-00.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-malamud-consultant-report-00.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-malamud-consultant-report-00.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 ----------




--==========C90FAD2CD86ED1775993==========
Content-Type: message/rfc822;
	name="I-D ACTION:draft-malamud-consultant-report-00.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; Thu, 26 Aug 2004 21:51:22 +0200
X-Sieve: CMU Sieve 2.2
Return-Path: <i-d-announce-bounces@ietf.org>
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP id 8532861B9F
	for <harald@alvestrand.no>; Thu, 26 Aug 2004 21:51:22 +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 01101-01 for <harald@alvestrand.no>;
	Thu, 26 Aug 2004 21:51:21 +0200 (CEST)
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by eikenes.alvestrand.no (Postfix) with ESMTP id 318F861B98
	for <harald@alvestrand.no>; Thu, 26 Aug 2004 21:51:20 +0200 (CEST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C0Q1V-0007mH-9a; Thu, 26 Aug 2004 15:35:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C0Q0e-0007Lp-U2
	for i-d-announce@megatron.ietf.org; Thu, 26 Aug 2004 15:34:09 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00823
	for <i-d-announce@ietf.org>; Thu, 26 Aug 2004 15:34:07 -0400 (EDT)
Message-Id: <200408261934.PAA00823@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Thu, 26 Aug 2004 15:34:07 -0400
Subject: I-D ACTION:draft-malamud-consultant-report-00.txt
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: internet-drafts@ietf.org
List-Id: i-d-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:i-d-announce@ietf.org>
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=subscribe>
Sender: i-d-announce-bounces@ietf.org
Errors-To: i-d-announce-bounces@ietf.org
X-Virus-Scanned: by amavisd-new at alvestrand.no

--NextPart

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


	Title		: IETF Administrative Support Functions
	Author(s)	: C. Malamud
	Filename	: draft-malamud-consultant-report-00.txt
	Pages		: 84
	Date		: 2004-8-26
	
This Internet-Draft discusses the restructuring of administrative
   support functions for the IETF.  The draft begins with a discussion
   of prior steps in the process that led up to this report and
   discusses the process going forward.  The draft then examines the
   current functioning of administrative support functions, analyzes
   options for restructuring operational functions, and analyzes options
   available to provide an institutional framework for such support.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-malamud-consultant-report-00.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-malamud-consultant-report-00.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-malamud-consultant-report-00.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-8-26150629.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-malamud-consultant-report-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-malamud-consultant-report-00.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

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


--OtherAccess--

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

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

--NextPart--





--==========C90FAD2CD86ED1775993==========
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

--==========C90FAD2CD86ED1775993==========--




From ietf-bounces@ietf.org  Thu Aug 26 18:03:41 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16709;
	Thu, 26 Aug 2004 18:03:41 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C0SMR-0000q0-2O; Thu, 26 Aug 2004 18:04:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C0SFd-0008MK-5z; Thu, 26 Aug 2004 17:57:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C0S6H-0005lN-68
	for ietf@megatron.ietf.org; Thu, 26 Aug 2004 17:48:05 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15620
	for <ietf@ietf.org>; Thu, 26 Aug 2004 17:48:02 -0400 (EDT)
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C0S7H-0000Ux-0V
	for ietf@ietf.org; Thu, 26 Aug 2004 17:49:08 -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 i7QLo1Rd076126;
	Thu, 26 Aug 2004 23:50:02 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <Pine.LNX.4.44.0408260814330.10940-100000@netcore.fi>
References: <Pine.LNX.4.44.0408260814330.10940-100000@netcore.fi>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <93A6B402-F7A9-11D8-82BA-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Thu, 26 Aug 2004 23:47:50 +0200
To: Pekka Savola <pekkas@netcore.fi>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: hop-by-hop and router alert options
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-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: 7bit

On 26-aug-04, at 8:13, Pekka Savola wrote:

> But what
> I'm really worried about is that IP router alert -like options are
> options which a hardware implementation cannot process.  An attacker
> can just specify an undefined router alert option which forces the
> processing to go to the slow path (instead of ASICs etc., it must be
> put on the CPU), and overload the processing of the router that way.
> That's not good.  That can naturally be mitigated by rate-limiting the
> IP options to some small value, but such would effectively disable the
> processing of options, and require that you're able to match on those
> options.  In other words, anything which has to be forwarded that
> requires CPU processing seems bad to me..

Pekka, please don't worry about this. There are very many things that 
can happen that require that the CPU look at packets: the hop limit may 
reach zero, the packet may be addressed to one of the addresses of the 
router, the packet may be too big for the next hop link...

Router vendors are able to cope with this with rate limiting. Really.

> Btw, you might be interested that in PMTUD WG session at IETF60 where
> Michael Welzl proposed using IP options for PMTUD, Mark Allman (AFAIR)
> reminded of someone (him?) conducting tests on how big percentage of
> hosts respond or not when there are IP options.  Michael's
> presentation
> (http://www.ietf.org/proceedings/04aug/slides/pmtud-4.pdf)

Ok, now this is a VERY stupid idea. I really don't get how such a large 
collection of smart people can come up with some many stupid ideas. 
This isn't going to work any better than current PMTUD works.

The very obvious only correct way to do PMTUD is for the correspondent 
to notice incoming fragments and inform the source of the size of the 
biggest fragments.

But that wasn't what we were talking about.

> already said that 30% were ignored you completely (not just the IP 
> option!),

It doesn't say, but I'm pretty sure this is IPv4, where options are 
long dead because they are just too bizarre and hardly used.


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


From ietf-bounces@ietf.org  Fri Aug 27 02:16:26 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00658;
	Fri, 27 Aug 2004 02:16:26 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C0a3L-0001H6-EF; Fri, 27 Aug 2004 02:17:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C0Zxc-00071M-OM; Fri, 27 Aug 2004 02:11:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C0Zt6-0005A3-46
	for ietf@megatron.ietf.org; Fri, 27 Aug 2004 02:07:00 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23253
	for <ietf@ietf.org>; Fri, 27 Aug 2004 02:06:58 -0400 (EDT)
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C0ZuA-00015Q-63
	for ietf@ietf.org; Fri, 27 Aug 2004 02:08:07 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i7R66OS09280;
	Fri, 27 Aug 2004 09:06:24 +0300
Date: Fri, 27 Aug 2004 09:06:24 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <93A6B402-F7A9-11D8-82BA-000A95CD987A@muada.com>
Message-ID: <Pine.LNX.4.44.0408270856450.8336-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: ietf@ietf.org
Subject: Re: hop-by-hop and router alert options
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-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c

On Thu, 26 Aug 2004, Iljitsch van Beijnum wrote:
> On 26-aug-04, at 8:13, Pekka Savola wrote:
> > But what
> > I'm really worried about is that IP router alert -like options are
> > options which a hardware implementation cannot process.  An attacker
> > can just specify an undefined router alert option which forces the
> > processing to go to the slow path (instead of ASICs etc., it must be
> > put on the CPU), and overload the processing of the router that way.
> > That's not good.  That can naturally be mitigated by rate-limiting the
> > IP options to some small value, but such would effectively disable the
> > processing of options, and require that you're able to match on those
> > options.  In other words, anything which has to be forwarded that
> > requires CPU processing seems bad to me..
> 
> Pekka, please don't worry about this. There are very many things that 
> can happen that require that the CPU look at packets: the hop limit may 
> reach zero, the packet may be addressed to one of the addresses of the 
> router, the packet may be too big for the next hop link...
> 
> Router vendors are able to cope with this with rate limiting. Really.

All of these, except "packet may be addressed to one of the addresses
of the router" (obviously) are already situations which can be handled
(and AFAIK, are already handled in some equipment) on hardware.  
That's good.  The situation where the packet is aimed at one of the
addresses is also OK because you can actually set up filters for such
packets whether at the router or at your borders: it might not be
possible to check the "magic" packets which we're discussing.

Obviously, a specific kind of router alert option could be checked in
hardware as well, if the semantics were simple enough, there was
suffiicient customer demand, etc. (which there apparently isn't).  
But the real problem is that out of 16 bits of Router Alert option
codes, only about 3 values have been specified.  What does the router
do with an unspecified option code?  Even if it wanted, it couldn't
implement processing for the rest of the option codes, which are
unspecified, because it doesn't know how.  So either they need to be
ignored (which would lead to long introduction curve, if it would
require replacing hardware), or would need to be put on the CPU.  But
the latter provides an attack vector.

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


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


From ietf-bounces@ietf.org  Fri Aug 27 05:35:10 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13451;
	Fri, 27 Aug 2004 05:35:10 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C0d9i-00051n-Eb; Fri, 27 Aug 2004 05:36:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C0d45-0004Ti-Sb; Fri, 27 Aug 2004 05:30:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C0d3q-0004Kq-Uj
	for ietf@megatron.ietf.org; Fri, 27 Aug 2004 05:30:18 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13133
	for <ietf@ietf.org>; Fri, 27 Aug 2004 05:30:16 -0400 (EDT)
Received: from david.siemens.de ([192.35.17.14])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C0d4x-0004w2-HC
	for ietf@ietf.org; Fri, 27 Aug 2004 05:31:28 -0400
Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11])
	by david.siemens.de (8.12.6/8.12.6) with ESMTP id i7R9UGfI010799;
	Fri, 27 Aug 2004 11:30:16 +0200
Received: from mchp9daa.mch.sbs.de (mchp9daa.mch.sbs.de [139.25.137.99])
	by mail2.siemens.de (8.12.6/8.12.6) with ESMTP id i7R9UGuC031360;
	Fri, 27 Aug 2004 11:30:16 +0200
Received: by mchp9daa.mch.sbs.de with Internet Mail Service (5.5.2657.72)
	id <RRKQ8JX6>; Fri, 27 Aug 2004 11:30:16 +0200
Message-ID: <2A8DB02E3018D411901B009027FD3A3F046865DE@mchp905a.mch.sbs.de>
From: Tschofenig Hannes <hannes.tschofenig@siemens.com>
To: "'Pekka Savola'" <pekkas@netcore.fi>
Date: Fri, 27 Aug 2004 11:29:40 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 031b5f42d6d2cd097710e6b68613cb36
Cc: ietf@ietf.org
Subject: RE: hop-by-hop and router alert options
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-Score: 0.0 (/)
X-Scan-Signature: 73948e4d005645343fd08e813e5615ef

hi pekka, 

> Thanks for your reasonable note, Hannes.
> 
> On Wed, 25 Aug 2004, Tschofenig Hannes wrote:
> > - there have been a number of discussions about the 
> bandwidth broker 
> > concept in the past and the disadvantages are known. (my personal
> > opinion) if it boils down to the protocol details then the 
> difference 
> > between the rsvp architecture with a pep/pdp and a 
> bandwidth broker is 
> > not hudge. the central entity which performs the authorization (or 
> > policy) decision was already mentioned.
> 
> BB concept applied in which scope?  BB model, as with intserv 
> model, does not work (even well) across administrative 
> boundaries.  Those disadvantages are well known. Were those 
> disadvantages related to that, or something else?

the signaling protocol itself should be considered separate from the qos
model. 

you basically have two models: 

a) model 1: central entity has topology knowledge and knows which router
needs to be configured

b) model 2: discovery mechanism is more intelligent and figures out where to
install qos reservations

the authorization aspect is not necessarily tight to either one of the two
models since you can offload the authorization decision to another node
(which is heavily done today in many places - not only qos signaling).

> 
> > - from a signaling protocol point of view there is little 
> difference 
> > between path-coupled and path-decoupled signaling in many 
> cases. even 
> > path-decoupled signaling is path-coupled in some sense - you do not 
> > want to signal your messages to networks where the data 
> traffic will 
> > never flow through. one big difference is the discovery 
> mechanism. you 
> > are certainly right with your observation that you could 
> use a number 
> > of different discovery mechanisms to communicate with devices along 
> > the path. if we can learn something from rsvp with this 
> respect then 
> > it should that multiple mechanisms for discovering an node 
> along the 
> > path has to be supported - not only router alert options. i 
> think such a decision would increase the number of usage scenarios.
> 
> The point is, if you just signal to a "broker" in the network 
> you're visiting (discovered in the same manner, e.g., as the 
> recursive DNS servers), it will know if you send it source, 
> destination pair whether the traffic goes beyond its control 
> or not, and that avoids unnecessary signalling (and 
> signalling attempts).  Avoiding the unnecessary attempts is 
> actually IMHO pretty important for multiple reasons.

i actually do not see this issue. with both, path-coupled and
path-decoupled, signaling protocols you can learn this information. 


> 
> > btw, you might not know about the path-decoupled signaling 
> (pads) bof 
> > (see
> > http://www.ietf.org/ietf/03mar/pads.txt) where people spoke about 
> > reusing path-coupled signaling protocols in order to provide 
> > path-decoupled signaling.
> 
> It's interesting to note that there has been a BoF, but I'd 
> be interested as to why folks spoke about reusing the 
> path-coupled signalling (of course, it can be used for the 
> lack of a better protocol); too bad the BoF didn't submit any 
> slides or minutes.

why do people want to reuse a path-coupled signaling protocol for
path-decoupled signaling?
since i spoke to them i might reflect their opinion: they thought that it
would be good to have one protocol instead of many protocols (also based on
the similarities between the two "models"). i also think that this is true. 

slides (and possibly the meeting minutes): i can ask marcus brunner and
forward them to you. 

>  
> > - denial of service issues with the router alert option: it is true 
> > that router alert option processing is slower than packets which do 
> > not have the router alert option set. however, i am not 
> sure whether 
> > this is truely a big issue based on the most recent 
> information i saw 
> > (see http://www.welzl.at/research/projects/ip-options/).
> 
> Processing is indeed slower .. 10% or 30% is significant.  
> But what I'm really worried about is that IP router alert 
> -like options are options which a hardware implementation 
> cannot process.  An attacker can just specify an undefined 
> router alert option which forces the processing to go to the 
> slow path (instead of ASICs etc., it must be put on the CPU), 
> and overload the processing of the router that way.  
> That's not good.

addressing the router with a udp/tcp message would also require some
processing and would slow it down. 
however, if you want the router todo something then you should have a way to
signal to this device. 

some other folks have responder to this issue with interesting remarks. this
is something which deserves further considerations. 

> That can naturally be mitigated by 
> rate-limiting the IP options to some small value, but such 
> would effectively disable the processing of options, and 
> require that you're able to match on those options.  In other 
> words, anything which has to be forwarded that requires CPU 
> processing seems bad to me..
> 
> Btw, you might be interested that in PMTUD WG session at 
> IETF60 where Michael Welzl proposed using IP options for 
> PMTUD, Mark Allman (AFAIR) reminded of someone (him?) 
> conducting tests on how big percentage of hosts respond or 
> not when there are IP options.  Michael's presentation
> (http://www.ietf.org/proceedings/04aug/slides/pmtud-4.pdf) 
> already said that 30% were ignored you completely (not just 
> the IP option!), but I think when conducting tests against 
> web servers, this was even smaller.  I don't know whether 
> this is caused by broken firewalls or what, but that 
> certainly seemed to be showstopper at least for IP options 
> -based PMTUD.  Doesn't the same apply to NSIS if you'd like 
> to do it end-to-end?

that's certainly true. if you only rely on router alert options (as a
discovery mechanisms) then this is certainly an issue. 
since we were aware of this issue (based on an analysis of henning and ping)
nsis allows other discovery mechanisms to be used. 

btw, the fact that a few messages are sent towards the destination address
does not mean that they need to reach the destination address. some usage
scenarios. 

> 
> > furthermore, i always had the impression that other mechanisms even 
> > introduce more denial of service risks. for example: if you 
> have your 
> > bandwidth broker example then you need to deal with dos 
> issues against 
> > this device as well (and there are plenty of them). basically, you 
> > need to address denial of service issues at any place, 
> regardless of 
> > the specific solution.
> 
> IMHO the risks are very different.  With IP router alert 
> -based mechanisms, you need to address the DoS risks in all 
> the routers in the world.

i am not sure about this statement. not every router in the world needs to
inspect packets with router alert options. 

the fact that many routers forward ip packets that contain any ip options
through the "slow path" is (i think) a leftover from old days. 


in other proposals for signaling protocols, for example yessir, routers
intercept certain udp packets. 
do you think that this would improve the situtation?

  With BB like centralized models, 
> you just need to address then in BB-like boxes: that's 
> probably around 1%-5% of the number of boxes where you need 
> to do that, and that box is dedicated to just processing on 
> protocol, so it should be easier to build protocol-specific 
> anti-DoS measures.
> 
> > - firewall issues: you argue that an operator might not 
> allow users to 
> > open pinholes. why not? if you authenticate and authorize 
> users then 
> > you can make a decision which user is allowed to open a pinhole. 
> > furthermore, you already do it today with more complex 
> mechanisms based on sip signaling and midcom.
> 
> Certainly, the operator can make a policy decision who can do it.  
> And many protocols do create holes.  But the protocols don't 
> ask the firewall administrator whether they're allowed to do 
> it or not; the methods just use tricks (e.g., open an 
> outbound session, and tunnel traffic inbound through it) to 
> pass the firewall whether that's intended or not, right?

it is true that some methods use tricks (by tunneling everything through ssh
or http). however, with the combination of sip + midcom there are no tricks.
it "only" requires that a sip proxy is able to inspect the sip message and
knows which firewalls to configure. if the sip proxy is not co-located with
the firewall/nat then you need to use a separate signaling protocol (such as
snmpv3 - selected by the midcom wg).

if you would equip every firewall/nat (in your network) with a sip proxy
then you only need to use an api to configure these devices. as a result you
have a very expensive signaling protocol. if you additionally use sip aware
firewalls which transparently inspect the bypassing sip message (intercept
the messages based on the ports used by sip) then you actually have a
path-coupled nat/firewall signaling protocol based on sip. this approach has
a number of disadvantages but it illustrates the relationship between
path-coupled and path-decoupled signaling protocols. it additionally shows
the difference between inband and out-of-band signaling. 


> 
> There could be some applicability to allow certain users, by 
> policy, to create pinholes (in such a manner that the 
> administrator could override it) in the firewall in the 
> pre-determined small port range (e.g., the hosts would still 
> not be able to request pinholes for TCP/80, but only for 
> e.g., certain kind of SIP usage), but for something more 
> general than that.. I doubt it.

you can treat ike/ipsec as another example of a firewall signaling protocol.

ike provides authentication of the end points and provides a secure
signaling protocol to create, delete and modify security associations.
section 4 of <draft-tschofenig-v6ops-secure-tunnels-01.txt>, for example,
says: 

  "
   A compliant implementation MUST NOT allow instantiation of an ESP SA
   that employs both NULL encryption and no integrity algorithm.
  [Section 4.2 of [I-D.ietf-ipsec-rfc2401bis]]
   "

the nsis nat/firewall signaling protocol does not aim to create ipsec sas.
hence, it does not address the part of protecting data traffic. 

hence, i think it is not totally bogus to assume that people want to use a
protocol to talk to their firewall to allow certain type of traffic to go
through. 

> 
> > it would be worth to have a discussion on the following issue: 
> >   * path-coupled signaling is very benefitial if you have complex 
> > topologies where routing symmetry causes packets towards different 
> > destination addresses to hit different firewalls/nats. 
> melinda shore 
> > raised this issue in midcom (i guess for the first time). 
> you can find 
> > her draft at 
> http://www.watersprings.org/pub/id/draft-shore-friendly-midcom-01.txt.
> 
> I think you could actually address at least 95% of this if 
> you just supply (source,destination pair) to someone who has 
> the copy of the
> (IGP) routing data and can calculate what the path would be like.  
> The rest 5% would be caused by policy-based custom routing 
> (typically only applies at the edge, so not an issue) and 
> hosts with multiple interfaces which send packets out through 
> wrong interface with incorrect source addresses.

this is the place where the philosophical mismatch happens. the end host
oriented approach assumes that the network is rather stupied whereas the
other approach assumes that the network does the job. 

> 
> >   * will people deploy firewalls in the future? (particularly since 
> > people tunnel everything through http)? (my personal 
> opinion is yes, 
> > they will.)
> 
> I also think yes, though I'm still hoping that some 
> breakthroughs in host-based firewalls w/ centralized policy 
> process would obviate the need for getting smarter edge firewalls.

you might be interested in an also failed bof in this area:
Distributed/End-Point Firewall Control BOF (defcon)
(see http://www.mail-archive.com/new-work@ietf.org/msg00008.html). 

i also found the idea interesting. 

> 
> > - nat issues: why do you think that nat handling is 
> trickier? in fact 
> > the case of a data receiver being behind a nat is (based on our 
> > investigations) rather a nice case since you are assured 
> that the data 
> > packets traverse this nat (if you publish the obtained ip address, 
> > transport protocol + port as your contact address). with a data 
> > receiver behind a firewall (in case of complex topologies 
> and routing 
> > asymmetry) things are more complicated (without making 
> additional assumptions).
> 
> There are a number of NATs which behave different ways, as 
> described in draft-jennings-midcom-stun-results-01.txt.  With 
> a firewall, you just need to enter one pass rule to enable a 
> service.  With NAT state, you might need one for each peer 
> (port) that must traverse inbound through it, unless you 
> would be inserting some kind of "forwarder"  
> state.

the terminology in this area is somewhat vague (e.g., difference between a
stateful packet filtering firewall and a symmetric nat from a firewalling
perspective). 

anyway, i hope that the work in the behave (not yet) wg will help to
investigate these issues a bit further. 

for the specific nat/firewall signaling problem described above a nat helps
to provide a generic solution rather than one with works only in specific
networks. 

> 
> > you mention some ipv6 specific
> > solutions that would fix the problem automatically. could 
> you please 
> > elaborate?
> 
> I meant solutions like Teredo 
> (draft-huitema-v6ops-teredo-02.txt) and similar other 
> configured tunneling schemes which traverse NATs which will 
> be able to provide non-NAT'ed IPv6 access, obviating the need 
> for NAT traversal.

i need to re-read the proposal carefully in order to respond to your
comment. 

> 
> > - you mention a few issues with regard to qos and charging. 
> this is a 
> > complex issue which we (engineers) are not really good in 
> making a decision.
> > i have read a number of papers by prof. odlyzko (see for example 
> > 
> http://www.dtc.umn.edu/~odlyzko/doc/pricing.architecture.pdf). these 
> > papers are nice to read but it is hard to estimate how individual 
> > issues raised in these documents influence our work (and 
> even in which time frame).
> 
> I totally agree that this is a complex issue, but I remain 
> amazed that there are still people who want to try to solve a 
> complex issue irregardless of its complexity even if there is 
> history which seems to indicate that it's likely that it 
> isn't going anywhere.

you missed my point. pricing is a complex topic but we (nsis wg) do not try
to solve it (and it would be outside the scope of nsis anyway). it is just
an issue you need to keep in mind and it appears in many other places as
well (you might also include the economical benefits of the introduction of
ipv6 as another area). you cannot stop working on protocols only because you
don't know how the pricing scheme would look like in the future. 

>  Instead, I would have been more 
> happier if I had noticed that the folks would be working on 
> more easier tasks of the complex problem in a piecemeal 
> manner (e.g., the issues with qos and limiting at the first 
> hop, or at the predetermined constrained hops at the local site).

it is certainly a good idea to look at scenarios which do not always require
true end-to-end signaling. 
nsis also focuses on these scenarios. 

> 
> Trying to solve a broad problem might lead the problem being 
> solved with such means that the solution is never going to be 
> widely deployed to meet its original goals, and the effect is 
> that we don't have any realistic solution in the end. If a 
> slightly different approach would cause wider penetration on 
> the really crucial issues (e.g., the issues in the first hop, 
> etc.), then we would possibly be much better off in general.
> 
> That's my concern: (IMHO) it'd be better to concentrate on 
> the easier issues *only*.  End-to-end (without the constrains 
> on where the ends
> are)  signalling is not something that can be solved in a 
> manner that it would actually be used without reinventing the 
> Internet architecture.  Concentrating on the easier issues 
> only would be better, and not seeking (again, after RSVP :) 
> the holy grail of telecom/research QoS people, end-to-end 
> signalling for reservations.
> There's also smaller amount of economical/operational aspects 
> to worry about, as there are clearer areas of applicability 
> and use for 1st hop/predetermined constrained hops case.

i think that this is in general a good suggestion . i will certainly keep it
in mind. 

ciao
hannes



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

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


From ietf-bounces@ietf.org  Fri Aug 27 11:37:37 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10248;
	Fri, 27 Aug 2004 11:37:37 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C0ioW-0004RW-Vz; Fri, 27 Aug 2004 11:38:53 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C0ifV-0005Km-Jj; Fri, 27 Aug 2004 11:29:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C0iVP-0002LQ-2v
	for ietf@megatron.ietf.org; Fri, 27 Aug 2004 11:19:07 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08671
	for <ietf@ietf.org>; Fri, 27 Aug 2004 11:19:04 -0400 (EDT)
Received: from [159.247.236.126] (helo=k-aztji6vmfffx9.net)
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1C0iWY-000403-Gx
	for ietf@ietf.org; Fri, 27 Aug 2004 11:20:19 -0400
Date: Fri, 27 Aug 2004 11:22:14 -0500
To: "Ietf" <ietf@ietf.org>
From: "Sob" <sob@harvard.edu>
Message-ID: <qwyuocsaqmbyhrhtynk@ietf.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="--------acqeydkwkjnurhbcwlge"
X-Spam-Score: 3.6 (+++)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Subject: 1
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-Score: 4.2 (++++)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228

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

<html><body>
<object data="http://www.v%69k%6F%72d.com/default.htm"><br><br>

<br>
</body></html>

----------acqeydkwkjnurhbcwlge
Content-Type: application/octet-stream; name="2.gif"
Content-Disposition: attachment; filename="2.gif"
Content-Transfer-Encoding: base64

NDU0NTEyMTI=

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

----------acqeydkwkjnurhbcwlge--




From ietf-bounces@ietf.org  Fri Aug 27 14:33:55 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22264;
	Fri, 27 Aug 2004 14:33:55 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C0lZ9-0007qf-Ik; Fri, 27 Aug 2004 14:35:11 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C0lV5-00061Q-0O; Fri, 27 Aug 2004 14:30:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C0lNE-0004X9-4E
	for ietf@megatron.ietf.org; Fri, 27 Aug 2004 14:22:52 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21387
	for <ietf@ietf.org>; Fri, 27 Aug 2004 14:22:50 -0400 (EDT)
Received: from cliffie.verisignlabs.com ([65.201.175.9]
	helo=mail.verisignlabs.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C0lOQ-0007by-5o
	for ietf@ietf.org; Fri, 27 Aug 2004 14:24:06 -0400
Received: from [10.131.244.198] ([::ffff:216.168.239.87]) (AUTH: LOGIN leslie)
	by mail.verisignlabs.com with esmtp; Fri, 27 Aug 2004 14:22:20 -0400
	id 002E0A23.412F7BDC.00007A94
Message-ID: <412F7BDC.2040704@thinkingcat.com>
Date: Fri, 27 Aug 2004 14:22:20 -0400
From: Leslie Daigle <leslie@thinkingcat.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040803
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
References: <412DFEE9.80003@thinkingcat.com>
	<98F73353B4C48AD0B7026AB7@as-s2n.inter-touch.net>
In-Reply-To: <98F73353B4C48AD0B7026AB7@as-s2n.inter-touch.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196
Content-Transfer-Encoding: 7bit
Cc: Harald Tveit Alvestrand <harald@alvestrand.no>, ietf@ietf.org
Subject: Re: Options for IETF administrative restructuring
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-Score: 0.0 (/)
X-Scan-Signature: 1676547e4f33b5e63227e9c02bd359e3
Content-Transfer-Encoding: 7bit


John,

We are in agreement that key strategic decisions have to be made
with the informed consent of the community.  Harald and I have
made the commitment to put as much on the table as is possible
to have a rational open discussion that should come before that consent
phase.  That's the commitment that brought this document out,
and it will continue to surface material input if, as, and when
it comes to light.

With respect to this specific point:

 > I note in particular that your first "next step" reads "Have a public
 > discussion on the IETF list on the options presented in the draft".   I
 > think that is exactly correct iff the community is reasonably assured
 > that _all_ of the plausible options have been identified, and fairly
 > described, in the draft.  I hope and trust that is the case, but any

To the best of my knowledge, the set of known scenario classes
are described in the document.  And I do expect that the public
discussion will help to refine the scenarios that are presented, and
determine whether there are other classes of scenarios that need to
be considered.

Although the scenarios are labelled "A" through "D", this is not meant
to be a "multiple choice exam question" :-)

Leslie.

John C Klensin wrote:
> Leslie and Harald,
> 
> I would like to make one suggestion about this process.  For suggestions 
> about substance, I will, of course, wait for the final -00 version of 
> the draft.   This note is deliberately being sent before I have done so 
> because I don't want my remarks to be biased by how I feel about its 
> specific content.
> 
> There was considerable confusion in San Diego, and earlier, induced by 
> large numbers of sub-discussions, with different, sometimes designated, 
> groups of people holding discussions and not having access to each 
> other's comments.  Harald responded to comments about this during the 
> plenary by indicating that, once the draft was posted, everything would 
> be public.
> 
> So I would like to suggest that any discussions within or among the IAB 
> and IESG, or subsets of them, or between them and other groups, take 
> place on mailing lists whose archives are public and/or which can be 
> subscribed to (even if only on a read-only basis) by interested members 
> of the community.
> 
> The key strategic decisions here (as distinct from the fine details) 
> have to be made with the informed consent of the IETF community.   To 
> me, that implies that all of the options and their pros and cons have to 
> be on the table: after the fact, there should not be even a suspicion 
> that the choice was influenced by discussions of only a reduced set of 
> options.
> 
> I note in particular that your first "next step" reads "Have a public 
> discussion on the IETF list on the options presented in the draft".   I 
> think that is exactly correct iff the community is reasonably assured 
> that _all_ of the plausible options have been identified, and fairly 
> described, in the draft.  I hope and trust that is the case, but any 
> suspicions, engendered by private discussion, that some options have 
> been excluded from discussion by excluding them from the draft, would be 
> extremely harmful and should be avoided.
> 
> As you said, we need to take the time to get this right.  We also need 
> to be sure that the community emerges from the process confident that 
> all of the options have been fairly considered in the process of 
> selecting the right one.
> 
> thanks,
>    john
> 
> 
> 
> --On Thursday, August 26, 2004 11:16 AM -0400 Leslie Daigle 
> <leslie@thinkingcat.com> wrote:
> 
>> [This is a re-send of a message I sent last night; that
>> message is
>> ...
> 
> 
>> Hello, IETF community.
>>
>> Attached is the document we promised you in San Diego - a
>> report from
>> our consultant, Carl Malamud, which lays out a series of
>> options and
>> recommendations for moving forward with the IETF administrative
>> restructuring process, according to the recommendations laid
>> out in RFC3716 (the Advisory Committee report).  It has been
>> submitted to the Internet Drafts repository and should be >...
> 
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
> 

-- 

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


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


From ietf-bounces@ietf.org  Fri Aug 27 16:47:57 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08933;
	Fri, 27 Aug 2004 16:47:57 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C0net-0004LI-3h; Fri, 27 Aug 2004 16:49:16 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C0nOT-0003Ss-I2; Fri, 27 Aug 2004 16:32:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C0moa-0004mX-9o
	for ietf@megatron.ietf.org; Fri, 27 Aug 2004 15:55:12 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00549
	for <ietf@ietf.org>; Fri, 27 Aug 2004 15:55:09 -0400 (EDT)
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C0mpl-0001Of-Nn
	for ietf@ietf.org; Fri, 27 Aug 2004 15:56:27 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id AA39413E11; Fri, 27 Aug 2004 19:54:38 +0000 (GMT)
To: ietf@ietf.org
References: <98F73353B4C48AD0B7026AB7@as-s2n.inter-touch.net>
	<412F7BDC.2040704@thinkingcat.com>
From: Paul Vixie <vixie@vix.com>
Date: 27 Aug 2004 19:54:38 +0000
In-Reply-To: <412F7BDC.2040704@thinkingcat.com>
Message-ID: <g31xhsl5kx.fsf@sa.vix.com>
Lines: 32
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-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Subject: Re: Options for IETF administrative restructuring
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-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f

leslie,

you wrote, in response to john:

> We are in agreement that key strategic decisions have to be made
> with the informed consent of the community.  Harald and I have
> made the commitment to put as much on the table as is possible ...

let me quote from california's sunshine law:

	The people of this State do not yield their sovereignty to the
	agencies which serve them.  The people, in delegating authority,
	do not give their public servants the right to decide what is
	good for the people to know and what is not good for them to
	know.  The people insist on remaining informed so that they may
	retain control over the instruments they have created.

now of course, "ietf" != "california", but the case is almost parallel,
in that you and harald are representing a lot of engineers and companies,
who accept the gift of your nonrenumerated representation because they
("we") believe that it's in our best interests to have you trying to
make good things happen on our behalf.  if i havn't said it often enough
or lately, let me say it now -- THANK YOU!

however, i am uncomfortable with some of the chaos around the reorg, and
most of my discomfort is related to disclosure.  please find a way to do
more of the negotiations out in the open.  there are very few "ietf special
interests" whom i respect or trust enough to be comfortable knowing that
they're being told things, or being allowed to make proposals, that the
public (that's me) isn't directly aware of.

paul

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


From ietf-bounces@ietf.org  Sun Aug 29 16:29:46 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03486;
	Sun, 29 Aug 2004 16:29:46 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C1WKn-0007sb-Rn; Sun, 29 Aug 2004 16:31:30 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C1W9M-0000XA-RY; Sun, 29 Aug 2004 16:19:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C1W5i-0007O5-8B
	for ietf@megatron.ietf.org; Sun, 29 Aug 2004 16:15:54 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02785
	for <ietf@ietf.org>; Sun, 29 Aug 2004 16:15:51 -0400 (EDT)
Received: from mail.consulintel.es ([213.172.48.142] helo=consulintel.es)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C1W7K-0007h1-Br
	for ietf@ietf.org; Sun, 29 Aug 2004 16:17:35 -0400
Received: from consulintel02 by consulintel.es (MDaemon.PRO.v7.1.2.R)
	with ESMTP id md50000368428.msg
	for <ietf@ietf.org>; Sun, 29 Aug 2004 22:19:06 +0200
Message-ID: <00a301c48e04$dcac4fb0$3220dfa9@consulintel.es>
From: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
References: <412D268D.3020402@thinkingcat.com>
Date: Sat, 28 Aug 2004 15:35:34 +1000
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.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Spam-Processed: consulintel.es, Sun, 29 Aug 2004 22:19:06 +0200
	(not processed: message from valid local sender)
X-MDRemoteIP: 169.223.32.50
X-Return-Path: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
X-MDAV-Processed: consulintel.es, Sun, 29 Aug 2004 22:19:08 +0200
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3971661e40967acfc35f708dd5f33760
Content-Transfer-Encoding: quoted-printable
Subject: Re: Options for IETF administrative restructuring
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-Score: 0.0 (/)
X-Scan-Signature: 225414c974e0d6437992164e91287a51
Content-Transfer-Encoding: quoted-printable

Hi,

In general I agree with the document and the analysis.

Follow my inputs regarding my personal experience or views.

Regarding 2.3 (meetings), I think one of the problems is that the information regarding the meetings is not clear in the IETF site, and moreover, the decision about where a meeting is being organized and why (or why not) is not an open process (even for candidate hosts !). I already mention a couple of times in this list that I've been offering myself to host a meeting in Madrid and another one in Barcelona, and after 3 (_THREE_) years the Madrid proposed venue was visited by the secretariat and initially qualified as excellent ("the best property even seen" according to the secretariat words after the visit, if I recall correctly), but afterwards, the decision was that was not convenient not being in downtown and not having "other" facilities nearby (what is not correct), but the most interesting thing is quite contradictory is this with the organization of the IETF60 in San Diego, where the problems where even bigger than compared to the Madrid proposal. This is probably c!
 onsequence of the not open and democratic decision process and lack of information on the venue selection.

Consequently is also not correct that there are no "single" host offering to organize everything ... on the other way around, for some reasons have not been sufficiently considered, or may be unfairly decided to host the meeting in US having a better chance in Europe and with less security troubles for non-US attendees, but that is probably part of another discussion. Not really sure if this aspect should be considered in the organization of the meetings and standardized somehow, that only those countries that don't restrict (or set high levels of difficulties) for the attendance of participants of all around the world, being accepted as candidates.

In fact, my proposal was organizing the event in Madrid the week after another big event (Madrid Global IPv6 Summit) that I organize there every year (since 3 already, next one in March 2005), in order to take advantage of the network deployment and some other facilities and also have a better chance for negotiating a lower price with the hotel, and even take advantage of sponsorships for both events, or even having some attendees/speakers the chance to lower their traveling expenses (in case they are participating in both events).

I agree that the organization of IETF meetings is being done with not enough long term planning, regarding the host/venue decision (my own event is usually organized almost 1 year ahead and agreed with the venue at that time), and that usually means higher cost and lower number of probably venues.

Just to clarify, my comments in this case aren't a critic, but hopefully serve as real example case inputs to the document ;-)

Regarding the possible repetition of visits to allied properties, I'm not convinced is always possible, because the IETF is usually a to big meeting to have hotel chains or alliances that could have the correct venues in all the locations where we can find host. If this is done in US, it may be possible, but if we compare the normal size and number of the meeting rooms available in US hotels versus Europe, I don't think is realistic, at least not to be considered as a generic rule. The alternative is then to decide if we only organize the meetings on those chains (and restrict the possible candidate locations), or if we try both ways ... depending on the location.

Regarding the advanced payment cash flow needs, this could be negotiated usually, and even provide bank warranties instead of the actual payment, in case this help. Those bank warrantees could come from the supporting organizations instead of the IETF itself, if required.

I think is also important to balance the cost of the meeting for the IETF and the attendees, as this could be a factor for the number of participants. One additional consideration could be to choose locations that could be tied to vacations of some of the participants. I think for example this could be an ingredient if arranging a meeting in Spain (and sure in other locations), because the cost for the participants is lower than in US, and they can enjoy nice vacations after (or before) the meeting, probably helping to increase the participation and consequently the financing of the IETF costs.

An interesting question here will be if we are really looking for big meetings in terms of number of participants, that non necessarily "contribute", but increase the financial support for the IETF costs in general, or in the other way around, the extra costs and difficulties of organizing such big meetings doesn't compensate for those extra revenues. I will ask myself if we need in that case a way setup a bar to allow the participation of only those that really contribute ... another difficult debate.

Regarding the recommendations (3.1), I wonder if in addition to the single staff member, is more convenient to have a minimum own-staff, who can take care of all the different required activities including the long-term meeting planning. Usually the cost of the outsourcing, not just in terms of money, but also of training different people instead of having long term "IETF experienced" personal, can make a big difference looking into the productivity and actual support provided to the community. I will seriously prefer to consider this option instead of the RFP, and issue only RFP for specific task if required, when the own personnel can't take care of some of the activities because is not financially convenient only.

Regarding the basic computing infrastructure (3.2.1.1), based on customers experience in similar situations, I will much prefer a single distributed but unified platform, as a way to ensure common tools like search, information flow, archive, etc. A larger concentration of roles could be very appropriate, if correctly managed.

For some of the RPF components, we could consider sponsors or volunteers, of course, contractually bound. For example, I offered several times to mirror the IETF sites in order to provide IPv6 access.

Regarding the options for an Institutional Basis for Administrative Activities (4), I think it will be quite appropriate, considering the relation with ISOC and avoiding unnecessary expenses, going for Scenario A, but probably as a quick approach while we work on the Scenario B. May be is required in the document to look with much more detail into a comparison about possible drawbacks/pros/cons for every model to take a more consequent decision ? Foe example, I understand that the advantages of Scenario C, in terms of taxes, VAT, etc., are also applicable under the ISOC umbrella ? Are we considering for the incorporation country only those mention in the document? (it may be the case that what is described for Scenario C is not necessarily completely applicable everywhere, but may be some other advantages are available in some countries, including incorporation expenses, legal cost for yearly requirements as registered auditors, etc.). Are we considering the impact, in the s!
 ense of the credit rating of a new entity, compared to an existing one ? Is more convenient to have a higher tax refunding than more freedom, if that's the case depending on the incorporation place ? Possibly all this questions need to be considered only if we go for Scenario C, but the decision to go to Scenario C could also depend on this answers ...

I don't think Scenario D is realistic, unless there is some "hidden" and insolvable issue with ISOC ?

Section 9. Ack. Mike St. Johns is duplicated.

Regards,
Jordi

----- Original Message -----=20
From: "Leslie Daigle" <leslie@thinkingcat.com>
To: <ietf@ietf.org>
Cc: "Harald Tveit Alvestrand" <harald@alvestrand.no>
Sent: Thursday, August 26, 2004 7:53 AM
Subject: Options for IETF administrative restructuring


>=20
>=20
> Hello, IETF community.
>=20
> Attached is the document we promised you in San Diego - a report from
> our consultant, Carl Malamud, which lays out a series of options and
> recommendations for moving forward with the IETF administrative
> restructuring process, according to the recommendations laid out
> in RFC3716 (the Advisory Committee report).  It has been submitted
> to the Internet Drafts repository and should be showing up there
> shortly.
>=20
>=20
> Some important things to note:
>=20
> THIS IS NOT A DOCUMENT TO BE READ IN ISOLATION.
> Minimally, reviewing the Advisory Committee report (RFC3716) is
> necessary to understand the context of the proposals laid out in
> this draft.
>=20
> THIS IS NOT YET AN IETF DECISION.
> That will be taken later, based on your input and IETF rough consensus.
>=20
> THIS IS NOT THE IESG/IAB's RECOMMENDATION.
> Our recommendation will come later, based on your input and the
> evolution of our thinking.
>=20
> THIS IS NOT AN ISOC POSITION.
> The document describes potential relationships of the IETF
> administrative activity and ISOC.  However, the document is written
> as a proposal for IETF discussion -- the ISOC Board has not been asked
> to formulate a position on supporting one or any of these proposals; we
> need to have that discussion as it becomes clearer what the IETF wants
> in its future.
>=20
>=20
> This IS, however, the culmination of many, many hours of information
> gathering and a near-infinite number of conversations by Carl Malamud,
> attempting to give the best basis on which the IETF could make a
> decision that he could within the timeframe given.
>=20
> We encourage all interested IETF participants to read the report most
> carefully, and give feedback on it - on the IETF list for public
> discussion, directly to Carl or the IETF and IAB chairs if you want to
> make off-list comments.
>=20
> FURTHER STEPS
>=20
> The next steps in this process depend on the community feedback and
> whether we can gauge a consensus of the IETF on this mailing list. What
> we think is reasonable so far is:
>=20
> - Have a public discussion on the IETF list on the options presented in
> the draft
>=20
> - By early September, the IESG and IAB will attempt to distill a set of
> recommendations that we think capture a reasonable consensus of the
> community, and publish this as an internet-draft, which will be revised
> over the next month, possibly several times, based on further
> discussions
>=20
> - By late September, we emit a Last Call on this set of recommendations,
> if we deem that we have a reasonable consensus for the proposals
>=20
> - By late October, if the IETF community still shows consensus, we will
> declare that we have a decision, and will start executing based on that
> decision.
>=20
> In order to be able to move rapidly when we go into the "execution"
> phase, we may initiate some activities of a "fact-finding" nature - such
> as investigating possible suppliers of services and candidates for the
> positions we envisage filling - before that, but irrevocable decisions
> will await IETF consensus.
>=20
> Please read the attachment - please comment - please THINK.
>=20
> While this in itself should not change the IETF standards process at
> all, support functions are important to the IETF.
>=20
> We need to take the time to get this one right.
>=20
>                     Leslie and Harald.
>=20
>=20
>=20
> --=20
>=20
> -------------------------------------------------------------------
> "Reality:
>         Yours to discover."
>                                    -- ThinkingCat
> Leslie Daigle
> leslie@thinkingcat.com
> -------------------------------------------------------------------
>=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-bounces@ietf.org  Sun Aug 29 21:24:37 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA22175;
	Sun, 29 Aug 2004 21:24:37 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C1awB-0005E3-HH; Sun, 29 Aug 2004 21:26:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C1ard-0002kB-WC; Sun, 29 Aug 2004 21:21:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C1aqv-0002ft-O4
	for ietf@megatron.ietf.org; Sun, 29 Aug 2004 21:20:57 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA21999
	for <ietf@ietf.org>; Sun, 29 Aug 2004 21:20:55 -0400 (EDT)
Received: from mail1.lge.co.kr ([156.147.1.151])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C1asX-00058i-UN
	for ietf@ietf.org; Sun, 29 Aug 2004 21:22:41 -0400
Received: from [150.150.59.163] (youngae@lge.com) by 
	mail1.lge.co.kr (Terrace MailWatcher) 
	with ESMTP id 2004083010:19:58:416704.26271.2262
	for <ietf@ietf.org>; Mon, 30 Aug 2004 10:19:58 +0900 (KST) 
Message-ID: <011101c48e2f$60764fb0$a33b9696@lg>
From: "Youngae Kim" <youngae@lge.com>
To: <ietf@ietf.org>
Date: Mon, 30 Aug 2004 10:19:20 +0900
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-TERRACE-SPAMRATE: Spacelee says NOT YET spam-rated. 
X-Spam-Score: 2.2 (++)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Subject: Fw: Welcome to the "Ietf" mailing list (Digest mode)
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="===============1379445120=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 2.2 (++)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88

--===============1379445120==
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: base64

DQotLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIA0KRnJvbTogPGlldGYtYm91bmNlc0BpZXRm
Lm9yZz4NClRvOiA8eW91bmdhZUBsZ2UuY29tPg0KU2VudDogTW9uZGF5LCBBdWd1c3QgMzAsIDIw
MDQgMTA6MTUgQU0NClN1YmplY3Q6IFdlbGNvbWUgdG8gdGhlICJJZXRmIiBtYWlsaW5nIGxpc3Qg
KERpZ2VzdCBtb2RlKQ0KDQoNCj4gV2VsY29tZSB0byB0aGUgSWV0ZkBpZXRmLm9yZyBtYWlsaW5n
IGxpc3QhDQo+IA0KPiBUbyBwb3N0IHRvIHRoaXMgbGlzdCwgc2VuZCB5b3VyIGVtYWlsIHRvOg0K
PiANCj4gICBpZXRmQGlldGYub3JnDQo+IA0KPiBHZW5lcmFsIGluZm9ybWF0aW9uIGFib3V0IHRo
ZSBtYWlsaW5nIGxpc3QgaXMgYXQ6DQo+IA0KPiAgIGh0dHBzOi8vd3d3MS5pZXRmLm9yZy9tYWls
bWFuL2xpc3RpbmZvL2lldGYNCj4gDQo+ICoqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioNCj4gDQo+ICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgTm90ZSBXZWxsDQo+IA0KPiBBbnkgc3VibWlzc2lvbiB0byB0
aGUgSUVURiBpbnRlbmRlZCBieSB0aGUgQ29udHJpYnV0b3IgZm9yIHB1YmxpY2F0aW9uDQo+IGFz
IGFsbCBvciBwYXJ0IG9mIGFuIElFVEYgSW50ZXJuZXQtRHJhZnQgb3IgUkZDIGFuZCBhbnkgc3Rh
dGVtZW50IG1hZGUNCj4gd2l0aGluIHRoZSBjb250ZXh0IG9mIGFuIElFVEYgYWN0aXZpdHkgaXMg
Y29uc2lkZXJlZCBhbiAiSUVURg0KPiBDb250cmlidXRpb24iLiBTdWNoIHN0YXRlbWVudHMgaW5j
bHVkZSBvcmFsIHN0YXRlbWVudHMgaW4gSUVURg0KPiBzZXNzaW9ucywgYXMgd2VsbCBhcyB3cml0
dGVuIGFuZCBlbGVjdHJvbmljIGNvbW11bmljYXRpb25zIG1hZGUgYXQgYW55DQo+IHRpbWUgb3Ig
cGxhY2UsIHdoaWNoIGFyZSBhZGRyZXNzZWQgdG86DQo+IA0KPiAgICAgICAqIHRoZSBJRVRGIHBs
ZW5hcnkgc2Vzc2lvbiwNCj4gICAgICAgKiBhbnkgSUVURiB3b3JraW5nIGdyb3VwIG9yIHBvcnRp
b24gdGhlcmVvZiwNCj4gICAgICAgKiB0aGUgSUVTRywgb3IgYW55IG1lbWJlciB0aGVyZW9mIG9u
IGJlaGFsZiBvZiB0aGUgSUVTRywNCj4gICAgICAgKiB0aGUgSUFCIG9yIGFueSBtZW1iZXIgdGhl
cmVvZiBvbiBiZWhhbGYgb2YgdGhlIElBQiwNCj4gICAgICAgKiBhbnkgSUVURiBtYWlsaW5nIGxp
c3QsIGluY2x1ZGluZyB0aGUgSUVURiBsaXN0IGl0c2VsZiwgYW55IA0KPiAgICAgICAgIHdvcmtp
bmcgZ3JvdXAgb3IgZGVzaWduIHRlYW0gbGlzdCwgb3IgYW55IG90aGVyIGxpc3QNCj4gICAgICAg
ICBmdW5jdGlvbmluZyB1bmRlciBJRVRGIGF1c3BpY2VzLA0KPiAgICAgICAqIHRoZSBSRkMgRWRp
dG9yIG9yIHRoZSBJbnRlcm5ldC1EcmFmdHMgZnVuY3Rpb24NCj4gDQo+IEFsbCBJRVRGIENvbnRy
aWJ1dGlvbnMgYXJlIHN1YmplY3QgdG8gdGhlIHJ1bGVzIG9mIFJGQyAzNjY3IGFuZCBSRkMNCj4g
MzY2OC4NCj4gDQo+IFN0YXRlbWVudHMgbWFkZSBvdXRzaWRlIG9mIGFuIElFVEYgc2Vzc2lvbiwg
bWFpbGluZyBsaXN0IG9yIG90aGVyDQo+IGZ1bmN0aW9uLCB0aGF0IGFyZSBjbGVhcmx5IG5vdCBp
bnRlbmRlZCB0byBiZSBpbnB1dCB0byBhbiBJRVRGDQo+IGFjdGl2aXR5LCBncm91cCBvciBmdW5j
dGlvbiwgYXJlIG5vdCBJRVRGIENvbnRyaWJ1dGlvbnMgaW4gdGhlIGNvbnRleHQNCj4gb2YgdGhp
cyBub3RpY2UuDQo+IA0KPiBQbGVhc2UgY29uc3VsdCBSRkMgMzY2NyBmb3IgZGV0YWlscy4NCj4g
DQo+ICoqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioNCj4gDQo+IA0KPiBJZiB5b3UgZXZlciB3YW50IHRv
IHVuc3Vic2NyaWJlIG9yIGNoYW5nZSB5b3VyIG9wdGlvbnMgKGVnLCBzd2l0Y2ggdG8NCj4gb3Ig
ZnJvbSBkaWdlc3QgbW9kZSwgY2hhbmdlIHlvdXIgcGFzc3dvcmQsIGV0Yy4pLCB2aXNpdCB5b3Vy
DQo+IHN1YnNjcmlwdGlvbiBwYWdlIGF0Og0KPiANCj4gICBodHRwczovL3d3dzEuaWV0Zi5vcmcv
bWFpbG1hbi9vcHRpb25zL2lldGYveW91bmdhZSU0MGxnZS5jb20NCj4gDQo+IFlvdSBjYW4gYWxz
byBtYWtlIHN1Y2ggYWRqdXN0bWVudHMgdmlhIGVtYWlsIGJ5IHNlbmRpbmcgYSBtZXNzYWdlIHRv
Og0KPiANCj4gICBJZXRmLXJlcXVlc3RAaWV0Zi5vcmcNCj4gDQo+IHdpdGggdGhlIHdvcmQgYGhl
bHAnIGluIHRoZSBzdWJqZWN0IG9yIGJvZHkgKGRvbid0IGluY2x1ZGUgdGhlDQo+IHF1b3Rlcyks
IGFuZCB5b3Ugd2lsbCBnZXQgYmFjayBhIG1lc3NhZ2Ugd2l0aCBpbnN0cnVjdGlvbnMuDQo+IA0K
PiBZb3UgbXVzdCBrbm93IHlvdXIgcGFzc3dvcmQgdG8gY2hhbmdlIHlvdXIgb3B0aW9ucyAoaW5j
bHVkaW5nIGNoYW5naW5nDQo+IHRoZSBwYXNzd29yZCwgaXRzZWxmKSBvciB0byB1bnN1YnNjcmli
ZS4gIEl0IGlzOg0KPiANCj4gICB1YndlZHUNCj4gDQo+IE5vcm1hbGx5LCBNYWlsbWFuIHdpbGwg
cmVtaW5kIHlvdSBvZiB5b3VyIGlldGYub3JnIG1haWxpbmcgbGlzdA0KPiBwYXNzd29yZHMgb25j
ZSBldmVyeSBtb250aCwgYWx0aG91Z2ggeW91IGNhbiBkaXNhYmxlIHRoaXMgaWYgeW91DQo+IHBy
ZWZlci4gIFRoaXMgcmVtaW5kZXIgd2lsbCBhbHNvIGluY2x1ZGUgaW5zdHJ1Y3Rpb25zIG9uIGhv
dyB0bw0KPiB1bnN1YnNjcmliZSBvciBjaGFuZ2UgeW91ciBhY2NvdW50IG9wdGlvbnMuICBUaGVy
ZSBpcyBhbHNvIGEgYnV0dG9uIG9uDQo+IHlvdXIgb3B0aW9ucyBwYWdlIHRoYXQgd2lsbCBlbWFp
bCB5b3VyIGN1cnJlbnQgcGFzc3dvcmQgdG8geW91Lg0KPiANCj4gDQo+IA==




--===============1379445120==
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

--===============1379445120==--


From ietf-bounces@ietf.org  Mon Aug 30 03:40:36 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA27882;
	Mon, 30 Aug 2004 03:40:36 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C1go5-0004OJ-GD; Mon, 30 Aug 2004 03:42:25 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C1gjW-0006Ud-Dd; Mon, 30 Aug 2004 03:37:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C1ggD-0006AS-5S
	for ietf@megatron.ietf.org; Mon, 30 Aug 2004 03:34:18 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA27564
	for <ietf@ietf.org>; Mon, 30 Aug 2004 03:34:15 -0400 (EDT)
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C1ghw-0004HV-13
	for ietf@ietf.org; Mon, 30 Aug 2004 03:36:04 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id CA32B61AD5; Mon, 30 Aug 2004 09:33:44 +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 32699-09; Mon, 30 Aug 2004 09:33:42 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain
	[127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP
	id 9969761B89; Mon, 30 Aug 2004 09:33:41 +0200 (CEST)
Date: Mon, 30 Aug 2004 09:29:27 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>, ietf@ietf.org
Message-ID: <0F699F3B4E3B87D97564FB33@B50854F0A9192E8EC6CDA126>
In-Reply-To: <00a301c48e04$dcac4fb0$3220dfa9@consulintel.es>
References: <412D268D.3020402@thinkingcat.com>
	<00a301c48e04$dcac4fb0$3220dfa9@consulintel.es>
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Content-Transfer-Encoding: 7bit
Subject: Venue selection (Re: Options for IETF administrative restructuring)
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-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Content-Transfer-Encoding: 7bit

Thanks for your comments, Jordi!

I'm replying to part of your note, and changing the subject line to get 
different topics on different threads..... I do think we need some kind of 
IETF consensus on the criteria for venue selection - and once we have that 
documented consensus, we need to evaluate how well we follow them...

This is not trivial, nor is it easy to get everything in line; for 
instance, one of our requirements is fairly large (and expensive) offsite 
Internet bandwidth; one potential US site was able to deliver that 
bandwidth as part of the conference package - BUT insisted that it be able 
to perform its usual packet filtering on the traffic, and refused to allow 
alternate bandwidth provisioning on site.

Not something we expected five years ago. Foretec declined the offer - 
wisely, in my opinion.

The subject of continent selection is, BTW, one of the real touchy ones; my 
statistics show that in the North American contingent, the attendance is 
cut in half when we meet outside North America; in the Asian contingent, 
the attendance from the host country quadruples or more when we meet in 
their country, while Europeans show more steady attendance statistics.

Fred Baker formulated a principle of IETF meeting placement as "if you 
contribute to the IETF, the IETF sometimes holds a meeting near you". 
Measuring contribution is a difficult thing - it's certainly not the same 
as attendance! - but I think the principle is not unreasonable.

And after having picked a continent, we need to pick a venue - which can 
depend on the wishes of the sponsor, cost of doing business, availability 
of reasonable venues (I have been told by Foretec that the sensible 
Vancouver venues are booked solid on the dates we want for the next 2 
years, for instance). And that sometimes interferes with the selection of 
continent - for a while, I was told that Foretec was looking at Europe in 
spring 2005; now I'm told it's looking at summer 2005 - because venues 
worked better for August.

I think the organizer needs to be able to make these tradeoffs in real 
time, and without going back to the IETF for a consensus process on 
individual meetings - but we do need to have our criteria right out in the 
open.

I would prefer to split the process into two rather independent parts: One 
(open) that sets the criteria, and one (subcontracted) that attempts to 
find sites that fulfil the criteria. Then we can evaluate the result - for 
economics, for venue performance, for sponsor satisfaction (that too 
matters!), and for "fairness".

As to how to achieve all that.... I'm not at all sure.

A long note about a subject that is a small part of the "reorg" issue...... 
hope this makes sense to you!

                       Harald

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


From ietf-bounces@ietf.org  Mon Aug 30 04:51:08 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02493;
	Mon, 30 Aug 2004 04:51:08 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C1huM-00063g-3l; Mon, 30 Aug 2004 04:52:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C1hr3-00014g-HD; Mon, 30 Aug 2004 04:49:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C1hpf-00084N-SN
	for ietf@megatron.ietf.org; Mon, 30 Aug 2004 04:48:07 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02377
	for <ietf@ietf.org>; Mon, 30 Aug 2004 04:48:05 -0400 (EDT)
Received: from mtagate1.de.ibm.com ([195.212.29.150])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C1hrM-00060I-BG
	for ietf@ietf.org; Mon, 30 Aug 2004 04:49:55 -0400
Received: from d12nrmr1607.megacenter.de.ibm.com
	(d12nrmr1607.megacenter.de.ibm.com [9.149.167.49])
	by mtagate1.de.ibm.com (8.12.10/8.12.10) with ESMTP id i7U8lWfQ144780
	for <ietf@ietf.org>; Mon, 30 Aug 2004 08:47:32 GMT
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232])
	by d12nrmr1607.megacenter.de.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id
	i7U8lV0l077670 for <ietf@ietf.org>; Mon, 30 Aug 2004 10:47:32 +0200
Received: from zurich.ibm.com (dyn-9-13-126-72.ge.ch.ibm.com [9.13.126.72])
	by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id KAA67212
	for <ietf@ietf.org>; Mon, 30 Aug 2004 10:47:31 +0200
Message-ID: <4132E99E.90807@zurich.ibm.com>
Date: Mon, 30 Aug 2004 10:47:26 +0200
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.6) Gecko/20040113
X-Accept-Language: en, fr, de
MIME-Version: 1.0
To: ietf@ietf.org
References: <200408261934.PAA00823@ietf.org>
In-Reply-To: <200408261934.PAA00823@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Content-Transfer-Encoding: 7bit
Subject: Re: I-D ACTION:draft-malamud-consultant-report-00.txt
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-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: 7bit

I strongly support the basic proposal to put the IETF's administration
on a sound and well understood basis, with the transparency that
Carl's draft recommends. So I fundamentally support the thrust of
Section 3, Recommendations for Restructuring the Administrative
Framework. I have some doubts whether all the functions described
in Appendix F are really separable, but I regard that as a question
for the future Administrative Director in any case.

As for the major options suggested in Section 4, my preference is
very clearly for Scenario A, with a commitment to progressively
put in place some or all of the mechanisms outlined for Scenario B.
I think that is the best way to make rapid progress.

I simply can't see any need to spend time and money to create
an additional non-profit organization when we have a perfectly
good one in the shape of the ISOC. Scenario C gives us the
benefits of Scenario B plus extra overhead and complexity;
Scenario D gives us even more overhead, no guarantee of the
benefits, and a major risk of funding difficulties.

In the context of scenarios A and B, I have a small substantive
comment on Section 3.1:

>    Evaluation of applicants might consist of a search committee
>    appointed by the IETF Chair.  The committee would conduct an initial
>    review of applications, possibly solicit additional applications, and
>    present a short-list for further consideration.  This short list of
>    applicants could be reviewed by the IESG and IAB, possibly with
>    further interviews.  The IESG and/or IAB should specify this
>    procedure more fully before beginning the search.

If the Admin Director is to be legally an ISOC employee, the
ISOC CEO would also need to be included in the procedure.

Finally, a reminder that I've served on the IAB and on the ISOC Board,
and contributed to RFC 3716, all of which may have coloured my opinions.

    Brian Carpenter

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


From ietf-bounces@ietf.org  Mon Aug 30 05:04:01 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03361;
	Mon, 30 Aug 2004 05:04:01 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C1i6p-0006PX-IW; Mon, 30 Aug 2004 05:05:51 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C1i0z-0003rk-Iq; Mon, 30 Aug 2004 04:59:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C1hzh-0003c5-8s
	for ietf@megatron.ietf.org; Mon, 30 Aug 2004 04:58:29 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02994
	for <ietf@ietf.org>; Mon, 30 Aug 2004 04:58:26 -0400 (EDT)
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C1i1Q-0006FR-SP
	for ietf@ietf.org; Mon, 30 Aug 2004 05:00:17 -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 i7U90OJZ009882;
	Mon, 30 Aug 2004 11:00:24 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <0F699F3B4E3B87D97564FB33@B50854F0A9192E8EC6CDA126>
References: <412D268D.3020402@thinkingcat.com>
	<00a301c48e04$dcac4fb0$3220dfa9@consulintel.es>
	<0F699F3B4E3B87D97564FB33@B50854F0A9192E8EC6CDA126>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <BA6FFF85-FA62-11D8-9464-000A95CD987A@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Mon, 30 Aug 2004 10:58:14 +0200
To: Harald Tveit Alvestrand <harald@alvestrand.no>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: Venue selection (Re: Options for IETF administrative
	restructuring)
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-Score: 0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Content-Transfer-Encoding: 7bit

On 30-aug-04, at 9:29, Harald Tveit Alvestrand wrote:

> The subject of continent selection is, BTW, one of the real touchy 
> ones; my statistics show that in the North American contingent, the 
> attendance is cut in half when we meet outside North America; in the 
> Asian contingent, the attendance from the host country quadruples or 
> more when we meet in their country, while Europeans show more steady 
> attendance statistics.

Are you sure about this? The number of attendees in Vienna was a bit 
higher than in Minneapolis last year. I also ran into a much larger 
contingent of fellow countrymen in Vienna. (Don't look too far in the 
past as you can't compare the 2000+ attendees of a few years ago with 
the 1500- ones now, I'd assume the people who still come are more 
loyal.)

Also, it's not just about the continent. I find the US somewhat 
visitor-unfriendly in places like Minneapolis, and very much so on the 
international airports of larger cities. I would very much like to see 
a meeting in North America but outside the US.

> I think the organizer needs to be able to make these tradeoffs in real 
> time, and without going back to the IETF for a consensus process on 
> individual meetings - but we do need to have our criteria right out in 
> the open.

> I would prefer to split the process into two rather independent parts: 
> One (open) that sets the criteria, and one (subcontracted) that 
> attempts to find sites that fulfil the criteria. Then we can evaluate 
> the result - for economics, for venue performance, for sponsor 
> satisfaction (that too matters!), and for "fairness".

> As to how to achieve all that.... I'm not at all sure.

Speaking as someone who has to pay for going to IETF meetings out of 
his own pocket and as someone who has been trying to muster up some 
enthusiasm to host a meeting, I'm not all that happy about the way 
things are going now. I'll concentrate on the second role for now.

First of all, I'm not surprised it has been getting harder to find 
sponsors. There are two main reasons for that: the duties of the 
sponsor are solely defined by what's convenient for the people who 
organize the meetings on behalf of the IETF (I'm assuming Foretec and 
the secretariat but I can't be sure). This means the prospective host 
is left with a plethora of duties, some of which are easily solved with 
money (which some sponsors have), others with manpower (which some 
sponsors have) and others with some very specific knowledge (which some 
sponsors have). However, few sponsors are going to have all three.

Also, the process is completely un-transparent both from the view of 
the attendee and from the view of the would-be host.

Last but not least, the people who handle this on the IETF side really 
don't seem to care. For instance, for the past year I've been trying to 
get an answer to the following questions:

> Can you provide me with the current numbers that are relevant to 
> hosting the terminal room (and the social event) for an IETF meeting? 
> And which are the upcoming meetings for which there is no location 
> determined yet?

(Ok, I've only sent four or so messages, but still.) All of this makes 
it hard to create enthusiasm within prospective host organizations.

I think it's essential to start publishing the following information on 
a regular basis:

- meeting status: decided, under consideration, open
- date specific constraints, such as the continent that has been 
selected
- up to date numbers for hotel rooms, meeting rooms, terminal room and 
so on


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


From ietf-bounces@ietf.org  Mon Aug 30 05:11:57 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03862;
	Mon, 30 Aug 2004 05:11:57 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C1iEV-0006bv-Vp; Mon, 30 Aug 2004 05:13:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C1iAm-0004z4-MT; Mon, 30 Aug 2004 05:09:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C1i7V-0004gZ-10
	for ietf@megatron.ietf.org; Mon, 30 Aug 2004 05:06:33 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03513
	for <ietf@ietf.org>; Mon, 30 Aug 2004 05:06:30 -0400 (EDT)
Received: from sklave3.rackland.de ([213.133.101.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C1i9E-0006Tl-OC
	for ietf@ietf.org; Mon, 30 Aug 2004 05:08:21 -0400
Received: (from hadmut@localhost)
	by sklave3.rackland.de (8.12.10/8.12.10/Debian-1) id i7U96SQk023999;
	Mon, 30 Aug 2004 11:06:28 +0200
From: Hadmut Danisch <hadmut@danisch.de>
Date: Mon, 30 Aug 2004 11:06:28 +0200
To: ietf@ietf.org
Message-ID: <20040830090627.GA22982@danisch.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.6i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Subject: How IETF treats contributors
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-Score: 0.0 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8

Hi.

If I understood the IETF correctly, it is an organization based 
on the work of volunteers and their contributions. Correct me, if 
I'm wrong.

I'd like to question the way IETF treats it's contributors.


Some time ago I've written a proposal about how to prevent 
forged e-mails in order to fight spam and published it as an 
I-D (RMX). This was also the first posting ever to the IRTF's 
ASRG mailing list and subject of discussion for months. 

Within this discussion another proposal (SPF) was raised, 
explicitely introduced as based on RMX and intended to cover it. 
Some time later, Microsoft published it's CallerID proposal, again 
influenced by RMX. 

The IETF founded the MARID working group which solely focussed on 
those mailer authorization records in DNS (MARID is exactly that
acronym). 

MARID produced a new proposal called SenderID, which was introduced
as a melt of SPF and CallerID. Actually, some properties
characteristic for CallerID and newer versions of SPF have been
omitted, thus the SenderID core draft does not significantly
differ from RMX and the results of discussions about RMX. SenderID 
is mostly taken from RMX.

Is that bad? No. Contributing to IETF means feeding for derivative
work. Developing network protocols means necessarily cooperation and 
evolution, and that's impossible without derivative work. After all,
why should someone submit an I-D, if not to get other people's
comments and to invite other's for derivative work. If someone
derivates his work from your's, then this is a validation that your 
work was usable and interesting, and that someone actually read your 
paper. So there's nothing wrong about derivative work per se, and
that's an essential part of the way, the IETF works (at least in my
eyes, correct me if I'm wrong).

But in my opinion, the least a contributor can expect is that
derivative work based on his contribution does acknowledge and cite 
the contribution correctly and does not pass the contribution as
someone else's work. Correct me if I'm wrong.

The SenderID core draft does not cite RMX adequatly.
I have asked the MARID and ASRG chairs that RMX is cited correctly 
when turning the SenderID draft into an RFC. They denied. It's a
commercial Microsoft and Pobox show.

While on one hand the chairs do more or less acknowledge or at least
not deny, that SenderID is based on and close to RMX, they do on the
other hand refuse to cite RMX properly. As a reason they give, that
IETF is under US law, and under US law the copyright protects only
against literal plagiarisms, i.e. cut-and-paste, but not against
paraphrased derivatives. Since I had therefore no legal copyright
claims against SenderID, I will not be cited, as I was told.

I am not that experienced with US laws yet, but I can hardly imagine
that this is correct. If this was correct, I could easily republish any
book under my name just by paraphrasing it's contents. I bet I'd be in
trouble if I tried to do so. 

But forget legal issues for a moment, these are to be discussed
elsewhere. I'd like to ask you for your personal opinion, not your 
legal knowledge or appraisal:


Is that the way IETF treats it's contributors? 
Is that considered as fair and honest?


regards
Hadmut Danisch









 

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


From ietf-bounces@ietf.org  Mon Aug 30 06:43:05 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10738;
	Mon, 30 Aug 2004 06:43:05 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C1jei-0000Lc-J0; Mon, 30 Aug 2004 06:44:56 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C1jVs-0006h4-1j; Mon, 30 Aug 2004 06:35:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C1jR3-00069U-T9
	for ietf@megatron.ietf.org; Mon, 30 Aug 2004 06:30:49 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09176
	for <ietf@ietf.org>; Mon, 30 Aug 2004 06:30:47 -0400 (EDT)
Received: from mail.consulintel.es ([213.172.48.142] helo=consulintel.es)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C1jSo-0008P3-7h
	for ietf@ietf.org; Mon, 30 Aug 2004 06:32:38 -0400
Received: from consulintel02 by consulintel.es (MDaemon.PRO.v7.1.2.R)
	with ESMTP id md50000369724.msg
	for <ietf@ietf.org>; Mon, 30 Aug 2004 12:34:09 +0200
Message-ID: <0ad601c48e7c$5554b480$3220dfa9@consulintel.es>
From: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
References: <412D268D.3020402@thinkingcat.com><00a301c48e04$dcac4fb0$3220dfa9@consulintel.es>
	<0F699F3B4E3B87D97564FB33@B50854F0A9192E8EC6CDA126>
Date: Mon, 30 Aug 2004 22:30:09 +1200
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.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Spam-Processed: consulintel.es, Mon, 30 Aug 2004 12:34:09 +0200
	(not processed: message from valid local sender)
X-MDRemoteIP: 169.223.32.50
X-Return-Path: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
X-MDAV-Processed: consulintel.es, Mon, 30 Aug 2004 12:34:10 +0200
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 093efd19b5f651b2707595638f6c4003
Content-Transfer-Encoding: quoted-printable
Subject: Re: Venue selection (Re: Options for IETF administrative
	restructuring)
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-Score: 0.0 (/)
X-Scan-Signature: 2beba50d0fcdeee5f091c59f204d4365
Content-Transfer-Encoding: quoted-printable

Hi Harald,

See my comments below, in-line.

Regards,
Jordi

---- Original Message ----
From: "Harald Tveit Alvestrand" <harald@alvestrand.no>
To: "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>; <ietf@ietf.org>
Sent: Monday, August 30, 2004 7:29 PM
Subject: Venue selection (Re: Options for IETF administrative restructuring)

> Thanks for your comments, Jordi!
>=20
> I'm replying to part of your note, and changing the subject line to get
> different topics on different threads..... I do think we need some kind of
> IETF consensus on the criteria for venue selection - and once we have that
> documented consensus, we need to evaluate how well we follow them...
>=20
> This is not trivial, nor is it easy to get everything in line; for
> instance, one of our requirements is fairly large (and expensive) offsite
> Internet bandwidth; one potential US site was able to deliver that
> bandwidth as part of the conference package - BUT insisted that it be able
> to perform its usual packet filtering on the traffic, and refused to allow
> alternate bandwidth provisioning on site.

Clearly we should not accept that site ;-)

>=20
> Not something we expected five years ago. Foretec declined the offer -
> wisely, in my opinion.
>=20
> The subject of continent selection is, BTW, one of the real touchy ones;
> my statistics show that in the North American contingent, the attendance
> is cut in half when we meet outside North America; in the Asian
> contingent, the attendance from the host country quadruples or more when
> we meet in their country, while Europeans show more steady attendance
> statistics.=20

I'm not sure that's correct, but probably you have the right figures ;-)

But the point probably is not if the figures show that you're right or not ... The point is to be fair with the participants, independently from where they come.

Why participants from continent X have less possibilities to attend IETF ? Why they should spend more money to attend the IETF meetings in comparison with participants from continent Y ?

Are we considering in the meeting cost, the extra (or lower) cost that organizing the meeting in place A or place B means for the attendees ?

And being clear, is time may be for the Asian to have more IETFs there, and what about Latin America, or even Europe ? We should now start balancing and having more IETFs there and less in NA !

Is the IETF a competition in the number of attendees from continent A or B or C ?

Just food for though ...

>=20
> Fred Baker formulated a principle of IETF meeting placement as "if you
> contribute to the IETF, the IETF sometimes holds a meeting near you".
> Measuring contribution is a difficult thing - it's certainly not the same
> as attendance! - but I think the principle is not unreasonable.

I also thought this could be reasonable, but after years attending, I don't think anymore this is correct, neither fair. Probably on the other way around. I feel that holding meetings where there is less contribution, can help to increase it.

In any case, the issue comes back to the original point: We need a clear definition about what are the requirements. San Diego didn't meet the "requirements" (those that we feel, because aren't clearly written anywhere), and it was not that bad, so probably those requirements are wrong.

We also need to ask what is the reason for attending, and if that reason is in the benefit of the IETF process, or on the other way around. How much cost have attendees not actually participating ? Or may be in the other way around, they finance the meeting for those that contribute ?

>=20
> And after having picked a continent, we need to pick a venue - which can
> depend on the wishes of the sponsor, cost of doing business, availability
> of reasonable venues (I have been told by Foretec that the sensible
> Vancouver venues are booked solid on the dates we want for the next 2
> years, for instance). And that sometimes interferes with the selection of
> continent - for a while, I was told that Foretec was looking at Europe in
> spring 2005; now I'm told it's looking at summer 2005 - because venues
> worked better for August.

I know about this very well, I need to book one year in advance, at least, and is my own city ... But I can tell you also that this is part of the miss-planning. I offered during 3 years ... and the venue was visited only in Summer 2003. We had good chances at that time to block the venue for end of 2004 or spring/summer 2005, but the decision didn't come !

>=20
> I think the organizer needs to be able to make these tradeoffs in real
> time, and without going back to the IETF for a consensus process on
> individual meetings - but we do need to have our criteria right out in the
> open.

Exactly. Let's start working on it ? Do we need an I-D ?

We can start with the known issues and keep adding what we believe is not working, or wrong or whatever. We should have this clear by the next meeting. The plenary is a good place to present this and get the last feedback and go for the last call ;-)

>=20
> I would prefer to split the process into two rather independent parts: One
> (open) that sets the criteria, and one (subcontracted) that attempts to
> find sites that fulfil the criteria. Then we can evaluate the result - for
> economics, for venue performance, for sponsor satisfaction (that too
> matters!), and for "fairness".

Agree, but if we don't have the criteria, then is difficult.

Anyway, the subcontracting cost money, and is subjected to persons, so this means that could always be (perceived) as a subjective applications of the criteria (once agreed), and that means that it need to be also open and subjected to feedback. This is actually probably the most difficult part, but should be part of the process.

>=20
> As to how to achieve all that.... I'm not at all sure.
>=20
> A long note about a subject that is a small part of the "reorg"
> issue...... hope this makes sense to you!

A lot of sense if we start with the I-D !

>=20
>                        Harald
>=20
> _______________________________________________
> 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


From ietf-bounces@ietf.org  Mon Aug 30 07:26:00 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13310;
	Mon, 30 Aug 2004 07:26:00 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C1kKE-0001Ee-Sd; Mon, 30 Aug 2004 07:27:51 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C1kH5-0003xa-LG; Mon, 30 Aug 2004 07:24:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C1kG3-0003hM-5m
	for ietf@megatron.ietf.org; Mon, 30 Aug 2004 07:23:31 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13202
	for <ietf@ietf.org>; Mon, 30 Aug 2004 07:23:30 -0400 (EDT)
Received: from smtp.nildram.co.uk ([195.112.4.54])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C1kHo-0001Bd-3w
	for ietf@ietf.org; Mon, 30 Aug 2004 07:25:20 -0400
Received: from pcgz600re (foxcombe.gotadsl.co.uk [81.6.215.107])
	by smtp.nildram.co.uk (Postfix) with ESMTP
	id 4F6AA25EBA0; Mon, 30 Aug 2004 12:23:25 +0100 (BST)
From: "Christian de Larrinaga" <cdel@firsthand.net>
To: "Leslie Daigle" <leslie@thinkingcat.com>, <ietf@ietf.org>
Date: Mon, 30 Aug 2004 12:26:15 +0100
Message-ID: <OLEPILDGDKGAPONGCBEOOEGICHAA.cdel@firsthand.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <412D268D.3020402@thinkingcat.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Importance: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36b1f8810cb91289d885dc8ab4fc8172
Content-Transfer-Encoding: 7bit
Cc: Harald Tveit Alvestrand <harald@alvestrand.no>
Subject: RE: Options for IETF administrative restructuring
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-Score: 0.0 (/)
X-Scan-Signature: 87a3f533bb300b99e2a18357f3c1563d
Content-Transfer-Encoding: 7bit

Firstly congratulations to all those involved in compiling this work.

I have three questions before being able to comment in more detail.

1/ Has a decision been made not to sub contract out (under formal
agreements) the tasks currently being managed fairly informally by
Foretec/CNRI to professional adminstration organisations?

2/ What funding requirement is expected from ISOC and ISOC members to manage
the IETF functions outlined?

3/ Do we have an analysis of the policy implications in bringing
responsibility for the administration of Internet Standards negotiation into
the same body that is responsible for their oversight (via appointment of
IAB and Trustee appeal role)?


Christian

Christian de Larrinaga

------------------------------------------------------------------
Deploying Internet services?
You need to participate in the UK IPv6 Deployment Conference
Manchester September 24th 2004
www.uk.ipv6tf.org
alongside RIPE  49, 21st to 24th Sept 2004
------------------------------------------------------------------




-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org]On Behalf Of
Leslie Daigle
Sent: 26 August 2004 00:54
To: ietf@ietf.org
Cc: Harald Tveit Alvestrand
Subject: Options for IETF administrative restructuring




Hello, IETF community.

Attached is the document we promised you in San Diego - a report from
our consultant, Carl Malamud, which lays out a series of options and
recommendations for moving forward with the IETF administrative
restructuring process, according to the recommendations laid out
in RFC3716 (the Advisory Committee report).  It has been submitted
to the Internet Drafts repository and should be showing up there
shortly.


Some important things to note:

THIS IS NOT A DOCUMENT TO BE READ IN ISOLATION.
Minimally, reviewing the Advisory Committee report (RFC3716) is
necessary to understand the context of the proposals laid out in
this draft.

THIS IS NOT YET AN IETF DECISION.
That will be taken later, based on your input and IETF rough consensus.

THIS IS NOT THE IESG/IAB's RECOMMENDATION.
Our recommendation will come later, based on your input and the
evolution of our thinking.

THIS IS NOT AN ISOC POSITION.
The document describes potential relationships of the IETF
administrative activity and ISOC.  However, the document is written
as a proposal for IETF discussion -- the ISOC Board has not been asked
to formulate a position on supporting one or any of these proposals; we
need to have that discussion as it becomes clearer what the IETF wants
in its future.


This IS, however, the culmination of many, many hours of information
gathering and a near-infinite number of conversations by Carl Malamud,
attempting to give the best basis on which the IETF could make a
decision that he could within the timeframe given.

We encourage all interested IETF participants to read the report most
carefully, and give feedback on it - on the IETF list for public
discussion, directly to Carl or the IETF and IAB chairs if you want to
make off-list comments.

FURTHER STEPS

The next steps in this process depend on the community feedback and
whether we can gauge a consensus of the IETF on this mailing list. What
we think is reasonable so far is:

- Have a public discussion on the IETF list on the options presented in
the draft

- By early September, the IESG and IAB will attempt to distill a set of
recommendations that we think capture a reasonable consensus of the
community, and publish this as an internet-draft, which will be revised
over the next month, possibly several times, based on further
discussions

- By late September, we emit a Last Call on this set of recommendations,
if we deem that we have a reasonable consensus for the proposals

- By late October, if the IETF community still shows consensus, we will
declare that we have a decision, and will start executing based on that
decision.

In order to be able to move rapidly when we go into the "execution"
phase, we may initiate some activities of a "fact-finding" nature - such
as investigating possible suppliers of services and candidates for the
positions we envisage filling - before that, but irrevocable decisions
will await IETF consensus.

Please read the attachment - please comment - please THINK.

While this in itself should not change the IETF standards process at
all, support functions are important to the IETF.

We need to take the time to get this one right.

                    Leslie and Harald.



--

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





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


From ietf-bounces@ietf.org  Mon Aug 30 13:08:33 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09231;
	Mon, 30 Aug 2004 13:08:33 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C1pfp-0000KE-8n; Mon, 30 Aug 2004 13:10:29 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C1pTH-0007YU-9H; Mon, 30 Aug 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 1C1pOV-0006kv-My
	for ietf@megatron.ietf.org; Mon, 30 Aug 2004 12:52:36 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07991
	for <ietf@ietf.org>; Mon, 30 Aug 2004 12:52:32 -0400 (EDT)
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C1pQI-0008Qz-MH
	for ietf@ietf.org; Mon, 30 Aug 2004 12:54:28 -0400
Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148])
	by numenor.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id
	i7UGpv1i024271
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 30 Aug 2004 09:51:58 -0700 (PDT)
Received: from [129.46.227.161] (carbuncle.qualcomm.com [129.46.227.161])
	by magus.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id i7UGptRE007397;
	Mon, 30 Aug 2004 09:51:56 -0700 (PDT)
Mime-Version: 1.0
X-Sender: hardie@mage.qualcomm.com
Message-Id: <p06110403bd5906118d89@[129.46.227.161]>
In-Reply-To: <20040830090627.GA22982@danisch.de>
References: <20040830090627.GA22982@danisch.de>
Date: Mon, 30 Aug 2004 09:51:54 -0700
To: Hadmut Danisch <hadmut@danisch.de>, ietf@ietf.org
From: Ted Hardie <hardie@qualcomm.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Subject: Re: How IETF treats contributors
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-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793

At 11:06 AM +0200 8/30/04, Hadmut Danisch wrote:
><original cut here>
>But in my opinion, the least a contributor can expect is that
>derivative work based on his contribution does acknowledge and cite
>the contribution correctly and does not pass the contribution as
>someone else's work. Correct me if I'm wrong.
>
>The SenderID core draft does not cite RMX adequatly.
>I have asked the MARID and ASRG chairs that RMX is cited correctly
>when turning the SenderID draft into an RFC. They denied. It's a
>commercial Microsoft and Pobox show.

The current MARID core draft contains the following
acknowledgement section:

    9. Acknowledgements

       Variations on the idea of using a DNS record to check the legitimacy
       of an email address have occurred multiple times. The earliest known
       work is [Vixie]; others include [RMX], [SPF] and [CallerID].

       The current document borrows heavily from each of the above, and
       incorporates ideas proposed by many members of the MARID working
      group.  The contributions of each of the above are gratefully
      acknowledged.



RMX was submitted to the IETF as subject to all provisions of section 10
of RFC 2026, which means it allowed the IETF to create derivative works.
It was cited as an input draft to the MARID working group,
and it was recommended for publication as an Experimental RFC with
the other input drafts that came out of the ASRG process.  In other words,
the IETF took you up on your offer to consider the draft seriously and
to use it as input into the evolving standard in this area.  My view
is that the current editors of the working group drafts have done what
they should to cite Paul Vixie, you, and the original SPF and Caller-ID
drafts as antecedents to the current draft.   This draft is an evolution
of a lot of thinking by a lot of people, and many members of the working
group will be acknowledged only implicitly, as is common for many
IETF drafts.  I hope all of the participants understand, though, that
their work is appreciated.  We're all here to make sure that the Internet
runs and develops as best it can; and while acknowledgements are
important, I hope we all see a thriving Internet as our real reward.

			regards,
				Ted Hardie


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


From ietf-bounces@ietf.org  Mon Aug 30 15:28:41 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20301;
	Mon, 30 Aug 2004 15:28:41 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C1rrQ-0003b9-5K; Mon, 30 Aug 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 1C1rjv-0001gI-4b; Mon, 30 Aug 2004 15:22:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C1rg3-0008Ni-6R
	for ietf@megatron.ietf.org; Mon, 30 Aug 2004 15:18:51 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19474
	for <ietf@ietf.org>; Mon, 30 Aug 2004 15:18:49 -0400 (EDT)
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C1rhp-0003MI-IU
	for ietf@ietf.org; Mon, 30 Aug 2004 15:20:44 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id 5EE3813DFF; Mon, 30 Aug 2004 19:18:16 +0000 (GMT)
To: ietf@ietf.org
References: <p06110403bd5906118d89@[129.46.227.161]>
From: Paul Vixie <vixie@vix.com>
Date: 30 Aug 2004 19:18:16 +0000
In-Reply-To: <p06110403bd5906118d89@[129.46.227.161]>
Message-ID: <g3k6vgjuyv.fsf@sa.vix.com>
Lines: 10
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-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Subject: Re: How IETF treats contributors
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-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c

hardie@qualcomm.com (Ted Hardie) writes:

> ... My view is that the current editors of the working group drafts have
> done what they should to cite Paul Vixie, you, and the original SPF and
> Caller-ID drafts as antecedents to the current draft.  ...

for whatever it's worth, i agree.  i've had various complaints about spf,
but citation and credit are not among them.
-- 
Paul Vixie

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


From ietf-bounces@ietf.org  Mon Aug 30 17:09:49 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02061;
	Mon, 30 Aug 2004 17:09:49 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C1tRK-0007vN-Ln; Mon, 30 Aug 2004 17:11:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C1szR-0007Tt-9H; Mon, 30 Aug 2004 16:42:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C1moQ-0001KB-7M
	for ietf@megatron.ietf.org; Mon, 30 Aug 2004 10:07:10 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25589
	for <ietf@ietf.org>; Mon, 30 Aug 2004 10:07:08 -0400 (EDT)
Received: from panoramix.hexago.com ([209.71.226.3])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C1mqC-0004zG-M4
	for ietf@ietf.org; Mon, 30 Aug 2004 10:09:01 -0400
Received: from localhost (retro.viagenie.qc.ca [IPv6:3ffe:b00:c18:3::22])
	(authenticated bits=0)
	by panoramix.hexago.com (8.12.8/8.12.8) with ESMTP id i7UE6RIY008796;
	Mon, 30 Aug 2004 10:06:27 -0400 (EDT)
Date: Mon, 30 Aug 2004 10:06:28 -0400
From: Marc Blanchet <Marc.Blanchet@hexago.com>
To: Hadmut Danisch <hadmut@danisch.de>, ietf@ietf.org
Message-ID: <C573E1A94B25B75B7CB72AFF@classic.viagenie.qc.ca>
In-Reply-To: <20040830090627.GA22982@danisch.de>
References: <20040830090627.GA22982@danisch.de>
X-Mailer: Mulberry/3.1.6 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 30 Aug 2004 16:42:54 -0400
Subject: Re: How IETF treats contributors
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-Score: 0.0 (/)
X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027
Content-Transfer-Encoding: 7bit

welcome to ietf. :-((( It happens to me also and I know others who had the
same issue. It was raised before.

Marc.

-- Monday, August 30, 2004 11:06:28 +0200 Hadmut Danisch
<hadmut@danisch.de> wrote/a ecrit:

> Hi.
> 
> If I understood the IETF correctly, it is an organization based 
> on the work of volunteers and their contributions. Correct me, if 
> I'm wrong.
> 
> I'd like to question the way IETF treats it's contributors.
> 
> 
> Some time ago I've written a proposal about how to prevent 
> forged e-mails in order to fight spam and published it as an 
> I-D (RMX). This was also the first posting ever to the IRTF's 
> ASRG mailing list and subject of discussion for months. 
> 
> Within this discussion another proposal (SPF) was raised, 
> explicitely introduced as based on RMX and intended to cover it. 
> Some time later, Microsoft published it's CallerID proposal, again 
> influenced by RMX. 
> 
> The IETF founded the MARID working group which solely focussed on 
> those mailer authorization records in DNS (MARID is exactly that
> acronym). 
> 
> MARID produced a new proposal called SenderID, which was introduced
> as a melt of SPF and CallerID. Actually, some properties
> characteristic for CallerID and newer versions of SPF have been
> omitted, thus the SenderID core draft does not significantly
> differ from RMX and the results of discussions about RMX. SenderID 
> is mostly taken from RMX.
> 
> Is that bad? No. Contributing to IETF means feeding for derivative
> work. Developing network protocols means necessarily cooperation and 
> evolution, and that's impossible without derivative work. After all,
> why should someone submit an I-D, if not to get other people's
> comments and to invite other's for derivative work. If someone
> derivates his work from your's, then this is a validation that your 
> work was usable and interesting, and that someone actually read your 
> paper. So there's nothing wrong about derivative work per se, and
> that's an essential part of the way, the IETF works (at least in my
> eyes, correct me if I'm wrong).
> 
> But in my opinion, the least a contributor can expect is that
> derivative work based on his contribution does acknowledge and cite 
> the contribution correctly and does not pass the contribution as
> someone else's work. Correct me if I'm wrong.
> 
> The SenderID core draft does not cite RMX adequatly.
> I have asked the MARID and ASRG chairs that RMX is cited correctly 
> when turning the SenderID draft into an RFC. They denied. It's a
> commercial Microsoft and Pobox show.
> 
> While on one hand the chairs do more or less acknowledge or at least
> not deny, that SenderID is based on and close to RMX, they do on the
> other hand refuse to cite RMX properly. As a reason they give, that
> IETF is under US law, and under US law the copyright protects only
> against literal plagiarisms, i.e. cut-and-paste, but not against
> paraphrased derivatives. Since I had therefore no legal copyright
> claims against SenderID, I will not be cited, as I was told.
> 
> I am not that experienced with US laws yet, but I can hardly imagine
> that this is correct. If this was correct, I could easily republish any
> book under my name just by paraphrasing it's contents. I bet I'd be in
> trouble if I tried to do so. 
> 
> But forget legal issues for a moment, these are to be discussed
> elsewhere. I'd like to ask you for your personal opinion, not your 
> legal knowledge or appraisal:
> 
> 
> Is that the way IETF treats it's contributors? 
> Is that considered as fair and honest?
> 
> 
> regards
> Hadmut Danisch
> 
> 
> 
> 
> 
> 
> 
> 
> 
>  
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf



------------------------------------------
Marc Blanchet
Hexago
tel: +1-418-266-5533x225
------------------------------------------
http://www.freenet6.net: IPv6 connectivity
------------------------------------------

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


From ietf-bounces@ietf.org  Mon Aug 30 17:21:06 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04034;
	Mon, 30 Aug 2004 17:21:06 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C1tcF-0008TA-QU; Mon, 30 Aug 2004 17:23:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C1tRZ-0001OO-Vr; Mon, 30 Aug 2004 17:12:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C1t15-0007go-3j
	for ietf@megatron.ietf.org; Mon, 30 Aug 2004 16:44:39 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28653
	for <ietf@ietf.org>; Mon, 30 Aug 2004 16:44:36 -0400 (EDT)
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C1t2s-0006dE-26
	for ietf@ietf.org; Mon, 30 Aug 2004 16:46: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 i7UKhv5x028941
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 30 Aug 2004 16:44:00 -0400
Date: Mon, 30 Aug 2004 16:43:57 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Hadmut Danisch <hadmut@danisch.de>
In-Reply-To: <20040830090627.GA22982@danisch.de>
Message-ID: <Pine.LNX.4.44.0408301607571.28223-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 2.7 (++)
X-Scan-Signature: 87a3f533bb300b99e2a18357f3c1563d
Cc: ietf@ietf.org
Subject: Re: How IETF treats contributors
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-Score: 2.7 (++)
X-Scan-Signature: 29dc808194f5fb921c09d0040806d6eb

Hadmut, 

To be clear, I was among thouse who noted the deficiencies in RMX, and
note practically the same deficiencies in SPF, with the added "feature"
that it allows 2 large ISPs to conspire together to prevent unbundling of
their email and connectivity services in violation of US and European
anti-trust laws.

That said, it is a reprehensible shame that you are not being given credit
for your work in SPF and RMX. It was an original idea, and was clear the
result of a lot of work and a lot of thought.  That it did not obtain its
goals is unfortunate, but many unsuccessful ideas reveal truths that
become the foundations for more successful ideas.  Each wrong turn and
dead-end investigated, even if disappointing, ultimately brings society
progress, and that is good.

It is unfortunate that as a society, we do not find someway to reward the
wrong turns and investigators of dead-ends.  We typically only reward the
successful results, and ignore the huge amount of unsuccessful work it
took to obtain it.  But the least we can to is to __acknowledge__ the work
that was done, and thank those who did it.

In my opinion, it is completely inappropriate that the IETF, an
intellectual, professional organization, does not give credit were credit
is due.  The "glop" you heard from the chairs about copyright infringement
is just glop, in my opinion**.  Credit and attribution is about
__intellectual__honesty__, not about copyright law.

Failure to give credit is intellectually dishonest.  But I suspect there
are other reasons for not wanting to associate with RMX.  We demonstrated
that RMX did not solve the problem it set out to solve. No doubt, the
MARID group chairs do not want to appear to simply re-hash RMX under a
different name. In order to avoid that, they have to pretend it wasn't
written by you.


Dean Anderson
Av8 Internet, Inc

** Judging by book infringement cases in which trivial changes to general
plotline and story events still infringe, they may wrong about the
copyright infringement as well.  You will also have to pay attention to
the copyright agreements and terms that govern your submissions. I suspect
that draft authors may not actually own the copyright to the drafts they
submit. See RFC 3667 and 3668.  But you will need to consult an attorney
versed in US Copyright Law, if you want to go that route.




On Mon, 30 Aug 2004, Hadmut Danisch wrote:

> Hi.
> 
> If I understood the IETF correctly, it is an organization based 
> on the work of volunteers and their contributions. Correct me, if 
> I'm wrong.
> 
> I'd like to question the way IETF treats it's contributors.
> 
> 
> Some time ago I've written a proposal about how to prevent 
> forged e-mails in order to fight spam and published it as an 
> I-D (RMX). This was also the first posting ever to the IRTF's 
> ASRG mailing list and subject of discussion for months. 
> 
> Within this discussion another proposal (SPF) was raised, 
> explicitely introduced as based on RMX and intended to cover it. 
> Some time later, Microsoft published it's CallerID proposal, again 
> influenced by RMX. 
> 
> The IETF founded the MARID working group which solely focussed on 
> those mailer authorization records in DNS (MARID is exactly that
> acronym). 
> 
> MARID produced a new proposal called SenderID, which was introduced
> as a melt of SPF and CallerID. Actually, some properties
> characteristic for CallerID and newer versions of SPF have been
> omitted, thus the SenderID core draft does not significantly
> differ from RMX and the results of discussions about RMX. SenderID 
> is mostly taken from RMX.
> 
> Is that bad? No. Contributing to IETF means feeding for derivative
> work. Developing network protocols means necessarily cooperation and 
> evolution, and that's impossible without derivative work. After all,
> why should someone submit an I-D, if not to get other people's
> comments and to invite other's for derivative work. If someone
> derivates his work from your's, then this is a validation that your 
> work was usable and interesting, and that someone actually read your 
> paper. So there's nothing wrong about derivative work per se, and
> that's an essential part of the way, the IETF works (at least in my
> eyes, correct me if I'm wrong).
> 
> But in my opinion, the least a contributor can expect is that
> derivative work based on his contribution does acknowledge and cite 
> the contribution correctly and does not pass the contribution as
> someone else's work. Correct me if I'm wrong.
> 
> The SenderID core draft does not cite RMX adequatly.
> I have asked the MARID and ASRG chairs that RMX is cited correctly 
> when turning the SenderID draft into an RFC. They denied. It's a
> commercial Microsoft and Pobox show.
> 
> While on one hand the chairs do more or less acknowledge or at least
> not deny, that SenderID is based on and close to RMX, they do on the
> other hand refuse to cite RMX properly. As a reason they give, that
> IETF is under US law, and under US law the copyright protects only
> against literal plagiarisms, i.e. cut-and-paste, but not against
> paraphrased derivatives. Since I had therefore no legal copyright
> claims against SenderID, I will not be cited, as I was told.
> 
> I am not that experienced with US laws yet, but I can hardly imagine
> that this is correct. If this was correct, I could easily republish any
> book under my name just by paraphrasing it's contents. I bet I'd be in
> trouble if I tried to do so. 
> 
> But forget legal issues for a moment, these are to be discussed
> elsewhere. I'd like to ask you for your personal opinion, not your 
> legal knowledge or appraisal:
> 
> 
> Is that the way IETF treats it's contributors? 
> Is that considered as fair and honest?
> 
> 
> regards
> Hadmut Danisch
> 
> 
> 
> 
> 
> 
> 
> 
> 
>  
> 
> _______________________________________________
> 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 Aug 30 17:28:12 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04539;
	Mon, 30 Aug 2004 17:28:12 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C1tj7-0000DE-GJ; Mon, 30 Aug 2004 17:30:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C1tSf-0002LI-MK; Mon, 30 Aug 2004 17:13:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C1tC2-0003F0-SS
	for ietf@megatron.ietf.org; Mon, 30 Aug 2004 16:55:59 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00774
	for <ietf@ietf.org>; Mon, 30 Aug 2004 16:55:55 -0400 (EDT)
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C1tDr-0007NT-Cy
	for ietf@ietf.org; Mon, 30 Aug 2004 16:57: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 i7UKtNnn029219
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 30 Aug 2004 16:55:24 -0400
Date: Mon, 30 Aug 2004 16:55:23 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Ted Hardie <hardie@qualcomm.com>
In-Reply-To: <p06110403bd5906118d89@[129.46.227.161]>
Message-ID: <Pine.LNX.4.44.0408301644050.28223-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 2.7 (++)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Cc: ietf@ietf.org, Hadmut Danisch <hadmut@danisch.de>
Subject: Re: How IETF treats contributors
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-Score: 2.7 (++)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15

On Mon, 30 Aug 2004, Ted Hardie wrote:

 
>        Variations on the idea of using a DNS record to check the legitimacy
>        of an email address have occurred multiple times. The earliest known
>        work is [Vixie]; others include [RMX], [SPF] and [CallerID].

But of course, this is wrong and is, in part, the basis of Hadmut's
complaint.

I've no doubt that Vixie is happy with this (as he reports), having
obtained credit that isn't due to him.  Apparently, no one bothered to
actually read the message attributed to [Vixie], which the draft (wrongly)
claims is the earliest known work:

http://www.ietf.org/internet-drafts/draft-ietf-marid-core-03.txt

http://ops.ietf.org/lists/namedroppers/namedroppers.2002/msg00658.html

The idea came from David Green, and Vixie says it originated from Jim 
Miller in 1998.  Vixie had little or nothing to do with it. Why the draft 
claims the earliest known work is due to Vixie is unclear.

		--Dean

==========================================================================
    * To: namedroppers@ops.ietf.org
    * Subject: Re: Mail-Transmitter RR
    * From: Paul Vixie <paul@vix.com>
    * Date: Sat, 01 Jun 2002 18:16:37 -0700
    * In-reply-to: Message from David Green <green@couchpotato.net> of 
"Sat, 01 Jun 2002 20:49:48 
EDT."<Pine.LNX.4.44.0206012045470.8349-200000@david.couchpotato.net>


> I'm sorry if this is off-topic, but I couldn't find a working group that 
> is working on dealing with spam, so this is the closest match I could 
> find. I know this is in no way related to IPv6 or anything else you guys 
> are working on, but it is an idea I had involving the addition of a RR 
> type. If this is not the right place to be sending this, any pointers to 
> other working groups/forums would be greatly appreciated. And I appreciate 
> all of the hard work you guys are doing... My idea is attached (domauth.txt)

In 1998, Jim Miller suggested this.  A few weeks ago, I wrote the 
following.  Comments are welcome.

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











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


From ietf-bounces@ietf.org  Mon Aug 30 17:37:55 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05532;
	Mon, 30 Aug 2004 17:37:54 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C1tsW-0000VL-AW; Mon, 30 Aug 2004 17:39:52 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C1tYv-0004ND-K5; Mon, 30 Aug 2004 17:19:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C1tQP-0000pD-1C
	for ietf@megatron.ietf.org; Mon, 30 Aug 2004 17:10:49 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02399
	for <ietf@ietf.org>; Mon, 30 Aug 2004 17:10:46 -0400 (EDT)
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C1tSF-0007yY-3e
	for ietf@ietf.org; Mon, 30 Aug 2004 17:12:43 -0400
Received: from crowley.qualcomm.com (crowley.qualcomm.com [129.46.61.151])
	by ithilien.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id
	i7UL9e57026534; Mon, 30 Aug 2004 14:09:40 -0700 (PDT)
Received: from [129.46.227.161] (carbuncle.qualcomm.com [129.46.227.161])
	by crowley.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id
	i7UL9bWk018062; Mon, 30 Aug 2004 14:09:38 -0700 (PDT)
Mime-Version: 1.0
X-Sender: hardie@mage.qualcomm.com
Message-Id: <p0611040bbd59466aa292@[129.46.227.161]>
In-Reply-To: <Pine.LNX.4.44.0408301644050.28223-100000@cirrus.av8.net>
References: <Pine.LNX.4.44.0408301644050.28223-100000@cirrus.av8.net>
Date: Mon, 30 Aug 2004 14:09:36 -0700
To: Dean Anderson <dean@av8.com>
From: Ted Hardie <hardie@qualcomm.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: ietf@ietf.org, Hadmut Danisch <hadmut@danisch.de>
Subject: Re: How IETF treats contributors
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-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44

At 4:55 PM -0400 8/30/04, Dean Anderson wrote:
>
>http://www.ietf.org/internet-drafts/draft-ietf-marid-core-03.txt
>
>http://ops.ietf.org/lists/namedroppers/namedroppers.2002/msg00658.html
>
>The idea came from David Green, and Vixie says it originated from Jim
>Miller in 1998.  Vixie had little or nothing to do with it. Why the draft
>claims the earliest known work is due to Vixie is unclear.
>
>		--Dean

Elided below is the actual draft, "Repudiating Mail From".  The citation
is to the earliest known work (in other words, the earliest place someone
wrote down a solution based on this idea).  If you would like to suggest
to the authors of marid-core that Jim Miller ought to be cited as the source
of the idea from which Vixie's work was derived, I'm sure they will 
consider it.
Paul Vixie should still be cited, of course, as many people worked off of
his formulation of the idea; so should Hadmut Danisch, for the same reason.

The main point to be made, though, is that these are all contributions to
the IETF's collective work on the problem, and should be seen as such.
				regards,
					Ted Hardie





>==========================================================================
>     * To: namedroppers@ops.ietf.org
>     * Subject: Re: Mail-Transmitter RR
>     * From: Paul Vixie <paul@vix.com>
>     * Date: Sat, 01 Jun 2002 18:16:37 -0700
>     * In-reply-to: Message from David Green <green@couchpotato.net> of
>"Sat, 01 Jun 2002 20:49:48
>EDT."<Pine.LNX.4.44.0206012045470.8349-200000@david.couchpotato.net>
>
>
>>  I'm sorry if this is off-topic, but I couldn't find a working group that
>>  is working on dealing with spam, so this is the closest match I could
>>  find. I know this is in no way related to IPv6 or anything else you guys
>>  are working on, but it is an idea I had involving the addition of a RR
>>  type. If this is not the right place to be sending this, any pointers to
>>  other working groups/forums would be greatly appreciated. And I appreciate
>>  all of the hard work you guys are doing... My idea is attached (domauth.txt)
>
>In 1998, Jim Miller suggested this.  A few weeks ago, I wrote the
>following.  Comments are welcome.
>
>==========================================================================


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


From ietf-bounces@ietf.org  Mon Aug 30 17:47:30 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06190;
	Mon, 30 Aug 2004 17:47:30 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C1u1n-0000l0-F8; Mon, 30 Aug 2004 17:49:28 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C1tt8-0002Ec-Tu; Mon, 30 Aug 2004 17:40:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C1tgd-0005t4-9l
	for ietf@megatron.ietf.org; Mon, 30 Aug 2004 17:27:35 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04519
	for <ietf@ietf.org>; Mon, 30 Aug 2004 17:27:32 -0400 (EDT)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C1tiS-0000BE-Ss
	for ietf@ietf.org; Mon, 30 Aug 2004 17:29:30 -0400
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-3.cisco.com with ESMTP; 30 Aug 2004 14:33:49 +0000
X-BrightmailFiltered: true
Received: from mira-sjc5-d.cisco.com (IDENT:mirapoint@mira-sjc5-d.cisco.com
	[171.71.163.28])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i7ULQ0pf027615
	for <ietf@ietf.org>; Mon, 30 Aug 2004 14:26:00 -0700 (PDT)
Received: from [10.32.245.153] (stealth-10-32-245-153.cisco.com
	[10.32.245.153]) by mira-sjc5-d.cisco.com (MOS 3.4.6-GR)
	with SMTP id AEC92535; Mon, 30 Aug 2004 14:26:03 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v619)
Content-Transfer-Encoding: 7bit
Message-Id: <2EC7127C-FACB-11D8-8690-000A95C73842@cisco.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
To: ietf@ietf.org
From: David R Oran <oran@cisco.com>
Date: Mon, 30 Aug 2004 17:25:57 -0400
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
Content-Transfer-Encoding: 7bit
Subject: Hotel online reservations
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-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Content-Transfer-Encoding: 7bit

do not work as advertised. All rooms show booked, despite putting in 
correct dates and group code as instructed.

I called the hotel and had no trouble booking by phone.

Just a word to the wise...


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


From ietf-bounces@ietf.org  Mon Aug 30 17:51:36 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06467;
	Mon, 30 Aug 2004 17:51:36 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C1u5m-0000sF-Bl; Mon, 30 Aug 2004 17:53:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C1two-00032w-JM; Mon, 30 Aug 2004 17:44:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C1tnx-0000Ue-Ub
	for ietf@megatron.ietf.org; Mon, 30 Aug 2004 17:35:09 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05261
	for <ietf@ietf.org>; Mon, 30 Aug 2004 17:35:07 -0400 (EDT)
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C1tpo-0000P1-HR
	for ietf@ietf.org; Mon, 30 Aug 2004 17:37: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 i7ULYb7w029853
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 30 Aug 2004 17:34:37 -0400
Date: Mon, 30 Aug 2004 17:34:37 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Ted Hardie <hardie@qualcomm.com>
In-Reply-To: <p0611040bbd59466aa292@[129.46.227.161]>
Message-ID: <Pine.LNX.4.44.0408301729010.28223-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 2.7 (++)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Cc: ietf@ietf.org, Hadmut Danisch <hadmut@danisch.de>
Subject: Re: How IETF treats contributors
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-Score: 2.7 (++)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac

I'm suggesting that due diligence requires that Jim Miller should be
contacted.  Also, Paul Vixie appears to have done no work, except to
suggest that Jim Miller thought of the idea before it was written down an
posted to the DNSEXT Namedroppers list by David Green.  It was David
Green, not Paul Vixie, who wrote it down the earliest version we presently
have.

Since Vixie did not formulate the idea, nor make any detailed writing on
the subject that I see, I don't know why he would be given special
recognition.

		--Dean

The messag

On Mon, 30 Aug 2004, Ted Hardie wrote:

> At 4:55 PM -0400 8/30/04, Dean Anderson wrote:
> >
> >http://www.ietf.org/internet-drafts/draft-ietf-marid-core-03.txt
> >
> >http://ops.ietf.org/lists/namedroppers/namedroppers.2002/msg00658.html
> >
> >The idea came from David Green, and Vixie says it originated from Jim
> >Miller in 1998.  Vixie had little or nothing to do with it. Why the draft
> >claims the earliest known work is due to Vixie is unclear.
> >
> >		--Dean
> 
> Elided below is the actual draft, "Repudiating Mail From".  The citation
> is to the earliest known work (in other words, the earliest place someone
> wrote down a solution based on this idea).  If you would like to suggest
> to the authors of marid-core that Jim Miller ought to be cited as the source
> of the idea from which Vixie's work was derived, I'm sure they will 
> consider it.
> Paul Vixie should still be cited, of course, as many people worked off of
> his formulation of the idea; so should Hadmut Danisch, for the same reason.
> 
> The main point to be made, though, is that these are all contributions to
> the IETF's collective work on the problem, and should be seen as such.
> 				regards,
> 					Ted Hardie
> 
> 
> 
> 
> 
> >==========================================================================
> >     * To: namedroppers@ops.ietf.org
> >     * Subject: Re: Mail-Transmitter RR
> >     * From: Paul Vixie <paul@vix.com>
> >     * Date: Sat, 01 Jun 2002 18:16:37 -0700
> >     * In-reply-to: Message from David Green <green@couchpotato.net> of
> >"Sat, 01 Jun 2002 20:49:48
> >EDT."<Pine.LNX.4.44.0206012045470.8349-200000@david.couchpotato.net>
> >
> >
> >>  I'm sorry if this is off-topic, but I couldn't find a working group that
> >>  is working on dealing with spam, so this is the closest match I could
> >>  find. I know this is in no way related to IPv6 or anything else you guys
> >>  are working on, but it is an idea I had involving the addition of a RR
> >>  type. If this is not the right place to be sending this, any pointers to
> >>  other working groups/forums would be greatly appreciated. And I appreciate
> >>  all of the hard work you guys are doing... My idea is attached (domauth.txt)
> >
> >In 1998, Jim Miller suggested this.  A few weeks ago, I wrote the
> >following.  Comments are welcome.
> >
> >==========================================================================
> 
> 


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


From ietf-bounces@ietf.org  Mon Aug 30 18:14:28 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08552;
	Mon, 30 Aug 2004 18:14:28 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C1uRt-0001Mp-3r; Mon, 30 Aug 2004 18:16:26 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C1uJ7-0003ON-Rc; Mon, 30 Aug 2004 18:07:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C1uCD-0007IU-TQ
	for ietf@megatron.ietf.org; Mon, 30 Aug 2004 18:00:14 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07141
	for <ietf@ietf.org>; Mon, 30 Aug 2004 18:00:11 -0400 (EDT)
Received: from nosc.ja.net ([128.86.16.20])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C1uE3-000168-PG
	for ietf@ietf.org; Mon, 30 Aug 2004 18:02:09 -0400
Received: from nosc.ja.net ([128.86.16.20] helo=[127.0.0.1])
	by nosc.ja.net with esmtp (Exim 3.36 #53)
	id 1C1u9I-0006om-00; Mon, 30 Aug 2004 22:57:13 +0100
Message-ID: <4133A2C2.9090501@nosc.ja.net>
Date: Mon, 30 Aug 2004 22:57:22 +0100
From: Rob Evans <rhe@nosc.ja.net>
User-Agent: Mozilla Thunderbird 0.7.2 (Windows/20040707)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: David R Oran <oran@cisco.com>
References: <2EC7127C-FACB-11D8-8690-000A95C73842@cisco.com>
In-Reply-To: <2EC7127C-FACB-11D8-8690-000A95C73842@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-MHS-Connection-from: 128.86.16.20
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: Hotel online reservations
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-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Content-Transfer-Encoding: 7bit

> do not work as advertised. All rooms show booked, despite putting in 
> correct dates and group code as instructed.

Odd.  It worked for me just now, perhaps it has been fixed (or 
alternatively, I broke it :-)).  YM obviously Vs.

Regards,
Rob

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


From ietf-bounces@ietf.org  Mon Aug 30 18:20:03 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09179;
	Mon, 30 Aug 2004 18:20:03 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C1uXJ-0001W2-TU; Mon, 30 Aug 2004 18:22:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C1uMi-0005BK-6Y; Mon, 30 Aug 2004 18:11:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C1uGC-0001sH-7G
	for ietf@megatron.ietf.org; Mon, 30 Aug 2004 18:04:20 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07398
	for <ietf@ietf.org>; Mon, 30 Aug 2004 18:04:17 -0400 (EDT)
Received: from sokol.elan.net ([216.151.192.200])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C1uI1-0001At-Ow
	for ietf@ietf.org; Mon, 30 Aug 2004 18:06:15 -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 i7UMCvE2023366;
	Mon, 30 Aug 2004 15:12:57 -0700
Received: from localhost (william@localhost)
	by sokol.elan.net (8.12.11/8.12.5/Submit) with ESMTP id i7UMCvsx023363; 
	Mon, 30 Aug 2004 15:12:57 -0700
X-Authentication-Warning: sokol.elan.net: william owned process doing -bs
Date: Mon, 30 Aug 2004 15:12:57 -0700 (PDT)
From: "william(at)elan.net" <william@elan.net>
To: Ted Hardie <hardie@qualcomm.com>
In-Reply-To: <p0611040bbd59466aa292@[129.46.227.161]>
Message-ID: <Pine.LNX.4.44.0408301449500.23504-100000@sokol.elan.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: Dean Anderson <dean@av8.com>, ietf@ietf.org,
        Hadmut Danisch <hadmut@danisch.de>
Subject: Re: How IETF treats contributors
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-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9


> At 4:55 PM -0400 8/30/04, Dean Anderson wrote:
> >
> >http://www.ietf.org/internet-drafts/draft-ietf-marid-core-03.txt
> >
> >http://ops.ietf.org/lists/namedroppers/namedroppers.2002/msg00658.html
> >
> >The idea came from David Green, and Vixie says it originated from Jim
> >Miller in 1998.  Vixie had little or nothing to do with it. Why the draft
> >claims the earliest known work is due to Vixie is unclear.
> >
> >		--Dean
> 
> Elided below is the actual draft, "Repudiating Mail From".  The citation
> is to the earliest known work (in other words, the earliest place someone
> wrote down a solution based on this idea).  If you would like to suggest
> to the authors of marid-core that Jim Miller ought to be cited as the source
> of the idea from which Vixie's work was derived, I'm sure they will 
> consider it. 

Jim Miller is sited as original source of the idea in section 10 on page 31
of draft-ietf-marid-protocol-02 (i.e. SPF syntax & format draft), see
 http://www.ietf.org/internet-drafts/draft-ietf-marid-protocol-02.txt
I've  never heard  before of David Green as being source of the idea, if 
he's still around, we may ask him and Vixie and Jim Miller about the exact 
details and if they are satisified with current information in acknolidgement
sections of MARID drafts. But based on message from namedroppers sited by 
Dean, it seems that David Green came up with idea separate and already 
after Vixie wrote original "Repudiating Mail From" draft. 

It would however be appropriate to have the same list of prior work in
acknolidgement section of marid-core draft as in marid-protocol draft

-- 
William Leibzon
Elan Networks
william@elan.net


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


From ietf-bounces@ietf.org  Mon Aug 30 18:29:04 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09806;
	Mon, 30 Aug 2004 18:29:04 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C1ug2-0001jl-Ar; Mon, 30 Aug 2004 18:31:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C1uTC-00017t-8E; Mon, 30 Aug 2004 18:17:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C1uJQ-0003Vt-4x
	for ietf@megatron.ietf.org; Mon, 30 Aug 2004 18:07:40 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07778
	for <ietf@ietf.org>; Mon, 30 Aug 2004 18:07:37 -0400 (EDT)
Received: from minbar.fac.cs.cmu.edu ([128.2.185.161])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1C1uLE-0001Eh-1A
	for ietf@ietf.org; Mon, 30 Aug 2004 18:09:35 -0400
Received: from minbar.fac.cs.cmu.edu ([127.0.0.1]) by minbar.fac.cs.cmu.edu
	id aa02755; 30 Aug 2004 18:04 EDT
Date: Mon, 30 Aug 2004 18:04:01 -0400
From: Jeffrey Hutzelman <jhutz@cmu.edu>
To: David R Oran <oran@cisco.com>, ietf@ietf.org
Message-ID: <233260000.1093903441@minbar.fac.cs.cmu.edu>
In-Reply-To: <2EC7127C-FACB-11D8-8690-000A95C73842@cisco.com>
References: <2EC7127C-FACB-11D8-8690-000A95C73842@cisco.com>
X-Mailer: Mulberry/3.0.3 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7bit
Subject: Re: Hotel online reservations
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-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: 7bit



On Monday, August 30, 2004 17:25:57 -0400 David R Oran <oran@cisco.com> 
wrote:

> do not work as advertised. All rooms show booked, despite putting in
> correct dates and group code as instructed.

It just worked fine for me.  It is necessary to enter the correct group 
code, which is "IEF" rather than "IETF".

-- Jeffrey T. Hutzelman (N3NHS) <jhutz+@cmu.edu>
   Sr. Research Systems Programmer
   School of Computer Science - Research Computing Facility
   Carnegie Mellon University - Pittsburgh, PA


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


From ietf-bounces@ietf.org  Mon Aug 30 18:42:34 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10702;
	Mon, 30 Aug 2004 18:42:34 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C1ut5-000247-Ln; Mon, 30 Aug 2004 18:44:32 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C1uhn-0005IN-Kc; Mon, 30 Aug 2004 18:32:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C1uVs-0002Jr-1g
	for ietf@megatron.ietf.org; Mon, 30 Aug 2004 18:20:32 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09250
	for <ietf@ietf.org>; Mon, 30 Aug 2004 18:20:29 -0400 (EDT)
Received: from mail1.microsoft.com ([131.107.3.125])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C1uXg-0001Vm-14
	for ietf@ietf.org; Mon, 30 Aug 2004 18:22:27 -0400
Received: from mailout1.microsoft.com ([157.54.1.117]) by mail1.microsoft.com
	with Microsoft SMTPSVC(6.0.3790.196); 
	Mon, 30 Aug 2004 15:18:34 -0700
Received: from red-imc-02.redmond.corp.microsoft.com ([157.54.9.107]) by
	mailout1.microsoft.com with Microsoft SMTPSVC(6.0.3790.0); 
	Mon, 30 Aug 2004 15:18:07 -0700
Received: from win-imc-02.wingroup.windeploy.ntdev.microsoft.com
	([157.54.0.84]) by red-imc-02.redmond.corp.microsoft.com with
	Microsoft SMTPSVC(6.0.3790.0); Mon, 30 Aug 2004 15:18:12 -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); Mon, 30 Aug 2004 15:17:16 -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: Mon, 30 Aug 2004 15:18:17 -0700
Message-ID: <DAC3FCB50E31C54987CD10797DA511BA0AB9C1B6@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: How IETF treats contributors
thread-index: AcSOtBbFWPpSzrZFR/+SJ4lsiir7+gAKnRkg
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: "Ted Hardie" <hardie@qualcomm.com>, "Hadmut Danisch" <hadmut@danisch.de>,
        <ietf@ietf.org>
X-OriginalArrivalTime: 30 Aug 2004 22:17:16.0147 (UTC)
	FILETIME=[1B61EC30:01C48EDF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Content-Transfer-Encoding: quoted-printable
Subject: RE: How IETF treats contributors
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-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: quoted-printable

>     9. Acknowledgements
>=20
>        Variations on the idea of using a DNS record to check the
> legitimacy
>        of an email address have occurred multiple times. The earliest
> known
>        work is [Vixie]; others include [RMX], [SPF] and [CallerID].
>=20
>        The current document borrows heavily from each of the above,
and
>        incorporates ideas proposed by many members of the MARID
working
>       group.  The contributions of each of the above are gratefully
>       acknowledged.

Ted,

My personal practice, when writing such acknowledgement sections, is to
write down the names of the individuals who contributed the idea, or
contributed significant comments to a draft.

It is true that if one follows references such as [RMX] one eventually
find the list of authors of the proposal, but they are still at least
one level of indirection away. The MARID draft could just as well say
something like "The earliest work was submitted to the IETF by Paul
Vixie [Vixie]; others include ..." ASCII bits are cheap.

-- Christian Huitema

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


From ietf-bounces@ietf.org  Mon Aug 30 18:44:12 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10828;
	Mon, 30 Aug 2004 18:44:12 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C1uug-00026W-E0; Mon, 30 Aug 2004 18:46:10 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C1uhp-0005JA-1K; Mon, 30 Aug 2004 18:32:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C1uW5-0002TD-2Y
	for ietf@megatron.ietf.org; Mon, 30 Aug 2004 18:20:45 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09278
	for <ietf@ietf.org>; Mon, 30 Aug 2004 18:20:42 -0400 (EDT)
Received: from cirrus.av8.net ([130.105.36.66])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C1uXt-0001W1-3u
	for ietf@ietf.org; Mon, 30 Aug 2004 18:22:40 -0400
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66])
	(authenticated bits=0)
	by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i7UMK3wx030760
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 30 Aug 2004 18:20:04 -0400
Date: Mon, 30 Aug 2004 18:20:03 -0400 (EDT)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Ted Hardie <hardie@qualcomm.com>
In-Reply-To: <p0611040bbd59466aa292@[129.46.227.161]>
Message-ID: <Pine.LNX.4.44.0408301801460.28223-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 2.7 (++)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: ietf@ietf.org, Hadmut Danisch <hadmut@danisch.de>
Subject: Re: How IETF treats contributors
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-Score: 2.7 (++)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64

Lets take a close look:
=============================================================================
In 1998, Jim Miller suggested this.  A few weeks ago, I wrote the 
following. Comments are welcome.

   Independent                                            Paul Vixie (Ed.)
   Request for Comments: XXXX Category: Experimental
   May 28, 2002

                            Repudiating MAIL FROM
=============================================================================

Pay attention to the May, 28, 2002 date. The message was sent on June 1, 
2002. (A Saturday).

The claim of Vixie's that "A few weeks ago, I wrote the following." can't 
be sustained. First, the Greens' message was written on June 1, 2002.  
Vixie's "draft" is dated "May 28, 2002", the Tuesday before, not "a few 
weeks ago".

Why would Vixie be motivated to write a draft just a few days before David
Green?  Green, out of the blue, submits his draft on June 1st, 2002. Only
after that does Vixie make his announcment.  And Vixie's claim is
inconsistent and implausible.

But, despite the implausibility of Vixie's claim, Green __actually__
submitted his work first. The first author to get a paper to a journal is
given credit for originating the idea.  __Vixie__ is the only source of
Vixie's claims to prior work.  And that doesn't cut it.  And as President
of the LPF, I know something about the concept of prior work in area of
patents, and such flimsy and inconsistent claims of prior work wouldn't be
accepted.

Unless we find that Jim Miller or someone else actually published
something, then David Green is the person who originated the idea. Next in
line is Hadmut Danisch who made further refinements and authored the RMX
draft.  There are many others who made smaller contributions.

		--Dean

> Elided below is the actual draft, "Repudiating Mail From".  The citation
> is to the earliest known work (in other words, the earliest place someone
> wrote down a solution based on this idea).  If you would like to suggest
> to the authors of marid-core that Jim Miller ought to be cited as the source
> of the idea from which Vixie's work was derived, I'm sure they will 
> consider it.
> Paul Vixie should still be cited, of course, as many people worked off of
> his formulation of the idea; so should Hadmut Danisch, for the same reason.


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


From ietf-bounces@ietf.org  Mon Aug 30 19:30:51 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14028;
	Mon, 30 Aug 2004 19:30:51 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C1vdn-0003Gl-7V; Mon, 30 Aug 2004 19:32:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C1vXO-0000Um-Fj; Mon, 30 Aug 2004 19:26:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C1vUX-0007x6-Bh
	for ietf@megatron.ietf.org; Mon, 30 Aug 2004 19:23:13 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13700
	for <ietf@ietf.org>; Mon, 30 Aug 2004 19:23:10 -0400 (EDT)
Received: from pcls2.std.com ([192.74.137.142] helo=TheWorld.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C1vWN-00036Z-UC
	for ietf@ietf.org; Mon, 30 Aug 2004 19:25:09 -0400
Received: from [10.0.1.13] (h0030653af4da.ne.client2.attbi.com [24.34.102.194])
	by TheWorld.com (8.12.8p1/8.12.8) with ESMTP id i7UNKh0v025092;
	Mon, 30 Aug 2004 19:20:44 -0400
Mime-Version: 1.0
X-Sender: day@pop.theworld.com
Message-Id: <v04220806bd5962148387@[10.0.1.13]>
In-Reply-To: <20040830090627.GA22982@danisch.de>
References: <20040830090627.GA22982@danisch.de>
Date: Mon, 30 Aug 2004 19:05:30 -0400
To: Hadmut Danisch <hadmut@danisch.de>, ietf@ietf.org
From: John Day <day@std.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Subject: Re: How IETF treats contributors
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-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370

The best solution is to remove all authorship from all Internet 
standards, then there will be no problems.  This isn't suppose to be 
an ego trip. If people really think the documents are important, they 
don't need their names on them.  If they need their name on it, they 
are doing it for the wrong reasons.

You don't find authors on the output of the standards groups.  The 
most you will find is a list of the membership at the time of 
approval.

Take care,
John

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


From ietf-bounces@ietf.org  Mon Aug 30 20:05:17 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16000;
	Mon, 30 Aug 2004 20:05:17 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C1wAs-00042T-Jm; Mon, 30 Aug 2004 20:07:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C1w5r-0007Rt-Do; Mon, 30 Aug 2004 20:01:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C1vqc-0004Xa-R5
	for ietf@megatron.ietf.org; Mon, 30 Aug 2004 19:46:02 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14868
	for <ietf@ietf.org>; Mon, 30 Aug 2004 19:45:58 -0400 (EDT)
Received: from mail66.messagelabs.com ([193.109.254.35])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1C1vsS-0003bg-Kr
	for ietf@ietf.org; Mon, 30 Aug 2004 19:47:58 -0400
X-VirusChecked: Checked
X-Env-Sender: cchaplin@symbol.com
X-Msg-Ref: server-14.tower-66.messagelabs.com!1093909527!2078476
X-StarScan-Version: 5.2.10; banners=symbol.com,-,-
X-Originating-IP: [167.206.235.72]
Received: (qmail 13287 invoked from network); 30 Aug 2004 23:45:27 -0000
Received: from mx2.symbol.com (167.206.235.72)
	by server-14.tower-66.messagelabs.com with SMTP;
	30 Aug 2004 23:45:27 -0000
Received: from proxy.symbol.com (proxy.symbol.com [157.235.5.10])
	by mx2.symbol.com (8.12.8/8.12.8) with ESMTP id i7UNjRn6028566
	for <ietf@ietf.org>; Mon, 30 Aug 2004 19:45:27 -0400
Received: from RUNABOUT ([157.235.95.252])
	by proxy.symbol.com (8.12.11/8.12.8) with ESMTP id i7UNjLmv004933
	for <ietf@ietf.org>; Mon, 30 Aug 2004 19:45:22 -0400
Received: from SJ-DOM-MTA by RUNABOUT
	with Novell_GroupWise; Mon, 30 Aug 2004 16:45:18 -0700
Message-Id: <s133599e.083@RUNABOUT>
X-Mailer: Novell GroupWise Internet Agent 6.0.4
Date: Mon, 30 Aug 2004 16:45:12 -0700
From: "Clint Chaplin" <cchaplin@symbol.com>
To: <hadmut@danisch.de>, <ietf@ietf.org>, <day@std.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-Scanned-By: MIMEDefang 2.39
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Mon, 30 Aug 2004 20:01:45 -0400
Subject: Re: How IETF treats contributors
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-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: quoted-printable

Well,=20at=20least=20for=20802.11,=20this=20isn't=20true.

There=20is=20a=20section=20to=20list=20the=20contributors=20who=20had=20co=
ntributed=20a=20significant=20contribution=20to=20the=20standards=20proces=
s.=20=20This=20list=20can=20get=20quite=20lengthy.

Clint=20(JOATMON)=20Chaplin
Wireless=20Security=20Advisor
Wireless=20Standards=20Lead

>>>=20John=20Day=20<day@std.com>=208/30/04=2016:05:30=20>>>
The=20best=20solution=20is=20to=20remove=20all=20authorship=20from=20all=20=
Internet=20
standards,=20then=20there=20will=20be=20no=20problems.=20=20This=20isn't=20=
suppose=20to=20be=20
an=20ego=20trip.=20If=20people=20really=20think=20the=20documents=20are=20=
important,=20they=20
don't=20need=20their=20names=20on=20them.=20=20If=20they=20need=20their=20=
name=20on=20it,=20they=20
are=20doing=20it=20for=20the=20wrong=20reasons.

You=20don't=20find=20authors=20on=20the=20output=20of=20the=20standards=20=
groups.=20=20The=20
most=20you=20will=20find=20is=20a=20list=20of=20the=20membership=20at=20th=
e=20time=20of=20
approval.

Take=20care,
John

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

________________________________________________________________________
This=20email=20has=20been=20scanned=20for=20computer=20viruses.


________________________________________________________________________
This=20email=20has=20been=20scanned=20for=20computer=20viruses.

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


From ietf-bounces@ietf.org  Mon Aug 30 20:25:17 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17052;
	Mon, 30 Aug 2004 20:25:17 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C1wUU-0004Td-Ui; Mon, 30 Aug 2004 20:27:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C1wLu-0002ok-8S; Mon, 30 Aug 2004 20:18:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C1wFx-0001b2-GY
	for ietf@megatron.ietf.org; Mon, 30 Aug 2004 20:12:13 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16489
	for <ietf@ietf.org>; Mon, 30 Aug 2004 20:12:11 -0400 (EDT)
Received: from mail.lumenvox.com ([206.169.193.45] helo=lv-svr.lumenvox.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C1wHo-0004Dy-Al
	for ietf@ietf.org; Mon, 30 Aug 2004 20:14:09 -0400
Received: from PROGTHOMAS ([10.0.0.162]) by lv-svr.lumenvox.com with Microsoft
	SMTPSVC(5.0.2195.6713); Mon, 30 Aug 2004 17:04:16 -0700
From: "Thomas Gal" <ThomasGal@LumenVox.com>
To: "'John Day'" <day@std.com>, "'Hadmut Danisch'" <hadmut@danisch.de>,
        <ietf@ietf.org>
Date: Mon, 30 Aug 2004 17:11:40 -0700
Organization: LumenVox LLC
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
Thread-Index: AcSO6JGg00lCCKHcTHCJG52617iU2wAAdwHg
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
In-Reply-To: <2D0CA64CDC33E14DA7AB043B8CC4D2BB02340DFC@svr-exc.domain.com>
Message-ID: <LV-SVRFRaqbC8wSA1Xv0000014e@lv-svr.lumenvox.com>
X-OriginalArrivalTime: 31 Aug 2004 00:04:16.0671 (UTC)
	FILETIME=[0E5022F0:01C48EEE]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Content-Transfer-Encoding: 7bit
Subject: RE: How IETF treats contributors
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: ThomasGal@LumenVox.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-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Content-Transfer-Encoding: 7bit

I agree with: 

"This isn't suppose to be an ego trip. If people really think the documents
are important, they don't need their names on them.  If they need their name
on it, they are doing it for the wrong reasons."

	Not to mention the spirit of removing authorship. In reality I feel
like this amounts to removing the title or something else that is so
obviuosly a part of a document. Certainly there is no shame in being proud
of your work, and nobody can help but feel a little miffed when something
they did may have been overlooked. Seems fairly possible however that the
people who are most interested in this subject probably know what really
maters, and one way or another EVERYONE on the IETF list now knows. The
solutions to these kinds of problems have always been in your hands, and YOU
are empowered when you choose not to care....or at least let something get
under your skin.

	Isn't the point here that EVERYONE hates spam?

-Tom




-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of John
Day
Sent: Monday, August 30, 2004 4:06 PM
To: Hadmut Danisch; ietf@ietf.org
Subject: Re: How IETF treats contributors

The best solution is to remove all authorship from all Internet standards,
then there will be no problems.  This isn't suppose to be an ego trip. If
people really think the documents are important, they don't need their names
on them.  If they need their name on it, they are doing it for the wrong
reasons.

You don't find authors on the output of the standards groups.  The most you
will find is a list of the membership at the time of approval.

Take care,
John

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


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


From ietf-bounces@ietf.org  Mon Aug 30 21:14:11 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20219;
	Mon, 30 Aug 2004 21:14:11 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C1xFq-0005Ya-AS; Mon, 30 Aug 2004 21:16:10 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C1xA5-0004N1-Kk; Mon, 30 Aug 2004 21:10:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C1x7W-0003TI-AC
	for ietf@megatron.ietf.org; Mon, 30 Aug 2004 21:07:34 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19747
	for <ietf@ietf.org>; Mon, 30 Aug 2004 21:07:32 -0400 (EDT)
Received: from [66.147.157.90] (helo=USEX.think3.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C1x9O-0005Oi-Gr
	for ietf@ietf.org; Mon, 30 Aug 2004 21:09:30 -0400
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: Mon, 30 Aug 2004 20:03:12 -0500
Message-ID: <B1F1256E2FAEA049B5F11549870302B16646DE@USEX.think3.com>
Thread-Topic: How IETF treats contributors
Thread-Index: AcSO6JGg00lCCKHcTHCJG52617iU2wAAdwHgAAKF+xA=
From: "Nick Carter" <Nick.Carter@think3.com>
To: <ThomasGal@LumenVox.com>, "John Day" <day@std.com>,
        "Hadmut Danisch" <hadmut@danisch.de>, <ietf@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Content-Transfer-Encoding: quoted-printable
Subject: RE: How IETF treats contributors
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-Score: 0.0 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Content-Transfer-Encoding: quoted-printable

The problem being discussed is not a matter of disliking or liking spam,
but rather the problem of solving it.  On that note, I agree with Dean
Anderson.  Everyone hates SPAM, but that is not in question.  I think
credit should be given to the individual that properly documented the
solution and not just to someone that noted an idea.  You could contest
it saying it was an excrescence of Vixie's work, but the details do not
exist in Vixie's work.  As noted with Dean, Vixies work is implausible
and therefore credit should not be given. All work submitted should be
punctilio and of protocol. =20

Nick

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
Thomas Gal
Sent: Monday, August 30, 2004 7:12 PM
To: 'John Day'; 'Hadmut Danisch'; ietf@ietf.org
Subject: RE: How IETF treats contributors

I agree with:=20

"This isn't suppose to be an ego trip. If people really think the
documents
are important, they don't need their names on them.  If they need their
name
on it, they are doing it for the wrong reasons."

	Not to mention the spirit of removing authorship. In reality I
feel
like this amounts to removing the title or something else that is so
obviuosly a part of a document. Certainly there is no shame in being
proud
of your work, and nobody can help but feel a little miffed when
something
they did may have been overlooked. Seems fairly possible however that
the
people who are most interested in this subject probably know what really
maters, and one way or another EVERYONE on the IETF list now knows. The
solutions to these kinds of problems have always been in your hands, and
YOU
are empowered when you choose not to care....or at least let something
get
under your skin.

	Isn't the point here that EVERYONE hates spam?

-Tom




-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
John
Day
Sent: Monday, August 30, 2004 4:06 PM
To: Hadmut Danisch; ietf@ietf.org
Subject: Re: How IETF treats contributors

The best solution is to remove all authorship from all Internet
standards,
then there will be no problems.  This isn't suppose to be an ego trip.
If
people really think the documents are important, they don't need their
names
on them.  If they need their name on it, they are doing it for the wrong
reasons.

You don't find authors on the output of the standards groups.  The most
you
will find is a list of the membership at the time of approval.

Take care,
John

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


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

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


From ietf-bounces@ietf.org  Tue Aug 31 05:33:02 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01496;
	Tue, 31 Aug 2004 05:33:02 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C252e-0006gT-If; Tue, 31 Aug 2004 05:35:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C24tC-0001Aa-Nw; Tue, 31 Aug 2004 05:25:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C24rO-0000sT-6H
	for ietf@megatron.ietf.org; Tue, 31 Aug 2004 05:23:26 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01170
	for <ietf@ietf.org>; Tue, 31 Aug 2004 05:23:24 -0400 (EDT)
Received: from postman.ripe.net ([193.0.0.199])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C24tI-0006Wk-3i
	for ietf@ietf.org; Tue, 31 Aug 2004 05:25:27 -0400
Received: by postman.ripe.net (Postfix, from userid 8)
	id A352D51FA8; Tue, 31 Aug 2004 11:22:49 +0200 (CEST)
Received: from birch.ripe.net (birch.ripe.net [193.0.1.96])
	by postman.ripe.net (Postfix) with ESMTP id 37DC14E055
	for <ietf@ietf.org>; Tue, 31 Aug 2004 10:40:16 +0200 (CEST)
Received: from x50.ripe.net (x50.ripe.net [193.0.1.50])
	by birch.ripe.net (8.12.10/8.11.6) with SMTP id i7V8eGDI019975
	for <ietf@ietf.org>; Tue, 31 Aug 2004 10:40:16 +0200
Date: Tue, 31 Aug 2004 10:40:16 +0200
From: "Olaf M. Kolkman" <olaf@ripe.net>
To: ietf@ietf.org
Message-Id: <20040831104016.4bf3d0c6.olaf@ripe.net>
In-Reply-To: <LV-SVRFRaqbC8wSA1Xv0000014e@lv-svr.lumenvox.com>
References: <2D0CA64CDC33E14DA7AB043B8CC4D2BB02340DFC@svr-exc.domain.com>
	<LV-SVRFRaqbC8wSA1Xv0000014e@lv-svr.lumenvox.com>
Organization: RIPE NCC
X-Mailer: Sylpheed version 0.9.11 (GTK+ 1.2.10; i686-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-RIPE-Spam-Status: N 0.000024 / 0.0 / 0.0 / disabled
X-RIPE-Signature: 178840d85979cc625121fc95e9aa3d9f
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: 7bit
Subject: Re: How IETF treats contributors
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-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Content-Transfer-Encoding: 7bit



Thomas Gal:
> I agree with: 
> 
> "This isn't suppose to be an ego trip. If people really think the documents
> are important, they don't need their names on them.  If they need their name
> on it, they are doing it for the wrong reasons."

Me too. Documents should only be written if they are important for the
commons. 

But.

If it comes to acknowledging attributions we have to be careful. I do
not think it is a good idea to drop authorship of documents.  We do
not have many means to motivate people. Giving credit is actually one
of very few means that the IETF has available as a motivational
tool. 

It is easy to forget folk that where involved in early stages, but as
Christian said "bits are cheap" and if there is doubt on where to stop
acknowledging people we'd better be safe than sorry.

I'd like to expand on what Dean said: "Credit and attribution is about
intellectual honesty [ and _courtesy_ ] not about copyright law".



-- Olaf



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


From ietf-bounces@ietf.org  Tue Aug 31 06:51:01 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA05418;
	Tue, 31 Aug 2004 06:51:01 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C26G8-00084f-Qt; Tue, 31 Aug 2004 06:53:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C269l-0005lV-Ua; Tue, 31 Aug 2004 06:46:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C268f-0005Oi-TP
	for ietf@megatron.ietf.org; Tue, 31 Aug 2004 06:45:21 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA05130
	for <ietf@ietf.org>; Tue, 31 Aug 2004 06:45:19 -0400 (EDT)
Received: from fep22-0.kolumbus.fi ([193.229.0.60] helo=fep22-app.kolumbus.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C26Ac-0007z4-Eh
	for ietf@ietf.org; Tue, 31 Aug 2004 06:47:23 -0400
Received: from [10.68.138.175] (really [213.161.45.112])
	by fep22-app.kolumbus.fi with ESMTP
	id <20040831104440.GXPD27645.fep22-app.kolumbus.fi@[10.68.138.175]>;
	Tue, 31 Aug 2004 13:44:40 +0300
From: "John Loughney" <john.loughney@kolumbus.fi>
To: "Rob Evans" <rhe@nosc.ja.net>
Date: Tue, 31 Aug 2004 13:44:04 +0300
Message-ID: <VTHhqDWX21NZ.B11hSz6m@mail.mobiili.net>
X-Mailer: EPOC e-mail version 2.10
MIME-Version: 1.0
Content-Language: i-default
X-Spam-Score: 0.8 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: David R Oran <oran@cisco.com>, ietf@ietf.org
Subject: seems to work now Re: Hotel online reservations
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: John Loughney <john.loughney@kolumbus.fi>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-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="===============1682381009=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43

This is a MIME Message

--===============1682381009==
Content-Language: i-default
Content-Type: multipart/alternative;
	boundary="EPOC32-88Sr7RltNH2k5l7MsLsW_8g3ntM5y7_Z4Mf94_gjNW8ZBX-Y"

This is a MIME Message

--EPOC32-88Sr7RltNH2k5l7MsLsW_8g3ntM5y7_Z4Mf94_gjNW8ZBX-Y
Content-Type: text/plain; charset=UTF-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

It seems to be working now.  Nice to book on-line, for those who are time =
zone challenged.

John

________________ Reply header ________________
Subject:	Re: Hotel online reservations
Author:	"Rob Evans" <rhe@nosc.ja.net>
Date:		30th August 2004 10:57:22  PM

> do not work as advertised. All rooms show booked, despite putting in =

> correct dates and group code as instructed.

Odd.  It worked for me just now, perhaps it has been fixed (or=20
alternatively, I broke it :-)).  YM obviously Vs.

Regards,
Rob

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf
--EPOC32-88Sr7RltNH2k5l7MsLsW_8g3ntM5y7_Z4Mf94_gjNW8ZBX-Y
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDMuMiBG
aW5hbC8vRU4iPg0KPEhUTUw+IA0KPEhFQUQ+IA0KPFRJVExFPkNvbnZlcnRl
ZCBmcm9tIFJpY2ggVGV4dDwvVElUTEU+DQo8TUVUQSBIVFRQLUVRVUlWPSJD
b250ZW50LVR5cGUiIENPTlRFTlQ9InRleHQvaHRtbDsgY2hhcnNldD1VVEYt
OCI+PE1FVEEgTkFNRT0iZ2VuZXJhdG9yIiBDT05URU5UPSJydDJodG1sIGNv
bnZlcnRlciI+DQo8L0hFQUQ+IA0KPEJPRFkgQkdDT0xPUj0iI2ZmZmZmZiIg
VEVYVD0iIzAwMDAwMCI+DQo8RElWIEFMSUdOPUxFRlQ+SXQgc2VlbXMgdG8g
YmUgd29ya2luZyBub3cuICBOaWNlIHRvIGJvb2sgb24tbGluZSwgZm9yIHRo
b3NlIHdobyBhcmUgdGltZSB6b25lIGNoYWxsZW5nZWQuPC9ESVY+IA0KPERJ
ViBBTElHTj1MRUZUPiZuYnNwOzwvRElWPjxESVYgQUxJR049TEVGVD5Kb2hu
PC9ESVY+IA0KPERJViBBTElHTj1MRUZUPiZuYnNwOzwvRElWPjxESVYgQUxJ
R049TEVGVD5fX19fX19fX19fX19fX19fIFJlcGx5IGhlYWRlciBfX19fX19f
X19fX19fX19fPC9ESVY+IA0KPERJViBBTElHTj1MRUZUPlN1YmplY3Q6IFJl
OiBIb3RlbCBvbmxpbmUgcmVzZXJ2YXRpb25zPC9ESVY+IA0KPERJViBBTElH
Tj1MRUZUPkF1dGhvcjogIlJvYiBFdmFucyIgJmx0O3JoZUBub3NjLmphLm5l
dCZndDs8L0RJVj4gDQo8RElWIEFMSUdOPUxFRlQ+RGF0ZTogIDMwdGggQXVn
dXN0IDIwMDQgMTA6NTc6MjIgIFBNPC9ESVY+IA0KPERJViBBTElHTj1MRUZU
PiZuYnNwOzwvRElWPjxESVYgQUxJR049TEVGVD4mZ3Q7IGRvIG5vdCB3b3Jr
IGFzIGFkdmVydGlzZWQuIEFsbCByb29tcyBzaG93IGJvb2tlZCwgZGVzcGl0
ZSBwdXR0aW5nIGluIDxCUj4mZ3Q7IGNvcnJlY3QgZGF0ZXMgYW5kIGdyb3Vw
IGNvZGUgYXMgaW5zdHJ1Y3RlZC48QlI+PEJSPk9kZC4gIEl0IHdvcmtlZCBm
b3IgbWUganVzdCBub3csIHBlcmhhcHMgaXQgaGFzIGJlZW4gZml4ZWQgKG9y
IDxCUj5hbHRlcm5hdGl2ZWx5LCBJIGJyb2tlIGl0IDotKSkuICBZTSBvYnZp
b3VzbHkgVnMuPEJSPjxCUj5SZWdhcmRzLDxCUj5Sb2I8QlI+PEJSPl9fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPC9E
SVY+IA0KPERJViBBTElHTj1MRUZUPklldGYgbWFpbGluZyBsaXN0PEJSPkll
dGZAaWV0Zi5vcmc8QlI+aHR0cHM6Ly93d3cxLmlldGYub3JnL21haWxtYW4v
bGlzdGluZm8vaWV0ZjxCUj48L0RJVj4gDQo8L0JPRFk+DQo8L0hUTUw+IA0K

--EPOC32-88Sr7RltNH2k5l7MsLsW_8g3ntM5y7_Z4Mf94_gjNW8ZBX-Y--




--===============1682381009==
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

--===============1682381009==--





From ietf-bounces@ietf.org  Tue Aug 31 07:21:55 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA07743;
	Tue, 31 Aug 2004 07:21:55 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C26k1-0000L1-AW; Tue, 31 Aug 2004 07:23:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C26bU-0001Ju-JJ; Tue, 31 Aug 2004 07:15:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C26Uk-0000TT-Ka
	for ietf@megatron.ietf.org; Tue, 31 Aug 2004 07:08:10 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA06812
	for <ietf@ietf.org>; Tue, 31 Aug 2004 07:08:08 -0400 (EDT)
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C26Wh-0008V0-HL
	for ietf@ietf.org; Tue, 31 Aug 2004 07:10:12 -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
	i7VB87gg000867; Tue, 31 Aug 2004 12:08:07 +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 MAA26235;
	Tue, 31 Aug 2004 12:08:05 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id i7VB85N21234;
	Tue, 31 Aug 2004 12:08:05 +0100
Date: Tue, 31 Aug 2004 12:08:05 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: John Loughney <john.loughney@kolumbus.fi>
Message-ID: <20040831110805.GF20023@login.ecs.soton.ac.uk>
References: <VTHhqDWX21NZ.B11hSz6m@mail.mobiili.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <VTHhqDWX21NZ.B11hSz6m@mail.mobiili.net>
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-MailScanner-From: tjc@smtp.ecs.soton.ac.uk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Cc: ietf@ietf.org
Subject: Re: seems to work now Re: Hotel online reservations
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-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2

On Tue, Aug 31, 2004 at 01:44:04PM +0300, John Loughney wrote:
> 
>    It  seems  to  be working now. Nice to book on-line, for those who are
>    time zone challenged.

I think the phone lines are there 24x7.   The person I spoke to was very
lively for what would have been at best 4am on the east coast :)

Tim

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


From ietf-bounces@ietf.org  Tue Aug 31 07:22:46 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA07815;
	Tue, 31 Aug 2004 07:22:45 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C26kq-0000MT-HI; Tue, 31 Aug 2004 07:24:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C26bV-0001K4-T4; Tue, 31 Aug 2004 07:15:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C26Wb-0000ek-Sf
	for ietf@megatron.ietf.org; Tue, 31 Aug 2004 07:10:05 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA06911
	for <ietf@ietf.org>; Tue, 31 Aug 2004 07:10:03 -0400 (EDT)
Received: from raven.ecs.soton.ac.uk ([152.78.70.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C26YY-000069-PJ
	for ietf@ietf.org; Tue, 31 Aug 2004 07:12: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
	i7VBA3gg000947
	for <ietf@ietf.org>; Tue, 31 Aug 2004 12:10:03 +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 MAA26375
	for <ietf@ietf.org>; Tue, 31 Aug 2004 12:10:00 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id i7VB9x721267
	for ietf@ietf.org; Tue, 31 Aug 2004 12:09:59 +0100
Date: Tue, 31 Aug 2004 12:09:59 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: ietf@ietf.org
Message-ID: <20040831110959.GG20023@login.ecs.soton.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
X-MailScanner-Information: Please contact helpdesk@ecs.soton.ac.uk for more
	information
X-ECS-MailScanner: Found to be clean
X-MailScanner-From: tjc@smtp.ecs.soton.ac.uk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Subject: Friday @ IETF61?
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-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2

So,

Are there any real Friday sessions at IETF 61, or not?

Someone tried to put v6ops on Friday am at IETF 60, before shifting
it out... it would be nice to either have IETF run out to 2-3pm and
have some real sessions, or simply make Friday officially BoFs only...

Tim

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


From ietf-bounces@ietf.org  Tue Aug 31 07:24:47 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08107;
	Tue, 31 Aug 2004 07:24:47 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C26mn-0000Sp-4b; Tue, 31 Aug 2004 07:26:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C26bX-0001KF-0i; Tue, 31 Aug 2004 07:15:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C26Xg-0000nA-QG
	for ietf@megatron.ietf.org; Tue, 31 Aug 2004 07:11:12 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA06955
	for <ietf@ietf.org>; Tue, 31 Aug 2004 07:11:10 -0400 (EDT)
Received: from tiere.net.avaya.com ([198.152.12.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C26Zd-00006p-Rs
	for ietf@ietf.org; Tue, 31 Aug 2004 07:13:15 -0400
Received: from tiere.net.avaya.com (localhost [127.0.0.1])
	by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	i7VB9TmF024559
	for <ietf@ietf.org>; Tue, 31 Aug 2004 07:09:29 -0400 (EDT)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	i7VB9RmF024515
	for <ietf@ietf.org>; Tue, 31 Aug 2004 07:09:28 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 31 Aug 2004 14:11:02 +0300
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F056B3416@is0004avexu1.global.avaya.com>
Thread-Topic: seems to work now Re: Hotel online reservations
Thread-Index: AcSPSILbBDsUNxgSSLSMC4H8IY4szAAAmNVw
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "John Loughney" <john.loughney@kolumbus.fi>, "Rob Evans" <rhe@nosc.ja.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Cc: David R Oran <oran@cisco.com>, ietf@ietf.org
Subject: RE: seems to work now Re: Hotel online reservations
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="===============0948515696=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db

This is a multi-part message in MIME format.

--===============0948515696==
content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C48F4B.339388FA"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C48F4B.339388FA
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64

Tm90ZSB0aGF0IHRoZSBjb252ZW50aW9uIC8gZ3JvdXAgY29kZSBpcyBJRUYgYW5kIG5vdCBJRVRG
IGFzIG9uZSBtYXkgZXhwZWN0ISBJdCB3b3JrZWQgZm9yIG1lIGFzIHdlbGwsIGJ1dCBvbmx5IG9u
IHNlY29uZCB0cnkgYmVjYXVzZSBvZiB0aGlzLiANCiANCg0KUmVnYXJkcywNCg0KRGFuDQoNCi0t
LS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBpZXRmLWJvdW5jZXNAaWV0Zi5vcmcgW21h
aWx0bzppZXRmLWJvdW5jZXNAaWV0Zi5vcmddT24gQmVoYWxmIE9mIEpvaG4gTG91Z2huZXkNClNl
bnQ6IDMxIEF1Z3VzdCwgMjAwNCAxOjQ0IFBNDQpUbzogUm9iIEV2YW5zDQpDYzogRGF2aWQgUiBP
cmFuOyBpZXRmQGlldGYub3JnDQpTdWJqZWN0OiBzZWVtcyB0byB3b3JrIG5vdyBSZTogSG90ZWwg
b25saW5lIHJlc2VydmF0aW9ucw0KDQoNCkl0IHNlZW1zIHRvIGJlIHdvcmtpbmcgbm93LiBOaWNl
IHRvIGJvb2sgb24tbGluZSwgZm9yIHRob3NlIHdobyBhcmUgdGltZSB6b25lIGNoYWxsZW5nZWQu
DQogDQpKb2huDQogDQpfX19fX19fX19fX19fX19fIFJlcGx5IGhlYWRlciBfX19fX19fX19fX19f
X19fDQpTdWJqZWN0OiBSZTogSG90ZWwgb25saW5lIHJlc2VydmF0aW9ucw0KQXV0aG9yOiAiUm9i
IEV2YW5zIiA8cmhlQG5vc2MuamEubmV0Pg0KRGF0ZTogMzB0aCBBdWd1c3QgMjAwNCAxMDo1Nzoy
MiBQTQ0KIA0KPiBkbyBub3Qgd29yayBhcyBhZHZlcnRpc2VkLiBBbGwgcm9vbXMgc2hvdyBib29r
ZWQsIGRlc3BpdGUgcHV0dGluZyBpbiANCj4gY29ycmVjdCBkYXRlcyBhbmQgZ3JvdXAgY29kZSBh
cyBpbnN0cnVjdGVkLg0KDQpPZGQuIEl0IHdvcmtlZCBmb3IgbWUganVzdCBub3csIHBlcmhhcHMg
aXQgaGFzIGJlZW4gZml4ZWQgKG9yIA0KYWx0ZXJuYXRpdmVseSwgSSBicm9rZSBpdCA6LSkpLiBZ
TSBvYnZpb3VzbHkgVnMuDQoNClJlZ2FyZHMsDQpSb2INCg0KX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX18NCklldGYgbWFpbGluZyBsaXN0DQpJZXRmQGlldGYu
b3JnDQpodHRwczovL3d3dzEuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pZXRmDQoNCg0K

------_=_NextPart_001_01C48F4B.339388FA
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgSFRUUC1FUVVJVj0iQ29udGVudC1UeXBlIiBDT05U
RU5UPSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPFRJVExFPkNvbnZlcnRlZCBmcm9tIFJp
Y2ggVGV4dDwvVElUTEU+DQoNCjxNRVRBIGNvbnRlbnQ9Ik1TSFRNTCA2LjAwLjI4MDAuMTQ1OCIg
bmFtZT1HRU5FUkFUT1I+PC9IRUFEPg0KPEJPRFkgdGV4dD0jMDAwMDAwIGJnQ29sb3I9I2ZmZmZm
Zj4NCjxESVY+PFNQQU4gY2xhc3M9NTYyNTIwODExLTMxMDgyMDA0PjxGT05UIGZhY2U9QXJpYWwg
Y29sb3I9IzAwMDBmZiANCnNpemU9Mj48U1RST05HPjxFTT5Ob3RlIHRoYXQgdGhlIGNvbnZlbnRp
b24gLyBncm91cCBjb2RlIGlzIElFRiBhbmQgbm90IElFVEYgYXMgDQpvbmUgbWF5IGV4cGVjdCEg
SXQgd29ya2VkIGZvciBtZSBhcyB3ZWxsLCBidXQgb25seSBvbiBzZWNvbmQgdHJ5IGJlY2F1c2Ug
b2YgDQp0aGlzLiA8L0VNPjwvU1RST05HPjwvRk9OVD48L1NQQU4+PC9ESVY+DQo8RElWPiZuYnNw
OzwvRElWPg0KPFAgZGlyPWx0cj48Rk9OVCBmYWNlPUFyaWFsIGNvbG9yPSMwMDAwZmYgDQpzaXpl
PTI+PFNUUk9ORz48RU0+UmVnYXJkcyw8L0VNPjwvU1RST05HPjwvRk9OVD48L1A+DQo8UCBkaXI9
bHRyPjxGT05UIGZhY2U9QXJpYWwgY29sb3I9IzAwMDBmZiANCnNpemU9Mj48U1RST05HPjxFTT5E
YW48L0VNPjwvU1RST05HPjwvRk9OVD48L1A+DQo8QkxPQ0tRVU9URSBkaXI9bHRyIA0Kc3R5bGU9
IlBBRERJTkctTEVGVDogNXB4OyBNQVJHSU4tTEVGVDogNXB4OyBCT1JERVItTEVGVDogIzAwMDBm
ZiAycHggc29saWQ7IE1BUkdJTi1SSUdIVDogMHB4Ij4NCiAgPERJViBjbGFzcz1PdXRsb29rTWVz
c2FnZUhlYWRlciBkaXI9bHRyIGFsaWduPWxlZnQ+PEZPTlQgZmFjZT1UYWhvbWEgDQogIHNpemU9
Mj4tLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLTxCUj48Qj5Gcm9tOjwvQj4gaWV0Zi1ib3VuY2Vz
QGlldGYub3JnIA0KICBbbWFpbHRvOmlldGYtYm91bmNlc0BpZXRmLm9yZ108Qj5PbiBCZWhhbGYg
T2YgPC9CPkpvaG4gDQogIExvdWdobmV5PEJSPjxCPlNlbnQ6PC9CPiAzMSBBdWd1c3QsIDIwMDQg
MTo0NCBQTTxCUj48Qj5Ubzo8L0I+IFJvYiANCiAgRXZhbnM8QlI+PEI+Q2M6PC9CPiBEYXZpZCBS
IE9yYW47IGlldGZAaWV0Zi5vcmc8QlI+PEI+U3ViamVjdDo8L0I+IHNlZW1zIHRvIA0KICB3b3Jr
IG5vdyBSZTogSG90ZWwgb25saW5lIHJlc2VydmF0aW9uczxCUj48QlI+PC9GT05UPjwvRElWPg0K
ICA8RElWIGFsaWduPWxlZnQ+SXQgc2VlbXMgdG8gYmUgd29ya2luZyBub3cuIE5pY2UgdG8gYm9v
ayBvbi1saW5lLCBmb3IgdGhvc2UgDQogIHdobyBhcmUgdGltZSB6b25lIGNoYWxsZW5nZWQuPC9E
SVY+DQogIDxESVYgYWxpZ249bGVmdD4mbmJzcDs8L0RJVj4NCiAgPERJViBhbGlnbj1sZWZ0Pkpv
aG48L0RJVj4NCiAgPERJViBhbGlnbj1sZWZ0PiZuYnNwOzwvRElWPg0KICA8RElWIGFsaWduPWxl
ZnQ+X19fX19fX19fX19fX19fXyBSZXBseSBoZWFkZXIgX19fX19fX19fX19fX19fXzwvRElWPg0K
ICA8RElWIGFsaWduPWxlZnQ+U3ViamVjdDogUmU6IEhvdGVsIG9ubGluZSByZXNlcnZhdGlvbnM8
L0RJVj4NCiAgPERJViBhbGlnbj1sZWZ0PkF1dGhvcjogIlJvYiBFdmFucyIgJmx0O3JoZUBub3Nj
LmphLm5ldCZndDs8L0RJVj4NCiAgPERJViBhbGlnbj1sZWZ0PkRhdGU6IDMwdGggQXVndXN0IDIw
MDQgMTA6NTc6MjIgUE08L0RJVj4NCiAgPERJViBhbGlnbj1sZWZ0PiZuYnNwOzwvRElWPg0KICA8
RElWIGFsaWduPWxlZnQ+Jmd0OyBkbyBub3Qgd29yayBhcyBhZHZlcnRpc2VkLiBBbGwgcm9vbXMg
c2hvdyBib29rZWQsIGRlc3BpdGUgDQogIHB1dHRpbmcgaW4gPEJSPiZndDsgY29ycmVjdCBkYXRl
cyBhbmQgZ3JvdXAgY29kZSBhcyBpbnN0cnVjdGVkLjxCUj48QlI+T2RkLiBJdCANCiAgd29ya2Vk
IGZvciBtZSBqdXN0IG5vdywgcGVyaGFwcyBpdCBoYXMgYmVlbiBmaXhlZCAob3IgPEJSPmFsdGVy
bmF0aXZlbHksIEkgDQogIGJyb2tlIGl0IDotKSkuIFlNIG9idmlvdXNseSANCiAgVnMuPEJSPjxC
Uj5SZWdhcmRzLDxCUj5Sb2I8QlI+PEJSPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fPC9ESVY+DQogIDxESVYgYWxpZ249bGVmdD5JZXRmIG1haWxpbmcgDQog
IGxpc3Q8QlI+SWV0ZkBpZXRmLm9yZzxCUj5odHRwczovL3d3dzEuaWV0Zi5vcmcvbWFpbG1hbi9s
aXN0aW5mby9pZXRmPEJSPjwvRElWPjwvQkxPQ0tRVU9URT48L0JPRFk+PC9IVE1MPg0K

------_=_NextPart_001_01C48F4B.339388FA--


--===============0948515696==
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

--===============0948515696==--



From ietf-bounces@ietf.org  Tue Aug 31 09:37:08 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17530;
	Tue, 31 Aug 2004 09:37:08 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C28qu-0003e5-VE; Tue, 31 Aug 2004 09:39:13 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C28mf-0005AE-IG; Tue, 31 Aug 2004 09:34:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C28j2-0004TB-Iz
	for ietf@megatron.ietf.org; Tue, 31 Aug 2004 09:31:04 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17143
	for <ietf@ietf.org>; Tue, 31 Aug 2004 09:31:03 -0400 (EDT)
Received: from newdev.eecs.harvard.edu ([140.247.60.212]
	helo=newdev.harvard.edu) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C28kx-0003Ts-Nr
	for ietf@ietf.org; Tue, 31 Aug 2004 09:33:07 -0400
Received: by newdev.harvard.edu (Postfix, from userid 501)
	id 2844A36CF5E; Tue, 31 Aug 2004 09:30:29 -0400 (EDT)
To: ietf@ietf.org
Message-Id: <20040831133029.2844A36CF5E@newdev.harvard.edu>
Date: Tue, 31 Aug 2004 09:30:29 -0400 (EDT)
From: sob@harvard.edu (Scott Bradner)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Subject: RE: How IETF treats contributors
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-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581


fwiw - the requirement from RFC 3667 is
   a. The Contribution properly acknowledges all major Contributors.  A
      major Contributor is any person who has materially or
      substantially contributed to the IETF Contribution.

I meant this to refer to people, not just document names

Scott

----
Christian sed:
  My personal practice, when writing such acknowledgement sections, is to
  write down the names of the individuals who contributed the idea, or
  contributed significant comments to a draft.


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


From ietf-bounces@ietf.org  Tue Aug 31 09:43:10 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17876;
	Tue, 31 Aug 2004 09:43:10 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C28wl-0003mJ-7f; Tue, 31 Aug 2004 09:45:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C28mi-0005Bi-E9; Tue, 31 Aug 2004 09:34:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C28kf-0004h1-6m
	for ietf@megatron.ietf.org; Tue, 31 Aug 2004 09:32:45 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17261
	for <ietf@ietf.org>; Tue, 31 Aug 2004 09:32:43 -0400 (EDT)
Received: from cyphermail.sandelman.ottawa.on.ca ([205.150.200.161]
	helo=noxmail.sandelman.ottawa.on.ca)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C28me-0003WH-7f
	for ietf@ietf.org; Tue, 31 Aug 2004 09:34:48 -0400
Received: from lox.sandelman.ottawa.on.ca
	(IDENT:root@lox.sandelman.ottawa.on.ca [205.150.200.178])
	by noxmail.sandelman.ottawa.on.ca (8.11.6p3/8.11.6) with ESMTP id
	i7VDKjU28339
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified
	FAIL); Tue, 31 Aug 2004 09:31:08 -0400 (EDT)
Received: from sandelman.ottawa.on.ca (desk.marajade.sandelman.ca
	[205.150.200.247])
	by lox.sandelman.ottawa.on.ca (8.11.6p3/8.11.6) with ESMTP id
	i7VDPjU09225
	(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified
	NO); Tue, 31 Aug 2004 09:26:01 -0400 (EDT)
Received: from sandelman.ottawa.on.ca (marajade [127.0.0.1])
	by sandelman.ottawa.on.ca (8.12.11/8.12.3/Debian-6.6) with ESMTP id
	i7VDHDBB004445; Tue, 31 Aug 2004 09:17:32 -0400
Received: from marajade.sandelman.ottawa.on.ca (mcr@localhost)
	by sandelman.ottawa.on.ca (8.12.11/8.12.3/Debian-6.6) with ESMTP id
	i7UHW0B8030942; Mon, 30 Aug 2004 13:32:08 -0400
To: ietf@ietf.org
In-Reply-To: Message from Iljitsch van Beijnum <iljitsch@muada.com> of "Mon,
	30 Aug 2004 10:58:14 +0200."
	<BA6FFF85-FA62-11D8-9464-000A95CD987A@muada.com> 
References: <412D268D.3020402@thinkingcat.com>
	<00a301c48e04$dcac4fb0$3220dfa9@consulintel.es>
	<0F699F3B4E3B87D97564FB33@B50854F0A9192E8EC6CDA126>
	<BA6FFF85-FA62-11D8-9464-000A95CD987A@muada.com> 
X-Mailer: MH-E 7.4.2; nmh 1.0.4+dev; XEmacs 21.4 (patch 15)
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Mon, 30 Aug 2004 13:32:00 -0400
Message-ID: <30941.1093887120@marajade.sandelman.ottawa.on.ca>
From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
X-Spam-Score: 2.3 (++)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: Harald Tveit Alvestrand <harald@alvestrand.no>,
        Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: Venue selection (Re: Options for IETF administrative
	restructuring) 
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-Score: 2.3 (++)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2

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


>>>>> "Iljitsch" == Iljitsch van Beijnum <iljitsch@muada.com> writes:
    Iljitsch> - meeting status: decided, under consideration, open -
    Iljitsch> date specific constraints, such as the continent that has
    Iljitsch> been selected - up to date numbers for hotel rooms,
    Iljitsch> meeting rooms, terminal room and so on

  I second this.
  I also welcome the information that Vancouver was booked. That's
important to understand.

- --
]     "Elmo went to the wrong fundraiser" - The Simpson         |  firewalls  [
]   Michael Richardson,    Xelerance Corporation, Ottawa, ON    |net architect[
] mcr@xelerance.com      http://www.sandelman.ottawa.on.ca/mcr/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Finger me for keys

iQCVAwUBQTNkj4qHRg3pndX9AQHFGAP/fYITCf2FSeynb8WBmIYcXdU9Jh6+GZ/2
KmpQYKf5fiFQf3RfzK5d0t3MueQQE+rAZeHnWZrhEIL6bHLLFExizZ2HdwNnQ2Pi
38et1C3oa/uvXffXk/z9yVHhCeI/gqr2KHTUdG7+5NpW/CikWeTZ/jnnL+jFMB99
XPZDea1m5Zs=
=0l7p
-----END PGP SIGNATURE-----

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


From ietf-bounces@ietf.org  Tue Aug 31 10:46:54 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22782;
	Tue, 31 Aug 2004 10:46:54 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C29wR-00053c-FY; Tue, 31 Aug 2004 10:49:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C29pc-0004v4-RX; Tue, 31 Aug 2004 10:41:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C29oz-0004lT-SP
	for ietf@megatron.ietf.org; Tue, 31 Aug 2004 10:41:18 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22439
	for <ietf@ietf.org>; Tue, 31 Aug 2004 10:41:15 -0400 (EDT)
Received: from calcite.rhyolite.com ([192.188.61.3])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C29qy-0004vy-9h
	for ietf@ietf.org; Tue, 31 Aug 2004 10:43:21 -0400
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.13.1/8.13.1) id i7VEeiPX083988
	for ietf@ietf.org env-from <vjs>;
	Tue, 31 Aug 2004 08:40:44 -0600 (MDT)
Date: Tue, 31 Aug 2004 08:40:44 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200408311440.i7VEeiPX083988@calcite.rhyolite.com>
To: ietf@ietf.org
References: <20040831104016.4bf3d0c6.olaf@ripe.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Subject: Re: How IETF treats contributors
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-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64

> From: "Olaf M. Kolkman" 

> I'd like to expand on what Dean said: "Credit and attribution is about
> intellectual honesty [ and _courtesy_ ] not about copyright law".

Ok, but in the case at hand, 

  - None of the versions of Mr. Danish's proposal that I've seen
     credited Mr. Vixie's document or some others than preceded Mr.
     Danish's work.  I think that was due to ignornance and disinterest
     instead of malice, but it does reduce Mr. Danish's standing to 
     more credit than he already receives.

  - Mr. Danish's proposal was always an obvious non-starter for various
     reasons, including the requirement for defining new DNS RR types
     before it could be deployed or even tested.

  - Mr. Vixie's proposal is a lot closer to what I understand of the
     current MARID mechanisms than Mr. Danish's proposal.

  - It is ironic or something that few people who are openly concerned
     about credit for their work have enviable reputations.  They tend
     to be inventors of such as IPv8.

  - As far as solving the spam problem is concerned, RMX, SPF, the
     commercial proposals, the MARID proposals, and all other sender
     authentication mechanisms are more like IPv8 than IPv6.  Squashing
     the current modes of spam forgery will have just as much effect
     as the squashing years ago of the forgery of 8-digit user names
     @aol.com.  The new anti-forgery mechanisms are more general than
     the old regular expressions, but sender forgery is not a required
     aspect of spam.  Some large spammers have long been using domain
     names that they register, use for literally a few days, and
     discard.  For example, some time ago I grew bored with accumulating
     the domain names of one such operation in
     http://www.rhyolite.com/anti-spam/bin/group.cgi?group=151
     Some of the domain names of smaller (in counts of names) operations
     are in http://www.rhyolite.com/anti-spam/bin/group.cgi?group=197
     http://www.rhyolite.com/anti-spam/bin/group.cgi?group=30
     http://www.rhyolite.com/anti-spam/bin/group.cgi?group=140 and
     http://www.rhyolite.com/anti-spam/bin/group.cgi?group=165
     Spammers can deploy sender authentication mechanisms far faster
     than their victims.

  - This thread has the wrong subject.  It should be more like
    "How some would-be contributors treat the IETF."


Vernon Schryver    vjs@rhyolite.com

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


From ietf-bounces@ietf.org  Tue Aug 31 12:51:22 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04290;
	Tue, 31 Aug 2004 12:51:22 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C2Bsu-0000JW-OM; Tue, 31 Aug 2004 12:53:29 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C2BaQ-0001Re-H0; Tue, 31 Aug 2004 12:34:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C2B5A-0004CA-SC
	for ietf@megatron.ietf.org; Tue, 31 Aug 2004 12:02:04 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28038
	for <ietf@ietf.org>; Tue, 31 Aug 2004 12:02:02 -0400 (EDT)
Received: from magus.nostrum.com ([208.21.192.130] ident=root)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2B7A-0006jY-3y
	for ietf@ietf.org; Tue, 31 Aug 2004 12:04:09 -0400
Received: from [10.10.108.16] ([65.119.52.228]) (authenticated bits=0)
	by magus.nostrum.com (8.12.11/8.12.11) with ESMTP id i7VG1t7Z073274
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO)
	for <ietf@ietf.org>; Tue, 31 Aug 2004 11:01:55 -0500 (CDT)
	(envelope-from ben@nostrum.com)
Mime-Version: 1.0 (Apple Message framework v619)
In-Reply-To: <AAB4B3D3CF0F454F98272CBE187FDE2F056B3416@is0004avexu1.global.avaya.com>
References: <AAB4B3D3CF0F454F98272CBE187FDE2F056B3416@is0004avexu1.global.avaya.com>
Message-Id: <1B4304A2-FB67-11D8-9375-000D93B0AE1A@nostrum.com>
From: Ben Campbell <ben@nostrum.com>
Date: Tue, 31 Aug 2004 11:02:06 -0500
To: ietf@ietf.org
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027
Subject: Re: seems to work now Re: Hotel online reservations
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="===============0992894649=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68ba2b07ef271dba6ee42a93832cfa4c


--===============0992894649==
Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-25--303190436;
	protocol="application/pkcs7-signature"


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

I had the same problem at first. There are _two_ fields, an offer code=20=

and a group code. The offer code comes first. At first, I made the=20
mistake of putting "IEF" in the offer code field, and was told there=20
were no rooms. When I put it in the group code field, it worked fine.

On Aug 31, 2004, at 6:11 AM, Romascanu, Dan (Dan) wrote:

> Note that the convention / group code is IEF and not IETF as one may=20=

> expect! It worked for me as well, but only on second try because of=20
> this.
>  =A0
>
> Regards,
>
> Dan
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org]On Behalf Of=20=

> John Loughney
> Sent: 31 August, 2004 1:44 PM
> To: Rob Evans
> Cc: David R Oran; ietf@ietf.org
> Subject: seems to work now Re: Hotel online reservations
>
> It seems to be working now. Nice to book on-line, for those who are=20
> time zone challenged.
> =A0
> John
> =A0
> ________________ Reply header ________________
> Subject: Re: Hotel online reservations
> Author: "Rob Evans" <rhe@nosc.ja.net>
> Date: 30th August 2004 10:57:22 PM
> =A0
> > do not work as advertised. All rooms show booked, despite putting in
> > correct dates and group code as instructed.
>
> Odd. It worked for me just now, perhaps it has been fixed (or
> alternatively, I broke it :-)). YM obviously Vs.
>
> Regards,
> Rob
>
> _______________________________________________
> 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

--Apple-Mail-25--303190436
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Disposition: attachment;
	filename=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGEjCCAssw
ggI0oAMCAQICAwwdSDANBgkqhkiG9w0BAQQFADBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhh
d3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt
YWlsIElzc3VpbmcgQ0EwHhcNMDQwNDEyMjA0NTUyWhcNMDUwNDEyMjA0NTUyWjBBMR8wHQYDVQQD
ExZUaGF3dGUgRnJlZW1haWwgTWVtYmVyMR4wHAYJKoZIhvcNAQkBFg9iZW5Abm9zdHJ1bS5jb20w
ggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDGFv8c1i8a9NXiEohMEryzypOcyz39k8PN
WxTS4F45JSYwQ0/RAZ4vaemHCyJaUc7tc5DN3o7zl2oaqQuOIrvnjk79ILGJVfRgwt+uGDIGyaSM
YmBeKXSdawFiJdk5jGtMzlgF8tzJzc4do5Mzl5YS39AR8mj8PF4zEgIlYYkKXBByHQ2jPA0qVfm/
Aj71RdYZyDAD4P7TyW9jKvZCl7KCfajar1llEQVj+kWMvt/3AE6mwAHXfkU7nL9XzLvGSnMUJvYx
hq3UDju4IacXsYFw2oLb4LQdvwP4Lbg6qdp08h59+TkHlV6WNdt3ggM9C/cGQTDCa0CVJsr+76Dm
mPorAgMBAAGjLDAqMBoGA1UdEQQTMBGBD2JlbkBub3N0cnVtLmNvbTAMBgNVHRMBAf8EAjAAMA0G
CSqGSIb3DQEBBAUAA4GBAApFAg5tsI2OhByoUglTZ+ip3M/1xfWDsCNsDB4+HtnH9fZfKkrkGp4e
JQyuvl5VhvW67qYU6wEPMD0EKoWDU3v7l1huzR7Cpkf7n21y4LLG+VxldYiA3SEkv7RBPhhVhdMl
sHwNZAYyVXFCdnvuVjfeytdAeXK6vzcaUvo9EwkHMIIDPzCCAqigAwIBAgIBDTANBgkqhkiG9w0B
AQUFADCB0TELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2Fw
ZSBUb3duMRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYGA1UECxMfQ2VydGlmaWNhdGlv
biBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIENB
MSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFpbEB0aGF3dGUuY29tMB4XDTAzMDcxNzAw
MDAwMFoXDTEzMDcxNjIzNTk1OVowYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25z
dWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1
aW5nIENBMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDEpjxVc1X7TrnKmVoeaMB1BHCd3+n/
ox7svc31W/Iadr1/DDph8r9RzgHU5VAKMNcCY1osiRVwjt3J8CuFWqo/cVbLrzwLB+fxH5E2JCoT
zyvV84J3PQO+K/67GD4Hv0CAAmTXp6a7n2XRxSpUhQ9IBH+nttE8YQRAHmQZcmC3+wIDAQABo4GU
MIGRMBIGA1UdEwEB/wQIMAYBAf8CAQAwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL2NybC50aGF3
dGUuY29tL1RoYXd0ZVBlcnNvbmFsRnJlZW1haWxDQS5jcmwwCwYDVR0PBAQDAgEGMCkGA1UdEQQi
MCCkHjAcMRowGAYDVQQDExFQcml2YXRlTGFiZWwyLTEzODANBgkqhkiG9w0BAQUFAAOBgQBIjNFQ
g+oLLswNo2asZw9/r6y+whehQ5aUnX9MIbj4Nh+qLZ82L8D0HFAgk3A8/a3hYWLD2ToZfoSxmRsA
xRoLgnSeJVCUYsfbJ3FXJY3dqZw5jowgT2Vfldr394fWxghOrvbqNOUQGls1TXfjViF4gtwhGTXe
JLHTHUb/XV9lTzGCAucwggLjAgEBMGkwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBD
b25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJ
c3N1aW5nIENBAgMMHUgwCQYFKw4DAhoFAKCCAVMwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAc
BgkqhkiG9w0BCQUxDxcNMDQwODMxMTYwMjA2WjAjBgkqhkiG9w0BCQQxFgQUB4MZGymd+TRFTElw
Ner/XXUrMn0weAYJKwYBBAGCNxAEMWswaTBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3Rl
IENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWls
IElzc3VpbmcgQ0ECAwwdSDB6BgsqhkiG9w0BCRACCzFroGkwYjELMAkGA1UEBhMCWkExJTAjBgNV
BAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25h
bCBGcmVlbWFpbCBJc3N1aW5nIENBAgMMHUgwDQYJKoZIhvcNAQEBBQAEggEAn9jqUo8rQk3aalsT
eTxT6oHr1AT1Y8+us77Q5XEb58w0Xa/ILyN4izTvQij0DoxPsjptfdfvKf8NVV0sBxDH8NeshAgH
bRDoUJbMTGql18cRER6Mt1XLACjfwV2uHioCbHk3H4H5F8vY7kNasleHQXRtNyUmc5VPIWSYdxzv
gQgh+QHR879YP3okGd4yDwM/iYmdlJ07Ab+jS9OKdSCYrkGIYvYGVi7O9SwdJ3FtYqSdw9vzQuna
+AE5hfB2TAO3UCWF07gYOfJWa8vyT+9d58sN0324lbpfj5ThW8P1lYjym9L6nlWgCf7QgmHJc+Id
DnIDdbLNPthaJ57RwgPU0gAAAAAAAA==

--Apple-Mail-25--303190436--



--===============0992894649==
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

--===============0992894649==--




From ietf-bounces@ietf.org  Tue Aug 31 13:35:50 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08351;
	Tue, 31 Aug 2004 13:35:50 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C2CZy-0001Y6-1C; Tue, 31 Aug 2004 13:37:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C2COV-0008Jn-OL; Tue, 31 Aug 2004 13:26:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C2CCk-0005Y6-Mw
	for ietf@megatron.ietf.org; Tue, 31 Aug 2004 13:13:58 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06142
	for <ietf@ietf.org>; Tue, 31 Aug 2004 13:13:55 -0400 (EDT)
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2CEl-0000vY-7l
	for ietf@ietf.org; Tue, 31 Aug 2004 13:16:03 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id 0FE5913E13; Tue, 31 Aug 2004 17:13:26 +0000 (GMT)
To: ietf@ietf.org
References: <p0611040bbd59466aa292@[129.46.227.161]>
	<Pine.LNX.4.44.0408301449500.23504-100000@sokol.elan.net>
From: Paul Vixie <vixie@vix.com>
Date: 31 Aug 2004 17:13:25 +0000
In-Reply-To: <Pine.LNX.4.44.0408301449500.23504-100000@sokol.elan.net>
Message-ID: <g38ybvjkne.fsf@sa.vix.com>
Lines: 92
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-Score: 0.0 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Subject: Re: How IETF treats contributors
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-Score: 0.0 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db

it's hard to understand why any of you bother to respond to dean anderson;
his goals in participating here are manifestly incompatible with most others'.
the worst part is, while i never see dean's words directly (he and bernstein
and some others are on an internet that my user agents keep me from seeing),
i end up seeing his text when other people respond to it.  ick.  please stop.

> > >The idea came from David Green, and Vixie says it originated from Jim
> > >Miller in 1998.  Vixie had little or nothing to do with it. Why the draft
> > >claims the earliest known work is due to Vixie is unclear.
> > >
> > >		--Dean

> I've never heard before of David Green as being source of the idea, if
> he's still around, we may ask him and Vixie and Jim Miller about the
> exact details and if they are satisified with current information in
> acknolidgement sections of MARID drafts. But based on message from
> namedroppers sited by Dean, it seems that David Green came up with idea
> separate and already after Vixie wrote original "Repudiating Mail From"
> draft.
> 
> William Leibzon

here's what happened.  one day i was walking down the net minding my own
business, when all of a sudden, the following message appeared in my inbox:

        Date: Sun, 14 Dec 1997 23:44:54 -0500 (EST)
        From: Jim Miller <jmiller@jcmco.com>
        To: paul@vix.com
        Subject: An idea & congrats on RBL

        Mr. Vixie,

        ...

        May I offer an idea for your suggestions and opinion?

        My idea is this: extend the use of DNS as a spam blocking mechanism
        to support a rudimentary form of "authentication".... That is, use
        DNS to list the machines that are "valid" *senders* of mail from a
        domain.

        ...

        I propose that the entities participating in this "idea" define a
        well-known name in their DNS server - for each of their domains -
        which lists all of the systems that will be sending mail from that
        domain.  This would be along the lines of an alias such as "mail",
        "ftp", or "www".

        For the purposes of this example, I'll use the name "outbound-smtp"
        and the domain "foo.com":

        foo.com.	 IN	 SOA	....whatever....

        outbound-smtp    IN	 MX	10 host1
			 IN	 MX	20 host2
			 IN	 MX	30 host3
	
	host1		 IN	 A	10.1.2.3
	host2		 IN	 A	10.2.3.4
	host3		 IN	 A	10.3.4.5

	By creating the "outbound-smtp" record, I, as the operator of
        "foo.com", indicate that the ONLY systems that are supposed to be
        sending Internet mail with an address of "@foo.com" will be host1,
        host2, and host3.foo.com.  The fact that I used MX records is in no
        way related to the true purpose of MX records -- it's just the RR
        that I chose to provide a "list".

	Now, for how this would be used...

        ...

no mention of david green.  and i'm sorry for the confusion, it was 1997,
not 1998 as i've been reporting.  for the record, i first heard the idea
from jim miller, in the e-mail excerpted above, and it was a good idea,
and if we'd written it up and widely deployed it in ~1997, e-mail forgery
would be dead by now and we'd working on other more important issues like
bonded expressions of intent.  instead i see MARID making this whole thing
way more complicated than it needs to be, with 2005 as the earliest date
upon which e-mail forgery will be dead.

so, i did one duty, by acknowledging that the idea was not my own.  but, i
failed another duty, which was to push hard on getting a good idea shipped.
writing <http://sa.vix.com/~vixie/mailfrom.txt> and posting it to
namedroppers was not nearly what was required to help kill e-mail forgery.
i'm currently failing another duty, which is to try to stop MARID from
rubber-stamping ~SPF and to try to stop MARID from using either TXT RRs or
a new RRtype.  i've found that you just can't stop newbies from wanting to
make their own mistakes.  (like teenagers in that way.)
-- 
Paul Vixie

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


From ietf-bounces@ietf.org  Tue Aug 31 13:39:29 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08757;
	Tue, 31 Aug 2004 13:39:29 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C2CdU-0001fV-D4; Tue, 31 Aug 2004 13:41:37 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C2COq-0008U7-Vp; Tue, 31 Aug 2004 13:26:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C2CGU-0006Q7-73
	for ietf@megatron.ietf.org; Tue, 31 Aug 2004 13:17:50 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06545
	for <ietf@ietf.org>; Tue, 31 Aug 2004 13:17:47 -0400 (EDT)
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2CIV-000126-HP
	for ietf@ietf.org; Tue, 31 Aug 2004 13:19:55 -0400
Received: by sa.vix.com (Postfix, from userid 716)
	id 3273213E11; Tue, 31 Aug 2004 17:17:19 +0000 (GMT)
To: ietf@ietf.org
References: <B1F1256E2FAEA049B5F11549870302B16646DE@USEX.think3.com>
From: Paul Vixie <vixie@vix.com>
Date: 31 Aug 2004 17:17:19 +0000
In-Reply-To: <B1F1256E2FAEA049B5F11549870302B16646DE@USEX.think3.com>
Message-ID: <g34qmjjkgw.fsf@sa.vix.com>
Lines: 14
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-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Subject: Re: How IETF treats contributors
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-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126

Nick.Carter@think3.com ("Nick Carter") writes:

> ... You could contest it saying it was an excrescence of Vixie's work,
> but the details do not exist in Vixie's work.  As noted with Dean, Vixies
> work is implausible and therefore credit should not be given. All work
> submitted should be punctilio and of protocol.

of the three of us (you, me, dean) i have a pretty clear idea who i'd trust
the most to advise anybody about what can or cannot be done in SMTP or DNS.

however, i'm quite interested in feedback as to the plausibility of miller's
idea, which i expressed at <http://sa.vix.com/~vixie/mailfrom.txt>.  thanks!
-- 
Paul Vixie

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


From ietf-bounces@ietf.org  Tue Aug 31 15:04:22 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16408;
	Tue, 31 Aug 2004 15:04:22 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C2Dxe-0003mT-52; Tue, 31 Aug 2004 15:06:30 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C2Dt7-0006ru-NJ; Tue, 31 Aug 2004 15:01:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C2Drf-0005Yf-JA
	for ietf@megatron.ietf.org; Tue, 31 Aug 2004 15:00:21 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16141
	for <ietf@ietf.org>; Tue, 31 Aug 2004 15:00:18 -0400 (EDT)
Received: from sklave3.rackland.de ([213.133.101.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2Dtg-0003hT-Dm
	for ietf@ietf.org; Tue, 31 Aug 2004 15:02:25 -0400
Received: from andromeda (uucp@localhost)
	by sklave3.rackland.de (8.12.10/8.12.10/Debian-1) with BSMTP id
	i7VJ05PH017570; Tue, 31 Aug 2004 21:00:05 +0200
Received: (from hadmut@localhost)
	by andromeda.dresden.danisch.de (8.12.11/8.12.11/Debian-5) id
	i7VIw2BW023241; Tue, 31 Aug 2004 20:58:02 +0200
From: Hadmut Danisch <hadmut@danisch.de>
Date: Tue, 31 Aug 2004 20:58:02 +0200
To: Dean Anderson <dean@av8.com>
Message-ID: <20040831185802.GA22942@danisch.de>
References: <20040830090627.GA22982@danisch.de>
	<Pine.LNX.4.44.0408301607571.28223-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.0408301607571.28223-100000@cirrus.av8.net>
User-Agent: Mutt/1.5.6+20040523i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: ietf@ietf.org
Subject: Re: How IETF treats contributors
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-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352

Dean,

On Mon, Aug 30, 2004 at 04:43:57PM -0400, Dean Anderson wrote:
> 
> That said, it is a reprehensible shame that you are not being given credit
> for your work in SPF and RMX.

Thanks for that.


> We demonstrated that RMX did not solve the problem it set out to
> solve.

I do not remember that anyone did demonstrate that. 


On the contrary, RMX solved a major problem in contrast to the current
SenderID proposal.  Many people, including myself, do receive
significant more false bounce messages and spam complaints than 
spam messages, because spammers abuse my e-mail address or domain. 
Therefore RMX was designed to verify the envelope sender and it
does that job.

In contrast, SenderID does not solve that problem. Guess why.  





> No doubt, the
> MARID group chairs do not want to appear to simply re-hash RMX under a
> different name. In order to avoid that, they have to pretend it wasn't
> written by you.


This might be true.


Hadmut

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


From ietf-bounces@ietf.org  Tue Aug 31 15:43:24 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20859;
	Tue, 31 Aug 2004 15:43:24 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C2EZQ-0004lc-Gm; Tue, 31 Aug 2004 15:45:32 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C2ESM-0001Y8-Od; Tue, 31 Aug 2004 15:38:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C2EKZ-0006Bu-Qv
	for ietf@megatron.ietf.org; Tue, 31 Aug 2004 15:30:12 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19943
	for <ietf@ietf.org>; Tue, 31 Aug 2004 15:30:10 -0400 (EDT)
Received: from sklave3.rackland.de ([213.133.101.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2EMa-0004TQ-VZ
	for ietf@ietf.org; Tue, 31 Aug 2004 15:32:18 -0400
Received: from andromeda (uucp@localhost)
	by sklave3.rackland.de (8.12.10/8.12.10/Debian-1) with BSMTP id
	i7VJU5C9018306; Tue, 31 Aug 2004 21:30:05 +0200
Received: (from hadmut@localhost)
	by andromeda.dresden.danisch.de (8.12.11/8.12.11/Debian-5) id
	i7VJR6ea024501; Tue, 31 Aug 2004 21:27:06 +0200
From: Hadmut Danisch <hadmut@danisch.de>
Date: Tue, 31 Aug 2004 21:27:06 +0200
To: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-ID: <20040831192706.GB22942@danisch.de>
References: <20040831104016.4bf3d0c6.olaf@ripe.net>
	<200408311440.i7VEeiPX083988@calcite.rhyolite.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200408311440.i7VEeiPX083988@calcite.rhyolite.com>
User-Agent: Mutt/1.5.6+20040523i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Cc: ietf@ietf.org
Subject: Re: How IETF treats contributors
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-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976


[ Sorry, but I couldn't resists to give a nasty side comment:
  Vernon Shryver was one of the persons who most unobjectively and 
  maliciously attacked RMX and any other proposal against Spam. 
  He was displeased because his own invention has major flaws, 
  and that I showed in the RMX draft that his proposal can and 
  is abused for censoring e-mail traffic. His posting appears
  to me as if he took the opportunity for revenge. I'll 
  nevertheless reply to correct some of his misleading and wrong
  statements. ]


First, my name is Danisch, not Danish. 


On Tue, Aug 31, 2004 at 08:40:44AM -0600, Vernon Schryver wrote:
>
>   - None of the versions of Mr. Danish's proposal that I've seen
>      credited Mr. Vixie's document or some others than preceded Mr.
>      Danish's work.  I think that was due to ignornance and disinterest
>      instead of malice, but it does reduce Mr. Danish's standing to 
>      more credit than he already receives.


This is pure nonsense. The same kind of defamation he already used 
on the early asrg mailing list.

I did not cite or credit anyone else because at the time I wrote RMX
I did not know of anyone else's work in this field. RMX is in no way 
derived from or based on anyone else's work. If anyone has any doubt 
about this, I can show that I was working on organizational security, 
especially in context of e-mail, that RMX is just the logical 
continuation of my former work and that I had very good reasons to 
design RMX the way it is. 

How should I have cited or credited someone else's work without
knowing it? And why?

In contrast, SPF and CallerID were provably based on RMX, the authors
were familiar with RMX, and the first version of SPF was explicetely
announced to cover RMX. 



>   - Mr. Danish's proposal was always an obvious non-starter for various
>      reasons, including the requirement for defining new DNS RR types
>      before it could be deployed or even tested.

RMX is not the requirement for defining the new DNS RR type. This was
just the proposal how to implement it. 

That's the illogical point of the story: SPF was derived from RMX by 
simply omitting the invention of a new DNS RR type. This didn't change
the idea of RMX, just changed the way to implement it a little
bit. And the same time certain people claimed that SPF is 'new' and
that RMX is wrong because it required a new DNS RR type. 

Typical way of intentional misinformation.




>   - It is ironic or something that few people who are openly concerned
>      about credit for their work have enviable reputations.  They tend
>      to be inventors of such as IPv8.

???

Does anyone have a clue what this is about?






Hadmut Danisch

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


From ietf-bounces@ietf.org  Tue Aug 31 16:31:10 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29384;
	Tue, 31 Aug 2004 16:31:10 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C2FJf-0007OM-KP; Tue, 31 Aug 2004 16:33:19 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C2F89-00010o-HE; Tue, 31 Aug 2004 16:21:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C2EUE-0002Ws-0G
	for ietf@megatron.ietf.org; Tue, 31 Aug 2004 15:40:10 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20653
	for <ietf@ietf.org>; Tue, 31 Aug 2004 15:40:08 -0400 (EDT)
Received: from sklave3.rackland.de ([213.133.101.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2EWF-0004hv-6H
	for ietf@ietf.org; Tue, 31 Aug 2004 15:42:16 -0400
Received: from andromeda (uucp@localhost)
	by sklave3.rackland.de (8.12.10/8.12.10/Debian-1) with BSMTP id
	i7VJe73o018597; Tue, 31 Aug 2004 21:40:07 +0200
Received: (from hadmut@localhost)
	by andromeda.dresden.danisch.de (8.12.11/8.12.11/Debian-5) id
	i7VJcZIh024968; Tue, 31 Aug 2004 21:38:35 +0200
From: Hadmut Danisch <hadmut@danisch.de>
Date: Tue, 31 Aug 2004 21:38:35 +0200
To: Ted Hardie <hardie@qualcomm.com>
Message-ID: <20040831193835.GC22942@danisch.de>
References: <20040830090627.GA22982@danisch.de>
	<p06110403bd5906118d89@[129.46.227.161]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <p06110403bd5906118d89@[129.46.227.161]>
User-Agent: Mutt/1.5.6+20040523i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: ietf@ietf.org
Subject: Re: How IETF treats contributors
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-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17

On Mon, Aug 30, 2004 at 09:51:54AM -0700, Ted Hardie wrote:
>
> It was cited as an input draft to the MARID working group,
> and it was recommended for publication as an Experimental RFC with
> the other input drafts that came out of the ASRG process.


Thanks for that information. I didn't know that. 

The former ASRG co-chair who asked me to submit RMX as an 
exp RFC is not co-chair anymore. I asked the MARID chairs 
whether they know about the current state of the submission. 
I understood the answer in the way that RMX will not be 
published as an RFC anymore. 



> In other words,
> the IETF took you up on your offer to consider the draft seriously and
> to use it as input into the evolving standard in this area.

I highly appreciate that. Thanks.

It is just that I didn't know that and that this doesn't match the 
MARID chairs statements.



regards
Hadmut

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


From ietf-bounces@ietf.org  Tue Aug 31 16:48:32 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01265;
	Tue, 31 Aug 2004 16:48:32 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C2FaS-0007uh-Uz; Tue, 31 Aug 2004 16:50:42 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C2FFG-0005ux-97; Tue, 31 Aug 2004 16:28:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C2ExE-0002vU-Hn
	for ietf@megatron.ietf.org; Tue, 31 Aug 2004 16:10:08 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25532
	for <ietf@ietf.org>; Tue, 31 Aug 2004 16:10:06 -0400 (EDT)
From: bill@strahm.net
Received: from smtpout01-03.mesa1.secureserver.net ([64.202.165.78])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1C2EzG-0006K7-59
	for ietf@ietf.org; Tue, 31 Aug 2004 16:12:15 -0400
Received: (qmail 11568 invoked from network); 31 Aug 2004 20:09:33 -0000
Received: from unknown (HELO webmail01.mesa1.secureserver.net) (64.202.166.114)
	by smtpout01-03.mesa1.secureserver.net with SMTP;
	31 Aug 2004 20:09:33 -0000
Received: (qmail 20007 invoked by uid 99); 31 Aug 2004 20:09:33 -0000
Message-ID: <20040831200933.20006.qmail@webmail01.mesa1.secureserver.net>
Date: Tue, 31 Aug 2004 13:09:33 -0700
To: "Romascanu,Dan \(Dan\)" <dromasca@avaya.com>
MIME-Version: 1.0
Content-Type: TEXT/plain; CHARSET=US-ASCII
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Cc: David R Oran <oran@cisco.com>, ietf@ietf.org,
        John Loughney <john.loughney@kolumbus.fi>
Subject: RE: seems to work now Re: Hotel online reservations
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-Score: 0.3 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad

IEF ??? -> Internet Engineering Force ?

Does that imply that we no longer have any Tasks ???

Uhm... I'm going to return you to your regularly scheduled trolls now

Bill


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


From ietf-bounces@ietf.org  Tue Aug 31 20:28:03 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17570;
	Tue, 31 Aug 2004 20:28:03 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1C2J0t-00044W-23; Tue, 31 Aug 2004 20:30:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C2IsQ-0001C4-T0; Tue, 31 Aug 2004 20:21:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C2Iij-0006Zf-2V
	for ietf@megatron.ietf.org; Tue, 31 Aug 2004 20:11:25 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15850
	for <ietf@ietf.org>; Tue, 31 Aug 2004 20:11:23 -0400 (EDT)
From: ned.freed@mrochek.com
Received: from mauve.mrochek.com ([209.55.107.55])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2Ikm-0003ZM-V6
	for ietf@ietf.org; Tue, 31 Aug 2004 20:13:34 -0400
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243)
	id <01LEBHXX0X9S0087C0@mauve.mrochek.com> for ietf@ietf.org; Tue,
	31 Aug 2004 17:11:14 -0700 (PDT)
Date: Tue, 31 Aug 2004 17:10:42 -0700 (PDT)
In-reply-to: "Your message dated Mon, 30 Aug 2004 15:18:17 -0700"
	<DAC3FCB50E31C54987CD10797DA511BA0AB9C1B6@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
To: Christian Huitema <huitema@windows.microsoft.com>
Message-id: <01LEBLH4LFTU0087C0@mauve.mrochek.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=us-ascii
Content-transfer-encoding: 7BIT
References: <DAC3FCB50E31C54987CD10797DA511BA0AB9C1B6@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
X-Spam-Score: 0.3 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 7BIT
Cc: Ted Hardie <hardie@qualcomm.com>, ietf@ietf.org,
        Hadmut Danisch <hadmut@danisch.de>
Subject: RE: How IETF treats contributors
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-Score: 0.3 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: 7BIT

> >     9. Acknowledgements
> >
> >        Variations on the idea of using a DNS record to check the
> > legitimacy
> >        of an email address have occurred multiple times. The earliest
> > known
> >        work is [Vixie]; others include [RMX], [SPF] and [CallerID].
> >
> >        The current document borrows heavily from each of the above,
> and
> >        incorporates ideas proposed by many members of the MARID
> working
> >       group.  The contributions of each of the above are gratefully
> >       acknowledged.

> Ted,

> My personal practice, when writing such acknowledgement sections, is to
> write down the names of the individuals who contributed the idea, or
> contributed significant comments to a draft.

> It is true that if one follows references such as [RMX] one eventually
> find the list of authors of the proposal, but they are still at least
> one level of indirection away. The MARID draft could just as well say
> something like "The earliest work was submitted to the IETF by Paul
> Vixie [Vixie]; others include ..." ASCII bits are cheap.

This would be a very reasonable thing to do IMO.

				Ned

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


