From owner-ietf-outbound  Tue Feb  1 07:30:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA12571
	for ietf-outbound.10@ietf.org; Tue, 1 Feb 2000 07:30:01 -0500 (EST)
Received: from camaleon.lander.es ([212.95.212.2])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA12316
	for <ietf@ietf.org>; Tue, 1 Feb 2000 07:24:27 -0500 (EST)
Received: (qmail 21176 invoked from network); 1 Feb 2000 12:23:51 -0000
Received: from lince.lander.es (195.76.46.35)
  by camaleon.lander.es with SMTP; 1 Feb 2000 12:23:51 -0000
Received: (qmail 26642 invoked from network); 1 Feb 2000 12:22:13 -0000
Received: from ppp-46-247.lander.es (HELO salva) (195.76.46.247)
  by lince.lander.es with SMTP; 1 Feb 2000 12:22:13 -0000
Message-Id: <3.0.6.32.20000201132748.007d78d0@lince.lander.es>
X-Sender: svidal@lince.lander.es (Unverified)
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32)
Date: Tue, 01 Feb 2000 13:27:48 +0100
To: Gordon Cook <cook@cookreport.com>
From: Salvador Vidal <svidal@lander.es>
Subject: Re:...the Internet 2000 Citizens 0
Cc: ietf@ietf.org
In-Reply-To: <v04210101b4b299b39e9a@[192.168.0.1]>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id HAA12316
Content-Transfer-Encoding: 8bit

Hello Gordon and all,

At 19:16 24/01/00 -0500, you wrote:
>http://cookreport.com/ipeverywhere.shtml

A report about Internet politics with sense and without censorship!, Is
Echelon on Strike?

>At the beginning of the new millennium the Internet is globally 
>triumphant.  Blindly embraced by politicians who do not >understand it

Politicians ignorance is not problem, they have our money to have the
service of the best consultants, but independence, are able the politicians
to do independent decisions when they need big boys money for their
electoral campains?

>we have traveled from the certainty of knowledge that publishing >is 
>an activity whereby elite gate keepers package knowledge for the 
>masses to a world where every computer owner can become a >publisher. 

Yes, but the big boys remain the control of information, so citizens are
able to publish but not to find the independent publishers if big boys
donīt want, there are some inciatives to break this elite control of
information like link exchange between webmaster, Do we need much more
about this critical point? 

>These changes made the dream of the network becoming 
>the computer - a dream that was first articulated earlier in the 
>decade -seem likely to become true.  They also made possible the rise 
>of a new application service provider industry.

Future applications will require much more information about users and
their business not only for personalization but also for subjetive
interpretation of the virtuality, must we give all this information to the
ISP without garaties about their transparent activity with this information?
 
>We must strive for educational 
>processes that will make clear to regulators and the public alike 
>what economic and policy consequences will flow from the two 
>different approaches to the market.

You touch the main point, Do we need political, social, economic,
cultural,..., goals for Internet, to determine wich technical decisions are
better for this goals, or is better to continue taken random decisions just
to see what happend?

>Therefore one must consider whether the Internet technical community 
>while doing battle over the presumed uniformity necessary for IPv6 is 
>actually depriving itself of the time and effort needed to face more 
>intractable problems of scaling, including protocol diversity. 

Do the protocol diversity will aply also to normal user activities?, i.e.
hipertext with multiple links or electronic messages with and undefined
number of fields that diferent virtual comunities will adapt to their
circuntances, to aproach to the goal that the culture defines the standars,
not the standars the culture.


>We find that one battle of the year 2000 is to be between the 
>horizontal versus vertically integrated business models.

It looks that horizontal business model will be least bad for users but:

-Sure many stakeholders will defend copyrights, which of the horizontal
stakeholder will defend the citizens right to access to the culture?
-Sure many stakeholders will defend companies rights to keep the secret of
the products, which horizontal, vertical or diagonal one will defend the
citizens right to have information and protection about the produts they use?
...


>They must also make the right judgments about the governance and 
>standards wars, and the rapid shift in market economics. The >winners 
>will be those who get the  right answers to this complex mix of 
>questions.

Instead my questions are very simple, like me!, I donīt know who are your
winners but I am sure about the lossers, citizens as usual! 

So I agree with internet 2000, yes but Internet 2000 Citizens 0

The system remain unbalance, SO WHAT?

>Gordon Cook January 24, 2000
>
>****************************************************************
>The COOK Report on Internet      Index to 8 years of the COOK  Report
>431 Greenway Ave, Ewing, NJ 08618 USA  http://cookreport.com
>(609) 882-2572 (phone & fax)              IP Everywhere: Riding the
>cook@cookreport.com                     Internet Tsunami - 392 pages
>just published. See  http://cookreport.com/ipeverywhere.shtml
>****************************************************************
>

Best Regards,

Salvador Vidal

******************************************************************
You get this message because you "subscribe" to my distribution list,
acording to the actual regulation this message is not considered spam,
because I give you a way to unsubscribe:

If you want to unsubscribe please call my grandmother Angelina at + 34 91
650 24 53, Bable speaking with a very high voice volume will be an asset
for this regard.
******************************************************************



From owner-ietf-outbound@ietf.org  Tue Feb  1 07:31:39 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12757
	for <ietf-web-archive@odin.ietf.org>; Tue, 1 Feb 2000 07:31:39 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA06261;
	Tue, 1 Feb 2000 07:29:41 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id HAA12571
	for ietf-outbound.10@ietf.org; Tue, 1 Feb 2000 07:30:01 -0500 (EST)
Received: from camaleon.lander.es ([212.95.212.2])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA12316
	for <ietf@ietf.org>; Tue, 1 Feb 2000 07:24:27 -0500 (EST)
Received: (qmail 21176 invoked from network); 1 Feb 2000 12:23:51 -0000
Received: from lince.lander.es (195.76.46.35)
  by camaleon.lander.es with SMTP; 1 Feb 2000 12:23:51 -0000
Received: (qmail 26642 invoked from network); 1 Feb 2000 12:22:13 -0000
Received: from ppp-46-247.lander.es (HELO salva) (195.76.46.247)
  by lince.lander.es with SMTP; 1 Feb 2000 12:22:13 -0000
Message-Id: <3.0.6.32.20000201132748.007d78d0@lince.lander.es>
X-Sender: svidal@lince.lander.es (Unverified)
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32)
Date: Tue, 01 Feb 2000 13:27:48 +0100
To: Gordon Cook <cook@cookreport.com>
From: Salvador Vidal <svidal@lander.es>
Subject: Re:...the Internet 2000 Citizens 0
Cc: ietf@ietf.org
In-Reply-To: <v04210101b4b299b39e9a@[192.168.0.1]>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id HAA12316
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hello Gordon and all,

At 19:16 24/01/00 -0500, you wrote:
>http://cookreport.com/ipeverywhere.shtml

A report about Internet politics with sense and without censorship!, Is
Echelon on Strike?

>At the beginning of the new millennium the Internet is globally 
>triumphant.  Blindly embraced by politicians who do not >understand it

Politicians ignorance is not problem, they have our money to have the
service of the best consultants, but independence, are able the politicians
to do independent decisions when they need big boys money for their
electoral campains?

>we have traveled from the certainty of knowledge that publishing >is 
>an activity whereby elite gate keepers package knowledge for the 
>masses to a world where every computer owner can become a >publisher. 

Yes, but the big boys remain the control of information, so citizens are
able to publish but not to find the independent publishers if big boys
donīt want, there are some inciatives to break this elite control of
information like link exchange between webmaster, Do we need much more
about this critical point? 

>These changes made the dream of the network becoming 
>the computer - a dream that was first articulated earlier in the 
>decade -seem likely to become true.  They also made possible the rise 
>of a new application service provider industry.

Future applications will require much more information about users and
their business not only for personalization but also for subjetive
interpretation of the virtuality, must we give all this information to the
ISP without garaties about their transparent activity with this information?
 
>We must strive for educational 
>processes that will make clear to regulators and the public alike 
>what economic and policy consequences will flow from the two 
>different approaches to the market.

You touch the main point, Do we need political, social, economic,
cultural,..., goals for Internet, to determine wich technical decisions are
better for this goals, or is better to continue taken random decisions just
to see what happend?

>Therefore one must consider whether the Internet technical community 
>while doing battle over the presumed uniformity necessary for IPv6 is 
>actually depriving itself of the time and effort needed to face more 
>intractable problems of scaling, including protocol diversity. 

Do the protocol diversity will aply also to normal user activities?, i.e.
hipertext with multiple links or electronic messages with and undefined
number of fields that diferent virtual comunities will adapt to their
circuntances, to aproach to the goal that the culture defines the standars,
not the standars the culture.


>We find that one battle of the year 2000 is to be between the 
>horizontal versus vertically integrated business models.

It looks that horizontal business model will be least bad for users but:

-Sure many stakeholders will defend copyrights, which of the horizontal
stakeholder will defend the citizens right to access to the culture?
-Sure many stakeholders will defend companies rights to keep the secret of
the products, which horizontal, vertical or diagonal one will defend the
citizens right to have information and protection about the produts they use?
...


>They must also make the right judgments about the governance and 
>standards wars, and the rapid shift in market economics. The >winners 
>will be those who get the  right answers to this complex mix of 
>questions.

Instead my questions are very simple, like me!, I donīt know who are your
winners but I am sure about the lossers, citizens as usual! 

So I agree with internet 2000, yes but Internet 2000 Citizens 0

The system remain unbalance, SO WHAT?

>Gordon Cook January 24, 2000
>
>****************************************************************
>The COOK Report on Internet      Index to 8 years of the COOK  Report
>431 Greenway Ave, Ewing, NJ 08618 USA  http://cookreport.com
>(609) 882-2572 (phone & fax)              IP Everywhere: Riding the
>cook@cookreport.com                     Internet Tsunami - 392 pages
>just published. See  http://cookreport.com/ipeverywhere.shtml
>****************************************************************
>

Best Regards,

Salvador Vidal

******************************************************************
You get this message because you "subscribe" to my distribution list,
acording to the actual regulation this message is not considered spam,
because I give you a way to unsubscribe:

If you want to unsubscribe please call my grandmother Angelina at + 34 91
650 24 53, Bable speaking with a very high voice volume will be an asset
for this regard.
******************************************************************



From owner-ietf-outbound  Tue Feb  1 09:50:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA19836
	for ietf-outbound.10@ietf.org; Tue, 1 Feb 2000 09:50:03 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19491
	for <ietf@ietf.org>; Tue, 1 Feb 2000 09:41:04 -0500 (EST)
Message-Id: <200002011441.JAA19491@ietf.org>
From: The IETF Secretariat <ietf-secretariat@ietf.org>
To: ietf@ietf.org
Subject: IETF List maintenance
Reply-to: ietf-request@ietf.org
Date: Tue, 01 Feb 2000 09:41:04 -0500
Sender: scoya@cnri.reston.va.us


To remove yourself from the IETF discussion list, send a message to
ietf-request@ietf.org

Enter just the word unsubscribe in the body of the message.

NOTE: List requests do not take effect until the next day, and there
      are always messages in the outbound queue. As such, you may 
      receive some messages, but only for a relatively short time.


The IETF discussion list serves two purposes. It furthers the
development and specification of Internet technology through discussion
of technical issues. It also hosts discussions of IETF direction,
policy, and procedures. As this is the most general IETF mailing list,
considerable latitude is allowed. Advertising, whether to solicit
business or promote employment opportunities, falls well outside the
range of acceptable topics, as do discussions of a personal nature.

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

In addition to the topics noted above, appropriate postings include: 

o Last Call discussions of proposed protocol actions 
o Discussion of technical issues that are candidates for IETF work, but
  do not yet have an appropriate e-mail venue
o Discussion of IETF administrative policies 
o Questions and clarifications concerning IETF meetings. 

Inappropriate postings include: 
o Unsolicited bulk e-mail 
o Discussion of subjects unrelated to IETF policy, meetings,
  activities, or technical concerns
o Unprofessional commentary, regardless of the general subject. 

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 as they deem appropriate to limit abuse. Complaints
regarding their decisions should be referred to the IAB <iab@iab.org>



From owner-ietf-outbound@ietf.org  Tue Feb  1 09:57:16 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20308
	for <ietf-web-archive@odin.ietf.org>; Tue, 1 Feb 2000 09:57:16 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA11224;
	Tue, 1 Feb 2000 09:55:29 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id JAA19836
	for ietf-outbound.10@ietf.org; Tue, 1 Feb 2000 09:50:03 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19491
	for <ietf@ietf.org>; Tue, 1 Feb 2000 09:41:04 -0500 (EST)
Message-Id: <200002011441.JAA19491@ietf.org>
From: The IETF Secretariat <ietf-secretariat@ietf.org>
To: ietf@ietf.org
Subject: IETF List maintenance
Reply-to: ietf-request@ietf.org
Date: Tue, 01 Feb 2000 09:41:04 -0500
Sender: scoya@cnri.reston.va.us


To remove yourself from the IETF discussion list, send a message to
ietf-request@ietf.org

Enter just the word unsubscribe in the body of the message.

NOTE: List requests do not take effect until the next day, and there
      are always messages in the outbound queue. As such, you may 
      receive some messages, but only for a relatively short time.


The IETF discussion list serves two purposes. It furthers the
development and specification of Internet technology through discussion
of technical issues. It also hosts discussions of IETF direction,
policy, and procedures. As this is the most general IETF mailing list,
considerable latitude is allowed. Advertising, whether to solicit
business or promote employment opportunities, falls well outside the
range of acceptable topics, as do discussions of a personal nature.

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

In addition to the topics noted above, appropriate postings include: 

o Last Call discussions of proposed protocol actions 
o Discussion of technical issues that are candidates for IETF work, but
  do not yet have an appropriate e-mail venue
o Discussion of IETF administrative policies 
o Questions and clarifications concerning IETF meetings. 

Inappropriate postings include: 
o Unsolicited bulk e-mail 
o Discussion of subjects unrelated to IETF policy, meetings,
  activities, or technical concerns
o Unprofessional commentary, regardless of the general subject. 

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 as they deem appropriate to limit abuse. Complaints
regarding their decisions should be referred to the IAB <iab@iab.org>



From owner-ietf-outbound  Tue Feb  1 13:40:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA28148
	for ietf-outbound.10@ietf.org; Tue, 1 Feb 2000 13:40:03 -0500 (EST)
Received: from a.crl.com (A.crl.com [165.113.1.65])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27957
	for <ietf@ietf.org>; Tue, 1 Feb 2000 13:33:57 -0500 (EST)
Received: from europa (A100018.sfx4.as.crl.com [168.75.100.18]) 
	by a.crl.com (8.8.7/) via SMTP id KAA20983; Tue, 1 Feb 2000 10:33:56 -0800 (PST)
        env-from (kaelin@everest.com)
Message-ID: <00b101bf6ce2$fbe12bf0$d2400d0a@europa>
From: "Kaelin Colclasure" <kaelin@everest.com>
To: <ietf@ietf.org>
Cc: <Michael.Condry@eng.sun.com>
Subject: Mailing list for forming WG?
Date: Tue, 1 Feb 2000 10:34:31 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I apologize if this information is available elsewhere, but I was wondering
if the Majordomo at ietf.org is a resource available for hosting mailing
lists
for discussions which aspire to be an IETF working group?

Such a discussion has been ongoing on the SOAP mailing list in the wake of
the
recent meeting announced by Michael Condry. But it's become apparent to at
least some of the participants that the SOAP list is not an appropriate
forum,
and an alternative venue is being sought.

A list hosted at ietf.org would seem to have the benefit of providing a good
repository of context should a working group actually be formed.

If this use of Majordomo at ietf.org is permissable, whom would one contact
about setting up such a list?

-- Kaelin





From owner-ietf-outbound@ietf.org  Tue Feb  1 13:46:42 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28502
	for <ietf-web-archive@odin.ietf.org>; Tue, 1 Feb 2000 13:46:42 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA18654;
	Tue, 1 Feb 2000 13:44:50 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id NAA28148
	for ietf-outbound.10@ietf.org; Tue, 1 Feb 2000 13:40:03 -0500 (EST)
Received: from a.crl.com (A.crl.com [165.113.1.65])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27957
	for <ietf@ietf.org>; Tue, 1 Feb 2000 13:33:57 -0500 (EST)
Received: from europa (A100018.sfx4.as.crl.com [168.75.100.18]) 
	by a.crl.com (8.8.7/) via SMTP id KAA20983; Tue, 1 Feb 2000 10:33:56 -0800 (PST)
        env-from (kaelin@everest.com)
Message-ID: <00b101bf6ce2$fbe12bf0$d2400d0a@europa>
From: "Kaelin Colclasure" <kaelin@everest.com>
To: <ietf@ietf.org>
Cc: <Michael.Condry@eng.sun.com>
Subject: Mailing list for forming WG?
Date: Tue, 1 Feb 2000 10:34:31 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I apologize if this information is available elsewhere, but I was wondering
if the Majordomo at ietf.org is a resource available for hosting mailing
lists
for discussions which aspire to be an IETF working group?

Such a discussion has been ongoing on the SOAP mailing list in the wake of
the
recent meeting announced by Michael Condry. But it's become apparent to at
least some of the participants that the SOAP list is not an appropriate
forum,
and an alternative venue is being sought.

A list hosted at ietf.org would seem to have the benefit of providing a good
repository of context should a working group actually be formed.

If this use of Majordomo at ietf.org is permissable, whom would one contact
about setting up such a list?

-- Kaelin





From owner-ietf-outbound  Tue Feb  1 15:20:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA01442
	for ietf-outbound.10@ietf.org; Tue, 1 Feb 2000 15:20:03 -0500 (EST)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01094
	for <ietf@ietf.org>; Tue, 1 Feb 2000 15:10:29 -0500 (EST)
Received: from sp3at21.hursley.ibm.com (sp3at21.hursley.ibm.com [9.20.45.21]) by mail-gw.hursley.ibm.com (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id UAA144198; Tue, 1 Feb 2000 20:09:31 GMT
Received: from hursley.ibm.com (gsine01.us.sine.ibm.com [9.14.6.41]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id UAA16720; Tue, 1 Feb 2000 20:09:29 GMT
Message-ID: <38973CC0.7587C6AD@hursley.ibm.com>
Date: Tue, 01 Feb 2000 14:06:24 -0600
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en,fr
MIME-Version: 1.0
To: rms46.oke.com@vlsm.org
CC: MILIS IETF <ietf@ietf.org>, isoc@isoc.org
Subject: Re: 1601bis: The Charter of IAB
References: <38928323.6DF08264@oke.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Rahmat,

"Rahmat M. Samik-Ibrahim" wrote:
> 
> To Whom It May Concern
> 
> Re: Last Call: Charter of the Internet Architecture Board (IAB) to BCP
> 
> > The IESG plans to make a decision in the next few weeks, and
> > solicits final comments on this action.  Please send any
> > comments to the iesg@ietf.org or ietf@ietf.org mailing lists
> > by February 9, 2000.
> 
> > Files can be obtained via
> > http://www.ietf.org/internet-drafts/draft-ietf-iab-rfc1601bis-02.txt
> 
> General
> 
> 1. Why should the IESG approve the charter? Why not the ISOC?

Because this is an IETF document defining the charter of an IETF committee.

> 2. There is no clear statement about the relationship between
>    ISOC and IAB. Why?

The following seems clear enough to me:

   The IAB acts as a source of advice and guidance to the Board of
   Trustees and Officers of the Internet Society concerning technical,
   architectural, procedural, and (where appropriate) policy matters
   pertaining to the Internet and its enabling technologies. If
   necessary the IAB may convene panels of knowledgeable people, hold
   hearings, and otherwise pursue the investigation of specific
   questions or topics presented to it by the Internet Society.

> 3. There is no clear statement about relationship with RFC-Editor,
>    IESG, IETF-Sec, IANA, and ICANN. Why?

On the contrary, relations with the RFC-Ed, IESG, and IANA are
described explicitly. There is no particular relationship with the
IETF Secretariat and no formal relationship whatever with ICANN,
so on those two there is nothing to describe.
> 
> Accountability
> 
> 4. As the community is not only exclusively the IETF anymore,
>    what does really "on behalf of the Internet Community" mean?

This phrase does not occur in the draft.

>    What measurement will be used? 

If the IETF doesn't like the job we do, they have recourse under BCP 10.

>    Will the IAB publish at least
>    an annual "progress report"? 

That might be a good idea if we had the time, but it is not something
to put in a charter.

> What/Where is the replacement of
>    what IAB previously reported in the IMR?

All the information previously supplied in the IMR is now available
on the IETF and/or RFC Editor web sites.

> 
> 5. How will the IAB implement "own choosing" of BCP-9:
>    "The IAB shall then review the situation and attempt to resolve
>    it in a manner of its OWN CHOOSING."

These words are not in the draft we are discussing.

>    See also BCP-9:
>    6.5  Conflict Resolution and Appeals
>    6.5.1 Working Group Disputes
>    6.5.2 Process Failures
>    6.5.3 Questions of Applicable Procedure
>    See also BCP-11:
>    3.6  Internet Architecture Board
>    3.7  Internet Assigned Numbers Authority

I fail to see the relevance of this list to the document we are discussing.

> 6. What should the IAB/ISOC do, if the IESG signs a treaty without
>    having a Last Call?

I fail to see why this question is relevant to the document we are discussing

> -------------------------------------------------------------------
> 
> Enclosed is my suggested framework of 1601bis

I don't see any items in your framework that are both appropriate to
include in the charter and not included in the existing draft.

   Brian



From owner-ietf-outbound@ietf.org  Tue Feb  1 15:22:46 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01588
	for <ietf-web-archive@odin.ietf.org>; Tue, 1 Feb 2000 15:22:46 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA21647;
	Tue, 1 Feb 2000 15:20:54 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id PAA01442
	for ietf-outbound.10@ietf.org; Tue, 1 Feb 2000 15:20:03 -0500 (EST)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01094
	for <ietf@ietf.org>; Tue, 1 Feb 2000 15:10:29 -0500 (EST)
Received: from sp3at21.hursley.ibm.com (sp3at21.hursley.ibm.com [9.20.45.21]) by mail-gw.hursley.ibm.com (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id UAA144198; Tue, 1 Feb 2000 20:09:31 GMT
Received: from hursley.ibm.com (gsine01.us.sine.ibm.com [9.14.6.41]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id UAA16720; Tue, 1 Feb 2000 20:09:29 GMT
Message-ID: <38973CC0.7587C6AD@hursley.ibm.com>
Date: Tue, 01 Feb 2000 14:06:24 -0600
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en,fr
MIME-Version: 1.0
To: rms46.oke.com@vlsm.org
CC: MILIS IETF <ietf@ietf.org>, isoc@isoc.org
Subject: Re: 1601bis: The Charter of IAB
References: <38928323.6DF08264@oke.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Rahmat,

"Rahmat M. Samik-Ibrahim" wrote:
> 
> To Whom It May Concern
> 
> Re: Last Call: Charter of the Internet Architecture Board (IAB) to BCP
> 
> > The IESG plans to make a decision in the next few weeks, and
> > solicits final comments on this action.  Please send any
> > comments to the iesg@ietf.org or ietf@ietf.org mailing lists
> > by February 9, 2000.
> 
> > Files can be obtained via
> > http://www.ietf.org/internet-drafts/draft-ietf-iab-rfc1601bis-02.txt
> 
> General
> 
> 1. Why should the IESG approve the charter? Why not the ISOC?

Because this is an IETF document defining the charter of an IETF committee.

> 2. There is no clear statement about the relationship between
>    ISOC and IAB. Why?

The following seems clear enough to me:

   The IAB acts as a source of advice and guidance to the Board of
   Trustees and Officers of the Internet Society concerning technical,
   architectural, procedural, and (where appropriate) policy matters
   pertaining to the Internet and its enabling technologies. If
   necessary the IAB may convene panels of knowledgeable people, hold
   hearings, and otherwise pursue the investigation of specific
   questions or topics presented to it by the Internet Society.

> 3. There is no clear statement about relationship with RFC-Editor,
>    IESG, IETF-Sec, IANA, and ICANN. Why?

On the contrary, relations with the RFC-Ed, IESG, and IANA are
described explicitly. There is no particular relationship with the
IETF Secretariat and no formal relationship whatever with ICANN,
so on those two there is nothing to describe.
> 
> Accountability
> 
> 4. As the community is not only exclusively the IETF anymore,
>    what does really "on behalf of the Internet Community" mean?

This phrase does not occur in the draft.

>    What measurement will be used? 

If the IETF doesn't like the job we do, they have recourse under BCP 10.

>    Will the IAB publish at least
>    an annual "progress report"? 

That might be a good idea if we had the time, but it is not something
to put in a charter.

> What/Where is the replacement of
>    what IAB previously reported in the IMR?

All the information previously supplied in the IMR is now available
on the IETF and/or RFC Editor web sites.

> 
> 5. How will the IAB implement "own choosing" of BCP-9:
>    "The IAB shall then review the situation and attempt to resolve
>    it in a manner of its OWN CHOOSING."

These words are not in the draft we are discussing.

>    See also BCP-9:
>    6.5  Conflict Resolution and Appeals
>    6.5.1 Working Group Disputes
>    6.5.2 Process Failures
>    6.5.3 Questions of Applicable Procedure
>    See also BCP-11:
>    3.6  Internet Architecture Board
>    3.7  Internet Assigned Numbers Authority

I fail to see the relevance of this list to the document we are discussing.

> 6. What should the IAB/ISOC do, if the IESG signs a treaty without
>    having a Last Call?

I fail to see why this question is relevant to the document we are discussing

> -------------------------------------------------------------------
> 
> Enclosed is my suggested framework of 1601bis

I don't see any items in your framework that are both appropriate to
include in the charter and not included in the existing draft.

   Brian



From owner-ietf-outbound  Tue Feb  1 17:00:50 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA06315
	for ietf-outbound.10@ietf.org; Tue, 1 Feb 2000 17:00:03 -0500 (EST)
Received: from fwns2.raleigh.ibm.com (fwns2d.raleigh.ibm.com [204.146.167.236])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05932
	for <ietf@ietf.org>; Tue, 1 Feb 2000 16:52:44 -0500 (EST)
Received: from rtpmail03.raleigh.ibm.com (rtpmail03.raleigh.ibm.com [9.37.172.47])
	by fwns2.raleigh.ibm.com (8.9.0/8.9.0/RTP-FW-1.2) with ESMTP id QAA16936;
	Tue, 1 Feb 2000 16:52:35 -0500
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.37.82.31])
	by rtpmail03.raleigh.ibm.com (8.8.5/8.8.5/RTP-ral-1.1) with ESMTP id QAA20740;
	Tue, 1 Feb 2000 16:52:37 -0500
Received: from rotala.raleigh.ibm.com (localhost [127.0.0.1]) by rotala.raleigh.ibm.com (8.9.3/8.7/RTP-ral-1.0) with ESMTP id QAA09535; Tue, 1 Feb 2000 16:47:07 -0500
Message-Id: <200002012147.QAA09535@rotala.raleigh.ibm.com>
To: "Kaelin Colclasure" <kaelin@everest.com>
cc: ietf@ietf.org, Michael.Condry@eng.sun.com
Subject: Re: Mailing list for forming WG? 
In-Reply-To: Message from "Kaelin Colclasure" <kaelin@everest.com> 
   of "Tue, 01 Feb 2000 10:34:31 PST." <00b101bf6ce2$fbe12bf0$d2400d0a@europa> 
Date: Tue, 01 Feb 2000 16:47:07 -0500
From: Thomas Narten <narten@raleigh.ibm.com>

> I apologize if this information is available elsewhere, but I was
> wondering if the Majordomo at ietf.org is a resource available for
> hosting mailing lists for discussions which aspire to be an IETF
> working group?

The main problem with this is that not all mailing lists ever become
WGs. We'd be potentially opening up the floodgates to anyone who wants
a mailing list. I doubt that the secretariate has the resources for
that.

Also, some might say that if an effort can't garner sufficient
interest for someone to be willing to host a mailing list, that is an
indication of lack of support for the topic.

Finally, the IETF already has plenty of problems with some folks
(mis)using the IETF name. If we allowed pre-WG mailing lists to be
hosted from ietf.org, I'm sure some folks would point that fact out
quite loudly when asserting that they will be defining the next
standard. "See, we already have an official IETF mailing list".

Thomas



From owner-ietf-outbound@ietf.org  Tue Feb  1 17:03:59 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06593
	for <ietf-web-archive@odin.ietf.org>; Tue, 1 Feb 2000 17:03:54 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA25104;
	Tue, 1 Feb 2000 17:02:05 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id RAA06315
	for ietf-outbound.10@ietf.org; Tue, 1 Feb 2000 17:00:03 -0500 (EST)
Received: from fwns2.raleigh.ibm.com (fwns2d.raleigh.ibm.com [204.146.167.236])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05932
	for <ietf@ietf.org>; Tue, 1 Feb 2000 16:52:44 -0500 (EST)
Received: from rtpmail03.raleigh.ibm.com (rtpmail03.raleigh.ibm.com [9.37.172.47])
	by fwns2.raleigh.ibm.com (8.9.0/8.9.0/RTP-FW-1.2) with ESMTP id QAA16936;
	Tue, 1 Feb 2000 16:52:35 -0500
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.37.82.31])
	by rtpmail03.raleigh.ibm.com (8.8.5/8.8.5/RTP-ral-1.1) with ESMTP id QAA20740;
	Tue, 1 Feb 2000 16:52:37 -0500
Received: from rotala.raleigh.ibm.com (localhost [127.0.0.1]) by rotala.raleigh.ibm.com (8.9.3/8.7/RTP-ral-1.0) with ESMTP id QAA09535; Tue, 1 Feb 2000 16:47:07 -0500
Message-Id: <200002012147.QAA09535@rotala.raleigh.ibm.com>
To: "Kaelin Colclasure" <kaelin@everest.com>
cc: ietf@ietf.org, Michael.Condry@eng.sun.com
Subject: Re: Mailing list for forming WG? 
In-Reply-To: Message from "Kaelin Colclasure" <kaelin@everest.com> 
   of "Tue, 01 Feb 2000 10:34:31 PST." <00b101bf6ce2$fbe12bf0$d2400d0a@europa> 
Date: Tue, 01 Feb 2000 16:47:07 -0500
From: Thomas Narten <narten@raleigh.ibm.com>

> I apologize if this information is available elsewhere, but I was
> wondering if the Majordomo at ietf.org is a resource available for
> hosting mailing lists for discussions which aspire to be an IETF
> working group?

The main problem with this is that not all mailing lists ever become
WGs. We'd be potentially opening up the floodgates to anyone who wants
a mailing list. I doubt that the secretariate has the resources for
that.

Also, some might say that if an effort can't garner sufficient
interest for someone to be willing to host a mailing list, that is an
indication of lack of support for the topic.

Finally, the IETF already has plenty of problems with some folks
(mis)using the IETF name. If we allowed pre-WG mailing lists to be
hosted from ietf.org, I'm sure some folks would point that fact out
quite loudly when asserting that they will be defining the next
standard. "See, we already have an official IETF mailing list".

Thomas



From owner-ietf-outbound  Tue Feb  1 18:11:33 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA09165
	for ietf-outbound.10@ietf.org; Tue, 1 Feb 2000 18:10:02 -0500 (EST)
Received: from SSP1NO21.highway.telekom.at (EMAIL-AON.highway.telekom.at [195.3.96.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09117
	for <ietf@ietf.org>; Tue, 1 Feb 2000 18:08:44 -0500 (EST)
Received: from mwelser (N139P011.dipool.highway.telekom.at [195.3.113.75])
	by SSP1NO21.highway.telekom.at (8.9.3/8.9.3) with SMTP id AAA234318;
	Wed, 2 Feb 2000 00:04:15 +0100
Reply-To: <mwelser@highway.telekom.at>
From: "Michael Welser" <michael.welser@aon.at>
To: "Adrian Zoicas" <adrian.zoicas@etsi.fr>,
        "=?iso-8859-1?Q?Catherine_Zennstr=F6m?=" <cz@everyday.com>,
        "Colin Willcock" <c.willcock@expert-telecoms.com>,
        "Anthony Wiles" <anthony.wiles@etsi.fr>,
        "Sean White" <swhite@shannon.tellabs.com>,
        "Laurent Vreck" <laurent.vreck@etsi.fr>,
        "Christine Voulgre" <christine.voulgre@etsi.fr>,
        "Olivier Verdy" <olivier.verdy@etsi.fr>,
        "Pieter Veenstra" <p.k.veenstra@kpn-telecom.nl>,
        "Keimpe van der Wal" <keimpevanderwal@hotmail.com>,
        "Yannick Surzur" <yannick.surzur@cnet.francetelecom.fr>,
        "Ian Spiers" <spiers@ncp.gpt.co.uk>,
        "Peter Schmitting" <schmitting.fscom@wanadoo.fr>,
        "Michael Sanders" <michael.sanders@etsi.fr>,
        "Graham Rose" <graham.rose@etsi.fr>,
        "=?iso-8859-1?Q?Jo=EBl_Poulain?=" <joel.poulain@etsi.fr>,
        "Maurice Pope" <maurice.pope@etsi.fr>,
        "Emmanuel Piegay" <Emmanuel.PIEGAY@dematic-postal.com>,
        "Poul Erik Pedersen" <poep@tdk.dk>, "Henk Oort" <hoort@lucent.com>,
        "Gerd Ochel" <gerd.ochel@etsi.fr>,
        "Ultan Mulligan" <ultan.mulligan@etsi.fr>,
        "=?iso-8859-1?Q?Hans-Peter_M=FCller?=" <hans_peter_mueller@darmstadt2.detecon.de>,
        "Didier Mouron" <dmouron@wanadoo.fr>,
        "John Meredith" <john.meredith@etsi.fr>,
        "Gerry McAuley" <gerry.mcauley@etsi.fr>,
        "Anders Ljunggren-Svanes" <anders.ljunggren@ecsoft.no>,
        "Jeanne Lancry" <jeanne.lancry@etsi.fr>,
        "Denise Kratzer" <denise_kratzer@hotmail.com>,
        "Fiona Keane" <Fiona.Keane@energis-ecs.com>,
        "Emmanuelle Jouan" <emmanuelle.jouan@etsi.fr>, <ietf@ietf.org>,
        "Karen Hughes" <karen.hughes@etsi.fr>,
        "Janez Hocevar" <janez@usm.mzt.si>,
        "Roberto Gaetano" <r.gaetano@iaea.org>,
        "=?iso-8859-1?Q?Nad=E8ge_Florival?=" <Nadege.Florival@etsi.fr>,
        "Laurence Ferrand" <laurence.ferrand@etsi.fr>,
        "Tormod Egeland" <tormod.egeland@grimstad.nett.telenor.no>,
        "Keith Drage" <keith.drage@siemenscomms.co.uk>,
        "Christian Don" <christian.don@francetelecom.fr>,
        "Ian Doig" <ian.doig@etsi.fr>,
        "Claire d'Esclercs" <Claire.Desclercs@etsi.fr>,
        "Antoine Caner" <antoine.caner@etsi.fr>,
        "Mike Briggs" <mike.briggs@bt.com>,
        "Mark Bogers" <mark.bogers@dg3.cec.be>
Date: Wed, 2 Feb 2000 00:07:40 +0100
Message-ID: <NCBBKPFPMLHLEIJAJJLLIEKMDBAA.michael.welser@aon.at>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Dear all,

it seems that I chose just the right moment for going back to Austria. I am
deeply unhappy about the ongoing political development in this country, to an
extent which approaches nausea. Nevertheless, please bear in mind that when
meeting three Austrians, "only" one actually voted for Haider.

Somewhat desperate, kind regards,

Michael

------------------------------------------------------------
mailto:mwelser@highway.telekom.at         Telekom Austria AG
tel: +43 (1) 79711 1622                               Abt RS
fax: +43 (1) 79711 1608                    Arsenal Objekt 22
http://www.telekom.at                           Postfach 111
http://www.aon.at                                A-1103 Wien




From owner-ietf-outbound@ietf.org  Tue Feb  1 18:17:55 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09344
	for <ietf-web-archive@odin.ietf.org>; Tue, 1 Feb 2000 18:17:54 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA27234;
	Tue, 1 Feb 2000 18:15:20 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id SAA09165
	for ietf-outbound.10@ietf.org; Tue, 1 Feb 2000 18:10:02 -0500 (EST)
Received: from SSP1NO21.highway.telekom.at (EMAIL-AON.highway.telekom.at [195.3.96.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09117
	for <ietf@ietf.org>; Tue, 1 Feb 2000 18:08:44 -0500 (EST)
Received: from mwelser (N139P011.dipool.highway.telekom.at [195.3.113.75])
	by SSP1NO21.highway.telekom.at (8.9.3/8.9.3) with SMTP id AAA234318;
	Wed, 2 Feb 2000 00:04:15 +0100
Reply-To: <mwelser@highway.telekom.at>
From: "Michael Welser" <michael.welser@aon.at>
To: "Adrian Zoicas" <adrian.zoicas@etsi.fr>,
        "=?iso-8859-1?Q?Catherine_Zennstr=F6m?=" <cz@everyday.com>,
        "Colin Willcock" <c.willcock@expert-telecoms.com>,
        "Anthony Wiles" <anthony.wiles@etsi.fr>,
        "Sean White" <swhite@shannon.tellabs.com>,
        "Laurent Vreck" <laurent.vreck@etsi.fr>,
        "Christine Voulgre" <christine.voulgre@etsi.fr>,
        "Olivier Verdy" <olivier.verdy@etsi.fr>,
        "Pieter Veenstra" <p.k.veenstra@kpn-telecom.nl>,
        "Keimpe van der Wal" <keimpevanderwal@hotmail.com>,
        "Yannick Surzur" <yannick.surzur@cnet.francetelecom.fr>,
        "Ian Spiers" <spiers@ncp.gpt.co.uk>,
        "Peter Schmitting" <schmitting.fscom@wanadoo.fr>,
        "Michael Sanders" <michael.sanders@etsi.fr>,
        "Graham Rose" <graham.rose@etsi.fr>,
        "=?iso-8859-1?Q?Jo=EBl_Poulain?=" <joel.poulain@etsi.fr>,
        "Maurice Pope" <maurice.pope@etsi.fr>,
        "Emmanuel Piegay" <Emmanuel.PIEGAY@dematic-postal.com>,
        "Poul Erik Pedersen" <poep@tdk.dk>, "Henk Oort" <hoort@lucent.com>,
        "Gerd Ochel" <gerd.ochel@etsi.fr>,
        "Ultan Mulligan" <ultan.mulligan@etsi.fr>,
        "=?iso-8859-1?Q?Hans-Peter_M=FCller?=" <hans_peter_mueller@darmstadt2.detecon.de>,
        "Didier Mouron" <dmouron@wanadoo.fr>,
        "John Meredith" <john.meredith@etsi.fr>,
        "Gerry McAuley" <gerry.mcauley@etsi.fr>,
        "Anders Ljunggren-Svanes" <anders.ljunggren@ecsoft.no>,
        "Jeanne Lancry" <jeanne.lancry@etsi.fr>,
        "Denise Kratzer" <denise_kratzer@hotmail.com>,
        "Fiona Keane" <Fiona.Keane@energis-ecs.com>,
        "Emmanuelle Jouan" <emmanuelle.jouan@etsi.fr>, <ietf@ietf.org>,
        "Karen Hughes" <karen.hughes@etsi.fr>,
        "Janez Hocevar" <janez@usm.mzt.si>,
        "Roberto Gaetano" <r.gaetano@iaea.org>,
        "=?iso-8859-1?Q?Nad=E8ge_Florival?=" <Nadege.Florival@etsi.fr>,
        "Laurence Ferrand" <laurence.ferrand@etsi.fr>,
        "Tormod Egeland" <tormod.egeland@grimstad.nett.telenor.no>,
        "Keith Drage" <keith.drage@siemenscomms.co.uk>,
        "Christian Don" <christian.don@francetelecom.fr>,
        "Ian Doig" <ian.doig@etsi.fr>,
        "Claire d'Esclercs" <Claire.Desclercs@etsi.fr>,
        "Antoine Caner" <antoine.caner@etsi.fr>,
        "Mike Briggs" <mike.briggs@bt.com>,
        "Mark Bogers" <mark.bogers@dg3.cec.be>
Date: Wed, 2 Feb 2000 00:07:40 +0100
Message-ID: <NCBBKPFPMLHLEIJAJJLLIEKMDBAA.michael.welser@aon.at>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Dear all,

it seems that I chose just the right moment for going back to Austria. I am
deeply unhappy about the ongoing political development in this country, to an
extent which approaches nausea. Nevertheless, please bear in mind that when
meeting three Austrians, "only" one actually voted for Haider.

Somewhat desperate, kind regards,

Michael

------------------------------------------------------------
mailto:mwelser@highway.telekom.at         Telekom Austria AG
tel: +43 (1) 79711 1622                               Abt RS
fax: +43 (1) 79711 1608                    Arsenal Objekt 22
http://www.telekom.at                           Postfach 111
http://www.aon.at                                A-1103 Wien




From owner-ietf-outbound  Tue Feb  1 18:30:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA09511
	for ietf-outbound.10@ietf.org; Tue, 1 Feb 2000 18:30:02 -0500 (EST)
Received: from prue.eim.surrey.ac.uk (IDENT:exim@prue.eim.surrey.ac.uk [131.227.76.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09365
	for <ietf@ietf.org>; Tue, 1 Feb 2000 18:20:13 -0500 (EST)
Received: from petra.ee.surrey.ac.uk ([131.227.88.13] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.03 #1)
	id 12FmaA-0000Ze-00; Tue, 01 Feb 2000 23:19:38 +0000
Date: Tue, 1 Feb 2000 23:19:33 +0000 (GMT)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-Sender: eep1lw@petra.ee.surrey.ac.uk
Reply-To: L.Wood@eim.surrey.ac.uk
To: Thomas Narten <narten@raleigh.ibm.com>
cc: Kaelin Colclasure <kaelin@everest.com>, ietf@ietf.org,
        Michael.Condry@eng.sun.com
Subject: Re: Mailing list for forming WG?
In-Reply-To: <200002012147.QAA09535@rotala.raleigh.ibm.com>
Message-ID: <Pine.SOL.4.10.10002012302440.26191-100000@petra.ee.surrey.ac.uk>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 1 Feb 2000, Thomas Narten wrote:

> > I apologize if this information is available elsewhere, but I was
> > wondering if the Majordomo at ietf.org is a resource available for
> > hosting mailing lists for discussions which aspire to be an IETF
> > working group?
> 
> The main problem with this is that not all mailing lists ever become
> WGs. We'd be potentially opening up the floodgates to anyone who wants
> a mailing list. I doubt that the secretariate has the resources for
> that.
> 
> Also, some might say that if an effort can't garner sufficient
> interest for someone to be willing to host a mailing list, that is an
> indication of lack of support for the topic.

Then they've not been paying attention lately. A couple of services
that spring to mind for setting up mailing lists are:

http://www.onelist.com/
http://www.egroups.com/

The effort and level of knowledge required to set up a mailing list is
pretty minimal these days.

L.

<L.Wood@surrey.ac.uk>PGP<http://www.ee.surrey.ac.uk/Personal/L.Wood/>






From owner-ietf-outbound@ietf.org  Tue Feb  1 18:33:35 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09658
	for <ietf-web-archive@odin.ietf.org>; Tue, 1 Feb 2000 18:33:34 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA27626;
	Tue, 1 Feb 2000 18:31:33 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id SAA09511
	for ietf-outbound.10@ietf.org; Tue, 1 Feb 2000 18:30:02 -0500 (EST)
Received: from prue.eim.surrey.ac.uk (IDENT:exim@prue.eim.surrey.ac.uk [131.227.76.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09365
	for <ietf@ietf.org>; Tue, 1 Feb 2000 18:20:13 -0500 (EST)
Received: from petra.ee.surrey.ac.uk ([131.227.88.13] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.03 #1)
	id 12FmaA-0000Ze-00; Tue, 01 Feb 2000 23:19:38 +0000
Date: Tue, 1 Feb 2000 23:19:33 +0000 (GMT)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-Sender: eep1lw@petra.ee.surrey.ac.uk
Reply-To: L.Wood@eim.surrey.ac.uk
To: Thomas Narten <narten@raleigh.ibm.com>
cc: Kaelin Colclasure <kaelin@everest.com>, ietf@ietf.org,
        Michael.Condry@eng.sun.com
Subject: Re: Mailing list for forming WG?
In-Reply-To: <200002012147.QAA09535@rotala.raleigh.ibm.com>
Message-ID: <Pine.SOL.4.10.10002012302440.26191-100000@petra.ee.surrey.ac.uk>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 1 Feb 2000, Thomas Narten wrote:

> > I apologize if this information is available elsewhere, but I was
> > wondering if the Majordomo at ietf.org is a resource available for
> > hosting mailing lists for discussions which aspire to be an IETF
> > working group?
> 
> The main problem with this is that not all mailing lists ever become
> WGs. We'd be potentially opening up the floodgates to anyone who wants
> a mailing list. I doubt that the secretariate has the resources for
> that.
> 
> Also, some might say that if an effort can't garner sufficient
> interest for someone to be willing to host a mailing list, that is an
> indication of lack of support for the topic.

Then they've not been paying attention lately. A couple of services
that spring to mind for setting up mailing lists are:

http://www.onelist.com/
http://www.egroups.com/

The effort and level of knowledge required to set up a mailing list is
pretty minimal these days.

L.

<L.Wood@surrey.ac.uk>PGP<http://www.ee.surrey.ac.uk/Personal/L.Wood/>






From owner-ietf-outbound  Tue Feb  1 19:00:27 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA10165
	for ietf-outbound.10@ietf.org; Tue, 1 Feb 2000 19:00:04 -0500 (EST)
Received: from lint.cisco.com (lint.cisco.com [171.68.224.209])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10015
	for <ietf@ietf.org>; Tue, 1 Feb 2000 18:53:30 -0500 (EST)
Received: from bigger-dawgs (pferguso-isdn.cisco.com [171.70.114.134]) by lint.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id PAA16199; Tue, 1 Feb 2000 15:52:28 -0800 (PST)
Message-Id: <4.2.2.20000201185000.00a3f100@lint.cisco.com>
X-Sender: pferguso@lint.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Tue, 01 Feb 2000 18:52:16 -0500
To: L.Wood@eim.surrey.ac.uk
From: Paul Ferguson <ferguson@cisco.com>
Subject: Re: Mailing list for forming WG?
Cc: ietf@ietf.org
In-Reply-To: <Pine.SOL.4.10.10002012302440.26191-100000@petra.ee.surrey.
 ac.uk>
References: <200002012147.QAA09535@rotala.raleigh.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 11:19 PM 02/01/2000 +0000, Lloyd Wood wrote:

>Then they've not been paying attention lately. A couple of services
>that spring to mind for setting up mailing lists are:
>
>http://www.onelist.com/
>http://www.egroups.com/
>
>The effort and level of knowledge required to set up a mailing list is
>pretty minimal these days.

Acually, anyone who wishes to start a mailing list, whether related
to the IETF or not, can do so -- just obtain a copy of majordomo (or
listserv or whatever) and Viola!

That's how mailing lists used to be done for working groups in
the IETF anyways -- someone just volunteered to set one up.

- paul



From owner-ietf-outbound@ietf.org  Tue Feb  1 19:02:13 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10295
	for <ietf-web-archive@odin.ietf.org>; Tue, 1 Feb 2000 19:02:13 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA28412;
	Tue, 1 Feb 2000 19:00:23 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id TAA10165
	for ietf-outbound.10@ietf.org; Tue, 1 Feb 2000 19:00:04 -0500 (EST)
Received: from lint.cisco.com (lint.cisco.com [171.68.224.209])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10015
	for <ietf@ietf.org>; Tue, 1 Feb 2000 18:53:30 -0500 (EST)
Received: from bigger-dawgs (pferguso-isdn.cisco.com [171.70.114.134]) by lint.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id PAA16199; Tue, 1 Feb 2000 15:52:28 -0800 (PST)
Message-Id: <4.2.2.20000201185000.00a3f100@lint.cisco.com>
X-Sender: pferguso@lint.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Tue, 01 Feb 2000 18:52:16 -0500
To: L.Wood@eim.surrey.ac.uk
From: Paul Ferguson <ferguson@cisco.com>
Subject: Re: Mailing list for forming WG?
Cc: ietf@ietf.org
In-Reply-To: <Pine.SOL.4.10.10002012302440.26191-100000@petra.ee.surrey.
 ac.uk>
References: <200002012147.QAA09535@rotala.raleigh.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 11:19 PM 02/01/2000 +0000, Lloyd Wood wrote:

>Then they've not been paying attention lately. A couple of services
>that spring to mind for setting up mailing lists are:
>
>http://www.onelist.com/
>http://www.egroups.com/
>
>The effort and level of knowledge required to set up a mailing list is
>pretty minimal these days.

Acually, anyone who wishes to start a mailing list, whether related
to the IETF or not, can do so -- just obtain a copy of majordomo (or
listserv or whatever) and Viola!

That's how mailing lists used to be done for working groups in
the IETF anyways -- someone just volunteered to set one up.

- paul



From owner-ietf-outbound  Tue Feb  1 21:01:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA12301
	for ietf-outbound.10@ietf.org; Tue, 1 Feb 2000 21:00:02 -0500 (EST)
Received: from everest.com (everest.com [24.142.61.135])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12181
	for <ietf@ietf.org>; Tue, 1 Feb 2000 20:52:37 -0500 (EST)
Received: from summit (summit [192.168.1.2])
	by everest.com (8.9.3/8.9.3) with SMTP id RAA02166;
	Tue, 1 Feb 2000 17:13:43 -0800
Message-ID: <008901bf6d19$8ddb9050$0201a8c0@everest.com>
From: "Kaelin Colclasure" <kaelin@everest.com>
To: <L.Wood@eim.surrey.ac.uk>, "Thomas Narten" <narten@raleigh.ibm.com>
Cc: <ietf@ietf.org>, <Michael.Condry@eng.sun.com>
References: <Pine.SOL.4.10.10002012302440.26191-100000@petra.ee.surrey.ac.uk>
Subject: Re: Mailing list for forming WG?
Date: Tue, 1 Feb 2000 17:05:11 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Gentlemen,

Thank you for your responses. I am certainly aware of egroups.com, as
I host a list there, and a good friend of mine is one of their
architects. I asked about hosting it at ietf.org only to establish
wether this was or was not accepted procedure.

The rational for *not* allowing this sounds perfectly reasonable to
me. :-)

Just for future reference -- if a WG is formed, what is the usual
procedure regarding pre-existing mailing lists? Does the WG continue
using the original list? Are archives transferred? Or just linked
with an href?

-- Kaelin

--
Become a Venture Technologist... <http://www.everest.com/careers/>

----- Original Message -----
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
To: Thomas Narten <narten@raleigh.ibm.com>
Cc: Kaelin Colclasure <kaelin@everest.com>; <ietf@ietf.org>;
<Michael.Condry@eng.sun.com>
Sent: Tuesday, February 01, 2000 3:19 PM
Subject: Re: Mailing list for forming WG?


> On Tue, 1 Feb 2000, Thomas Narten wrote:
>
> > > I apologize if this information is available elsewhere, but I was
> > > wondering if the Majordomo at ietf.org is a resource available for
> > > hosting mailing lists for discussions which aspire to be an IETF
> > > working group?
> >
> > The main problem with this is that not all mailing lists ever become
> > WGs. We'd be potentially opening up the floodgates to anyone who wants
> > a mailing list. I doubt that the secretariate has the resources for
> > that.
> >
> > Also, some might say that if an effort can't garner sufficient
> > interest for someone to be willing to host a mailing list, that is an
> > indication of lack of support for the topic.
>
> Then they've not been paying attention lately. A couple of services
> that spring to mind for setting up mailing lists are:
>
> http://www.onelist.com/
> http://www.egroups.com/
>
> The effort and level of knowledge required to set up a mailing list is
> pretty minimal these days.
>
> L.
>
> <L.Wood@surrey.ac.uk>PGP<http://www.ee.surrey.ac.uk/Personal/L.Wood/>
>
>
>
>



From owner-ietf-outbound@ietf.org  Tue Feb  1 21:03:49 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12424
	for <ietf-web-archive@odin.ietf.org>; Tue, 1 Feb 2000 21:03:49 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA01871;
	Tue, 1 Feb 2000 21:01:57 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id VAA12301
	for ietf-outbound.10@ietf.org; Tue, 1 Feb 2000 21:00:02 -0500 (EST)
Received: from everest.com (everest.com [24.142.61.135])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12181
	for <ietf@ietf.org>; Tue, 1 Feb 2000 20:52:37 -0500 (EST)
Received: from summit (summit [192.168.1.2])
	by everest.com (8.9.3/8.9.3) with SMTP id RAA02166;
	Tue, 1 Feb 2000 17:13:43 -0800
Message-ID: <008901bf6d19$8ddb9050$0201a8c0@everest.com>
From: "Kaelin Colclasure" <kaelin@everest.com>
To: <L.Wood@eim.surrey.ac.uk>, "Thomas Narten" <narten@raleigh.ibm.com>
Cc: <ietf@ietf.org>, <Michael.Condry@eng.sun.com>
References: <Pine.SOL.4.10.10002012302440.26191-100000@petra.ee.surrey.ac.uk>
Subject: Re: Mailing list for forming WG?
Date: Tue, 1 Feb 2000 17:05:11 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Gentlemen,

Thank you for your responses. I am certainly aware of egroups.com, as
I host a list there, and a good friend of mine is one of their
architects. I asked about hosting it at ietf.org only to establish
wether this was or was not accepted procedure.

The rational for *not* allowing this sounds perfectly reasonable to
me. :-)

Just for future reference -- if a WG is formed, what is the usual
procedure regarding pre-existing mailing lists? Does the WG continue
using the original list? Are archives transferred? Or just linked
with an href?

-- Kaelin

--
Become a Venture Technologist... <http://www.everest.com/careers/>

----- Original Message -----
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
To: Thomas Narten <narten@raleigh.ibm.com>
Cc: Kaelin Colclasure <kaelin@everest.com>; <ietf@ietf.org>;
<Michael.Condry@eng.sun.com>
Sent: Tuesday, February 01, 2000 3:19 PM
Subject: Re: Mailing list for forming WG?


> On Tue, 1 Feb 2000, Thomas Narten wrote:
>
> > > I apologize if this information is available elsewhere, but I was
> > > wondering if the Majordomo at ietf.org is a resource available for
> > > hosting mailing lists for discussions which aspire to be an IETF
> > > working group?
> >
> > The main problem with this is that not all mailing lists ever become
> > WGs. We'd be potentially opening up the floodgates to anyone who wants
> > a mailing list. I doubt that the secretariate has the resources for
> > that.
> >
> > Also, some might say that if an effort can't garner sufficient
> > interest for someone to be willing to host a mailing list, that is an
> > indication of lack of support for the topic.
>
> Then they've not been paying attention lately. A couple of services
> that spring to mind for setting up mailing lists are:
>
> http://www.onelist.com/
> http://www.egroups.com/
>
> The effort and level of knowledge required to set up a mailing list is
> pretty minimal these days.
>
> L.
>
> <L.Wood@surrey.ac.uk>PGP<http://www.ee.surrey.ac.uk/Personal/L.Wood/>
>
>
>
>



From owner-ietf-outbound  Wed Feb  2 03:02:35 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA00626
	for ietf-outbound.10@ietf.org; Wed, 2 Feb 2000 03:00:02 -0500 (EST)
Received: from ucsi26.energis-ecs.com (pop.energis-ecs.com [212.38.192.79])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00563
	for <ietf@ietf.org>; Wed, 2 Feb 2000 02:51:21 -0500 (EST)
Received: by ucspop3.unisource-ucs.com with Internet Mail Service (5.5.2650.21)
	id <DYA8Q6ZS>; Wed, 2 Feb 2000 08:49:46 +0100
Message-ID: <71C2207BEBE5D211BE050008C79F692BB2CEBA@ucspop3.unisource-ucs.com>
From: "Keane, Fiona" <Fiona.Keane@energis-ecs.com>
To: Adrian Zoicas <adrian.zoicas@etsi.fr>,
        =?iso-8859-1?Q?Catherine_Zen?=
	=?iso-8859-1?Q?nstr=F6m?= <cz@everyday.com>,
        Colin Willcock
	 <c.willcock@expert-telecoms.com>,
        Anthony Wiles <anthony.wiles@etsi.fr>,
        Sean White <swhite@shannon.tellabs.com>,
        laurent vreck
	 <laurent.vreck@etsi.fr>,
        Christine Voulgre <christine.voulgre@etsi.fr>,
        Olivier Verdy <olivier.verdy@etsi.fr>,
        Pieter Veenstra
	 <p.k.veenstra@kpn-telecom.nl>,
        Keimpe van der Wal
	 <keimpevanderwal@hotmail.com>,
        Yannick Surzur
	 <yannick.surzur@cnet.francetelecom.fr>,
        Ian Spiers
	 <spiers@ncp.gpt.co.uk>,
        Peter Schmitting <schmitting.fscom@wanadoo.fr>,
        Michael Sanders <michael.sanders@etsi.fr>,
        Graham Rose
	 <graham.rose@etsi.fr>,
        =?iso-8859-1?Q?Jo=EBl_Poulain?=
	 <joel.poulain@etsi.fr>,
        Maurice Pope <maurice.pope@etsi.fr>,
        Emmanuel Piegay <Emmanuel.PIEGAY@dematic-postal.com>,
        Poul Erik Pedersen
	 <poep@tdk.dk>, Henk Oort <hoort@lucent.com>,
        Gerd Ochel
	 <gerd.ochel@etsi.fr>,
        Ultan Mulligan <ultan.mulligan@etsi.fr>,
        =?iso-8859-1?Q?Hans-Peter_M=FCller?=
	 <hans_peter_mueller@darmstadt2.detecon.de>,
        Didier Mouron
	 <dmouron@wanadoo.fr>,
        John Meredith <john.meredith@etsi.fr>,
        Gerry McAuley <gerry.mcauley@etsi.fr>,
        Anders Ljunggren-Svanes
	 <anders.ljunggren@ecsoft.no>,
        Jeanne Lancry <jeanne.lancry@etsi.fr>,
        Denise Kratzer <denise_kratzer@hotmail.com>,
        "Keane, Fiona"
	 <Fiona.Keane@energis-ecs.com>,
        Emmanuelle Jouan
	 <emmanuelle.jouan@etsi.fr>, ietf@ietf.org,
        Karen Hughes
	 <karen.hughes@etsi.fr>,
        Janez Hocevar <janez@usm.mzt.si>, Roberto Gaetano <r.gaetano@iaea.org>,
        =?iso-8859-1?Q?Nad=E8ge_Florival?=
	 <Nadege.Florival@etsi.fr>,
        Laurence Ferrand <laurence.ferrand@etsi.fr>,
        Tormod Egeland <tormod.egeland@grimstad.nett.telenor.no>,
        Keith Drage
	 <keith.drage@siemenscomms.co.uk>,
        Christian Don
	 <christian.don@francetelecom.fr>,
        Ian Doig <ian.doig@etsi.fr>,
        "Claire d'Esclercs" <Claire.Desclercs@etsi.fr>,
        Antoine Caner
	 <antoine.caner@etsi.fr>,
        Mike Briggs <mike.briggs@bt.com>,
        Mark Bogers
	 <mark.bogers@dg3.cec.be>,
        "'mwelser@highway.telekom.at'"
	 <mwelser@highway.telekom.at>
Subject: RE: 
Date: Wed, 2 Feb 2000 08:49:35 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_000_01BF6D52.12B08E90"

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_000_01BF6D52.12B08E90
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Look on the bright side. Your only down the road from little moi!!
This means when I make my trip to Austria (which I will obviously do in =
the
near future given the border is less than 2 hours away), I have someone =
to
show me around.
PS I spent yesterday evening trying to fix a large light to the
ceiling.............on my own. Oh the joys of moving into a new
appartment.........without light fittings!!!


Fiona

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

> Fiona Keane
Engineering=20

Energis (Switzerland) AG
Carrier Services
Industriestrasse 21
CH-8304 Wallisellen
Switzerland
Directline  Phone	+41 1 839 34 06
Reception Phone:	+41 1 839 32 11
Fax:	                +41 1 839 32 95

 <<disclaim.txt>>=20

> ----------
> From: 	Michael Welser[SMTP:michael.welser@aon.at]
> Reply To: 	mwelser@highway.telekom.at
> Sent: 	02 February 2000 00:07
> To: 	Adrian Zoicas; Catherine Zennstr=F6m; Colin Willcock; Anthony =
Wiles;
> Sean White; Laurent Vreck; Christine Voulgre; Olivier Verdy; Pieter
> Veenstra; Keimpe van der Wal; Yannick Surzur; Ian Spiers; Peter
> Schmitting; Michael Sanders; Graham Rose; Jo=EBl Poulain; Maurice =
Pope;
> Emmanuel Piegay; Poul Erik Pedersen; Henk Oort; Gerd Ochel; Ultan
> Mulligan; Hans-Peter M=FCller; Didier Mouron; John Meredith; Gerry =
McAuley;
> Anders Ljunggren-Svanes; Jeanne Lancry; Denise Kratzer; Fiona Keane;
> Emmanuelle Jouan; ietf@ietf.org; Karen Hughes; Janez Hocevar; Roberto
> Gaetano; Nad=E8ge Florival; Laurence Ferrand; Tormod Egeland; Keith =
Drage;
> Christian Don; Ian Doig; Claire d'Esclercs; Antoine Caner; Mike =
Briggs;
> Mark Bogers
>=20
> Dear all,
>=20
> it seems that I chose just the right moment for going back to =
Austria. I
> am
> deeply unhappy about the ongoing political development in this =
country, to
> an
> extent which approaches nausea. Nevertheless, please bear in mind =
that
> when
> meeting three Austrians, "only" one actually voted for Haider.
>=20
> Somewhat desperate, kind regards,
>=20
> Michael
>=20
> ------------------------------------------------------------
> mailto:mwelser@highway.telekom.at         Telekom Austria AG
> tel: +43 (1) 79711 1622                               Abt RS
> fax: +43 (1) 79711 1608                    Arsenal Objekt 22
> http://www.telekom.at                           Postfach 111
> http://www.aon.at                                A-1103 Wien
>=20
>=20

------_=_NextPart_000_01BF6D52.12B08E90
Content-Type: application/octet-stream;
	name="disclaim.txt"
Content-Disposition: attachment;
	filename="disclaim.txt"


This message contains confidential information and is intended only
for the individual named.  If you are not the named addressee you
should not disseminate, distribute or copy this e-mail.  Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses.  The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission.  If
verification is required please request a hard-copy version.  This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities or
related financial instruments.

------_=_NextPart_000_01BF6D52.12B08E90--



From owner-ietf-outbound@ietf.org  Wed Feb  2 03:04:47 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00820
	for <ietf-web-archive@odin.ietf.org>; Wed, 2 Feb 2000 03:04:46 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA22795;
	Wed, 2 Feb 2000 03:02:53 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id DAA00626
	for ietf-outbound.10@ietf.org; Wed, 2 Feb 2000 03:00:02 -0500 (EST)
Received: from ucsi26.energis-ecs.com (pop.energis-ecs.com [212.38.192.79])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00563
	for <ietf@ietf.org>; Wed, 2 Feb 2000 02:51:21 -0500 (EST)
Received: by ucspop3.unisource-ucs.com with Internet Mail Service (5.5.2650.21)
	id <DYA8Q6ZS>; Wed, 2 Feb 2000 08:49:46 +0100
Message-ID: <71C2207BEBE5D211BE050008C79F692BB2CEBA@ucspop3.unisource-ucs.com>
From: "Keane, Fiona" <Fiona.Keane@energis-ecs.com>
To: Adrian Zoicas <adrian.zoicas@etsi.fr>,
        =?iso-8859-1?Q?Catherine_Zen?=
	=?iso-8859-1?Q?nstr=F6m?= <cz@everyday.com>,
        Colin Willcock
	 <c.willcock@expert-telecoms.com>,
        Anthony Wiles <anthony.wiles@etsi.fr>,
        Sean White <swhite@shannon.tellabs.com>,
        laurent vreck
	 <laurent.vreck@etsi.fr>,
        Christine Voulgre <christine.voulgre@etsi.fr>,
        Olivier Verdy <olivier.verdy@etsi.fr>,
        Pieter Veenstra
	 <p.k.veenstra@kpn-telecom.nl>,
        Keimpe van der Wal
	 <keimpevanderwal@hotmail.com>,
        Yannick Surzur
	 <yannick.surzur@cnet.francetelecom.fr>,
        Ian Spiers
	 <spiers@ncp.gpt.co.uk>,
        Peter Schmitting <schmitting.fscom@wanadoo.fr>,
        Michael Sanders <michael.sanders@etsi.fr>,
        Graham Rose
	 <graham.rose@etsi.fr>,
        =?iso-8859-1?Q?Jo=EBl_Poulain?=
	 <joel.poulain@etsi.fr>,
        Maurice Pope <maurice.pope@etsi.fr>,
        Emmanuel Piegay <Emmanuel.PIEGAY@dematic-postal.com>,
        Poul Erik Pedersen
	 <poep@tdk.dk>, Henk Oort <hoort@lucent.com>,
        Gerd Ochel
	 <gerd.ochel@etsi.fr>,
        Ultan Mulligan <ultan.mulligan@etsi.fr>,
        =?iso-8859-1?Q?Hans-Peter_M=FCller?=
	 <hans_peter_mueller@darmstadt2.detecon.de>,
        Didier Mouron
	 <dmouron@wanadoo.fr>,
        John Meredith <john.meredith@etsi.fr>,
        Gerry McAuley <gerry.mcauley@etsi.fr>,
        Anders Ljunggren-Svanes
	 <anders.ljunggren@ecsoft.no>,
        Jeanne Lancry <jeanne.lancry@etsi.fr>,
        Denise Kratzer <denise_kratzer@hotmail.com>,
        "Keane, Fiona"
	 <Fiona.Keane@energis-ecs.com>,
        Emmanuelle Jouan
	 <emmanuelle.jouan@etsi.fr>, ietf@ietf.org,
        Karen Hughes
	 <karen.hughes@etsi.fr>,
        Janez Hocevar <janez@usm.mzt.si>, Roberto Gaetano <r.gaetano@iaea.org>,
        =?iso-8859-1?Q?Nad=E8ge_Florival?=
	 <Nadege.Florival@etsi.fr>,
        Laurence Ferrand <laurence.ferrand@etsi.fr>,
        Tormod Egeland <tormod.egeland@grimstad.nett.telenor.no>,
        Keith Drage
	 <keith.drage@siemenscomms.co.uk>,
        Christian Don
	 <christian.don@francetelecom.fr>,
        Ian Doig <ian.doig@etsi.fr>,
        "Claire d'Esclercs" <Claire.Desclercs@etsi.fr>,
        Antoine Caner
	 <antoine.caner@etsi.fr>,
        Mike Briggs <mike.briggs@bt.com>,
        Mark Bogers
	 <mark.bogers@dg3.cec.be>,
        "'mwelser@highway.telekom.at'"
	 <mwelser@highway.telekom.at>
Subject: RE: 
Date: Wed, 2 Feb 2000 08:49:35 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_000_01BF6D52.12B08E90"

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_000_01BF6D52.12B08E90
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Look on the bright side. Your only down the road from little moi!!
This means when I make my trip to Austria (which I will obviously do in =
the
near future given the border is less than 2 hours away), I have someone =
to
show me around.
PS I spent yesterday evening trying to fix a large light to the
ceiling.............on my own. Oh the joys of moving into a new
appartment.........without light fittings!!!


Fiona

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

> Fiona Keane
Engineering=20

Energis (Switzerland) AG
Carrier Services
Industriestrasse 21
CH-8304 Wallisellen
Switzerland
Directline  Phone	+41 1 839 34 06
Reception Phone:	+41 1 839 32 11
Fax:	                +41 1 839 32 95

 <<disclaim.txt>>=20

> ----------
> From: 	Michael Welser[SMTP:michael.welser@aon.at]
> Reply To: 	mwelser@highway.telekom.at
> Sent: 	02 February 2000 00:07
> To: 	Adrian Zoicas; Catherine Zennstr=F6m; Colin Willcock; Anthony =
Wiles;
> Sean White; Laurent Vreck; Christine Voulgre; Olivier Verdy; Pieter
> Veenstra; Keimpe van der Wal; Yannick Surzur; Ian Spiers; Peter
> Schmitting; Michael Sanders; Graham Rose; Jo=EBl Poulain; Maurice =
Pope;
> Emmanuel Piegay; Poul Erik Pedersen; Henk Oort; Gerd Ochel; Ultan
> Mulligan; Hans-Peter M=FCller; Didier Mouron; John Meredith; Gerry =
McAuley;
> Anders Ljunggren-Svanes; Jeanne Lancry; Denise Kratzer; Fiona Keane;
> Emmanuelle Jouan; ietf@ietf.org; Karen Hughes; Janez Hocevar; Roberto
> Gaetano; Nad=E8ge Florival; Laurence Ferrand; Tormod Egeland; Keith =
Drage;
> Christian Don; Ian Doig; Claire d'Esclercs; Antoine Caner; Mike =
Briggs;
> Mark Bogers
>=20
> Dear all,
>=20
> it seems that I chose just the right moment for going back to =
Austria. I
> am
> deeply unhappy about the ongoing political development in this =
country, to
> an
> extent which approaches nausea. Nevertheless, please bear in mind =
that
> when
> meeting three Austrians, "only" one actually voted for Haider.
>=20
> Somewhat desperate, kind regards,
>=20
> Michael
>=20
> ------------------------------------------------------------
> mailto:mwelser@highway.telekom.at         Telekom Austria AG
> tel: +43 (1) 79711 1622                               Abt RS
> fax: +43 (1) 79711 1608                    Arsenal Objekt 22
> http://www.telekom.at                           Postfach 111
> http://www.aon.at                                A-1103 Wien
>=20
>=20

------_=_NextPart_000_01BF6D52.12B08E90
Content-Type: application/octet-stream;
	name="disclaim.txt"
Content-Disposition: attachment;
	filename="disclaim.txt"


This message contains confidential information and is intended only
for the individual named.  If you are not the named addressee you
should not disseminate, distribute or copy this e-mail.  Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses.  The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission.  If
verification is required please request a hard-copy version.  This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities or
related financial instruments.

------_=_NextPart_000_01BF6D52.12B08E90--



From owner-ietf-outbound  Wed Feb  2 03:30:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA01047
	for ietf-outbound.10@ietf.org; Wed, 2 Feb 2000 03:30:02 -0500 (EST)
Received: from SSP1NO21.highway.telekom.at (EMAIL-AON.highway.telekom.at [195.3.96.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00983
	for <ietf@ietf.org>; Wed, 2 Feb 2000 03:23:03 -0500 (EST)
Received: from mwelser (N011P025.dipool.highway.telekom.at [195.3.65.89])
	by SSP1NO21.highway.telekom.at (8.9.3/8.9.3) with SMTP id JAA435094
	for <ietf@ietf.org>; Wed, 2 Feb 2000 09:23:01 +0100
Reply-To: <mwelser@highway.telekom.at>
From: "Michael Welser" <michael.welser@aon.at>
To: <ietf@ietf.org>
Date: Wed, 2 Feb 2000 09:26:27 +0100
Message-ID: <NCBBKPFPMLHLEIJAJJLLAELIDBAA.michael.welser@aon.at>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I am deeply sorry to have bothered this list with personal my concerns. The
address of ietf@ietf.org slipped in by accident (it was very late in the evening
local time).

Regards,

Michael

------------------------------------------------------------
mailto:mwelser@highway.telekom.at         Telekom Austria AG
tel: +43 (1) 79711 1622                               Abt RS
fax: +43 (1) 79711 1608                    Arsenal Objekt 22
http://www.telekom.at                           Postfach 111
http://www.aon.at                                A-1103 Wien




From owner-ietf-outbound@ietf.org  Wed Feb  2 03:31:10 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01153
	for <ietf-web-archive@odin.ietf.org>; Wed, 2 Feb 2000 03:31:10 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA23455;
	Wed, 2 Feb 2000 03:29:27 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id DAA01047
	for ietf-outbound.10@ietf.org; Wed, 2 Feb 2000 03:30:02 -0500 (EST)
Received: from SSP1NO21.highway.telekom.at (EMAIL-AON.highway.telekom.at [195.3.96.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00983
	for <ietf@ietf.org>; Wed, 2 Feb 2000 03:23:03 -0500 (EST)
Received: from mwelser (N011P025.dipool.highway.telekom.at [195.3.65.89])
	by SSP1NO21.highway.telekom.at (8.9.3/8.9.3) with SMTP id JAA435094
	for <ietf@ietf.org>; Wed, 2 Feb 2000 09:23:01 +0100
Reply-To: <mwelser@highway.telekom.at>
From: "Michael Welser" <michael.welser@aon.at>
To: <ietf@ietf.org>
Date: Wed, 2 Feb 2000 09:26:27 +0100
Message-ID: <NCBBKPFPMLHLEIJAJJLLAELIDBAA.michael.welser@aon.at>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I am deeply sorry to have bothered this list with personal my concerns. The
address of ietf@ietf.org slipped in by accident (it was very late in the evening
local time).

Regards,

Michael

------------------------------------------------------------
mailto:mwelser@highway.telekom.at         Telekom Austria AG
tel: +43 (1) 79711 1622                               Abt RS
fax: +43 (1) 79711 1608                    Arsenal Objekt 22
http://www.telekom.at                           Postfach 111
http://www.aon.at                                A-1103 Wien




From owner-ietf-outbound  Wed Feb  2 03:40:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA01246
	for ietf-outbound.10@ietf.org; Wed, 2 Feb 2000 03:40:02 -0500 (EST)
Received: from suraksha.wipsys.soft.net (suraksha.wipsys.soft.net [202.54.69.9] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01065
	for <ietf@ietf.org>; Wed, 2 Feb 2000 03:30:17 -0500 (EST)
Received: by suraksha.wipsys.soft.net (8.8.8+Sun/SMI-SVR4)
	id NAA18955; Wed, 2 Feb 2000 13:57:59 +0530 (IST)
Received: from bhairavi(192.168.160.25) by suraksha via smap (V2.0)
	id xmaa18943; Wed, 2 Feb 00 13:57:38 +0530
Received: from wipro.com ([192.168.160.237]) by bhairavi.wipsys.soft.net
          (Netscape Messaging Server 3.6)  with ESMTP id AAA496D;
          Wed, 2 Feb 2000 14:00:27 +0530
Message-ID: <3897E56C.A5BB6D9F@wipro.com>
Date: Wed, 02 Feb 2000 13:36:04 +0530
From: "Panditha Govindraj" <govinda.rajp@wipro.com>
Organization: Wipro Global R & D
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: "Keane, Fiona" <Fiona.Keane@energis-ecs.com>
CC: Adrian Zoicas <adrian.zoicas@etsi.fr>,
        "Catherine  =?iso-8859-1?Q?Zennstr=F6m?=" <cz@everyday.com>,
        Colin Willcock  <c.willcock@expert-telecoms.com>,
        Anthony Wiles <anthony.wiles@etsi.fr>,
        Sean White <swhite@shannon.tellabs.com>,
        laurent vreck  <laurent.vreck@etsi.fr>,
        Christine Voulgre <christine.voulgre@etsi.fr>,
        Olivier Verdy <olivier.verdy@etsi.fr>,
        Pieter Veenstra  <p.k.veenstra@kpn-telecom.nl>,
        Keimpe van der Wal  <keimpevanderwal@hotmail.com>,
        Yannick Surzur  <yannick.surzur@cnet.francetelecom.fr>,
        Ian Spiers  <spiers@ncp.gpt.co.uk>,
        Peter Schmitting <schmitting.fscom@wanadoo.fr>,
        Michael Sanders <michael.sanders@etsi.fr>,
        Graham Rose  <graham.rose@etsi.fr>,
        "=?iso-8859-1?Q?Jo=EBl?= Poulain"  <joel.poulain@etsi.fr>,
        Maurice Pope <maurice.pope@etsi.fr>,
        Emmanuel  Piegay <Emmanuel.PIEGAY@dematic-postal.com>,
        Poul Erik Pedersen  <poep@tdk.dk>, Henk Oort <hoort@lucent.com>,
        Gerd Ochel  <gerd.ochel@etsi.fr>,
        Ultan Mulligan <ultan.mulligan@etsi.fr>,
        " Hans-Peter =?iso-8859-1?Q?M=FCller?="  <hans_peter_mueller@darmstadt2.detecon.de>,
        Didier Mouron  <dmouron@wanadoo.fr>,
        John Meredith <john.meredith@etsi.fr>,
        Gerry  McAuley <gerry.mcauley@etsi.fr>,
        Anders Ljunggren-Svanes  <anders.ljunggren@ecsoft.no>,
        Jeanne Lancry <jeanne.lancry@etsi.fr>,
        Denise Kratzer <denise_kratzer@hotmail.com>,
        Emmanuelle Jouan  <emmanuelle.jouan@etsi.fr>, ietf@ietf.org,
        Karen Hughes  <karen.hughes@etsi.fr>, Janez Hocevar <janez@usm.mzt.si>,
        Roberto  Gaetano <r.gaetano@iaea.org>,
        "=?iso-8859-1?Q?Nad=E8ge?= Florival"  <Nadege.Florival@etsi.fr>,
        Laurence Ferrand <laurence.ferrand@etsi.fr>,
        Tormod Egeland <tormod.egeland@grimstad.nett.telenor.no>,
        Keith Drage  <keith.drage@siemenscomms.co.uk>,
        Christian Don  <christian.don@francetelecom.fr>,
        Ian Doig <ian.doig@etsi.fr>,
        "Claire  d'Esclercs" <Claire.Desclercs@etsi.fr>,
        Antoine Caner  <antoine.caner@etsi.fr>,
        Mike Briggs <mike.briggs@bt.com>,
        Mark Bogers  <mark.bogers@dg3.cec.be>,
        "'mwelser@highway.telekom.at'"  <mwelser@highway.telekom.at>
Subject: Re: 
References: <71C2207BEBE5D211BE050008C79F692BB2CEBA@ucspop3.unisource-ucs.com>
Content-Type: multipart/mixed;
 boundary="------------93525CC5B50A5CD5695C19D8"

This is a multi-part message in MIME format.
--------------93525CC5B50A5CD5695C19D8
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Hi All,

    Iam From India , I will be visiting Germany (Munich) for the first time .
Can any body tell me Where to Find a Good and Suitable accomaodation worth abt
20$ to 25$ in Germany Munich.

regards
Govindaraj.P

"Keane, Fiona" wrote:

> Look on the bright side. Your only down the road from little moi!!
> This means when I make my trip to Austria (which I will obviously do in the
> near future given the border is less than 2 hours away), I have someone to
> show me around.
> PS I spent yesterday evening trying to fix a large light to the
> ceiling.............on my own. Oh the joys of moving into a new
> appartment.........without light fittings!!!
>
> Fiona
>
> *************************************************************
>
> > Fiona Keane
> Engineering
>
> Energis (Switzerland) AG
> Carrier Services
> Industriestrasse 21
> CH-8304 Wallisellen
> Switzerland
> Directline  Phone       +41 1 839 34 06
> Reception Phone:        +41 1 839 32 11
> Fax:                    +41 1 839 32 95
>
>  <<disclaim.txt>>
>
> > ----------
> > From:         Michael Welser[SMTP:michael.welser@aon.at]
> > Reply To:     mwelser@highway.telekom.at
> > Sent:         02 February 2000 00:07
> > To:   Adrian Zoicas; Catherine Zennström; Colin Willcock; Anthony Wiles;
> > Sean White; Laurent Vreck; Christine Voulgre; Olivier Verdy; Pieter
> > Veenstra; Keimpe van der Wal; Yannick Surzur; Ian Spiers; Peter
> > Schmitting; Michael Sanders; Graham Rose; Joël Poulain; Maurice Pope;
> > Emmanuel Piegay; Poul Erik Pedersen; Henk Oort; Gerd Ochel; Ultan
> > Mulligan; Hans-Peter Müller; Didier Mouron; John Meredith; Gerry McAuley;
> > Anders Ljunggren-Svanes; Jeanne Lancry; Denise Kratzer; Fiona Keane;
> > Emmanuelle Jouan; ietf@ietf.org; Karen Hughes; Janez Hocevar; Roberto
> > Gaetano; Nadčge Florival; Laurence Ferrand; Tormod Egeland; Keith Drage;
> > Christian Don; Ian Doig; Claire d'Esclercs; Antoine Caner; Mike Briggs;
> > Mark Bogers
> >
> > Dear all,
> >
> > it seems that I chose just the right moment for going back to Austria. I
> > am
> > deeply unhappy about the ongoing political development in this country, to
> > an
> > extent which approaches nausea. Nevertheless, please bear in mind that
> > when
> > meeting three Austrians, "only" one actually voted for Haider.
> >
> > Somewhat desperate, kind regards,
> >
> > Michael
> >
> > ------------------------------------------------------------
> > mailto:mwelser@highway.telekom.at         Telekom Austria AG
> > tel: +43 (1) 79711 1622                               Abt RS
> > fax: +43 (1) 79711 1608                    Arsenal Objekt 22
> > http://www.telekom.at                           Postfach 111
> > http://www.aon.at                                A-1103 Wien
> >
> >
>
>   ------------------------------------------------------------------------
>
>    disclaim.txtName: disclaim.txt
>                Type: Plain Text (text/plain)

--------------93525CC5B50A5CD5695C19D8
Content-Type: text/x-vcard; charset=us-ascii;
 name="govinda.rajp.vcf"
Content-Description: Card for Govindaraj Panditha
Content-Disposition: attachment;
 filename="govinda.rajp.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Panditha;Govindaraj
tel;home:91-44-4830675
tel;work:91-44-2301530 Ext 339
x-mozilla-html:FALSE
url:http://www.wipro.com
org:Wipro Global R & D;CHENNAI 
version:2.1
email;internet:govinda.rajp@wipro.com
title:Senior Engineer Software
note:Iam Just Collecting Pebbles in SEA SHORE
adr;quoted-printable:;;111, Anna Salai=0D=0A2nd Floor=0D=0AGuindy;CHENNAI;Tamil Nadu;600032;India
x-mozilla-cpt:wipro.com;-5744
fn:Govindaraj Panditha
end:vcard

--------------93525CC5B50A5CD5695C19D8--



From owner-ietf-outbound@ietf.org  Wed Feb  2 03:41:39 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01308
	for <ietf-web-archive@odin.ietf.org>; Wed, 2 Feb 2000 03:41:39 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA23738;
	Wed, 2 Feb 2000 03:39:50 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id DAA01246
	for ietf-outbound.10@ietf.org; Wed, 2 Feb 2000 03:40:02 -0500 (EST)
Received: from suraksha.wipsys.soft.net (suraksha.wipsys.soft.net [202.54.69.9] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01065
	for <ietf@ietf.org>; Wed, 2 Feb 2000 03:30:17 -0500 (EST)
Received: by suraksha.wipsys.soft.net (8.8.8+Sun/SMI-SVR4)
	id NAA18955; Wed, 2 Feb 2000 13:57:59 +0530 (IST)
Received: from bhairavi(192.168.160.25) by suraksha via smap (V2.0)
	id xmaa18943; Wed, 2 Feb 00 13:57:38 +0530
Received: from wipro.com ([192.168.160.237]) by bhairavi.wipsys.soft.net
          (Netscape Messaging Server 3.6)  with ESMTP id AAA496D;
          Wed, 2 Feb 2000 14:00:27 +0530
Message-ID: <3897E56C.A5BB6D9F@wipro.com>
Date: Wed, 02 Feb 2000 13:36:04 +0530
From: "Panditha Govindraj" <govinda.rajp@wipro.com>
Organization: Wipro Global R & D
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: "Keane, Fiona" <Fiona.Keane@energis-ecs.com>
CC: Adrian Zoicas <adrian.zoicas@etsi.fr>,
        "Catherine  =?iso-8859-1?Q?Zennstr=F6m?=" <cz@everyday.com>,
        Colin Willcock  <c.willcock@expert-telecoms.com>,
        Anthony Wiles <anthony.wiles@etsi.fr>,
        Sean White <swhite@shannon.tellabs.com>,
        laurent vreck  <laurent.vreck@etsi.fr>,
        Christine Voulgre <christine.voulgre@etsi.fr>,
        Olivier Verdy <olivier.verdy@etsi.fr>,
        Pieter Veenstra  <p.k.veenstra@kpn-telecom.nl>,
        Keimpe van der Wal  <keimpevanderwal@hotmail.com>,
        Yannick Surzur  <yannick.surzur@cnet.francetelecom.fr>,
        Ian Spiers  <spiers@ncp.gpt.co.uk>,
        Peter Schmitting <schmitting.fscom@wanadoo.fr>,
        Michael Sanders <michael.sanders@etsi.fr>,
        Graham Rose  <graham.rose@etsi.fr>,
        "=?iso-8859-1?Q?Jo=EBl?= Poulain"  <joel.poulain@etsi.fr>,
        Maurice Pope <maurice.pope@etsi.fr>,
        Emmanuel  Piegay <Emmanuel.PIEGAY@dematic-postal.com>,
        Poul Erik Pedersen  <poep@tdk.dk>, Henk Oort <hoort@lucent.com>,
        Gerd Ochel  <gerd.ochel@etsi.fr>,
        Ultan Mulligan <ultan.mulligan@etsi.fr>,
        " Hans-Peter =?iso-8859-1?Q?M=FCller?="  <hans_peter_mueller@darmstadt2.detecon.de>,
        Didier Mouron  <dmouron@wanadoo.fr>,
        John Meredith <john.meredith@etsi.fr>,
        Gerry  McAuley <gerry.mcauley@etsi.fr>,
        Anders Ljunggren-Svanes  <anders.ljunggren@ecsoft.no>,
        Jeanne Lancry <jeanne.lancry@etsi.fr>,
        Denise Kratzer <denise_kratzer@hotmail.com>,
        Emmanuelle Jouan  <emmanuelle.jouan@etsi.fr>, ietf@ietf.org,
        Karen Hughes  <karen.hughes@etsi.fr>, Janez Hocevar <janez@usm.mzt.si>,
        Roberto  Gaetano <r.gaetano@iaea.org>,
        "=?iso-8859-1?Q?Nad=E8ge?= Florival"  <Nadege.Florival@etsi.fr>,
        Laurence Ferrand <laurence.ferrand@etsi.fr>,
        Tormod Egeland <tormod.egeland@grimstad.nett.telenor.no>,
        Keith Drage  <keith.drage@siemenscomms.co.uk>,
        Christian Don  <christian.don@francetelecom.fr>,
        Ian Doig <ian.doig@etsi.fr>,
        "Claire  d'Esclercs" <Claire.Desclercs@etsi.fr>,
        Antoine Caner  <antoine.caner@etsi.fr>,
        Mike Briggs <mike.briggs@bt.com>,
        Mark Bogers  <mark.bogers@dg3.cec.be>,
        "'mwelser@highway.telekom.at'"  <mwelser@highway.telekom.at>
Subject: Re: 
References: <71C2207BEBE5D211BE050008C79F692BB2CEBA@ucspop3.unisource-ucs.com>
Content-Type: multipart/mixed;
 boundary="------------93525CC5B50A5CD5695C19D8"

This is a multi-part message in MIME format.
--------------93525CC5B50A5CD5695C19D8
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Hi All,

    Iam From India , I will be visiting Germany (Munich) for the first time .
Can any body tell me Where to Find a Good and Suitable accomaodation worth abt
20$ to 25$ in Germany Munich.

regards
Govindaraj.P

"Keane, Fiona" wrote:

> Look on the bright side. Your only down the road from little moi!!
> This means when I make my trip to Austria (which I will obviously do in the
> near future given the border is less than 2 hours away), I have someone to
> show me around.
> PS I spent yesterday evening trying to fix a large light to the
> ceiling.............on my own. Oh the joys of moving into a new
> appartment.........without light fittings!!!
>
> Fiona
>
> *************************************************************
>
> > Fiona Keane
> Engineering
>
> Energis (Switzerland) AG
> Carrier Services
> Industriestrasse 21
> CH-8304 Wallisellen
> Switzerland
> Directline  Phone       +41 1 839 34 06
> Reception Phone:        +41 1 839 32 11
> Fax:                    +41 1 839 32 95
>
>  <<disclaim.txt>>
>
> > ----------
> > From:         Michael Welser[SMTP:michael.welser@aon.at]
> > Reply To:     mwelser@highway.telekom.at
> > Sent:         02 February 2000 00:07
> > To:   Adrian Zoicas; Catherine Zennström; Colin Willcock; Anthony Wiles;
> > Sean White; Laurent Vreck; Christine Voulgre; Olivier Verdy; Pieter
> > Veenstra; Keimpe van der Wal; Yannick Surzur; Ian Spiers; Peter
> > Schmitting; Michael Sanders; Graham Rose; Joël Poulain; Maurice Pope;
> > Emmanuel Piegay; Poul Erik Pedersen; Henk Oort; Gerd Ochel; Ultan
> > Mulligan; Hans-Peter Müller; Didier Mouron; John Meredith; Gerry McAuley;
> > Anders Ljunggren-Svanes; Jeanne Lancry; Denise Kratzer; Fiona Keane;
> > Emmanuelle Jouan; ietf@ietf.org; Karen Hughes; Janez Hocevar; Roberto
> > Gaetano; Nadčge Florival; Laurence Ferrand; Tormod Egeland; Keith Drage;
> > Christian Don; Ian Doig; Claire d'Esclercs; Antoine Caner; Mike Briggs;
> > Mark Bogers
> >
> > Dear all,
> >
> > it seems that I chose just the right moment for going back to Austria. I
> > am
> > deeply unhappy about the ongoing political development in this country, to
> > an
> > extent which approaches nausea. Nevertheless, please bear in mind that
> > when
> > meeting three Austrians, "only" one actually voted for Haider.
> >
> > Somewhat desperate, kind regards,
> >
> > Michael
> >
> > ------------------------------------------------------------
> > mailto:mwelser@highway.telekom.at         Telekom Austria AG
> > tel: +43 (1) 79711 1622                               Abt RS
> > fax: +43 (1) 79711 1608                    Arsenal Objekt 22
> > http://www.telekom.at                           Postfach 111
> > http://www.aon.at                                A-1103 Wien
> >
> >
>
>   ------------------------------------------------------------------------
>
>    disclaim.txtName: disclaim.txt
>                Type: Plain Text (text/plain)

--------------93525CC5B50A5CD5695C19D8
Content-Type: text/x-vcard; charset=us-ascii;
 name="govinda.rajp.vcf"
Content-Description: Card for Govindaraj Panditha
Content-Disposition: attachment;
 filename="govinda.rajp.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Panditha;Govindaraj
tel;home:91-44-4830675
tel;work:91-44-2301530 Ext 339
x-mozilla-html:FALSE
url:http://www.wipro.com
org:Wipro Global R & D;CHENNAI 
version:2.1
email;internet:govinda.rajp@wipro.com
title:Senior Engineer Software
note:Iam Just Collecting Pebbles in SEA SHORE
adr;quoted-printable:;;111, Anna Salai=0D=0A2nd Floor=0D=0AGuindy;CHENNAI;Tamil Nadu;600032;India
x-mozilla-cpt:wipro.com;-5744
fn:Govindaraj Panditha
end:vcard

--------------93525CC5B50A5CD5695C19D8--



From owner-ietf-outbound  Wed Feb  2 08:50:54 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA08537
	for ietf-outbound.10@ietf.org; Wed, 2 Feb 2000 08:50:02 -0500 (EST)
Received: from relay1.pair.com (relay1.pair.com [209.68.1.20])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA08276
	for <ietf@ietf.org>; Wed, 2 Feb 2000 08:45:46 -0500 (EST)
Received: (qmail 26377 invoked from network); 2 Feb 2000 13:44:25 -0000
Received: from flure.pair.com (HELO asgard) (209.68.1.159)
  by relay1.pair.com with SMTP; 2 Feb 2000 13:44:25 -0000
X-pair-Authenticated: 209.68.1.159
From: "Thomas Wolfram" <thomas@wolfram.net>
To: "Keane, Fiona" <Fiona.Keane@energis-ecs.com>,
        "Panditha Govindraj" <govinda.rajp@wipro.com>
Cc: <mwelser@highway.telekom.at>, <ietf@ietf.org>
Subject: RE: 
Date: Wed, 2 Feb 2000 14:44:56 +0100
Message-ID: <NDBBLNHJKCGKDMCNLPFHCEIECBAA.thomas@wolfram.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
In-Reply-To: <3897E56C.A5BB6D9F@wipro.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id IAA08276
Content-Transfer-Encoding: 8bit


Hi,

Panditha Govindraj wrote:
> 
> Hi All,
> 
>     Iam From India , I will be visiting Germany (Munich) for the 
> first time .
> Can any body tell me Where to Find a Good and Suitable 
> accomaodation worth abt
> 20$ to 25$ in Germany Munich.

check out: http://www.munich-tourist.de/ (under "Munich Key")
regards,



From owner-ietf-outbound@ietf.org  Wed Feb  2 09:04:59 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09353
	for <ietf-web-archive@odin.ietf.org>; Wed, 2 Feb 2000 09:04:54 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA02652;
	Wed, 2 Feb 2000 09:03:07 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id IAA08537
	for ietf-outbound.10@ietf.org; Wed, 2 Feb 2000 08:50:02 -0500 (EST)
Received: from relay1.pair.com (relay1.pair.com [209.68.1.20])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA08276
	for <ietf@ietf.org>; Wed, 2 Feb 2000 08:45:46 -0500 (EST)
Received: (qmail 26377 invoked from network); 2 Feb 2000 13:44:25 -0000
Received: from flure.pair.com (HELO asgard) (209.68.1.159)
  by relay1.pair.com with SMTP; 2 Feb 2000 13:44:25 -0000
X-pair-Authenticated: 209.68.1.159
From: "Thomas Wolfram" <thomas@wolfram.net>
To: "Keane, Fiona" <Fiona.Keane@energis-ecs.com>,
        "Panditha Govindraj" <govinda.rajp@wipro.com>
Cc: <mwelser@highway.telekom.at>, <ietf@ietf.org>
Subject: RE: 
Date: Wed, 2 Feb 2000 14:44:56 +0100
Message-ID: <NDBBLNHJKCGKDMCNLPFHCEIECBAA.thomas@wolfram.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
In-Reply-To: <3897E56C.A5BB6D9F@wipro.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id IAA08276
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit


Hi,

Panditha Govindraj wrote:
> 
> Hi All,
> 
>     Iam From India , I will be visiting Germany (Munich) for the 
> first time .
> Can any body tell me Where to Find a Good and Suitable 
> accomaodation worth abt
> 20$ to 25$ in Germany Munich.

check out: http://www.munich-tourist.de/ (under "Munich Key")
regards,



From owner-ietf-outbound  Wed Feb  2 14:01:26 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA18201
	for ietf-outbound.10@ietf.org; Wed, 2 Feb 2000 14:00:02 -0500 (EST)
Received: from www.dci.co.ir ([195.146.32.3])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA18106
	for <IETF@IETF.ORG>; Wed, 2 Feb 2000 13:54:27 -0500 (EST)
From: Mahouti.ir@www.dci.co.ir
Message-Id: <200002021854.NAA18106@ietf.org>
To: IETF@ietf.org
Date: 2 Feb 2000 22:24:02 EDT
Subject: M





                         MAHOUTI
                  P. O. BOX 14185-374
                  TEHERAN,      IRAN.
      PHONE: (98-21)922405, TELEX:214496 MAHO IR
      URL: WWW.AZAD.AC.IR/USERS/MAHOUTI/HOME.HTM
          E-MAIL:  MAHOUTI.IR@WWW.DCI.CO.IR
                 FAX: (98-21) 922 405


Gentlemen:

We wish to invite you to participate in the
Tabriz / Iran International Fair to be  held
9 - 14 May, 2000. Exhibiting Building, Construction,
Road and Highway Materials and related Equipments.

Tabriz is the Iran's largest and or Industrial
City with over 2,000,000 popul
ering with Turkey, Armenia and
Azarbayjan. Attracting visitors from these Countries.

Costs are very reasonable, your Hotel, Meals and
12 Meters of Hall space fone week will be about
USD 4,500.--
           tion,
will be cleared from customs by the Fair authorities
and you may sell or take back as you prefer. No need
for you to have an agent in Iran.

Your questions to our E-MAIL address appreciated.

Best Regards

Hamid  Mahouti



              



From owner-ietf-outbound@ietf.org  Wed Feb  2 14:04:23 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18425
	for <ietf-web-archive@odin.ietf.org>; Wed, 2 Feb 2000 14:04:23 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA14077;
	Wed, 2 Feb 2000 14:02:31 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id OAA18201
	for ietf-outbound.10@ietf.org; Wed, 2 Feb 2000 14:00:02 -0500 (EST)
Received: from www.dci.co.ir ([195.146.32.3])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA18106
	for <IETF@IETF.ORG>; Wed, 2 Feb 2000 13:54:27 -0500 (EST)
From: Mahouti.ir@www.dci.co.ir
Message-Id: <200002021854.NAA18106@ietf.org>
To: IETF@ietf.org
Date: 2 Feb 2000 22:24:02 EDT
Subject: M





                         MAHOUTI
                  P. O. BOX 14185-374
                  TEHERAN,      IRAN.
      PHONE: (98-21)922405, TELEX:214496 MAHO IR
      URL: WWW.AZAD.AC.IR/USERS/MAHOUTI/HOME.HTM
          E-MAIL:  MAHOUTI.IR@WWW.DCI.CO.IR
                 FAX: (98-21) 922 405


Gentlemen:

We wish to invite you to participate in the
Tabriz / Iran International Fair to be  held
9 - 14 May, 2000. Exhibiting Building, Construction,
Road and Highway Materials and related Equipments.

Tabriz is the Iran's largest and or Industrial
City with over 2,000,000 popul
ering with Turkey, Armenia and
Azarbayjan. Attracting visitors from these Countries.

Costs are very reasonable, your Hotel, Meals and
12 Meters of Hall space fone week will be about
USD 4,500.--
           tion,
will be cleared from customs by the Fair authorities
and you may sell or take back as you prefer. No need
for you to have an agent in Iran.

Your questions to our E-MAIL address appreciated.

Best Regards

Hamid  Mahouti



              



From owner-ietf-outbound  Wed Feb  2 19:00:39 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA23746
	for ietf-outbound.10@ietf.org; Wed, 2 Feb 2000 19:00:05 -0500 (EST)
Received: from osf1.gmu.edu (osf1.gmu.edu [129.174.1.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23675
	for <IETF@ietf.org>; Wed, 2 Feb 2000 18:52:32 -0500 (EST)
Received: from localhost (hgadi1@localhost)
	by osf1.gmu.edu (8.8.8/8.8.8) with ESMTP id SAA09664
	for <IETF@ietf.org>; Wed, 2 Feb 2000 18:52:33 -0500 (EST)
Date: Wed, 2 Feb 2000 18:52:33 -0500 (EST)
From: Hari Bapiraju Gadi <hgadi1@osf1.gmu.edu>
To: IETF@ietf.org
Subject: fragmentation?
In-Reply-To: <200002021854.NAA18106@ietf.org>
Message-ID: <Pine.OSF.4.21.0002021848050.7989-100000@osf1.gmu.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Hello,

Apart from RFC 791 and RFC 815, are there any RFC's talking about
fragmentaion algorithms.Does anyone know good resources about fragmention
and their implementation code.

Thanks,

Hari B.Gadi 



From owner-ietf-outbound@ietf.org  Wed Feb  2 19:04:29 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA23875
	for <ietf-web-archive@odin.ietf.org>; Wed, 2 Feb 2000 19:04:29 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA22857;
	Wed, 2 Feb 2000 19:02:38 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id TAA23746
	for ietf-outbound.10@ietf.org; Wed, 2 Feb 2000 19:00:05 -0500 (EST)
Received: from osf1.gmu.edu (osf1.gmu.edu [129.174.1.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23675
	for <IETF@ietf.org>; Wed, 2 Feb 2000 18:52:32 -0500 (EST)
Received: from localhost (hgadi1@localhost)
	by osf1.gmu.edu (8.8.8/8.8.8) with ESMTP id SAA09664
	for <IETF@ietf.org>; Wed, 2 Feb 2000 18:52:33 -0500 (EST)
Date: Wed, 2 Feb 2000 18:52:33 -0500 (EST)
From: Hari Bapiraju Gadi <hgadi1@osf1.gmu.edu>
To: IETF@ietf.org
Subject: fragmentation?
In-Reply-To: <200002021854.NAA18106@ietf.org>
Message-ID: <Pine.OSF.4.21.0002021848050.7989-100000@osf1.gmu.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Hello,

Apart from RFC 791 and RFC 815, are there any RFC's talking about
fragmentaion algorithms.Does anyone know good resources about fragmention
and their implementation code.

Thanks,

Hari B.Gadi 



From owner-ietf-outbound  Wed Feb  2 22:40:47 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA27572
	for ietf-outbound.10@ietf.org; Wed, 2 Feb 2000 22:40:02 -0500 (EST)
Received: from osf1.gmu.edu (osf1.gmu.edu [129.174.1.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27543
	for <IETF@ietf.org>; Wed, 2 Feb 2000 22:38:10 -0500 (EST)
Received: from localhost (hgadi1@localhost)
	by osf1.gmu.edu (8.8.8/8.8.8) with ESMTP id WAA10472;
	Wed, 2 Feb 2000 22:38:10 -0500 (EST)
Date: Wed, 2 Feb 2000 22:38:10 -0500 (EST)
From: Hari Bapiraju Gadi <hgadi1@osf1.gmu.edu>
To: Bob Braden <braden@ISI.EDU>
cc: IETF@ietf.org
Subject: Re: fragmentation?
In-Reply-To: <200002030041.AAA02431@gra.isi.edu>
Message-ID: <Pine.OSF.4.21.0002022233140.2435-100000@osf1.gmu.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Dear Mr.Braden,
I meant both fragmentation as well as reassembly.
I was looking at linux implementation, its good enough.

But I wanted to make sure that I was not missing anything.

Thanks for your reply,
Hari B.Gadi.

On Thu, 3 Feb 2000,
Bob
Braden wrote:

> 
> Fragmentation is trivial; it is reassembly that is tricky.
> 
> Bob Braden
> 



From owner-ietf-outbound@ietf.org  Wed Feb  2 22:42:19 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27752
	for <ietf-web-archive@odin.ietf.org>; Wed, 2 Feb 2000 22:42:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA00734;
	Wed, 2 Feb 2000 22:40:27 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id WAA27572
	for ietf-outbound.10@ietf.org; Wed, 2 Feb 2000 22:40:02 -0500 (EST)
Received: from osf1.gmu.edu (osf1.gmu.edu [129.174.1.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27543
	for <IETF@ietf.org>; Wed, 2 Feb 2000 22:38:10 -0500 (EST)
Received: from localhost (hgadi1@localhost)
	by osf1.gmu.edu (8.8.8/8.8.8) with ESMTP id WAA10472;
	Wed, 2 Feb 2000 22:38:10 -0500 (EST)
Date: Wed, 2 Feb 2000 22:38:10 -0500 (EST)
From: Hari Bapiraju Gadi <hgadi1@osf1.gmu.edu>
To: Bob Braden <braden@ISI.EDU>
cc: IETF@ietf.org
Subject: Re: fragmentation?
In-Reply-To: <200002030041.AAA02431@gra.isi.edu>
Message-ID: <Pine.OSF.4.21.0002022233140.2435-100000@osf1.gmu.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Dear Mr.Braden,
I meant both fragmentation as well as reassembly.
I was looking at linux implementation, its good enough.

But I wanted to make sure that I was not missing anything.

Thanks for your reply,
Hari B.Gadi.

On Thu, 3 Feb 2000,
Bob
Braden wrote:

> 
> Fragmentation is trivial; it is reassembly that is tricky.
> 
> Bob Braden
> 



From owner-ietf-outbound  Thu Feb  3 11:41:55 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA22201
	for ietf-outbound.10@ietf.org; Thu, 3 Feb 2000 11:40:02 -0500 (EST)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22118
	for <IETF@ietf.org>; Thu, 3 Feb 2000 11:35:19 -0500 (EST)
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id IAA10146;
	Thu, 3 Feb 2000 08:35:16 -0800 (PST)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost)
	by gra.isi.edu (8.8.7/8.8.6) id QAA02618;
	Thu, 3 Feb 2000 16:35:16 GMT
Date: Thu, 3 Feb 2000 16:35:16 GMT
Message-Id: <200002031635.QAA02618@gra.isi.edu>
To: braden@ISI.EDU, hgadi1@osf1.gmu.edu
Subject: Re: fragmentation?
Cc: IETF@ietf.org
X-Sun-Charset: US-ASCII


  *> From hgadi1@osf1.gmu.edu Wed Feb  2 19:38:12 2000
  *> Date: Wed, 2 Feb 2000 22:38:10 -0500 (EST)
  *> From: Hari Bapiraju Gadi <hgadi1@osf1.gmu.edu>
  *> To: Bob Braden <braden@ISI.EDU>
  *> cc: IETF@ietf.org
  *> Subject: Re: fragmentation?
  *> In-Reply-To: <200002030041.AAA02431@gra.isi.edu>
  *> MIME-Version: 1.0
  *> X-Lines: 19
  *> 
  *> Dear Mr.Braden,
  *> I meant both fragmentation as well as reassembly.
  *> I was looking at linux implementation, its good enough.
  *> 
  *> But I wanted to make sure that I was not missing anything.

If you have not seen Dave Clark's RFC on reassembly, you have
missed something.  Do you need an RFC #? It was one of the famous
"Dave Clark 5" RFCs, somewhere in the later 800s as I remember.

Bob



From owner-ietf-outbound@ietf.org  Thu Feb  3 13:53:47 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26683
	for <ietf-web-archive@odin.ietf.org>; Thu, 3 Feb 2000 13:53:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA09086
	for <ietf-web-archive@optimus.ietf.org>; Thu, 3 Feb 2000 13:51:48 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id LAA22201
	for ietf-outbound.10@ietf.org; Thu, 3 Feb 2000 11:40:02 -0500 (EST)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22118
	for <IETF@ietf.org>; Thu, 3 Feb 2000 11:35:19 -0500 (EST)
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id IAA10146;
	Thu, 3 Feb 2000 08:35:16 -0800 (PST)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost)
	by gra.isi.edu (8.8.7/8.8.6) id QAA02618;
	Thu, 3 Feb 2000 16:35:16 GMT
Date: Thu, 3 Feb 2000 16:35:16 GMT
Message-Id: <200002031635.QAA02618@gra.isi.edu>
To: braden@ISI.EDU, hgadi1@osf1.gmu.edu
Subject: Re: fragmentation?
Cc: IETF@ietf.org
X-Sun-Charset: US-ASCII


  *> From hgadi1@osf1.gmu.edu Wed Feb  2 19:38:12 2000
  *> Date: Wed, 2 Feb 2000 22:38:10 -0500 (EST)
  *> From: Hari Bapiraju Gadi <hgadi1@osf1.gmu.edu>
  *> To: Bob Braden <braden@ISI.EDU>
  *> cc: IETF@ietf.org
  *> Subject: Re: fragmentation?
  *> In-Reply-To: <200002030041.AAA02431@gra.isi.edu>
  *> MIME-Version: 1.0
  *> X-Lines: 19
  *> 
  *> Dear Mr.Braden,
  *> I meant both fragmentation as well as reassembly.
  *> I was looking at linux implementation, its good enough.
  *> 
  *> But I wanted to make sure that I was not missing anything.

If you have not seen Dave Clark's RFC on reassembly, you have
missed something.  Do you need an RFC #? It was one of the famous
"Dave Clark 5" RFCs, somewhere in the later 800s as I remember.

Bob



From owner-ietf-outbound  Thu Feb  3 20:00:39 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA02856
	for ietf-outbound.10@ietf.org; Thu, 3 Feb 2000 20:00:03 -0500 (EST)
Received: from server.jad.net ([202.134.2.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02803
	for <ietf@ietf.org>; Thu, 3 Feb 2000 19:56:08 -0500 (EST)
Received: from oke.com (cf-isrlab7.comp.nus.edu.sg [137.132.85.181])
	by server.jad.net (8.9.2/8.9.2) with ESMTP id IAA82672;
	Fri, 4 Feb 2000 08:56:51 +0700 (JAVT)
	(envelope-from rms46@oke.com)
Sender: ibrahim@server.jad.net
Message-ID: <389A238C.27FA1B46@oke.com>
Date: Fri, 04 Feb 2000 08:55:40 +0800
From: "Rahmat M. Samik-Ibrahim" <rms46@oke.com>
Reply-To: rms46.oke.com@vlsm.org
Organization: VLSM-TJT
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5-22 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: MILIS IETF <ietf@ietf.org>, hgadi1@osf1.gmu.edu
Subject: Re: fragmentation?
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hello:

> If you have not seen Dave Clark's RFC on reassembly, you have
> missed something.  Do you need an RFC #? It was one of the famous
> "Dave Clark 5" RFCs, somewhere in the later 800s as I remember.

0815 IP datagram reassembly algorithms. D.D. Clark. Jul-01-1982.
     (Format: TXT=14575 bytes) (Status: UNKNOWN)

See also http://www.ietf.org/rfc/rfc0815.txt


Gong Xi Fa Cai, 
Hong Bao Na Lai 
(=a prosperous millennium :-),

-- 
- Rahmat M. Samik-Ibrahim --  VLSM-TJT --  http://rms46.vlsm.org/ -
- Da da da ich lieb dich nicht du liebst mich nicht aha -- TRIO82 -



From owner-ietf-outbound@ietf.org  Thu Feb  3 20:02:16 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02967
	for <ietf-web-archive@odin.ietf.org>; Thu, 3 Feb 2000 20:02:16 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA28042;
	Thu, 3 Feb 2000 20:00:20 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id UAA02856
	for ietf-outbound.10@ietf.org; Thu, 3 Feb 2000 20:00:03 -0500 (EST)
Received: from server.jad.net ([202.134.2.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02803
	for <ietf@ietf.org>; Thu, 3 Feb 2000 19:56:08 -0500 (EST)
Received: from oke.com (cf-isrlab7.comp.nus.edu.sg [137.132.85.181])
	by server.jad.net (8.9.2/8.9.2) with ESMTP id IAA82672;
	Fri, 4 Feb 2000 08:56:51 +0700 (JAVT)
	(envelope-from rms46@oke.com)
Sender: ibrahim@server.jad.net
Message-ID: <389A238C.27FA1B46@oke.com>
Date: Fri, 04 Feb 2000 08:55:40 +0800
From: "Rahmat M. Samik-Ibrahim" <rms46@oke.com>
Reply-To: rms46.oke.com@vlsm.org
Organization: VLSM-TJT
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5-22 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: MILIS IETF <ietf@ietf.org>, hgadi1@osf1.gmu.edu
Subject: Re: fragmentation?
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hello:

> If you have not seen Dave Clark's RFC on reassembly, you have
> missed something.  Do you need an RFC #? It was one of the famous
> "Dave Clark 5" RFCs, somewhere in the later 800s as I remember.

0815 IP datagram reassembly algorithms. D.D. Clark. Jul-01-1982.
     (Format: TXT=14575 bytes) (Status: UNKNOWN)

See also http://www.ietf.org/rfc/rfc0815.txt


Gong Xi Fa Cai, 
Hong Bao Na Lai 
(=a prosperous millennium :-),

-- 
- Rahmat M. Samik-Ibrahim --  VLSM-TJT --  http://rms46.vlsm.org/ -
- Da da da ich lieb dich nicht du liebst mich nicht aha -- TRIO82 -



From owner-ietf-outbound  Fri Feb  4 09:39:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA28262
	for ietf-outbound.10@ietf.org; Fri, 4 Feb 2000 09:36:33 -0500 (EST)
Received: from mason.buystainlessonline.com (216-59-114-105.usa2.flashcom.net [216.59.114.105])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA26688
	for <ietf@ietf.org>; Fri, 4 Feb 2000 09:00:30 -0500 (EST)
From: auctions@buystainlessonline.com
Message-Id: <cckvhpivfufbrr.tmdtwyltdxueqbfw@mason.buystainlessonline.com>
MIME-Version: 1.0
X-Encoding: MIME
Content-Type: multipart/alternative;
	boundary="----=_NextPart_320623751655725754604743121"
Reply-To: webmaster@buystainlessonline.com
Date: Fri, 04 Feb 2000 08:57:59 -0500
To: ietf@ietf.org
Subject: 4 year high for Nickel on the LME

This is a multi-part message in MIME format.

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

StainlessOnly! is a weekly Stainless Steel related Electronic Magazine. We are
currently reaching:23,677 readers.

BuyStainlessOnline gears up for change!
This week and next will mark a transitional period for our site. The 
following STOCK products will become available:
Rounds, Sheets, Plate, Pipe, Tube, Coil, and Welding Wire.
We have also been receiving a large number of requests for 
Nuts and Bolts (Fasteners). More on that later 

LME nickel prices hit 4-year high
LONDON, Feb. 2 -- Nickel tallied prices not seen in more than four
Years in early ring trading on the London Metal Exchange Wednesday.
A high of $8,900 per tonne was reached in the first ring in what analysts
And dealers said was a result of primarily fund and speculative buying.
LME nickel inventories also fell 138 tonnes to 42,324 tonnes, reaching
Their lowest level since 1991.

Anaconda Nickel output 'minimal'
SYDNEY, Australia, Jan. 31 (Reuters) -- Lateritic nickel producer Anaconda Nickel Ltd. said Monday it expects to reach cash positive operations in the March quarter after "minimal" production of high-grade nickel and cobalt in the December quarter. In its December quarterly report, Anaconda said it produced 600 tonnes of London Metal Exchange-grade nickel at Murrin Murrin in Western Australia in the month of December and 53 tonnes of high-grade cobalt. No figures were given for October and November. The level of impurities in the metal had been minimal and quality was improving as operator experience increased. Anaconda said mechanical and construction material issues had delayed the commissioning and ramp-up of the project, but production had confirmed the robustness of the process.

What can you expect as a buyer?
For the next six months (At Least) OEM people along with smaller sized
Distributors will experience continually climbing prices and virtually
All stainless items. Those items produced overseas (namely ANGLE from ASIA)
Will see an ABNORMALLY high increase due to the importation duties
Currently being imposed. 



For your info:
Since the start of the Federal tax of imported steel (Sept 99), US based mills have added 
A total of $20.00cwt in Nickel Surcharges. This newest mill press release indicates that 
The prices for stainless steel products will continue to climb.

Scrap Pricing (Philadelphia):
Scrap has remained constant, holding around $36.00cwt.

We currently have (43) Stainless Steel items up for auction.
If you have a surplus/overstock item that you wish to sell,
please visit www.buystainlessonline.com and click "Start an Auction"

To place an inquiry in a NON-HTML based format......
simply reply to this email with the necessary info.

TO BE REMOVED:
send a blank email to UNSUBSCRIBE@buystainlessonline.com


------=_NextPart_320623751655725754604743121
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml"
xmlns:o=3D"urn:schemas-microsoft-com:office:office"
xmlns:w=3D"urn:schemas-microsoft-com:office:word"
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1">
<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 9">
<meta name=3DOriginator content=3D"Microsoft Word 9">
<link rel=3DFile-List href=3D"./stainlessonly!_files/filelist.xml">
<link rel=3DEdit-Time-Data href=3D"./stainlessonly!_files/editdata.mso">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title> </title>
<!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>75</w:Zoom>
 </w:WordDocument>
</xml><![endif]-->
<style>
<!--
 /* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:0 0 0 0 0 0 0 0 0 0;
	mso-font-alt:Arial;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-format:other;
	mso-font-pitch:variable;
	mso-font-signature:3 0 0 0 1 0;}
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
h1
	{mso-style-next:Normal;
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	page-break-after:avoid;
	mso-outline-level:1;
	font-size:12.0pt;
	font-family:"Times New Roman";
	color:navy;
	mso-font-kerning:0pt;
	font-weight:normal;
	text-decoration:underline;
	text-underline:single;}
p.MsoBodyText, li.MsoBodyText, div.MsoBodyText
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	color:#339966;}
a:link, span.MsoHyperlink
	{color:#408080;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;
	text-underline:single;}
p
	{margin-right:0in;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"2050"/>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1"/>
 </o:shapelayout></xml><![endif]--><!--[if gte mso 9]><xml>
 <u1:DocumentProperties>
  <u1:Author>Mason</u1:Author>
  <u1:Template>Normal</u1:Template>
  <u1:LastAuthor>KSM</u1:LastAuthor>
  <u1:Revision>8</u1:Revision>
  <u1:TotalTime>30</u1:TotalTime>
  <u1:Created>1999-12-21T18:27:00Z</u1:Created>
  <u1:LastSaved>1999-12-22T17:35:00Z</u1:LastSaved>
  <u1:Pages>2</u1:Pages>
  <u1:Words>89</u1:Words>
  <u1:Characters>511</u1:Characters>
  <u1:Company>Keystone Specialty Metals</u1:Company>
  <u1:Lines>4</u1:Lines>
  <u1:Paragraphs>1</u1:Paragraphs>
  <u1:CharactersWithSpaces>627</u1:CharactersWithSpaces>
  <u1:Version>9.2720</u1:Version>
 </u1:DocumentProperties>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <u2:WordDocument>
  <u2:Zoom>75</u2:Zoom>
 </u2:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <u3:shapedefaults u4:ext=3D"edit" spidmax=3D"1029"/>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <u5:shapelayout u6:ext=3D"edit">
  <u5:idmap u6:ext=3D"edit" data=3D"1"/>
 </u5:shapelayout>
</xml><![endif]-->
</head>

<body lang=3DEN-US link=3D"#408080" vlink=3Dpurple style=3D'tab-interval:.5in'>

<div class=3DSection1>

<p class=3DMsoNormal><u7:wrapblock><u8:shapetype id=3D"_x0000_t75" 
coordsize=3D"21600,21600" u7:spt=3D"75" u7:preferrelative=3D"t" 
path=3D"m@4@5l@4@11@9@11@9@5xe" filled=3D"f" stroked=3D"f"><u8:stroke 
joinstyle=3D"miter"/><u8:formulas><u8:f eqn=3D"if lineDrawn pixelLineWidth 
0"/><u8:f eqn=3D"sum @0 1 0"/><u8:f eqn=3D"sum 0 0 @1"/><u8:f eqn=3D"prod @2 1 
2"/><u8:f eqn=3D"prod @3 21600 pixelWidth"/><u8:f eqn=3D"prod @3 21600 
pixelHeight"/><u8:f eqn=3D"sum @0 0 1"/><u8:f eqn=3D"prod @6 1 2"/><u8:f eqn=3D"prod 
@7 21600 pixelWidth"/><u8:f eqn=3D"sum @8 21600 0"/><u8:f eqn=3D"prod @7 21600 
pixelHeight"/><u8:f eqn=3D"sum @10 21600 0"/></u8:formulas><u8:path 
u7:extrusionok=3D"f" gradientshapeok=3D"t" u7:connecttype=3D"rect"/><u7:lock 
u8:ext=3D"edit" aspectratio=3D"t"/></u8:shapetype><u8:shape id=3D"_x0000_s1028" 
type=3D"#_x0000_t75" style=3D"position:absolute;&#13;&#10;  margin-left:0;
margin-top:0;width:324pt;height:54pt;z-index:1;&#13;&#10;  
mso-position-horizontal-relative:text;
mso-position-vertical-relative:text"><u8:imagedata src=3D".
/joinlist_files/image001.gif" u7:title=3D"logo"/><u9:wrap 
type=3D"topAndBottom"/></u8:shape><img
width=3D463 height=3D81 id=3D"_x0000_i1025"
src=3D"http://buystainlessonline.com/gifs/stonlarge.gif" 
u8:shapes=3D"_x0000_s1028"></u7:wrapblock></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.
0pt'>StainlessOnly!
Is a weekly Stainless Steel related E Magazine<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.
0pt'>Currently
serving over 20,000 users. StainlessOnly! Is brought to 
<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.
0pt'>You
by <span style=3D'color:navy'><a href=3D"http://buystainlessonline.com/"><span
style=3D'color:navy;text-decoration:none;
text-underline:none'>BuyStainlessOnline.
</span></a></span><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'><!
[if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.
0pt'>This
Week in Stainless:<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'><!
[if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><b><span style=3D'font-size:11.0pt;mso-bidi-font-size:12.0pt;

color:#333399'>BuyStainlessOnline gears up for change!
<o:p></o:p></span></b></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>This week and next will mark a transitional period for our site.
The <o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>following STOCK products will become 
available:<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>Rounds, Sheets, Plate, Pipe, Tube, Coil, and Welding Wire.
<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>We have also been receiving a large number of requests for 
<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>Nuts and Bolts (Fasteners). More on that later&#8230;&#8230;
</span><span
style=3D'color:black'> <o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:black'><![if !supportEmptyParas]>&nbsp;
<![endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><b><span style=3D'font-size:11.0pt;mso-bidi-font-size:13.5pt;

font-family:Helvetica'>LME nickel prices hit 4-year high</span></b><br>
LONDON, Feb. 2 -- Nickel tallied prices not seen in more than four</p>

<p><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'>Years in early 
ring
trading on the London Metal Exchange Wednesday.<o:p></o:p></span></p>

<p><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'>A high of $8,900 
per
tonne was reached in the first ring in what analysts<o:p></o:p></span></p>

<p><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'>And dealers said 
was
a result of primarily fund and speculative buying.<o:p></o:p></span></p>

<p><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'>LME nickel
inventories also fell 138 tonnes to 42,324 tonnes, 
reaching<o:p></o:p></span></p>

<p><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'>Their lowest level
since 1991.<span style=3D'color:#003366'><o:p></o:p></span></span></p>

<p><b><span style=3D'font-size:11.0pt;mso-bidi-font-size:13.5pt;
font-family:Helvetica;
color:#003366'>Anaconda Nickel output 'minimal'</span></b><span
style=3D'color:#003366'><br>
</span><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'>SYDNEY,
Australia, Jan. 31 (Reuters) -- Lateritic nickel producer Anaconda Nickel Ltd.

said Monday it expects to reach cash positive operations in the March quarter
after &quot;minimal&quot; production of high-grade nickel and cobalt in the
December quarter. In its December quarterly report, Anaconda said it produced
600 tonnes of London Metal Exchange-grade nickel at Murrin Murrin in Western
Australia in the month of December and 53 tonnes of high-grade cobalt. No
figures were given for October and November. The level of impurities in the
metal had been minimal and quality was improving as operator experience
increased. Anaconda said mechanical and construction material issues had
delayed the commissioning and ramp-up of the project, but production had
confirmed the robustness of the process.<o:p></o:p></span></p>

<p class=3DMsoNormal><b><span style=3D'font-size:11.0pt;mso-bidi-font-size:12.0pt;

color:#003366'>What can you expect as a buyer?<o:p></o:p></span></b></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>For the next six months (At Least) OEM people along with smaller
sized<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>Distributors will experience continually climbing prices and
virtually<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>All stainless items. Those items produced overseas (namely ANGLE
from ASIA)<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>Will see an ABNORMALLY high increase due to the importation 
duties<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>Currently being imposed. <o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:#003366'><![if !supportEmptyParas]>&nbsp;<!
[endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>Scrap Pricing (</span><span style=3D'font-size:9.0pt;
mso-bidi-font-size:
12.0pt;color:navy'>Philadelphia</span><span style=3D'font-size:9.0pt;
mso-bidi-font-size:
12.0pt;color:black'>):<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>Scrap has remained constant, holding around $36.00cwt.
</span><span
style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:navy'><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:navy'><![if !supportEmptyParas]>&nbsp;<!
[endif]><o:p></o:p></span></p>

<h1><span style=3D'text-decoration:none;text-underline:none'><![if !
supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></h1>

<h1><span style=3D'text-decoration:none;text-underline:none'>BuyStainlessOnline.
com
Auction Statistics<o:p></o:p></span></h1>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'><!
[if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></p>

<table border=3D1 cellpadding=3D0 width=3D"19%" style=3D'width:19.82%;
mso-cellspacing:
 1.5pt;mso-padding-alt:0in 0in 0in 0in'>
 <tr>
  <td width=3D"74%" style=3D'width:74.66%;background:#BBBBBB;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal align=3Dcenter 
style=3D'text-align:center'><b>Category</b><span
  style=3D'color:black'><o:p></o:p></span></p>
  </td>
  <td width=3D"22%" style=3D'width:22.38%;background:#BBBBBB;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><b>Items</b><span
  style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"74%" style=3D'width:74.66%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?
angle">Angle</a><span
  style=3D'color:black'><o:p></o:p></span></p>
  </td>
  <td width=3D"22%" style=3D'width:22.38%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>0<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"74%" style=3D'width:74.66%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?
coil">Coil</a><span
  style=3D'color:black'><o:p></o:p></span></p>
  </td>
  <td width=3D"22%" style=3D'width:22.38%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>6<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"74%" style=3D'width:74.66%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?flat">Flat 
Bar</a><span
  style=3D'color:black'><o:p></o:p></span></p>
  </td>
  <td width=3D"22%" style=3D'width:22.38%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>8<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"74%" style=3D'width:74.66%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?
pipe">Pipe</a><span
  style=3D'color:black'><o:p></o:p></span></p>
  </td>
  <td width=3D"22%" style=3D'width:22.38%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>4<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"74%" style=3D'width:74.66%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?
plate">Plate</a><span
  style=3D'color:black'><o:p></o:p></span></p>
  </td>
  <td width=3D"22%" style=3D'width:22.38%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>10<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"74%" style=3D'width:74.66%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?rounds">Round 
Bar</a><span
  style=3D'color:black'><o:p></o:p></span></p>
  </td>
  <td width=3D"22%" style=3D'width:22.38%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>6<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"74%" style=3D'width:74.66%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?
sheet">Sheet</a><span
  style=3D'color:black'><o:p></o:p></span></p>
  </td>
  <td width=3D"22%" style=3D'width:22.38%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>9<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"74%" style=3D'width:74.66%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?
tubing">Tubing</a><span
  style=3D'color:black'><o:p></o:p></span></p>
  </td>
  <td width=3D"22%" style=3D'width:22.38%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>1<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
</table>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'><!
[if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'><!
[if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'><!
[if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'>If
you have a surplus item that you wish to sell,<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.
0pt'>Feel
free to add an item! </span><b><span style=3D'font-size:10.0pt;
mso-bidi-font-size:
12.0pt;color:navy'><a href=3D"http://www.buystainlessonline.com/addtolist.htm"
title=3D"Start an Auction"><span style=3D'color:navy;text-decoration:none;
text-underline:none'>CLICK HERE</span></a></span></b><span 
style=3D'color:navy'><o:p></o:p></span></p>

<p class=3DMsoNormal><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;
color:red'><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><b><span style=3D'color:red'><![if !supportEmptyParas]>&nbsp;
<![endif]><o:p></o:p></span></b></p>

<p class=3DMsoNormal><b><span style=3D'color:navy'><a
href=3D"mailto:remove@buystainlessonline.com?subject=3Dunsubscribe"
title=3D"This will remove you from the E magazine StainlessOnly!"><span
style=3D'color:navy;text-decoration:none;text-underline:none'>UNSUBSCRIBE ME!
</span></a><o:p></o:p></span></b></p>

</div>

</body>

</html>

------=_NextPart_320623751655725754604743121--



From owner-ietf-outbound@ietf.org  Fri Feb  4 09:41:35 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28413
	for <ietf-web-archive@odin.ietf.org>; Fri, 4 Feb 2000 09:41:35 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA26217;
	Fri, 4 Feb 2000 09:39:42 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id JAA28262
	for ietf-outbound.10@ietf.org; Fri, 4 Feb 2000 09:36:33 -0500 (EST)
Received: from mason.buystainlessonline.com (216-59-114-105.usa2.flashcom.net [216.59.114.105])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA26688
	for <ietf@ietf.org>; Fri, 4 Feb 2000 09:00:30 -0500 (EST)
From: auctions@buystainlessonline.com
Message-Id: <cckvhpivfufbrr.tmdtwyltdxueqbfw@mason.buystainlessonline.com>
MIME-Version: 1.0
X-Encoding: MIME
Content-Type: multipart/alternative;
	boundary="----=_NextPart_320623751655725754604743121"
Reply-To: webmaster@buystainlessonline.com
Date: Fri, 04 Feb 2000 08:57:59 -0500
To: ietf@ietf.org
Subject: 4 year high for Nickel on the LME

This is a multi-part message in MIME format.

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

StainlessOnly! is a weekly Stainless Steel related Electronic Magazine. We are
currently reaching:23,677 readers.

BuyStainlessOnline gears up for change!
This week and next will mark a transitional period for our site. The 
following STOCK products will become available:
Rounds, Sheets, Plate, Pipe, Tube, Coil, and Welding Wire.
We have also been receiving a large number of requests for 
Nuts and Bolts (Fasteners). More on that later 

LME nickel prices hit 4-year high
LONDON, Feb. 2 -- Nickel tallied prices not seen in more than four
Years in early ring trading on the London Metal Exchange Wednesday.
A high of $8,900 per tonne was reached in the first ring in what analysts
And dealers said was a result of primarily fund and speculative buying.
LME nickel inventories also fell 138 tonnes to 42,324 tonnes, reaching
Their lowest level since 1991.

Anaconda Nickel output 'minimal'
SYDNEY, Australia, Jan. 31 (Reuters) -- Lateritic nickel producer Anaconda Nickel Ltd. said Monday it expects to reach cash positive operations in the March quarter after "minimal" production of high-grade nickel and cobalt in the December quarter. In its December quarterly report, Anaconda said it produced 600 tonnes of London Metal Exchange-grade nickel at Murrin Murrin in Western Australia in the month of December and 53 tonnes of high-grade cobalt. No figures were given for October and November. The level of impurities in the metal had been minimal and quality was improving as operator experience increased. Anaconda said mechanical and construction material issues had delayed the commissioning and ramp-up of the project, but production had confirmed the robustness of the process.

What can you expect as a buyer?
For the next six months (At Least) OEM people along with smaller sized
Distributors will experience continually climbing prices and virtually
All stainless items. Those items produced overseas (namely ANGLE from ASIA)
Will see an ABNORMALLY high increase due to the importation duties
Currently being imposed. 



For your info:
Since the start of the Federal tax of imported steel (Sept 99), US based mills have added 
A total of $20.00cwt in Nickel Surcharges. This newest mill press release indicates that 
The prices for stainless steel products will continue to climb.

Scrap Pricing (Philadelphia):
Scrap has remained constant, holding around $36.00cwt.

We currently have (43) Stainless Steel items up for auction.
If you have a surplus/overstock item that you wish to sell,
please visit www.buystainlessonline.com and click "Start an Auction"

To place an inquiry in a NON-HTML based format......
simply reply to this email with the necessary info.

TO BE REMOVED:
send a blank email to UNSUBSCRIBE@buystainlessonline.com


------=_NextPart_320623751655725754604743121
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml"
xmlns:o=3D"urn:schemas-microsoft-com:office:office"
xmlns:w=3D"urn:schemas-microsoft-com:office:word"
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1">
<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 9">
<meta name=3DOriginator content=3D"Microsoft Word 9">
<link rel=3DFile-List href=3D"./stainlessonly!_files/filelist.xml">
<link rel=3DEdit-Time-Data href=3D"./stainlessonly!_files/editdata.mso">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title> </title>
<!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>75</w:Zoom>
 </w:WordDocument>
</xml><![endif]-->
<style>
<!--
 /* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:0 0 0 0 0 0 0 0 0 0;
	mso-font-alt:Arial;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-format:other;
	mso-font-pitch:variable;
	mso-font-signature:3 0 0 0 1 0;}
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
h1
	{mso-style-next:Normal;
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	page-break-after:avoid;
	mso-outline-level:1;
	font-size:12.0pt;
	font-family:"Times New Roman";
	color:navy;
	mso-font-kerning:0pt;
	font-weight:normal;
	text-decoration:underline;
	text-underline:single;}
p.MsoBodyText, li.MsoBodyText, div.MsoBodyText
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	color:#339966;}
a:link, span.MsoHyperlink
	{color:#408080;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;
	text-underline:single;}
p
	{margin-right:0in;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"2050"/>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1"/>
 </o:shapelayout></xml><![endif]--><!--[if gte mso 9]><xml>
 <u1:DocumentProperties>
  <u1:Author>Mason</u1:Author>
  <u1:Template>Normal</u1:Template>
  <u1:LastAuthor>KSM</u1:LastAuthor>
  <u1:Revision>8</u1:Revision>
  <u1:TotalTime>30</u1:TotalTime>
  <u1:Created>1999-12-21T18:27:00Z</u1:Created>
  <u1:LastSaved>1999-12-22T17:35:00Z</u1:LastSaved>
  <u1:Pages>2</u1:Pages>
  <u1:Words>89</u1:Words>
  <u1:Characters>511</u1:Characters>
  <u1:Company>Keystone Specialty Metals</u1:Company>
  <u1:Lines>4</u1:Lines>
  <u1:Paragraphs>1</u1:Paragraphs>
  <u1:CharactersWithSpaces>627</u1:CharactersWithSpaces>
  <u1:Version>9.2720</u1:Version>
 </u1:DocumentProperties>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <u2:WordDocument>
  <u2:Zoom>75</u2:Zoom>
 </u2:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <u3:shapedefaults u4:ext=3D"edit" spidmax=3D"1029"/>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <u5:shapelayout u6:ext=3D"edit">
  <u5:idmap u6:ext=3D"edit" data=3D"1"/>
 </u5:shapelayout>
</xml><![endif]-->
</head>

<body lang=3DEN-US link=3D"#408080" vlink=3Dpurple style=3D'tab-interval:.5in'>

<div class=3DSection1>

<p class=3DMsoNormal><u7:wrapblock><u8:shapetype id=3D"_x0000_t75" 
coordsize=3D"21600,21600" u7:spt=3D"75" u7:preferrelative=3D"t" 
path=3D"m@4@5l@4@11@9@11@9@5xe" filled=3D"f" stroked=3D"f"><u8:stroke 
joinstyle=3D"miter"/><u8:formulas><u8:f eqn=3D"if lineDrawn pixelLineWidth 
0"/><u8:f eqn=3D"sum @0 1 0"/><u8:f eqn=3D"sum 0 0 @1"/><u8:f eqn=3D"prod @2 1 
2"/><u8:f eqn=3D"prod @3 21600 pixelWidth"/><u8:f eqn=3D"prod @3 21600 
pixelHeight"/><u8:f eqn=3D"sum @0 0 1"/><u8:f eqn=3D"prod @6 1 2"/><u8:f eqn=3D"prod 
@7 21600 pixelWidth"/><u8:f eqn=3D"sum @8 21600 0"/><u8:f eqn=3D"prod @7 21600 
pixelHeight"/><u8:f eqn=3D"sum @10 21600 0"/></u8:formulas><u8:path 
u7:extrusionok=3D"f" gradientshapeok=3D"t" u7:connecttype=3D"rect"/><u7:lock 
u8:ext=3D"edit" aspectratio=3D"t"/></u8:shapetype><u8:shape id=3D"_x0000_s1028" 
type=3D"#_x0000_t75" style=3D"position:absolute;&#13;&#10;  margin-left:0;
margin-top:0;width:324pt;height:54pt;z-index:1;&#13;&#10;  
mso-position-horizontal-relative:text;
mso-position-vertical-relative:text"><u8:imagedata src=3D".
/joinlist_files/image001.gif" u7:title=3D"logo"/><u9:wrap 
type=3D"topAndBottom"/></u8:shape><img
width=3D463 height=3D81 id=3D"_x0000_i1025"
src=3D"http://buystainlessonline.com/gifs/stonlarge.gif" 
u8:shapes=3D"_x0000_s1028"></u7:wrapblock></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.
0pt'>StainlessOnly!
Is a weekly Stainless Steel related E Magazine<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.
0pt'>Currently
serving over 20,000 users. StainlessOnly! Is brought to 
<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.
0pt'>You
by <span style=3D'color:navy'><a href=3D"http://buystainlessonline.com/"><span
style=3D'color:navy;text-decoration:none;
text-underline:none'>BuyStainlessOnline.
</span></a></span><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'><!
[if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.
0pt'>This
Week in Stainless:<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'><!
[if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><b><span style=3D'font-size:11.0pt;mso-bidi-font-size:12.0pt;

color:#333399'>BuyStainlessOnline gears up for change!
<o:p></o:p></span></b></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>This week and next will mark a transitional period for our site.
The <o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>following STOCK products will become 
available:<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>Rounds, Sheets, Plate, Pipe, Tube, Coil, and Welding Wire.
<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>We have also been receiving a large number of requests for 
<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>Nuts and Bolts (Fasteners). More on that later&#8230;&#8230;
</span><span
style=3D'color:black'> <o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:black'><![if !supportEmptyParas]>&nbsp;
<![endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><b><span style=3D'font-size:11.0pt;mso-bidi-font-size:13.5pt;

font-family:Helvetica'>LME nickel prices hit 4-year high</span></b><br>
LONDON, Feb. 2 -- Nickel tallied prices not seen in more than four</p>

<p><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'>Years in early 
ring
trading on the London Metal Exchange Wednesday.<o:p></o:p></span></p>

<p><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'>A high of $8,900 
per
tonne was reached in the first ring in what analysts<o:p></o:p></span></p>

<p><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'>And dealers said 
was
a result of primarily fund and speculative buying.<o:p></o:p></span></p>

<p><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'>LME nickel
inventories also fell 138 tonnes to 42,324 tonnes, 
reaching<o:p></o:p></span></p>

<p><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'>Their lowest level
since 1991.<span style=3D'color:#003366'><o:p></o:p></span></span></p>

<p><b><span style=3D'font-size:11.0pt;mso-bidi-font-size:13.5pt;
font-family:Helvetica;
color:#003366'>Anaconda Nickel output 'minimal'</span></b><span
style=3D'color:#003366'><br>
</span><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'>SYDNEY,
Australia, Jan. 31 (Reuters) -- Lateritic nickel producer Anaconda Nickel Ltd.

said Monday it expects to reach cash positive operations in the March quarter
after &quot;minimal&quot; production of high-grade nickel and cobalt in the
December quarter. In its December quarterly report, Anaconda said it produced
600 tonnes of London Metal Exchange-grade nickel at Murrin Murrin in Western
Australia in the month of December and 53 tonnes of high-grade cobalt. No
figures were given for October and November. The level of impurities in the
metal had been minimal and quality was improving as operator experience
increased. Anaconda said mechanical and construction material issues had
delayed the commissioning and ramp-up of the project, but production had
confirmed the robustness of the process.<o:p></o:p></span></p>

<p class=3DMsoNormal><b><span style=3D'font-size:11.0pt;mso-bidi-font-size:12.0pt;

color:#003366'>What can you expect as a buyer?<o:p></o:p></span></b></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>For the next six months (At Least) OEM people along with smaller
sized<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>Distributors will experience continually climbing prices and
virtually<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>All stainless items. Those items produced overseas (namely ANGLE
from ASIA)<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>Will see an ABNORMALLY high increase due to the importation 
duties<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>Currently being imposed. <o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:#003366'><![if !supportEmptyParas]>&nbsp;<!
[endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>Scrap Pricing (</span><span style=3D'font-size:9.0pt;
mso-bidi-font-size:
12.0pt;color:navy'>Philadelphia</span><span style=3D'font-size:9.0pt;
mso-bidi-font-size:
12.0pt;color:black'>):<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>Scrap has remained constant, holding around $36.00cwt.
</span><span
style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:navy'><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:navy'><![if !supportEmptyParas]>&nbsp;<!
[endif]><o:p></o:p></span></p>

<h1><span style=3D'text-decoration:none;text-underline:none'><![if !
supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></h1>

<h1><span style=3D'text-decoration:none;text-underline:none'>BuyStainlessOnline.
com
Auction Statistics<o:p></o:p></span></h1>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'><!
[if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></p>

<table border=3D1 cellpadding=3D0 width=3D"19%" style=3D'width:19.82%;
mso-cellspacing:
 1.5pt;mso-padding-alt:0in 0in 0in 0in'>
 <tr>
  <td width=3D"74%" style=3D'width:74.66%;background:#BBBBBB;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal align=3Dcenter 
style=3D'text-align:center'><b>Category</b><span
  style=3D'color:black'><o:p></o:p></span></p>
  </td>
  <td width=3D"22%" style=3D'width:22.38%;background:#BBBBBB;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><b>Items</b><span
  style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"74%" style=3D'width:74.66%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?
angle">Angle</a><span
  style=3D'color:black'><o:p></o:p></span></p>
  </td>
  <td width=3D"22%" style=3D'width:22.38%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>0<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"74%" style=3D'width:74.66%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?
coil">Coil</a><span
  style=3D'color:black'><o:p></o:p></span></p>
  </td>
  <td width=3D"22%" style=3D'width:22.38%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>6<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"74%" style=3D'width:74.66%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?flat">Flat 
Bar</a><span
  style=3D'color:black'><o:p></o:p></span></p>
  </td>
  <td width=3D"22%" style=3D'width:22.38%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>8<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"74%" style=3D'width:74.66%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?
pipe">Pipe</a><span
  style=3D'color:black'><o:p></o:p></span></p>
  </td>
  <td width=3D"22%" style=3D'width:22.38%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>4<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"74%" style=3D'width:74.66%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?
plate">Plate</a><span
  style=3D'color:black'><o:p></o:p></span></p>
  </td>
  <td width=3D"22%" style=3D'width:22.38%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>10<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"74%" style=3D'width:74.66%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?rounds">Round 
Bar</a><span
  style=3D'color:black'><o:p></o:p></span></p>
  </td>
  <td width=3D"22%" style=3D'width:22.38%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>6<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"74%" style=3D'width:74.66%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?
sheet">Sheet</a><span
  style=3D'color:black'><o:p></o:p></span></p>
  </td>
  <td width=3D"22%" style=3D'width:22.38%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>9<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"74%" style=3D'width:74.66%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?
tubing">Tubing</a><span
  style=3D'color:black'><o:p></o:p></span></p>
  </td>
  <td width=3D"22%" style=3D'width:22.38%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>1<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
</table>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'><!
[if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'><!
[if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'><!
[if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'>If
you have a surplus item that you wish to sell,<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.
0pt'>Feel
free to add an item! </span><b><span style=3D'font-size:10.0pt;
mso-bidi-font-size:
12.0pt;color:navy'><a href=3D"http://www.buystainlessonline.com/addtolist.htm"
title=3D"Start an Auction"><span style=3D'color:navy;text-decoration:none;
text-underline:none'>CLICK HERE</span></a></span></b><span 
style=3D'color:navy'><o:p></o:p></span></p>

<p class=3DMsoNormal><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;
color:red'><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><b><span style=3D'color:red'><![if !supportEmptyParas]>&nbsp;
<![endif]><o:p></o:p></span></b></p>

<p class=3DMsoNormal><b><span style=3D'color:navy'><a
href=3D"mailto:remove@buystainlessonline.com?subject=3Dunsubscribe"
title=3D"This will remove you from the E magazine StainlessOnly!"><span
style=3D'color:navy;text-decoration:none;text-underline:none'>UNSUBSCRIBE ME!
</span></a><o:p></o:p></span></b></p>

</div>

</body>

</html>

------=_NextPart_320623751655725754604743121--



From owner-ietf-outbound  Fri Feb  4 09:34:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA27993
	for ietf-outbound.10@ietf.org; Fri, 4 Feb 2000 09:30:09 -0500 (EST)
Received: from mason.buystainlessonline.com (216-59-114-105.usa2.flashcom.net [216.59.114.105])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA26688
	for <ietf@ietf.org>; Fri, 4 Feb 2000 09:00:30 -0500 (EST)
From: auctions@buystainlessonline.com
Message-Id: <cckvhpivfufbrr.tmdtwyltdxueqbfw@mason.buystainlessonline.com>
MIME-Version: 1.0
X-Encoding: MIME
Content-Type: multipart/alternative;
	boundary="----=_NextPart_320623751655725754604743121"
Reply-To: webmaster@buystainlessonline.com
Date: Fri, 04 Feb 2000 08:57:59 -0500
To: ietf@ietf.org
Subject: 4 year high for Nickel on the LME

This is a multi-part message in MIME format.

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

StainlessOnly! is a weekly Stainless Steel related Electronic Magazine. We are
currently reaching:23,677 readers.

BuyStainlessOnline gears up for change!
This week and next will mark a transitional period for our site. The 
following STOCK products will become available:
Rounds, Sheets, Plate, Pipe, Tube, Coil, and Welding Wire.
We have also been receiving a large number of requests for 
Nuts and Bolts (Fasteners). More on that later 

LME nickel prices hit 4-year high
LONDON, Feb. 2 -- Nickel tallied prices not seen in more than four
Years in early ring trading on the London Metal Exchange Wednesday.
A high of $8,900 per tonne was reached in the first ring in what analysts
And dealers said was a result of primarily fund and speculative buying.
LME nickel inventories also fell 138 tonnes to 42,324 tonnes, reaching
Their lowest level since 1991.

Anaconda Nickel output 'minimal'
SYDNEY, Australia, Jan. 31 (Reuters) -- Lateritic nickel producer Anaconda Nickel Ltd. said Monday it expects to reach cash positive operations in the March quarter after "minimal" production of high-grade nickel and cobalt in the December quarter. In its December quarterly report, Anaconda said it produced 600 tonnes of London Metal Exchange-grade nickel at Murrin Murrin in Western Australia in the month of December and 53 tonnes of high-grade cobalt. No figures were given for October and November. The level of impurities in the metal had been minimal and quality was improving as operator experience increased. Anaconda said mechanical and construction material issues had delayed the commissioning and ramp-up of the project, but production had confirmed the robustness of the process.

What can you expect as a buyer?
For the next six months (At Least) OEM people along with smaller sized
Distributors will experience continually climbing prices and virtually
All stainless items. Those items produced overseas (namely ANGLE from ASIA)
Will see an ABNORMALLY high increase due to the importation duties
Currently being imposed. 



For your info:
Since the start of the Federal tax of imported steel (Sept 99), US based mills have added 
A total of $20.00cwt in Nickel Surcharges. This newest mill press release indicates that 
The prices for stainless steel products will continue to climb.

Scrap Pricing (Philadelphia):
Scrap has remained constant, holding around $36.00cwt.

We currently have (43) Stainless Steel items up for auction.
If you have a surplus/overstock item that you wish to sell,
please visit www.buystainlessonline.com and click "Start an Auction"

To place an inquiry in a NON-HTML based format......
simply reply to this email with the necessary info.

TO BE REMOVED:
send a blank email to UNSUBSCRIBE@buystainlessonline.com


------=_NextPart_320623751655725754604743121
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml"
xmlns:o=3D"urn:schemas-microsoft-com:office:office"
xmlns:w=3D"urn:schemas-microsoft-com:office:word"
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1">
<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 9">
<meta name=3DOriginator content=3D"Microsoft Word 9">
<link rel=3DFile-List href=3D"./stainlessonly!_files/filelist.xml">
<link rel=3DEdit-Time-Data href=3D"./stainlessonly!_files/editdata.mso">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title> </title>
<!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>75</w:Zoom>
 </w:WordDocument>
</xml><![endif]-->
<style>
<!--
 /* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:0 0 0 0 0 0 0 0 0 0;
	mso-font-alt:Arial;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-format:other;
	mso-font-pitch:variable;
	mso-font-signature:3 0 0 0 1 0;}
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
h1
	{mso-style-next:Normal;
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	page-break-after:avoid;
	mso-outline-level:1;
	font-size:12.0pt;
	font-family:"Times New Roman";
	color:navy;
	mso-font-kerning:0pt;
	font-weight:normal;
	text-decoration:underline;
	text-underline:single;}
p.MsoBodyText, li.MsoBodyText, div.MsoBodyText
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	color:#339966;}
a:link, span.MsoHyperlink
	{color:#408080;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;
	text-underline:single;}
p
	{margin-right:0in;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"2050"/>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1"/>
 </o:shapelayout></xml><![endif]--><!--[if gte mso 9]><xml>
 <u1:DocumentProperties>
  <u1:Author>Mason</u1:Author>
  <u1:Template>Normal</u1:Template>
  <u1:LastAuthor>KSM</u1:LastAuthor>
  <u1:Revision>8</u1:Revision>
  <u1:TotalTime>30</u1:TotalTime>
  <u1:Created>1999-12-21T18:27:00Z</u1:Created>
  <u1:LastSaved>1999-12-22T17:35:00Z</u1:LastSaved>
  <u1:Pages>2</u1:Pages>
  <u1:Words>89</u1:Words>
  <u1:Characters>511</u1:Characters>
  <u1:Company>Keystone Specialty Metals</u1:Company>
  <u1:Lines>4</u1:Lines>
  <u1:Paragraphs>1</u1:Paragraphs>
  <u1:CharactersWithSpaces>627</u1:CharactersWithSpaces>
  <u1:Version>9.2720</u1:Version>
 </u1:DocumentProperties>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <u2:WordDocument>
  <u2:Zoom>75</u2:Zoom>
 </u2:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <u3:shapedefaults u4:ext=3D"edit" spidmax=3D"1029"/>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <u5:shapelayout u6:ext=3D"edit">
  <u5:idmap u6:ext=3D"edit" data=3D"1"/>
 </u5:shapelayout>
</xml><![endif]-->
</head>

<body lang=3DEN-US link=3D"#408080" vlink=3Dpurple style=3D'tab-interval:.5in'>

<div class=3DSection1>

<p class=3DMsoNormal><u7:wrapblock><u8:shapetype id=3D"_x0000_t75" 
coordsize=3D"21600,21600" u7:spt=3D"75" u7:preferrelative=3D"t" 
path=3D"m@4@5l@4@11@9@11@9@5xe" filled=3D"f" stroked=3D"f"><u8:stroke 
joinstyle=3D"miter"/><u8:formulas><u8:f eqn=3D"if lineDrawn pixelLineWidth 
0"/><u8:f eqn=3D"sum @0 1 0"/><u8:f eqn=3D"sum 0 0 @1"/><u8:f eqn=3D"prod @2 1 
2"/><u8:f eqn=3D"prod @3 21600 pixelWidth"/><u8:f eqn=3D"prod @3 21600 
pixelHeight"/><u8:f eqn=3D"sum @0 0 1"/><u8:f eqn=3D"prod @6 1 2"/><u8:f eqn=3D"prod 
@7 21600 pixelWidth"/><u8:f eqn=3D"sum @8 21600 0"/><u8:f eqn=3D"prod @7 21600 
pixelHeight"/><u8:f eqn=3D"sum @10 21600 0"/></u8:formulas><u8:path 
u7:extrusionok=3D"f" gradientshapeok=3D"t" u7:connecttype=3D"rect"/><u7:lock 
u8:ext=3D"edit" aspectratio=3D"t"/></u8:shapetype><u8:shape id=3D"_x0000_s1028" 
type=3D"#_x0000_t75" style=3D"position:absolute;&#13;&#10;  margin-left:0;
margin-top:0;width:324pt;height:54pt;z-index:1;&#13;&#10;  
mso-position-horizontal-relative:text;
mso-position-vertical-relative:text"><u8:imagedata src=3D".
/joinlist_files/image001.gif" u7:title=3D"logo"/><u9:wrap 
type=3D"topAndBottom"/></u8:shape><img
width=3D463 height=3D81 id=3D"_x0000_i1025"
src=3D"http://buystainlessonline.com/gifs/stonlarge.gif" 
u8:shapes=3D"_x0000_s1028"></u7:wrapblock></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.
0pt'>StainlessOnly!
Is a weekly Stainless Steel related E Magazine<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.
0pt'>Currently
serving over 20,000 users. StainlessOnly! Is brought to 
<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.
0pt'>You
by <span style=3D'color:navy'><a href=3D"http://buystainlessonline.com/"><span
style=3D'color:navy;text-decoration:none;
text-underline:none'>BuyStainlessOnline.
</span></a></span><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'><!
[if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.
0pt'>This
Week in Stainless:<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'><!
[if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><b><span style=3D'font-size:11.0pt;mso-bidi-font-size:12.0pt;

color:#333399'>BuyStainlessOnline gears up for change!
<o:p></o:p></span></b></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>This week and next will mark a transitional period for our site.
The <o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>following STOCK products will become 
available:<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>Rounds, Sheets, Plate, Pipe, Tube, Coil, and Welding Wire.
<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>We have also been receiving a large number of requests for 
<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>Nuts and Bolts (Fasteners). More on that later&#8230;&#8230;
</span><span
style=3D'color:black'> <o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:black'><![if !supportEmptyParas]>&nbsp;
<![endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><b><span style=3D'font-size:11.0pt;mso-bidi-font-size:13.5pt;

font-family:Helvetica'>LME nickel prices hit 4-year high</span></b><br>
LONDON, Feb. 2 -- Nickel tallied prices not seen in more than four</p>

<p><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'>Years in early 
ring
trading on the London Metal Exchange Wednesday.<o:p></o:p></span></p>

<p><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'>A high of $8,900 
per
tonne was reached in the first ring in what analysts<o:p></o:p></span></p>

<p><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'>And dealers said 
was
a result of primarily fund and speculative buying.<o:p></o:p></span></p>

<p><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'>LME nickel
inventories also fell 138 tonnes to 42,324 tonnes, 
reaching<o:p></o:p></span></p>

<p><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'>Their lowest level
since 1991.<span style=3D'color:#003366'><o:p></o:p></span></span></p>

<p><b><span style=3D'font-size:11.0pt;mso-bidi-font-size:13.5pt;
font-family:Helvetica;
color:#003366'>Anaconda Nickel output 'minimal'</span></b><span
style=3D'color:#003366'><br>
</span><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'>SYDNEY,
Australia, Jan. 31 (Reuters) -- Lateritic nickel producer Anaconda Nickel Ltd.

said Monday it expects to reach cash positive operations in the March quarter
after &quot;minimal&quot; production of high-grade nickel and cobalt in the
December quarter. In its December quarterly report, Anaconda said it produced
600 tonnes of London Metal Exchange-grade nickel at Murrin Murrin in Western
Australia in the month of December and 53 tonnes of high-grade cobalt. No
figures were given for October and November. The level of impurities in the
metal had been minimal and quality was improving as operator experience
increased. Anaconda said mechanical and construction material issues had
delayed the commissioning and ramp-up of the project, but production had
confirmed the robustness of the process.<o:p></o:p></span></p>

<p class=3DMsoNormal><b><span style=3D'font-size:11.0pt;mso-bidi-font-size:12.0pt;

color:#003366'>What can you expect as a buyer?<o:p></o:p></span></b></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>For the next six months (At Least) OEM people along with smaller
sized<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>Distributors will experience continually climbing prices and
virtually<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>All stainless items. Those items produced overseas (namely ANGLE
from ASIA)<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>Will see an ABNORMALLY high increase due to the importation 
duties<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>Currently being imposed. <o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:#003366'><![if !supportEmptyParas]>&nbsp;<!
[endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>Scrap Pricing (</span><span style=3D'font-size:9.0pt;
mso-bidi-font-size:
12.0pt;color:navy'>Philadelphia</span><span style=3D'font-size:9.0pt;
mso-bidi-font-size:
12.0pt;color:black'>):<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>Scrap has remained constant, holding around $36.00cwt.
</span><span
style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:navy'><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:navy'><![if !supportEmptyParas]>&nbsp;<!
[endif]><o:p></o:p></span></p>

<h1><span style=3D'text-decoration:none;text-underline:none'><![if !
supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></h1>

<h1><span style=3D'text-decoration:none;text-underline:none'>BuyStainlessOnline.
com
Auction Statistics<o:p></o:p></span></h1>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'><!
[if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></p>

<table border=3D1 cellpadding=3D0 width=3D"19%" style=3D'width:19.82%;
mso-cellspacing:
 1.5pt;mso-padding-alt:0in 0in 0in 0in'>
 <tr>
  <td width=3D"74%" style=3D'width:74.66%;background:#BBBBBB;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal align=3Dcenter 
style=3D'text-align:center'><b>Category</b><span
  style=3D'color:black'><o:p></o:p></span></p>
  </td>
  <td width=3D"22%" style=3D'width:22.38%;background:#BBBBBB;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><b>Items</b><span
  style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"74%" style=3D'width:74.66%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?
angle">Angle</a><span
  style=3D'color:black'><o:p></o:p></span></p>
  </td>
  <td width=3D"22%" style=3D'width:22.38%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>0<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"74%" style=3D'width:74.66%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?
coil">Coil</a><span
  style=3D'color:black'><o:p></o:p></span></p>
  </td>
  <td width=3D"22%" style=3D'width:22.38%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>6<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"74%" style=3D'width:74.66%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?flat">Flat 
Bar</a><span
  style=3D'color:black'><o:p></o:p></span></p>
  </td>
  <td width=3D"22%" style=3D'width:22.38%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>8<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"74%" style=3D'width:74.66%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?
pipe">Pipe</a><span
  style=3D'color:black'><o:p></o:p></span></p>
  </td>
  <td width=3D"22%" style=3D'width:22.38%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>4<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"74%" style=3D'width:74.66%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?
plate">Plate</a><span
  style=3D'color:black'><o:p></o:p></span></p>
  </td>
  <td width=3D"22%" style=3D'width:22.38%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>10<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"74%" style=3D'width:74.66%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?rounds">Round 
Bar</a><span
  style=3D'color:black'><o:p></o:p></span></p>
  </td>
  <td width=3D"22%" style=3D'width:22.38%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>6<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"74%" style=3D'width:74.66%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?
sheet">Sheet</a><span
  style=3D'color:black'><o:p></o:p></span></p>
  </td>
  <td width=3D"22%" style=3D'width:22.38%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>9<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"74%" style=3D'width:74.66%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?
tubing">Tubing</a><span
  style=3D'color:black'><o:p></o:p></span></p>
  </td>
  <td width=3D"22%" style=3D'width:22.38%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>1<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
</table>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'><!
[if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'><!
[if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'><!
[if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'>If
you have a surplus item that you wish to sell,<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.
0pt'>Feel
free to add an item! </span><b><span style=3D'font-size:10.0pt;
mso-bidi-font-size:
12.0pt;color:navy'><a href=3D"http://www.buystainlessonline.com/addtolist.htm"
title=3D"Start an Auction"><span style=3D'color:navy;text-decoration:none;
text-underline:none'>CLICK HERE</span></a></span></b><span 
style=3D'color:navy'><o:p></o:p></span></p>

<p class=3DMsoNormal><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;
color:red'><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><b><span style=3D'color:red'><![if !supportEmptyParas]>&nbsp;
<![endif]><o:p></o:p></span></b></p>

<p class=3DMsoNormal><b><span style=3D'color:navy'><a
href=3D"mailto:remove@buystainlessonline.com?subject=3Dunsubscribe"
title=3D"This will remove you from the E magazine StainlessOnly!"><span
style=3D'color:navy;text-decoration:none;text-underline:none'>UNSUBSCRIBE ME!
</span></a><o:p></o:p></span></b></p>

</div>

</body>

</html>

------=_NextPart_320623751655725754604743121--



From owner-ietf-outbound@ietf.org  Fri Feb  4 09:41:56 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28461
	for <ietf-web-archive@odin.ietf.org>; Fri, 4 Feb 2000 09:41:56 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA26247;
	Fri, 4 Feb 2000 09:40:28 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id JAA27993
	for ietf-outbound.10@ietf.org; Fri, 4 Feb 2000 09:30:09 -0500 (EST)
Received: from mason.buystainlessonline.com (216-59-114-105.usa2.flashcom.net [216.59.114.105])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA26688
	for <ietf@ietf.org>; Fri, 4 Feb 2000 09:00:30 -0500 (EST)
From: auctions@buystainlessonline.com
Message-Id: <cckvhpivfufbrr.tmdtwyltdxueqbfw@mason.buystainlessonline.com>
MIME-Version: 1.0
X-Encoding: MIME
Content-Type: multipart/alternative;
	boundary="----=_NextPart_320623751655725754604743121"
Reply-To: webmaster@buystainlessonline.com
Date: Fri, 04 Feb 2000 08:57:59 -0500
To: ietf@ietf.org
Subject: 4 year high for Nickel on the LME

This is a multi-part message in MIME format.

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

StainlessOnly! is a weekly Stainless Steel related Electronic Magazine. We are
currently reaching:23,677 readers.

BuyStainlessOnline gears up for change!
This week and next will mark a transitional period for our site. The 
following STOCK products will become available:
Rounds, Sheets, Plate, Pipe, Tube, Coil, and Welding Wire.
We have also been receiving a large number of requests for 
Nuts and Bolts (Fasteners). More on that later 

LME nickel prices hit 4-year high
LONDON, Feb. 2 -- Nickel tallied prices not seen in more than four
Years in early ring trading on the London Metal Exchange Wednesday.
A high of $8,900 per tonne was reached in the first ring in what analysts
And dealers said was a result of primarily fund and speculative buying.
LME nickel inventories also fell 138 tonnes to 42,324 tonnes, reaching
Their lowest level since 1991.

Anaconda Nickel output 'minimal'
SYDNEY, Australia, Jan. 31 (Reuters) -- Lateritic nickel producer Anaconda Nickel Ltd. said Monday it expects to reach cash positive operations in the March quarter after "minimal" production of high-grade nickel and cobalt in the December quarter. In its December quarterly report, Anaconda said it produced 600 tonnes of London Metal Exchange-grade nickel at Murrin Murrin in Western Australia in the month of December and 53 tonnes of high-grade cobalt. No figures were given for October and November. The level of impurities in the metal had been minimal and quality was improving as operator experience increased. Anaconda said mechanical and construction material issues had delayed the commissioning and ramp-up of the project, but production had confirmed the robustness of the process.

What can you expect as a buyer?
For the next six months (At Least) OEM people along with smaller sized
Distributors will experience continually climbing prices and virtually
All stainless items. Those items produced overseas (namely ANGLE from ASIA)
Will see an ABNORMALLY high increase due to the importation duties
Currently being imposed. 



For your info:
Since the start of the Federal tax of imported steel (Sept 99), US based mills have added 
A total of $20.00cwt in Nickel Surcharges. This newest mill press release indicates that 
The prices for stainless steel products will continue to climb.

Scrap Pricing (Philadelphia):
Scrap has remained constant, holding around $36.00cwt.

We currently have (43) Stainless Steel items up for auction.
If you have a surplus/overstock item that you wish to sell,
please visit www.buystainlessonline.com and click "Start an Auction"

To place an inquiry in a NON-HTML based format......
simply reply to this email with the necessary info.

TO BE REMOVED:
send a blank email to UNSUBSCRIBE@buystainlessonline.com


------=_NextPart_320623751655725754604743121
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml"
xmlns:o=3D"urn:schemas-microsoft-com:office:office"
xmlns:w=3D"urn:schemas-microsoft-com:office:word"
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1">
<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 9">
<meta name=3DOriginator content=3D"Microsoft Word 9">
<link rel=3DFile-List href=3D"./stainlessonly!_files/filelist.xml">
<link rel=3DEdit-Time-Data href=3D"./stainlessonly!_files/editdata.mso">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title> </title>
<!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:Zoom>75</w:Zoom>
 </w:WordDocument>
</xml><![endif]-->
<style>
<!--
 /* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:0 0 0 0 0 0 0 0 0 0;
	mso-font-alt:Arial;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-format:other;
	mso-font-pitch:variable;
	mso-font-signature:3 0 0 0 1 0;}
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
h1
	{mso-style-next:Normal;
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	page-break-after:avoid;
	mso-outline-level:1;
	font-size:12.0pt;
	font-family:"Times New Roman";
	color:navy;
	mso-font-kerning:0pt;
	font-weight:normal;
	text-decoration:underline;
	text-underline:single;}
p.MsoBodyText, li.MsoBodyText, div.MsoBodyText
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";
	color:#339966;}
a:link, span.MsoHyperlink
	{color:#408080;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;
	text-underline:single;}
p
	{margin-right:0in;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"2050"/>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1"/>
 </o:shapelayout></xml><![endif]--><!--[if gte mso 9]><xml>
 <u1:DocumentProperties>
  <u1:Author>Mason</u1:Author>
  <u1:Template>Normal</u1:Template>
  <u1:LastAuthor>KSM</u1:LastAuthor>
  <u1:Revision>8</u1:Revision>
  <u1:TotalTime>30</u1:TotalTime>
  <u1:Created>1999-12-21T18:27:00Z</u1:Created>
  <u1:LastSaved>1999-12-22T17:35:00Z</u1:LastSaved>
  <u1:Pages>2</u1:Pages>
  <u1:Words>89</u1:Words>
  <u1:Characters>511</u1:Characters>
  <u1:Company>Keystone Specialty Metals</u1:Company>
  <u1:Lines>4</u1:Lines>
  <u1:Paragraphs>1</u1:Paragraphs>
  <u1:CharactersWithSpaces>627</u1:CharactersWithSpaces>
  <u1:Version>9.2720</u1:Version>
 </u1:DocumentProperties>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <u2:WordDocument>
  <u2:Zoom>75</u2:Zoom>
 </u2:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <u3:shapedefaults u4:ext=3D"edit" spidmax=3D"1029"/>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <u5:shapelayout u6:ext=3D"edit">
  <u5:idmap u6:ext=3D"edit" data=3D"1"/>
 </u5:shapelayout>
</xml><![endif]-->
</head>

<body lang=3DEN-US link=3D"#408080" vlink=3Dpurple style=3D'tab-interval:.5in'>

<div class=3DSection1>

<p class=3DMsoNormal><u7:wrapblock><u8:shapetype id=3D"_x0000_t75" 
coordsize=3D"21600,21600" u7:spt=3D"75" u7:preferrelative=3D"t" 
path=3D"m@4@5l@4@11@9@11@9@5xe" filled=3D"f" stroked=3D"f"><u8:stroke 
joinstyle=3D"miter"/><u8:formulas><u8:f eqn=3D"if lineDrawn pixelLineWidth 
0"/><u8:f eqn=3D"sum @0 1 0"/><u8:f eqn=3D"sum 0 0 @1"/><u8:f eqn=3D"prod @2 1 
2"/><u8:f eqn=3D"prod @3 21600 pixelWidth"/><u8:f eqn=3D"prod @3 21600 
pixelHeight"/><u8:f eqn=3D"sum @0 0 1"/><u8:f eqn=3D"prod @6 1 2"/><u8:f eqn=3D"prod 
@7 21600 pixelWidth"/><u8:f eqn=3D"sum @8 21600 0"/><u8:f eqn=3D"prod @7 21600 
pixelHeight"/><u8:f eqn=3D"sum @10 21600 0"/></u8:formulas><u8:path 
u7:extrusionok=3D"f" gradientshapeok=3D"t" u7:connecttype=3D"rect"/><u7:lock 
u8:ext=3D"edit" aspectratio=3D"t"/></u8:shapetype><u8:shape id=3D"_x0000_s1028" 
type=3D"#_x0000_t75" style=3D"position:absolute;&#13;&#10;  margin-left:0;
margin-top:0;width:324pt;height:54pt;z-index:1;&#13;&#10;  
mso-position-horizontal-relative:text;
mso-position-vertical-relative:text"><u8:imagedata src=3D".
/joinlist_files/image001.gif" u7:title=3D"logo"/><u9:wrap 
type=3D"topAndBottom"/></u8:shape><img
width=3D463 height=3D81 id=3D"_x0000_i1025"
src=3D"http://buystainlessonline.com/gifs/stonlarge.gif" 
u8:shapes=3D"_x0000_s1028"></u7:wrapblock></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.
0pt'>StainlessOnly!
Is a weekly Stainless Steel related E Magazine<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.
0pt'>Currently
serving over 20,000 users. StainlessOnly! Is brought to 
<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.
0pt'>You
by <span style=3D'color:navy'><a href=3D"http://buystainlessonline.com/"><span
style=3D'color:navy;text-decoration:none;
text-underline:none'>BuyStainlessOnline.
</span></a></span><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'><!
[if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.
0pt'>This
Week in Stainless:<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'><!
[if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><b><span style=3D'font-size:11.0pt;mso-bidi-font-size:12.0pt;

color:#333399'>BuyStainlessOnline gears up for change!
<o:p></o:p></span></b></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>This week and next will mark a transitional period for our site.
The <o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>following STOCK products will become 
available:<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>Rounds, Sheets, Plate, Pipe, Tube, Coil, and Welding Wire.
<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>We have also been receiving a large number of requests for 
<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>Nuts and Bolts (Fasteners). More on that later&#8230;&#8230;
</span><span
style=3D'color:black'> <o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:black'><![if !supportEmptyParas]>&nbsp;
<![endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><b><span style=3D'font-size:11.0pt;mso-bidi-font-size:13.5pt;

font-family:Helvetica'>LME nickel prices hit 4-year high</span></b><br>
LONDON, Feb. 2 -- Nickel tallied prices not seen in more than four</p>

<p><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'>Years in early 
ring
trading on the London Metal Exchange Wednesday.<o:p></o:p></span></p>

<p><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'>A high of $8,900 
per
tonne was reached in the first ring in what analysts<o:p></o:p></span></p>

<p><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'>And dealers said 
was
a result of primarily fund and speculative buying.<o:p></o:p></span></p>

<p><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'>LME nickel
inventories also fell 138 tonnes to 42,324 tonnes, 
reaching<o:p></o:p></span></p>

<p><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'>Their lowest level
since 1991.<span style=3D'color:#003366'><o:p></o:p></span></span></p>

<p><b><span style=3D'font-size:11.0pt;mso-bidi-font-size:13.5pt;
font-family:Helvetica;
color:#003366'>Anaconda Nickel output 'minimal'</span></b><span
style=3D'color:#003366'><br>
</span><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'>SYDNEY,
Australia, Jan. 31 (Reuters) -- Lateritic nickel producer Anaconda Nickel Ltd.

said Monday it expects to reach cash positive operations in the March quarter
after &quot;minimal&quot; production of high-grade nickel and cobalt in the
December quarter. In its December quarterly report, Anaconda said it produced
600 tonnes of London Metal Exchange-grade nickel at Murrin Murrin in Western
Australia in the month of December and 53 tonnes of high-grade cobalt. No
figures were given for October and November. The level of impurities in the
metal had been minimal and quality was improving as operator experience
increased. Anaconda said mechanical and construction material issues had
delayed the commissioning and ramp-up of the project, but production had
confirmed the robustness of the process.<o:p></o:p></span></p>

<p class=3DMsoNormal><b><span style=3D'font-size:11.0pt;mso-bidi-font-size:12.0pt;

color:#003366'>What can you expect as a buyer?<o:p></o:p></span></b></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>For the next six months (At Least) OEM people along with smaller
sized<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>Distributors will experience continually climbing prices and
virtually<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>All stainless items. Those items produced overseas (namely ANGLE
from ASIA)<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>Will see an ABNORMALLY high increase due to the importation 
duties<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>Currently being imposed. <o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:#003366'><![if !supportEmptyParas]>&nbsp;<!
[endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>Scrap Pricing (</span><span style=3D'font-size:9.0pt;
mso-bidi-font-size:
12.0pt;color:navy'>Philadelphia</span><span style=3D'font-size:9.0pt;
mso-bidi-font-size:
12.0pt;color:black'>):<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:black'>Scrap has remained constant, holding around $36.00cwt.
</span><span
style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt;
color:navy'><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'color:navy'><![if !supportEmptyParas]>&nbsp;<!
[endif]><o:p></o:p></span></p>

<h1><span style=3D'text-decoration:none;text-underline:none'><![if !
supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></h1>

<h1><span style=3D'text-decoration:none;text-underline:none'>BuyStainlessOnline.
com
Auction Statistics<o:p></o:p></span></h1>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'><!
[if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></p>

<table border=3D1 cellpadding=3D0 width=3D"19%" style=3D'width:19.82%;
mso-cellspacing:
 1.5pt;mso-padding-alt:0in 0in 0in 0in'>
 <tr>
  <td width=3D"74%" style=3D'width:74.66%;background:#BBBBBB;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal align=3Dcenter 
style=3D'text-align:center'><b>Category</b><span
  style=3D'color:black'><o:p></o:p></span></p>
  </td>
  <td width=3D"22%" style=3D'width:22.38%;background:#BBBBBB;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><b>Items</b><span
  style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"74%" style=3D'width:74.66%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?
angle">Angle</a><span
  style=3D'color:black'><o:p></o:p></span></p>
  </td>
  <td width=3D"22%" style=3D'width:22.38%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>0<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"74%" style=3D'width:74.66%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?
coil">Coil</a><span
  style=3D'color:black'><o:p></o:p></span></p>
  </td>
  <td width=3D"22%" style=3D'width:22.38%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>6<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"74%" style=3D'width:74.66%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?flat">Flat 
Bar</a><span
  style=3D'color:black'><o:p></o:p></span></p>
  </td>
  <td width=3D"22%" style=3D'width:22.38%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>8<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"74%" style=3D'width:74.66%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?
pipe">Pipe</a><span
  style=3D'color:black'><o:p></o:p></span></p>
  </td>
  <td width=3D"22%" style=3D'width:22.38%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>4<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"74%" style=3D'width:74.66%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?
plate">Plate</a><span
  style=3D'color:black'><o:p></o:p></span></p>
  </td>
  <td width=3D"22%" style=3D'width:22.38%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>10<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"74%" style=3D'width:74.66%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?rounds">Round 
Bar</a><span
  style=3D'color:black'><o:p></o:p></span></p>
  </td>
  <td width=3D"22%" style=3D'width:22.38%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>6<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"74%" style=3D'width:74.66%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?
sheet">Sheet</a><span
  style=3D'color:black'><o:p></o:p></span></p>
  </td>
  <td width=3D"22%" style=3D'width:22.38%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>9<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td width=3D"74%" style=3D'width:74.66%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal><a
  href=3D"http://buystainlessonline.com/cgi-local/auction.cgi?
tubing">Tubing</a><span
  style=3D'color:black'><o:p></o:p></span></p>
  </td>
  <td width=3D"22%" style=3D'width:22.38%;background:#EEEEEE;padding:.75pt .75pt .
75pt .75pt'>
  <p class=3DMsoNormal>1<span style=3D'color:black'><o:p></o:p></span></p>
  </td>
 </tr>
</table>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'><!
[if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'><!
[if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'><!
[if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.0pt'>If
you have a surplus item that you wish to sell,<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;mso-bidi-font-size:12.
0pt'>Feel
free to add an item! </span><b><span style=3D'font-size:10.0pt;
mso-bidi-font-size:
12.0pt;color:navy'><a href=3D"http://www.buystainlessonline.com/addtolist.htm"
title=3D"Start an Auction"><span style=3D'color:navy;text-decoration:none;
text-underline:none'>CLICK HERE</span></a></span></b><span 
style=3D'color:navy'><o:p></o:p></span></p>

<p class=3DMsoNormal><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;
color:red'><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></span></p>

<p class=3DMsoNormal><b><span style=3D'color:red'><![if !supportEmptyParas]>&nbsp;
<![endif]><o:p></o:p></span></b></p>

<p class=3DMsoNormal><b><span style=3D'color:navy'><a
href=3D"mailto:remove@buystainlessonline.com?subject=3Dunsubscribe"
title=3D"This will remove you from the E magazine StainlessOnly!"><span
style=3D'color:navy;text-decoration:none;text-underline:none'>UNSUBSCRIBE ME!
</span></a><o:p></o:p></span></b></p>

</div>

</body>

</html>

------=_NextPart_320623751655725754604743121--



From owner-ietf-outbound  Sat Feb  5 06:51:03 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA03330
	for ietf-outbound.10@ietf.org; Sat, 5 Feb 2000 06:50:02 -0500 (EST)
Received: from server.jad.net ([202.134.2.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03285
	for <ietf@ietf.org>; Sat, 5 Feb 2000 06:45:43 -0500 (EST)
Received: from oke.com (cf-isrlab7.comp.nus.edu.sg [137.132.85.181])
	by server.jad.net (8.9.2/8.9.2) with ESMTP id TAA08034;
	Sat, 5 Feb 2000 19:46:41 +0700 (JAVT)
	(envelope-from rms46@oke.com)
Sender: ibrahim@server.jad.net
Message-ID: <389C0D4A.813EF55E@oke.com>
Date: Sat, 05 Feb 2000 19:45:14 +0800
From: "Rahmat M. Samik-Ibrahim" <rms46@oke.com>
Reply-To: rms46.oke.com@vlsm.org
Organization: VLSM-TJT
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5-22 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: MILIS IETF <ietf@ietf.org>
Subject: Re: 1601bis: The Charter of IAB
References: <38928323.6DF08264@oke.com> <38973CC0.7587C6AD@hursley.ibm.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Hello:

Thank you for you reply and your valuable time. This following 
is "LONG" (as it is now the dragon year :-). You might want
to hit d(delete) now, or adjust your procmail configuration.

Brian E Carpenter wrote:

>>> Files can be obtained via
>>> http://www.ietf.org/internet-drafts/draft-ietf-iab-rfc1601bis-02.txt

>>  1. Why should the IESG approve the charter? Why not the ISOC?

> Because this is an IETF document defining the charter of an 
> IETF committee.

Oh, I see... first of all, I have no problem that the IESG
is the one in charge of giving each BCP a "sequence" number.
However, letting the IESG approve its "appealing body" charter
might be a little bit complicated.

Borrowing Li's term, a BCP is something that is:
     ....................................
     "accepted by the IETF, and by God, 
      this is how we're gonna do things".
     ....................................

In my understanding, therefore, a BCP should be more than
just accepted by the IETF. Furthermore, the first charter 
of IAB was introduced in a different way:

  ............................................................
  Subject: Draft IAB charter as part of ISOC
  From: Lyman Chapin
  Date: Wed, 15 Apr 92

  [...] Before I present the charter to the ISOC board, 
  I would like to hear from any of you who may have comments
  on the draft. Incorporation of the IAB into the ISOC brings 
  the IESG, IETF, and all of the other "pieces" into the ISOC 
  as well, so please read the proposed charter carefully, 
  and feel free to comment either directly to me or to the 
  IAB and/or IETF as a whole.

  [... see also RFC-1358 http://www.ietf.org/rfc/rfc1358.txt ]
  .............................................................


And so was RFC-1602 ( http://www.ietf.org/rfc/rfc1602.txt )

  .........................................................  
  Notice
 
  [...] This document is provisional, pending legal review
   and concurrence of the Internet Society Trustees.  [...]
  .........................................................


See also the minutes DRAFT of POISED95 WG, Los Angeles, 
4 & 5 March 1996:

   ..........................................................
   Minutes:  Bob Steen
   Chair:    Erik Huizer

   Overall Document Issues.
   ========================
   All three documents need to be accepted by the ISOC BoT.
   They will be given last call at the IETF level and then sent
   with a letter to the ISOC BoT.

   (... this following is extra ...)
   There was a short discussion on whether or not the Poised96
   should try to find out what is wrong with the process and
   examine the IAB, IETF, IRTF Roles  What's wrong?  What's not?
   The goal being to make a broad recommendation to fix these
   problems.  After discussion, this was dropped as unworkable.
   ...........................................................



So, what is the problem of clarifying who reviews the IAB
charter, and how it is going to be modified? Basically,
the IESG should concentrate with IETF's "core business",
and get rid (=out source) whatever the IESG is not 
interested to do in the first place.


>> 2. There is no clear statement about the relationship between
>>    ISOC and IAB. Why?

> The following seems clear enough to me:

>    The IAB acts as a source of advice and guidance to the Board of
>    Trustees and Officers of the Internet Society concerning technical,
>    architectural, procedural, and (where appropriate) policy matters
>    pertaining to the Internet and its enabling technologies.

Why? What for? It is about time for the IAB to understand how
important it is -- as an "appeal body", and not as a "super IESG".
The IAB is needed for maintaining the integrity of the IETF,
and to make sure that the IESG does what it supposed to do.
I have no idea (due to the poor documentation) whether the IESG
is really listen to the IAB when approving a new WG.

The ISOC is needed just like a monarchy needs a "king" or "queen"
but nothing else. The ISOC is needed to approve the IAB charter,
to appoint a NomCom chair, providing legal protections, 
perhaps as a supreme appeal body, etc.

Even being an "appeal body" can be delegated to a NOMCOM like
(or jury like) committee. But, the IAB should make sure that
the appeal body proceed as it supposed to do.


>> Enclosed is my suggested framework of 1601bis

> I don't see any items in your framework that are both appropriate to
> include in the charter and not included in the existing draft.

Still not clear? Basically,  I would like to suggest to put
back point #5 and especially point #6 of RFC 1160
(http://www.ietf.org/rfc/rfc1160.txt)

    ..............................................................
    The IAB performs the following functions:
    1)   Sets Internet Standards,
    2)   Manages the RFC publication process,
    3)   Reviews the operation of the IETF and IRTF,
    4)   Performs strategic planning for the Internet, identifying
         long-range problems and opportunities,
    5)   Acts as an international technical policy liaison and
         representative for the Internet community, and
    6)   Resolves technical issues which cannot be treated within
         the IETF or IRTF frameworks.
    ..............................................................

regards,

-- 
- Rahmat M. Samik-Ibrahim --  VLSM-TJT --  http://rms46.vlsm.org/ -
- Da da da ich lieb dich nicht du liebst mich nicht aha -- TRIO82 -



From owner-ietf-outbound@ietf.org  Sat Feb  5 06:52:32 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03373
	for <ietf-web-archive@odin.ietf.org>; Sat, 5 Feb 2000 06:52:27 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA11353;
	Sat, 5 Feb 2000 06:50:34 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id GAA03330
	for ietf-outbound.10@ietf.org; Sat, 5 Feb 2000 06:50:02 -0500 (EST)
Received: from server.jad.net ([202.134.2.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03285
	for <ietf@ietf.org>; Sat, 5 Feb 2000 06:45:43 -0500 (EST)
Received: from oke.com (cf-isrlab7.comp.nus.edu.sg [137.132.85.181])
	by server.jad.net (8.9.2/8.9.2) with ESMTP id TAA08034;
	Sat, 5 Feb 2000 19:46:41 +0700 (JAVT)
	(envelope-from rms46@oke.com)
Sender: ibrahim@server.jad.net
Message-ID: <389C0D4A.813EF55E@oke.com>
Date: Sat, 05 Feb 2000 19:45:14 +0800
From: "Rahmat M. Samik-Ibrahim" <rms46@oke.com>
Reply-To: rms46.oke.com@vlsm.org
Organization: VLSM-TJT
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5-22 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: MILIS IETF <ietf@ietf.org>
Subject: Re: 1601bis: The Charter of IAB
References: <38928323.6DF08264@oke.com> <38973CC0.7587C6AD@hursley.ibm.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Hello:

Thank you for you reply and your valuable time. This following 
is "LONG" (as it is now the dragon year :-). You might want
to hit d(delete) now, or adjust your procmail configuration.

Brian E Carpenter wrote:

>>> Files can be obtained via
>>> http://www.ietf.org/internet-drafts/draft-ietf-iab-rfc1601bis-02.txt

>>  1. Why should the IESG approve the charter? Why not the ISOC?

> Because this is an IETF document defining the charter of an 
> IETF committee.

Oh, I see... first of all, I have no problem that the IESG
is the one in charge of giving each BCP a "sequence" number.
However, letting the IESG approve its "appealing body" charter
might be a little bit complicated.

Borrowing Li's term, a BCP is something that is:
     ....................................
     "accepted by the IETF, and by God, 
      this is how we're gonna do things".
     ....................................

In my understanding, therefore, a BCP should be more than
just accepted by the IETF. Furthermore, the first charter 
of IAB was introduced in a different way:

  ............................................................
  Subject: Draft IAB charter as part of ISOC
  From: Lyman Chapin
  Date: Wed, 15 Apr 92

  [...] Before I present the charter to the ISOC board, 
  I would like to hear from any of you who may have comments
  on the draft. Incorporation of the IAB into the ISOC brings 
  the IESG, IETF, and all of the other "pieces" into the ISOC 
  as well, so please read the proposed charter carefully, 
  and feel free to comment either directly to me or to the 
  IAB and/or IETF as a whole.

  [... see also RFC-1358 http://www.ietf.org/rfc/rfc1358.txt ]
  .............................................................


And so was RFC-1602 ( http://www.ietf.org/rfc/rfc1602.txt )

  .........................................................  
  Notice
 
  [...] This document is provisional, pending legal review
   and concurrence of the Internet Society Trustees.  [...]
  .........................................................


See also the minutes DRAFT of POISED95 WG, Los Angeles, 
4 & 5 March 1996:

   ..........................................................
   Minutes:  Bob Steen
   Chair:    Erik Huizer

   Overall Document Issues.
   ========================
   All three documents need to be accepted by the ISOC BoT.
   They will be given last call at the IETF level and then sent
   with a letter to the ISOC BoT.

   (... this following is extra ...)
   There was a short discussion on whether or not the Poised96
   should try to find out what is wrong with the process and
   examine the IAB, IETF, IRTF Roles  What's wrong?  What's not?
   The goal being to make a broad recommendation to fix these
   problems.  After discussion, this was dropped as unworkable.
   ...........................................................



So, what is the problem of clarifying who reviews the IAB
charter, and how it is going to be modified? Basically,
the IESG should concentrate with IETF's "core business",
and get rid (=out source) whatever the IESG is not 
interested to do in the first place.


>> 2. There is no clear statement about the relationship between
>>    ISOC and IAB. Why?

> The following seems clear enough to me:

>    The IAB acts as a source of advice and guidance to the Board of
>    Trustees and Officers of the Internet Society concerning technical,
>    architectural, procedural, and (where appropriate) policy matters
>    pertaining to the Internet and its enabling technologies.

Why? What for? It is about time for the IAB to understand how
important it is -- as an "appeal body", and not as a "super IESG".
The IAB is needed for maintaining the integrity of the IETF,
and to make sure that the IESG does what it supposed to do.
I have no idea (due to the poor documentation) whether the IESG
is really listen to the IAB when approving a new WG.

The ISOC is needed just like a monarchy needs a "king" or "queen"
but nothing else. The ISOC is needed to approve the IAB charter,
to appoint a NomCom chair, providing legal protections, 
perhaps as a supreme appeal body, etc.

Even being an "appeal body" can be delegated to a NOMCOM like
(or jury like) committee. But, the IAB should make sure that
the appeal body proceed as it supposed to do.


>> Enclosed is my suggested framework of 1601bis

> I don't see any items in your framework that are both appropriate to
> include in the charter and not included in the existing draft.

Still not clear? Basically,  I would like to suggest to put
back point #5 and especially point #6 of RFC 1160
(http://www.ietf.org/rfc/rfc1160.txt)

    ..............................................................
    The IAB performs the following functions:
    1)   Sets Internet Standards,
    2)   Manages the RFC publication process,
    3)   Reviews the operation of the IETF and IRTF,
    4)   Performs strategic planning for the Internet, identifying
         long-range problems and opportunities,
    5)   Acts as an international technical policy liaison and
         representative for the Internet community, and
    6)   Resolves technical issues which cannot be treated within
         the IETF or IRTF frameworks.
    ..............................................................

regards,

-- 
- Rahmat M. Samik-Ibrahim --  VLSM-TJT --  http://rms46.vlsm.org/ -
- Da da da ich lieb dich nicht du liebst mich nicht aha -- TRIO82 -



From owner-ietf-outbound  Mon Feb  7 03:23:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA00667
	for ietf-outbound.10@ietf.org; Mon, 7 Feb 2000 03:20:02 -0500 (EST)
Received: from prosyst.com (server.prosyst.com [195.14.248.34] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA00593
	for <ietf@ietf.org>; Mon, 7 Feb 2000 03:12:03 -0500 (EST)
Message-ID: <389E7E06.D430AEDF@prosyst.com>
Date: Mon, 07 Feb 2000 10:10:46 +0200
From: plamen kosseff <p_kosseff@prosyst.com>
X-Mailer: Mozilla 4.5 [en] (WinNT; I)
X-Accept-Language: bg,en
MIME-Version: 1.0
To: webmaster@buystainlessonline.com
CC: ietf@ietf.org
Subject: Re: 4 year high for Nickel on the LME
References: <cckvhpivfufbrr.tmdtwyltdxueqbfw@mason.buystainlessonline.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

how to hell this got here



From owner-ietf-outbound@ietf.org  Mon Feb  7 03:26:16 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00735
	for <ietf-web-archive@odin.ietf.org>; Mon, 7 Feb 2000 03:26:16 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA09574;
	Mon, 7 Feb 2000 03:24:15 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id DAA00667
	for ietf-outbound.10@ietf.org; Mon, 7 Feb 2000 03:20:02 -0500 (EST)
Received: from prosyst.com (server.prosyst.com [195.14.248.34] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA00593
	for <ietf@ietf.org>; Mon, 7 Feb 2000 03:12:03 -0500 (EST)
Message-ID: <389E7E06.D430AEDF@prosyst.com>
Date: Mon, 07 Feb 2000 10:10:46 +0200
From: plamen kosseff <p_kosseff@prosyst.com>
X-Mailer: Mozilla 4.5 [en] (WinNT; I)
X-Accept-Language: bg,en
MIME-Version: 1.0
To: webmaster@buystainlessonline.com
CC: ietf@ietf.org
Subject: Re: 4 year high for Nickel on the LME
References: <cckvhpivfufbrr.tmdtwyltdxueqbfw@mason.buystainlessonline.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

how to hell this got here



From owner-ietf-outbound  Mon Feb  7 11:20:59 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA13960
	for ietf-outbound.10@ietf.org; Mon, 7 Feb 2000 11:20:02 -0500 (EST)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13855
	for <ietf@ietf.org>; Mon, 7 Feb 2000 11:16:09 -0500 (EST)
Received: from sp3at21.hursley.ibm.com (sp3at21.hursley.ibm.com [9.20.45.21]) by mail-gw.hursley.ibm.com (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id QAA278358; Mon, 7 Feb 2000 16:15:32 GMT
Received: from hursley.ibm.com (gsine04.us.sine.ibm.com [9.14.6.44]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id QAA27768; Mon, 7 Feb 2000 16:15:28 GMT
Message-ID: <389EEEE1.555A4FF4@hursley.ibm.com>
Date: Mon, 07 Feb 2000 10:12:17 -0600
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en,fr
MIME-Version: 1.0
To: rms46.oke.com@vlsm.org
CC: MILIS IETF <ietf@ietf.org>
Subject: Re: 1601bis: The Charter of IAB
References: <38928323.6DF08264@oke.com> <38973CC0.7587C6AD@hursley.ibm.com> <389C0D4A.813EF55E@oke.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi Rahmat,

I can read your words, but I really can't understand your concerns. You seem
to be worrying about dragons that I can't see. Happy New Year, anyway.

  Brian

"Rahmat M. Samik-Ibrahim" wrote:
> 
> Hello:
> 
> Thank you for you reply and your valuable time. This following
> is "LONG" (as it is now the dragon year :-). You might want
> to hit d(delete) now, or adjust your procmail configuration.
> 
> Brian E Carpenter wrote:
> 
> >>> Files can be obtained via
> >>> http://www.ietf.org/internet-drafts/draft-ietf-iab-rfc1601bis-02.txt
> 
> >>  1. Why should the IESG approve the charter? Why not the ISOC?
> 
> > Because this is an IETF document defining the charter of an
> > IETF committee.
> 
> Oh, I see... first of all, I have no problem that the IESG
> is the one in charge of giving each BCP a "sequence" number.
> However, letting the IESG approve its "appealing body" charter
> might be a little bit complicated.
> 
> Borrowing Li's term, a BCP is something that is:
>      ....................................
>      "accepted by the IETF, and by God,
>       this is how we're gonna do things".
>      ....................................
> 
> In my understanding, therefore, a BCP should be more than
> just accepted by the IETF. Furthermore, the first charter
> of IAB was introduced in a different way:
> 
>   ............................................................
>   Subject: Draft IAB charter as part of ISOC
>   From: Lyman Chapin
>   Date: Wed, 15 Apr 92
> 
>   [...] Before I present the charter to the ISOC board,
>   I would like to hear from any of you who may have comments
>   on the draft. Incorporation of the IAB into the ISOC brings
>   the IESG, IETF, and all of the other "pieces" into the ISOC
>   as well, so please read the proposed charter carefully,
>   and feel free to comment either directly to me or to the
>   IAB and/or IETF as a whole.
> 
>   [... see also RFC-1358 http://www.ietf.org/rfc/rfc1358.txt ]
>   .............................................................
> 
> And so was RFC-1602 ( http://www.ietf.org/rfc/rfc1602.txt )
> 
>   .........................................................
>   Notice
> 
>   [...] This document is provisional, pending legal review
>    and concurrence of the Internet Society Trustees.  [...]
>   .........................................................
> 
> See also the minutes DRAFT of POISED95 WG, Los Angeles,
> 4 & 5 March 1996:
> 
>    ..........................................................
>    Minutes:  Bob Steen
>    Chair:    Erik Huizer
> 
>    Overall Document Issues.
>    ========================
>    All three documents need to be accepted by the ISOC BoT.
>    They will be given last call at the IETF level and then sent
>    with a letter to the ISOC BoT.
> 
>    (... this following is extra ...)
>    There was a short discussion on whether or not the Poised96
>    should try to find out what is wrong with the process and
>    examine the IAB, IETF, IRTF Roles  What's wrong?  What's not?
>    The goal being to make a broad recommendation to fix these
>    problems.  After discussion, this was dropped as unworkable.
>    ...........................................................
> 
> So, what is the problem of clarifying who reviews the IAB
> charter, and how it is going to be modified? Basically,
> the IESG should concentrate with IETF's "core business",
> and get rid (=out source) whatever the IESG is not
> interested to do in the first place.
> 
> >> 2. There is no clear statement about the relationship between
> >>    ISOC and IAB. Why?
> 
> > The following seems clear enough to me:
> 
> >    The IAB acts as a source of advice and guidance to the Board of
> >    Trustees and Officers of the Internet Society concerning technical,
> >    architectural, procedural, and (where appropriate) policy matters
> >    pertaining to the Internet and its enabling technologies.
> 
> Why? What for? It is about time for the IAB to understand how
> important it is -- as an "appeal body", and not as a "super IESG".
> The IAB is needed for maintaining the integrity of the IETF,
> and to make sure that the IESG does what it supposed to do.
> I have no idea (due to the poor documentation) whether the IESG
> is really listen to the IAB when approving a new WG.
> 
> The ISOC is needed just like a monarchy needs a "king" or "queen"
> but nothing else. The ISOC is needed to approve the IAB charter,
> to appoint a NomCom chair, providing legal protections,
> perhaps as a supreme appeal body, etc.
> 
> Even being an "appeal body" can be delegated to a NOMCOM like
> (or jury like) committee. But, the IAB should make sure that
> the appeal body proceed as it supposed to do.
> 
> >> Enclosed is my suggested framework of 1601bis
> 
> > I don't see any items in your framework that are both appropriate to
> > include in the charter and not included in the existing draft.
> 
> Still not clear? Basically,  I would like to suggest to put
> back point #5 and especially point #6 of RFC 1160
> (http://www.ietf.org/rfc/rfc1160.txt)
> 
>     ..............................................................
>     The IAB performs the following functions:
>     1)   Sets Internet Standards,
>     2)   Manages the RFC publication process,
>     3)   Reviews the operation of the IETF and IRTF,
>     4)   Performs strategic planning for the Internet, identifying
>          long-range problems and opportunities,
>     5)   Acts as an international technical policy liaison and
>          representative for the Internet community, and
>     6)   Resolves technical issues which cannot be treated within
>          the IETF or IRTF frameworks.
>     ..............................................................
> 
> regards,
> 
> --
> - Rahmat M. Samik-Ibrahim --  VLSM-TJT --  http://rms46.vlsm.org/ -
> - Da da da ich lieb dich nicht du liebst mich nicht aha -- TRIO82 -



From owner-ietf-outbound@ietf.org  Mon Feb  7 11:26:43 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14189
	for <ietf-web-archive@odin.ietf.org>; Mon, 7 Feb 2000 11:26:43 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA23026;
	Mon, 7 Feb 2000 11:24:51 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id LAA13960
	for ietf-outbound.10@ietf.org; Mon, 7 Feb 2000 11:20:02 -0500 (EST)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13855
	for <ietf@ietf.org>; Mon, 7 Feb 2000 11:16:09 -0500 (EST)
Received: from sp3at21.hursley.ibm.com (sp3at21.hursley.ibm.com [9.20.45.21]) by mail-gw.hursley.ibm.com (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id QAA278358; Mon, 7 Feb 2000 16:15:32 GMT
Received: from hursley.ibm.com (gsine04.us.sine.ibm.com [9.14.6.44]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id QAA27768; Mon, 7 Feb 2000 16:15:28 GMT
Message-ID: <389EEEE1.555A4FF4@hursley.ibm.com>
Date: Mon, 07 Feb 2000 10:12:17 -0600
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en,fr
MIME-Version: 1.0
To: rms46.oke.com@vlsm.org
CC: MILIS IETF <ietf@ietf.org>
Subject: Re: 1601bis: The Charter of IAB
References: <38928323.6DF08264@oke.com> <38973CC0.7587C6AD@hursley.ibm.com> <389C0D4A.813EF55E@oke.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi Rahmat,

I can read your words, but I really can't understand your concerns. You seem
to be worrying about dragons that I can't see. Happy New Year, anyway.

  Brian

"Rahmat M. Samik-Ibrahim" wrote:
> 
> Hello:
> 
> Thank you for you reply and your valuable time. This following
> is "LONG" (as it is now the dragon year :-). You might want
> to hit d(delete) now, or adjust your procmail configuration.
> 
> Brian E Carpenter wrote:
> 
> >>> Files can be obtained via
> >>> http://www.ietf.org/internet-drafts/draft-ietf-iab-rfc1601bis-02.txt
> 
> >>  1. Why should the IESG approve the charter? Why not the ISOC?
> 
> > Because this is an IETF document defining the charter of an
> > IETF committee.
> 
> Oh, I see... first of all, I have no problem that the IESG
> is the one in charge of giving each BCP a "sequence" number.
> However, letting the IESG approve its "appealing body" charter
> might be a little bit complicated.
> 
> Borrowing Li's term, a BCP is something that is:
>      ....................................
>      "accepted by the IETF, and by God,
>       this is how we're gonna do things".
>      ....................................
> 
> In my understanding, therefore, a BCP should be more than
> just accepted by the IETF. Furthermore, the first charter
> of IAB was introduced in a different way:
> 
>   ............................................................
>   Subject: Draft IAB charter as part of ISOC
>   From: Lyman Chapin
>   Date: Wed, 15 Apr 92
> 
>   [...] Before I present the charter to the ISOC board,
>   I would like to hear from any of you who may have comments
>   on the draft. Incorporation of the IAB into the ISOC brings
>   the IESG, IETF, and all of the other "pieces" into the ISOC
>   as well, so please read the proposed charter carefully,
>   and feel free to comment either directly to me or to the
>   IAB and/or IETF as a whole.
> 
>   [... see also RFC-1358 http://www.ietf.org/rfc/rfc1358.txt ]
>   .............................................................
> 
> And so was RFC-1602 ( http://www.ietf.org/rfc/rfc1602.txt )
> 
>   .........................................................
>   Notice
> 
>   [...] This document is provisional, pending legal review
>    and concurrence of the Internet Society Trustees.  [...]
>   .........................................................
> 
> See also the minutes DRAFT of POISED95 WG, Los Angeles,
> 4 & 5 March 1996:
> 
>    ..........................................................
>    Minutes:  Bob Steen
>    Chair:    Erik Huizer
> 
>    Overall Document Issues.
>    ========================
>    All three documents need to be accepted by the ISOC BoT.
>    They will be given last call at the IETF level and then sent
>    with a letter to the ISOC BoT.
> 
>    (... this following is extra ...)
>    There was a short discussion on whether or not the Poised96
>    should try to find out what is wrong with the process and
>    examine the IAB, IETF, IRTF Roles  What's wrong?  What's not?
>    The goal being to make a broad recommendation to fix these
>    problems.  After discussion, this was dropped as unworkable.
>    ...........................................................
> 
> So, what is the problem of clarifying who reviews the IAB
> charter, and how it is going to be modified? Basically,
> the IESG should concentrate with IETF's "core business",
> and get rid (=out source) whatever the IESG is not
> interested to do in the first place.
> 
> >> 2. There is no clear statement about the relationship between
> >>    ISOC and IAB. Why?
> 
> > The following seems clear enough to me:
> 
> >    The IAB acts as a source of advice and guidance to the Board of
> >    Trustees and Officers of the Internet Society concerning technical,
> >    architectural, procedural, and (where appropriate) policy matters
> >    pertaining to the Internet and its enabling technologies.
> 
> Why? What for? It is about time for the IAB to understand how
> important it is -- as an "appeal body", and not as a "super IESG".
> The IAB is needed for maintaining the integrity of the IETF,
> and to make sure that the IESG does what it supposed to do.
> I have no idea (due to the poor documentation) whether the IESG
> is really listen to the IAB when approving a new WG.
> 
> The ISOC is needed just like a monarchy needs a "king" or "queen"
> but nothing else. The ISOC is needed to approve the IAB charter,
> to appoint a NomCom chair, providing legal protections,
> perhaps as a supreme appeal body, etc.
> 
> Even being an "appeal body" can be delegated to a NOMCOM like
> (or jury like) committee. But, the IAB should make sure that
> the appeal body proceed as it supposed to do.
> 
> >> Enclosed is my suggested framework of 1601bis
> 
> > I don't see any items in your framework that are both appropriate to
> > include in the charter and not included in the existing draft.
> 
> Still not clear? Basically,  I would like to suggest to put
> back point #5 and especially point #6 of RFC 1160
> (http://www.ietf.org/rfc/rfc1160.txt)
> 
>     ..............................................................
>     The IAB performs the following functions:
>     1)   Sets Internet Standards,
>     2)   Manages the RFC publication process,
>     3)   Reviews the operation of the IETF and IRTF,
>     4)   Performs strategic planning for the Internet, identifying
>          long-range problems and opportunities,
>     5)   Acts as an international technical policy liaison and
>          representative for the Internet community, and
>     6)   Resolves technical issues which cannot be treated within
>          the IETF or IRTF frameworks.
>     ..............................................................
> 
> regards,
> 
> --
> - Rahmat M. Samik-Ibrahim --  VLSM-TJT --  http://rms46.vlsm.org/ -
> - Da da da ich lieb dich nicht du liebst mich nicht aha -- TRIO82 -



From owner-ietf-outbound  Wed Feb  9 06:31:48 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA03389
	for ietf-outbound.10@ietf.org; Wed, 9 Feb 2000 06:30:01 -0500 (EST)
Received: from mail1.itu.int (mail1.itu.ch [156.106.192.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03320
	for <IETF@ietf.org>; Wed, 9 Feb 2000 06:22:07 -0500 (EST)
Received: from dcrocker.~nodomain~ (BRANDENBURG [156.106.209.25]) by mail1.itu.int with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id D5S7DWVH; Wed, 9 Feb 2000 12:22:19 +0100
Message-Id: <4.3.0.39.0.20000209092752.00c554f0@mail.bayarea.net>
X-Sender: dcrocker@mail.bayarea.net
X-Mailer: QUALCOMM Windows Eudora Version 4.3.0.39 (Beta)
Date: Wed, 09 Feb 2000 11:21:24 +0100
To: IETF@ietf.org
From: Dave Crocker <dcrocker@brandenburg.com>
Subject: IETF meeting wireless "standard"
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

Folks,

Although providers of Internet access at IETF meetings are free to add all 
sorts of functional enhancements, there are some basics that have become 
standard, such as DHCP-based RJ-45 Ethernet access.

Given the remarkable benefit that we have experienced with wireless access, 
recently, I'd like to suggest that we declare it a standard for IETF 
meetings.

My impression from online discussions prior to the last IETF meeting, is 
that there is a rough consensus that 802.11 DS (2Mbps/11Mbps) is the 
technology choice, for the current market.

(I've already been told that Adelaide will support this, so this thread 
does not affect their service efforts.)

My reason for the particular timing of this note is to wonder -- if there 
is consensus about long-term support for 802.11 DS -- whether a bulk 
purchase of cards for a discounted price is worth pursuing prior to (or at) 
Adelaide?

d/

=-=-=-=-=
Dave Crocker  <dcrocker@brandenburg.com>
Brandenburg Consulting  <www.brandenburg.com>
Tel: +1.408.246.8253,  Fax: +1.408.273.6464
675 Spruce Drive,  Sunnyvale, CA 94086 USA

Gong Xi Fa Cai   /  Selamat Tahun Baru Cina



From owner-ietf-outbound@ietf.org  Wed Feb  9 06:33:05 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03519
	for <ietf-web-archive@odin.ietf.org>; Wed, 9 Feb 2000 06:33:05 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA02300;
	Wed, 9 Feb 2000 06:31:08 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id GAA03389
	for ietf-outbound.10@ietf.org; Wed, 9 Feb 2000 06:30:01 -0500 (EST)
Received: from mail1.itu.int (mail1.itu.ch [156.106.192.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03320
	for <IETF@ietf.org>; Wed, 9 Feb 2000 06:22:07 -0500 (EST)
Received: from dcrocker.~nodomain~ (BRANDENBURG [156.106.209.25]) by mail1.itu.int with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id D5S7DWVH; Wed, 9 Feb 2000 12:22:19 +0100
Message-Id: <4.3.0.39.0.20000209092752.00c554f0@mail.bayarea.net>
X-Sender: dcrocker@mail.bayarea.net
X-Mailer: QUALCOMM Windows Eudora Version 4.3.0.39 (Beta)
Date: Wed, 09 Feb 2000 11:21:24 +0100
To: IETF@ietf.org
From: Dave Crocker <dcrocker@brandenburg.com>
Subject: IETF meeting wireless "standard"
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

Folks,

Although providers of Internet access at IETF meetings are free to add all 
sorts of functional enhancements, there are some basics that have become 
standard, such as DHCP-based RJ-45 Ethernet access.

Given the remarkable benefit that we have experienced with wireless access, 
recently, I'd like to suggest that we declare it a standard for IETF 
meetings.

My impression from online discussions prior to the last IETF meeting, is 
that there is a rough consensus that 802.11 DS (2Mbps/11Mbps) is the 
technology choice, for the current market.

(I've already been told that Adelaide will support this, so this thread 
does not affect their service efforts.)

My reason for the particular timing of this note is to wonder -- if there 
is consensus about long-term support for 802.11 DS -- whether a bulk 
purchase of cards for a discounted price is worth pursuing prior to (or at) 
Adelaide?

d/

=-=-=-=-=
Dave Crocker  <dcrocker@brandenburg.com>
Brandenburg Consulting  <www.brandenburg.com>
Tel: +1.408.246.8253,  Fax: +1.408.273.6464
675 Spruce Drive,  Sunnyvale, CA 94086 USA

Gong Xi Fa Cai   /  Selamat Tahun Baru Cina



From owner-ietf-outbound  Wed Feb  9 09:30:42 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA06970
	for ietf-outbound.10@ietf.org; Wed, 9 Feb 2000 09:30:01 -0500 (EST)
Received: from tsx-prime.MIT.EDU (TSX-PRIME.MIT.EDU [18.86.0.76])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA06851
	for <IETF@ietf.org>; Wed, 9 Feb 2000 09:23:24 -0500 (EST)
Received: by tsx-prime.MIT.EDU 
	with sendmail-SMI-8.6/1.2, id JAA07600; Wed, 9 Feb 2000 09:23:19 -0500
Date: Wed, 9 Feb 2000 09:23:19 -0500
Message-Id: <200002091423.JAA07600@tsx-prime.MIT.EDU>
From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: Dave Crocker <dcrocker@brandenburg.com>
CC: IETF@ietf.org
In-reply-to: Dave Crocker's message of Wed, 09 Feb 2000 11:21:24 +0100,
	<4.3.0.39.0.20000209092752.00c554f0@mail.bayarea.net>
Subject: Re: IETF meeting wireless "standard"
Phone: (781) 391-3464
X-Loop: ietf@ietf.org

   Date: Wed, 09 Feb 2000 11:21:24 +0100
   From: Dave Crocker <dcrocker@brandenburg.com>

   My reason for the particular timing of this note is to wonder -- if there 
   is consensus about long-term support for 802.11 DS -- whether a bulk 
   purchase of cards for a discounted price is worth pursuing prior to (or at) 
   Adelaide?

Prior.  Definitely prior; that way folks don't have to spend the first
half of the week hacking support for the 802.11 DS card into NetBSD,
Linux, BSDI, et. al.  :-)

I'm definitely interested.  So do we have someone with a company
connection who can get the IETF a good bulk discount on 801.11 DS cards?
Especially the 11 megabit variant...  (Is Adelaide going to have 11 mbps
support?) 

						- Ted



From owner-ietf-outbound@ietf.org  Wed Feb  9 09:33:18 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07106
	for <ietf-web-archive@odin.ietf.org>; Wed, 9 Feb 2000 09:33:18 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA07219;
	Wed, 9 Feb 2000 09:31:18 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id JAA06970
	for ietf-outbound.10@ietf.org; Wed, 9 Feb 2000 09:30:01 -0500 (EST)
Received: from tsx-prime.MIT.EDU (TSX-PRIME.MIT.EDU [18.86.0.76])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA06851
	for <IETF@ietf.org>; Wed, 9 Feb 2000 09:23:24 -0500 (EST)
Received: by tsx-prime.MIT.EDU 
	with sendmail-SMI-8.6/1.2, id JAA07600; Wed, 9 Feb 2000 09:23:19 -0500
Date: Wed, 9 Feb 2000 09:23:19 -0500
Message-Id: <200002091423.JAA07600@tsx-prime.MIT.EDU>
From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: Dave Crocker <dcrocker@brandenburg.com>
CC: IETF@ietf.org
In-reply-to: Dave Crocker's message of Wed, 09 Feb 2000 11:21:24 +0100,
	<4.3.0.39.0.20000209092752.00c554f0@mail.bayarea.net>
Subject: Re: IETF meeting wireless "standard"
Phone: (781) 391-3464
X-Loop: ietf@ietf.org

   Date: Wed, 09 Feb 2000 11:21:24 +0100
   From: Dave Crocker <dcrocker@brandenburg.com>

   My reason for the particular timing of this note is to wonder -- if there 
   is consensus about long-term support for 802.11 DS -- whether a bulk 
   purchase of cards for a discounted price is worth pursuing prior to (or at) 
   Adelaide?

Prior.  Definitely prior; that way folks don't have to spend the first
half of the week hacking support for the 802.11 DS card into NetBSD,
Linux, BSDI, et. al.  :-)

I'm definitely interested.  So do we have someone with a company
connection who can get the IETF a good bulk discount on 801.11 DS cards?
Especially the 11 megabit variant...  (Is Adelaide going to have 11 mbps
support?) 

						- Ted



From owner-ietf-outbound  Wed Feb  9 10:20:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA07882
	for ietf-outbound.10@ietf.org; Wed, 9 Feb 2000 10:20:02 -0500 (EST)
Received: from alpha.netvision.net.il (alpha.netvision.net.il [194.90.1.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07857
	for <ietf@ietf.org>; Wed, 9 Feb 2000 10:19:39 -0500 (EST)
Received: from sendout.icomverse.com (Efrat-FR3.ser.netvision.net.il [199.203.174.65])
	by alpha.netvision.net.il (8.9.3/8.8.6) with ESMTP id RAA29603
	for <ietf@ietf.org>; Wed, 9 Feb 2000 17:19:25 +0200 (IST)
Received: from ismail1.icomverse.com (ismail1.icomverse.com [190.190.110.2])
	by sendout.icomverse.com (8.9.3/8.8.7) with ESMTP id RAA18048
	for <ietf@ietf.org>; Wed, 9 Feb 2000 17:19:59 +0200
Received: by ismail1.icomverse.com with Internet Mail Service (5.5.2650.21)
	id <1RMLNRQC>; Wed, 9 Feb 2000 17:19:06 +0200
Message-ID: <CE835E918749D21191B10060084C377E016D1E93@ismail1.icomverse.com>
From: "Gazal, Elly" <Elly_Gazal@icomverse.com>
To: "'IETF'" <ietf@ietf.org>
Subject: voice mail packaging
Date: Wed, 9 Feb 2000 17:19:05 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-8-i"
X-Loop: ietf@ietf.org

What is Voicemail packaging? 
Are SIP+ and SIP-TGCP related to VM packaging? if so, how?

Please help!


Regards,

Elly Gazal
System Engineer

Signaling R&D Group
Comverse Network Systems Ltd.

*(Tel):		972-3-6458994
*(Fax):		972-3-6458915
*(Mobile):	N/A
*(Addr):	7 Habarzel st., Ramat-Hachayal
             	Tel-Aviv, 69710, Israel
* (Time):	GMT+02:00
* (e-mail):  	Elly_Gazal@icomverse.com



From owner-ietf-outbound@ietf.org  Wed Feb  9 10:21:36 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07955
	for <ietf-web-archive@odin.ietf.org>; Wed, 9 Feb 2000 10:21:35 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA10243;
	Wed, 9 Feb 2000 10:19:39 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id KAA07882
	for ietf-outbound.10@ietf.org; Wed, 9 Feb 2000 10:20:02 -0500 (EST)
Received: from alpha.netvision.net.il (alpha.netvision.net.il [194.90.1.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07857
	for <ietf@ietf.org>; Wed, 9 Feb 2000 10:19:39 -0500 (EST)
Received: from sendout.icomverse.com (Efrat-FR3.ser.netvision.net.il [199.203.174.65])
	by alpha.netvision.net.il (8.9.3/8.8.6) with ESMTP id RAA29603
	for <ietf@ietf.org>; Wed, 9 Feb 2000 17:19:25 +0200 (IST)
Received: from ismail1.icomverse.com (ismail1.icomverse.com [190.190.110.2])
	by sendout.icomverse.com (8.9.3/8.8.7) with ESMTP id RAA18048
	for <ietf@ietf.org>; Wed, 9 Feb 2000 17:19:59 +0200
Received: by ismail1.icomverse.com with Internet Mail Service (5.5.2650.21)
	id <1RMLNRQC>; Wed, 9 Feb 2000 17:19:06 +0200
Message-ID: <CE835E918749D21191B10060084C377E016D1E93@ismail1.icomverse.com>
From: "Gazal, Elly" <Elly_Gazal@icomverse.com>
To: "'IETF'" <ietf@ietf.org>
Subject: voice mail packaging
Date: Wed, 9 Feb 2000 17:19:05 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-8-i"
X-Loop: ietf@ietf.org

What is Voicemail packaging? 
Are SIP+ and SIP-TGCP related to VM packaging? if so, how?

Please help!


Regards,

Elly Gazal
System Engineer

Signaling R&D Group
Comverse Network Systems Ltd.

*(Tel):		972-3-6458994
*(Fax):		972-3-6458915
*(Mobile):	N/A
*(Addr):	7 Habarzel st., Ramat-Hachayal
             	Tel-Aviv, 69710, Israel
* (Time):	GMT+02:00
* (e-mail):  	Elly_Gazal@icomverse.com



From owner-ietf-outbound  Wed Feb  9 10:50:33 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA08454
	for ietf-outbound.10@ietf.org; Wed, 9 Feb 2000 10:50:02 -0500 (EST)
Received: from alpha.netvision.net.il (alpha.netvision.net.il [194.90.1.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08370
	for <ietf@ietf.org>; Wed, 9 Feb 2000 10:45:57 -0500 (EST)
Received: from sendout.icomverse.com (Efrat-FR3.ser.netvision.net.il [199.203.174.65])
	by alpha.netvision.net.il (8.9.3/8.8.6) with ESMTP id RAA19412
	for <ietf@ietf.org>; Wed, 9 Feb 2000 17:45:34 +0200 (IST)
Received: from ismail1.icomverse.com (ismail1.icomverse.com [190.190.110.2])
	by sendout.icomverse.com (8.9.3/8.8.7) with ESMTP id RAA18843
	for <ietf@ietf.org>; Wed, 9 Feb 2000 17:46:14 +0200
Received: by ismail1.icomverse.com with Internet Mail Service (5.5.2650.21)
	id <1RMLNRQT>; Wed, 9 Feb 2000 17:45:22 +0200
Message-ID: <CE835E918749D21191B10060084C377E016D1E96@ismail1.icomverse.com>
From: "Gazal, Elly" <Elly_Gazal@icomverse.com>
To: "'IETF'" <ietf@ietf.org>
Subject: VM packaging
Date: Wed, 9 Feb 2000 17:45:21 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-8-i"
X-Loop: ietf@ietf.org

Can anyone explain what is "VoiceMail Packaging"???

Regards,

Elly Gazal
System Engineer



From owner-ietf-outbound@ietf.org  Wed Feb  9 10:51:35 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08516
	for <ietf-web-archive@odin.ietf.org>; Wed, 9 Feb 2000 10:51:35 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA11029;
	Wed, 9 Feb 2000 10:49:39 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id KAA08454
	for ietf-outbound.10@ietf.org; Wed, 9 Feb 2000 10:50:02 -0500 (EST)
Received: from alpha.netvision.net.il (alpha.netvision.net.il [194.90.1.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08370
	for <ietf@ietf.org>; Wed, 9 Feb 2000 10:45:57 -0500 (EST)
Received: from sendout.icomverse.com (Efrat-FR3.ser.netvision.net.il [199.203.174.65])
	by alpha.netvision.net.il (8.9.3/8.8.6) with ESMTP id RAA19412
	for <ietf@ietf.org>; Wed, 9 Feb 2000 17:45:34 +0200 (IST)
Received: from ismail1.icomverse.com (ismail1.icomverse.com [190.190.110.2])
	by sendout.icomverse.com (8.9.3/8.8.7) with ESMTP id RAA18843
	for <ietf@ietf.org>; Wed, 9 Feb 2000 17:46:14 +0200
Received: by ismail1.icomverse.com with Internet Mail Service (5.5.2650.21)
	id <1RMLNRQT>; Wed, 9 Feb 2000 17:45:22 +0200
Message-ID: <CE835E918749D21191B10060084C377E016D1E96@ismail1.icomverse.com>
From: "Gazal, Elly" <Elly_Gazal@icomverse.com>
To: "'IETF'" <ietf@ietf.org>
Subject: VM packaging
Date: Wed, 9 Feb 2000 17:45:21 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-8-i"
X-Loop: ietf@ietf.org

Can anyone explain what is "VoiceMail Packaging"???

Regards,

Elly Gazal
System Engineer



From owner-ietf-outbound  Wed Feb  9 13:40:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA15928
	for ietf-outbound.10@ietf.org; Wed, 9 Feb 2000 13:40:03 -0500 (EST)
Received: from infidel.boolean.net (root@router.boolean.net [198.144.206.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15425
	for <ietf@ietf.org>; Wed, 9 Feb 2000 13:32:40 -0500 (EST)
Received: from gypsy (gypsy.boolean.net [198.144.202.243])
	by infidel.boolean.net (8.9.3/8.9.3) with SMTP id SAA04319
	for <ietf@ietf.org>; Wed, 9 Feb 2000 18:32:38 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <3.0.5.32.20000209103238.0093d100@infidel.boolean.net>
X-Sender: guru@infidel.boolean.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Wed, 09 Feb 2000 10:32:38 -0800
To: ietf@ietf.org
From: "Kurt D. Zeilenga" <Kurt@OPENLDAP.ORG>
Subject: Intended category of I-Ds
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

I believe the I-D guidelines should be revised to recommend
authors include a statement indicating which RFC category the
I-D is intended to be published in.  This allows the reviewer
to apply determine a level of scrutity based upon the intended
category.

I've come a cross a number of WG I-Ds which did not indicate
their intended category AND the WG I-D didn't provide appropriate
clarification.  (Yes, I've brought this to the attention of
the WG chairs and I-D authors).

Comments?



From owner-ietf-outbound@ietf.org  Wed Feb  9 13:41:38 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16086
	for <ietf-web-archive@odin.ietf.org>; Wed, 9 Feb 2000 13:41:38 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA18259;
	Wed, 9 Feb 2000 13:39:40 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id NAA15928
	for ietf-outbound.10@ietf.org; Wed, 9 Feb 2000 13:40:03 -0500 (EST)
Received: from infidel.boolean.net (root@router.boolean.net [198.144.206.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15425
	for <ietf@ietf.org>; Wed, 9 Feb 2000 13:32:40 -0500 (EST)
Received: from gypsy (gypsy.boolean.net [198.144.202.243])
	by infidel.boolean.net (8.9.3/8.9.3) with SMTP id SAA04319
	for <ietf@ietf.org>; Wed, 9 Feb 2000 18:32:38 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <3.0.5.32.20000209103238.0093d100@infidel.boolean.net>
X-Sender: guru@infidel.boolean.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Wed, 09 Feb 2000 10:32:38 -0800
To: ietf@ietf.org
From: "Kurt D. Zeilenga" <Kurt@OPENLDAP.ORG>
Subject: Intended category of I-Ds
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

I believe the I-D guidelines should be revised to recommend
authors include a statement indicating which RFC category the
I-D is intended to be published in.  This allows the reviewer
to apply determine a level of scrutity based upon the intended
category.

I've come a cross a number of WG I-Ds which did not indicate
their intended category AND the WG I-D didn't provide appropriate
clarification.  (Yes, I've brought this to the attention of
the WG chairs and I-D authors).

Comments?



From owner-ietf-outbound  Wed Feb  9 14:50:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA19954
	for ietf-outbound.10@ietf.org; Wed, 9 Feb 2000 14:50:02 -0500 (EST)
Received: from inetco.com (strauss.inetco.com [207.102.246.97])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19568
	for <ietf@ietf.org>; Wed, 9 Feb 2000 14:41:38 -0500 (EST)
Received: from dixon.inetco ([192.168.168.56]) by strauss.inetco.com with ESMTP id <115202>; Wed, 9 Feb 2000 11:41:59 -0800
Received: by dixon.inetco.com with Internet Mail Service (5.5.2448.0)
	id <CPY5ZMDH>; Wed, 9 Feb 2000 11:41:46 -0800
Message-ID: <88AD04D76428D3119EDA0080C8E3273F055F85@dixon.inetco.com>
From: Cameron Young <Cameron_Young@inetco.com>
To: ietf@ietf.org
Subject: RE: Intended category of I-Ds
Date:  Wed, 9 Feb 2000 11:41:35 -0800 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain; charset="iso-8859-1"
X-Loop: ietf@ietf.org

I agree.  A potentially incorrect target category  is
more useful during the review stage than no category 
at all.

As an editor of one ID, I struggled with the benefit of
listing a category, versus the concern that the mysterious 
IETF editors might throw it back for "non-conformance".

I've since gathered that there is considerable freedom
here, but I think some explicit comments or addition to
the template would make it a little easier for newbies 
like me.

Cameron Young
INETCO Systems Ltd.

-----Original Message-----
From: Kurt D. Zeilenga [mailto:Kurt@OpenLDAP.org]
Sent: Wednesday, February 09, 2000 10:33 AM
To: ietf@ietf.org
Subject: Intended category of I-Ds


I believe the I-D guidelines should be revised to recommend
authors include a statement indicating which RFC category the
I-D is intended to be published in.  This allows the reviewer
to apply determine a level of scrutity based upon the intended
category.

I've come a cross a number of WG I-Ds which did not indicate
their intended category AND the WG I-D didn't provide appropriate
clarification.  (Yes, I've brought this to the attention of
the WG chairs and I-D authors).

Comments?



From owner-ietf-outbound@ietf.org  Wed Feb  9 14:52:38 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20111
	for <ietf-web-archive@odin.ietf.org>; Wed, 9 Feb 2000 14:52:38 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA20725;
	Wed, 9 Feb 2000 14:50:43 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id OAA19954
	for ietf-outbound.10@ietf.org; Wed, 9 Feb 2000 14:50:02 -0500 (EST)
Received: from inetco.com (strauss.inetco.com [207.102.246.97])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19568
	for <ietf@ietf.org>; Wed, 9 Feb 2000 14:41:38 -0500 (EST)
Received: from dixon.inetco ([192.168.168.56]) by strauss.inetco.com with ESMTP id <115202>; Wed, 9 Feb 2000 11:41:59 -0800
Received: by dixon.inetco.com with Internet Mail Service (5.5.2448.0)
	id <CPY5ZMDH>; Wed, 9 Feb 2000 11:41:46 -0800
Message-ID: <88AD04D76428D3119EDA0080C8E3273F055F85@dixon.inetco.com>
From: Cameron Young <Cameron_Young@inetco.com>
To: ietf@ietf.org
Subject: RE: Intended category of I-Ds
Date:  Wed, 9 Feb 2000 11:41:35 -0800 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain; charset="iso-8859-1"
X-Loop: ietf@ietf.org

I agree.  A potentially incorrect target category  is
more useful during the review stage than no category 
at all.

As an editor of one ID, I struggled with the benefit of
listing a category, versus the concern that the mysterious 
IETF editors might throw it back for "non-conformance".

I've since gathered that there is considerable freedom
here, but I think some explicit comments or addition to
the template would make it a little easier for newbies 
like me.

Cameron Young
INETCO Systems Ltd.

-----Original Message-----
From: Kurt D. Zeilenga [mailto:Kurt@OpenLDAP.org]
Sent: Wednesday, February 09, 2000 10:33 AM
To: ietf@ietf.org
Subject: Intended category of I-Ds


I believe the I-D guidelines should be revised to recommend
authors include a statement indicating which RFC category the
I-D is intended to be published in.  This allows the reviewer
to apply determine a level of scrutity based upon the intended
category.

I've come a cross a number of WG I-Ds which did not indicate
their intended category AND the WG I-D didn't provide appropriate
clarification.  (Yes, I've brought this to the attention of
the WG chairs and I-D authors).

Comments?



From owner-ietf-outbound  Wed Feb  9 15:30:27 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA22295
	for ietf-outbound.10@ietf.org; Wed, 9 Feb 2000 15:30:03 -0500 (EST)
Received: from infidel.boolean.net (root@router.boolean.net [198.144.206.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21513
	for <ietf@ietf.org>; Wed, 9 Feb 2000 15:20:14 -0500 (EST)
Received: from gypsy (gypsy.boolean.net [198.144.202.243])
	by infidel.boolean.net (8.9.3/8.9.3) with SMTP id UAA04660
	for <ietf@ietf.org>; Wed, 9 Feb 2000 20:20:12 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <3.0.5.32.20000209122010.00971280@infidel.boolean.net>
X-Sender: guru@infidel.boolean.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Wed, 09 Feb 2000 12:20:10 -0800
To: ietf@ietf.org
From: "Kurt D. Zeilenga" <Kurt@OPENLDAP.ORG>
Subject: RE: Intended category of I-Ds
In-Reply-To: <88AD04D76428D3119EDA0080C8E3273F055F85@dixon.inetco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 11:41 AM 2/9/00 -0800, Cameron Young wrote:
>I've come a cross a number of WG I-Ds which did not indicate
>their intended category AND the WG I-D didn't provide appropriate
>clarification.  (Yes, I've brought this to the attention of
>the WG chairs and I-D authors).

I meant:

I've come a cross a number of WG I-Ds which did not indicate
their intended category AND the WG CHARTER didn't provide
appropriate clarification.



From owner-ietf-outbound@ietf.org  Wed Feb  9 15:34:17 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22544
	for <ietf-web-archive@odin.ietf.org>; Wed, 9 Feb 2000 15:34:17 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA22767;
	Wed, 9 Feb 2000 15:32:22 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id PAA22295
	for ietf-outbound.10@ietf.org; Wed, 9 Feb 2000 15:30:03 -0500 (EST)
Received: from infidel.boolean.net (root@router.boolean.net [198.144.206.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21513
	for <ietf@ietf.org>; Wed, 9 Feb 2000 15:20:14 -0500 (EST)
Received: from gypsy (gypsy.boolean.net [198.144.202.243])
	by infidel.boolean.net (8.9.3/8.9.3) with SMTP id UAA04660
	for <ietf@ietf.org>; Wed, 9 Feb 2000 20:20:12 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <3.0.5.32.20000209122010.00971280@infidel.boolean.net>
X-Sender: guru@infidel.boolean.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Wed, 09 Feb 2000 12:20:10 -0800
To: ietf@ietf.org
From: "Kurt D. Zeilenga" <Kurt@OPENLDAP.ORG>
Subject: RE: Intended category of I-Ds
In-Reply-To: <88AD04D76428D3119EDA0080C8E3273F055F85@dixon.inetco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 11:41 AM 2/9/00 -0800, Cameron Young wrote:
>I've come a cross a number of WG I-Ds which did not indicate
>their intended category AND the WG I-D didn't provide appropriate
>clarification.  (Yes, I've brought this to the attention of
>the WG chairs and I-D authors).

I meant:

I've come a cross a number of WG I-Ds which did not indicate
their intended category AND the WG CHARTER didn't provide
appropriate clarification.



From owner-ietf-outbound  Wed Feb  9 23:40:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA03403
	for ietf-outbound.10@ietf.org; Wed, 9 Feb 2000 23:40:03 -0500 (EST)
Received: from samar.sasi.com (sasi.com [164.164.56.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA03361
	for <ietf@ietf.org>; Wed, 9 Feb 2000 23:36:00 -0500 (EST)
Received: from samar (samar.sasi.com [164.164.56.2])
	by samar.sasi.com (8.9.3/8.9.3) with SMTP id KAA24535
	for <ietf@ietf.org>; Thu, 10 Feb 2000 10:06:56 +0530 (IST)
Received: from hpd11.sasi.com ([10.0.16.11]) by samar.sasi.com; Thu, 10 Feb 2000 10:06:54 +0000 (IST)
Received: from localhost (ramp@localhost)
	by hpd11.sasi.com (8.9.1/8.9.1) with ESMTP id KAA02838
	for <ietf@ietf.org>; Thu, 10 Feb 2000 10:12:02 +0530 (IST)
Date: Thu, 10 Feb 2000 10:12:02 +0530 (IST)
From: B G Ramprasad Torati <ramp@sasi.com>
To: "'IETF'" <ietf@ietf.org>
Subject: Regarding OSPF source code...!
In-Reply-To: <CE835E918749D21191B10060084C377E016D1E93@ismail1.icomverse.com>
Message-ID: <Pine.GHP.4.10.10002101006580.2830-100000@hpd11.sasi.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

Hi,

Can anybody help in finding out OSPF free source code. I heard that it is
available in the public domain over net. If anybody knows about the
internet site, please forward it to me.

Thank you,

Regards,
B G Ramprasad Torati
B.E(Hns.) Computer Science,
BITS,Pilani
INDIA-333031

E-mail: ramp@sasi.com



From owner-ietf-outbound@ietf.org  Wed Feb  9 23:42:13 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA03466
	for <ietf-web-archive@odin.ietf.org>; Wed, 9 Feb 2000 23:42:13 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA06692;
	Wed, 9 Feb 2000 23:40:14 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id XAA03403
	for ietf-outbound.10@ietf.org; Wed, 9 Feb 2000 23:40:03 -0500 (EST)
Received: from samar.sasi.com (sasi.com [164.164.56.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA03361
	for <ietf@ietf.org>; Wed, 9 Feb 2000 23:36:00 -0500 (EST)
Received: from samar (samar.sasi.com [164.164.56.2])
	by samar.sasi.com (8.9.3/8.9.3) with SMTP id KAA24535
	for <ietf@ietf.org>; Thu, 10 Feb 2000 10:06:56 +0530 (IST)
Received: from hpd11.sasi.com ([10.0.16.11]) by samar.sasi.com; Thu, 10 Feb 2000 10:06:54 +0000 (IST)
Received: from localhost (ramp@localhost)
	by hpd11.sasi.com (8.9.1/8.9.1) with ESMTP id KAA02838
	for <ietf@ietf.org>; Thu, 10 Feb 2000 10:12:02 +0530 (IST)
Date: Thu, 10 Feb 2000 10:12:02 +0530 (IST)
From: B G Ramprasad Torati <ramp@sasi.com>
To: "'IETF'" <ietf@ietf.org>
Subject: Regarding OSPF source code...!
In-Reply-To: <CE835E918749D21191B10060084C377E016D1E93@ismail1.icomverse.com>
Message-ID: <Pine.GHP.4.10.10002101006580.2830-100000@hpd11.sasi.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

Hi,

Can anybody help in finding out OSPF free source code. I heard that it is
available in the public domain over net. If anybody knows about the
internet site, please forward it to me.

Thank you,

Regards,
B G Ramprasad Torati
B.E(Hns.) Computer Science,
BITS,Pilani
INDIA-333031

E-mail: ramp@sasi.com



From owner-ietf-outbound  Thu Feb 10 08:20:50 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA22346
	for ietf-outbound.10@ietf.org; Thu, 10 Feb 2000 08:20:02 -0500 (EST)
Received: from localhost.localdomain ([207.8.144.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA21985
	for <ietf@ietf.org>; Thu, 10 Feb 2000 08:14:24 -0500 (EST)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id IAA05826
	for <ietf@ietf.org>; Thu, 10 Feb 2000 08:13:58 -0500
Sender: francis@localhost.localdomain
Message-ID: <38A2B994.945C52AA@ecal.com>
Date: Thu, 10 Feb 2000 08:13:56 -0500
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.2.12-20 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: "'IETF'" <ietf@ietf.org>
Subject: Re: Regarding OSPF source code...!
References: <Pine.GHP.4.10.10002101006580.2830-100000@hpd11.sasi.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

B G Ramprasad Torati wrote:

> Can anybody help in finding out OSPF free source code. I heard that it is
> available in the public domain over net.

It's supported in gated, which is included in RedHat Linux.
ftp://ftp.redhat.com

--
/================================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.  |
|Chief Scientist |===============================================|
|eCal Corp.      |"All gateways lose information. Some do it more|
|francis@ecal.com|efficiently than others." -- Einar Stefferud   |
\================================================================/





From owner-ietf-outbound@ietf.org  Thu Feb 10 08:22:20 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22516
	for <ietf-web-archive@odin.ietf.org>; Thu, 10 Feb 2000 08:22:20 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA24974;
	Thu, 10 Feb 2000 08:20:22 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id IAA22346
	for ietf-outbound.10@ietf.org; Thu, 10 Feb 2000 08:20:02 -0500 (EST)
Received: from localhost.localdomain ([207.8.144.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA21985
	for <ietf@ietf.org>; Thu, 10 Feb 2000 08:14:24 -0500 (EST)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id IAA05826
	for <ietf@ietf.org>; Thu, 10 Feb 2000 08:13:58 -0500
Sender: francis@localhost.localdomain
Message-ID: <38A2B994.945C52AA@ecal.com>
Date: Thu, 10 Feb 2000 08:13:56 -0500
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.2.12-20 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: "'IETF'" <ietf@ietf.org>
Subject: Re: Regarding OSPF source code...!
References: <Pine.GHP.4.10.10002101006580.2830-100000@hpd11.sasi.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

B G Ramprasad Torati wrote:

> Can anybody help in finding out OSPF free source code. I heard that it is
> available in the public domain over net.

It's supported in gated, which is included in RedHat Linux.
ftp://ftp.redhat.com

--
/================================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.  |
|Chief Scientist |===============================================|
|eCal Corp.      |"All gateways lose information. Some do it more|
|francis@ecal.com|efficiently than others." -- Einar Stefferud   |
\================================================================/





From owner-ietf-outbound  Thu Feb 10 12:21:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA04697
	for ietf-outbound.10@ietf.org; Thu, 10 Feb 2000 12:20:02 -0500 (EST)
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04472
	for <ietf@ietf.org>; Thu, 10 Feb 2000 12:14:00 -0500 (EST)
Received: from web1.merit.edu (web1.merit.edu [198.108.62.192])
	by segue.merit.edu (Postfix) with ESMTP
	id 57D6D5DF40; Thu, 10 Feb 2000 12:13:36 -0500 (EST)
Received: (from web@localhost)
	by web1.merit.edu (8.9.3/8.9.1) id MAA16124;
	Thu, 10 Feb 2000 12:13:36 -0500 (EST)
Date: Thu, 10 Feb 2000 12:13:35 -0500
From: William Bulley <web@merit.edu>
To: B G Ramprasad Torati <ramp@sasi.com>
Cc: ietf@ietf.org
Subject: Re: Regarding OSPF source code...!
Message-ID: <20000210121335.C15660@web1.merit.edu>
Mail-Followup-To: B G Ramprasad Torati <ramp@sasi.com>, ietf@ietf.org
References: <CE835E918749D21191B10060084C377E016D1E93@ismail1.icomverse.com> <Pine.GHP.4.10.10002101006580.2830-100000@hpd11.sasi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.6i
In-Reply-To: <Pine.GHP.4.10.10002101006580.2830-100000@hpd11.sasi.com>; from B G Ramprasad Torati on Thu, Feb 10, 2000 at 10:12:02AM +0530
X-Loop: ietf@ietf.org

According to B G Ramprasad Torati <ramp@sasi.com>:
> 
> Can anybody help in finding out OSPF free source code. I heard that it is
> available in the public domain over net. If anybody knows about the
> internet site, please forward it to me.

How about:

  http://www.gated.org

Regards,

web...

-- 
William Bulley                     Email: web@merit.edu
Merit Network Inc.                 Ann Arbor, Michigan



From owner-ietf-outbound@ietf.org  Thu Feb 10 12:23:11 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04811
	for <ietf-web-archive@odin.ietf.org>; Thu, 10 Feb 2000 12:23:10 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA01623;
	Thu, 10 Feb 2000 12:21:11 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id MAA04697
	for ietf-outbound.10@ietf.org; Thu, 10 Feb 2000 12:20:02 -0500 (EST)
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04472
	for <ietf@ietf.org>; Thu, 10 Feb 2000 12:14:00 -0500 (EST)
Received: from web1.merit.edu (web1.merit.edu [198.108.62.192])
	by segue.merit.edu (Postfix) with ESMTP
	id 57D6D5DF40; Thu, 10 Feb 2000 12:13:36 -0500 (EST)
Received: (from web@localhost)
	by web1.merit.edu (8.9.3/8.9.1) id MAA16124;
	Thu, 10 Feb 2000 12:13:36 -0500 (EST)
Date: Thu, 10 Feb 2000 12:13:35 -0500
From: William Bulley <web@merit.edu>
To: B G Ramprasad Torati <ramp@sasi.com>
Cc: ietf@ietf.org
Subject: Re: Regarding OSPF source code...!
Message-ID: <20000210121335.C15660@web1.merit.edu>
Mail-Followup-To: B G Ramprasad Torati <ramp@sasi.com>, ietf@ietf.org
References: <CE835E918749D21191B10060084C377E016D1E93@ismail1.icomverse.com> <Pine.GHP.4.10.10002101006580.2830-100000@hpd11.sasi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.6i
In-Reply-To: <Pine.GHP.4.10.10002101006580.2830-100000@hpd11.sasi.com>; from B G Ramprasad Torati on Thu, Feb 10, 2000 at 10:12:02AM +0530
X-Loop: ietf@ietf.org

According to B G Ramprasad Torati <ramp@sasi.com>:
> 
> Can anybody help in finding out OSPF free source code. I heard that it is
> available in the public domain over net. If anybody knows about the
> internet site, please forward it to me.

How about:

  http://www.gated.org

Regards,

web...

-- 
William Bulley                     Email: web@merit.edu
Merit Network Inc.                 Ann Arbor, Michigan



From owner-ietf-outbound  Thu Feb 10 21:12:59 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA14287
	for ietf-outbound.10@ietf.org; Thu, 10 Feb 2000 21:10:01 -0500 (EST)
Received: from kuji.off.connect.com.au (kuji.off.connect.com.au [203.63.69.33])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA14243
	for <IETF@ietf.org>; Thu, 10 Feb 2000 21:02:38 -0500 (EST)
Received: from connect.com.au (mrp@localhost) by kuji.off.connect.com.au with ESMTP id MAA09360
  (8.8.8/IDA-1.6); Fri, 11 Feb 2000 12:31:16 +1030 (CST)
Message-ID: <200002110201.MAA09360@kuji.off.connect.com.au>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
cc: Dave Crocker <dcrocker@brandenburg.com>, IETF@ietf.org
Subject: Re: IETF meeting wireless "standard"
In-reply-to: Your message of "Wed, 09 Feb 2000 09:23:19 CDT."
             <200002091423.JAA07600@tsx-prime.MIT.EDU>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <9358.950234475.1@connect.com.au>
Date: Fri, 11 Feb 2000 12:31:15 +1030
From: Mark Prior <mrp@connect.com.au>
X-Loop: ietf@ietf.org

     I'm definitely interested.  So do we have someone with a company
     connection who can get the IETF a good bulk discount on 801.11 DS cards?
     Especially the 11 megabit variant...  (Is Adelaide going to have 11 mbps
     support?)

The current plan is to have 802.11 DS 11Mbps support. I am still
working on the final details with two vendors (who are also interested
in doing an IETF special deal on the cards). If I can get appropriate
access points we wlll also have 802.11 FH support but that is of a
lesser priority for me at this stage.

As a local host I would certainly like to see the IETF say "the
wireless standard is x" (for one single value of x) as trying to pull
this together is tough enough as it is without having to source two
different types of wireless cards (luckily for me GSM uses 900MHz :-)

Mark.



From owner-ietf-outbound@ietf.org  Thu Feb 10 21:19:36 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA14394
	for <ietf-web-archive@odin.ietf.org>; Thu, 10 Feb 2000 21:19:36 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA22407;
	Thu, 10 Feb 2000 21:17:13 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id VAA14287
	for ietf-outbound.10@ietf.org; Thu, 10 Feb 2000 21:10:01 -0500 (EST)
Received: from kuji.off.connect.com.au (kuji.off.connect.com.au [203.63.69.33])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA14243
	for <IETF@ietf.org>; Thu, 10 Feb 2000 21:02:38 -0500 (EST)
Received: from connect.com.au (mrp@localhost) by kuji.off.connect.com.au with ESMTP id MAA09360
  (8.8.8/IDA-1.6); Fri, 11 Feb 2000 12:31:16 +1030 (CST)
Message-ID: <200002110201.MAA09360@kuji.off.connect.com.au>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
cc: Dave Crocker <dcrocker@brandenburg.com>, IETF@ietf.org
Subject: Re: IETF meeting wireless "standard"
In-reply-to: Your message of "Wed, 09 Feb 2000 09:23:19 CDT."
             <200002091423.JAA07600@tsx-prime.MIT.EDU>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <9358.950234475.1@connect.com.au>
Date: Fri, 11 Feb 2000 12:31:15 +1030
From: Mark Prior <mrp@connect.com.au>
X-Loop: ietf@ietf.org

     I'm definitely interested.  So do we have someone with a company
     connection who can get the IETF a good bulk discount on 801.11 DS cards?
     Especially the 11 megabit variant...  (Is Adelaide going to have 11 mbps
     support?)

The current plan is to have 802.11 DS 11Mbps support. I am still
working on the final details with two vendors (who are also interested
in doing an IETF special deal on the cards). If I can get appropriate
access points we wlll also have 802.11 FH support but that is of a
lesser priority for me at this stage.

As a local host I would certainly like to see the IETF say "the
wireless standard is x" (for one single value of x) as trying to pull
this together is tough enough as it is without having to source two
different types of wireless cards (luckily for me GSM uses 900MHz :-)

Mark.



From owner-ietf-outbound  Fri Feb 11 03:30:53 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA02464
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 03:30:02 -0500 (EST)
Received: from smtp7.atl.mindspring.net (smtp7.atl.mindspring.net [207.69.128.51])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02437
	for <ietf@ietf.org>; Fri, 11 Feb 2000 03:25:47 -0500 (EST)
Received: from ix.netcom.com (user-33qsdrq.dialup.mindspring.com [199.174.55.122])
	by smtp7.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id DAA16883;
	Fri, 11 Feb 2000 03:25:42 -0500 (EST)
Message-ID: <38A3E101.CD0D8662@ix.netcom.com>
Date: Fri, 11 Feb 2000 02:14:25 -0800
From: Jeff Williams <jwkckid1@ix.netcom.com>
Organization: INEGroup Spokesman
X-Mailer: Mozilla 4.08 [en] (Win95; U; 16bit)
MIME-Version: 1.0
To: david@AMINAL.COM
CC: DOMAIN-POLICY@LISTS.INTERNIC.NET, ietf@ietf.org,
        Roeland Meyer <rmeyer@mhsc.com>
Subject: Re: IAB Technical Comment on the Unique DNS Root
References: <Pine.LNX.4.20.0002102242510.28451-100000@proxy.pccf.net> <20000210231210.A23767@slurp.aminal.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

David and all,

  I agree completely David.  You might want to let the IETF know
this as they obviously don't or are now using the IETF drafting
process as a political forum...  But than again Donald Eastlake
(Draft in questions author) has always been of a single root
structure bent.

David Schutt wrote:

> This single root argument is getting a bit tired.
>
> Understandably, people are worried about name space collisions,
> they would prefer that there be only one com zone. A single root
> is probably the most convenient way to achieve that, but it's not
> the only one.
>
> I've been trying out some software that lets me pick and choose where
> I'll get name resolution for any particular domain, and it works just fine.
> I can mix and match any way I want, use the legacy root servers, add local
> TLD's, add public TLD's not referenced by the roots, or even specify name
> servers for all TLD's and not reference the roots at all.
>
> A single root is an administrative convenience, makes it easy for everyone
> to keep track of who is serving what TLD's. It's convenient enough that
> most people find it much easier to continue to reference the current roots.
> Elevating that to a technical necessity is stretching things a bit,
> though.
>
> Ultimately, anyone can make the decision to get their resolution service
> from a different .com TLD, and it would be difficult if not impossible to
> stop them.
>
> The question is, why would anybody want to?
>
> And if no one would want to, why make a big deal out of it?
>
> David Schutt
>
> On Thu, Feb 10, 2000 at 10:44:29PM -0500, !Dr. Joe Baptista wrote:
> > Looks like the IAB is a bit nervose these days.
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts directories.
> > This draft is a work item of the Internet Architecture Board Working Group of the IETF.
> >
> >         Title           : IAB Technical Comment on the Unique DNS Root
> >         Author(s)       : IAB
> >         Filename        : draft-ietf-iab-unique-dns-root-00.txt
> >         Pages           : 5
> >         Date            : 07-Feb-00
> >
> > To remain a global network, the Internet requires the existence of a
> > globally unique public name space.  The DNS name space is a
> > hierarchical name space derived from a single, globally unique root.
> > This is a technical constraint inherent in the design of the DNS
> > system.  Therefore it is not technically feasible for there to be
> > more than one root in the public DNS system.  That one root must be
> > supported by a small number of coordinated root servers, and
> > administered by a unique naming authority.
> > Put simply, deploying multiple public DNS roots would raise a very
> > strong possibility that users of different ISPs who click on the same
> > link on a web page could end up at different destinations, against
> > the will of the web page designers.
> > This does not preclude private networks from operating their own
> > private name spaces, but if they wish to make use of names uniquely
> > defined for the global Internet, they have to fetch that information
> > from the global DNS naming hierarchy, and in particular from the
> > coordinated root servers of the global DNS naming hierarchy.
> >
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-ietf-iab-unique-dns-root-00.txt

Regards,
--
Jeffrey A. Williams
Spokesman INEGroup (Over 95k members strong!)
CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng.
Information Network Eng. Group. INEG. INC.
E-Mail jwkckid1@ix.netcom.com
Contact Number:  972-447-1894
Address: 5 East Kirkwood Blvd. Grapevine Texas 75208




From owner-ietf-outbound@ietf.org  Fri Feb 11 03:35:27 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02592
	for <ietf-web-archive@odin.ietf.org>; Fri, 11 Feb 2000 03:35:27 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA09220;
	Fri, 11 Feb 2000 03:33:31 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id DAA02464
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 03:30:02 -0500 (EST)
Received: from smtp7.atl.mindspring.net (smtp7.atl.mindspring.net [207.69.128.51])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02437
	for <ietf@ietf.org>; Fri, 11 Feb 2000 03:25:47 -0500 (EST)
Received: from ix.netcom.com (user-33qsdrq.dialup.mindspring.com [199.174.55.122])
	by smtp7.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id DAA16883;
	Fri, 11 Feb 2000 03:25:42 -0500 (EST)
Message-ID: <38A3E101.CD0D8662@ix.netcom.com>
Date: Fri, 11 Feb 2000 02:14:25 -0800
From: Jeff Williams <jwkckid1@ix.netcom.com>
Organization: INEGroup Spokesman
X-Mailer: Mozilla 4.08 [en] (Win95; U; 16bit)
MIME-Version: 1.0
To: david@AMINAL.COM
CC: DOMAIN-POLICY@LISTS.INTERNIC.NET, ietf@ietf.org,
        Roeland Meyer <rmeyer@mhsc.com>
Subject: Re: IAB Technical Comment on the Unique DNS Root
References: <Pine.LNX.4.20.0002102242510.28451-100000@proxy.pccf.net> <20000210231210.A23767@slurp.aminal.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

David and all,

  I agree completely David.  You might want to let the IETF know
this as they obviously don't or are now using the IETF drafting
process as a political forum...  But than again Donald Eastlake
(Draft in questions author) has always been of a single root
structure bent.

David Schutt wrote:

> This single root argument is getting a bit tired.
>
> Understandably, people are worried about name space collisions,
> they would prefer that there be only one com zone. A single root
> is probably the most convenient way to achieve that, but it's not
> the only one.
>
> I've been trying out some software that lets me pick and choose where
> I'll get name resolution for any particular domain, and it works just fine.
> I can mix and match any way I want, use the legacy root servers, add local
> TLD's, add public TLD's not referenced by the roots, or even specify name
> servers for all TLD's and not reference the roots at all.
>
> A single root is an administrative convenience, makes it easy for everyone
> to keep track of who is serving what TLD's. It's convenient enough that
> most people find it much easier to continue to reference the current roots.
> Elevating that to a technical necessity is stretching things a bit,
> though.
>
> Ultimately, anyone can make the decision to get their resolution service
> from a different .com TLD, and it would be difficult if not impossible to
> stop them.
>
> The question is, why would anybody want to?
>
> And if no one would want to, why make a big deal out of it?
>
> David Schutt
>
> On Thu, Feb 10, 2000 at 10:44:29PM -0500, !Dr. Joe Baptista wrote:
> > Looks like the IAB is a bit nervose these days.
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts directories.
> > This draft is a work item of the Internet Architecture Board Working Group of the IETF.
> >
> >         Title           : IAB Technical Comment on the Unique DNS Root
> >         Author(s)       : IAB
> >         Filename        : draft-ietf-iab-unique-dns-root-00.txt
> >         Pages           : 5
> >         Date            : 07-Feb-00
> >
> > To remain a global network, the Internet requires the existence of a
> > globally unique public name space.  The DNS name space is a
> > hierarchical name space derived from a single, globally unique root.
> > This is a technical constraint inherent in the design of the DNS
> > system.  Therefore it is not technically feasible for there to be
> > more than one root in the public DNS system.  That one root must be
> > supported by a small number of coordinated root servers, and
> > administered by a unique naming authority.
> > Put simply, deploying multiple public DNS roots would raise a very
> > strong possibility that users of different ISPs who click on the same
> > link on a web page could end up at different destinations, against
> > the will of the web page designers.
> > This does not preclude private networks from operating their own
> > private name spaces, but if they wish to make use of names uniquely
> > defined for the global Internet, they have to fetch that information
> > from the global DNS naming hierarchy, and in particular from the
> > coordinated root servers of the global DNS naming hierarchy.
> >
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-ietf-iab-unique-dns-root-00.txt

Regards,
--
Jeffrey A. Williams
Spokesman INEGroup (Over 95k members strong!)
CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng.
Information Network Eng. Group. INEG. INC.
E-Mail jwkckid1@ix.netcom.com
Contact Number:  972-447-1894
Address: 5 East Kirkwood Blvd. Grapevine Texas 75208




From owner-ietf-outbound  Fri Feb 11 09:04:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA08747
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 09:00:02 -0500 (EST)
Received: from postfix1.free.fr (postfix@postfix1.free.fr [212.27.32.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08698
	for <ietf@ietf.org>; Fri, 11 Feb 2000 08:58:43 -0500 (EST)
From: jordan@free.fr
Received: from imp.free.fr (imp.free.fr [212.27.32.34])
	by postfix1.free.fr (Postfix) with ESMTP id 0975728DE7
	for <ietf@ietf.org>; Fri, 11 Feb 2000 14:58:36 +0100 (MET)
Received: (from www-data@localhost)
	by imp.free.fr (8.9.3/8.9.3/Debian 8.9.3-6) id KAA06931
	for ietf@ietf.org; Fri, 11 Feb 2000 10:08:13 +0100
Message-ID: <950260093.38a3d17d2412f@imp.free.fr>
Date: Fri, 11 Feb 2000 10:08:13 +0100
To: ietf@ietf.org
Subject: Anycast details...
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 8bit
User-Agent: IMP/PHP IMAP webmail program 2.2.0
X-Originating-IP: 155.69.4.53
Content-Transfer-Encoding: 8bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

Hi,

I am currently trying to understand Anycast and i figured out that very liitle
information is available on this subject. Only a few RFCs and drafts.
Are there any concrete experiences on Anycast ?
Thank you.

Regards,
Alexis Jordan.



From owner-ietf-outbound@ietf.org  Fri Feb 11 09:09:54 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09228
	for <ietf-web-archive@odin.ietf.org>; Fri, 11 Feb 2000 09:09:54 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA17889;
	Fri, 11 Feb 2000 09:07:51 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id JAA08747
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 09:00:02 -0500 (EST)
Received: from postfix1.free.fr (postfix@postfix1.free.fr [212.27.32.21])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08698
	for <ietf@ietf.org>; Fri, 11 Feb 2000 08:58:43 -0500 (EST)
From: jordan@free.fr
Received: from imp.free.fr (imp.free.fr [212.27.32.34])
	by postfix1.free.fr (Postfix) with ESMTP id 0975728DE7
	for <ietf@ietf.org>; Fri, 11 Feb 2000 14:58:36 +0100 (MET)
Received: (from www-data@localhost)
	by imp.free.fr (8.9.3/8.9.3/Debian 8.9.3-6) id KAA06931
	for ietf@ietf.org; Fri, 11 Feb 2000 10:08:13 +0100
Message-ID: <950260093.38a3d17d2412f@imp.free.fr>
Date: Fri, 11 Feb 2000 10:08:13 +0100
To: ietf@ietf.org
Subject: Anycast details...
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 8bit
User-Agent: IMP/PHP IMAP webmail program 2.2.0
X-Originating-IP: 155.69.4.53
Content-Transfer-Encoding: 8bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hi,

I am currently trying to understand Anycast and i figured out that very liitle
information is available on this subject. Only a few RFCs and drafts.
Are there any concrete experiences on Anycast ?
Thank you.

Regards,
Alexis Jordan.



From owner-ietf-outbound  Fri Feb 11 11:33:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA13361
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 11:30:02 -0500 (EST)
Received: from prue.eim.surrey.ac.uk (IDENT:exim@prue.eim.surrey.ac.uk [131.227.76.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13205
	for <ietf@ietf.org>; Fri, 11 Feb 2000 11:24:20 -0500 (EST)
Received: from petra.ee.surrey.ac.uk ([131.227.88.13] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.03 #1)
	id 12JIrR-0000Qa-00; Fri, 11 Feb 2000 16:24:01 +0000
Date: Fri, 11 Feb 2000 16:23:52 +0000 (GMT)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-Sender: eep1lw@petra.ee.surrey.ac.uk
Reply-To: L.Wood@eim.surrey.ac.uk
To: jordan@free.fr
cc: ietf@ietf.org
Subject: Re: Anycast details...
In-Reply-To: <950260093.38a3d17d2412f@imp.free.fr>
Message-ID: <Pine.SOL.4.10.10002111615440.26570-100000@petra.ee.surrey.ac.uk>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Fri, 11 Feb 2000 jordan@free.fr wrote:

> I am currently trying to understand Anycast and i figured out that very liitle
> information is available on this subject. Only a few RFCs and drafts.

One paper I'm aware of touching on routing implications of anycast is:

Weijia Jia, Dong Xuan, Wei Zhao, "Integrated Routing Algorithms for
Aycast Messages", IEEE Communications Magazine, January 2000, pp
48-53.

also http://www.cs.tamu.edu/faculty/zhao/cv.html#PUBLICATIONS
has for download:

W. Jia and Wei Zhao, Integrated Routing Algorithms for Anycast
Messages, in Proc. of  IEEE Global Telecommunications Conference
(Globecom), Volume: 3, 1998, pp. 1635-1640.

D. Xuan, W. Jia, and Wei Zhao, Routing Algorithms for Anycast
Messages, in Proc. of International Conference on Parallel Processing,
Aug. 1998, pp. 122-130. 

L.

> Are there any concrete experiences on Anycast ?
> Thank you.
> 
> Regards,
> Alexis Jordan.

<L.Wood@surrey.ac.uk>PGP<http://www.ee.surrey.ac.uk/Personal/L.Wood/>




From owner-ietf-outbound@ietf.org  Fri Feb 11 11:39:09 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13718
	for <ietf-web-archive@odin.ietf.org>; Fri, 11 Feb 2000 11:39:08 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA21919;
	Fri, 11 Feb 2000 11:37:10 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id LAA13361
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 11:30:02 -0500 (EST)
Received: from prue.eim.surrey.ac.uk (IDENT:exim@prue.eim.surrey.ac.uk [131.227.76.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13205
	for <ietf@ietf.org>; Fri, 11 Feb 2000 11:24:20 -0500 (EST)
Received: from petra.ee.surrey.ac.uk ([131.227.88.13] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.03 #1)
	id 12JIrR-0000Qa-00; Fri, 11 Feb 2000 16:24:01 +0000
Date: Fri, 11 Feb 2000 16:23:52 +0000 (GMT)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-Sender: eep1lw@petra.ee.surrey.ac.uk
Reply-To: L.Wood@eim.surrey.ac.uk
To: jordan@free.fr
cc: ietf@ietf.org
Subject: Re: Anycast details...
In-Reply-To: <950260093.38a3d17d2412f@imp.free.fr>
Message-ID: <Pine.SOL.4.10.10002111615440.26570-100000@petra.ee.surrey.ac.uk>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Fri, 11 Feb 2000 jordan@free.fr wrote:

> I am currently trying to understand Anycast and i figured out that very liitle
> information is available on this subject. Only a few RFCs and drafts.

One paper I'm aware of touching on routing implications of anycast is:

Weijia Jia, Dong Xuan, Wei Zhao, "Integrated Routing Algorithms for
Aycast Messages", IEEE Communications Magazine, January 2000, pp
48-53.

also http://www.cs.tamu.edu/faculty/zhao/cv.html#PUBLICATIONS
has for download:

W. Jia and Wei Zhao, Integrated Routing Algorithms for Anycast
Messages, in Proc. of  IEEE Global Telecommunications Conference
(Globecom), Volume: 3, 1998, pp. 1635-1640.

D. Xuan, W. Jia, and Wei Zhao, Routing Algorithms for Anycast
Messages, in Proc. of International Conference on Parallel Processing,
Aug. 1998, pp. 122-130. 

L.

> Are there any concrete experiences on Anycast ?
> Thank you.
> 
> Regards,
> Alexis Jordan.

<L.Wood@surrey.ac.uk>PGP<http://www.ee.surrey.ac.uk/Personal/L.Wood/>




From owner-ietf-outbound  Fri Feb 11 12:42:33 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA15601
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 12:40:02 -0500 (EST)
Received: from ib.rc.vix.com (ib.rc.vix.com [204.152.187.22])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15397
	for <ietf@ietf.org>; Fri, 11 Feb 2000 12:33:25 -0500 (EST)
Received: from bb.rc.vix.com (bb.rc.vix.com [204.152.187.11]) 
	by ib.rc.vix.com (8.9.1/8.9.1) via ESMTP id JAA26253; Fri, 11 Feb 2000 09:32:18 -0800 (PST)
	env-from (April.Marine@nominum.com)
Received: from localhost (amarine@localhost) 
	by bb.rc.vix.com (8.9.1/8.9.1) via ESMTP id JAA21103; Fri, 11 Feb 2000 09:32:18 -0800 (PST)
	env-from (April.Marine@nominum.com)
Date: Fri, 11 Feb 2000 09:32:18 -0800 (PST)
From: April Marine <April.Marine@nominum.com>
To: ietf@ietf.org, namedroppers@ops.ietf.org, bind-users@isc.org
Subject: Latest Internet Domain Survey/ Host Count
Message-ID: <Pine.BSI.4.21.0002110931130.10134-100000@bb.rc.vix.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

Data from the January 2000 Internet Domain Survey is now available
from the Internet Software Consortium's web site at
http://www.isc.org/ds/.  The latest count shows more than 72 million
hosts, an increase from 56 million 6 months ago.  The Internet Domain
Survey is the longest running count of Internet growth, dating back to
1987.  The Survey is a joint effort of Network Wizards and the
Internet Software Consortium, with operational support provided by
Nominum, Inc.

fyi,
April

-------------------------------------------------------------------------
April Marine				
Director of Operations				april.marine@nominum.com
Nominum, Inc.					+1.650.779.6006



From owner-ietf-outbound@ietf.org  Fri Feb 11 12:49:06 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15778
	for <ietf-web-archive@odin.ietf.org>; Fri, 11 Feb 2000 12:49:06 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA23991;
	Fri, 11 Feb 2000 12:47:03 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id MAA15601
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 12:40:02 -0500 (EST)
Received: from ib.rc.vix.com (ib.rc.vix.com [204.152.187.22])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15397
	for <ietf@ietf.org>; Fri, 11 Feb 2000 12:33:25 -0500 (EST)
Received: from bb.rc.vix.com (bb.rc.vix.com [204.152.187.11]) 
	by ib.rc.vix.com (8.9.1/8.9.1) via ESMTP id JAA26253; Fri, 11 Feb 2000 09:32:18 -0800 (PST)
	env-from (April.Marine@nominum.com)
Received: from localhost (amarine@localhost) 
	by bb.rc.vix.com (8.9.1/8.9.1) via ESMTP id JAA21103; Fri, 11 Feb 2000 09:32:18 -0800 (PST)
	env-from (April.Marine@nominum.com)
Date: Fri, 11 Feb 2000 09:32:18 -0800 (PST)
From: April Marine <April.Marine@nominum.com>
To: ietf@ietf.org, namedroppers@ops.ietf.org, bind-users@isc.org
Subject: Latest Internet Domain Survey/ Host Count
Message-ID: <Pine.BSI.4.21.0002110931130.10134-100000@bb.rc.vix.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

Data from the January 2000 Internet Domain Survey is now available
from the Internet Software Consortium's web site at
http://www.isc.org/ds/.  The latest count shows more than 72 million
hosts, an increase from 56 million 6 months ago.  The Internet Domain
Survey is the longest running count of Internet growth, dating back to
1987.  The Survey is a joint effort of Network Wizards and the
Internet Software Consortium, with operational support provided by
Nominum, Inc.

fyi,
April

-------------------------------------------------------------------------
April Marine				
Director of Operations				april.marine@nominum.com
Nominum, Inc.					+1.650.779.6006



From owner-ietf-outbound  Fri Feb 11 13:30:49 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA16636
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 13:30:01 -0500 (EST)
Received: from smtp.jet.es (smtp.jet.es [194.179.100.25])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16584
	for <ietf@ietf.org>; Fri, 11 Feb 2000 13:27:15 -0500 (EST)
Received: from jet.es (infon6.jet.es [195.55.156.6])
	by smtp.jet.es (8.9.3/8.9.1) with ESMTP id TAA00807
	for <ietf@ietf.org>; Fri, 11 Feb 2000 19:26:45 +0100 (MET)
X-Envelope-To: <ietf@ietf.org>
Message-ID: <38A4B59C.80F669EE@jet.es>
Date: Fri, 11 Feb 2000 19:21:32 -0600
From: Julio =?iso-8859-1?Q?C=E9sar?= Serrano Ortuno <julk@jet.es>
X-Mailer: Mozilla 4.5 [es] (Win98; I)
X-Accept-Language: es
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: VM packaging
References: <CE835E918749D21191B10060084C377E016D1E96@ismail1.icomverse.com>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id NAA16584
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

"Gazal, Elly" escribió:
> 
> Can anyone explain what is "VoiceMail Packaging"???
> 
> Regards,
> 
> Elly Gazal
> System Engineer


I supose that is a compressed format of mail contents same as MIME (last
without compression). This package format must provide the posibility of
sending voice withing SMTP. However, it's needs a special software to
get packed data into real voice (sounds).

Don't espect too much. I hasn't experience with voicemail. But I ever
belive that.

Thanks for reading it. (And sorry for my english)

Julio Serrano



From owner-ietf-outbound@ietf.org  Fri Feb 11 13:36:46 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16906
	for <ietf-web-archive@odin.ietf.org>; Fri, 11 Feb 2000 13:36:46 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA25068;
	Fri, 11 Feb 2000 13:34:46 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id NAA16636
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 13:30:01 -0500 (EST)
Received: from smtp.jet.es (smtp.jet.es [194.179.100.25])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16584
	for <ietf@ietf.org>; Fri, 11 Feb 2000 13:27:15 -0500 (EST)
Received: from jet.es (infon6.jet.es [195.55.156.6])
	by smtp.jet.es (8.9.3/8.9.1) with ESMTP id TAA00807
	for <ietf@ietf.org>; Fri, 11 Feb 2000 19:26:45 +0100 (MET)
X-Envelope-To: <ietf@ietf.org>
Message-ID: <38A4B59C.80F669EE@jet.es>
Date: Fri, 11 Feb 2000 19:21:32 -0600
From: Julio =?iso-8859-1?Q?C=E9sar?= Serrano Ortuno <julk@jet.es>
X-Mailer: Mozilla 4.5 [es] (Win98; I)
X-Accept-Language: es
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: VM packaging
References: <CE835E918749D21191B10060084C377E016D1E96@ismail1.icomverse.com>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id NAA16584
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

"Gazal, Elly" escribió:
> 
> Can anyone explain what is "VoiceMail Packaging"???
> 
> Regards,
> 
> Elly Gazal
> System Engineer


I supose that is a compressed format of mail contents same as MIME (last
without compression). This package format must provide the posibility of
sending voice withing SMTP. However, it's needs a special software to
get packed data into real voice (sounds).

Don't espect too much. I hasn't experience with voicemail. But I ever
belive that.

Thanks for reading it. (And sorry for my english)

Julio Serrano



From owner-ietf-outbound  Fri Feb 11 14:51:32 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA18242
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 14:50:02 -0500 (EST)
Received: from alcor.process.com (alcor.process.com [192.42.95.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18090
	for <IETF@IETF.ORG>; Fri, 11 Feb 2000 14:40:50 -0500 (EST)
Received: by process.com (MX V5.1-X A2w8g) id 198;
          Fri, 11 Feb 2000 14:40:16 -0500
Sender: volz@process.com
Date: Fri, 11 Feb 2000 14:40:15 -0500
From: Bernie Volz <volz@process.com>
To: IETF@ietf.org
Message-ID: <009E5826.5FC1D447.198@process.com>
Subject: Internet SYN Flooding, spoofing attacks
X-Loop: ietf@ietf.org

Regarding the recent TCP SYN Flooding attacks, why aren't ALL ISPs
required to put filtering on their networks that PREVENTS packets with
invalid source addresses ever entering their infrastructure? If every
site connected to the Internet did this, spoofing would be much more
difficult because you couldn't do it. Sure, you could spoof an address
from YOUR network, but that's all. And guess what, it would be much
easier to track and thus to shut down the intrusions should they occur.

Thus ever edge router should have filter lists that prevent it
forwarding traffic out to the Internet (ISPs network) any packet that
does not have a source address that is valid from that site.

I would hope that lots of ISPs already do this. But, perhaps not.

- Bernie Volz
  Process Software



From owner-ietf-outbound@ietf.org  Fri Feb 11 14:57:20 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18389
	for <ietf-web-archive@odin.ietf.org>; Fri, 11 Feb 2000 14:57:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA27031;
	Fri, 11 Feb 2000 14:55:21 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id OAA18242
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 14:50:02 -0500 (EST)
Received: from alcor.process.com (alcor.process.com [192.42.95.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18090
	for <IETF@IETF.ORG>; Fri, 11 Feb 2000 14:40:50 -0500 (EST)
Received: by process.com (MX V5.1-X A2w8g) id 198;
          Fri, 11 Feb 2000 14:40:16 -0500
Sender: volz@process.com
Date: Fri, 11 Feb 2000 14:40:15 -0500
From: Bernie Volz <volz@process.com>
To: IETF@ietf.org
Message-ID: <009E5826.5FC1D447.198@process.com>
Subject: Internet SYN Flooding, spoofing attacks
X-Loop: ietf@ietf.org

Regarding the recent TCP SYN Flooding attacks, why aren't ALL ISPs
required to put filtering on their networks that PREVENTS packets with
invalid source addresses ever entering their infrastructure? If every
site connected to the Internet did this, spoofing would be much more
difficult because you couldn't do it. Sure, you could spoof an address
from YOUR network, but that's all. And guess what, it would be much
easier to track and thus to shut down the intrusions should they occur.

Thus ever edge router should have filter lists that prevent it
forwarding traffic out to the Internet (ISPs network) any packet that
does not have a source address that is valid from that site.

I would hope that lots of ISPs already do this. But, perhaps not.

- Bernie Volz
  Process Software



From owner-ietf-outbound  Fri Feb 11 15:00:27 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA18470
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 15:00:02 -0500 (EST)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18402
	for <IETF@ietf.org>; Fri, 11 Feb 2000 14:57:35 -0500 (EST)
Received: from randy by rip.psg.com with local (Exim 3.13 #1)
	id 12JMC2-000AGH-00; Fri, 11 Feb 2000 11:57:30 -0800
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Bernie Volz <volz@PROCESS.COM>
Cc: IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
References: <009E5826.5FC1D447.198@process.com>
Message-Id: <E12JMC2-000AGH-00@rip.psg.com>
Date: Fri, 11 Feb 2000 11:57:30 -0800
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

> Regarding the recent TCP SYN Flooding attacks, why aren't ALL ISPs
> required to put filtering on their networks that PREVENTS packets with
> invalid source addresses ever entering their infrastructure?

maybe you want to be reading the nanog mailing list, nanog@merit.edu, where
the problems with and tactics for this and other approaches are discussed.

randy



From owner-ietf-outbound@ietf.org  Fri Feb 11 15:04:14 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18677
	for <ietf-web-archive@odin.ietf.org>; Fri, 11 Feb 2000 15:04:13 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA27250;
	Fri, 11 Feb 2000 15:02:14 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id PAA18470
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 15:00:02 -0500 (EST)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18402
	for <IETF@ietf.org>; Fri, 11 Feb 2000 14:57:35 -0500 (EST)
Received: from randy by rip.psg.com with local (Exim 3.13 #1)
	id 12JMC2-000AGH-00; Fri, 11 Feb 2000 11:57:30 -0800
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Bernie Volz <volz@PROCESS.COM>
Cc: IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
References: <009E5826.5FC1D447.198@process.com>
Message-Id: <E12JMC2-000AGH-00@rip.psg.com>
Date: Fri, 11 Feb 2000 11:57:30 -0800
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> Regarding the recent TCP SYN Flooding attacks, why aren't ALL ISPs
> required to put filtering on their networks that PREVENTS packets with
> invalid source addresses ever entering their infrastructure?

maybe you want to be reading the nanog mailing list, nanog@merit.edu, where
the problems with and tactics for this and other approaches are discussed.

randy



From owner-ietf-outbound  Fri Feb 11 15:20:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA18980
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 15:20:02 -0500 (EST)
Received: from mailman.cisco.com (mailman.cisco.com [171.68.225.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18870
	for <IETF@ietf.org>; Fri, 11 Feb 2000 15:16:32 -0500 (EST)
Received: from bigger-dawgs (pferguso-isdn.cisco.com [171.70.114.134]) by mailman.cisco.com (8.8.8+Sun/CISCO.SERVER.1.2) with ESMTP id MAA01118; Fri, 11 Feb 2000 12:15:10 -0800 (PST)
Message-Id: <4.2.2.20000211151342.00a36e60@lint.cisco.com>
X-Sender: pferguso@lint.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Fri, 11 Feb 2000 15:15:07 -0500
To: Bernie Volz <volz@process.com>
From: Paul Ferguson <ferguson@cisco.com>
Subject: Re: Internet SYN Flooding, spoofing attacks
Cc: IETF@ietf.org
In-Reply-To: <009E5826.5FC1D447.198@process.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 02:40 PM 02/11/2000 -0500, Bernie Volz wrote:

>Regarding the recent TCP SYN Flooding attacks, why aren't ALL ISPs
>required to put filtering on their networks that PREVENTS packets with
>invalid source addresses ever entering their infrastructure?

Because there is no "Internet Police", that's why.


>If every
>site connected to the Internet did this, spoofing would be much more
>difficult because you couldn't do it. Sure, you could spoof an address
>from YOUR network, but that's all. And guess what, it would be much
>easier to track and thus to shut down the intrusions should they occur.

Yes, this practice is documented in RFC2267.


>Thus ever edge router should have filter lists that prevent it
>forwarding traffic out to the Internet (ISPs network) any packet that
>does not have a source address that is valid from that site.
>
>I would hope that lots of ISPs already do this. But, perhaps not.

I would hope so, too, but apparently many do not.

Thus, the problem at hand.

- paul


>- Bernie Volz
>   Process Software



From owner-ietf-outbound@ietf.org  Fri Feb 11 15:22:41 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19053
	for <ietf-web-archive@odin.ietf.org>; Fri, 11 Feb 2000 15:22:41 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA27546;
	Fri, 11 Feb 2000 15:20:42 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id PAA18980
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 15:20:02 -0500 (EST)
Received: from mailman.cisco.com (mailman.cisco.com [171.68.225.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18870
	for <IETF@ietf.org>; Fri, 11 Feb 2000 15:16:32 -0500 (EST)
Received: from bigger-dawgs (pferguso-isdn.cisco.com [171.70.114.134]) by mailman.cisco.com (8.8.8+Sun/CISCO.SERVER.1.2) with ESMTP id MAA01118; Fri, 11 Feb 2000 12:15:10 -0800 (PST)
Message-Id: <4.2.2.20000211151342.00a36e60@lint.cisco.com>
X-Sender: pferguso@lint.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Fri, 11 Feb 2000 15:15:07 -0500
To: Bernie Volz <volz@process.com>
From: Paul Ferguson <ferguson@cisco.com>
Subject: Re: Internet SYN Flooding, spoofing attacks
Cc: IETF@ietf.org
In-Reply-To: <009E5826.5FC1D447.198@process.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 02:40 PM 02/11/2000 -0500, Bernie Volz wrote:

>Regarding the recent TCP SYN Flooding attacks, why aren't ALL ISPs
>required to put filtering on their networks that PREVENTS packets with
>invalid source addresses ever entering their infrastructure?

Because there is no "Internet Police", that's why.


>If every
>site connected to the Internet did this, spoofing would be much more
>difficult because you couldn't do it. Sure, you could spoof an address
>from YOUR network, but that's all. And guess what, it would be much
>easier to track and thus to shut down the intrusions should they occur.

Yes, this practice is documented in RFC2267.


>Thus ever edge router should have filter lists that prevent it
>forwarding traffic out to the Internet (ISPs network) any packet that
>does not have a source address that is valid from that site.
>
>I would hope that lots of ISPs already do this. But, perhaps not.

I would hope so, too, but apparently many do not.

Thus, the problem at hand.

- paul


>- Bernie Volz
>   Process Software



From owner-ietf-outbound  Fri Feb 11 15:30:26 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA19192
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 15:30:02 -0500 (EST)
Received: from mailman.cisco.com (mailman.cisco.com [171.68.225.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19168
	for <ietf@ietf.org>; Fri, 11 Feb 2000 15:29:44 -0500 (EST)
Received: from bigger-dawgs (pferguso-isdn.cisco.com [171.70.114.134]) by mailman.cisco.com (8.8.8+Sun/CISCO.SERVER.1.2) with ESMTP id MAA05639 for <ietf@ietf.org>; Fri, 11 Feb 2000 12:29:12 -0800 (PST)
Message-Id: <4.2.2.20000211152745.00a548f0@lint.cisco.com>
X-Sender: pferguso@lint.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Fri, 11 Feb 2000 15:29:08 -0500
To: ietf@ietf.org
From: Paul Ferguson <ferguson@cisco.com>
Subject: Re: Internet SYN Flooding, spoofing attacks
In-Reply-To: <E12JMC2-000AGH-00@rip.psg.com>
References: <009E5826.5FC1D447.198@process.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 11:57 AM 02/11/2000 -0800, Randy Bush wrote:

> > Regarding the recent TCP SYN Flooding attacks, why aren't ALL ISPs
> > required to put filtering on their networks that PREVENTS packets with
> > invalid source addresses ever entering their infrastructure?
>
>maybe you want to be reading the nanog mailing list, nanog@merit.edu, where
>the problems with and tactics for this and other approaches are discussed.

Let's point folks to:

  http://www.nanog.org/mailinglist.html

instead.

The last thing I want to see on the NANOG list is a bunch of
"subscribe me" messages.

- paul



From owner-ietf-outbound@ietf.org  Fri Feb 11 15:35:06 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19475
	for <ietf-web-archive@odin.ietf.org>; Fri, 11 Feb 2000 15:35:06 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA27869;
	Fri, 11 Feb 2000 15:33:05 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id PAA19192
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 15:30:02 -0500 (EST)
Received: from mailman.cisco.com (mailman.cisco.com [171.68.225.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19168
	for <ietf@ietf.org>; Fri, 11 Feb 2000 15:29:44 -0500 (EST)
Received: from bigger-dawgs (pferguso-isdn.cisco.com [171.70.114.134]) by mailman.cisco.com (8.8.8+Sun/CISCO.SERVER.1.2) with ESMTP id MAA05639 for <ietf@ietf.org>; Fri, 11 Feb 2000 12:29:12 -0800 (PST)
Message-Id: <4.2.2.20000211152745.00a548f0@lint.cisco.com>
X-Sender: pferguso@lint.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Fri, 11 Feb 2000 15:29:08 -0500
To: ietf@ietf.org
From: Paul Ferguson <ferguson@cisco.com>
Subject: Re: Internet SYN Flooding, spoofing attacks
In-Reply-To: <E12JMC2-000AGH-00@rip.psg.com>
References: <009E5826.5FC1D447.198@process.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 11:57 AM 02/11/2000 -0800, Randy Bush wrote:

> > Regarding the recent TCP SYN Flooding attacks, why aren't ALL ISPs
> > required to put filtering on their networks that PREVENTS packets with
> > invalid source addresses ever entering their infrastructure?
>
>maybe you want to be reading the nanog mailing list, nanog@merit.edu, where
>the problems with and tactics for this and other approaches are discussed.

Let's point folks to:

  http://www.nanog.org/mailinglist.html

instead.

The last thing I want to see on the NANOG list is a bunch of
"subscribe me" messages.

- paul



From owner-ietf-outbound  Fri Feb 11 15:40:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA19591
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 15:40:02 -0500 (EST)
Received: from black-ice.cc.vt.edu (black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19405
	for <IETF@ietf.org>; Fri, 11 Feb 2000 15:33:23 -0500 (EST)
Received: from black-ice.cc.vt.edu (LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.0.Beta13/8.10.0.Beta13) with ESMTP id e1BKXC917344;
	Fri, 11 Feb 2000 15:33:13 -0500
Message-Id: <200002112033.e1BKXC917344@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Bernie Volz <volz@process.com>
cc: IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks 
In-reply-to: Your message of "Fri, 11 Feb 2000 14:40:15 EST."
             <009E5826.5FC1D447.198@process.com> 
From: Valdis.Kletnieks@vt.edu
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <009E5826.5FC1D447.198@process.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 11 Feb 2000 15:33:12 -0500
X-Loop: ietf@ietf.org

On Fri, 11 Feb 2000 14:40:15 EST, Bernie Volz <volz@process.com>  said:
> Regarding the recent TCP SYN Flooding attacks, why aren't ALL ISPs
> required to put filtering on their networks that PREVENTS packets with
> invalid source addresses ever entering their infrastructure? If every
> site connected to the Internet did this, spoofing would be much more

See RFC2267.

The problem is that the IETF doesn't have the legal authority to beat ISP's
into submission on this one.  There's also the problem that many ISP's are
somewhat marginal in cluefulness, so things like RFC2267 tend to be of the
"preaching to the choir" variety.

Given that RFC2267 is over 2 years old now, what *do* you suggest the network
community at large do to motivate the sites that still haven't implemented it?

Would somebody be interested in running a BGP blackhole feed of prefixes
known not to be filtering, similar to the maps.vix.com feed for closing
off E-mail spam?  Perhaps if that became prevalent, ISPs would cleanup their
act when their legitimate users couldn't get anyplace because their ISP
wasn't filtering.

<As he dons his asbestos underwear> ;)


-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound@ietf.org  Fri Feb 11 15:45:27 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19796
	for <ietf-web-archive@odin.ietf.org>; Fri, 11 Feb 2000 15:45:27 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA28035;
	Fri, 11 Feb 2000 15:43:27 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id PAA19591
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 15:40:02 -0500 (EST)
Received: from black-ice.cc.vt.edu (black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19405
	for <IETF@ietf.org>; Fri, 11 Feb 2000 15:33:23 -0500 (EST)
Received: from black-ice.cc.vt.edu (LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.0.Beta13/8.10.0.Beta13) with ESMTP id e1BKXC917344;
	Fri, 11 Feb 2000 15:33:13 -0500
Message-Id: <200002112033.e1BKXC917344@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Bernie Volz <volz@process.com>
cc: IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks 
In-reply-to: Your message of "Fri, 11 Feb 2000 14:40:15 EST."
             <009E5826.5FC1D447.198@process.com> 
From: Valdis.Kletnieks@vt.edu
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <009E5826.5FC1D447.198@process.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 11 Feb 2000 15:33:12 -0500
X-Loop: ietf@ietf.org

On Fri, 11 Feb 2000 14:40:15 EST, Bernie Volz <volz@process.com>  said:
> Regarding the recent TCP SYN Flooding attacks, why aren't ALL ISPs
> required to put filtering on their networks that PREVENTS packets with
> invalid source addresses ever entering their infrastructure? If every
> site connected to the Internet did this, spoofing would be much more

See RFC2267.

The problem is that the IETF doesn't have the legal authority to beat ISP's
into submission on this one.  There's also the problem that many ISP's are
somewhat marginal in cluefulness, so things like RFC2267 tend to be of the
"preaching to the choir" variety.

Given that RFC2267 is over 2 years old now, what *do* you suggest the network
community at large do to motivate the sites that still haven't implemented it?

Would somebody be interested in running a BGP blackhole feed of prefixes
known not to be filtering, similar to the maps.vix.com feed for closing
off E-mail spam?  Perhaps if that became prevalent, ISPs would cleanup their
act when their legitimate users couldn't get anyplace because their ISP
wasn't filtering.

<As he dons his asbestos underwear> ;)


-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Fri Feb 11 15:50:35 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA19945
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 15:50:02 -0500 (EST)
Received: from ariel ([216.52.68.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19807
	for <IETF@ietf.org>; Fri, 11 Feb 2000 15:45:41 -0500 (EST)
Received: from ecal.com (localhost [127.0.0.1])
	by ariel (8.9.3/8.9.3) with ESMTP id PAA10410
	for <IETF@ietf.org>; Fri, 11 Feb 2000 15:45:11 -0500
Sender: francis@ariel
Message-ID: <38A474D5.9CF794F4@ecal.com>
Date: Fri, 11 Feb 2000 15:45:09 -0500
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.2.12-20 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
References: <009E5826.5FC1D447.198@process.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Bernie Volz wrote:

> Regarding the recent TCP SYN Flooding attacks, why aren't ALL ISPs
> required to put filtering on their networks that PREVENTS packets with
> invalid source addresses ever entering their infrastructure?

That wouldn't help with the current version of the problem.  An attacker
sends out a virus or worm or something; when it's running on 10^5
machines, the attacker turns them loose on the target.  Each of the source
addresses is valid; each of the packets sent is innocuous in and of
itself.

--
/=================================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.   |
|Chief Scientist |================================================|
|eCal Corp.      |"Genius, Brain! But what if the dragon eats us?"|
|francis@ecal.com|"That would alter our plans."                   |
\=================================================================/





From owner-ietf-outbound@ietf.org  Fri Feb 11 15:56:29 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20177
	for <ietf-web-archive@odin.ietf.org>; Fri, 11 Feb 2000 15:56:29 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA28202;
	Fri, 11 Feb 2000 15:54:31 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id PAA19945
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 15:50:02 -0500 (EST)
Received: from ariel ([216.52.68.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19807
	for <IETF@ietf.org>; Fri, 11 Feb 2000 15:45:41 -0500 (EST)
Received: from ecal.com (localhost [127.0.0.1])
	by ariel (8.9.3/8.9.3) with ESMTP id PAA10410
	for <IETF@ietf.org>; Fri, 11 Feb 2000 15:45:11 -0500
Sender: francis@ariel
Message-ID: <38A474D5.9CF794F4@ecal.com>
Date: Fri, 11 Feb 2000 15:45:09 -0500
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.2.12-20 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
References: <009E5826.5FC1D447.198@process.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Bernie Volz wrote:

> Regarding the recent TCP SYN Flooding attacks, why aren't ALL ISPs
> required to put filtering on their networks that PREVENTS packets with
> invalid source addresses ever entering their infrastructure?

That wouldn't help with the current version of the problem.  An attacker
sends out a virus or worm or something; when it's running on 10^5
machines, the attacker turns them loose on the target.  Each of the source
addresses is valid; each of the packets sent is innocuous in and of
itself.

--
/=================================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.   |
|Chief Scientist |================================================|
|eCal Corp.      |"Genius, Brain! But what if the dragon eats us?"|
|francis@ecal.com|"That would alter our plans."                   |
\=================================================================/





From owner-ietf-outbound  Fri Feb 11 16:20:43 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA21366
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 16:20:03 -0500 (EST)
Received: from alcove.wittsend.com (IDENT:root@alcove.wittsend.com [130.205.0.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21235
	for <IETF@ietf.org>; Fri, 11 Feb 2000 16:18:11 -0500 (EST)
Received: (from mhw@localhost)
	by alcove.wittsend.com (8.9.3/8.9.3) id QAA01014;
	Fri, 11 Feb 2000 16:17:55 -0500
Date: Fri, 11 Feb 2000 16:17:54 -0500
From: "Michael H. Warfield" <mhw@wittsend.com>
To: Bernie Volz <volz@PROCESS.COM>
Cc: IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
Message-ID: <20000211161754.A30474@alcove.wittsend.com>
References: <009E5826.5FC1D447.198@process.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.1.2i
In-Reply-To: <009E5826.5FC1D447.198@process.com>; from volz@PROCESS.COM on Fri, Feb 11, 2000 at 02:40:15PM -0500
X-Loop: ietf@ietf.org

On Fri, Feb 11, 2000 at 02:40:15PM -0500, Bernie Volz wrote:
> Regarding the recent TCP SYN Flooding attacks, why aren't ALL ISPs
> required to put filtering on their networks that PREVENTS packets with
> invalid source addresses ever entering their infrastructure? If every
> site connected to the Internet did this, spoofing would be much more
> difficult because you couldn't do it. Sure, you could spoof an address
> from YOUR network, but that's all. And guess what, it would be much
> easier to track and thus to shut down the intrusions should they occur.

	Clue alert...

	The recent attacks were not TCP SYN Floods.

	Please check recent Bugtraq and Cert information regarding
Distributed DoS attacks.

	Further references:

http://xforce.iss.net/alerts/advise40.php3
http://www.cert.org/advisories/CA-2000-01.html
http://www.fbi.gov/nipc/trinoo.htm

	Detailed analysis of TFN (Tribe Flood Network), Trin00, and
Stacheldraht (Barbed Wire) are here:

http://staff.washington.edu/dittrich/misc/tfn.analysis
http://staff.washington.edu/dittrich/misc/trinoo.analysis
http://staff.washington.edu/dittrich/misc/stacheldraht.analysis

	Contrary to popular belief and the common press, TFN2K (Tribe
Flood Network 2000) also has Windows versions of the slave daemons
as well as Solaris and Linux versions.

	A lot of these attacks appeared to be SMURF style attacks and
TFN (Tribe Flood Network) and TFN2K have distributed smurf capabilities.

	This wasn't even close to being a TCP SYN flood.

	As far as spoofing goes, in their SMURF mode, the only spoofing
is the src_addr part of the ICMP echo that the slave systems send to
their LOCAL broadcast address.  That src_addr is the address of the
system being attacked by ICMP_ECHOREPLY packets that simply consume all
its bandwidth.  Check out the analysis.

	Anti spoofing entry filters would have been of zero effect.

> Thus ever edge router should have filter lists that prevent it
> forwarding traffic out to the Internet (ISPs network) any packet that
> does not have a source address that is valid from that site.

	Would not have helped except maybe in some of the UDP attack
modes of the slaves.

> I would hope that lots of ISPs already do this. But, perhaps not.

> - Bernie Volz
>   Process Software

	Mike
-- 
 Michael H. Warfield    |  (770) 985-6132   |  mhw@WittsEnd.com
  (The Mad Wizard)      |  (770) 331-2437   |  http://www.wittsend.com/mhw/
  NIC whois:  MHW9      |  An optimist believes we live in the best of all
 PGP Key: 0xDF1DD471    |  possible worlds.  A pessimist is sure of it!



From owner-ietf-outbound@ietf.org  Fri Feb 11 16:25:40 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21595
	for <ietf-web-archive@odin.ietf.org>; Fri, 11 Feb 2000 16:25:40 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA28849;
	Fri, 11 Feb 2000 16:23:43 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id QAA21366
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 16:20:03 -0500 (EST)
Received: from alcove.wittsend.com (IDENT:root@alcove.wittsend.com [130.205.0.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21235
	for <IETF@ietf.org>; Fri, 11 Feb 2000 16:18:11 -0500 (EST)
Received: (from mhw@localhost)
	by alcove.wittsend.com (8.9.3/8.9.3) id QAA01014;
	Fri, 11 Feb 2000 16:17:55 -0500
Date: Fri, 11 Feb 2000 16:17:54 -0500
From: "Michael H. Warfield" <mhw@wittsend.com>
To: Bernie Volz <volz@PROCESS.COM>
Cc: IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
Message-ID: <20000211161754.A30474@alcove.wittsend.com>
References: <009E5826.5FC1D447.198@process.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.1.2i
In-Reply-To: <009E5826.5FC1D447.198@process.com>; from volz@PROCESS.COM on Fri, Feb 11, 2000 at 02:40:15PM -0500
X-Loop: ietf@ietf.org

On Fri, Feb 11, 2000 at 02:40:15PM -0500, Bernie Volz wrote:
> Regarding the recent TCP SYN Flooding attacks, why aren't ALL ISPs
> required to put filtering on their networks that PREVENTS packets with
> invalid source addresses ever entering their infrastructure? If every
> site connected to the Internet did this, spoofing would be much more
> difficult because you couldn't do it. Sure, you could spoof an address
> from YOUR network, but that's all. And guess what, it would be much
> easier to track and thus to shut down the intrusions should they occur.

	Clue alert...

	The recent attacks were not TCP SYN Floods.

	Please check recent Bugtraq and Cert information regarding
Distributed DoS attacks.

	Further references:

http://xforce.iss.net/alerts/advise40.php3
http://www.cert.org/advisories/CA-2000-01.html
http://www.fbi.gov/nipc/trinoo.htm

	Detailed analysis of TFN (Tribe Flood Network), Trin00, and
Stacheldraht (Barbed Wire) are here:

http://staff.washington.edu/dittrich/misc/tfn.analysis
http://staff.washington.edu/dittrich/misc/trinoo.analysis
http://staff.washington.edu/dittrich/misc/stacheldraht.analysis

	Contrary to popular belief and the common press, TFN2K (Tribe
Flood Network 2000) also has Windows versions of the slave daemons
as well as Solaris and Linux versions.

	A lot of these attacks appeared to be SMURF style attacks and
TFN (Tribe Flood Network) and TFN2K have distributed smurf capabilities.

	This wasn't even close to being a TCP SYN flood.

	As far as spoofing goes, in their SMURF mode, the only spoofing
is the src_addr part of the ICMP echo that the slave systems send to
their LOCAL broadcast address.  That src_addr is the address of the
system being attacked by ICMP_ECHOREPLY packets that simply consume all
its bandwidth.  Check out the analysis.

	Anti spoofing entry filters would have been of zero effect.

> Thus ever edge router should have filter lists that prevent it
> forwarding traffic out to the Internet (ISPs network) any packet that
> does not have a source address that is valid from that site.

	Would not have helped except maybe in some of the UDP attack
modes of the slaves.

> I would hope that lots of ISPs already do this. But, perhaps not.

> - Bernie Volz
>   Process Software

	Mike
-- 
 Michael H. Warfield    |  (770) 985-6132   |  mhw@WittsEnd.com
  (The Mad Wizard)      |  (770) 331-2437   |  http://www.wittsend.com/mhw/
  NIC whois:  MHW9      |  An optimist believes we live in the best of all
 PGP Key: 0xDF1DD471    |  possible worlds.  A pessimist is sure of it!



From owner-ietf-outbound  Fri Feb 11 16:30:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA21736
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 16:30:03 -0500 (EST)
Received: from drawbridge.ascend.com (drawbridge.ascend.com [198.4.92.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21428
	for <IETF@ietf.org>; Fri, 11 Feb 2000 16:21:45 -0500 (EST)
Received: from fw-ext.ascend.com (fw-ext [198.4.92.5])
	by drawbridge.ascend.com (8.9.1a/8.9.1) with SMTP id NAA03881;
	Fri, 11 Feb 2000 13:15:14 -0800 (PST)
Received: from russet.ascend.com by fw-ext.ascend.com
          via smtpd (for drawbridge.ascend.com [198.4.92.1]) with SMTP; 11 Feb 2000 21:21:27 UT
Received: from porky (porky.ascend.com [192.207.23.83])
	by russet.ascend.com (8.9.1a/8.9.1) with ESMTP id NAA02439;
	Fri, 11 Feb 2000 13:21:27 -0800 (PST)
Received: from ascend.com by ascend.com
Message-Id: <4.2.2.20000211130524.00ad84e0@porky>
X-Sender: mhold@porky
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Fri, 11 Feb 2000 13:16:18 -0800
To: "Theodore Y. Ts'o" <tytso@MIT.EDU>
From: Matt Holdrege <matt@ascend.com>
Subject: Re: IETF meeting wireless "standard"
Cc: Dave Crocker <dcrocker@brandenburg.com>, IETF@ietf.org
In-Reply-To: <200002091423.JAA07600@tsx-prime.MIT.EDU>
References: <Dave Crocker's message of Wed, 09 Feb 2000 11:21:24 +0100, <4.3.0.39.0.20000209092752.00c554f0@mail.bayarea.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 09:23 AM 2/9/00 -0500, Theodore Y. Ts'o wrote:
>Prior.  Definitely prior; that way folks don't have to spend the first
>half of the week hacking support for the 802.11 DS card into NetBSD,
>Linux, BSDI, et. al.  :-)

There is a neat FAQ at http://www.wavelan.com/products/faq/ and one of the 
FAQ items says: The WaveLAN Network Interface Cards (NICs) include NDIS and 
ODI client drivers, allowing WaveLAN to work in the Windows 95/98, Windows 
NT, Win2K, Apple, Linux and Novell environments. I seem to recall that 
someone has already done NetBSD and BSDI for these cards, but I've lost 
that email.

>I'm definitely interested.  So do we have someone with a company
>connection who can get the IETF a good bulk discount on 801.11 DS cards?
>Especially the 11 megabit variant...  (Is Adelaide going to have 11 mbps
>support?)

I've been working on getting Lucent to sponsor DS 11Mbps base station 
support as well as a deep IETF-special discount on new 11mbps PCMCIA cards. 
More information to come soon.

BTW, if you have older slower Wavelan gear the new base stations are 
backwards compatible.




From owner-ietf-outbound@ietf.org  Fri Feb 11 16:33:49 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21971
	for <ietf-web-archive@odin.ietf.org>; Fri, 11 Feb 2000 16:33:49 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA29094;
	Fri, 11 Feb 2000 16:31:39 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id QAA21736
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 16:30:03 -0500 (EST)
Received: from drawbridge.ascend.com (drawbridge.ascend.com [198.4.92.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21428
	for <IETF@ietf.org>; Fri, 11 Feb 2000 16:21:45 -0500 (EST)
Received: from fw-ext.ascend.com (fw-ext [198.4.92.5])
	by drawbridge.ascend.com (8.9.1a/8.9.1) with SMTP id NAA03881;
	Fri, 11 Feb 2000 13:15:14 -0800 (PST)
Received: from russet.ascend.com by fw-ext.ascend.com
          via smtpd (for drawbridge.ascend.com [198.4.92.1]) with SMTP; 11 Feb 2000 21:21:27 UT
Received: from porky (porky.ascend.com [192.207.23.83])
	by russet.ascend.com (8.9.1a/8.9.1) with ESMTP id NAA02439;
	Fri, 11 Feb 2000 13:21:27 -0800 (PST)
Received: from ascend.com by ascend.com
Message-Id: <4.2.2.20000211130524.00ad84e0@porky>
X-Sender: mhold@porky
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Fri, 11 Feb 2000 13:16:18 -0800
To: "Theodore Y. Ts'o" <tytso@MIT.EDU>
From: Matt Holdrege <matt@ascend.com>
Subject: Re: IETF meeting wireless "standard"
Cc: Dave Crocker <dcrocker@brandenburg.com>, IETF@ietf.org
In-Reply-To: <200002091423.JAA07600@tsx-prime.MIT.EDU>
References: <Dave Crocker's message of Wed, 09 Feb 2000 11:21:24 +0100, <4.3.0.39.0.20000209092752.00c554f0@mail.bayarea.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 09:23 AM 2/9/00 -0500, Theodore Y. Ts'o wrote:
>Prior.  Definitely prior; that way folks don't have to spend the first
>half of the week hacking support for the 802.11 DS card into NetBSD,
>Linux, BSDI, et. al.  :-)

There is a neat FAQ at http://www.wavelan.com/products/faq/ and one of the 
FAQ items says: The WaveLAN Network Interface Cards (NICs) include NDIS and 
ODI client drivers, allowing WaveLAN to work in the Windows 95/98, Windows 
NT, Win2K, Apple, Linux and Novell environments. I seem to recall that 
someone has already done NetBSD and BSDI for these cards, but I've lost 
that email.

>I'm definitely interested.  So do we have someone with a company
>connection who can get the IETF a good bulk discount on 801.11 DS cards?
>Especially the 11 megabit variant...  (Is Adelaide going to have 11 mbps
>support?)

I've been working on getting Lucent to sponsor DS 11Mbps base station 
support as well as a deep IETF-special discount on new 11mbps PCMCIA cards. 
More information to come soon.

BTW, if you have older slower Wavelan gear the new base stations are 
backwards compatible.




From owner-ietf-outbound  Fri Feb 11 16:40:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA22245
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 16:40:04 -0500 (EST)
Received: from mailman.cisco.com (mailman.cisco.com [171.68.225.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22077
	for <IETF@ietf.org>; Fri, 11 Feb 2000 16:35:58 -0500 (EST)
Received: from bigger-dawgs (pferguso-isdn.cisco.com [171.70.114.134]) by mailman.cisco.com (8.8.8+Sun/CISCO.SERVER.1.2) with ESMTP id NAA29777; Fri, 11 Feb 2000 13:35:22 -0800 (PST)
Message-Id: <4.2.2.20000211163325.00a50470@lint.cisco.com>
X-Sender: pferguso@lint.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Fri, 11 Feb 2000 16:35:18 -0500
To: Valdis.Kletnieks@vt.edu
From: Paul Ferguson <ferguson@cisco.com>
Subject: Re: Internet SYN Flooding, spoofing attacks 
Cc: IETF@ietf.org
In-Reply-To: <200002112033.e1BKXC917344@black-ice.cc.vt.edu>
References: <Your message of "Fri, 11 Feb 2000 14:40:15 EST." <009E5826.5FC1D447.198@process.com>
 <009E5826.5FC1D447.198@process.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 03:33 PM 02/11/2000 -0500, Valdis.Kletnieks@vt.edu wrote:

>Given that RFC2267 is over 2 years old now, what *do* you suggest the network
>community at large do to motivate the sites that still haven't implemented it?

Do you think that if RFC2267 was advanced as a BCP that
it would carry more weight, and therefore more ISP's would
implement RFC2267-style filtering? Coupled with the latest
denial of service attacks?

- paul



From owner-ietf-outbound@ietf.org  Fri Feb 11 16:44:45 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22484
	for <ietf-web-archive@odin.ietf.org>; Fri, 11 Feb 2000 16:44:45 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA29286;
	Fri, 11 Feb 2000 16:42:48 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id QAA22245
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 16:40:04 -0500 (EST)
Received: from mailman.cisco.com (mailman.cisco.com [171.68.225.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22077
	for <IETF@ietf.org>; Fri, 11 Feb 2000 16:35:58 -0500 (EST)
Received: from bigger-dawgs (pferguso-isdn.cisco.com [171.70.114.134]) by mailman.cisco.com (8.8.8+Sun/CISCO.SERVER.1.2) with ESMTP id NAA29777; Fri, 11 Feb 2000 13:35:22 -0800 (PST)
Message-Id: <4.2.2.20000211163325.00a50470@lint.cisco.com>
X-Sender: pferguso@lint.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Fri, 11 Feb 2000 16:35:18 -0500
To: Valdis.Kletnieks@vt.edu
From: Paul Ferguson <ferguson@cisco.com>
Subject: Re: Internet SYN Flooding, spoofing attacks 
Cc: IETF@ietf.org
In-Reply-To: <200002112033.e1BKXC917344@black-ice.cc.vt.edu>
References: <Your message of "Fri, 11 Feb 2000 14:40:15 EST." <009E5826.5FC1D447.198@process.com>
 <009E5826.5FC1D447.198@process.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 03:33 PM 02/11/2000 -0500, Valdis.Kletnieks@vt.edu wrote:

>Given that RFC2267 is over 2 years old now, what *do* you suggest the network
>community at large do to motivate the sites that still haven't implemented it?

Do you think that if RFC2267 was advanced as a BCP that
it would carry more weight, and therefore more ISP's would
implement RFC2267-style filtering? Coupled with the latest
denial of service attacks?

- paul



From owner-ietf-outbound  Fri Feb 11 16:50:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA22701
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 16:50:03 -0500 (EST)
Received: from mailman.cisco.com (mailman.cisco.com [171.68.225.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22677
	for <IETF@ietf.org>; Fri, 11 Feb 2000 16:49:47 -0500 (EST)
Received: from bigger-dawgs (pferguso-isdn.cisco.com [171.70.114.134]) by mailman.cisco.com (8.8.8+Sun/CISCO.SERVER.1.2) with ESMTP id NAA05466; Fri, 11 Feb 2000 13:49:12 -0800 (PST)
Message-Id: <4.2.2.20000211163625.00a4d770@lint.cisco.com>
X-Sender: pferguso@lint.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Fri, 11 Feb 2000 16:49:08 -0500
To: John Stracke <francis@ECAL.COM>
From: Paul Ferguson <ferguson@cisco.com>
Subject: Re: Internet SYN Flooding, spoofing attacks
Cc: IETF@ietf.org
In-Reply-To: <38A474D5.9CF794F4@ecal.com>
References: <009E5826.5FC1D447.198@process.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 03:45 PM 02/11/2000 -0500, John Stracke wrote:

> > Regarding the recent TCP SYN Flooding attacks, why aren't ALL ISPs
> > required to put filtering on their networks that PREVENTS packets with
> > invalid source addresses ever entering their infrastructure?
>
>That wouldn't help with the current version of the problem.  An attacker
>sends out a virus or worm or something; when it's running on 10^5
>machines, the attacker turns them loose on the target.  Each of the source
>addresses is valid; each of the packets sent is innocuous in and of
>itself.

Yes, it would certainly help.

It would allow the attacks to be traced back to the zombies (in
the case of these DDoS attacks), and the perpetrators to be traced
back and identified.

- paul



From owner-ietf-outbound@ietf.org  Fri Feb 11 16:54:36 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22984
	for <ietf-web-archive@odin.ietf.org>; Fri, 11 Feb 2000 16:54:36 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA29455;
	Fri, 11 Feb 2000 16:52:35 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id QAA22701
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 16:50:03 -0500 (EST)
Received: from mailman.cisco.com (mailman.cisco.com [171.68.225.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22677
	for <IETF@ietf.org>; Fri, 11 Feb 2000 16:49:47 -0500 (EST)
Received: from bigger-dawgs (pferguso-isdn.cisco.com [171.70.114.134]) by mailman.cisco.com (8.8.8+Sun/CISCO.SERVER.1.2) with ESMTP id NAA05466; Fri, 11 Feb 2000 13:49:12 -0800 (PST)
Message-Id: <4.2.2.20000211163625.00a4d770@lint.cisco.com>
X-Sender: pferguso@lint.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Fri, 11 Feb 2000 16:49:08 -0500
To: John Stracke <francis@ECAL.COM>
From: Paul Ferguson <ferguson@cisco.com>
Subject: Re: Internet SYN Flooding, spoofing attacks
Cc: IETF@ietf.org
In-Reply-To: <38A474D5.9CF794F4@ecal.com>
References: <009E5826.5FC1D447.198@process.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 03:45 PM 02/11/2000 -0500, John Stracke wrote:

> > Regarding the recent TCP SYN Flooding attacks, why aren't ALL ISPs
> > required to put filtering on their networks that PREVENTS packets with
> > invalid source addresses ever entering their infrastructure?
>
>That wouldn't help with the current version of the problem.  An attacker
>sends out a virus or worm or something; when it's running on 10^5
>machines, the attacker turns them loose on the target.  Each of the source
>addresses is valid; each of the packets sent is innocuous in and of
>itself.

Yes, it would certainly help.

It would allow the attacks to be traced back to the zombies (in
the case of these DDoS attacks), and the perpetrators to be traced
back and identified.

- paul



From owner-ietf-outbound  Fri Feb 11 17:31:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA24230
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 17:30:01 -0500 (EST)
Received: from mailman.cisco.com (mailman.cisco.com [171.68.225.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23758
	for <IETF@ietf.org>; Fri, 11 Feb 2000 17:14:45 -0500 (EST)
Received: from bigger-dawgs (pferguso-isdn.cisco.com [171.70.114.134]) by mailman.cisco.com (8.8.8+Sun/CISCO.SERVER.1.2) with ESMTP id OAA15321; Fri, 11 Feb 2000 14:14:06 -0800 (PST)
Message-Id: <4.2.2.20000211170740.00a38c60@lint.cisco.com>
X-Sender: pferguso@lint.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Fri, 11 Feb 2000 17:14:02 -0500
To: Stephen Kent <kent@bbn.com>
From: Paul Ferguson <ferguson@cisco.com>
Subject: Re: Internet SYN Flooding, spoofing attacks
Cc: Bernie Volz <volz@process.com>, IETF@ietf.org
In-Reply-To: <v04220815b4ca365b3949@[171.78.30.107]>
References: <4.2.2.20000211151342.00a36e60@lint.cisco.com>
 <4.2.2.20000211151342.00a36e60@lint.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

Steve,

That's simply propagating FUD, and I think that by
making such sweeping assumptions, you are doing the
Internet community a disservice.

Is RFC2267-style filtering a perfect solution for
every situation? No. Sure there are some scenarios
where it foo bars transit traffic, but in the larger
scheme of things, most dual-homed networks are not
providing transit.

Does it impact router performance? Perhaps. It really
depends on various arbitrary issues.

 From an architectural perspective, it is very important
_where_ you filter to be effective, not cause transit
problems, and not make smoke roll out of the back of
the equipment.

Will it stop bogon source packets from being injected into
the Internet, so that anyone foolish enough top launch a
denial of service attack can be traced back, identified, and
prosecuted? Absolutely.

- paul


At 04:59 PM 02/11/2000 -0500, Stephen Kent wrote:

>Paul & Bernie,
>
>A more technically focused answer is that most routers are not
>designed to perform the filtering without adversely impacting
>throughput, and because dual homing and the mesh nature of Internet
>connectivity makes it hard to apply appropriate filters for all
>subscribers (remembering that some subscribers are really down stream
>service providers ...)
>
>Steve
>



From owner-ietf-outbound@ietf.org  Fri Feb 11 17:36:12 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24531
	for <ietf-web-archive@odin.ietf.org>; Fri, 11 Feb 2000 17:36:12 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA00489;
	Fri, 11 Feb 2000 17:34:15 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id RAA24230
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 17:30:01 -0500 (EST)
Received: from mailman.cisco.com (mailman.cisco.com [171.68.225.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23758
	for <IETF@ietf.org>; Fri, 11 Feb 2000 17:14:45 -0500 (EST)
Received: from bigger-dawgs (pferguso-isdn.cisco.com [171.70.114.134]) by mailman.cisco.com (8.8.8+Sun/CISCO.SERVER.1.2) with ESMTP id OAA15321; Fri, 11 Feb 2000 14:14:06 -0800 (PST)
Message-Id: <4.2.2.20000211170740.00a38c60@lint.cisco.com>
X-Sender: pferguso@lint.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Fri, 11 Feb 2000 17:14:02 -0500
To: Stephen Kent <kent@bbn.com>
From: Paul Ferguson <ferguson@cisco.com>
Subject: Re: Internet SYN Flooding, spoofing attacks
Cc: Bernie Volz <volz@process.com>, IETF@ietf.org
In-Reply-To: <v04220815b4ca365b3949@[171.78.30.107]>
References: <4.2.2.20000211151342.00a36e60@lint.cisco.com>
 <4.2.2.20000211151342.00a36e60@lint.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

Steve,

That's simply propagating FUD, and I think that by
making such sweeping assumptions, you are doing the
Internet community a disservice.

Is RFC2267-style filtering a perfect solution for
every situation? No. Sure there are some scenarios
where it foo bars transit traffic, but in the larger
scheme of things, most dual-homed networks are not
providing transit.

Does it impact router performance? Perhaps. It really
depends on various arbitrary issues.

 From an architectural perspective, it is very important
_where_ you filter to be effective, not cause transit
problems, and not make smoke roll out of the back of
the equipment.

Will it stop bogon source packets from being injected into
the Internet, so that anyone foolish enough top launch a
denial of service attack can be traced back, identified, and
prosecuted? Absolutely.

- paul


At 04:59 PM 02/11/2000 -0500, Stephen Kent wrote:

>Paul & Bernie,
>
>A more technically focused answer is that most routers are not
>designed to perform the filtering without adversely impacting
>throughput, and because dual homing and the mesh nature of Internet
>connectivity makes it hard to apply appropriate filters for all
>subscribers (remembering that some subscribers are really down stream
>service providers ...)
>
>Steve
>



From owner-ietf-outbound  Fri Feb 11 17:40:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA24653
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 17:40:02 -0500 (EST)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23997
	for <IETF@ietf.org>; Fri, 11 Feb 2000 17:24:20 -0500 (EST)
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.0.Beta13/8.10.0.Beta13) with ESMTP id e1BMO5917310;
	Fri, 11 Feb 2000 17:24:05 -0500
Message-Id: <200002112224.e1BMO5917310@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Paul Ferguson <ferguson@cisco.com>
cc: IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks 
In-reply-to: Your message of "Fri, 11 Feb 2000 16:35:18 EST."
             <4.2.2.20000211163325.00a50470@lint.cisco.com> 
From: Valdis.Kletnieks@vt.edu
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <009E5826.5FC1D447.198@process.com>
            <4.2.2.20000211163325.00a50470@lint.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 11 Feb 2000 17:24:04 -0500
X-Loop: ietf@ietf.org

On Fri, 11 Feb 2000 16:35:18 EST, Paul Ferguson said:
> Do you think that if RFC2267 was advanced as a BCP that
> it would carry more weight, and therefore more ISP's would
> implement RFC2267-style filtering? Coupled with the latest
> denial of service attacks?

On the one hand, I think it would make a good candidate for BCP.  It seems
to be similar in tone with RFCs 2502 and 2644.  I'd have to re-read it to
see if it would need any textual changes, or if it's OK as it is.

I was talking to a co-worker on this topic, and his exact quote was
"We have our s--t more together than most sites, despite our best
efforts".  The problem is that he was right - our site may have clue,
but there's a lot of uneducated sites out there.

Does anybody have statistics on how effective RFC2350 (Expectations
for Computer Security Incident Response) was?  Or RFC2502 (Anti-Spam
Recommendations for SMTP MTAs)? Or RFC2644 ( Changing the Default for
Directed Broadcasts in Routers)?  It would seem reasonable that moving
2267 to BCP should have a similar effectiveness...
-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech






From owner-ietf-outbound@ietf.org  Fri Feb 11 17:43:52 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24826
	for <ietf-web-archive@odin.ietf.org>; Fri, 11 Feb 2000 17:43:52 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA00651;
	Fri, 11 Feb 2000 17:41:52 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id RAA24653
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 17:40:02 -0500 (EST)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23997
	for <IETF@ietf.org>; Fri, 11 Feb 2000 17:24:20 -0500 (EST)
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.0.Beta13/8.10.0.Beta13) with ESMTP id e1BMO5917310;
	Fri, 11 Feb 2000 17:24:05 -0500
Message-Id: <200002112224.e1BMO5917310@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Paul Ferguson <ferguson@cisco.com>
cc: IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks 
In-reply-to: Your message of "Fri, 11 Feb 2000 16:35:18 EST."
             <4.2.2.20000211163325.00a50470@lint.cisco.com> 
From: Valdis.Kletnieks@vt.edu
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <009E5826.5FC1D447.198@process.com>
            <4.2.2.20000211163325.00a50470@lint.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 11 Feb 2000 17:24:04 -0500
X-Loop: ietf@ietf.org

On Fri, 11 Feb 2000 16:35:18 EST, Paul Ferguson said:
> Do you think that if RFC2267 was advanced as a BCP that
> it would carry more weight, and therefore more ISP's would
> implement RFC2267-style filtering? Coupled with the latest
> denial of service attacks?

On the one hand, I think it would make a good candidate for BCP.  It seems
to be similar in tone with RFCs 2502 and 2644.  I'd have to re-read it to
see if it would need any textual changes, or if it's OK as it is.

I was talking to a co-worker on this topic, and his exact quote was
"We have our s--t more together than most sites, despite our best
efforts".  The problem is that he was right - our site may have clue,
but there's a lot of uneducated sites out there.

Does anybody have statistics on how effective RFC2350 (Expectations
for Computer Security Incident Response) was?  Or RFC2502 (Anti-Spam
Recommendations for SMTP MTAs)? Or RFC2644 ( Changing the Default for
Directed Broadcasts in Routers)?  It would seem reasonable that moving
2267 to BCP should have a similar effectiveness...
-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech






From owner-ietf-outbound  Fri Feb 11 19:10:26 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA26977
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 19:10:04 -0500 (EST)
Received: from po1.bbn.com (PO1.BBN.COM [192.1.50.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26838
	for <IETF@ietf.org>; Fri, 11 Feb 2000 19:02:16 -0500 (EST)
Received: from [171.78.30.107] (comsec.bbn.com [171.78.30.107])
	by po1.bbn.com (8.9.1/8.9.1) with ESMTP id TAA27677;
	Fri, 11 Feb 2000 19:02:11 -0500 (EST)
Mime-Version: 1.0
X-Sender: kent@po1.bbn.com
Message-Id: <v04220816b4ca501c4638@[171.78.30.107]>
In-Reply-To: <4.2.2.20000211170740.00a38c60@lint.cisco.com>
References: <4.2.2.20000211151342.00a36e60@lint.cisco.com>
 <4.2.2.20000211151342.00a36e60@lint.cisco.com>
 <4.2.2.20000211170740.00a38c60@lint.cisco.com>
Date: Fri, 11 Feb 2000 19:01:02 -0500
To: Paul Ferguson <ferguson@cisco.com>
From: Stephen Kent <kent@bbn.com>
Subject: Re: Internet SYN Flooding, spoofing attacks
Cc: IETF@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

Paul,

I object to the characterization of my comments as "propagating FUD." 
One might equally well suggest that 2267 constitutes a naive model of 
how to prevent IP spoofing, but I was polite enough not to say that 
:-).

 From a security perspective, it is never desirable to rely on a 
mechanism that assumes that everyone else does "the right thing." 
When one suggests that a first tier ISP would not need to filter 
traffic from down stream providers, because IF they do the filtering, 
then the problem will not arise via those links, one is suggesting 
precisely this sort of model.

Edge filtering would often be helpful, but it is not a panacea, as 
pointed out by others in regard to the current set of attacks, nor is 
the performance impact trivial with most current routers. Because 
most routers are optimized for transit traffic forwarding, the 
ability to filter on the interface cards is limited, as I'm sure you 
know.  Also, several of the distributed DoS attacks we are seeing do 
not use fake source addresses from other sites, so simple filtering 
of the sort proposed in 2267 would not be effective in these cases.

Finally, I am aware of new routers for which this sort of filtering 
would be child's play, but they are not yet deployed.  One ought not 
suggest that edge filtering is not being applied simply because of 
laziness on the part of ISPs.

Steve




From owner-ietf-outbound@ietf.org  Fri Feb 11 19:11:56 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27043
	for <ietf-web-archive@odin.ietf.org>; Fri, 11 Feb 2000 19:11:56 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA02473;
	Fri, 11 Feb 2000 19:09:55 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id TAA26977
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 19:10:04 -0500 (EST)
Received: from po1.bbn.com (PO1.BBN.COM [192.1.50.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26838
	for <IETF@ietf.org>; Fri, 11 Feb 2000 19:02:16 -0500 (EST)
Received: from [171.78.30.107] (comsec.bbn.com [171.78.30.107])
	by po1.bbn.com (8.9.1/8.9.1) with ESMTP id TAA27677;
	Fri, 11 Feb 2000 19:02:11 -0500 (EST)
Mime-Version: 1.0
X-Sender: kent@po1.bbn.com
Message-Id: <v04220816b4ca501c4638@[171.78.30.107]>
In-Reply-To: <4.2.2.20000211170740.00a38c60@lint.cisco.com>
References: <4.2.2.20000211151342.00a36e60@lint.cisco.com>
 <4.2.2.20000211151342.00a36e60@lint.cisco.com>
 <4.2.2.20000211170740.00a38c60@lint.cisco.com>
Date: Fri, 11 Feb 2000 19:01:02 -0500
To: Paul Ferguson <ferguson@cisco.com>
From: Stephen Kent <kent@bbn.com>
Subject: Re: Internet SYN Flooding, spoofing attacks
Cc: IETF@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

Paul,

I object to the characterization of my comments as "propagating FUD." 
One might equally well suggest that 2267 constitutes a naive model of 
how to prevent IP spoofing, but I was polite enough not to say that 
:-).

 From a security perspective, it is never desirable to rely on a 
mechanism that assumes that everyone else does "the right thing." 
When one suggests that a first tier ISP would not need to filter 
traffic from down stream providers, because IF they do the filtering, 
then the problem will not arise via those links, one is suggesting 
precisely this sort of model.

Edge filtering would often be helpful, but it is not a panacea, as 
pointed out by others in regard to the current set of attacks, nor is 
the performance impact trivial with most current routers. Because 
most routers are optimized for transit traffic forwarding, the 
ability to filter on the interface cards is limited, as I'm sure you 
know.  Also, several of the distributed DoS attacks we are seeing do 
not use fake source addresses from other sites, so simple filtering 
of the sort proposed in 2267 would not be effective in these cases.

Finally, I am aware of new routers for which this sort of filtering 
would be child's play, but they are not yet deployed.  One ought not 
suggest that edge filtering is not being applied simply because of 
laziness on the part of ISPs.

Steve




From owner-ietf-outbound  Fri Feb 11 19:40:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA27391
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 19:40:03 -0500 (EST)
Received: from breakaway.Stanford.EDU (breakaway.Stanford.EDU [171.64.20.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27348
	for <ietf@ietf.org>; Fri, 11 Feb 2000 19:37:53 -0500 (EST)
Received: from localhost (hodges@localhost)
	by breakaway.Stanford.EDU (8.9.3/8.9.3) with ESMTP id QAA09761
	for <ietf@ietf.org>; Fri, 11 Feb 2000 16:37:53 -0800 (PST)
Message-Id: <200002120037.QAA09761@breakaway.Stanford.EDU>
X-Mailer: exmh version 2.0.2 2/24/98
Subject: Dave Clark was on PBS News Hour 10-Feb-2000..
To: ietf@ietf.org
From: Jeff.Hodges@stanford.edu
Reply-to: ietf@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 11 Feb 2000 16:37:53 -0800
Sender: hodges@Wind.Stanford.EDU
X-Loop: ietf@ietf.org

..the transcript is available here..

  http://www.pbs.org/newshour/bb/cyberspace/jan-june00/hack_attack_2-10.html

Overall series of relatively recent related segments..

  http://www.pbs.org/newshour/bb/cyberspace/internet_security.html


JeffH




From owner-ietf-outbound@ietf.org  Fri Feb 11 19:41:33 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27491
	for <ietf-web-archive@odin.ietf.org>; Fri, 11 Feb 2000 19:41:33 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA03628;
	Fri, 11 Feb 2000 19:39:32 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id TAA27391
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 19:40:03 -0500 (EST)
Received: from breakaway.Stanford.EDU (breakaway.Stanford.EDU [171.64.20.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27348
	for <ietf@ietf.org>; Fri, 11 Feb 2000 19:37:53 -0500 (EST)
Received: from localhost (hodges@localhost)
	by breakaway.Stanford.EDU (8.9.3/8.9.3) with ESMTP id QAA09761
	for <ietf@ietf.org>; Fri, 11 Feb 2000 16:37:53 -0800 (PST)
Message-Id: <200002120037.QAA09761@breakaway.Stanford.EDU>
X-Mailer: exmh version 2.0.2 2/24/98
Subject: Dave Clark was on PBS News Hour 10-Feb-2000..
To: ietf@ietf.org
From: Jeff.Hodges@stanford.edu
Reply-to: ietf@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 11 Feb 2000 16:37:53 -0800
Sender: hodges@Wind.Stanford.EDU
X-Loop: ietf@ietf.org

..the transcript is available here..

  http://www.pbs.org/newshour/bb/cyberspace/jan-june00/hack_attack_2-10.html

Overall series of relatively recent related segments..

  http://www.pbs.org/newshour/bb/cyberspace/internet_security.html


JeffH




From owner-ietf-outbound  Fri Feb 11 20:10:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA27917
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 20:10:02 -0500 (EST)
Received: from mailman.cisco.com (mailman.cisco.com [171.68.225.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27819
	for <IETF@ietf.org>; Fri, 11 Feb 2000 20:03:21 -0500 (EST)
Received: from bigger-dawgs (pferguso-isdn.cisco.com [171.70.114.134]) by mailman.cisco.com (8.8.8+Sun/CISCO.SERVER.1.2) with ESMTP id RAA07990; Fri, 11 Feb 2000 17:02:48 -0800 (PST)
Message-Id: <4.2.2.20000211194647.00a3e8a0@lint.cisco.com>
X-Sender: pferguso@lint.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Fri, 11 Feb 2000 20:02:44 -0500
To: Stephen Kent <kent@bbn.com>
From: Paul Ferguson <ferguson@cisco.com>
Subject: Re: Internet SYN Flooding, spoofing attacks
Cc: IETF@ietf.org, dts@senie.com
In-Reply-To: <v04220816b4ca501c4638@[171.78.30.107]>
References: <4.2.2.20000211170740.00a38c60@lint.cisco.com>
 <4.2.2.20000211151342.00a36e60@lint.cisco.com>
 <4.2.2.20000211151342.00a36e60@lint.cisco.com>
 <4.2.2.20000211170740.00a38c60@lint.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

Steve,

At 07:01 PM 02/11/2000 -0500, Stephen Kent wrote:

>  From a security perspective, it is never desirable to rely on a
>mechanism that assumes that everyone else does "the right thing."

I agree. Every potential target network is not only responsible
for their own security, but in my opinion, they should be
conscientiously motivated to do the Right Things for the Internet
community at-large.

Of course, it doesn't always work out that way, sadly, and I'm not
delusional that it does.

>When one suggests that a first tier ISP would not need to filter
>traffic from down stream providers, because IF they do the filtering,
>then the problem will not arise via those links, one is suggesting
>precisely this sort of model.

You're approaching this from the wrong perspective, in my opinion.

There is no assumption implied that RFC2267 filtering is needed --
it is required. What good is it if one or two or 300 people do
it, and another 157,000 do not?

Well, there is a little good, but the more people that do it, the
better off we all are.

The bottom line here is that RFC2267-style filtering (or unicast
RPF checks, or what have you) stops spoofed source address packets
from being transmitted into the Internet from places they have no
business being originated from to begin with.

In even the worst case, those conscientious network admins that
_do_ do it can say without remorse that they are doing their part,
and can at least be assured that DoS attacks using spoofed source
addresses are not being originated from their customer base.

And this is a Bad Thing?

>Edge filtering would often be helpful, but it is not a panacea, as
>pointed out by others in regard to the current set of attacks, nor is
>the performance impact trivial with most current routers.

It is negligible at the edge in most cases, but you really need to
define "edge" a little better. In some cases, it is very low speed
links, in others it is an OC-12.

>Because
>most routers are optimized for transit traffic forwarding, the
>ability to filter on the interface cards is limited, as I'm sure you
>know.

No, I don't know that at all. _Backbone_routers_ are optimized for
packet forwarding -- I do know that.

>  Also, several of the distributed DoS attacks we are seeing do
>not use fake source addresses from other sites, so simple filtering
>of the sort proposed in 2267 would not be effective in these cases.

Again, you're missing the point.

If attackers are limited to launching DoS attacks using traceable
addresses, then not only can their zombies be traced & found, but
so can their controller (the perpetrator himself). Of this, make no
mistake.

>Finally, I am aware of new routers for which this sort of filtering
>would be child's play, but they are not yet deployed.  One ought not
>suggest that edge filtering is not being applied simply because of
>laziness on the part of ISPs.

Steve, you said that -- I didn't. I think ISP's will do what their
customers pay them to do.

- paul



From owner-ietf-outbound@ietf.org  Fri Feb 11 20:13:06 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28009
	for <ietf-web-archive@odin.ietf.org>; Fri, 11 Feb 2000 20:13:06 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA05073;
	Fri, 11 Feb 2000 20:11:05 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id UAA27917
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 20:10:02 -0500 (EST)
Received: from mailman.cisco.com (mailman.cisco.com [171.68.225.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27819
	for <IETF@ietf.org>; Fri, 11 Feb 2000 20:03:21 -0500 (EST)
Received: from bigger-dawgs (pferguso-isdn.cisco.com [171.70.114.134]) by mailman.cisco.com (8.8.8+Sun/CISCO.SERVER.1.2) with ESMTP id RAA07990; Fri, 11 Feb 2000 17:02:48 -0800 (PST)
Message-Id: <4.2.2.20000211194647.00a3e8a0@lint.cisco.com>
X-Sender: pferguso@lint.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Fri, 11 Feb 2000 20:02:44 -0500
To: Stephen Kent <kent@bbn.com>
From: Paul Ferguson <ferguson@cisco.com>
Subject: Re: Internet SYN Flooding, spoofing attacks
Cc: IETF@ietf.org, dts@senie.com
In-Reply-To: <v04220816b4ca501c4638@[171.78.30.107]>
References: <4.2.2.20000211170740.00a38c60@lint.cisco.com>
 <4.2.2.20000211151342.00a36e60@lint.cisco.com>
 <4.2.2.20000211151342.00a36e60@lint.cisco.com>
 <4.2.2.20000211170740.00a38c60@lint.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

Steve,

At 07:01 PM 02/11/2000 -0500, Stephen Kent wrote:

>  From a security perspective, it is never desirable to rely on a
>mechanism that assumes that everyone else does "the right thing."

I agree. Every potential target network is not only responsible
for their own security, but in my opinion, they should be
conscientiously motivated to do the Right Things for the Internet
community at-large.

Of course, it doesn't always work out that way, sadly, and I'm not
delusional that it does.

>When one suggests that a first tier ISP would not need to filter
>traffic from down stream providers, because IF they do the filtering,
>then the problem will not arise via those links, one is suggesting
>precisely this sort of model.

You're approaching this from the wrong perspective, in my opinion.

There is no assumption implied that RFC2267 filtering is needed --
it is required. What good is it if one or two or 300 people do
it, and another 157,000 do not?

Well, there is a little good, but the more people that do it, the
better off we all are.

The bottom line here is that RFC2267-style filtering (or unicast
RPF checks, or what have you) stops spoofed source address packets
from being transmitted into the Internet from places they have no
business being originated from to begin with.

In even the worst case, those conscientious network admins that
_do_ do it can say without remorse that they are doing their part,
and can at least be assured that DoS attacks using spoofed source
addresses are not being originated from their customer base.

And this is a Bad Thing?

>Edge filtering would often be helpful, but it is not a panacea, as
>pointed out by others in regard to the current set of attacks, nor is
>the performance impact trivial with most current routers.

It is negligible at the edge in most cases, but you really need to
define "edge" a little better. In some cases, it is very low speed
links, in others it is an OC-12.

>Because
>most routers are optimized for transit traffic forwarding, the
>ability to filter on the interface cards is limited, as I'm sure you
>know.

No, I don't know that at all. _Backbone_routers_ are optimized for
packet forwarding -- I do know that.

>  Also, several of the distributed DoS attacks we are seeing do
>not use fake source addresses from other sites, so simple filtering
>of the sort proposed in 2267 would not be effective in these cases.

Again, you're missing the point.

If attackers are limited to launching DoS attacks using traceable
addresses, then not only can their zombies be traced & found, but
so can their controller (the perpetrator himself). Of this, make no
mistake.

>Finally, I am aware of new routers for which this sort of filtering
>would be child's play, but they are not yet deployed.  One ought not
>suggest that edge filtering is not being applied simply because of
>laziness on the part of ISPs.

Steve, you said that -- I didn't. I think ISP's will do what their
customers pay them to do.

- paul



From owner-ietf-outbound  Fri Feb 11 20:20:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA28160
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 20:20:02 -0500 (EST)
Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28023
	for <IETF@ietf.org>; Fri, 11 Feb 2000 20:14:25 -0500 (EST)
Received: from hermes.research.att.com (hermes.research.att.com [135.207.16.38])
	by mail-green.research.att.com (Postfix) with ESMTP
	id CFFCC1E00D; Fri, 11 Feb 2000 20:14:25 -0500 (EST)
Received: from SIGABA.research.att.com (sigaba.research.att.com [135.207.23.169])
	by hermes.research.att.com (8.8.7/8.8.7) with ESMTP id UAA13838;
	Fri, 11 Feb 2000 20:15:04 -0500 (EST)
Received: by SIGABA.research.att.com (Postfix, from userid 54047)
	id B614141F16; Fri, 11 Feb 2000 20:14:20 -0500 (EST)
Received: from roc (localhost [127.0.0.1])
	by SIGABA.research.att.com (Postfix) with ESMTP
	id A7075400B5; Fri, 11 Feb 2000 20:14:15 -0500 (EST)
X-Mailer: exmh version 2.1.1 10/15/1999
From: "Steven M. Bellovin" <smb@research.att.com>
To: Valdis.Kletnieks@vt.edu
Cc: Paul Ferguson <ferguson@cisco.com>, IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 11 Feb 2000 20:14:15 -0500
Sender: smb@research.att.com
Message-Id: <20000212011420.B614141F16@SIGABA.research.att.com>
X-Loop: ietf@ietf.org

In message <200002112224.e1BMO5917310@black-ice.cc.vt.edu>, Valdis.Kletnieks@vt
.edu writes:

> 
> Does anybody have statistics on how effective RFC2350 (Expectations
> for Computer Security Incident Response) was?  Or RFC2502 (Anti-Spam
> Recommendations for SMTP MTAs)? Or RFC2644 ( Changing the Default for
> Directed Broadcasts in Routers)?  It would seem reasonable that moving
> 2267 to BCP should have a similar effectiveness...

Well....  2267 is addressed more towards ISPs, and while there are certainly 
clueless ISPs out there, I suspect that on the average they're more clueful 
about the net than the typical end site.  (Obviously, there are exceptions in 
both categories; I did say *average*.)

		--Steve Bellovin




From owner-ietf-outbound@ietf.org  Fri Feb 11 20:21:30 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28218
	for <ietf-web-archive@odin.ietf.org>; Fri, 11 Feb 2000 20:21:30 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA05653;
	Fri, 11 Feb 2000 20:19:31 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id UAA28160
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 20:20:02 -0500 (EST)
Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28023
	for <IETF@ietf.org>; Fri, 11 Feb 2000 20:14:25 -0500 (EST)
Received: from hermes.research.att.com (hermes.research.att.com [135.207.16.38])
	by mail-green.research.att.com (Postfix) with ESMTP
	id CFFCC1E00D; Fri, 11 Feb 2000 20:14:25 -0500 (EST)
Received: from SIGABA.research.att.com (sigaba.research.att.com [135.207.23.169])
	by hermes.research.att.com (8.8.7/8.8.7) with ESMTP id UAA13838;
	Fri, 11 Feb 2000 20:15:04 -0500 (EST)
Received: by SIGABA.research.att.com (Postfix, from userid 54047)
	id B614141F16; Fri, 11 Feb 2000 20:14:20 -0500 (EST)
Received: from roc (localhost [127.0.0.1])
	by SIGABA.research.att.com (Postfix) with ESMTP
	id A7075400B5; Fri, 11 Feb 2000 20:14:15 -0500 (EST)
X-Mailer: exmh version 2.1.1 10/15/1999
From: "Steven M. Bellovin" <smb@research.att.com>
To: Valdis.Kletnieks@vt.edu
Cc: Paul Ferguson <ferguson@cisco.com>, IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 11 Feb 2000 20:14:15 -0500
Sender: smb@research.att.com
Message-Id: <20000212011420.B614141F16@SIGABA.research.att.com>
X-Loop: ietf@ietf.org

In message <200002112224.e1BMO5917310@black-ice.cc.vt.edu>, Valdis.Kletnieks@vt
.edu writes:

> 
> Does anybody have statistics on how effective RFC2350 (Expectations
> for Computer Security Incident Response) was?  Or RFC2502 (Anti-Spam
> Recommendations for SMTP MTAs)? Or RFC2644 ( Changing the Default for
> Directed Broadcasts in Routers)?  It would seem reasonable that moving
> 2267 to BCP should have a similar effectiveness...

Well....  2267 is addressed more towards ISPs, and while there are certainly 
clueless ISPs out there, I suspect that on the average they're more clueful 
about the net than the typical end site.  (Obviously, there are exceptions in 
both categories; I did say *average*.)

		--Steve Bellovin




From owner-ietf-outbound  Fri Feb 11 20:40:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA28674
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 20:40:02 -0500 (EST)
Received: from mailman.cisco.com (mailman.cisco.com [171.68.225.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28548
	for <ietf@ietf.org>; Fri, 11 Feb 2000 20:32:53 -0500 (EST)
Received: from bigger-dawgs (pferguso-isdn.cisco.com [171.70.114.134]) by mailman.cisco.com (8.8.8+Sun/CISCO.SERVER.1.2) with ESMTP id RAA14136 for <ietf@ietf.org>; Fri, 11 Feb 2000 17:32:22 -0800 (PST)
Message-Id: <4.2.2.20000211203058.00a4c160@lint.cisco.com>
X-Sender: pferguso@lint.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Fri, 11 Feb 2000 20:32:18 -0500
To: ietf@ietf.org
From: Paul Ferguson <ferguson@cisco.com>
Subject: [fwd] Lawyers Forsee Denial Of Service Suits 
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

It has begun. Sigh.

FYI,

- paul

http://www.techweb.com/wire/story/TWB20000211S0014




From owner-ietf-outbound@ietf.org  Fri Feb 11 20:41:38 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28744
	for <ietf-web-archive@odin.ietf.org>; Fri, 11 Feb 2000 20:41:38 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA06235;
	Fri, 11 Feb 2000 20:39:39 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id UAA28674
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 20:40:02 -0500 (EST)
Received: from mailman.cisco.com (mailman.cisco.com [171.68.225.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28548
	for <ietf@ietf.org>; Fri, 11 Feb 2000 20:32:53 -0500 (EST)
Received: from bigger-dawgs (pferguso-isdn.cisco.com [171.70.114.134]) by mailman.cisco.com (8.8.8+Sun/CISCO.SERVER.1.2) with ESMTP id RAA14136 for <ietf@ietf.org>; Fri, 11 Feb 2000 17:32:22 -0800 (PST)
Message-Id: <4.2.2.20000211203058.00a4c160@lint.cisco.com>
X-Sender: pferguso@lint.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Fri, 11 Feb 2000 20:32:18 -0500
To: ietf@ietf.org
From: Paul Ferguson <ferguson@cisco.com>
Subject: [fwd] Lawyers Forsee Denial Of Service Suits 
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

It has begun. Sigh.

FYI,

- paul

http://www.techweb.com/wire/story/TWB20000211S0014




From owner-ietf-outbound  Fri Feb 11 21:10:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA29374
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 21:10:02 -0500 (EST)
Received: from mailserver-ng.cs.umbc.edu (mailserver-ng.cs.umbc.edu [130.85.100.230])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29207
	for <IETF@ietf.org>; Fri, 11 Feb 2000 21:01:10 -0500 (EST)
Received: from localhost (wrath@localhost)
	by mailserver-ng.cs.umbc.edu (8.9.3/8.9.3) with SMTP id VAA18880;
	Fri, 11 Feb 2000 21:01:03 -0500 (EST)
Date: Fri, 11 Feb 2000 21:01:03 -0500 (EST)
From: Vijay Gill <wrath@cs.umbc.edu>
To: Paul Ferguson <ferguson@cisco.com>
cc: John Stracke <francis@ECAL.COM>, IETF@ietf.org, nanog@merit.edu
Subject: Re: Internet SYN Flooding, spoofing attacks
In-Reply-To: <4.2.2.20000211163625.00a4d770@lint.cisco.com>
Message-ID: <Pine.SOL.3.95.1000211205621.17799F-100000@mailserver-ng.cs.umbc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org


CC'd to NANOG, maybe we can move this there.

On Fri, 11 Feb 2000, Paul Ferguson wrote:

> It would allow the attacks to be traced back to the zombies (in
> the case of these DDoS attacks), and the perpetrators to be traced
> back and identified.

To make that easier, what is needed is something associated with a
downstream interface that is a part of the configuration itself, not a
separate access-list.  This makes it much easier to track on a large box
with many hundreds of customer links and so forth.

Something like so:

interface XXXm/n/p.q
description whatever customer
encaps ...
ip address x y
ip allow-source blocks-that-are-valid
ip allow-source ...more-blocks-

so on and so forth.

/vijay









From owner-ietf-outbound@ietf.org  Fri Feb 11 21:15:13 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29516
	for <ietf-web-archive@odin.ietf.org>; Fri, 11 Feb 2000 21:15:12 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA06921;
	Fri, 11 Feb 2000 21:13:14 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id VAA29374
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 21:10:02 -0500 (EST)
Received: from mailserver-ng.cs.umbc.edu (mailserver-ng.cs.umbc.edu [130.85.100.230])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29207
	for <IETF@ietf.org>; Fri, 11 Feb 2000 21:01:10 -0500 (EST)
Received: from localhost (wrath@localhost)
	by mailserver-ng.cs.umbc.edu (8.9.3/8.9.3) with SMTP id VAA18880;
	Fri, 11 Feb 2000 21:01:03 -0500 (EST)
Date: Fri, 11 Feb 2000 21:01:03 -0500 (EST)
From: Vijay Gill <wrath@cs.umbc.edu>
To: Paul Ferguson <ferguson@cisco.com>
cc: John Stracke <francis@ECAL.COM>, IETF@ietf.org, nanog@merit.edu
Subject: Re: Internet SYN Flooding, spoofing attacks
In-Reply-To: <4.2.2.20000211163625.00a4d770@lint.cisco.com>
Message-ID: <Pine.SOL.3.95.1000211205621.17799F-100000@mailserver-ng.cs.umbc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org


CC'd to NANOG, maybe we can move this there.

On Fri, 11 Feb 2000, Paul Ferguson wrote:

> It would allow the attacks to be traced back to the zombies (in
> the case of these DDoS attacks), and the perpetrators to be traced
> back and identified.

To make that easier, what is needed is something associated with a
downstream interface that is a part of the configuration itself, not a
separate access-list.  This makes it much easier to track on a large box
with many hundreds of customer links and so forth.

Something like so:

interface XXXm/n/p.q
description whatever customer
encaps ...
ip address x y
ip allow-source blocks-that-are-valid
ip allow-source ...more-blocks-

so on and so forth.

/vijay









From owner-ietf-outbound  Fri Feb 11 21:20:27 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA29612
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 21:20:02 -0500 (EST)
Received: from senie.com (anise.senie.com [199.125.85.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29214
	for <IETF@ietf.org>; Fri, 11 Feb 2000 21:01:50 -0500 (EST)
Received: from senie.com (anise.senie.com [199.125.85.28])
	by senie.com (8.8.7/8.8.7) with ESMTP id VAA06750;
	Fri, 11 Feb 2000 21:01:36 -0500
Message-ID: <38A4BEFE.5E57D6FE@senie.com>
Date: Fri, 11 Feb 2000 21:01:34 -0500
From: Daniel Senie <dts@senie.com>
Organization: Amaranth Networks Inc.
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Valdis.Kletnieks@vt.edu
CC: Paul Ferguson <ferguson@cisco.com>, IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
References: <009E5826.5FC1D447.198@process.com>
	            <4.2.2.20000211163325.00a50470@lint.cisco.com> <200002112224.e1BMO5917310@black-ice.cc.vt.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Valdis.Kletnieks@vt.edu wrote:
> 
> On Fri, 11 Feb 2000 16:35:18 EST, Paul Ferguson said:
> > Do you think that if RFC2267 was advanced as a BCP that
> > it would carry more weight, and therefore more ISP's would
> > implement RFC2267-style filtering? Coupled with the latest
> > denial of service attacks?
> 
> On the one hand, I think it would make a good candidate for BCP.  It seems
> to be similar in tone with RFCs 2502 and 2644.  I'd have to re-read it to
> see if it would need any textual changes, or if it's OK as it is.
> 
> I was talking to a co-worker on this topic, and his exact quote was
> "We have our s--t more together than most sites, despite our best
> efforts".  The problem is that he was right - our site may have clue,
> but there's a lot of uneducated sites out there.
> 
> Does anybody have statistics on how effective RFC2350 (Expectations
> for Computer Security Incident Response) was?  Or RFC2502 (Anti-Spam
> Recommendations for SMTP MTAs)? Or RFC2644 ( Changing the Default for
> Directed Broadcasts in Routers)?  It would seem reasonable that moving
> 2267 to BCP should have a similar effectiveness...

Ever since Paul and I wrote 2267, I've heard from ISPs and equipment
vendors, letting me know they'd implemented our recommendations. Lots of
folks are doing it because they understand they should do their part.

As for 2644, that one has only been out there a short time. It's not
clear how many people have noticed it yet. This document has two target
audiences, vendors and ISPs/users.

Some vendors made the change even before I wrote the document.  Router
Requirements (1812) have mandated devices have an on/off switch for this
feature for a long time. I would hope that all manufacturers at least
provided the config option. I hope the vendors who haven't changed their
defaults will get to this soon.

Many clueful network operators also took the time to ensure their
networks were clean. The problem with directed broadcasts is that EVERY
routing device really has to be checked, since with CIDR you really
don't know what comprises a broadcast. Network operators, especially,
need to spend the time to check the configurations on their equipment.
Awareness of this issue needs to be raised. As with ingress filtering,
everyone needs to do their part. Unfortunately, it may be threats of
negligence lawsuits that ultimately motivates some to take heed.

-- 
-----------------------------------------------------------------
Daniel Senie                                        dts@senie.com
Amaranth Networks Inc.            http://www.amaranthnetworks.com



From owner-ietf-outbound@ietf.org  Fri Feb 11 21:25:41 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29712
	for <ietf-web-archive@odin.ietf.org>; Fri, 11 Feb 2000 21:25:41 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA07033;
	Fri, 11 Feb 2000 21:23:42 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id VAA29612
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 21:20:02 -0500 (EST)
Received: from senie.com (anise.senie.com [199.125.85.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29214
	for <IETF@ietf.org>; Fri, 11 Feb 2000 21:01:50 -0500 (EST)
Received: from senie.com (anise.senie.com [199.125.85.28])
	by senie.com (8.8.7/8.8.7) with ESMTP id VAA06750;
	Fri, 11 Feb 2000 21:01:36 -0500
Message-ID: <38A4BEFE.5E57D6FE@senie.com>
Date: Fri, 11 Feb 2000 21:01:34 -0500
From: Daniel Senie <dts@senie.com>
Organization: Amaranth Networks Inc.
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Valdis.Kletnieks@vt.edu
CC: Paul Ferguson <ferguson@cisco.com>, IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
References: <009E5826.5FC1D447.198@process.com>
	            <4.2.2.20000211163325.00a50470@lint.cisco.com> <200002112224.e1BMO5917310@black-ice.cc.vt.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Valdis.Kletnieks@vt.edu wrote:
> 
> On Fri, 11 Feb 2000 16:35:18 EST, Paul Ferguson said:
> > Do you think that if RFC2267 was advanced as a BCP that
> > it would carry more weight, and therefore more ISP's would
> > implement RFC2267-style filtering? Coupled with the latest
> > denial of service attacks?
> 
> On the one hand, I think it would make a good candidate for BCP.  It seems
> to be similar in tone with RFCs 2502 and 2644.  I'd have to re-read it to
> see if it would need any textual changes, or if it's OK as it is.
> 
> I was talking to a co-worker on this topic, and his exact quote was
> "We have our s--t more together than most sites, despite our best
> efforts".  The problem is that he was right - our site may have clue,
> but there's a lot of uneducated sites out there.
> 
> Does anybody have statistics on how effective RFC2350 (Expectations
> for Computer Security Incident Response) was?  Or RFC2502 (Anti-Spam
> Recommendations for SMTP MTAs)? Or RFC2644 ( Changing the Default for
> Directed Broadcasts in Routers)?  It would seem reasonable that moving
> 2267 to BCP should have a similar effectiveness...

Ever since Paul and I wrote 2267, I've heard from ISPs and equipment
vendors, letting me know they'd implemented our recommendations. Lots of
folks are doing it because they understand they should do their part.

As for 2644, that one has only been out there a short time. It's not
clear how many people have noticed it yet. This document has two target
audiences, vendors and ISPs/users.

Some vendors made the change even before I wrote the document.  Router
Requirements (1812) have mandated devices have an on/off switch for this
feature for a long time. I would hope that all manufacturers at least
provided the config option. I hope the vendors who haven't changed their
defaults will get to this soon.

Many clueful network operators also took the time to ensure their
networks were clean. The problem with directed broadcasts is that EVERY
routing device really has to be checked, since with CIDR you really
don't know what comprises a broadcast. Network operators, especially,
need to spend the time to check the configurations on their equipment.
Awareness of this issue needs to be raised. As with ingress filtering,
everyone needs to do their part. Unfortunately, it may be threats of
negligence lawsuits that ultimately motivates some to take heed.

-- 
-----------------------------------------------------------------
Daniel Senie                                        dts@senie.com
Amaranth Networks Inc.            http://www.amaranthnetworks.com



From owner-ietf-outbound  Fri Feb 11 21:30:11 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA29791
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 21:30:03 -0500 (EST)
Received: from mailman.cisco.com (mailman.cisco.com [171.68.225.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29414
	for <IETF@ietf.org>; Fri, 11 Feb 2000 21:10:56 -0500 (EST)
Received: from bigger-dawgs (pferguso-isdn.cisco.com [171.70.114.134]) by mailman.cisco.com (8.8.8+Sun/CISCO.SERVER.1.2) with ESMTP id SAA20374; Fri, 11 Feb 2000 18:09:50 -0800 (PST)
Message-Id: <4.2.2.20000211210210.00a4e880@lint.cisco.com>
X-Sender: pferguso@lint.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Fri, 11 Feb 2000 21:09:47 -0500
To: Vijay Gill <wrath@cs.umbc.edu>
From: Paul Ferguson <ferguson@cisco.com>
Subject: Re: Internet SYN Flooding, spoofing attacks
Cc: John Stracke <francis@ECAL.COM>, IETF@ietf.org, nanog@merit.edu
In-Reply-To: <Pine.SOL.3.95.1000211205621.17799F-100000@mailserver-ng.cs
 .umbc.edu>
References: <4.2.2.20000211163625.00a4d770@lint.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

Vijay,

We (at least cisco, anyways) already have a knob for this:

  [no] ip verify unicast reverse-path

We call it Unicast RPF.

See also:

Craig Huegen's very useful web page on minimizing the effects
of DoS attacks:
http://users.quadrunner.com/chuegen/smurf.cgi

Cisco: Distributed Denial of Service (DDoS) News Flash,
February 9, 2000
http://www.cisco.com/warp/public/707/newsflash.html

Dave Dittrich's (University of Washington) very good
analysis of the recent DDoS attack tools.
http://www.washington.edu/People/dad/

NIPC (National Infrstructure Protection Center),
TRINOO/Tribal Flood Net/tfn2k stuff:
http://www.fbi.gov/nipc/trinoo.htm

"Handling A Distributed Denial of Service Trojan
Infection: Step-by-Step."
http://www.sans.org/y2k/DDoS.htm

CERT (Computer Emergency Response Team at CMU)
http://www.cert.org/

Cisco: Internet Security Advisories
http://www.cisco.com/warp/public/707/advisory.html

Characterizing and Tracing Packet Floods Using
Cisco Routers
http://www.cisco.com/warp/public/707/22.html

Cisco Product Security Incident Response (PSIRT)
http://www.cisco.com/warp/public/707/sec_incident_response.shtml

"Essential IOS" - Features Every ISP Should Consider
http://www.cisco.com/public/cons/isp/documents/IOSEssentialsPDF.zip

Know your enemy: Script Kiddies
http://www.enteract.com/~lspitz/enemy.html

Cisco Flow Logs and Intrusion Detection at the Ohio
State University
http://www.usenix.org/publications/login/1999-9/osu.html


If anyone else has useful links (it doesn't matter who
is the vendor, whatever), please let me know.

- paul

At 09:01 PM 02/11/2000 -0500, Vijay Gill wrote:

>CC'd to NANOG, maybe we can move this there.
>
>On Fri, 11 Feb 2000, Paul Ferguson wrote:
>
> > It would allow the attacks to be traced back to the zombies (in
> > the case of these DDoS attacks), and the perpetrators to be traced
> > back and identified.
>
>To make that easier, what is needed is something associated with a
>downstream interface that is a part of the configuration itself, not a
>separate access-list.  This makes it much easier to track on a large box
>with many hundreds of customer links and so forth.
>
>Something like so:
>
>interface XXXm/n/p.q
>description whatever customer
>encaps ...
>ip address x y
>ip allow-source blocks-that-are-valid
>ip allow-source ...more-blocks-
>
>so on and so forth.
>
>/vijay



From owner-ietf-outbound@ietf.org  Fri Feb 11 21:34:43 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29991
	for <ietf-web-archive@odin.ietf.org>; Fri, 11 Feb 2000 21:34:43 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA07195;
	Fri, 11 Feb 2000 21:32:44 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id VAA29791
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 21:30:03 -0500 (EST)
Received: from mailman.cisco.com (mailman.cisco.com [171.68.225.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29414
	for <IETF@ietf.org>; Fri, 11 Feb 2000 21:10:56 -0500 (EST)
Received: from bigger-dawgs (pferguso-isdn.cisco.com [171.70.114.134]) by mailman.cisco.com (8.8.8+Sun/CISCO.SERVER.1.2) with ESMTP id SAA20374; Fri, 11 Feb 2000 18:09:50 -0800 (PST)
Message-Id: <4.2.2.20000211210210.00a4e880@lint.cisco.com>
X-Sender: pferguso@lint.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Fri, 11 Feb 2000 21:09:47 -0500
To: Vijay Gill <wrath@cs.umbc.edu>
From: Paul Ferguson <ferguson@cisco.com>
Subject: Re: Internet SYN Flooding, spoofing attacks
Cc: John Stracke <francis@ECAL.COM>, IETF@ietf.org, nanog@merit.edu
In-Reply-To: <Pine.SOL.3.95.1000211205621.17799F-100000@mailserver-ng.cs
 .umbc.edu>
References: <4.2.2.20000211163625.00a4d770@lint.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

Vijay,

We (at least cisco, anyways) already have a knob for this:

  [no] ip verify unicast reverse-path

We call it Unicast RPF.

See also:

Craig Huegen's very useful web page on minimizing the effects
of DoS attacks:
http://users.quadrunner.com/chuegen/smurf.cgi

Cisco: Distributed Denial of Service (DDoS) News Flash,
February 9, 2000
http://www.cisco.com/warp/public/707/newsflash.html

Dave Dittrich's (University of Washington) very good
analysis of the recent DDoS attack tools.
http://www.washington.edu/People/dad/

NIPC (National Infrstructure Protection Center),
TRINOO/Tribal Flood Net/tfn2k stuff:
http://www.fbi.gov/nipc/trinoo.htm

"Handling A Distributed Denial of Service Trojan
Infection: Step-by-Step."
http://www.sans.org/y2k/DDoS.htm

CERT (Computer Emergency Response Team at CMU)
http://www.cert.org/

Cisco: Internet Security Advisories
http://www.cisco.com/warp/public/707/advisory.html

Characterizing and Tracing Packet Floods Using
Cisco Routers
http://www.cisco.com/warp/public/707/22.html

Cisco Product Security Incident Response (PSIRT)
http://www.cisco.com/warp/public/707/sec_incident_response.shtml

"Essential IOS" - Features Every ISP Should Consider
http://www.cisco.com/public/cons/isp/documents/IOSEssentialsPDF.zip

Know your enemy: Script Kiddies
http://www.enteract.com/~lspitz/enemy.html

Cisco Flow Logs and Intrusion Detection at the Ohio
State University
http://www.usenix.org/publications/login/1999-9/osu.html


If anyone else has useful links (it doesn't matter who
is the vendor, whatever), please let me know.

- paul

At 09:01 PM 02/11/2000 -0500, Vijay Gill wrote:

>CC'd to NANOG, maybe we can move this there.
>
>On Fri, 11 Feb 2000, Paul Ferguson wrote:
>
> > It would allow the attacks to be traced back to the zombies (in
> > the case of these DDoS attacks), and the perpetrators to be traced
> > back and identified.
>
>To make that easier, what is needed is something associated with a
>downstream interface that is a part of the configuration itself, not a
>separate access-list.  This makes it much easier to track on a large box
>with many hundreds of customer links and so forth.
>
>Something like so:
>
>interface XXXm/n/p.q
>description whatever customer
>encaps ...
>ip address x y
>ip allow-source blocks-that-are-valid
>ip allow-source ...more-blocks-
>
>so on and so forth.
>
>/vijay



From owner-ietf-outbound  Fri Feb 11 21:40:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA00153
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 21:40:03 -0500 (EST)
Received: from mailserver-ng.cs.umbc.edu (mailserver-ng.cs.umbc.edu [130.85.100.230])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29490
	for <IETF@ietf.org>; Fri, 11 Feb 2000 21:14:10 -0500 (EST)
Received: from localhost (wrath@localhost)
	by mailserver-ng.cs.umbc.edu (8.9.3/8.9.3) with SMTP id VAA19070;
	Fri, 11 Feb 2000 21:14:08 -0500 (EST)
Date: Fri, 11 Feb 2000 21:14:08 -0500 (EST)
From: Vijay Gill <wrath@cs.umbc.edu>
To: Paul Ferguson <ferguson@cisco.com>
cc: John Stracke <francis@ECAL.COM>, IETF@ietf.org, nanog@merit.edu
Subject: Re: Internet SYN Flooding, spoofing attacks
In-Reply-To: <4.2.2.20000211210210.00a4e880@lint.cisco.com>
Message-ID: <Pine.SOL.3.95.1000211211047.17799G-100000@mailserver-ng.cs.umbc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Fri, 11 Feb 2000, Paul Ferguson wrote:

> Vijay,
> 
> We (at least cisco, anyways) already have a knob for this:
> 
>   [no] ip verify unicast reverse-path
> 
> We call it Unicast RPF.

This only works on single homed customers. Due to asymmetric routing, the
customer can source _valid_ ip addresses from an ip source address that is
not routed over that interface.  I too would prefer some sort of magic
unicast RPF, but the best compromise is the built-in access filter.  The
solution must be general enough to work for multihomed, defaulting out
customers with blocks from n providers,

/vijay


> See also:
> 
> Craig Huegen's very useful web page on minimizing the effects
> of DoS attacks:
> http://users.quadrunner.com/chuegen/smurf.cgi
> 
> Cisco: Distributed Denial of Service (DDoS) News Flash,
> February 9, 2000
> http://www.cisco.com/warp/public/707/newsflash.html
> 
> Dave Dittrich's (University of Washington) very good
> analysis of the recent DDoS attack tools.
> http://www.washington.edu/People/dad/
> 
> NIPC (National Infrstructure Protection Center),
> TRINOO/Tribal Flood Net/tfn2k stuff:
> http://www.fbi.gov/nipc/trinoo.htm
> 
> "Handling A Distributed Denial of Service Trojan
> Infection: Step-by-Step."
> http://www.sans.org/y2k/DDoS.htm
> 
> CERT (Computer Emergency Response Team at CMU)
> http://www.cert.org/
> 
> Cisco: Internet Security Advisories
> http://www.cisco.com/warp/public/707/advisory.html
> 
> Characterizing and Tracing Packet Floods Using
> Cisco Routers
> http://www.cisco.com/warp/public/707/22.html
> 
> Cisco Product Security Incident Response (PSIRT)
> http://www.cisco.com/warp/public/707/sec_incident_response.shtml
> 
> "Essential IOS" - Features Every ISP Should Consider
> http://www.cisco.com/public/cons/isp/documents/IOSEssentialsPDF.zip
> 
> Know your enemy: Script Kiddies
> http://www.enteract.com/~lspitz/enemy.html
> 
> Cisco Flow Logs and Intrusion Detection at the Ohio
> State University
> http://www.usenix.org/publications/login/1999-9/osu.html
> 
> 
> If anyone else has useful links (it doesn't matter who
> is the vendor, whatever), please let me know.
> 
> - paul
> 
> At 09:01 PM 02/11/2000 -0500, Vijay Gill wrote:
> 
> >CC'd to NANOG, maybe we can move this there.
> >
> >On Fri, 11 Feb 2000, Paul Ferguson wrote:
> >
> > > It would allow the attacks to be traced back to the zombies (in
> > > the case of these DDoS attacks), and the perpetrators to be traced
> > > back and identified.
> >
> >To make that easier, what is needed is something associated with a
> >downstream interface that is a part of the configuration itself, not a
> >separate access-list.  This makes it much easier to track on a large box
> >with many hundreds of customer links and so forth.
> >
> >Something like so:
> >
> >interface XXXm/n/p.q
> >description whatever customer
> >encaps ...
> >ip address x y
> >ip allow-source blocks-that-are-valid
> >ip allow-source ...more-blocks-
> >
> >so on and so forth.
> >
> >/vijay
> 
> 

Vijay Gill                         |The (paying) customer is always right.
wrath@cs.umbc.edu, vijay@umbc.edu  |                  - Piercarlo Grandi
http://www.gl.umbc.edu/~vijay      | Eagles may soar, but weasels don't get
These are my opinions only.        | sucked into jet engines.



From owner-ietf-outbound@ietf.org  Fri Feb 11 21:44:47 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA00494
	for <ietf-web-archive@odin.ietf.org>; Fri, 11 Feb 2000 21:44:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA07286;
	Fri, 11 Feb 2000 21:42:48 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id VAA00153
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 21:40:03 -0500 (EST)
Received: from mailserver-ng.cs.umbc.edu (mailserver-ng.cs.umbc.edu [130.85.100.230])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29490
	for <IETF@ietf.org>; Fri, 11 Feb 2000 21:14:10 -0500 (EST)
Received: from localhost (wrath@localhost)
	by mailserver-ng.cs.umbc.edu (8.9.3/8.9.3) with SMTP id VAA19070;
	Fri, 11 Feb 2000 21:14:08 -0500 (EST)
Date: Fri, 11 Feb 2000 21:14:08 -0500 (EST)
From: Vijay Gill <wrath@cs.umbc.edu>
To: Paul Ferguson <ferguson@cisco.com>
cc: John Stracke <francis@ECAL.COM>, IETF@ietf.org, nanog@merit.edu
Subject: Re: Internet SYN Flooding, spoofing attacks
In-Reply-To: <4.2.2.20000211210210.00a4e880@lint.cisco.com>
Message-ID: <Pine.SOL.3.95.1000211211047.17799G-100000@mailserver-ng.cs.umbc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Fri, 11 Feb 2000, Paul Ferguson wrote:

> Vijay,
> 
> We (at least cisco, anyways) already have a knob for this:
> 
>   [no] ip verify unicast reverse-path
> 
> We call it Unicast RPF.

This only works on single homed customers. Due to asymmetric routing, the
customer can source _valid_ ip addresses from an ip source address that is
not routed over that interface.  I too would prefer some sort of magic
unicast RPF, but the best compromise is the built-in access filter.  The
solution must be general enough to work for multihomed, defaulting out
customers with blocks from n providers,

/vijay


> See also:
> 
> Craig Huegen's very useful web page on minimizing the effects
> of DoS attacks:
> http://users.quadrunner.com/chuegen/smurf.cgi
> 
> Cisco: Distributed Denial of Service (DDoS) News Flash,
> February 9, 2000
> http://www.cisco.com/warp/public/707/newsflash.html
> 
> Dave Dittrich's (University of Washington) very good
> analysis of the recent DDoS attack tools.
> http://www.washington.edu/People/dad/
> 
> NIPC (National Infrstructure Protection Center),
> TRINOO/Tribal Flood Net/tfn2k stuff:
> http://www.fbi.gov/nipc/trinoo.htm
> 
> "Handling A Distributed Denial of Service Trojan
> Infection: Step-by-Step."
> http://www.sans.org/y2k/DDoS.htm
> 
> CERT (Computer Emergency Response Team at CMU)
> http://www.cert.org/
> 
> Cisco: Internet Security Advisories
> http://www.cisco.com/warp/public/707/advisory.html
> 
> Characterizing and Tracing Packet Floods Using
> Cisco Routers
> http://www.cisco.com/warp/public/707/22.html
> 
> Cisco Product Security Incident Response (PSIRT)
> http://www.cisco.com/warp/public/707/sec_incident_response.shtml
> 
> "Essential IOS" - Features Every ISP Should Consider
> http://www.cisco.com/public/cons/isp/documents/IOSEssentialsPDF.zip
> 
> Know your enemy: Script Kiddies
> http://www.enteract.com/~lspitz/enemy.html
> 
> Cisco Flow Logs and Intrusion Detection at the Ohio
> State University
> http://www.usenix.org/publications/login/1999-9/osu.html
> 
> 
> If anyone else has useful links (it doesn't matter who
> is the vendor, whatever), please let me know.
> 
> - paul
> 
> At 09:01 PM 02/11/2000 -0500, Vijay Gill wrote:
> 
> >CC'd to NANOG, maybe we can move this there.
> >
> >On Fri, 11 Feb 2000, Paul Ferguson wrote:
> >
> > > It would allow the attacks to be traced back to the zombies (in
> > > the case of these DDoS attacks), and the perpetrators to be traced
> > > back and identified.
> >
> >To make that easier, what is needed is something associated with a
> >downstream interface that is a part of the configuration itself, not a
> >separate access-list.  This makes it much easier to track on a large box
> >with many hundreds of customer links and so forth.
> >
> >Something like so:
> >
> >interface XXXm/n/p.q
> >description whatever customer
> >encaps ...
> >ip address x y
> >ip allow-source blocks-that-are-valid
> >ip allow-source ...more-blocks-
> >
> >so on and so forth.
> >
> >/vijay
> 
> 

Vijay Gill                         |The (paying) customer is always right.
wrath@cs.umbc.edu, vijay@umbc.edu  |                  - Piercarlo Grandi
http://www.gl.umbc.edu/~vijay      | Eagles may soar, but weasels don't get
These are my opinions only.        | sucked into jet engines.



From owner-ietf-outbound  Fri Feb 11 21:50:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA01756
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 21:50:04 -0500 (EST)
Received: from mailman.cisco.com (mailman.cisco.com [171.68.225.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29624
	for <IETF@ietf.org>; Fri, 11 Feb 2000 21:20:15 -0500 (EST)
Received: from bigger-dawgs (pferguso-isdn.cisco.com [171.70.114.134]) by mailman.cisco.com (8.8.8+Sun/CISCO.SERVER.1.2) with ESMTP id SAA21876; Fri, 11 Feb 2000 18:19:12 -0800 (PST)
Message-Id: <4.2.2.20000211211503.00a53bb0@lint.cisco.com>
X-Sender: pferguso@lint.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Fri, 11 Feb 2000 21:19:09 -0500
To: Vijay Gill <wrath@cs.umbc.edu>
From: Paul Ferguson <ferguson@cisco.com>
Subject: Re: Internet SYN Flooding, spoofing attacks
Cc: John Stracke <francis@ECAL.COM>, IETF@ietf.org, nanog@merit.edu
In-Reply-To: <Pine.SOL.3.95.1000211211047.17799G-100000@mailserver-ng.cs
 .umbc.edu>
References: <4.2.2.20000211210210.00a4e880@lint.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 09:14 PM 02/11/2000 -0500, Vijay Gill wrote:

>This only works on single homed customers. Due to asymmetric routing, the
>customer can source _valid_ ip addresses from an ip source address that is
>not routed over that interface.  I too would prefer some sort of magic
>unicast RPF, but the best compromise is the built-in access filter.  The
>solution must be general enough to work for multihomed, defaulting out
>customers with blocks from n providers,

No, that is a common misconception, or rather, an overstatement of
a pretty easily described situation. It only breaks things in transit
situations, and only in transit situations where you might not have
the same forwarding path back to the source as you would via the same
interface a packet came in on.

This is a small percentage, I would thing, since the percentage of
ISP's offering transit pales in comparison to all other "access"
ISP's that do not. And in cases where ISP's _do_ offer transit, or
have transit agreements, will they really do this on their transit
interfaces? I think not.

- paul



From owner-ietf-outbound@ietf.org  Fri Feb 11 21:51:28 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01905
	for <ietf-web-archive@odin.ietf.org>; Fri, 11 Feb 2000 21:51:28 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA07347;
	Fri, 11 Feb 2000 21:49:31 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id VAA01756
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 21:50:04 -0500 (EST)
Received: from mailman.cisco.com (mailman.cisco.com [171.68.225.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29624
	for <IETF@ietf.org>; Fri, 11 Feb 2000 21:20:15 -0500 (EST)
Received: from bigger-dawgs (pferguso-isdn.cisco.com [171.70.114.134]) by mailman.cisco.com (8.8.8+Sun/CISCO.SERVER.1.2) with ESMTP id SAA21876; Fri, 11 Feb 2000 18:19:12 -0800 (PST)
Message-Id: <4.2.2.20000211211503.00a53bb0@lint.cisco.com>
X-Sender: pferguso@lint.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Fri, 11 Feb 2000 21:19:09 -0500
To: Vijay Gill <wrath@cs.umbc.edu>
From: Paul Ferguson <ferguson@cisco.com>
Subject: Re: Internet SYN Flooding, spoofing attacks
Cc: John Stracke <francis@ECAL.COM>, IETF@ietf.org, nanog@merit.edu
In-Reply-To: <Pine.SOL.3.95.1000211211047.17799G-100000@mailserver-ng.cs
 .umbc.edu>
References: <4.2.2.20000211210210.00a4e880@lint.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 09:14 PM 02/11/2000 -0500, Vijay Gill wrote:

>This only works on single homed customers. Due to asymmetric routing, the
>customer can source _valid_ ip addresses from an ip source address that is
>not routed over that interface.  I too would prefer some sort of magic
>unicast RPF, but the best compromise is the built-in access filter.  The
>solution must be general enough to work for multihomed, defaulting out
>customers with blocks from n providers,

No, that is a common misconception, or rather, an overstatement of
a pretty easily described situation. It only breaks things in transit
situations, and only in transit situations where you might not have
the same forwarding path back to the source as you would via the same
interface a packet came in on.

This is a small percentage, I would thing, since the percentage of
ISP's offering transit pales in comparison to all other "access"
ISP's that do not. And in cases where ISP's _do_ offer transit, or
have transit agreements, will they really do this on their transit
interfaces? I think not.

- paul



From owner-ietf-outbound  Fri Feb 11 22:03:51 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA02215
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 22:03:45 -0500 (EST)
Received: from cardinal.prod.itd.earthlink.net (cardinal.prod.itd.earthlink.net [207.217.121.154])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01034
	for <ietf@ietf.org>; Fri, 11 Feb 2000 21:47:59 -0500 (EST)
Received: from [38.26.139.190] (ipa16.trenton2.nj.pub-ip.psi.net [38.26.139.16])
	by cardinal.prod.itd.earthlink.net (8.9.3/8.9.3) with ESMTP id SAA23574
	for <ietf@ietf.org>; Fri, 11 Feb 2000 18:47:56 -0800 (PST)
Mime-Version: 1.0
X-Sender: cook@pop3.netaxs.com
Message-Id: <v0421010bb4ca730431d9@[38.26.139.190]>
Date: Fri, 11 Feb 2000 21:47:53 -0500
To: ietf@ietf.org
From: Gordon Cook <cook@cookreport.com>
Subject: March COOK report Summary ONLY /Diff serv interview  and 10 Gig E
 standards/
Content-Type: text/plain; charset="iso-8859-1" ; format="flowed"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id VAA01034
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

GIGABIT ETHERNET RIDES ECONOMY OF SCALE
AS IT ERASES LAN WAN BOUNDARY GIGABIT ETHERNET MAKES NETWORK LESS 
COMPLEX, EASIER TO MANAGE -- 10 GIG STANDARDS WILL DEMAND CHOICES 
AFFECTING ATM SONET WAN FUNCTIONALITY, pp. 1- 10


We interviewed Dan Dov Principal Engineer for LAN physical Layers 
with Hewlett-Packard's networks division and Mark Thompson product 
marketing manager for HP's ProCurve Networking Business on December 
6. In Smart Letter 30 on 12/9/99 David Isenberg wrote the following 
very good summary of why Gigabit Ethernet is hot. "Since there are 
many more LANs than WANs, GigE, due to its Ethernet LAN heritage, has 
huge economies of scale. (Every flavor of Ethernet that has hit the 
marketplace has slid down a 30% per year price reduction curve.) 
GigE's use in both LAN and WAN gives greater scale yet. Plus by 
erasing the LAN/WAN boundary, GigE decreases the complexity of the 
network, making it even stupider, easier to manage and easier to 
innovate upon. So it looks like the Stupid Network will be built of 
GigE over glass."

In the Interview Dov takes us through the technology reasons for 
Ethernet's increase in speed as its importance in LANs has grown and 
LANs themselves get larger and more bandwidth hungry.  Ethernet, in 
short, is leveraging its ubiquity, low cost and open standards on the 
back of the growing importance of the Internet and its increased 
bandwidth. In doing so it is playing a significant role in making new 
industries like Application Service provision possible.

Dov concludes that "the reason that the Ethernet succeeded as well as 
it has, its simplicity. Ethernet is a very simple, yet elegant 
protocol. But because of its simplicity, it's extremely inexpensive 
to develop and to manufacture Ethernet-compliant devices." Many 
people are taking gigabit Ethernet and applying it to wide area 
networking because of its simplicity, ease of access and simplicity 
of its framing.

In its relationship between volume and pricing Gigabit Ethernet 
offers significant values. Gigabit Ethernet initially was being 
installed in the local area network to provide interconnection 
between boxes that were connecting 100 megabits, and 10megabits, to 
the desktop. The volume of that kind of traffic quickly becomes very 
large. For these applications over short distances, compared to 
OC-24, gigabit Ethernet is actually cheaper, even though it provides 
more bandwidth. What people started to realize, because of the volume 
of gigabit Ethernet traffic that was going out and the relative 
simplicity of it, the cost of gigabit Ethernet ran under cut that of 
OC-24 pretty quickly. And the result is that people who are making 
the decisions as to what will be used to hook LANs to each other and 
to the Internet started deciding  to go with gigabit Ethernet, rather 
than with the OC-24 or OC-48. Gigabit  Ethernet's application is at 
the periphery of the internet  Therefore it is not being looked tofor 
the elimination of SONET add/drop multiplexers.

With ten gigabit Ethernet some people are proposing to basically take 
the ten gigabit Ethernet media access controller, the MAC, and 
packetize the data, just like we currently do in Ethernet at ten 
times the rate. But they then want to send it into a SONET framer. 
The SONET framer will then take that data and chop it up and put it 
into the SONET frame. The framer will send it across the network and 
when it gets received on the other side, it will be effectively 
deframed.  There are also people that are more focused on taking the 
current, simple Ethernet approach, which is just, take the data, put 
it onto an optical fiber and ship it on across the link. They don't 
want to get into the complexity of SONET framing and so on.

HP's Thompson offered the following analogy: " It's sort of like the 
subway system versus the inter city train system. Once, historically, 
if you wanted to ride the "train" from the center of one city to the 
center of another, you rode the subway system to get out to the train 
station, took a train and then subway back into a city. So what we're 
talking about now is Ethernet making it robust enough and fast enough 
so that your subway car can simply ride from one city to the next and 
that you don't have to change the vehicles that are riding on the 
tracks, the fiber, in the meantime."  In other words a  simplistic 
design that would work for the people who are working in the local 
area networks would also go for people who wanted to do optical 
transmission with Ethernet framing cross-country"  The interview 
concludes with a discussion of the issues being faced in the 
development of 10 gigabit Ethernet standards.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

EXPLOSION IN CAPACITY CHASED BY EXPLOSION IN USE
FIBER TO THE HOME FROM HP ORACLE AND POWER COMPANIES FOR LESS THAN 
$15 A MONTH -- ABOVENET ON THE NEED TO OWN FIBER
		pp. 10, 27


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ROLE OF DIFFSERV IN THE DEVELOPMENT OF QOS TOOLS
KATHY NICHOLS EXPLAINS HOW PURSUIT OF VIABLE QOS PROTOCOLS IS
TRANSITIONING FROM CENTRALIZED MODEL TO HORIZONTALLY ORGANIZED TOOL 
CHEST FROM WHICH ISPS CAN DESIGN CROSS ISP COMPATIBLE SERVICES, 
	pp. 11-19, 27


On November 16, we interviewed Kathy Nichols who with Brian Carpenter 
is co-chair of the very active Diffserv working group.  We asked 
Kathy to put Diffserv in its historical context.  She replied that 
originally people assumed that Quality of Service guarantees would be 
needed to do multimedia over the Internet.  Integrated Services and 
RSVP came out of these assumptions.  But RSVP had been designed by 
Lixia Zhang and others while Lixia was at Xerox Parc. The design was 
made with the assumption that you could put RSVP state into every 
router because you would always keep your application inside the 
network of a single provider.  After several years of experimentation 
the emerging view is that RSVP should be seen as a generic signaling 
protocol or a way for a host to talk to a network.  Other protocols 
would govern ways that hosts request things of a network to which 
they are talking.  One should note that the original work with RSVP 
and Intserv was done before April 1995 when the NSFNet backbone was 
shut off and when the topology and traffic on the internet to which 
people were thinking about applying quality of service were radically 
different that what they are now (almost exactly five years later).

By the beginning of 1997 some ISPs were beginning to talk of QoS in 
terms of being able to give some of the traffic that they carried 
better treatment than other traffic a kind of better best effort. 
According to Kathy "the Differentiated Services discussion happened 
because some service providers were not happy with the Intserv 
approach. They weren't going to let state cross their boundary. They 
didn't see how something with that much state could work. And it also 
didn't seem to do exactly what they wanted, which included to be able 
to tell a customer that they could replace their leased line and give 
them at least equivalent service. And it would be a good deal, 
because they should be able to offer it cheaper and reuse their 
infrastructure."

Traffic for a premium class of service could be relegated into 
special queues for that traffic alone.  Traffic for best effort and 
better best effort could remain in the same queue.  In most network 
conditions the packets would be treated the same while in exceptional 
conditions the mere best effort packets might find themselves 
discriminated against.  Some of the very best engineers and protocol 
designers in the Internet were coming up with schemes for how to do 
traffic marking and shaping to accomplish these goals. (The idea that 
the same queue can be used to have two different levels of service is 
the idea behind weighted RED.) Unfortunately their schemes - call 
them tools perhaps - were too often incompatible with each other. 
People were designing complex tools to work handle vast amounts of 
traffic in complex and rapidly changing situations.  Diffserv was 
started as a way to bring order out of a very complex chaos.  People 
wanted to structure a framework for which people could design their 
tools and to create a situation where if they designed them to be 
compatible with the framework they would be compatible and 
interoperable with each other.  Diffserv may be thought of as a set 
of guidelines within which various quality of service tools may be 
implemented.

Kathy states that the only way to scale QoS is to aggregate packets. 
If we group them inside of a "cloud" or domain, we will put them into 
something called a "behavior aggregate."  You create a behavior 
aggregate by saying that you will assign each packet that is to be a 
member of that aggregate a particular per hop behavior (PHB).  PHB 
permits the assigning of the same forwarding treatment for all 
network traffic that labeled with a given PHB.  You may then consider 
telling customers that they will pay a certain rate for traffic sent 
in conformance with the PHB aggregate they have purchased and let 
them know that  your routers will drop traffic labelled as conformant 
with a given PHB that in reality is found by the router to be non 
conformant.  One goal is to get the maximum amount of classification 
of what may be done with traffic out of a field that is no more than 
6 bits per packet.  What Diffserv is really doing for  ISPs and for 
hardware vendor is helping them to work together to establish 
reasonable guidelines within which many different quality of service 
provisions can  created.  The idea is that the ISP is allowed to 
establish its own QoS offerings.  Diffserv has created behavior 
aggregates and control planes that can be used to implement the 
policy goals of the behavior aggregate.  Two ISP may be able to solve 
cross ISP policy issues by sitting down with each other and selecting 
Diffserv compatible tools that would not have to be the exact same 
tool.  It is Diffserv's intention to give them tools by which they 
can achieve common QoS outcomes by means that inside their respective 
networks may be quite different.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

ALL RESPONSIBILITY DISINTERMEDIATED FROM DNS FIX
NEW ICANN DOC SHARED REGISTRY SYSTEM ENABLES REGISTRARS, SHARED 
REGISTRY AND ICANN TO DISCLAIM RESPONSIBILITY FOR ALL ACTIONS THAT 
INJURE REGISTRANTS        pp. 20 - 26

In mid January Wired 
http://www.wired.com/news/technology/0,1282,33753,00.html published a 
delightful summary of the results of Beckwith Burr', ICANN's, and 
NSI's redesign of the DNS system.  People were buying a domain name 
and paying for it at the time of purchase only to see it sold out 
from underneath them the very next day to someone else. For the 
little guy the Internet's domain name system had been put at risk by 
the Clinton Gore bureaucrats. No mater: the large, powerful and rich 
had the ICANN uniform dispute resolution policy and the even more 
Draconian cyber squatting legislation. ICANN had done a superb job of 
freeing the corporate trademark attorneys to do their thing. It had 
done this by creating a jury-rigged system where registrars could say 
that mistakes belonged to the registry which in turn could say it was 
playing by ICANN rules while ICANN disclaimed all responsibility for 
breakages in the system.

According to Wired, "ICANN said it was not responsible for domain 
name discrepancies between registrars and their customers.

The COOK Report reminds its readers that to be functional a domain 
name must be part of the registry database that determines what other 
names are taken and is responsible for getting the names into the 
root servers where down line DNS servers can find them.  The 
operation of the new system has been rigged by ICANN so that, while 
the registry gets names to advertise, it gets no information about 
the owners of the names in whose interest it is doing the 
advertisement.  This information is known to the Registrars whose 
agreements with ICANN give them enforceable rights vis-ā-vis the 
Registry. But the customers who pay a registrar to act as the 
intermediary between them and the registry have no enforceable rights 
what so ever to the use of the domain names for which they pay.

We do not  know  who designed and  put in place this truly bizarre 
system.  It was ICANN but the secret process by which it was done 
inside of ICANN has remained opaque to everyone on the outside.  As 
far as we can tell, ICANN rules by having its Jones Day attorneys, 
Touton and Sims work with Esther Dyson and Mike Roberts to establish 
policy that disenfranchises every Internet user (who does not also 
pay the necessary fees to become a registrar) of any rights to 
receive the benefits of the products for which they have paid. The 
registrar is fee to do anything it chooses with the domain name that 
it sells to the registrant.  The system is also dependent for its 
operation on a shared registry protocol that has been (according to 
the testimony of some outside experts who advised NSI on its design) 
implemented in such a way as to make any accountability to the 
registrants and even to the registrars unlikely.  NSI has sought what 
non experts will take as endorsement from the IETF by asking for 
publication of the protocol as an informational RFC.  One of the 
experts who advised NSI in the design has protested loudly against 
the move and asked NSI to free him from his non disclosure agreement 
so that he may publish his criticism to allow independent observers 
to make their own judgements.  NSI has refused.

By the end of the month it was clear that the entire shared registry 
system was a design failure. As early as late December complaints of 
break downs were becoming evident. On December 23 on the Domain 
policy list at NSI list member "A" complained " Most whois clients 
query the public NSI Registry database first which only updates *once 
per day* so it's quite possible for someone to do a domain query and 
be shown the old whois information of the old registrar. Nothing is 
wrong.

To which list member "B" replied: No, nothing is wrong as far as the 
design goes. But of course that [just looking at the design] is not 
far enough, is it? Therefore leaving the ability for registrars to 
"Steal" domain names and/or create a domain name conflict from the 
get go. Doesn't say much for stability, does it?  Our article 
summarizes debate from the IETF and Domain Policy lists that makes 
quite clear the absurdity that the White House and its ice president 
is visiting upon the Internet.

Froomkin & Auerbach Offer ICANN Bitter Criticism, pp. 27, 29, 30

Two who have tried to work with ICANN say foul in no uncertain and 
bitter terms to move by DNSO to censor DNSO GA mail list.  ICANN 
Makes it clear it will tolerate no criticism.

****************************************************************
The COOK Report on Internet      Index to 8 years of the COOK  Report
431 Greenway Ave, Ewing, NJ 08618 USA  http://cookreport.com
(609) 882-2572 (phone & fax)             Battle for Cyberspace: How
cook@cookreport.com                     Crucial Technical . . . - 392 pages
just published. See  http://cookreport.com/ipbattle.shtml
****************************************************************



From owner-ietf-outbound@ietf.org  Fri Feb 11 22:08:36 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02316
	for <ietf-web-archive@odin.ietf.org>; Fri, 11 Feb 2000 22:08:32 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA07624;
	Fri, 11 Feb 2000 22:06:32 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id WAA02215
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 22:03:45 -0500 (EST)
Received: from cardinal.prod.itd.earthlink.net (cardinal.prod.itd.earthlink.net [207.217.121.154])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01034
	for <ietf@ietf.org>; Fri, 11 Feb 2000 21:47:59 -0500 (EST)
Received: from [38.26.139.190] (ipa16.trenton2.nj.pub-ip.psi.net [38.26.139.16])
	by cardinal.prod.itd.earthlink.net (8.9.3/8.9.3) with ESMTP id SAA23574
	for <ietf@ietf.org>; Fri, 11 Feb 2000 18:47:56 -0800 (PST)
Mime-Version: 1.0
X-Sender: cook@pop3.netaxs.com
Message-Id: <v0421010bb4ca730431d9@[38.26.139.190]>
Date: Fri, 11 Feb 2000 21:47:53 -0500
To: ietf@ietf.org
From: Gordon Cook <cook@cookreport.com>
Subject: March COOK report Summary ONLY /Diff serv interview  and 10 Gig E
 standards/
Content-Type: text/plain; charset="iso-8859-1" ; format="flowed"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id VAA01034
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

GIGABIT ETHERNET RIDES ECONOMY OF SCALE
AS IT ERASES LAN WAN BOUNDARY GIGABIT ETHERNET MAKES NETWORK LESS 
COMPLEX, EASIER TO MANAGE -- 10 GIG STANDARDS WILL DEMAND CHOICES 
AFFECTING ATM SONET WAN FUNCTIONALITY, pp. 1- 10


We interviewed Dan Dov Principal Engineer for LAN physical Layers 
with Hewlett-Packard's networks division and Mark Thompson product 
marketing manager for HP's ProCurve Networking Business on December 
6. In Smart Letter 30 on 12/9/99 David Isenberg wrote the following 
very good summary of why Gigabit Ethernet is hot. "Since there are 
many more LANs than WANs, GigE, due to its Ethernet LAN heritage, has 
huge economies of scale. (Every flavor of Ethernet that has hit the 
marketplace has slid down a 30% per year price reduction curve.) 
GigE's use in both LAN and WAN gives greater scale yet. Plus by 
erasing the LAN/WAN boundary, GigE decreases the complexity of the 
network, making it even stupider, easier to manage and easier to 
innovate upon. So it looks like the Stupid Network will be built of 
GigE over glass."

In the Interview Dov takes us through the technology reasons for 
Ethernet's increase in speed as its importance in LANs has grown and 
LANs themselves get larger and more bandwidth hungry.  Ethernet, in 
short, is leveraging its ubiquity, low cost and open standards on the 
back of the growing importance of the Internet and its increased 
bandwidth. In doing so it is playing a significant role in making new 
industries like Application Service provision possible.

Dov concludes that "the reason that the Ethernet succeeded as well as 
it has, its simplicity. Ethernet is a very simple, yet elegant 
protocol. But because of its simplicity, it's extremely inexpensive 
to develop and to manufacture Ethernet-compliant devices." Many 
people are taking gigabit Ethernet and applying it to wide area 
networking because of its simplicity, ease of access and simplicity 
of its framing.

In its relationship between volume and pricing Gigabit Ethernet 
offers significant values. Gigabit Ethernet initially was being 
installed in the local area network to provide interconnection 
between boxes that were connecting 100 megabits, and 10megabits, to 
the desktop. The volume of that kind of traffic quickly becomes very 
large. For these applications over short distances, compared to 
OC-24, gigabit Ethernet is actually cheaper, even though it provides 
more bandwidth. What people started to realize, because of the volume 
of gigabit Ethernet traffic that was going out and the relative 
simplicity of it, the cost of gigabit Ethernet ran under cut that of 
OC-24 pretty quickly. And the result is that people who are making 
the decisions as to what will be used to hook LANs to each other and 
to the Internet started deciding  to go with gigabit Ethernet, rather 
than with the OC-24 or OC-48. Gigabit  Ethernet's application is at 
the periphery of the internet  Therefore it is not being looked tofor 
the elimination of SONET add/drop multiplexers.

With ten gigabit Ethernet some people are proposing to basically take 
the ten gigabit Ethernet media access controller, the MAC, and 
packetize the data, just like we currently do in Ethernet at ten 
times the rate. But they then want to send it into a SONET framer. 
The SONET framer will then take that data and chop it up and put it 
into the SONET frame. The framer will send it across the network and 
when it gets received on the other side, it will be effectively 
deframed.  There are also people that are more focused on taking the 
current, simple Ethernet approach, which is just, take the data, put 
it onto an optical fiber and ship it on across the link. They don't 
want to get into the complexity of SONET framing and so on.

HP's Thompson offered the following analogy: " It's sort of like the 
subway system versus the inter city train system. Once, historically, 
if you wanted to ride the "train" from the center of one city to the 
center of another, you rode the subway system to get out to the train 
station, took a train and then subway back into a city. So what we're 
talking about now is Ethernet making it robust enough and fast enough 
so that your subway car can simply ride from one city to the next and 
that you don't have to change the vehicles that are riding on the 
tracks, the fiber, in the meantime."  In other words a  simplistic 
design that would work for the people who are working in the local 
area networks would also go for people who wanted to do optical 
transmission with Ethernet framing cross-country"  The interview 
concludes with a discussion of the issues being faced in the 
development of 10 gigabit Ethernet standards.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

EXPLOSION IN CAPACITY CHASED BY EXPLOSION IN USE
FIBER TO THE HOME FROM HP ORACLE AND POWER COMPANIES FOR LESS THAN 
$15 A MONTH -- ABOVENET ON THE NEED TO OWN FIBER
		pp. 10, 27


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ROLE OF DIFFSERV IN THE DEVELOPMENT OF QOS TOOLS
KATHY NICHOLS EXPLAINS HOW PURSUIT OF VIABLE QOS PROTOCOLS IS
TRANSITIONING FROM CENTRALIZED MODEL TO HORIZONTALLY ORGANIZED TOOL 
CHEST FROM WHICH ISPS CAN DESIGN CROSS ISP COMPATIBLE SERVICES, 
	pp. 11-19, 27


On November 16, we interviewed Kathy Nichols who with Brian Carpenter 
is co-chair of the very active Diffserv working group.  We asked 
Kathy to put Diffserv in its historical context.  She replied that 
originally people assumed that Quality of Service guarantees would be 
needed to do multimedia over the Internet.  Integrated Services and 
RSVP came out of these assumptions.  But RSVP had been designed by 
Lixia Zhang and others while Lixia was at Xerox Parc. The design was 
made with the assumption that you could put RSVP state into every 
router because you would always keep your application inside the 
network of a single provider.  After several years of experimentation 
the emerging view is that RSVP should be seen as a generic signaling 
protocol or a way for a host to talk to a network.  Other protocols 
would govern ways that hosts request things of a network to which 
they are talking.  One should note that the original work with RSVP 
and Intserv was done before April 1995 when the NSFNet backbone was 
shut off and when the topology and traffic on the internet to which 
people were thinking about applying quality of service were radically 
different that what they are now (almost exactly five years later).

By the beginning of 1997 some ISPs were beginning to talk of QoS in 
terms of being able to give some of the traffic that they carried 
better treatment than other traffic a kind of better best effort. 
According to Kathy "the Differentiated Services discussion happened 
because some service providers were not happy with the Intserv 
approach. They weren't going to let state cross their boundary. They 
didn't see how something with that much state could work. And it also 
didn't seem to do exactly what they wanted, which included to be able 
to tell a customer that they could replace their leased line and give 
them at least equivalent service. And it would be a good deal, 
because they should be able to offer it cheaper and reuse their 
infrastructure."

Traffic for a premium class of service could be relegated into 
special queues for that traffic alone.  Traffic for best effort and 
better best effort could remain in the same queue.  In most network 
conditions the packets would be treated the same while in exceptional 
conditions the mere best effort packets might find themselves 
discriminated against.  Some of the very best engineers and protocol 
designers in the Internet were coming up with schemes for how to do 
traffic marking and shaping to accomplish these goals. (The idea that 
the same queue can be used to have two different levels of service is 
the idea behind weighted RED.) Unfortunately their schemes - call 
them tools perhaps - were too often incompatible with each other. 
People were designing complex tools to work handle vast amounts of 
traffic in complex and rapidly changing situations.  Diffserv was 
started as a way to bring order out of a very complex chaos.  People 
wanted to structure a framework for which people could design their 
tools and to create a situation where if they designed them to be 
compatible with the framework they would be compatible and 
interoperable with each other.  Diffserv may be thought of as a set 
of guidelines within which various quality of service tools may be 
implemented.

Kathy states that the only way to scale QoS is to aggregate packets. 
If we group them inside of a "cloud" or domain, we will put them into 
something called a "behavior aggregate."  You create a behavior 
aggregate by saying that you will assign each packet that is to be a 
member of that aggregate a particular per hop behavior (PHB).  PHB 
permits the assigning of the same forwarding treatment for all 
network traffic that labeled with a given PHB.  You may then consider 
telling customers that they will pay a certain rate for traffic sent 
in conformance with the PHB aggregate they have purchased and let 
them know that  your routers will drop traffic labelled as conformant 
with a given PHB that in reality is found by the router to be non 
conformant.  One goal is to get the maximum amount of classification 
of what may be done with traffic out of a field that is no more than 
6 bits per packet.  What Diffserv is really doing for  ISPs and for 
hardware vendor is helping them to work together to establish 
reasonable guidelines within which many different quality of service 
provisions can  created.  The idea is that the ISP is allowed to 
establish its own QoS offerings.  Diffserv has created behavior 
aggregates and control planes that can be used to implement the 
policy goals of the behavior aggregate.  Two ISP may be able to solve 
cross ISP policy issues by sitting down with each other and selecting 
Diffserv compatible tools that would not have to be the exact same 
tool.  It is Diffserv's intention to give them tools by which they 
can achieve common QoS outcomes by means that inside their respective 
networks may be quite different.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

ALL RESPONSIBILITY DISINTERMEDIATED FROM DNS FIX
NEW ICANN DOC SHARED REGISTRY SYSTEM ENABLES REGISTRARS, SHARED 
REGISTRY AND ICANN TO DISCLAIM RESPONSIBILITY FOR ALL ACTIONS THAT 
INJURE REGISTRANTS        pp. 20 - 26

In mid January Wired 
http://www.wired.com/news/technology/0,1282,33753,00.html published a 
delightful summary of the results of Beckwith Burr', ICANN's, and 
NSI's redesign of the DNS system.  People were buying a domain name 
and paying for it at the time of purchase only to see it sold out 
from underneath them the very next day to someone else. For the 
little guy the Internet's domain name system had been put at risk by 
the Clinton Gore bureaucrats. No mater: the large, powerful and rich 
had the ICANN uniform dispute resolution policy and the even more 
Draconian cyber squatting legislation. ICANN had done a superb job of 
freeing the corporate trademark attorneys to do their thing. It had 
done this by creating a jury-rigged system where registrars could say 
that mistakes belonged to the registry which in turn could say it was 
playing by ICANN rules while ICANN disclaimed all responsibility for 
breakages in the system.

According to Wired, "ICANN said it was not responsible for domain 
name discrepancies between registrars and their customers.

The COOK Report reminds its readers that to be functional a domain 
name must be part of the registry database that determines what other 
names are taken and is responsible for getting the names into the 
root servers where down line DNS servers can find them.  The 
operation of the new system has been rigged by ICANN so that, while 
the registry gets names to advertise, it gets no information about 
the owners of the names in whose interest it is doing the 
advertisement.  This information is known to the Registrars whose 
agreements with ICANN give them enforceable rights vis-ā-vis the 
Registry. But the customers who pay a registrar to act as the 
intermediary between them and the registry have no enforceable rights 
what so ever to the use of the domain names for which they pay.

We do not  know  who designed and  put in place this truly bizarre 
system.  It was ICANN but the secret process by which it was done 
inside of ICANN has remained opaque to everyone on the outside.  As 
far as we can tell, ICANN rules by having its Jones Day attorneys, 
Touton and Sims work with Esther Dyson and Mike Roberts to establish 
policy that disenfranchises every Internet user (who does not also 
pay the necessary fees to become a registrar) of any rights to 
receive the benefits of the products for which they have paid. The 
registrar is fee to do anything it chooses with the domain name that 
it sells to the registrant.  The system is also dependent for its 
operation on a shared registry protocol that has been (according to 
the testimony of some outside experts who advised NSI on its design) 
implemented in such a way as to make any accountability to the 
registrants and even to the registrars unlikely.  NSI has sought what 
non experts will take as endorsement from the IETF by asking for 
publication of the protocol as an informational RFC.  One of the 
experts who advised NSI in the design has protested loudly against 
the move and asked NSI to free him from his non disclosure agreement 
so that he may publish his criticism to allow independent observers 
to make their own judgements.  NSI has refused.

By the end of the month it was clear that the entire shared registry 
system was a design failure. As early as late December complaints of 
break downs were becoming evident. On December 23 on the Domain 
policy list at NSI list member "A" complained " Most whois clients 
query the public NSI Registry database first which only updates *once 
per day* so it's quite possible for someone to do a domain query and 
be shown the old whois information of the old registrar. Nothing is 
wrong.

To which list member "B" replied: No, nothing is wrong as far as the 
design goes. But of course that [just looking at the design] is not 
far enough, is it? Therefore leaving the ability for registrars to 
"Steal" domain names and/or create a domain name conflict from the 
get go. Doesn't say much for stability, does it?  Our article 
summarizes debate from the IETF and Domain Policy lists that makes 
quite clear the absurdity that the White House and its ice president 
is visiting upon the Internet.

Froomkin & Auerbach Offer ICANN Bitter Criticism, pp. 27, 29, 30

Two who have tried to work with ICANN say foul in no uncertain and 
bitter terms to move by DNSO to censor DNSO GA mail list.  ICANN 
Makes it clear it will tolerate no criticism.

****************************************************************
The COOK Report on Internet      Index to 8 years of the COOK  Report
431 Greenway Ave, Ewing, NJ 08618 USA  http://cookreport.com
(609) 882-2572 (phone & fax)             Battle for Cyberspace: How
cook@cookreport.com                     Crucial Technical . . . - 392 pages
just published. See  http://cookreport.com/ipbattle.shtml
****************************************************************



From owner-ietf-outbound  Fri Feb 11 22:20:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA02534
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 22:20:02 -0500 (EST)
Received: from vulture.prod.itd.earthlink.net (vulture.prod.itd.earthlink.net [207.217.121.36])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02402
	for <ietf@ietf.org>; Fri, 11 Feb 2000 22:15:18 -0500 (EST)
Received: from [192.168.0.1] (ipa184.trenton2.nj.pub-ip.psi.net [38.26.139.184])
	by vulture.prod.itd.earthlink.net (8.9.3/8.9.3) with ESMTP id TAA06116
	for <ietf@ietf.org>; Fri, 11 Feb 2000 19:15:17 -0800 (PST)
Mime-Version: 1.0
X-Sender: cook@pop3.netaxs.com (Unverified)
Message-Id: <v04210111b4ca7c385b47@[38.26.139.190]>
X-Priority: 2 (High)
Date: Fri, 11 Feb 2000 22:15:48 -0500
To: ietf@ietf.org
From: Gordon Cook <cook@cookreport.com>
Subject: Apologies for double send  <sigh>!
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

I had one queued for IETF and stopped the transmission from eudora 
before it completed.  Or so I thought!  I had not finished my edits 
on it .  The two pieces were not the same.  But I sincerely regret 
letting the first escape.... eudora said it was still queued.  Any 
way I sent it here primarily because I thought the Kathy Nicols 
interview would be interesting for those not in the diffserv WG.

Rest assured I have no intention of adding ietf to my monthly distribution.

again my apologies - this is not the place to suffer hand eye brain 
coordination lapse.

ARGH - AND NOW FOR 20 MINUTES I CAN'T CONNECT WITH EARTH LINK'S 
SERVER......  ARGH - I AM TRYING....
****************************************************************
The COOK Report on Internet      Index to 8 years of the COOK  Report
431 Greenway Ave, Ewing, NJ 08618 USA  http://cookreport.com
(609) 882-2572 (phone & fax)             Battle for Cyberspace: How
cook@cookreport.com                     Crucial Technical . . . - 392 pages
just published. See  http://cookreport.com/ipbattle.shtml
****************************************************************



From owner-ietf-outbound@ietf.org  Fri Feb 11 22:21:55 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02625
	for <ietf-web-archive@odin.ietf.org>; Fri, 11 Feb 2000 22:21:55 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA07784;
	Fri, 11 Feb 2000 22:19:57 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id WAA02534
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 22:20:02 -0500 (EST)
Received: from vulture.prod.itd.earthlink.net (vulture.prod.itd.earthlink.net [207.217.121.36])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02402
	for <ietf@ietf.org>; Fri, 11 Feb 2000 22:15:18 -0500 (EST)
Received: from [192.168.0.1] (ipa184.trenton2.nj.pub-ip.psi.net [38.26.139.184])
	by vulture.prod.itd.earthlink.net (8.9.3/8.9.3) with ESMTP id TAA06116
	for <ietf@ietf.org>; Fri, 11 Feb 2000 19:15:17 -0800 (PST)
Mime-Version: 1.0
X-Sender: cook@pop3.netaxs.com (Unverified)
Message-Id: <v04210111b4ca7c385b47@[38.26.139.190]>
X-Priority: 2 (High)
Date: Fri, 11 Feb 2000 22:15:48 -0500
To: ietf@ietf.org
From: Gordon Cook <cook@cookreport.com>
Subject: Apologies for double send  <sigh>!
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

I had one queued for IETF and stopped the transmission from eudora 
before it completed.  Or so I thought!  I had not finished my edits 
on it .  The two pieces were not the same.  But I sincerely regret 
letting the first escape.... eudora said it was still queued.  Any 
way I sent it here primarily because I thought the Kathy Nicols 
interview would be interesting for those not in the diffserv WG.

Rest assured I have no intention of adding ietf to my monthly distribution.

again my apologies - this is not the place to suffer hand eye brain 
coordination lapse.

ARGH - AND NOW FOR 20 MINUTES I CAN'T CONNECT WITH EARTH LINK'S 
SERVER......  ARGH - I AM TRYING....
****************************************************************
The COOK Report on Internet      Index to 8 years of the COOK  Report
431 Greenway Ave, Ewing, NJ 08618 USA  http://cookreport.com
(609) 882-2572 (phone & fax)             Battle for Cyberspace: How
cook@cookreport.com                     Crucial Technical . . . - 392 pages
just published. See  http://cookreport.com/ipbattle.shtml
****************************************************************



From owner-ietf-outbound  Fri Feb 11 23:40:26 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA05100
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 23:40:02 -0500 (EST)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05016
	for <IETF@ietf.org>; Fri, 11 Feb 2000 23:33:19 -0500 (EST)
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.0.Beta13/8.10.0.Beta13) with ESMTP id e1C4XF936940;
	Fri, 11 Feb 2000 23:33:15 -0500
Message-Id: <200002120433.e1C4XF936940@black-ice.cc.vt.edu>
To: Paul Ferguson <ferguson@cisco.com>
cc: IETF@ietf.org, nanog@merit.edu
Subject: Re: Internet SYN Flooding, spoofing attacks 
In-reply-to: Your message of "Fri, 11 Feb 2000 21:09:47 EST."
             <4.2.2.20000211210210.00a4e880@lint.cisco.com> 
From: Valdis.Kletnieks@vt.edu
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <4.2.2.20000211163625.00a4d770@lint.cisco.com>
            <4.2.2.20000211210210.00a4e880@lint.cisco.com>
Date: Fri, 11 Feb 2000 23:33:14 -0500
X-Loop: ietf@ietf.org

On Fri, 11 Feb 2000 21:09:47 EST, Paul Ferguson said:
> We (at least cisco, anyways) already have a knob for this:
> 
>   [no] ip verify unicast reverse-path
> 
> We call it Unicast RPF.

Paul:

What are the chances of setting up "The Next Release" of IOS
so that for simple configs (for example, a customer backbone and
one upstream link to a provider) the knob would automagically default
to Doing The Right Thing?  I of course am writing as a non-expert on
the innnards of IOS, and I'm expecting flame-fests regarding "simple
config" and "Right Thing".

No, it's not a total fix.  It won't fix everything.  It may not
even be possible.  But it certainly would be nice. ;)

				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound@ietf.org  Fri Feb 11 23:41:57 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05167
	for <ietf-web-archive@odin.ietf.org>; Fri, 11 Feb 2000 23:41:57 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA08796;
	Fri, 11 Feb 2000 23:39:59 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id XAA05100
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 23:40:02 -0500 (EST)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05016
	for <IETF@ietf.org>; Fri, 11 Feb 2000 23:33:19 -0500 (EST)
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.0.Beta13/8.10.0.Beta13) with ESMTP id e1C4XF936940;
	Fri, 11 Feb 2000 23:33:15 -0500
Message-Id: <200002120433.e1C4XF936940@black-ice.cc.vt.edu>
To: Paul Ferguson <ferguson@cisco.com>
cc: IETF@ietf.org, nanog@merit.edu
Subject: Re: Internet SYN Flooding, spoofing attacks 
In-reply-to: Your message of "Fri, 11 Feb 2000 21:09:47 EST."
             <4.2.2.20000211210210.00a4e880@lint.cisco.com> 
From: Valdis.Kletnieks@vt.edu
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <4.2.2.20000211163625.00a4d770@lint.cisco.com>
            <4.2.2.20000211210210.00a4e880@lint.cisco.com>
Date: Fri, 11 Feb 2000 23:33:14 -0500
X-Loop: ietf@ietf.org

On Fri, 11 Feb 2000 21:09:47 EST, Paul Ferguson said:
> We (at least cisco, anyways) already have a knob for this:
> 
>   [no] ip verify unicast reverse-path
> 
> We call it Unicast RPF.

Paul:

What are the chances of setting up "The Next Release" of IOS
so that for simple configs (for example, a customer backbone and
one upstream link to a provider) the knob would automagically default
to Doing The Right Thing?  I of course am writing as a non-expert on
the innnards of IOS, and I'm expecting flame-fests regarding "simple
config" and "Right Thing".

No, it's not a total fix.  It won't fix everything.  It may not
even be possible.  But it certainly would be nice. ;)

				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Fri Feb 11 23:50:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA05287
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 23:50:02 -0500 (EST)
Received: from server.jad.net ([202.134.2.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05026
	for <ietf@ietf.org>; Fri, 11 Feb 2000 23:34:39 -0500 (EST)
Received: from oke.com (cf-isrlab7.comp.nus.edu.sg [137.132.85.181])
	by server.jad.net (8.9.2/8.9.2) with ESMTP id MAA10198;
	Sat, 12 Feb 2000 12:35:31 +0700 (JAVT)
	(envelope-from rms46@oke.com)
Sender: ibrahim@server.jad.net
Message-ID: <38A4E275.78D95BDB@oke.com>
Date: Sat, 12 Feb 2000 12:32:53 +0800
From: "Rahmat M. Samik-Ibrahim" <rms46@oke.com>
Reply-To: rms46.oke.com@vlsm.org
Organization: VLSM-TJT
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5-22 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: MILIS IETF <ietf@ietf.org>
CC: MILIS gnM-DICK <dick@egroups.com>
Subject: SUMMARY: flooding and spoofing attacks
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Hello:

I try to summarize about what is going on. Please let me know if
I miss something. I will put this later into http://ittf.vlsm.org
========================================================================

Clue alert... the recent attacks were not TCP SYN Floods (Warfield).

- Place to discuss: NANOG (The North American Network Operators' Group)
  Milis: http://www.nanog.org/mailinglist.html

- RFCs
  2267 Network Ingress Filtering: Defeating Denial of Service 
       Attacks which employ IP Source Address Spoofing
       http://www.ietf.org/rfc/rfc2267.txt
         "There is no assumption implied that RFC2267 filtering 
          is needed -- it is required. What good is it if one or 
          two or 300 people do it, and another 157,000 do not?
          (Ferguson)"
          "... while there are certainly clueless ISPs out there, 
          I suspect that on the average they're more clueful 
          about the net than the typical end site (Bellovin)."
  2350 Expectations for Computer Security Incident Response
       http://www.ietf.org/rfc/rfc2350.txt
  2502 Limitations of Internet Protocol Suite for Distributed
       Simulation in the Large Multicast Environment
       http://www.ietf.org/rfc/rfc2502.txt
  2644 Changing the Default for Directed Broadcasts in Routers
       http://www.ietf.org/rfc/rfc2644.txt

- Further references:
  http://xforce.iss.net/alerts/advise40.php3
  http://www.cert.org/advisories/CA-2000-01.html

- Analysis of TFN (Tribe Flood Network):
  http://staff.washington.edu/dittrich/misc/tfn.analysis
  http://staff.washington.edu/dittrich/misc/trinoo.analysis
  http://staff.washington.edu/dittrich/misc/stacheldraht.analysis

- Craig Huegen's on minimizing the effects of DoS attacks:
  http://users.quadrunner.com/chuegen/smurf.cgi

- Distributed Denial of Service (DDoS) News Flash,
  http://www.cisco.com/warp/public/707/newsflash.html

- Dave Dittrich's analysis of the recent DDoS attack tools.
  http://www.washington.edu/People/dad/

- NIPC (National Infrstructure Protection Center),
  TRINOO/Tribal Flood Net/tfn2k stuff:
  http://www.fbi.gov/nipc/trinoo.htm

- Handling A Distributed Denial of Service Trojan Infection: 
  Step-by-Step.
  http://www.sans.org/y2k/DDoS.htm

- Internet Security Advisories
  http://www.cisco.com/warp/public/707/advisory.html
  http://www.cisco.com/warp/public/707/22.html
  http://www.cisco.com/warp/public/707/sec_incident_response.shtml
  http://www.cisco.com/public/cons/isp/documents/IOSEssentialsPDF.zip

- Know your enemy: Script Kiddies
  http://www.enteract.com/~lspitz/enemy.html

- Flow Logs and Intrusion Detection at the Ohio State University
  http://www.usenix.org/publications/login/1999-9/osu.html

- Achtung LAWyers!
  http://www.techweb.com/wire/story/TWB20000211S0014

- The size of the internet: 72,000,000 domains/hosts.
  http://www.isc.org/ds/

- Sources (tararengkyu ka):
    Steve Bellovin
    Paul Ferguson
    Valdis Kletnieks
    April Marine
    Michael H. Warfield

tabe,

-- 
- Rahmat M. Samik-Ibrahim --  VLSM-TJT --  http://rms46.vlsm.org/ -
- Always select ShutDown from the StartMenu - M$Windows after crash



From owner-ietf-outbound@ietf.org  Fri Feb 11 23:51:04 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05344
	for <ietf-web-archive@odin.ietf.org>; Fri, 11 Feb 2000 23:51:04 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA08874;
	Fri, 11 Feb 2000 23:49:04 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id XAA05287
	for ietf-outbound.10@ietf.org; Fri, 11 Feb 2000 23:50:02 -0500 (EST)
Received: from server.jad.net ([202.134.2.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05026
	for <ietf@ietf.org>; Fri, 11 Feb 2000 23:34:39 -0500 (EST)
Received: from oke.com (cf-isrlab7.comp.nus.edu.sg [137.132.85.181])
	by server.jad.net (8.9.2/8.9.2) with ESMTP id MAA10198;
	Sat, 12 Feb 2000 12:35:31 +0700 (JAVT)
	(envelope-from rms46@oke.com)
Sender: ibrahim@server.jad.net
Message-ID: <38A4E275.78D95BDB@oke.com>
Date: Sat, 12 Feb 2000 12:32:53 +0800
From: "Rahmat M. Samik-Ibrahim" <rms46@oke.com>
Reply-To: rms46.oke.com@vlsm.org
Organization: VLSM-TJT
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5-22 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: MILIS IETF <ietf@ietf.org>
CC: MILIS gnM-DICK <dick@egroups.com>
Subject: SUMMARY: flooding and spoofing attacks
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hello:

I try to summarize about what is going on. Please let me know if
I miss something. I will put this later into http://ittf.vlsm.org
========================================================================

Clue alert... the recent attacks were not TCP SYN Floods (Warfield).

- Place to discuss: NANOG (The North American Network Operators' Group)
  Milis: http://www.nanog.org/mailinglist.html

- RFCs
  2267 Network Ingress Filtering: Defeating Denial of Service 
       Attacks which employ IP Source Address Spoofing
       http://www.ietf.org/rfc/rfc2267.txt
         "There is no assumption implied that RFC2267 filtering 
          is needed -- it is required. What good is it if one or 
          two or 300 people do it, and another 157,000 do not?
          (Ferguson)"
          "... while there are certainly clueless ISPs out there, 
          I suspect that on the average they're more clueful 
          about the net than the typical end site (Bellovin)."
  2350 Expectations for Computer Security Incident Response
       http://www.ietf.org/rfc/rfc2350.txt
  2502 Limitations of Internet Protocol Suite for Distributed
       Simulation in the Large Multicast Environment
       http://www.ietf.org/rfc/rfc2502.txt
  2644 Changing the Default for Directed Broadcasts in Routers
       http://www.ietf.org/rfc/rfc2644.txt

- Further references:
  http://xforce.iss.net/alerts/advise40.php3
  http://www.cert.org/advisories/CA-2000-01.html

- Analysis of TFN (Tribe Flood Network):
  http://staff.washington.edu/dittrich/misc/tfn.analysis
  http://staff.washington.edu/dittrich/misc/trinoo.analysis
  http://staff.washington.edu/dittrich/misc/stacheldraht.analysis

- Craig Huegen's on minimizing the effects of DoS attacks:
  http://users.quadrunner.com/chuegen/smurf.cgi

- Distributed Denial of Service (DDoS) News Flash,
  http://www.cisco.com/warp/public/707/newsflash.html

- Dave Dittrich's analysis of the recent DDoS attack tools.
  http://www.washington.edu/People/dad/

- NIPC (National Infrstructure Protection Center),
  TRINOO/Tribal Flood Net/tfn2k stuff:
  http://www.fbi.gov/nipc/trinoo.htm

- Handling A Distributed Denial of Service Trojan Infection: 
  Step-by-Step.
  http://www.sans.org/y2k/DDoS.htm

- Internet Security Advisories
  http://www.cisco.com/warp/public/707/advisory.html
  http://www.cisco.com/warp/public/707/22.html
  http://www.cisco.com/warp/public/707/sec_incident_response.shtml
  http://www.cisco.com/public/cons/isp/documents/IOSEssentialsPDF.zip

- Know your enemy: Script Kiddies
  http://www.enteract.com/~lspitz/enemy.html

- Flow Logs and Intrusion Detection at the Ohio State University
  http://www.usenix.org/publications/login/1999-9/osu.html

- Achtung LAWyers!
  http://www.techweb.com/wire/story/TWB20000211S0014

- The size of the internet: 72,000,000 domains/hosts.
  http://www.isc.org/ds/

- Sources (tararengkyu ka):
    Steve Bellovin
    Paul Ferguson
    Valdis Kletnieks
    April Marine
    Michael H. Warfield

tabe,

-- 
- Rahmat M. Samik-Ibrahim --  VLSM-TJT --  http://rms46.vlsm.org/ -
- Always select ShutDown from the StartMenu - M$Windows after crash



From owner-ietf-outbound  Sat Feb 12 00:20:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA05598
	for ietf-outbound.10@ietf.org; Sat, 12 Feb 2000 00:20:02 -0500 (EST)
Received: from mailman.cisco.com (mailman.cisco.com [171.68.225.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA05573
	for <IETF@ietf.org>; Sat, 12 Feb 2000 00:16:55 -0500 (EST)
Received: from bigger-dawgs (pferguso-isdn.cisco.com [171.70.114.134]) by mailman.cisco.com (8.8.8+Sun/CISCO.SERVER.1.2) with ESMTP id VAA09853; Fri, 11 Feb 2000 21:16:18 -0800 (PST)
Message-Id: <4.2.2.20000212000816.00a44a30@lint.cisco.com>
X-Sender: pferguso@lint.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Sat, 12 Feb 2000 00:16:14 -0500
To: Valdis.Kletnieks@vt.edu
From: Paul Ferguson <ferguson@cisco.com>
Subject: Re: Internet SYN Flooding, spoofing attacks 
Cc: IETF@ietf.org, nanog@merit.edu
In-Reply-To: <200002120433.e1C4XF936940@black-ice.cc.vt.edu>
References: <Your message of "Fri, 11 Feb 2000 21:09:47 EST." <4.2.2.20000211210210.00a4e880@lint.cisco.com>
 <4.2.2.20000211163625.00a4d770@lint.cisco.com>
 <4.2.2.20000211210210.00a4e880@lint.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 11:33 PM 02/11/2000 -0500, Valdis.Kletnieks@vt.edu wrote:

>What are the chances of setting up "The Next Release" of IOS
>so that for simple configs (for example, a customer backbone and
>one upstream link to a provider) the knob would automagically default
>to Doing The Right Thing?  I of course am writing as a non-expert on
>the innnards of IOS, and I'm expecting flame-fests regarding "simple
>config" and "Right Thing".
>
>No, it's not a total fix.  It won't fix everything.  It may not
>even be possible.  But it certainly would be nice. ;)

Something like "ip default clueless"? Just kidding. ;-)

Well, overwhelming support for any suggested default mod is
always considered. Really.

Overwhelming is the operative word here.

We (as do many other vendors, I would suggest) operate
under the "Principle of Least Astonishment": How many people
would we screw if we changed the defaults of a particular
command?

If overwhelming community support were to set the tone for a default
change, we would certainly not take it lightly. :-)

- paul



From owner-ietf-outbound@ietf.org  Sat Feb 12 00:21:21 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA05656
	for <ietf-web-archive@odin.ietf.org>; Sat, 12 Feb 2000 00:21:21 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA09238;
	Sat, 12 Feb 2000 00:19:18 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id AAA05598
	for ietf-outbound.10@ietf.org; Sat, 12 Feb 2000 00:20:02 -0500 (EST)
Received: from mailman.cisco.com (mailman.cisco.com [171.68.225.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA05573
	for <IETF@ietf.org>; Sat, 12 Feb 2000 00:16:55 -0500 (EST)
Received: from bigger-dawgs (pferguso-isdn.cisco.com [171.70.114.134]) by mailman.cisco.com (8.8.8+Sun/CISCO.SERVER.1.2) with ESMTP id VAA09853; Fri, 11 Feb 2000 21:16:18 -0800 (PST)
Message-Id: <4.2.2.20000212000816.00a44a30@lint.cisco.com>
X-Sender: pferguso@lint.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Sat, 12 Feb 2000 00:16:14 -0500
To: Valdis.Kletnieks@vt.edu
From: Paul Ferguson <ferguson@cisco.com>
Subject: Re: Internet SYN Flooding, spoofing attacks 
Cc: IETF@ietf.org, nanog@merit.edu
In-Reply-To: <200002120433.e1C4XF936940@black-ice.cc.vt.edu>
References: <Your message of "Fri, 11 Feb 2000 21:09:47 EST." <4.2.2.20000211210210.00a4e880@lint.cisco.com>
 <4.2.2.20000211163625.00a4d770@lint.cisco.com>
 <4.2.2.20000211210210.00a4e880@lint.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 11:33 PM 02/11/2000 -0500, Valdis.Kletnieks@vt.edu wrote:

>What are the chances of setting up "The Next Release" of IOS
>so that for simple configs (for example, a customer backbone and
>one upstream link to a provider) the knob would automagically default
>to Doing The Right Thing?  I of course am writing as a non-expert on
>the innnards of IOS, and I'm expecting flame-fests regarding "simple
>config" and "Right Thing".
>
>No, it's not a total fix.  It won't fix everything.  It may not
>even be possible.  But it certainly would be nice. ;)

Something like "ip default clueless"? Just kidding. ;-)

Well, overwhelming support for any suggested default mod is
always considered. Really.

Overwhelming is the operative word here.

We (as do many other vendors, I would suggest) operate
under the "Principle of Least Astonishment": How many people
would we screw if we changed the defaults of a particular
command?

If overwhelming community support were to set the tone for a default
change, we would certainly not take it lightly. :-)

- paul



From owner-ietf-outbound  Sat Feb 12 02:00:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA10271
	for ietf-outbound.10@ietf.org; Sat, 12 Feb 2000 02:00:02 -0500 (EST)
Received: from server.jad.net ([202.134.2.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA10123
	for <ietf@ietf.org>; Sat, 12 Feb 2000 01:58:33 -0500 (EST)
Received: from oke.com (cf-isrlab7.comp.nus.edu.sg [137.132.85.181])
	by server.jad.net (8.9.2/8.9.2) with ESMTP id OAA11826;
	Sat, 12 Feb 2000 14:59:26 +0700 (JAVT)
	(envelope-from rms46@oke.com)
Sender: ibrahim@server.jad.net
Message-ID: <38A50049.7851A5BF@oke.com>
Date: Sat, 12 Feb 2000 14:40:09 +0800
From: "Rahmat M. Samik-Ibrahim" <rms46@oke.com>
Reply-To: rms46.oke.com@vlsm.org
Organization: VLSM-TJT
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5-22 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: MILIS IETF <ietf@ietf.org>
Subject: Re: 1601bis: The Charter of IAB
References: <38928323.6DF08264@oke.com> <38973CC0.7587C6AD@hursley.ibm.com> <389C0D4A.813EF55E@oke.com> <389EEEE1.555A4FF4@hursley.ibm.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Brian E Carpenter wrote:

> I can read your words, but I really can't understand your concerns.
> You seem to be worrying about dragons that I can't see. Happy New 
> Year, anyway.

Hm... your reply is exactly my concern! Your answer is just based
on "can not understand" and not based on any document or past
history. Therefore, I would like to see more things in written.
Is this by the way how the board in handling appeals?
Who is the current IANA and RFC-Ed (chair/head/whatever)?

I also believe what Klensin wrote is still valid:

......................................................................

[... 22 Feb 1996 ... skipping voting out of existence, fine lunches 
 and dinners, and irresolvable controversy pronouncements...]

For questions of process, there is really a jury problem, not a
technical or architectural expertise one.  The IAB membership
may have no special competence to make decisions on process
matters and, if they were involved in the initial proposals in
any way, they may be contaminated relative to making fair
choices.  I suggest that, for process questions, the right
appeals body is a jury-like group that is chosen exactly the way
the Nomcomm is chosen -- volunteers from the IETF participant
pool and then at random, with no sitting IAB or IESG (or, I'd
think, ISOC Trustees) members permitted to volunteer.

I don't have an opinion as to whether we pick an appeals panel
for a year just in case we need them or pick them only when a
sufficient process appeal arises.  It is not clear to me that it
makes much difference -- except that, if they were picked on
demand, we might just take the attendance list from the last few
meetings and draw people from it on an "attendance subjects one
to the risk on volunteering" basis.  That has some drawbacks but
some appeal.

For the technical error questions, it is still not clear to me
that IAB is the right appeals body, especially if they were
active in formulating the position under appeal or an alternate
to it.   A randomly-chosen jury might still work, but might well
not have the right technical expertise.  As one possibility, we
could move toward a formalized blue-ribbon review and mediation
panel, with members of that panel being chosen by IESG, the WG
leadership, and the individual or group launching the appeal.
If it was appropriate to populate that panel with IAB members,
that would be fine, but the review itself would not be an IAB
responsibility.   If the panel didn't behave fairly, that
becomes a procedural question, and the appeals board outlined
above takes over.

................................................................

It seems that the only thing that I can do is keeping records
on who's who were on the board (+when), plus who were the nomcom 
who had elected them. Let the Vulcans, Klingons, and 
Ferengis make the final judgements in the next millennium.


tabe,

-- 
- Rahmat M. Samik-Ibrahim --  VLSM-TJT --  http://rms46.vlsm.org/ -
- Always select ShutDown from the StartMenu - M$Windows after crash




From owner-ietf-outbound@ietf.org  Sat Feb 12 02:01:50 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA12334
	for <ietf-web-archive@odin.ietf.org>; Sat, 12 Feb 2000 02:01:49 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA16294;
	Sat, 12 Feb 2000 01:59:33 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id CAA10271
	for ietf-outbound.10@ietf.org; Sat, 12 Feb 2000 02:00:02 -0500 (EST)
Received: from server.jad.net ([202.134.2.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA10123
	for <ietf@ietf.org>; Sat, 12 Feb 2000 01:58:33 -0500 (EST)
Received: from oke.com (cf-isrlab7.comp.nus.edu.sg [137.132.85.181])
	by server.jad.net (8.9.2/8.9.2) with ESMTP id OAA11826;
	Sat, 12 Feb 2000 14:59:26 +0700 (JAVT)
	(envelope-from rms46@oke.com)
Sender: ibrahim@server.jad.net
Message-ID: <38A50049.7851A5BF@oke.com>
Date: Sat, 12 Feb 2000 14:40:09 +0800
From: "Rahmat M. Samik-Ibrahim" <rms46@oke.com>
Reply-To: rms46.oke.com@vlsm.org
Organization: VLSM-TJT
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5-22 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: MILIS IETF <ietf@ietf.org>
Subject: Re: 1601bis: The Charter of IAB
References: <38928323.6DF08264@oke.com> <38973CC0.7587C6AD@hursley.ibm.com> <389C0D4A.813EF55E@oke.com> <389EEEE1.555A4FF4@hursley.ibm.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Brian E Carpenter wrote:

> I can read your words, but I really can't understand your concerns.
> You seem to be worrying about dragons that I can't see. Happy New 
> Year, anyway.

Hm... your reply is exactly my concern! Your answer is just based
on "can not understand" and not based on any document or past
history. Therefore, I would like to see more things in written.
Is this by the way how the board in handling appeals?
Who is the current IANA and RFC-Ed (chair/head/whatever)?

I also believe what Klensin wrote is still valid:

......................................................................

[... 22 Feb 1996 ... skipping voting out of existence, fine lunches 
 and dinners, and irresolvable controversy pronouncements...]

For questions of process, there is really a jury problem, not a
technical or architectural expertise one.  The IAB membership
may have no special competence to make decisions on process
matters and, if they were involved in the initial proposals in
any way, they may be contaminated relative to making fair
choices.  I suggest that, for process questions, the right
appeals body is a jury-like group that is chosen exactly the way
the Nomcomm is chosen -- volunteers from the IETF participant
pool and then at random, with no sitting IAB or IESG (or, I'd
think, ISOC Trustees) members permitted to volunteer.

I don't have an opinion as to whether we pick an appeals panel
for a year just in case we need them or pick them only when a
sufficient process appeal arises.  It is not clear to me that it
makes much difference -- except that, if they were picked on
demand, we might just take the attendance list from the last few
meetings and draw people from it on an "attendance subjects one
to the risk on volunteering" basis.  That has some drawbacks but
some appeal.

For the technical error questions, it is still not clear to me
that IAB is the right appeals body, especially if they were
active in formulating the position under appeal or an alternate
to it.   A randomly-chosen jury might still work, but might well
not have the right technical expertise.  As one possibility, we
could move toward a formalized blue-ribbon review and mediation
panel, with members of that panel being chosen by IESG, the WG
leadership, and the individual or group launching the appeal.
If it was appropriate to populate that panel with IAB members,
that would be fine, but the review itself would not be an IAB
responsibility.   If the panel didn't behave fairly, that
becomes a procedural question, and the appeals board outlined
above takes over.

................................................................

It seems that the only thing that I can do is keeping records
on who's who were on the board (+when), plus who were the nomcom 
who had elected them. Let the Vulcans, Klingons, and 
Ferengis make the final judgements in the next millennium.


tabe,

-- 
- Rahmat M. Samik-Ibrahim --  VLSM-TJT --  http://rms46.vlsm.org/ -
- Always select ShutDown from the StartMenu - M$Windows after crash




From owner-ietf-outbound  Sat Feb 12 05:50:27 2000
Received: by ietf.org (8.9.1a/8.9.1a) id FAA20100
	for ietf-outbound.10@ietf.org; Sat, 12 Feb 2000 05:50:02 -0500 (EST)
Received: from A4.JCK.COM (ns.jck.com [63.65.7.140])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA20076
	for <ietf@ietf.org>; Sat, 12 Feb 2000 05:46:49 -0500 (EST)
Received: from p2.jck.com ("port 2066"@[63.65.7.138])
 by a4.jck.com (PMDF V6.0-20 #40360) with ESMTP id <0FPT00PECCM97Q@a4.jck.com>
 for ietf@ietf.org; Sat, 12 Feb 2000 05:46:57 -0500 (EST)
Date: Sat, 12 Feb 2000 05:46:50 -0500
From: John C Klensin <klensin@jck.com>
Subject: Re: 1601bis: The Charter of IAB
In-reply-to: <38A50049.7851A5BF@oke.com>
To: "Rahmat M. Samik-Ibrahim" <ms46.oke.com@vlsm.org>
Cc: ietf@ietf.org
Message-id: <1146637804.950334410@p2.jck.com>
MIME-version: 1.0
X-Mailer: Mulberry/2.0.0b8 (Win32)
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7bit
Content-disposition: inline
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

--On Saturday, 12 February, 2000 14:40 +0800 "Rahmat M. 
Samik-Ibrahim" <rms46@oke.com> wrote:

> I also believe what Klensin wrote is still valid:
>
> ..............................................................
> ........
>
> [... 22 Feb 1996 ... skipping voting out of existence, fine
> lunches  and dinners, and irresolvable controversy
>   pronouncements...]

My, my, do I love being quoted out of context on a comment that 
was made four years ago, and was intended as humorous rather 
than a serious comment on the process.  I don't remember the 
comment or its context, but strongly suspect from the partial 
sentence excerpt that it was _never_ "valid" except as a 
sarcastic and/or cynical remark, made in passing and intended to 
mean the opposite.

Rahmat, this is one of the difficulties with the path you seem 
to want us to go down.  Except when formally hearing an appeal 
and, possibly in a very small number of other cases (I can't 
identify any at the moment, but don't want to get into a 
nit-picking argument with you about whether they exist), the IAB 
isn't a formal deliberative body.  And, even when we face those 
more formal situations, we are not, as we pointed out recently 
in another context,  a court of law and will not try to behave 
like one.  Instead, we operate very informally, as a collection 
of people trying to collectively understand issues and help the 
IETF move forward.   All of those people bring strong technical 
skills and experience to the table, rather than being 
professional or amateur lawyers or the like.  If you don't like 
the composition of the IAB in terms of the individual profiles 
and personalities, that is a Nomcom  issue, not a charter or 
procedural one.

In working informally --with each other and with the IETF 
participant community (especially those who are making technical 
contributions)-- we also tend to be human.  Under stress, some 
of us even become cynical or engage, informally, in what we call 
in the US "black humor".  So, as you must know, do several other 
professional population groups: this shouldn't be any surprise 
or cause for concern.  But that informal process is precisely 
what permits us to work as a team, in spite of different 
backgrounds and perspectives, and quite often come up with 
results that are clearer and better than any of us could have 
produced alone.  Tying us up in procedures, or requirements that 
we expose and document every word spoken or written, would, at a 
minimum, cripple our ability to get anything done.  That would, 
of cousre, prevent our doing harm by preventing our doing 
anything, but I, at least, don't see that as in the best 
interests of the IETF or the Internet generally.

I think those of us who have been following your notes over the 
last few years understand your concerns but generally do not 
agree.  As, I believe (haven't checked), the only member of the 
current or upcoming IAB with significant professional training 
in the social and behavioral sciences, I am probably more 
sympathetic than most to your desire for a clear historical 
record.  But --precisely because I continue to be interested in 
the interactions between process, formal procedures, and 
results-- I don't think it is productive in this case, 
especially to what, IMO, is the extreme to which you want to 
take things.  More specifically, I would personally prefer to 
avoid turning the IETF, or any of the related or subsidiary 
structures, into an experiment in political theory or utopianism 
(mine or anyone else's).

With regard to your substantive comments about appeals and jury 
processes... The reality is that all of the appeals that have 
reached the IAB within my memory have involved significant and 
often complex technical components, typically including 
questions of whether WG, WG Chair, or IESG decisions on a 
particular issue were reasonable in the light of some technical 
argument.   They haven't been exclusively procedural, or 
exclusively technical, but a inseparable mix of the two.    In 
the "outside world", the historical experience with 
randomly-chosen juries in that type of situation has been fairly 
terrible.  That is not surprising: if one doesn't understand the 
issues but is forced to make a decision, one decides on some 
other basis.  It is also well-known that, if the randomly-chosen 
members of the jury can be educated about the issues, then 
results get better: but that is a time-consuming process and can 
easily lead to claims about the biases of the educators who 
must, recursively, be selected and/or monitored by some process 
that reduces or eliminates those concerns.

Now, if we were dealing with exclusively procedural appeals, I 
would agree with you that an independently-selected appeals 
body, one that could deal with conflicting claims about what had 
occurred on an adversarial and evidentary basis, would be a 
better and more convenient idea.  I actually suggested that a 
few years ago, possibly in the document from which you extracted 
the above, because I assumed we would see mostly that type of 
appeal.  But, if I recall, the community rather throughly 
rejected that idea.  And, in retrospect, I'd assume that at 
least part of the reason was that I was wrong: while there would 
still be some attraction to getting appeal work off the IAB's 
agenda (my other motivation at the time), we haven't seen those 
types of appeals.

I could quibble with some of your other suggestions (e.g., 
picking people conditioned on attendance would result in an 
uncomfortably biased (in the statistical sense) group, 
especially if an appeal addressed the way in which a 
mailing-list-only participant was being treated.  But it isn't 
worth it: the general idea itself is fatally flawed by an 
incorrect assumption about the nature of the appeals that arise.

Conversely, blue-ribbon appeals panels for more technical issue 
have some logical appeal, but would, I believe, create a 
different sort of bias, one that involves very slow procedures 
and responses.  And a non-trivial fraction of IETF participants 
seem to have a deep suspicion that people who _really_ want to 
serve on such things should be disqualified as 
non-representative of the community, if not outright insane, 
which is probably not a good basis for trust in such panels.

The system isn't perfect, but options such as the ones you 
suggest were considered and the conclusion was that, on balance, 
the present setup isn't significantly worse than other possible 
choices and better than many of them.  And I think actual 
experience so far, as distinct from theorizing about 
possibilties for what might happen or about ideal processes, has 
largely confirmed the acceptability of those choices.

     john

p.s. The above remarks have not been examined to be sure that no 
word could possibly be misinterpreted by someone inclined to do 
so.  So now I guess I get to spend the next year or four 
worrying about which phrases will be taken out of context and 
used ot demonstrate something I don't believe (either now or "by 
then")  :-(




From owner-ietf-outbound@ietf.org  Sat Feb 12 05:51:26 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA20153
	for <ietf-web-archive@odin.ietf.org>; Sat, 12 Feb 2000 05:51:26 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA20680;
	Sat, 12 Feb 2000 05:49:27 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id FAA20100
	for ietf-outbound.10@ietf.org; Sat, 12 Feb 2000 05:50:02 -0500 (EST)
Received: from A4.JCK.COM (ns.jck.com [63.65.7.140])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA20076
	for <ietf@ietf.org>; Sat, 12 Feb 2000 05:46:49 -0500 (EST)
Received: from p2.jck.com ("port 2066"@[63.65.7.138])
 by a4.jck.com (PMDF V6.0-20 #40360) with ESMTP id <0FPT00PECCM97Q@a4.jck.com>
 for ietf@ietf.org; Sat, 12 Feb 2000 05:46:57 -0500 (EST)
Date: Sat, 12 Feb 2000 05:46:50 -0500
From: John C Klensin <klensin@jck.com>
Subject: Re: 1601bis: The Charter of IAB
In-reply-to: <38A50049.7851A5BF@oke.com>
To: "Rahmat M. Samik-Ibrahim" <ms46.oke.com@vlsm.org>
Cc: ietf@ietf.org
Message-id: <1146637804.950334410@p2.jck.com>
MIME-version: 1.0
X-Mailer: Mulberry/2.0.0b8 (Win32)
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7bit
Content-disposition: inline
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

--On Saturday, 12 February, 2000 14:40 +0800 "Rahmat M. 
Samik-Ibrahim" <rms46@oke.com> wrote:

> I also believe what Klensin wrote is still valid:
>
> ..............................................................
> ........
>
> [... 22 Feb 1996 ... skipping voting out of existence, fine
> lunches  and dinners, and irresolvable controversy
>   pronouncements...]

My, my, do I love being quoted out of context on a comment that 
was made four years ago, and was intended as humorous rather 
than a serious comment on the process.  I don't remember the 
comment or its context, but strongly suspect from the partial 
sentence excerpt that it was _never_ "valid" except as a 
sarcastic and/or cynical remark, made in passing and intended to 
mean the opposite.

Rahmat, this is one of the difficulties with the path you seem 
to want us to go down.  Except when formally hearing an appeal 
and, possibly in a very small number of other cases (I can't 
identify any at the moment, but don't want to get into a 
nit-picking argument with you about whether they exist), the IAB 
isn't a formal deliberative body.  And, even when we face those 
more formal situations, we are not, as we pointed out recently 
in another context,  a court of law and will not try to behave 
like one.  Instead, we operate very informally, as a collection 
of people trying to collectively understand issues and help the 
IETF move forward.   All of those people bring strong technical 
skills and experience to the table, rather than being 
professional or amateur lawyers or the like.  If you don't like 
the composition of the IAB in terms of the individual profiles 
and personalities, that is a Nomcom  issue, not a charter or 
procedural one.

In working informally --with each other and with the IETF 
participant community (especially those who are making technical 
contributions)-- we also tend to be human.  Under stress, some 
of us even become cynical or engage, informally, in what we call 
in the US "black humor".  So, as you must know, do several other 
professional population groups: this shouldn't be any surprise 
or cause for concern.  But that informal process is precisely 
what permits us to work as a team, in spite of different 
backgrounds and perspectives, and quite often come up with 
results that are clearer and better than any of us could have 
produced alone.  Tying us up in procedures, or requirements that 
we expose and document every word spoken or written, would, at a 
minimum, cripple our ability to get anything done.  That would, 
of cousre, prevent our doing harm by preventing our doing 
anything, but I, at least, don't see that as in the best 
interests of the IETF or the Internet generally.

I think those of us who have been following your notes over the 
last few years understand your concerns but generally do not 
agree.  As, I believe (haven't checked), the only member of the 
current or upcoming IAB with significant professional training 
in the social and behavioral sciences, I am probably more 
sympathetic than most to your desire for a clear historical 
record.  But --precisely because I continue to be interested in 
the interactions between process, formal procedures, and 
results-- I don't think it is productive in this case, 
especially to what, IMO, is the extreme to which you want to 
take things.  More specifically, I would personally prefer to 
avoid turning the IETF, or any of the related or subsidiary 
structures, into an experiment in political theory or utopianism 
(mine or anyone else's).

With regard to your substantive comments about appeals and jury 
processes... The reality is that all of the appeals that have 
reached the IAB within my memory have involved significant and 
often complex technical components, typically including 
questions of whether WG, WG Chair, or IESG decisions on a 
particular issue were reasonable in the light of some technical 
argument.   They haven't been exclusively procedural, or 
exclusively technical, but a inseparable mix of the two.    In 
the "outside world", the historical experience with 
randomly-chosen juries in that type of situation has been fairly 
terrible.  That is not surprising: if one doesn't understand the 
issues but is forced to make a decision, one decides on some 
other basis.  It is also well-known that, if the randomly-chosen 
members of the jury can be educated about the issues, then 
results get better: but that is a time-consuming process and can 
easily lead to claims about the biases of the educators who 
must, recursively, be selected and/or monitored by some process 
that reduces or eliminates those concerns.

Now, if we were dealing with exclusively procedural appeals, I 
would agree with you that an independently-selected appeals 
body, one that could deal with conflicting claims about what had 
occurred on an adversarial and evidentary basis, would be a 
better and more convenient idea.  I actually suggested that a 
few years ago, possibly in the document from which you extracted 
the above, because I assumed we would see mostly that type of 
appeal.  But, if I recall, the community rather throughly 
rejected that idea.  And, in retrospect, I'd assume that at 
least part of the reason was that I was wrong: while there would 
still be some attraction to getting appeal work off the IAB's 
agenda (my other motivation at the time), we haven't seen those 
types of appeals.

I could quibble with some of your other suggestions (e.g., 
picking people conditioned on attendance would result in an 
uncomfortably biased (in the statistical sense) group, 
especially if an appeal addressed the way in which a 
mailing-list-only participant was being treated.  But it isn't 
worth it: the general idea itself is fatally flawed by an 
incorrect assumption about the nature of the appeals that arise.

Conversely, blue-ribbon appeals panels for more technical issue 
have some logical appeal, but would, I believe, create a 
different sort of bias, one that involves very slow procedures 
and responses.  And a non-trivial fraction of IETF participants 
seem to have a deep suspicion that people who _really_ want to 
serve on such things should be disqualified as 
non-representative of the community, if not outright insane, 
which is probably not a good basis for trust in such panels.

The system isn't perfect, but options such as the ones you 
suggest were considered and the conclusion was that, on balance, 
the present setup isn't significantly worse than other possible 
choices and better than many of them.  And I think actual 
experience so far, as distinct from theorizing about 
possibilties for what might happen or about ideal processes, has 
largely confirmed the acceptability of those choices.

     john

p.s. The above remarks have not been examined to be sure that no 
word could possibly be misinterpreted by someone inclined to do 
so.  So now I guess I get to spend the next year or four 
worrying about which phrases will be taken out of context and 
used ot demonstrate something I don't believe (either now or "by 
then")  :-(




From owner-ietf-outbound  Sat Feb 12 08:00:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA21267
	for ietf-outbound.10@ietf.org; Sat, 12 Feb 2000 08:00:02 -0500 (EST)
Received: from kuji.off.connect.com.au (kuji.off.connect.com.au [203.63.69.33])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA21195
	for <IETF@ietf.org>; Sat, 12 Feb 2000 07:50:15 -0500 (EST)
Received: from connect.com.au (mrp@localhost) by kuji.off.connect.com.au with ESMTP id XAA02647
  (8.8.8/IDA-1.6); Sat, 12 Feb 2000 23:18:55 +1030 (CST)
Message-ID: <200002121248.XAA02647@kuji.off.connect.com.au>
To: Paul Ferguson <ferguson@cisco.com>
cc: Vijay Gill <wrath@cs.umbc.edu>, John Stracke <francis@ecal.com>,
        IETF@ietf.org, nanog@merit.edu
Subject: Re: Internet SYN Flooding, spoofing attacks
In-reply-to: Your message of "Fri, 11 Feb 2000 21:09:47 CDT."
             <4.2.2.20000211210210.00a4e880@lint.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2645.950359733.1@connect.com.au>
Date: Sat, 12 Feb 2000 23:18:54 +1030
From: Mark Prior <mrp@connect.com.au>
X-Loop: ietf@ietf.org

     We (at least cisco, anyways) already have a knob for this:

       [no] ip verify unicast reverse-path

     We call it Unicast RPF.

And its well documented... NOT
and available on all routers/interfaces... NOT

If it was documented and available on things like PRIs then it would
be a lot easier to deploy. Also some of the bugs that turn off CEF
need to be addressed (or at least also cause "ip verify unicast
reverse-path" to be turned off too).

Mark.



From owner-ietf-outbound@ietf.org  Sat Feb 12 08:02:31 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA21431
	for <ietf-web-archive@odin.ietf.org>; Sat, 12 Feb 2000 08:02:31 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA22182;
	Sat, 12 Feb 2000 08:00:31 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id IAA21267
	for ietf-outbound.10@ietf.org; Sat, 12 Feb 2000 08:00:02 -0500 (EST)
Received: from kuji.off.connect.com.au (kuji.off.connect.com.au [203.63.69.33])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA21195
	for <IETF@ietf.org>; Sat, 12 Feb 2000 07:50:15 -0500 (EST)
Received: from connect.com.au (mrp@localhost) by kuji.off.connect.com.au with ESMTP id XAA02647
  (8.8.8/IDA-1.6); Sat, 12 Feb 2000 23:18:55 +1030 (CST)
Message-ID: <200002121248.XAA02647@kuji.off.connect.com.au>
To: Paul Ferguson <ferguson@cisco.com>
cc: Vijay Gill <wrath@cs.umbc.edu>, John Stracke <francis@ecal.com>,
        IETF@ietf.org, nanog@merit.edu
Subject: Re: Internet SYN Flooding, spoofing attacks
In-reply-to: Your message of "Fri, 11 Feb 2000 21:09:47 CDT."
             <4.2.2.20000211210210.00a4e880@lint.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2645.950359733.1@connect.com.au>
Date: Sat, 12 Feb 2000 23:18:54 +1030
From: Mark Prior <mrp@connect.com.au>
X-Loop: ietf@ietf.org

     We (at least cisco, anyways) already have a knob for this:

       [no] ip verify unicast reverse-path

     We call it Unicast RPF.

And its well documented... NOT
and available on all routers/interfaces... NOT

If it was documented and available on things like PRIs then it would
be a lot easier to deploy. Also some of the bugs that turn off CEF
need to be addressed (or at least also cause "ip verify unicast
reverse-path" to be turned off too).

Mark.



From owner-ietf-outbound  Sat Feb 12 08:10:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA21550
	for ietf-outbound.10@ietf.org; Sat, 12 Feb 2000 08:10:02 -0500 (EST)
Received: from kuji.off.connect.com.au (kuji.off.connect.com.au [203.63.69.33])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA21207
	for <IETF@ietf.org>; Sat, 12 Feb 2000 07:51:49 -0500 (EST)
Received: from connect.com.au (mrp@localhost) by kuji.off.connect.com.au with ESMTP id XAA02700
  (8.8.8/IDA-1.6); Sat, 12 Feb 2000 23:20:29 +1030 (CST)
Message-ID: <200002121250.XAA02700@kuji.off.connect.com.au>
To: Paul Ferguson <ferguson@cisco.com>
cc: Vijay Gill <wrath@cs.umbc.edu>, John Stracke <francis@ecal.com>,
        IETF@ietf.org, nanog@merit.edu
Subject: Re: Internet SYN Flooding, spoofing attacks
In-reply-to: Your message of "Fri, 11 Feb 2000 21:19:09 CDT."
             <4.2.2.20000211211503.00a53bb0@lint.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2698.950359827.1@connect.com.au>
Date: Sat, 12 Feb 2000 23:20:28 +1030
From: Mark Prior <mrp@connect.com.au>
X-Loop: ietf@ietf.org

     This is a small percentage, I would thing, since the percentage of
     ISP's offering transit pales in comparison to all other "access"
     ISP's that do not. And in cases where ISP's _do_ offer transit, or
     have transit agreements, will they really do this on their transit
     interfaces? I think not.

Maybe not as small as you think when simplex satellite is involved.

Mark.



From owner-ietf-outbound@ietf.org  Sat Feb 12 08:12:14 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA21619
	for <ietf-web-archive@odin.ietf.org>; Sat, 12 Feb 2000 08:12:14 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA22234;
	Sat, 12 Feb 2000 08:10:16 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id IAA21550
	for ietf-outbound.10@ietf.org; Sat, 12 Feb 2000 08:10:02 -0500 (EST)
Received: from kuji.off.connect.com.au (kuji.off.connect.com.au [203.63.69.33])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA21207
	for <IETF@ietf.org>; Sat, 12 Feb 2000 07:51:49 -0500 (EST)
Received: from connect.com.au (mrp@localhost) by kuji.off.connect.com.au with ESMTP id XAA02700
  (8.8.8/IDA-1.6); Sat, 12 Feb 2000 23:20:29 +1030 (CST)
Message-ID: <200002121250.XAA02700@kuji.off.connect.com.au>
To: Paul Ferguson <ferguson@cisco.com>
cc: Vijay Gill <wrath@cs.umbc.edu>, John Stracke <francis@ecal.com>,
        IETF@ietf.org, nanog@merit.edu
Subject: Re: Internet SYN Flooding, spoofing attacks
In-reply-to: Your message of "Fri, 11 Feb 2000 21:19:09 CDT."
             <4.2.2.20000211211503.00a53bb0@lint.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2698.950359827.1@connect.com.au>
Date: Sat, 12 Feb 2000 23:20:28 +1030
From: Mark Prior <mrp@connect.com.au>
X-Loop: ietf@ietf.org

     This is a small percentage, I would thing, since the percentage of
     ISP's offering transit pales in comparison to all other "access"
     ISP's that do not. And in cases where ISP's _do_ offer transit, or
     have transit agreements, will they really do this on their transit
     interfaces? I think not.

Maybe not as small as you think when simplex satellite is involved.

Mark.



From owner-ietf-outbound  Sat Feb 12 14:51:37 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA25114
	for ietf-outbound.10@ietf.org; Sat, 12 Feb 2000 14:50:01 -0500 (EST)
Received: from dfw-smtpout1.email.verio.net (dfw-smtpout1.email.verio.net [129.250.36.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25057
	for <ietf@ietf.org>; Sat, 12 Feb 2000 14:41:49 -0500 (EST)
Received: from [129.250.38.61] (helo=dfw-mmp1.email.verio.net)
	by dfw-smtpout1.email.verio.net with esmtp (Exim 3.12 #7)
	id 12JiQL-0004qu-00
	for ietf@ietf.org; Sat, 12 Feb 2000 19:41:45 +0000
Received: from [209.21.28.65] (helo=nma.com)
	by dfw-mmp1.email.verio.net with esmtp (Exim 3.12 #7)
	id 12JiPr-0004m0-00
	for ietf@ietf.org; Sat, 12 Feb 2000 19:41:15 +0000
Message-ID: <38A5B73D.C5D7A2AE@nma.com>
Date: Sat, 12 Feb 2000 11:40:45 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony}  (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Announcement ivta.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

List:

                  Announcement ivta.org

Internet voting is a case where privacy must be protected, so that
arguments to justify losing voter privacy in the good name of security
are simply not possible.  Which  firmly posits security  as a protection
of privacy -- not as an enemy of privacy -- in the problem-solving
assumptions to be considered.

In this context, an international team of experts and companies are calling for
open discussions on Internet voting technology.  A public founding
assembly will take place February 28 in Washington D.C. at 9 a.m.

Details at http://www.ivta.org

Cheers,

Ed Gerck



From owner-ietf-outbound@ietf.org  Sat Feb 12 14:53:59 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25192
	for <ietf-web-archive@odin.ietf.org>; Sat, 12 Feb 2000 14:53:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA26181;
	Sat, 12 Feb 2000 14:51:57 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id OAA25114
	for ietf-outbound.10@ietf.org; Sat, 12 Feb 2000 14:50:01 -0500 (EST)
Received: from dfw-smtpout1.email.verio.net (dfw-smtpout1.email.verio.net [129.250.36.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25057
	for <ietf@ietf.org>; Sat, 12 Feb 2000 14:41:49 -0500 (EST)
Received: from [129.250.38.61] (helo=dfw-mmp1.email.verio.net)
	by dfw-smtpout1.email.verio.net with esmtp (Exim 3.12 #7)
	id 12JiQL-0004qu-00
	for ietf@ietf.org; Sat, 12 Feb 2000 19:41:45 +0000
Received: from [209.21.28.65] (helo=nma.com)
	by dfw-mmp1.email.verio.net with esmtp (Exim 3.12 #7)
	id 12JiPr-0004m0-00
	for ietf@ietf.org; Sat, 12 Feb 2000 19:41:15 +0000
Message-ID: <38A5B73D.C5D7A2AE@nma.com>
Date: Sat, 12 Feb 2000 11:40:45 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony}  (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Announcement ivta.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

List:

                  Announcement ivta.org

Internet voting is a case where privacy must be protected, so that
arguments to justify losing voter privacy in the good name of security
are simply not possible.  Which  firmly posits security  as a protection
of privacy -- not as an enemy of privacy -- in the problem-solving
assumptions to be considered.

In this context, an international team of experts and companies are calling for
open discussions on Internet voting technology.  A public founding
assembly will take place February 28 in Washington D.C. at 9 a.m.

Details at http://www.ivta.org

Cheers,

Ed Gerck



From owner-ietf-outbound  Sat Feb 12 15:30:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA25631
	for ietf-outbound.10@ietf.org; Sat, 12 Feb 2000 15:30:02 -0500 (EST)
Received: from proxy4.ba.best.com (root@proxy4.ba.best.com [206.184.139.15])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25593
	for <ietf@ietf.org>; Sat, 12 Feb 2000 15:27:21 -0500 (EST)
Received: from kaipara (mg130-170.ricochet.net [204.179.130.170])
	by proxy4.ba.best.com (8.9.3/8.9.2/best.out) with SMTP id MAA20617;
	Sat, 12 Feb 2000 12:25:16 -0800 (PST)
Message-Id: <3.0.6.32.20000212122505.008fbc20@shell7.ba.best.com>
X-Sender: rsf@shell7.ba.best.com
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32)
Date: Sat, 12 Feb 2000 12:25:05 -0800
To: Ed Gerck <egerck@nma.com>
From: Ross Finlayson <finlayson@live.com>
Subject: Re: Announcement ivta.org
Cc: ietf@ietf.org
In-Reply-To: <38A5B73D.C5D7A2AE@nma.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

From the web site:

"The IVTA takes much of its spirit from the Internet Engineering Task Force
(IETF)"

and

"The development of public standards at the IVTA is specific for Internet
voting applications, but otherwise similar to the work at the IETF and
other Internet standards bodies."


That's good, but why not undertake this within the existing IETF process,
rather than trying to emulate it?

	Ross.




From owner-ietf-outbound@ietf.org  Sat Feb 12 15:36:10 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25790
	for <ietf-web-archive@odin.ietf.org>; Sat, 12 Feb 2000 15:36:10 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA26644;
	Sat, 12 Feb 2000 15:34:09 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id PAA25631
	for ietf-outbound.10@ietf.org; Sat, 12 Feb 2000 15:30:02 -0500 (EST)
Received: from proxy4.ba.best.com (root@proxy4.ba.best.com [206.184.139.15])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25593
	for <ietf@ietf.org>; Sat, 12 Feb 2000 15:27:21 -0500 (EST)
Received: from kaipara (mg130-170.ricochet.net [204.179.130.170])
	by proxy4.ba.best.com (8.9.3/8.9.2/best.out) with SMTP id MAA20617;
	Sat, 12 Feb 2000 12:25:16 -0800 (PST)
Message-Id: <3.0.6.32.20000212122505.008fbc20@shell7.ba.best.com>
X-Sender: rsf@shell7.ba.best.com
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32)
Date: Sat, 12 Feb 2000 12:25:05 -0800
To: Ed Gerck <egerck@nma.com>
From: Ross Finlayson <finlayson@live.com>
Subject: Re: Announcement ivta.org
Cc: ietf@ietf.org
In-Reply-To: <38A5B73D.C5D7A2AE@nma.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

From the web site:

"The IVTA takes much of its spirit from the Internet Engineering Task Force
(IETF)"

and

"The development of public standards at the IVTA is specific for Internet
voting applications, but otherwise similar to the work at the IETF and
other Internet standards bodies."


That's good, but why not undertake this within the existing IETF process,
rather than trying to emulate it?

	Ross.




From owner-ietf-outbound  Sat Feb 12 15:40:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA25853
	for ietf-outbound.10@ietf.org; Sat, 12 Feb 2000 15:40:03 -0500 (EST)
Received: from dfw-smtpout2.email.verio.net (dfw-smtpout2.email.verio.net [129.250.36.42])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25741
	for <ietf@ietf.org>; Sat, 12 Feb 2000 15:33:54 -0500 (EST)
Received: from [129.250.38.63] (helo=dfw-mmp3.email.verio.net)
	by dfw-smtpout2.email.verio.net with esmtp (Exim 3.12 #7)
	id 12JjEo-0005p8-00; Sat, 12 Feb 2000 20:33:54 +0000
Received: from [209.21.28.105] (helo=nma.com)
	by dfw-mmp3.email.verio.net with esmtp (Exim 3.12 #7)
	id 12JjE5-0007SK-00; Sat, 12 Feb 2000 20:33:10 +0000
Message-ID: <38A5C375.780C716F@nma.com>
Date: Sat, 12 Feb 2000 12:32:53 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony}  (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Ross Finlayson <finlayson@live.com>
CC: ietf@ietf.org
Subject: Re: Announcement ivta.org
References: <3.0.6.32.20000212122505.008fbc20@shell7.ba.best.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit



Ross Finlayson wrote:

> >From the web site:
>
> "The IVTA takes much of its spirit from the Internet Engineering Task Force
> (IETF)"
>
> and
>
> "The development of public standards at the IVTA is specific for Internet
> voting applications, but otherwise similar to the work at the IETF and
> other Internet standards bodies."
>
> That's good, but why not undertake this within the existing IETF process,
> rather than trying to emulate it?

Because it is outside the scope of the IETF.

Cheers,

Ed Gerck




From owner-ietf-outbound@ietf.org  Sat Feb 12 15:44:10 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25941
	for <ietf-web-archive@odin.ietf.org>; Sat, 12 Feb 2000 15:44:10 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA26719;
	Sat, 12 Feb 2000 15:42:11 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id PAA25853
	for ietf-outbound.10@ietf.org; Sat, 12 Feb 2000 15:40:03 -0500 (EST)
Received: from dfw-smtpout2.email.verio.net (dfw-smtpout2.email.verio.net [129.250.36.42])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25741
	for <ietf@ietf.org>; Sat, 12 Feb 2000 15:33:54 -0500 (EST)
Received: from [129.250.38.63] (helo=dfw-mmp3.email.verio.net)
	by dfw-smtpout2.email.verio.net with esmtp (Exim 3.12 #7)
	id 12JjEo-0005p8-00; Sat, 12 Feb 2000 20:33:54 +0000
Received: from [209.21.28.105] (helo=nma.com)
	by dfw-mmp3.email.verio.net with esmtp (Exim 3.12 #7)
	id 12JjE5-0007SK-00; Sat, 12 Feb 2000 20:33:10 +0000
Message-ID: <38A5C375.780C716F@nma.com>
Date: Sat, 12 Feb 2000 12:32:53 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony}  (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Ross Finlayson <finlayson@live.com>
CC: ietf@ietf.org
Subject: Re: Announcement ivta.org
References: <3.0.6.32.20000212122505.008fbc20@shell7.ba.best.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit



Ross Finlayson wrote:

> >From the web site:
>
> "The IVTA takes much of its spirit from the Internet Engineering Task Force
> (IETF)"
>
> and
>
> "The development of public standards at the IVTA is specific for Internet
> voting applications, but otherwise similar to the work at the IETF and
> other Internet standards bodies."
>
> That's good, but why not undertake this within the existing IETF process,
> rather than trying to emulate it?

Because it is outside the scope of the IETF.

Cheers,

Ed Gerck




From owner-ietf-outbound  Sat Feb 12 16:00:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA26084
	for ietf-outbound.10@ietf.org; Sat, 12 Feb 2000 16:00:02 -0500 (EST)
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26013
	for <ietf@ietf.org>; Sat, 12 Feb 2000 15:53:49 -0500 (EST)
Received: from laptop (ip12.proper.com [165.227.249.12])
	by ns.secondary.com (8.9.3/8.9.3) with ESMTP id MAA04420
	for <ietf@ietf.org>; Sat, 12 Feb 2000 12:50:35 -0800 (PST)
Message-Id: <4.2.1.20000212124942.00bf2780@mail.imc.org>
X-Sender: phoffman@mail.imc.org
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.1 
Date: Sat, 12 Feb 2000 12:54:56 -0800
To: ietf@ietf.org
From: Paul Hoffman / IMC <phoffman@IMC.ORG>
Subject: Re: Announcement ivta.org
In-Reply-To: <38A5C375.780C716F@nma.com>
References: <3.0.6.32.20000212122505.008fbc20@shell7.ba.best.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 12:32 PM 2/12/00 -0800, Ed Gerck wrote:
>Ross Finlayson wrote:
> > That's good, but why not undertake this within the existing IETF process,
> > rather than trying to emulate it?
>
>Because it is outside the scope of the IETF.

For once, Ed and I might be in agreement on something. The IETF has already 
done all the technical groundwork needed for the process. They've got 
OpenPGP or S/MIME for the format of the messages, TLS or IPsec for 
transmission of any unencrypted content, and PKIX for certificates. All are 
on standards track. They can give privacy and authentication.

The remaining questions might be what needs to be private or public, what 
needs to be authenticated, and who the authenticating authority is. This 
doesn't sound like a job for the IETF, although I'm sure many IETF folks 
will want to participate or at least watch. We might even pull out our 
sharpened sticks if any of the participants say things like "our 
proprietary technology which is more secure" or such things.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-ietf-outbound@ietf.org  Sat Feb 12 16:03:20 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26227
	for <ietf-web-archive@odin.ietf.org>; Sat, 12 Feb 2000 16:03:20 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA26975;
	Sat, 12 Feb 2000 16:01:21 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id QAA26084
	for ietf-outbound.10@ietf.org; Sat, 12 Feb 2000 16:00:02 -0500 (EST)
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26013
	for <ietf@ietf.org>; Sat, 12 Feb 2000 15:53:49 -0500 (EST)
Received: from laptop (ip12.proper.com [165.227.249.12])
	by ns.secondary.com (8.9.3/8.9.3) with ESMTP id MAA04420
	for <ietf@ietf.org>; Sat, 12 Feb 2000 12:50:35 -0800 (PST)
Message-Id: <4.2.1.20000212124942.00bf2780@mail.imc.org>
X-Sender: phoffman@mail.imc.org
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.1 
Date: Sat, 12 Feb 2000 12:54:56 -0800
To: ietf@ietf.org
From: Paul Hoffman / IMC <phoffman@IMC.ORG>
Subject: Re: Announcement ivta.org
In-Reply-To: <38A5C375.780C716F@nma.com>
References: <3.0.6.32.20000212122505.008fbc20@shell7.ba.best.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 12:32 PM 2/12/00 -0800, Ed Gerck wrote:
>Ross Finlayson wrote:
> > That's good, but why not undertake this within the existing IETF process,
> > rather than trying to emulate it?
>
>Because it is outside the scope of the IETF.

For once, Ed and I might be in agreement on something. The IETF has already 
done all the technical groundwork needed for the process. They've got 
OpenPGP or S/MIME for the format of the messages, TLS or IPsec for 
transmission of any unencrypted content, and PKIX for certificates. All are 
on standards track. They can give privacy and authentication.

The remaining questions might be what needs to be private or public, what 
needs to be authenticated, and who the authenticating authority is. This 
doesn't sound like a job for the IETF, although I'm sure many IETF folks 
will want to participate or at least watch. We might even pull out our 
sharpened sticks if any of the participants say things like "our 
proprietary technology which is more secure" or such things.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-ietf-outbound  Sat Feb 12 16:10:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA26315
	for ietf-outbound.10@ietf.org; Sat, 12 Feb 2000 16:10:02 -0500 (EST)
Received: from also.media.org (also.media.org [204.62.246.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26020
	for <ietf@ietf.org>; Sat, 12 Feb 2000 15:53:55 -0500 (EST)
Received: (from carl@localhost)
	by also.media.org (8.9.3+Sun/8.9.3/981111bjb) id PAA16218;
	Sat, 12 Feb 2000 15:53:42 -0500 (EST)
From: Carl Malamud <carl@invisible.net>
Message-Id: <200002122053.PAA16218@also.media.org>
Subject: Re: Announcement ivta.org
To: egerck@nma.com (Ed Gerck)
Date: Sat, 12 Feb 2000 15:53:41 -0500 (EST)
Cc: finlayson@live.com (Ross Finlayson), ietf@ietf.org
In-Reply-To: <38A5C375.780C716F@nma.com> from "Ed Gerck" at Feb 12, 2000 12:32:53 PM
Organization: Invisible Worlds, Inc.
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

If it is outside the scope of the IETF, why send the announcement
to the IETF list?  :))

Carl

According to Ed Gerck:

> Ross Finlayson wrote:

> > >From the web site:
> >
> > "The IVTA takes much of its spirit from the Internet Engineering Task Force
> > (IETF)"
> >
> > and
> >
> > "The development of public standards at the IVTA is specific for Internet
> > voting applications, but otherwise similar to the work at the IETF and
> > other Internet standards bodies."
> >
> > That's good, but why not undertake this within the existing IETF process,
> > rather than trying to emulate it?

> Because it is outside the scope of the IETF.

> Cheers,

> Ed Gerck



From owner-ietf-outbound@ietf.org  Sat Feb 12 16:12:37 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26396
	for <ietf-web-archive@odin.ietf.org>; Sat, 12 Feb 2000 16:12:37 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA27065;
	Sat, 12 Feb 2000 16:10:38 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id QAA26315
	for ietf-outbound.10@ietf.org; Sat, 12 Feb 2000 16:10:02 -0500 (EST)
Received: from also.media.org (also.media.org [204.62.246.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26020
	for <ietf@ietf.org>; Sat, 12 Feb 2000 15:53:55 -0500 (EST)
Received: (from carl@localhost)
	by also.media.org (8.9.3+Sun/8.9.3/981111bjb) id PAA16218;
	Sat, 12 Feb 2000 15:53:42 -0500 (EST)
From: Carl Malamud <carl@invisible.net>
Message-Id: <200002122053.PAA16218@also.media.org>
Subject: Re: Announcement ivta.org
To: egerck@nma.com (Ed Gerck)
Date: Sat, 12 Feb 2000 15:53:41 -0500 (EST)
Cc: finlayson@live.com (Ross Finlayson), ietf@ietf.org
In-Reply-To: <38A5C375.780C716F@nma.com> from "Ed Gerck" at Feb 12, 2000 12:32:53 PM
Organization: Invisible Worlds, Inc.
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

If it is outside the scope of the IETF, why send the announcement
to the IETF list?  :))

Carl

According to Ed Gerck:

> Ross Finlayson wrote:

> > >From the web site:
> >
> > "The IVTA takes much of its spirit from the Internet Engineering Task Force
> > (IETF)"
> >
> > and
> >
> > "The development of public standards at the IVTA is specific for Internet
> > voting applications, but otherwise similar to the work at the IETF and
> > other Internet standards bodies."
> >
> > That's good, but why not undertake this within the existing IETF process,
> > rather than trying to emulate it?

> Because it is outside the scope of the IETF.

> Cheers,

> Ed Gerck



From owner-ietf-outbound  Sat Feb 12 16:40:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA26804
	for ietf-outbound.10@ietf.org; Sat, 12 Feb 2000 16:40:03 -0500 (EST)
Received: from po1.bbn.com (PO1.BBN.COM [192.1.50.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26669
	for <IETF@ietf.org>; Sat, 12 Feb 2000 16:33:42 -0500 (EST)
Received: from [128.33.238.119] (TC148.BBN.COM [128.33.238.148])
	by po1.bbn.com (8.9.1/8.9.1) with ESMTP id QAA00694;
	Sat, 12 Feb 2000 16:33:35 -0500 (EST)
Mime-Version: 1.0
X-Sender: kent@po1.bbn.com
Message-Id: <v04220802b4cb7d8ddca7@[128.33.238.119]>
In-Reply-To: <4.2.2.20000211194647.00a3e8a0@lint.cisco.com>
References: <4.2.2.20000211170740.00a38c60@lint.cisco.com>
 <4.2.2.20000211151342.00a36e60@lint.cisco.com>
 <4.2.2.20000211151342.00a36e60@lint.cisco.com>
 <4.2.2.20000211170740.00a38c60@lint.cisco.com>
 <4.2.2.20000211194647.00a3e8a0@lint.cisco.com>
Date: Sat, 12 Feb 2000 16:33:59 -0500
To: Paul Ferguson <ferguson@cisco.com>
From: Stephen Kent <kent@bbn.com>
Subject: Re: Internet SYN Flooding, spoofing attacks
Cc: IETF@ietf.org, dts@senie.com
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

Paul,

>
>>When one suggests that a first tier ISP would not need to filter
>>traffic from down stream providers, because IF they do the filtering,
>>then the problem will not arise via those links, one is suggesting
>>precisely this sort of model.
>
>You're approaching this from the wrong perspective, in my opinion.
>
>There is no assumption implied that RFC2267 filtering is needed --
>it is required. What good is it if one or two or 300 people do
>it, and another 157,000 do not?
>
>Well, there is a little good, but the more people that do it, the
>better off we all are.
>
>The bottom line here is that RFC2267-style filtering (or unicast
>RPF checks, or what have you) stops spoofed source address packets
>from being transmitted into the Internet from places they have no
>business being originated from to begin with.
>
>In even the worst case, those conscientious network admins that
>_do_ do it can say without remorse that they are doing their part,
>and can at least be assured that DoS attacks using spoofed source
>addresses are not being originated from their customer base.
>
>And this is a Bad Thing?

it is a bad thing if one bases defenses on the assumption that ALL 
the access points into the Internet will perform such filtering, and 
will do it consistently.  Even if all ISPs, and down stream providers 
performed the filtering, there is no guarantee that attackers could 
not circumvent the filter controls, either through direct attack on 
the routers, or through indirect attack on the management stations 
used to configure them.  I'm just saying that while edge filtering is 
potentially useful, it would not be a good idea to assume that it 
will be effective.

>
>>Edge filtering would often be helpful, but it is not a panacea, as
>>pointed out by others in regard to the current set of attacks, nor is
>>the performance impact trivial with most current routers.
>
>It is negligible at the edge in most cases, but you really need to
>define "edge" a little better. In some cases, it is very low speed
>links, in others it is an OC-12.

In talking with the operations folks at GTE-I, they expressed concern 
over the performance hit for many of their edge routers, based on the 
number of subscribers involved and other configuration 
characteristics.

>
>>Because
>>most routers are optimized for transit traffic forwarding, the
>>ability to filter on the interface cards is limited, as I'm sure you
>>know.
>
>No, I don't know that at all. _Backbone_routers_ are optimized for
>packet forwarding -- I do know that.

I would state that devices that examine IP headers and make routing 
decisions entirely on interface cards are optimized for traffic 
forwarding, vs. firewall-style devices that focus on header 
examination and ACL checking, and which typically do this by passing 
a packet through a general purpose processor, vs. in I/O interfaces. 
But, these are just generalizations.

>
>>  Also, several of the distributed DoS attacks we are seeing do
>>not use fake source addresses from other sites, so simple filtering
>>of the sort proposed in 2267 would not be effective in these cases.
>
>Again, you're missing the point.
>
>If attackers are limited to launching DoS attacks using traceable
>addresses, then not only can their zombies be traced & found, but
>so can their controller (the perpetrator himself). Of this, make no
>mistake.

Not necessarily. The traffic from a controller to the clients may be 
sufficiently offset in time as to make tracing back to the controller 
hard.  I agree that tracing to the traffic sources (or at least to 
the sites where the traffic sources are) would be easier if edge 
filtering were in place, and if it were not compromised.

>
>>Finally, I am aware of new routers for which this sort of filtering
>>would be child's play, but they are not yet deployed.  One ought not
>>suggest that edge filtering is not being applied simply because of
>>laziness on the part of ISPs.
>
>Steve, you said that -- I didn't. I think ISP's will do what their
>customers pay them to do.

ISPs do what they perceive is appropriate to maintain and gain market 
share, consistent with their cost models and router product 
availability. Different ISPs have different ideas of how to deploy 
routers and switches to aggregate traffic, which are driven by their 
traffic models, by economics, and by vendors.

Note that this is an international problem, not just a domestic one. 
Our operations folks tell me that many attacks are traceable to 
foreign sources, where the ability to ensure adherence to policies 
such as edge filtering is rather difficult.  Also, from a national 
security perspective, one would hardly rely on other countries 
enforcing such policies in their ISP domains.  That's why I think the 
best, long term approach to these problems requires a combination of 
improved host security and monitoring for attacks near the hosts 
(both appropriate measures when the hosts are servers with a vested 
interest in maintaining availability), plus rapid, automated response 
to detected attacks, and an ability to activate and adjust filters at 
all ISP interfaces, not just at subscriber interfaces.  This 
combination of measures does not rely on every ISP in the world doing 
the right thing, although it would benefit from such behavior.  It 
embodies a notion of self-protection, both at the subscriber and ISP 
levels, in support of the principle of least privilege.

Steve



From owner-ietf-outbound@ietf.org  Sat Feb 12 16:42:29 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26863
	for <ietf-web-archive@odin.ietf.org>; Sat, 12 Feb 2000 16:42:29 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA27448;
	Sat, 12 Feb 2000 16:40:30 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id QAA26804
	for ietf-outbound.10@ietf.org; Sat, 12 Feb 2000 16:40:03 -0500 (EST)
Received: from po1.bbn.com (PO1.BBN.COM [192.1.50.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26669
	for <IETF@ietf.org>; Sat, 12 Feb 2000 16:33:42 -0500 (EST)
Received: from [128.33.238.119] (TC148.BBN.COM [128.33.238.148])
	by po1.bbn.com (8.9.1/8.9.1) with ESMTP id QAA00694;
	Sat, 12 Feb 2000 16:33:35 -0500 (EST)
Mime-Version: 1.0
X-Sender: kent@po1.bbn.com
Message-Id: <v04220802b4cb7d8ddca7@[128.33.238.119]>
In-Reply-To: <4.2.2.20000211194647.00a3e8a0@lint.cisco.com>
References: <4.2.2.20000211170740.00a38c60@lint.cisco.com>
 <4.2.2.20000211151342.00a36e60@lint.cisco.com>
 <4.2.2.20000211151342.00a36e60@lint.cisco.com>
 <4.2.2.20000211170740.00a38c60@lint.cisco.com>
 <4.2.2.20000211194647.00a3e8a0@lint.cisco.com>
Date: Sat, 12 Feb 2000 16:33:59 -0500
To: Paul Ferguson <ferguson@cisco.com>
From: Stephen Kent <kent@bbn.com>
Subject: Re: Internet SYN Flooding, spoofing attacks
Cc: IETF@ietf.org, dts@senie.com
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

Paul,

>
>>When one suggests that a first tier ISP would not need to filter
>>traffic from down stream providers, because IF they do the filtering,
>>then the problem will not arise via those links, one is suggesting
>>precisely this sort of model.
>
>You're approaching this from the wrong perspective, in my opinion.
>
>There is no assumption implied that RFC2267 filtering is needed --
>it is required. What good is it if one or two or 300 people do
>it, and another 157,000 do not?
>
>Well, there is a little good, but the more people that do it, the
>better off we all are.
>
>The bottom line here is that RFC2267-style filtering (or unicast
>RPF checks, or what have you) stops spoofed source address packets
>from being transmitted into the Internet from places they have no
>business being originated from to begin with.
>
>In even the worst case, those conscientious network admins that
>_do_ do it can say without remorse that they are doing their part,
>and can at least be assured that DoS attacks using spoofed source
>addresses are not being originated from their customer base.
>
>And this is a Bad Thing?

it is a bad thing if one bases defenses on the assumption that ALL 
the access points into the Internet will perform such filtering, and 
will do it consistently.  Even if all ISPs, and down stream providers 
performed the filtering, there is no guarantee that attackers could 
not circumvent the filter controls, either through direct attack on 
the routers, or through indirect attack on the management stations 
used to configure them.  I'm just saying that while edge filtering is 
potentially useful, it would not be a good idea to assume that it 
will be effective.

>
>>Edge filtering would often be helpful, but it is not a panacea, as
>>pointed out by others in regard to the current set of attacks, nor is
>>the performance impact trivial with most current routers.
>
>It is negligible at the edge in most cases, but you really need to
>define "edge" a little better. In some cases, it is very low speed
>links, in others it is an OC-12.

In talking with the operations folks at GTE-I, they expressed concern 
over the performance hit for many of their edge routers, based on the 
number of subscribers involved and other configuration 
characteristics.

>
>>Because
>>most routers are optimized for transit traffic forwarding, the
>>ability to filter on the interface cards is limited, as I'm sure you
>>know.
>
>No, I don't know that at all. _Backbone_routers_ are optimized for
>packet forwarding -- I do know that.

I would state that devices that examine IP headers and make routing 
decisions entirely on interface cards are optimized for traffic 
forwarding, vs. firewall-style devices that focus on header 
examination and ACL checking, and which typically do this by passing 
a packet through a general purpose processor, vs. in I/O interfaces. 
But, these are just generalizations.

>
>>  Also, several of the distributed DoS attacks we are seeing do
>>not use fake source addresses from other sites, so simple filtering
>>of the sort proposed in 2267 would not be effective in these cases.
>
>Again, you're missing the point.
>
>If attackers are limited to launching DoS attacks using traceable
>addresses, then not only can their zombies be traced & found, but
>so can their controller (the perpetrator himself). Of this, make no
>mistake.

Not necessarily. The traffic from a controller to the clients may be 
sufficiently offset in time as to make tracing back to the controller 
hard.  I agree that tracing to the traffic sources (or at least to 
the sites where the traffic sources are) would be easier if edge 
filtering were in place, and if it were not compromised.

>
>>Finally, I am aware of new routers for which this sort of filtering
>>would be child's play, but they are not yet deployed.  One ought not
>>suggest that edge filtering is not being applied simply because of
>>laziness on the part of ISPs.
>
>Steve, you said that -- I didn't. I think ISP's will do what their
>customers pay them to do.

ISPs do what they perceive is appropriate to maintain and gain market 
share, consistent with their cost models and router product 
availability. Different ISPs have different ideas of how to deploy 
routers and switches to aggregate traffic, which are driven by their 
traffic models, by economics, and by vendors.

Note that this is an international problem, not just a domestic one. 
Our operations folks tell me that many attacks are traceable to 
foreign sources, where the ability to ensure adherence to policies 
such as edge filtering is rather difficult.  Also, from a national 
security perspective, one would hardly rely on other countries 
enforcing such policies in their ISP domains.  That's why I think the 
best, long term approach to these problems requires a combination of 
improved host security and monitoring for attacks near the hosts 
(both appropriate measures when the hosts are servers with a vested 
interest in maintaining availability), plus rapid, automated response 
to detected attacks, and an ability to activate and adjust filters at 
all ISP interfaces, not just at subscriber interfaces.  This 
combination of measures does not rely on every ISP in the world doing 
the right thing, although it would benefit from such behavior.  It 
embodies a notion of self-protection, both at the subscriber and ISP 
levels, in support of the principle of least privilege.

Steve



From owner-ietf-outbound  Sat Feb 12 18:40:35 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA27700
	for ietf-outbound.10@ietf.org; Sat, 12 Feb 2000 18:40:02 -0500 (EST)
Received: from alcove.wittsend.com (IDENT:root@alcove.wittsend.com [130.205.0.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27660
	for <ietf@ietf.org>; Sat, 12 Feb 2000 18:31:08 -0500 (EST)
Received: (from mhw@localhost)
	by alcove.wittsend.com (8.9.3/8.9.3) id SAA13128;
	Sat, 12 Feb 2000 18:30:48 -0500
Date: Sat, 12 Feb 2000 18:30:48 -0500
From: "Michael H. Warfield" <mhw@wittsend.com>
To: Carl Malamud <carl@invisible.net>
Cc: Ed Gerck <egerck@nma.com>, Ross Finlayson <finlayson@live.com>,
        ietf@ietf.org
Subject: Re: Announcement ivta.org
Message-ID: <20000212183048.B7845@alcove.wittsend.com>
References: <38A5C375.780C716F@nma.com> <200002122053.PAA16218@also.media.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.1.2i
In-Reply-To: <200002122053.PAA16218@also.media.org>; from carl@invisible.net on Sat, Feb 12, 2000 at 03:53:41PM -0500
X-Loop: ietf@ietf.org

On Sat, Feb 12, 2000 at 03:53:41PM -0500, Carl Malamud wrote:
> If it is outside the scope of the IETF, why send the announcement
> to the IETF list?  :))

	Common interests?  Notifying those people who think it is with
the scope of the IETF and would bitch that others are doing things behind
their backs?  Defensive action to protect from negative reactions from
IETF stalwarts?

	Announcement was a good move.  Moving the discussion to appropriate
forums would also be a good move.

> Carl

	Mike
-- 
 Michael H. Warfield    |  (770) 985-6132   |  mhw@WittsEnd.com
  (The Mad Wizard)      |  (770) 331-2437   |  http://www.wittsend.com/mhw/
  NIC whois:  MHW9      |  An optimist believes we live in the best of all
 PGP Key: 0xDF1DD471    |  possible worlds.  A pessimist is sure of it!



From owner-ietf-outbound@ietf.org  Sat Feb 12 18:43:09 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27782
	for <ietf-web-archive@odin.ietf.org>; Sat, 12 Feb 2000 18:43:09 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA28809;
	Sat, 12 Feb 2000 18:41:08 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id SAA27700
	for ietf-outbound.10@ietf.org; Sat, 12 Feb 2000 18:40:02 -0500 (EST)
Received: from alcove.wittsend.com (IDENT:root@alcove.wittsend.com [130.205.0.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27660
	for <ietf@ietf.org>; Sat, 12 Feb 2000 18:31:08 -0500 (EST)
Received: (from mhw@localhost)
	by alcove.wittsend.com (8.9.3/8.9.3) id SAA13128;
	Sat, 12 Feb 2000 18:30:48 -0500
Date: Sat, 12 Feb 2000 18:30:48 -0500
From: "Michael H. Warfield" <mhw@wittsend.com>
To: Carl Malamud <carl@invisible.net>
Cc: Ed Gerck <egerck@nma.com>, Ross Finlayson <finlayson@live.com>,
        ietf@ietf.org
Subject: Re: Announcement ivta.org
Message-ID: <20000212183048.B7845@alcove.wittsend.com>
References: <38A5C375.780C716F@nma.com> <200002122053.PAA16218@also.media.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.1.2i
In-Reply-To: <200002122053.PAA16218@also.media.org>; from carl@invisible.net on Sat, Feb 12, 2000 at 03:53:41PM -0500
X-Loop: ietf@ietf.org

On Sat, Feb 12, 2000 at 03:53:41PM -0500, Carl Malamud wrote:
> If it is outside the scope of the IETF, why send the announcement
> to the IETF list?  :))

	Common interests?  Notifying those people who think it is with
the scope of the IETF and would bitch that others are doing things behind
their backs?  Defensive action to protect from negative reactions from
IETF stalwarts?

	Announcement was a good move.  Moving the discussion to appropriate
forums would also be a good move.

> Carl

	Mike
-- 
 Michael H. Warfield    |  (770) 985-6132   |  mhw@WittsEnd.com
  (The Mad Wizard)      |  (770) 331-2437   |  http://www.wittsend.com/mhw/
  NIC whois:  MHW9      |  An optimist believes we live in the best of all
 PGP Key: 0xDF1DD471    |  possible worlds.  A pessimist is sure of it!



From owner-ietf-outbound  Sat Feb 12 19:10:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA28000
	for ietf-outbound.10@ietf.org; Sat, 12 Feb 2000 19:10:04 -0500 (EST)
Received: from dfw-smtpout1.email.verio.net (dfw-smtpout1.email.verio.net [129.250.36.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27938
	for <ietf@ietf.org>; Sat, 12 Feb 2000 19:02:45 -0500 (EST)
Received: from [129.250.38.62] (helo=dfw-mmp2.email.verio.net)
	by dfw-smtpout1.email.verio.net with esmtp (Exim 3.12 #7)
	id 12JmUx-0003FW-00; Sun, 13 Feb 2000 00:02:47 +0000
Received: from [209.21.28.123] (helo=nma.com)
	by dfw-mmp2.email.verio.net with esmtp (Exim 3.12 #7)
	id 12JmXL-00037v-00; Sun, 13 Feb 2000 00:05:15 +0000
Message-ID: <38A5F463.DC1CA67C@nma.com>
Date: Sat, 12 Feb 2000 16:01:39 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony}  (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Carl Malamud <carl@invisible.net>
CC: Ross Finlayson <finlayson@live.com>, ietf@ietf.org
Subject: Re: Announcement ivta.org
References: <200002122053.PAA16218@also.media.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit



Carl Malamud wrote:

> If it is outside the scope of the IETF, why send the announcement
> to the IETF list?  :))

For several good reasons but mainly because the IETF list and WGs have
many individuals  that have already gone through the learning curve needed
for collaborative work in standards work -- for example, that can reply in a
positive and up-beat way to this type of questions ;-)

We need to cope with diversity, and the old hands know this well, by being
liberal in what we accept while being conservative in what we require -- you
may note that my announcement email was short and that was, of course,
by design.

Also, because there are many individuals and companies in the IETF list
that may very well profit from a *specific* application area that can
immediately help them leverage from IETF work and experience -- which they
know much better than outsiders.  For example, by helping the IVTA avoid to
reinvent the wheel (so to say -- who needs yet another file transfer protocol?).

Last, but not all, because the IETF process is exactly the art (science?) of
transferring to the public domain information which is, essentially, private
-- so that everyone can benefit, including vendors and users.  Which
experience is by itself very useful to the young IVTA.  In elections systems,
the experience is the traditional one of closed systems and this needs to
change in order to cope with the much higher stakes and risks of an eventual
Internet election.

Thanks for the opportunity to explain, in the best IETF tradition ;-)  Iwrote
a bit, you ask ... I have then the opportunity and feel the need to explain
more.

Cheers,

Ed Gerck



From owner-ietf-outbound@ietf.org  Sat Feb 12 19:12:46 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28069
	for <ietf-web-archive@odin.ietf.org>; Sat, 12 Feb 2000 19:12:42 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA29588;
	Sat, 12 Feb 2000 19:10:39 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id TAA28000
	for ietf-outbound.10@ietf.org; Sat, 12 Feb 2000 19:10:04 -0500 (EST)
Received: from dfw-smtpout1.email.verio.net (dfw-smtpout1.email.verio.net [129.250.36.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27938
	for <ietf@ietf.org>; Sat, 12 Feb 2000 19:02:45 -0500 (EST)
Received: from [129.250.38.62] (helo=dfw-mmp2.email.verio.net)
	by dfw-smtpout1.email.verio.net with esmtp (Exim 3.12 #7)
	id 12JmUx-0003FW-00; Sun, 13 Feb 2000 00:02:47 +0000
Received: from [209.21.28.123] (helo=nma.com)
	by dfw-mmp2.email.verio.net with esmtp (Exim 3.12 #7)
	id 12JmXL-00037v-00; Sun, 13 Feb 2000 00:05:15 +0000
Message-ID: <38A5F463.DC1CA67C@nma.com>
Date: Sat, 12 Feb 2000 16:01:39 -0800
From: Ed Gerck <egerck@nma.com>
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony}  (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Carl Malamud <carl@invisible.net>
CC: Ross Finlayson <finlayson@live.com>, ietf@ietf.org
Subject: Re: Announcement ivta.org
References: <200002122053.PAA16218@also.media.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit



Carl Malamud wrote:

> If it is outside the scope of the IETF, why send the announcement
> to the IETF list?  :))

For several good reasons but mainly because the IETF list and WGs have
many individuals  that have already gone through the learning curve needed
for collaborative work in standards work -- for example, that can reply in a
positive and up-beat way to this type of questions ;-)

We need to cope with diversity, and the old hands know this well, by being
liberal in what we accept while being conservative in what we require -- you
may note that my announcement email was short and that was, of course,
by design.

Also, because there are many individuals and companies in the IETF list
that may very well profit from a *specific* application area that can
immediately help them leverage from IETF work and experience -- which they
know much better than outsiders.  For example, by helping the IVTA avoid to
reinvent the wheel (so to say -- who needs yet another file transfer protocol?).

Last, but not all, because the IETF process is exactly the art (science?) of
transferring to the public domain information which is, essentially, private
-- so that everyone can benefit, including vendors and users.  Which
experience is by itself very useful to the young IVTA.  In elections systems,
the experience is the traditional one of closed systems and this needs to
change in order to cope with the much higher stakes and risks of an eventual
Internet election.

Thanks for the opportunity to explain, in the best IETF tradition ;-)  Iwrote
a bit, you ask ... I have then the opportunity and feel the need to explain
more.

Cheers,

Ed Gerck



From owner-ietf-outbound  Sat Feb 12 20:20:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA28599
	for ietf-outbound.10@ietf.org; Sat, 12 Feb 2000 20:20:02 -0500 (EST)
Received: from dev01.i-dns.com ([203.116.224.27])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28512
	for <ietf@ietf.org>; Sat, 12 Feb 2000 20:13:46 -0500 (EST)
Received: from pobox.org.sg (ad202.166.28.232.magix.com.sg [202.166.28.232])
	by dev01.i-dns.com (8.9.3/8.9.3) with ESMTP id BAA08049;
	Sun, 13 Feb 2000 01:13:36 GMT
Message-ID: <38A6050E.58C416FD@pobox.org.sg>
Date: Sun, 13 Feb 2000 09:12:46 +0800
From: James Seng <jseng@POBOX.ORG.SG>
X-Mailer: Mozilla 4.7 [en] (Win98; I)
X-Accept-Language: en,zh,zh-TW,zh-CN
MIME-Version: 1.0
To: Ed Gerck <egerck@nma.com>
CC: Ross Finlayson <finlayson@live.com>, ietf@ietf.org
Subject: Re: Announcement ivta.org
References: <3.0.6.32.20000212122505.008fbc20@shell7.ba.best.com> <38A5C375.780C716F@nma.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Ed Gerck wrote:
> Because it is outside the scope of the IETF.

Why is it outside the scope of IETF? 

-James Seng



From owner-ietf-outbound@ietf.org  Sat Feb 12 20:22:32 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28676
	for <ietf-web-archive@odin.ietf.org>; Sat, 12 Feb 2000 20:22:32 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA02342;
	Sat, 12 Feb 2000 20:20:31 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id UAA28599
	for ietf-outbound.10@ietf.org; Sat, 12 Feb 2000 20:20:02 -0500 (EST)
Received: from dev01.i-dns.com ([203.116.224.27])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28512
	for <ietf@ietf.org>; Sat, 12 Feb 2000 20:13:46 -0500 (EST)
Received: from pobox.org.sg (ad202.166.28.232.magix.com.sg [202.166.28.232])
	by dev01.i-dns.com (8.9.3/8.9.3) with ESMTP id BAA08049;
	Sun, 13 Feb 2000 01:13:36 GMT
Message-ID: <38A6050E.58C416FD@pobox.org.sg>
Date: Sun, 13 Feb 2000 09:12:46 +0800
From: James Seng <jseng@POBOX.ORG.SG>
X-Mailer: Mozilla 4.7 [en] (Win98; I)
X-Accept-Language: en,zh,zh-TW,zh-CN
MIME-Version: 1.0
To: Ed Gerck <egerck@nma.com>
CC: Ross Finlayson <finlayson@live.com>, ietf@ietf.org
Subject: Re: Announcement ivta.org
References: <3.0.6.32.20000212122505.008fbc20@shell7.ba.best.com> <38A5C375.780C716F@nma.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Ed Gerck wrote:
> Because it is outside the scope of the IETF.

Why is it outside the scope of IETF? 

-James Seng



From owner-ietf-outbound  Sun Feb 13 05:43:36 2000
Received: by ietf.org (8.9.1a/8.9.1a) id FAA07179
	for ietf-outbound.10@ietf.org; Sun, 13 Feb 2000 05:40:02 -0500 (EST)
Received: from server.jad.net ([202.134.2.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA07152
	for <ietf@ietf.org>; Sun, 13 Feb 2000 05:31:52 -0500 (EST)
Received: from oke.com (cf-isrlab7.comp.nus.edu.sg [137.132.85.181])
	by server.jad.net (8.9.2/8.9.2) with ESMTP id SAA22537;
	Sun, 13 Feb 2000 18:32:54 +0700 (JAVT)
	(envelope-from rms46@oke.com)
Sender: ibrahim@server.jad.net
Message-ID: <38A687F1.7CD08223@oke.com>
Date: Sun, 13 Feb 2000 18:31:13 +0800
From: "Rahmat M. Samik-Ibrahim" <rms46@oke.com>
Reply-To: rms46.oke.com@vlsm.org
Organization: VLSM-TJT
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5-22 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: 1601bis: The Charter of IAB
References: <1146637804.950334410@p2.jck.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

John C Klensin wrote:

> My, my, do I love being quoted out of context on a comment that
> was made four years ago, and was intended as humorous rather
> than a serious comment on the process.

Sorry, I was not aware that an email to an IETF WG list with 
a subject "The appeals process and the IAB" and starts with 
"... have discussed with a few people..."  was intended as 
humorous.

Anyway, let's agree to disagree:

1. I am strongly opposing the current 1601bis, but who cares
   anyway? There is no way to make an appeal, and therefore,
   I believe it is a WIN-WIN situation: most likely that charter 
   will be approved, and I will save ISOC membership fee.

2. I have no problem with the informality at the WG and IESG 
   level, including sending humorous emails to a list :^).
   However, I believe that the IAB serves as a shim between
   that informality and its formal umbrella organization (ISOC).

3. I believe that the IESG is doing fine at its level except 
   it should stop signing treaties and MoUs with other organizations.
   But, I do not believe that the IESG needs a super-IESG
   (i.e. the current IAB) for technical oversight purpose.
   Even if the IESG needs one, an expert advisory panel
   could sever that purpose.

4. I believe that the IAB should deal with things that the IESG 
   is not interested anyway, including to deal with the formality 
   of the *REAL* community.

5. Case closed.

regrets,

-- 
- Rahmat M. Samik-Ibrahim --  VLSM-TJT --  http://rms46.vlsm.org/ -
- Always select ShutDown from the StartMenu - M$Windows after crash



From owner-ietf-outbound@ietf.org  Sun Feb 13 05:46:31 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA07245
	for <ietf-web-archive@odin.ietf.org>; Sun, 13 Feb 2000 05:46:31 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA15301;
	Sun, 13 Feb 2000 05:44:24 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id FAA07179
	for ietf-outbound.10@ietf.org; Sun, 13 Feb 2000 05:40:02 -0500 (EST)
Received: from server.jad.net ([202.134.2.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA07152
	for <ietf@ietf.org>; Sun, 13 Feb 2000 05:31:52 -0500 (EST)
Received: from oke.com (cf-isrlab7.comp.nus.edu.sg [137.132.85.181])
	by server.jad.net (8.9.2/8.9.2) with ESMTP id SAA22537;
	Sun, 13 Feb 2000 18:32:54 +0700 (JAVT)
	(envelope-from rms46@oke.com)
Sender: ibrahim@server.jad.net
Message-ID: <38A687F1.7CD08223@oke.com>
Date: Sun, 13 Feb 2000 18:31:13 +0800
From: "Rahmat M. Samik-Ibrahim" <rms46@oke.com>
Reply-To: rms46.oke.com@vlsm.org
Organization: VLSM-TJT
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5-22 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: 1601bis: The Charter of IAB
References: <1146637804.950334410@p2.jck.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

John C Klensin wrote:

> My, my, do I love being quoted out of context on a comment that
> was made four years ago, and was intended as humorous rather
> than a serious comment on the process.

Sorry, I was not aware that an email to an IETF WG list with 
a subject "The appeals process and the IAB" and starts with 
"... have discussed with a few people..."  was intended as 
humorous.

Anyway, let's agree to disagree:

1. I am strongly opposing the current 1601bis, but who cares
   anyway? There is no way to make an appeal, and therefore,
   I believe it is a WIN-WIN situation: most likely that charter 
   will be approved, and I will save ISOC membership fee.

2. I have no problem with the informality at the WG and IESG 
   level, including sending humorous emails to a list :^).
   However, I believe that the IAB serves as a shim between
   that informality and its formal umbrella organization (ISOC).

3. I believe that the IESG is doing fine at its level except 
   it should stop signing treaties and MoUs with other organizations.
   But, I do not believe that the IESG needs a super-IESG
   (i.e. the current IAB) for technical oversight purpose.
   Even if the IESG needs one, an expert advisory panel
   could sever that purpose.

4. I believe that the IAB should deal with things that the IESG 
   is not interested anyway, including to deal with the formality 
   of the *REAL* community.

5. Case closed.

regrets,

-- 
- Rahmat M. Samik-Ibrahim --  VLSM-TJT --  http://rms46.vlsm.org/ -
- Always select ShutDown from the StartMenu - M$Windows after crash



From owner-ietf-outbound  Sun Feb 13 19:20:42 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA14610
	for ietf-outbound.10@ietf.org; Sun, 13 Feb 2000 19:20:02 -0500 (EST)
Received: from snark.piermont.com (snark.piermont.com [206.1.51.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14568
	for <IETF@ietf.org>; Sun, 13 Feb 2000 19:14:41 -0500 (EST)
Received: by snark.piermont.com (Postfix, from userid 1000)
	id 6668E1E00E3; Sun, 13 Feb 2000 19:14:42 -0500 (EST)
To: Valdis.Kletnieks@vt.edu
Cc: IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
References: <009E5826.5FC1D447.198@process.com> <200002112033.e1BKXC917344@black-ice.cc.vt.edu>
From: "Perry E. Metzger" <perry@piermont.com>
Date: 13 Feb 2000 19:14:42 -0500
In-Reply-To: Valdis.Kletnieks@vt.edu's message of "Fri, 11 Feb 2000 15:33:12 -0500"
Message-ID: <87g0uwljwt.fsf@snark.piermont.com>
Lines: 17
X-Mailer: Gnus v5.5/Emacs 20.3
X-Loop: ietf@ietf.org


Valdis.Kletnieks@vt.edu writes:
> Given that RFC2267 is over 2 years old now, what *do* you suggest the network
> community at large do to motivate the sites that still haven't
> implemented it?

I think a simple motivation is appearing on the horizon. Lawyers are
revving up their word processors as we speak. I mean, here are all
these nice, deep-pocketed public companies that aren't taking an
action they fully know could reduce risk for third parties, and even
saying in public how it costs too much. Can you say "negligence suit
nirvana"? I knew you could.

As much as I hate the lawsharks, every once in a while they do some
good in motivating change.

Perry



From owner-ietf-outbound@ietf.org  Sun Feb 13 19:25:21 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14667
	for <ietf-web-archive@odin.ietf.org>; Sun, 13 Feb 2000 19:25:21 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA24480;
	Sun, 13 Feb 2000 19:23:23 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id TAA14610
	for ietf-outbound.10@ietf.org; Sun, 13 Feb 2000 19:20:02 -0500 (EST)
Received: from snark.piermont.com (snark.piermont.com [206.1.51.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14568
	for <IETF@ietf.org>; Sun, 13 Feb 2000 19:14:41 -0500 (EST)
Received: by snark.piermont.com (Postfix, from userid 1000)
	id 6668E1E00E3; Sun, 13 Feb 2000 19:14:42 -0500 (EST)
To: Valdis.Kletnieks@vt.edu
Cc: IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
References: <009E5826.5FC1D447.198@process.com> <200002112033.e1BKXC917344@black-ice.cc.vt.edu>
From: "Perry E. Metzger" <perry@piermont.com>
Date: 13 Feb 2000 19:14:42 -0500
In-Reply-To: Valdis.Kletnieks@vt.edu's message of "Fri, 11 Feb 2000 15:33:12 -0500"
Message-ID: <87g0uwljwt.fsf@snark.piermont.com>
Lines: 17
X-Mailer: Gnus v5.5/Emacs 20.3
X-Loop: ietf@ietf.org


Valdis.Kletnieks@vt.edu writes:
> Given that RFC2267 is over 2 years old now, what *do* you suggest the network
> community at large do to motivate the sites that still haven't
> implemented it?

I think a simple motivation is appearing on the horizon. Lawyers are
revving up their word processors as we speak. I mean, here are all
these nice, deep-pocketed public companies that aren't taking an
action they fully know could reduce risk for third parties, and even
saying in public how it costs too much. Can you say "negligence suit
nirvana"? I knew you could.

As much as I hate the lawsharks, every once in a while they do some
good in motivating change.

Perry



From owner-ietf-outbound  Sun Feb 13 21:40:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA15471
	for ietf-outbound.10@ietf.org; Sun, 13 Feb 2000 21:40:02 -0500 (EST)
Received: from dodo.prod.itd.earthlink.net (dodo.prod.itd.earthlink.net [207.217.120.99])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15413
	for <ietf@ietf.org>; Sun, 13 Feb 2000 21:31:20 -0500 (EST)
Received: from directavision.com (dialup-209.245.66.166.LosAngeles1.Level3.net [209.245.66.166])
	by dodo.prod.itd.earthlink.net (8.9.3/8.9.3) with ESMTP id SAA12655
	for <ietf@ietf.org>; Sun, 13 Feb 2000 18:30:39 -0800 (PST)
Message-ID: <38A76606.B1AA99F4@directavision.com>
Date: Sun, 13 Feb 2000 18:18:46 -0800
From: "FreeDBS@directavision.com from Dan Melendez" <email@directavision.com>
Organization: DIRECT-A-VISION, IND.
X-Mailer: Mozilla 4.04 [en] (Win95; I)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: New member seeks direction
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Hello,
I am interested in the following topics:

1) Internet television(all related tech info)
2) High speed Internet fundamentals
3) 801.11 DS cards (11mbps)

If you can refer me to some web files, I would greatly appreciate it.
Thank you for your time and make it a great day.
dan




From owner-ietf-outbound@ietf.org  Sun Feb 13 21:42:45 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15529
	for <ietf-web-archive@odin.ietf.org>; Sun, 13 Feb 2000 21:42:45 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA28363;
	Sun, 13 Feb 2000 21:40:42 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id VAA15471
	for ietf-outbound.10@ietf.org; Sun, 13 Feb 2000 21:40:02 -0500 (EST)
Received: from dodo.prod.itd.earthlink.net (dodo.prod.itd.earthlink.net [207.217.120.99])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15413
	for <ietf@ietf.org>; Sun, 13 Feb 2000 21:31:20 -0500 (EST)
Received: from directavision.com (dialup-209.245.66.166.LosAngeles1.Level3.net [209.245.66.166])
	by dodo.prod.itd.earthlink.net (8.9.3/8.9.3) with ESMTP id SAA12655
	for <ietf@ietf.org>; Sun, 13 Feb 2000 18:30:39 -0800 (PST)
Message-ID: <38A76606.B1AA99F4@directavision.com>
Date: Sun, 13 Feb 2000 18:18:46 -0800
From: "FreeDBS@directavision.com from Dan Melendez" <email@directavision.com>
Organization: DIRECT-A-VISION, IND.
X-Mailer: Mozilla 4.04 [en] (Win95; I)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: New member seeks direction
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hello,
I am interested in the following topics:

1) Internet television(all related tech info)
2) High speed Internet fundamentals
3) 801.11 DS cards (11mbps)

If you can refer me to some web files, I would greatly appreciate it.
Thank you for your time and make it a great day.
dan




From owner-ietf-outbound  Mon Feb 14 00:40:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA18899
	for ietf-outbound.10@ietf.org; Mon, 14 Feb 2000 00:40:02 -0500 (EST)
Received: from torque.pothole.com ([209.94.126.195])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA18839
	for <IETF@ietf.org>; Mon, 14 Feb 2000 00:37:07 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by torque.pothole.com (8.8.2/8.8.8) with SMTP id AAA15795
	for IETF@ietf.org; Mon, 14 Feb 2000 00:37:29 -0500 (EST)
Message-Id: <200002140537.AAA15795@torque.pothole.com>
X-Authentication-Warning: torque.pothole.com: localhost [127.0.0.1] didn't use HELO protocol
To: IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks 
In-reply-to: Your message of "Fri, 11 Feb 2000 16:35:18 EST."
             <4.2.2.20000211163325.00a50470@lint.cisco.com> 
Date: Mon, 14 Feb 2000 00:37:29 -0500
From: "Donald E. Eastlake 3rd" <dee3@torque.pothole.com>
X-Mts: smtp
X-Loop: ietf@ietf.org


I think that making egress filtering a BCP, applying community
pressure, bringing law suites, etc., will be about as effective
at eliminating forged source address packets on the Internet as
similar measures have been in eliminating open SMTP relays...

They help, but not much.

Donald

From:  Paul Ferguson <ferguson@cisco.com>
Message-Id:  <4.2.2.20000211163325.00a50470@lint.cisco.com>
Date:  Fri, 11 Feb 2000 16:35:18 -0500
To:  Valdis.Kletnieks@vt.edu
Cc:  IETF@ietf.org
In-Reply-To:  <200002112033.e1BKXC917344@black-ice.cc.vt.edu>
References:  <Your message of "Fri, 11 Feb 2000 14:40:15 EST." <009E5826.5FC1D447.198
@process.com>
	     <009E5826.5FC1D447.198@process.com>

>At 03:33 PM 02/11/2000 -0500, Valdis.Kletnieks@vt.edu wrote:
>
>>Given that RFC2267 is over 2 years old now, what *do* you suggest the network
>>community at large do to motivate the sites that still haven't implemented it?
>
>Do you think that if RFC2267 was advanced as a BCP that
>it would carry more weight, and therefore more ISP's would
>implement RFC2267-style filtering? Coupled with the latest
>denial of service attacks?
>
>- paul
>



From owner-ietf-outbound@ietf.org  Mon Feb 14 00:42:44 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA18960
	for <ietf-web-archive@odin.ietf.org>; Mon, 14 Feb 2000 00:42:44 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA02146;
	Mon, 14 Feb 2000 00:40:42 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id AAA18899
	for ietf-outbound.10@ietf.org; Mon, 14 Feb 2000 00:40:02 -0500 (EST)
Received: from torque.pothole.com ([209.94.126.195])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA18839
	for <IETF@ietf.org>; Mon, 14 Feb 2000 00:37:07 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by torque.pothole.com (8.8.2/8.8.8) with SMTP id AAA15795
	for IETF@ietf.org; Mon, 14 Feb 2000 00:37:29 -0500 (EST)
Message-Id: <200002140537.AAA15795@torque.pothole.com>
X-Authentication-Warning: torque.pothole.com: localhost [127.0.0.1] didn't use HELO protocol
To: IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks 
In-reply-to: Your message of "Fri, 11 Feb 2000 16:35:18 EST."
             <4.2.2.20000211163325.00a50470@lint.cisco.com> 
Date: Mon, 14 Feb 2000 00:37:29 -0500
From: "Donald E. Eastlake 3rd" <dee3@torque.pothole.com>
X-Mts: smtp
X-Loop: ietf@ietf.org


I think that making egress filtering a BCP, applying community
pressure, bringing law suites, etc., will be about as effective
at eliminating forged source address packets on the Internet as
similar measures have been in eliminating open SMTP relays...

They help, but not much.

Donald

From:  Paul Ferguson <ferguson@cisco.com>
Message-Id:  <4.2.2.20000211163325.00a50470@lint.cisco.com>
Date:  Fri, 11 Feb 2000 16:35:18 -0500
To:  Valdis.Kletnieks@vt.edu
Cc:  IETF@ietf.org
In-Reply-To:  <200002112033.e1BKXC917344@black-ice.cc.vt.edu>
References:  <Your message of "Fri, 11 Feb 2000 14:40:15 EST." <009E5826.5FC1D447.198
@process.com>
	     <009E5826.5FC1D447.198@process.com>

>At 03:33 PM 02/11/2000 -0500, Valdis.Kletnieks@vt.edu wrote:
>
>>Given that RFC2267 is over 2 years old now, what *do* you suggest the network
>>community at large do to motivate the sites that still haven't implemented it?
>
>Do you think that if RFC2267 was advanced as a BCP that
>it would carry more weight, and therefore more ISP's would
>implement RFC2267-style filtering? Coupled with the latest
>denial of service attacks?
>
>- paul
>



From owner-ietf-outbound  Mon Feb 14 05:52:48 2000
Received: by ietf.org (8.9.1a/8.9.1a) id FAA02800
	for ietf-outbound.10@ietf.org; Mon, 14 Feb 2000 05:50:01 -0500 (EST)
Received: from ns.pentamedia.com ([203.231.117.65])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02777
	for <ietf@ietf.org>; Mon, 14 Feb 2000 05:46:41 -0500 (EST)
Received: from mike ([203.231.117.76])
	by ns.pentamedia.com (8.9.3/8.9.3) with SMTP id SAA08467;
	Mon, 14 Feb 2000 18:26:58 +0900
Message-ID: <01fe01bf76d9$af500120$4c75e7cb@pentamedia.com>
From: "Mike Kim" <mike@pentamedia.com>
To: <FreeDBS@directavision.com>
Cc: <ietf@ietf.org>, <email@directavision.com>
Subject: Fw: New member seeks direction
Date: Mon, 14 Feb 2000 19:53:10 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by ietf.org id FAA02777
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

 
> -----Original Message-----
> From: FreeDBS@directavision.com from Dan Melendez [mailto:email@directavision.com]
> Sent: Monday, February 14, 2000 11:19 AM
> To: ietf@ietf.org
> Subject: New member seeks direction
> 
> 
> Hello,
> I am interested in the following topics:
> 
> 1) Internet television(all related tech info)
> 2) High speed Internet fundamentals
> 3) 801.11 DS cards (11mbps)
> 
> If you can refer me to some web files, I would greatly appreciate it.
> Thank you for your time and make it a great day.
> dan
> 
> 
> 


Dear Dan

Subject : ( PayTVs +  FreeTVs + Internet ) 
                Satellite Receiver PC Card 


We would like to introduce PC cards for satellite Internet/TV on PC, as an official PC-Card supplier of EuropeOnline etc.   For its specifications and company introduction, pls surf WWW.pentamedia.com


        FOB Korea Prices of PC cards


satellite Internet + FTA TV + PayTV (Pent@VISION-CI)
- sample(1~5) price : U$ 300 / unit
- over 1,000 pcs : U$ 270 / unit

satellite Internet + FreeToAir TV (Pent@VISION)
- sample(1~5) price : U$ 250 / unit
- over 1,000 pcs : U$ 230 / unit

satellite Internet (Pent@NET)
- sample(1~5) price : U$ 160 / unit
- over 1,000 pcs : U$ 130 / unit
 
satellite Internet (Pent@U : USB type)
- sample(1~5) price : U$ 270 / unit
- over 1,000 pcs : U$ 200 / unit


We also do satellite internet fundamentals including IP gateway to RSMS, RF etc.   Please let me know your requirements.


====================================
Mike KIM  /   PentaMedia Co., Ltd.
                 DEVELOPER & MANUFACTURER of
                 Satellite Internet / TV Receiver PC card

Email : mike@PentaMedia.com
Tel +82.2.3463.3164   Mobile +82.19.320.0106   Fax +82.2.3461.9486











From owner-ietf-outbound@ietf.org  Mon Feb 14 05:55:52 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02860
	for <ietf-web-archive@odin.ietf.org>; Mon, 14 Feb 2000 05:55:52 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA15848;
	Mon, 14 Feb 2000 05:53:51 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id FAA02800
	for ietf-outbound.10@ietf.org; Mon, 14 Feb 2000 05:50:01 -0500 (EST)
Received: from ns.pentamedia.com ([203.231.117.65])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02777
	for <ietf@ietf.org>; Mon, 14 Feb 2000 05:46:41 -0500 (EST)
Received: from mike ([203.231.117.76])
	by ns.pentamedia.com (8.9.3/8.9.3) with SMTP id SAA08467;
	Mon, 14 Feb 2000 18:26:58 +0900
Message-ID: <01fe01bf76d9$af500120$4c75e7cb@pentamedia.com>
From: "Mike Kim" <mike@pentamedia.com>
To: <FreeDBS@directavision.com>
Cc: <ietf@ietf.org>, <email@directavision.com>
Subject: Fw: New member seeks direction
Date: Mon, 14 Feb 2000 19:53:10 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by ietf.org id FAA02777
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

 
> -----Original Message-----
> From: FreeDBS@directavision.com from Dan Melendez [mailto:email@directavision.com]
> Sent: Monday, February 14, 2000 11:19 AM
> To: ietf@ietf.org
> Subject: New member seeks direction
> 
> 
> Hello,
> I am interested in the following topics:
> 
> 1) Internet television(all related tech info)
> 2) High speed Internet fundamentals
> 3) 801.11 DS cards (11mbps)
> 
> If you can refer me to some web files, I would greatly appreciate it.
> Thank you for your time and make it a great day.
> dan
> 
> 
> 


Dear Dan

Subject : ( PayTVs +  FreeTVs + Internet ) 
                Satellite Receiver PC Card 


We would like to introduce PC cards for satellite Internet/TV on PC, as an official PC-Card supplier of EuropeOnline etc.   For its specifications and company introduction, pls surf WWW.pentamedia.com


        FOB Korea Prices of PC cards


satellite Internet + FTA TV + PayTV (Pent@VISION-CI)
- sample(1~5) price : U$ 300 / unit
- over 1,000 pcs : U$ 270 / unit

satellite Internet + FreeToAir TV (Pent@VISION)
- sample(1~5) price : U$ 250 / unit
- over 1,000 pcs : U$ 230 / unit

satellite Internet (Pent@NET)
- sample(1~5) price : U$ 160 / unit
- over 1,000 pcs : U$ 130 / unit
 
satellite Internet (Pent@U : USB type)
- sample(1~5) price : U$ 270 / unit
- over 1,000 pcs : U$ 200 / unit


We also do satellite internet fundamentals including IP gateway to RSMS, RF etc.   Please let me know your requirements.


====================================
Mike KIM  /   PentaMedia Co., Ltd.
                 DEVELOPER & MANUFACTURER of
                 Satellite Internet / TV Receiver PC card

Email : mike@PentaMedia.com
Tel +82.2.3463.3164   Mobile +82.19.320.0106   Fax +82.2.3461.9486











From owner-ietf-outbound  Mon Feb 14 06:10:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA03019
	for ietf-outbound.10@ietf.org; Mon, 14 Feb 2000 06:10:02 -0500 (EST)
Received: from munnari.OZ.AU (munnari.OZ.AU [128.250.1.21])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA02990
	for <IETF@ietf.org>; Mon, 14 Feb 2000 06:05:45 -0500 (EST)
Received: from mundamutti.cs.mu.OZ.AU ([128.250.1.5])
	by munnari.OZ.AU with SMTP (5.83--+1.3.1+0.59) id LA14461;
	Mon, 14 Feb 2000 22:05:12 +1100 (from kre@munnari.OZ.AU)
From: Robert Elz <kre@munnari.OZ.AU>
To: "Donald E. Eastlake 3rd" <dee3@torque.pothole.com>
Cc: IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks 
In-Reply-To: Your message of "Mon, 14 Feb 2000 00:37:29 CDT."
             <200002140537.AAA15795@torque.pothole.com> 
Date: Mon, 14 Feb 2000 22:05:07 +1100
Message-Id: <15516.950526307@munnari.OZ.AU>
Sender: kre@munnari.OZ.AU
X-Loop: ietf@ietf.org

    Date:        Mon, 14 Feb 2000 00:37:29 -0500
    From:        "Donald E. Eastlake 3rd" <dee3@torque.pothole.com>
    Message-ID:  <200002140537.AAA15795@torque.pothole.com>

  | I think that making egress filtering a BCP, applying community
  | pressure, bringing law suites, etc., will be about as effective
  | at eliminating forged source address packets on the Internet as
  | similar measures have been in eliminating open SMTP relays...
  | 
  | They help, but not much.

I'm not sure there is a good analogy there.    There's no good purpose
in sending packets with incorrect source addresses I can think of, and
stopping the practice is the basic intent of the filters.  The only
justification for not doing it is cost - and then just just becomes a
part of the cost benefit analysis - will it cost us more or less to
implement this?

On the other hand, SMTP relays are not a problem anyone cares about of
themselves - just the contrary in fact, smtp relaying can be a very useful
function to have available (eg: you're travelling with your laptop
and have a bunch of mail waiting to go - you get a connection for a
few minutes between flights, but your normal home relay is unreachable
right now - being able to pick some other friendly relay and simply park
your mail on it can be a real advantage).   The thing to be fixed there
is the unwanted spam that is also using the services of the relay, that
is, it isn't the relay that is really the issue, it is the spam, if all
the spam went away, so-one would care about relays any more (other than now
to regret that whereas previously most sites would be happy to relay mail
now far fewer are).

Further, it isn't at all clear that preventing relaying will do much,
if anything, to stop spam - certainly blocking receiving mail from relays
will currently cut the amount of spam you receive a lot - but that's
because comparatively few people do that, and so the spammers are content
to ignore them and just continue making use of the relay services that
they can latch onto.   But should everyone stop relaying, does anyone really
believe that all the spammers are simply going to decide that there is
no point continuing, and all just go away?   Really?   Even if it means
that the spammers have to send all their mail directly, they'll do it
as long as the benefit from sending spam (at least appears to) outweigh
the costs.

So, the two issues are really not much alike - in one there's no good
purpose to be served by not blocking outgoing packets with bogus source
addresses, in the other there are lots of philosphical reasons for
not stopping relaying - hence there are some of us quite willing to do one
but not the other.

Spam is a social problem, and needs to be solved by social/legal means,
not technical ones (there is no technical difference between spam and
any other mailing list mail - it all looks the same - the only difference
is whether the recipient wanted to receive it or not.)  But we're
technocraats, all our tools are technical ones, so it is easy to see
how we grasp at any technical solution we think might help - the only
technical solution we've been able to find that seems like it might help
(a passing illusion really).  Unfortunately, the appearance of a technical
solution reduces the pressure on the social/legal types to come up with
a solution that really works - if we all would just admit that technically
there's nothing that can really be done ablut spam, and simply stopped
trying at all (allow it all through) the user pressure to get this
problem solved some other way would be much much greater...   On the other
hand, sending packets with an incorrect source address is a technical
problem - those packets don't meet the IP specs - what is supposed to be
in that field is the IP address of the sending node.   This is a problem
entirely open to a technical solution.

kre



From owner-ietf-outbound@ietf.org  Mon Feb 14 06:12:44 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03099
	for <ietf-web-archive@odin.ietf.org>; Mon, 14 Feb 2000 06:12:44 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA16160;
	Mon, 14 Feb 2000 06:10:43 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id GAA03019
	for ietf-outbound.10@ietf.org; Mon, 14 Feb 2000 06:10:02 -0500 (EST)
Received: from munnari.OZ.AU (munnari.OZ.AU [128.250.1.21])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA02990
	for <IETF@ietf.org>; Mon, 14 Feb 2000 06:05:45 -0500 (EST)
Received: from mundamutti.cs.mu.OZ.AU ([128.250.1.5])
	by munnari.OZ.AU with SMTP (5.83--+1.3.1+0.59) id LA14461;
	Mon, 14 Feb 2000 22:05:12 +1100 (from kre@munnari.OZ.AU)
From: Robert Elz <kre@munnari.OZ.AU>
To: "Donald E. Eastlake 3rd" <dee3@torque.pothole.com>
Cc: IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks 
In-Reply-To: Your message of "Mon, 14 Feb 2000 00:37:29 CDT."
             <200002140537.AAA15795@torque.pothole.com> 
Date: Mon, 14 Feb 2000 22:05:07 +1100
Message-Id: <15516.950526307@munnari.OZ.AU>
Sender: kre@munnari.OZ.AU
X-Loop: ietf@ietf.org

    Date:        Mon, 14 Feb 2000 00:37:29 -0500
    From:        "Donald E. Eastlake 3rd" <dee3@torque.pothole.com>
    Message-ID:  <200002140537.AAA15795@torque.pothole.com>

  | I think that making egress filtering a BCP, applying community
  | pressure, bringing law suites, etc., will be about as effective
  | at eliminating forged source address packets on the Internet as
  | similar measures have been in eliminating open SMTP relays...
  | 
  | They help, but not much.

I'm not sure there is a good analogy there.    There's no good purpose
in sending packets with incorrect source addresses I can think of, and
stopping the practice is the basic intent of the filters.  The only
justification for not doing it is cost - and then just just becomes a
part of the cost benefit analysis - will it cost us more or less to
implement this?

On the other hand, SMTP relays are not a problem anyone cares about of
themselves - just the contrary in fact, smtp relaying can be a very useful
function to have available (eg: you're travelling with your laptop
and have a bunch of mail waiting to go - you get a connection for a
few minutes between flights, but your normal home relay is unreachable
right now - being able to pick some other friendly relay and simply park
your mail on it can be a real advantage).   The thing to be fixed there
is the unwanted spam that is also using the services of the relay, that
is, it isn't the relay that is really the issue, it is the spam, if all
the spam went away, so-one would care about relays any more (other than now
to regret that whereas previously most sites would be happy to relay mail
now far fewer are).

Further, it isn't at all clear that preventing relaying will do much,
if anything, to stop spam - certainly blocking receiving mail from relays
will currently cut the amount of spam you receive a lot - but that's
because comparatively few people do that, and so the spammers are content
to ignore them and just continue making use of the relay services that
they can latch onto.   But should everyone stop relaying, does anyone really
believe that all the spammers are simply going to decide that there is
no point continuing, and all just go away?   Really?   Even if it means
that the spammers have to send all their mail directly, they'll do it
as long as the benefit from sending spam (at least appears to) outweigh
the costs.

So, the two issues are really not much alike - in one there's no good
purpose to be served by not blocking outgoing packets with bogus source
addresses, in the other there are lots of philosphical reasons for
not stopping relaying - hence there are some of us quite willing to do one
but not the other.

Spam is a social problem, and needs to be solved by social/legal means,
not technical ones (there is no technical difference between spam and
any other mailing list mail - it all looks the same - the only difference
is whether the recipient wanted to receive it or not.)  But we're
technocraats, all our tools are technical ones, so it is easy to see
how we grasp at any technical solution we think might help - the only
technical solution we've been able to find that seems like it might help
(a passing illusion really).  Unfortunately, the appearance of a technical
solution reduces the pressure on the social/legal types to come up with
a solution that really works - if we all would just admit that technically
there's nothing that can really be done ablut spam, and simply stopped
trying at all (allow it all through) the user pressure to get this
problem solved some other way would be much much greater...   On the other
hand, sending packets with an incorrect source address is a technical
problem - those packets don't meet the IP specs - what is supposed to be
in that field is the IP address of the sending node.   This is a problem
entirely open to a technical solution.

kre



From owner-ietf-outbound  Mon Feb 14 16:30:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA24267
	for ietf-outbound.10@ietf.org; Mon, 14 Feb 2000 16:30:02 -0500 (EST)
Received: from prue.eim.surrey.ac.uk (IDENT:exim@prue.eim.surrey.ac.uk [131.227.76.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24201
	for <ietf@ietf.org>; Mon, 14 Feb 2000 16:25:59 -0500 (EST)
Received: from petra.ee.surrey.ac.uk ([131.227.88.13] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.03 #1)
	id 12KT0J-0005lw-00
	for ietf@ietf.org; Mon, 14 Feb 2000 21:25:59 +0000
Date: Mon, 14 Feb 2000 21:25:56 +0000 (GMT)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-Sender: eep1lw@petra.ee.surrey.ac.uk
Reply-To: L.Wood@eim.surrey.ac.uk
To: ietf@ietf.org
Subject: Proposal: reclassify RFC2549, 1149 as historical
Message-ID: <Pine.SOL.4.10.10002142113530.5614-100000@petra.ee.surrey.ac.uk>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

I move we reclassify RFC2549 and RFC1149 as historical.

Evidence to support this: 'end of an era' according to
http://www.telegraph.co.uk/et?ac=000111464113065&pg=/et/00/2/14/wpig14.html
below.

In particular, I don't think the QoS additions have ever been fully
field tested; the WFQ proposal leads to observable instances of
dropped tails during measurement.

L.

don't you just hate thinking about sending yourself valentines?

<L.Wood@surrey.ac.uk>PGP<http://www.ee.surrey.ac.uk/Personal/L.Wood/>


ELECTRONIC TELEGRAPH, ISSUE 1725

Monday 14 February 2000

Spread of radio switches off political pigeon post
By Jon Stock in New Delhi

MORE than 600 Indian police carrier pigeons face early retirement
after officials decided to replace them with radios.
                                       
The decision to ground the birds before Wednesday's state assembly
elections in Orissa, eastern India, marks the end of an era. They
previously played a unique role in India's electoral process.
                                       
They last saw active duty during last year's general election, when
they carried messages to and from far-flung polling booths in the
remote Orissa districts of Koraput and Dhenkanal. The messages
detailed the law and order situation during polling. The pigeons are
kept in 28 lofts throughout the state and will now become showpieces
used solely for ceremonial purposes, according to Baikunthanath Das,
Superintendent of Police (Signals), who looks after them.

Their demise has been caused by what he called the advent of new
technology. He said: "Even the most remote interior areas now have VHF
radios."

The service was the only one of its kind in India. It was started in
1946 during British rule by the state police's Signal Establishment,
which bought more than 1,000 pigeons from the Indian Army after the
Second World War.



From owner-ietf-outbound@ietf.org  Mon Feb 14 16:35:22 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24439
	for <ietf-web-archive@odin.ietf.org>; Mon, 14 Feb 2000 16:35:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA01672;
	Mon, 14 Feb 2000 16:33:20 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id QAA24267
	for ietf-outbound.10@ietf.org; Mon, 14 Feb 2000 16:30:02 -0500 (EST)
Received: from prue.eim.surrey.ac.uk (IDENT:exim@prue.eim.surrey.ac.uk [131.227.76.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24201
	for <ietf@ietf.org>; Mon, 14 Feb 2000 16:25:59 -0500 (EST)
Received: from petra.ee.surrey.ac.uk ([131.227.88.13] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.03 #1)
	id 12KT0J-0005lw-00
	for ietf@ietf.org; Mon, 14 Feb 2000 21:25:59 +0000
Date: Mon, 14 Feb 2000 21:25:56 +0000 (GMT)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-Sender: eep1lw@petra.ee.surrey.ac.uk
Reply-To: L.Wood@eim.surrey.ac.uk
To: ietf@ietf.org
Subject: Proposal: reclassify RFC2549, 1149 as historical
Message-ID: <Pine.SOL.4.10.10002142113530.5614-100000@petra.ee.surrey.ac.uk>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

I move we reclassify RFC2549 and RFC1149 as historical.

Evidence to support this: 'end of an era' according to
http://www.telegraph.co.uk/et?ac=000111464113065&pg=/et/00/2/14/wpig14.html
below.

In particular, I don't think the QoS additions have ever been fully
field tested; the WFQ proposal leads to observable instances of
dropped tails during measurement.

L.

don't you just hate thinking about sending yourself valentines?

<L.Wood@surrey.ac.uk>PGP<http://www.ee.surrey.ac.uk/Personal/L.Wood/>


ELECTRONIC TELEGRAPH, ISSUE 1725

Monday 14 February 2000

Spread of radio switches off political pigeon post
By Jon Stock in New Delhi

MORE than 600 Indian police carrier pigeons face early retirement
after officials decided to replace them with radios.
                                       
The decision to ground the birds before Wednesday's state assembly
elections in Orissa, eastern India, marks the end of an era. They
previously played a unique role in India's electoral process.
                                       
They last saw active duty during last year's general election, when
they carried messages to and from far-flung polling booths in the
remote Orissa districts of Koraput and Dhenkanal. The messages
detailed the law and order situation during polling. The pigeons are
kept in 28 lofts throughout the state and will now become showpieces
used solely for ceremonial purposes, according to Baikunthanath Das,
Superintendent of Police (Signals), who looks after them.

Their demise has been caused by what he called the advent of new
technology. He said: "Even the most remote interior areas now have VHF
radios."

The service was the only one of its kind in India. It was started in
1946 during British rule by the state police's Signal Establishment,
which bought more than 1,000 pigeons from the Indian Army after the
Second World War.



From owner-ietf-outbound  Mon Feb 14 17:00:46 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA24936
	for ietf-outbound.10@ietf.org; Mon, 14 Feb 2000 17:00:02 -0500 (EST)
Received: from fepC.post.tele.dk (fepC.post.tele.dk [195.41.46.147])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24714
	for <IETF@ietf.org>; Mon, 14 Feb 2000 16:50:33 -0500 (EST)
Received: from Anders ([194.239.165.165]) by fepC.post.tele.dk
          (InterMail vM.4.01.02.00 201-229-116) with SMTP
          id <20000214215027.CLSW706.fepC.post.tele.dk@Anders>
          for <IETF@ietf.org>; Mon, 14 Feb 2000 22:50:27 +0100
Message-ID: <004801bf7735$7d3bb420$1000000a@DIC>
From: "Anders Feder" <lists.anders@feder.dk>
To: <IETF@ietf.org>
Subject: Re: Internet SYN Flooding, spoofing attacks
Date: Mon, 14 Feb 2000 22:50:19 +0100
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 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Robert Elz <kre@munnari.OZ.AU> wrote:
>I'm not sure there is a good analogy there.    There's no good purpose
>in sending packets with incorrect source addresses I can think of, and
>stopping the practice is the basic intent of the filters.

"In his early days at Intel, Andy Grove was approached by an employee who
suggested the company start work on a personal computer based on its chips.
Skeptical, he asked what a personal computer might do. The employee,
searching for a good example, said it could be used to store recipes. Grove
thought about the millions he'd have to spend on research, development, and
marketing, then considered the imperfect but steady quality of an
alphabetized loose-leaf binder. He finally passed on the idea and decided to
concentrate on the lucrative business of supplying chips for traffic
lights."

It is rarely very easy to see what requirements the future will bring and
particularly in this business you can't be sure what the technology of
tomorrow demands. And, agreed,  bogus source IPs _does_ at present time
look like nothing but the devils work. But in, say, 10 years a new flashy
techology could be requiring that you have the ability to stamp packets with
other IPs than your own. Unfortunately, back in year 2000, somebody put in
IP filters at all ISPs and now, 10 years after, these filters is so
integrated a part
of the ISP software that reprogramming would cost a fortune.
Also consider the size of the group of Internet users that send out packets
with incorrect source IPs. Using IP filters would be like illegalizing
coffee because a fraction of the people on the earth is allergic to
caffeine.

- Anders Feder







From owner-ietf-outbound@ietf.org  Mon Feb 14 17:04:38 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25133
	for <ietf-web-archive@odin.ietf.org>; Mon, 14 Feb 2000 17:04:38 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA02410;
	Mon, 14 Feb 2000 17:02:40 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id RAA24936
	for ietf-outbound.10@ietf.org; Mon, 14 Feb 2000 17:00:02 -0500 (EST)
Received: from fepC.post.tele.dk (fepC.post.tele.dk [195.41.46.147])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24714
	for <IETF@ietf.org>; Mon, 14 Feb 2000 16:50:33 -0500 (EST)
Received: from Anders ([194.239.165.165]) by fepC.post.tele.dk
          (InterMail vM.4.01.02.00 201-229-116) with SMTP
          id <20000214215027.CLSW706.fepC.post.tele.dk@Anders>
          for <IETF@ietf.org>; Mon, 14 Feb 2000 22:50:27 +0100
Message-ID: <004801bf7735$7d3bb420$1000000a@DIC>
From: "Anders Feder" <lists.anders@feder.dk>
To: <IETF@ietf.org>
Subject: Re: Internet SYN Flooding, spoofing attacks
Date: Mon, 14 Feb 2000 22:50:19 +0100
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 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Robert Elz <kre@munnari.OZ.AU> wrote:
>I'm not sure there is a good analogy there.    There's no good purpose
>in sending packets with incorrect source addresses I can think of, and
>stopping the practice is the basic intent of the filters.

"In his early days at Intel, Andy Grove was approached by an employee who
suggested the company start work on a personal computer based on its chips.
Skeptical, he asked what a personal computer might do. The employee,
searching for a good example, said it could be used to store recipes. Grove
thought about the millions he'd have to spend on research, development, and
marketing, then considered the imperfect but steady quality of an
alphabetized loose-leaf binder. He finally passed on the idea and decided to
concentrate on the lucrative business of supplying chips for traffic
lights."

It is rarely very easy to see what requirements the future will bring and
particularly in this business you can't be sure what the technology of
tomorrow demands. And, agreed,  bogus source IPs _does_ at present time
look like nothing but the devils work. But in, say, 10 years a new flashy
techology could be requiring that you have the ability to stamp packets with
other IPs than your own. Unfortunately, back in year 2000, somebody put in
IP filters at all ISPs and now, 10 years after, these filters is so
integrated a part
of the ISP software that reprogramming would cost a fortune.
Also consider the size of the group of Internet users that send out packets
with incorrect source IPs. Using IP filters would be like illegalizing
coffee because a fraction of the people on the earth is allergic to
caffeine.

- Anders Feder







From owner-ietf-outbound  Mon Feb 14 18:50:36 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA26624
	for ietf-outbound.10@ietf.org; Mon, 14 Feb 2000 18:50:02 -0500 (EST)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26550
	for <ietf@ietf.org>; Mon, 14 Feb 2000 18:45:21 -0500 (EST)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id SAA00271;
        Mon, 14 Feb 2000 18:37:05 -0500 (EST)
Message-Id: <200002142337.SAA00271@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
X-PGP-Key: 2F07A741 ; 78 15 8E 8B C0 06 5D D1  BC 08 05 7F 42 81 7E 90 
To: apps area chairs and working groups: ;
cc: ietf@ietf.org
reply-to: ietf@ietf.org
From: Keith Moore <moore@cs.utk.edu>
Subject: IETF Adelaide and interim meetings for APPS WGs
Date: Mon, 14 Feb 2000 18:37:05 -0500
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

It has come to the attention of the Applications Area Directors
that one or more Applications area working groups have elected
to not meet in Adelaide, and instead to hold an "interim meeting"
in the United States, presumably because of distance and/or cost issues.

IETF is an international organization, and it is IETF's longstanding 
practice to hold its meetings in various locations around the planet.
This serves both to encourage wider participation in IETF and also
to more fairly distribute travel costs and inconvenience (over time) 
among all participants.  The scheduleing of an interim WG meeting in 
the US in lieu of a WG meeting in Adelaide undermines this policy.  
This is insulting to non-US participants of IETF (many of whom have 
attended meetings in the US for years), embarassing to IETF as 
a whole, and a threat to IETF's international stature.

Even if a working group has few participants outside the United
States, a working group does not work in isolation from other
working groups.  Attendance at IETF meetings is an invaluable 
mechanism for cross-group collaboration.  

RFC 2418 states:

   Interim meetings are subject to the
   same rules for advance notification, reporting, open participation,
   and process, which apply to other working group meetings.

Since normal working group meetings require advance notification
via email to the entire IETF list, and the process for getting a meeting
slot involves prior approval of the Area Directors, the same
requirements apply to interim working group meetings.  Part of the 
reason for prior approval being required is to ensure that the 
locations of the meetings are not being chosen to favor certain 
participants over others.  

There have been several violations of this policy since publication
of RFC 2418.

Therefore,

- All interim meetings within the Applications Area which were not
  previously and explicitly approved by the Applications Area Directors, 
  are hereby cancelled.

- No Applications Area group will hold any interim meeting prior
  to April 15.

- No Applications Area group which does not hold a meeting in 
  Adelaide, will hold any interim meeting prior to July 31.
  (i.e. prior to the Pittsburg IETF meeting)

- This applies to all face to face meetings held for the purpose 
  of conducting working group discussion and to which the working 
  group is invited, even if labelled "informal" or otherwise 
  labelled to distinguish them from official working group meetings.

- Exceptions to this policy may be made for recently chartered groups,
  but Area Director approval is still required for such groups to
  schedule interim meetings.


for the Applications Area Directors,

Keith Moore



From owner-ietf-outbound@ietf.org  Mon Feb 14 18:54:05 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26768
	for <ietf-web-archive@odin.ietf.org>; Mon, 14 Feb 2000 18:54:05 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA05459;
	Mon, 14 Feb 2000 18:52:07 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id SAA26624
	for ietf-outbound.10@ietf.org; Mon, 14 Feb 2000 18:50:02 -0500 (EST)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26550
	for <ietf@ietf.org>; Mon, 14 Feb 2000 18:45:21 -0500 (EST)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id SAA00271;
        Mon, 14 Feb 2000 18:37:05 -0500 (EST)
Message-Id: <200002142337.SAA00271@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
X-PGP-Key: 2F07A741 ; 78 15 8E 8B C0 06 5D D1  BC 08 05 7F 42 81 7E 90 
To: apps area chairs and working groups: ;
cc: ietf@ietf.org
reply-to: ietf@ietf.org
From: Keith Moore <moore@cs.utk.edu>
Subject: IETF Adelaide and interim meetings for APPS WGs
Date: Mon, 14 Feb 2000 18:37:05 -0500
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

It has come to the attention of the Applications Area Directors
that one or more Applications area working groups have elected
to not meet in Adelaide, and instead to hold an "interim meeting"
in the United States, presumably because of distance and/or cost issues.

IETF is an international organization, and it is IETF's longstanding 
practice to hold its meetings in various locations around the planet.
This serves both to encourage wider participation in IETF and also
to more fairly distribute travel costs and inconvenience (over time) 
among all participants.  The scheduleing of an interim WG meeting in 
the US in lieu of a WG meeting in Adelaide undermines this policy.  
This is insulting to non-US participants of IETF (many of whom have 
attended meetings in the US for years), embarassing to IETF as 
a whole, and a threat to IETF's international stature.

Even if a working group has few participants outside the United
States, a working group does not work in isolation from other
working groups.  Attendance at IETF meetings is an invaluable 
mechanism for cross-group collaboration.  

RFC 2418 states:

   Interim meetings are subject to the
   same rules for advance notification, reporting, open participation,
   and process, which apply to other working group meetings.

Since normal working group meetings require advance notification
via email to the entire IETF list, and the process for getting a meeting
slot involves prior approval of the Area Directors, the same
requirements apply to interim working group meetings.  Part of the 
reason for prior approval being required is to ensure that the 
locations of the meetings are not being chosen to favor certain 
participants over others.  

There have been several violations of this policy since publication
of RFC 2418.

Therefore,

- All interim meetings within the Applications Area which were not
  previously and explicitly approved by the Applications Area Directors, 
  are hereby cancelled.

- No Applications Area group will hold any interim meeting prior
  to April 15.

- No Applications Area group which does not hold a meeting in 
  Adelaide, will hold any interim meeting prior to July 31.
  (i.e. prior to the Pittsburg IETF meeting)

- This applies to all face to face meetings held for the purpose 
  of conducting working group discussion and to which the working 
  group is invited, even if labelled "informal" or otherwise 
  labelled to distinguish them from official working group meetings.

- Exceptions to this policy may be made for recently chartered groups,
  but Area Director approval is still required for such groups to
  schedule interim meetings.


for the Applications Area Directors,

Keith Moore



From owner-ietf-outbound  Mon Feb 14 19:00:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA26853
	for ietf-outbound.10@ietf.org; Mon, 14 Feb 2000 19:00:02 -0500 (EST)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26567
	for <IETF@ietf.org>; Mon, 14 Feb 2000 18:45:58 -0500 (EST)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id PAA20854;
	Mon, 14 Feb 2000 15:41:14 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.9.3/8.9.3-VIRSCAN) id PAA04096;
	Mon, 14 Feb 2000 15:34:39 -0800
X-Virus-Scanned:  Mon, 14 Feb 2000 15:34:39 -0800 Nokia Silicon Valley AntiVirus Appliance
Received: from <charliep@iprg.nokia.com> (charliep.iprg.nokia.com [205.226.2.89]) by darkstar.iprg.nokia.com  SMTP/WTS (12.69)
 xma003974; Mon, 14 Feb 00 15:34:35 -0800
Sender: charliep@iprg.nokia.com
Message-ID: <38A89295.F17D1153@iprg.nokia.com>
Date: Mon, 14 Feb 2000 15:41:09 -0800
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Robert Elz <kre@munnari.OZ.AU>
CC: "Donald E. Eastlake 3rd" <dee3@TORQUE.POTHOLE.COM>, IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
References: <15516.950526307@munnari.OZ.AU>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Robert Elz wrote:

>                                             There's no good purpose
> in sending packets with incorrect source addresses I can think of, and
> stopping the practice is the basic intent of the filters.

Mobile IP would like to send out packets with the mobile node's
home address, while it is attached to a network in a foreign
domain.  The home address is likely to look "incorrect" from
the standpoint of such a filter.

Plus I don't think the gain is worth the pain.  I'd rather see
a technology that actually solves the problem instead of swatting
at gnats with a sledge hammer.

What if routers could preferentially keep track of things like SYN
packets and so on for a few seconds, and we had some traceback management
software and security associations with our neighbors enough to do
some automatic detection?

It might cost 2% more for the memory buffers, geez I don't know.

Regards,
Charlie P.



From owner-ietf-outbound@ietf.org  Mon Feb 14 19:02:33 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26973
	for <ietf-web-archive@odin.ietf.org>; Mon, 14 Feb 2000 19:02:32 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA05804;
	Mon, 14 Feb 2000 19:00:33 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id TAA26853
	for ietf-outbound.10@ietf.org; Mon, 14 Feb 2000 19:00:02 -0500 (EST)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26567
	for <IETF@ietf.org>; Mon, 14 Feb 2000 18:45:58 -0500 (EST)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id PAA20854;
	Mon, 14 Feb 2000 15:41:14 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.9.3/8.9.3-VIRSCAN) id PAA04096;
	Mon, 14 Feb 2000 15:34:39 -0800
X-Virus-Scanned:  Mon, 14 Feb 2000 15:34:39 -0800 Nokia Silicon Valley AntiVirus Appliance
Received: from <charliep@iprg.nokia.com> (charliep.iprg.nokia.com [205.226.2.89]) by darkstar.iprg.nokia.com  SMTP/WTS (12.69)
 xma003974; Mon, 14 Feb 00 15:34:35 -0800
Sender: charliep@iprg.nokia.com
Message-ID: <38A89295.F17D1153@iprg.nokia.com>
Date: Mon, 14 Feb 2000 15:41:09 -0800
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Robert Elz <kre@munnari.OZ.AU>
CC: "Donald E. Eastlake 3rd" <dee3@TORQUE.POTHOLE.COM>, IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
References: <15516.950526307@munnari.OZ.AU>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Robert Elz wrote:

>                                             There's no good purpose
> in sending packets with incorrect source addresses I can think of, and
> stopping the practice is the basic intent of the filters.

Mobile IP would like to send out packets with the mobile node's
home address, while it is attached to a network in a foreign
domain.  The home address is likely to look "incorrect" from
the standpoint of such a filter.

Plus I don't think the gain is worth the pain.  I'd rather see
a technology that actually solves the problem instead of swatting
at gnats with a sledge hammer.

What if routers could preferentially keep track of things like SYN
packets and so on for a few seconds, and we had some traceback management
software and security associations with our neighbors enough to do
some automatic detection?

It might cost 2% more for the memory buffers, geez I don't know.

Regards,
Charlie P.



From owner-ietf-outbound  Mon Feb 14 19:10:07 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA27105
	for ietf-outbound.10@ietf.org; Mon, 14 Feb 2000 19:10:02 -0500 (EST)
Received: from servo.qualcomm.com (servo.qualcomm.com [129.46.76.82])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27003
	for <IETF@ietf.org>; Mon, 14 Feb 2000 19:04:29 -0500 (EST)
Received: (from karn@localhost) by servo.qualcomm.com (8.8.5/1.4/8.7.2/1.14) id QAA04489; Mon, 14 Feb 2000 16:04:28 -0800 (PST)
Date: Mon, 14 Feb 2000 16:04:28 -0800 (PST)
Message-Id: <200002150004.QAA04489@servo.qualcomm.com>
From: Phil Karn <karn@qualcomm.com>
To: lists.anders@feder.dk
CC: IETF@ietf.org, karn@qualcomm.com
In-reply-to: <004801bf7735$7d3bb420$1000000a@DIC> (lists.anders@feder.dk)
Subject: Re: Internet SYN Flooding, spoofing attacks
X-Loop: ietf@ietf.org

>tomorrow demands. And, agreed,  bogus source IPs _does_ at present time
>look like nothing but the devils work. But in, say, 10 years a new flashy
>techology could be requiring that you have the ability to stamp packets with
>other IPs than your own. Unfortunately, back in year 2000, somebody put in

There already are some perfectly legitimate reasons to send packets
with "alien" IP source addresses. Mobile IP is the best example, but
various virtual private networking schemes also do this. For example,
I have a VPN set up over my cable modem so I can have a block of
static IP addresses for my home network. I had to do some work to
evade the $#@!! source IP address ingress filtering in my cable
network. I do it by tunneling the upstream packets through a machine
at work.

Being forced to tunnel not only increases the size of each packet, but
also entails suboptimum routing and reliance on yet more network
elements.  I use the new Linux policy routing mechanisms to tunnel
only those packets that have to be tunneled, which helps. But it would
sure be nice if I didn't have to tunnel my outbound packets at all.

Source address ingress filtering is one of those ideas that seems like
a good one when you first think about it, but it just doesn't pan out.
It interferes with some perfectly legitimate activities, it doesn't
really stop the bad guys, and it deflects attention away from the real
solutions.

In the case of MS-DOS (Multiple Source-Denial of Service) attacks like
the ones we saw last week, we need to deploy better inter-router
mechanisms to deal with congestion by moving the packet drop points as
far upstream as possible toward the senders. And if these mechanisms
can work for deliberate flooding attacks, they'll also deal with
non-deliberate congestion.

Phil



From owner-ietf-outbound@ietf.org  Mon Feb 14 19:12:20 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27204
	for <ietf-web-archive@odin.ietf.org>; Mon, 14 Feb 2000 19:12:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA06335;
	Mon, 14 Feb 2000 19:10:21 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id TAA27105
	for ietf-outbound.10@ietf.org; Mon, 14 Feb 2000 19:10:02 -0500 (EST)
Received: from servo.qualcomm.com (servo.qualcomm.com [129.46.76.82])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27003
	for <IETF@ietf.org>; Mon, 14 Feb 2000 19:04:29 -0500 (EST)
Received: (from karn@localhost) by servo.qualcomm.com (8.8.5/1.4/8.7.2/1.14) id QAA04489; Mon, 14 Feb 2000 16:04:28 -0800 (PST)
Date: Mon, 14 Feb 2000 16:04:28 -0800 (PST)
Message-Id: <200002150004.QAA04489@servo.qualcomm.com>
From: Phil Karn <karn@qualcomm.com>
To: lists.anders@feder.dk
CC: IETF@ietf.org, karn@qualcomm.com
In-reply-to: <004801bf7735$7d3bb420$1000000a@DIC> (lists.anders@feder.dk)
Subject: Re: Internet SYN Flooding, spoofing attacks
X-Loop: ietf@ietf.org

>tomorrow demands. And, agreed,  bogus source IPs _does_ at present time
>look like nothing but the devils work. But in, say, 10 years a new flashy
>techology could be requiring that you have the ability to stamp packets with
>other IPs than your own. Unfortunately, back in year 2000, somebody put in

There already are some perfectly legitimate reasons to send packets
with "alien" IP source addresses. Mobile IP is the best example, but
various virtual private networking schemes also do this. For example,
I have a VPN set up over my cable modem so I can have a block of
static IP addresses for my home network. I had to do some work to
evade the $#@!! source IP address ingress filtering in my cable
network. I do it by tunneling the upstream packets through a machine
at work.

Being forced to tunnel not only increases the size of each packet, but
also entails suboptimum routing and reliance on yet more network
elements.  I use the new Linux policy routing mechanisms to tunnel
only those packets that have to be tunneled, which helps. But it would
sure be nice if I didn't have to tunnel my outbound packets at all.

Source address ingress filtering is one of those ideas that seems like
a good one when you first think about it, but it just doesn't pan out.
It interferes with some perfectly legitimate activities, it doesn't
really stop the bad guys, and it deflects attention away from the real
solutions.

In the case of MS-DOS (Multiple Source-Denial of Service) attacks like
the ones we saw last week, we need to deploy better inter-router
mechanisms to deal with congestion by moving the packet drop points as
far upstream as possible toward the senders. And if these mechanisms
can work for deliberate flooding attacks, they'll also deal with
non-deliberate congestion.

Phil



From owner-ietf-outbound  Mon Feb 14 19:41:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA27716
	for ietf-outbound.10@ietf.org; Mon, 14 Feb 2000 19:40:02 -0500 (EST)
Received: from mailman.cisco.com (mailman.cisco.com [171.68.225.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27620
	for <IETF@ietf.org>; Mon, 14 Feb 2000 19:32:45 -0500 (EST)
Received: from bigger-dawgs (pferguso-isdn.cisco.com [171.70.114.134]) by mailman.cisco.com (8.8.8+Sun/CISCO.SERVER.1.2) with ESMTP id QAA17015; Mon, 14 Feb 2000 16:22:52 -0800 (PST)
Message-Id: <4.2.2.20000214191957.00a6c760@lint.cisco.com>
X-Sender: pferguso@lint.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Mon, 14 Feb 2000 19:22:45 -0500
To: "Charles E. Perkins" <charliep@iprg.nokia.com>
From: Paul Ferguson <ferguson@cisco.com>
Subject: Re: Internet SYN Flooding, spoofing attacks
Cc: Robert Elz <kre@munnari.OZ.AU>,
        "Donald E. Eastlake 3rd" <dee3@TORQUE.POTHOLE.COM>, IETF@ietf.org,
        dts@senie.com
In-Reply-To: <38A89295.F17D1153@iprg.nokia.com>
References: <15516.950526307@munnari.OZ.AU>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 03:41 PM 02/14/2000 -0800, Charles E. Perkins wrote:

>Mobile IP would like to send out packets with the mobile node's
>home address, while it is attached to a network in a foreign
>domain.  The home address is likely to look "incorrect" from
>the standpoint of such a filter.

If I'm not mistaken (although my coauthor has tracked the mobile
ip cruft more than have I), there is some notion of a tunneling
mechanism from the first-hop mobile ip gateway, such that the
bogon source is really never seen in that fashion (as a bogon).

Again, I admit complete ignorance of mobile ip cruft.

>Plus I don't think the gain is worth the pain.  I'd rather see
>a technology that actually solves the problem instead of swatting
>at gnats with a sledge hammer.

Well, right now, you get swatted. Figure out a better way, and
you'll stop getting swatted.

- paul



From owner-ietf-outbound@ietf.org  Mon Feb 14 19:43:25 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27871
	for <ietf-web-archive@odin.ietf.org>; Mon, 14 Feb 2000 19:43:25 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA07982;
	Mon, 14 Feb 2000 19:41:26 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id TAA27716
	for ietf-outbound.10@ietf.org; Mon, 14 Feb 2000 19:40:02 -0500 (EST)
Received: from mailman.cisco.com (mailman.cisco.com [171.68.225.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27620
	for <IETF@ietf.org>; Mon, 14 Feb 2000 19:32:45 -0500 (EST)
Received: from bigger-dawgs (pferguso-isdn.cisco.com [171.70.114.134]) by mailman.cisco.com (8.8.8+Sun/CISCO.SERVER.1.2) with ESMTP id QAA17015; Mon, 14 Feb 2000 16:22:52 -0800 (PST)
Message-Id: <4.2.2.20000214191957.00a6c760@lint.cisco.com>
X-Sender: pferguso@lint.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Mon, 14 Feb 2000 19:22:45 -0500
To: "Charles E. Perkins" <charliep@iprg.nokia.com>
From: Paul Ferguson <ferguson@cisco.com>
Subject: Re: Internet SYN Flooding, spoofing attacks
Cc: Robert Elz <kre@munnari.OZ.AU>,
        "Donald E. Eastlake 3rd" <dee3@TORQUE.POTHOLE.COM>, IETF@ietf.org,
        dts@senie.com
In-Reply-To: <38A89295.F17D1153@iprg.nokia.com>
References: <15516.950526307@munnari.OZ.AU>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 03:41 PM 02/14/2000 -0800, Charles E. Perkins wrote:

>Mobile IP would like to send out packets with the mobile node's
>home address, while it is attached to a network in a foreign
>domain.  The home address is likely to look "incorrect" from
>the standpoint of such a filter.

If I'm not mistaken (although my coauthor has tracked the mobile
ip cruft more than have I), there is some notion of a tunneling
mechanism from the first-hop mobile ip gateway, such that the
bogon source is really never seen in that fashion (as a bogon).

Again, I admit complete ignorance of mobile ip cruft.

>Plus I don't think the gain is worth the pain.  I'd rather see
>a technology that actually solves the problem instead of swatting
>at gnats with a sledge hammer.

Well, right now, you get swatted. Figure out a better way, and
you'll stop getting swatted.

- paul



From owner-ietf-outbound  Mon Feb 14 19:50:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA28004
	for ietf-outbound.10@ietf.org; Mon, 14 Feb 2000 19:50:02 -0500 (EST)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27912
	for <ietf@ietf.org>; Mon, 14 Feb 2000 19:45:05 -0500 (EST)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id RAA08041
	for ietf@ietf.org  env-from <vjs>;
	Mon, 14 Feb 2000 17:45:05 -0700 (MST)
Date: Mon, 14 Feb 2000 17:45:05 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200002150045.RAA08041@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
X-Loop: ietf@ietf.org

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

> ...
> RFC 2418 states:
>
>    Interim meetings are subject to the
>    same rules for advance notification, reporting, open participation,
>    and process, which apply to other working group meetings.

> ...
> - This applies to all face to face meetings held for the purpose 
>   of conducting working group discussion and to which the working 
>   group is invited, even if labelled "informal" or otherwise 
>   labelled to distinguish them from official working group meetings.

I'm not a lawyer, but that sounds like it might conflict with the U.S.
Constitution's provisions concerning freedom of assembly.  It also sounds
hard to police; if some working group participants encounter each other
in an airport waiting room, are they not allowed to talk business?  What
about participants who work for the same outfit and see each other daily?

Are you going to apply the same rules to meetings of the IAB and IESG?

You could doubtless fix those modest hassles with the wording of this
demand that RFC 2418 be honored, but what is the point?  Unless you going
to slide the IETF the rest of the way into the ITU/IEEE/ANSI swamp, won't
the mailing lists continue to be the only official forums for the working
groups?  Won't the working group meetings continue to be effectively
informal, slightly more than social gatherings? 

In other words and politically correct pretense asside, the IETF is not
an international organization.  Despite its posturing, the IETF is a U.S.
or perhaps North American organization that welcomes non-U.S. participants
and occasionally spends a lot of its U.S. participants' time and money to
try to make people outside of North America feel welcome.  If the IETF
did honestly aspire to be an international organization, it would need
the characteristics of the ITU (e.g. translators and high prices for
documents).  Do you think that would be a good thing?


(I've never attended an IETF working group meeting, despite working group
participation for a lot of years.  I've never felt the lack as far as
technical things go.  I can't find words in RFC 2418 that say that the
mailing list is the authoritative forum, which strikes me as a terrible
omission or catastrophic de facto change.)


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound@ietf.org  Mon Feb 14 19:52:31 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28094
	for <ietf-web-archive@odin.ietf.org>; Mon, 14 Feb 2000 19:52:31 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA08105;
	Mon, 14 Feb 2000 19:50:32 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id TAA28004
	for ietf-outbound.10@ietf.org; Mon, 14 Feb 2000 19:50:02 -0500 (EST)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27912
	for <ietf@ietf.org>; Mon, 14 Feb 2000 19:45:05 -0500 (EST)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id RAA08041
	for ietf@ietf.org  env-from <vjs>;
	Mon, 14 Feb 2000 17:45:05 -0700 (MST)
Date: Mon, 14 Feb 2000 17:45:05 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200002150045.RAA08041@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
X-Loop: ietf@ietf.org

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

> ...
> RFC 2418 states:
>
>    Interim meetings are subject to the
>    same rules for advance notification, reporting, open participation,
>    and process, which apply to other working group meetings.

> ...
> - This applies to all face to face meetings held for the purpose 
>   of conducting working group discussion and to which the working 
>   group is invited, even if labelled "informal" or otherwise 
>   labelled to distinguish them from official working group meetings.

I'm not a lawyer, but that sounds like it might conflict with the U.S.
Constitution's provisions concerning freedom of assembly.  It also sounds
hard to police; if some working group participants encounter each other
in an airport waiting room, are they not allowed to talk business?  What
about participants who work for the same outfit and see each other daily?

Are you going to apply the same rules to meetings of the IAB and IESG?

You could doubtless fix those modest hassles with the wording of this
demand that RFC 2418 be honored, but what is the point?  Unless you going
to slide the IETF the rest of the way into the ITU/IEEE/ANSI swamp, won't
the mailing lists continue to be the only official forums for the working
groups?  Won't the working group meetings continue to be effectively
informal, slightly more than social gatherings? 

In other words and politically correct pretense asside, the IETF is not
an international organization.  Despite its posturing, the IETF is a U.S.
or perhaps North American organization that welcomes non-U.S. participants
and occasionally spends a lot of its U.S. participants' time and money to
try to make people outside of North America feel welcome.  If the IETF
did honestly aspire to be an international organization, it would need
the characteristics of the ITU (e.g. translators and high prices for
documents).  Do you think that would be a good thing?


(I've never attended an IETF working group meeting, despite working group
participation for a lot of years.  I've never felt the lack as far as
technical things go.  I can't find words in RFC 2418 that say that the
mailing list is the authoritative forum, which strikes me as a terrible
omission or catastrophic de facto change.)


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Mon Feb 14 21:00:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA29667
	for ietf-outbound.10@ietf.org; Mon, 14 Feb 2000 21:00:02 -0500 (EST)
Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29456
	for <ietf@ietf.org>; Mon, 14 Feb 2000 20:53:47 -0500 (EST)
Received: from postal.research.att.com (postal.research.att.com [135.207.23.30])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id 670E44CE22; Mon, 14 Feb 2000 20:53:48 -0500 (EST)
Received: from SIGABA.research.att.com (sigaba.research.att.com [135.207.23.169])
	by postal.research.att.com (8.8.7/8.8.7) with ESMTP id UAA05510;
	Mon, 14 Feb 2000 20:53:47 -0500 (EST)
Received: by SIGABA.research.att.com (Postfix, from userid 54047)
	id 735FB41F16; Mon, 14 Feb 2000 20:53:47 -0500 (EST)
Received: from roc (localhost [127.0.0.1])
	by SIGABA.research.att.com (Postfix) with ESMTP
	id 645E6400B5; Mon, 14 Feb 2000 20:53:42 -0500 (EST)
X-Mailer: exmh version 2.1.1 10/15/1999
From: "Steven M. Bellovin" <smb@research.att.com>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
Cc: ietf@ietf.org
Subject: Re: IETF Adelaide and interim meetings for APPS WGs 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 14 Feb 2000 20:53:42 -0500
Sender: smb@research.att.com
Message-Id: <20000215015347.735FB41F16@SIGABA.research.att.com>
X-Loop: ietf@ietf.org

In message <200002150045.RAA08041@calcite.rhyolite.com>, Vernon Schryver writes
:

> I'm not a lawyer, but that sounds like it might conflict with the U.S.
> Constitution's provisions concerning freedom of assembly.

(a) The U.S. constitution applies to the Federal government (and sometimes to 
the state governments); it does not apply to private groups.
(b) No one ever said that these folks can't meet; they just can't do it under 
the imprimatur of the IETF. 

>  It also sounds
> hard to police; if some working group participants encounter each other
> in an airport waiting room, are they not allowed to talk business?  What
> about participants who work for the same outfit and see each other daily?
> 
> Are you going to apply the same rules to meetings of the IAB and IESG?

??  I'll let the IESG speak for itself.  The IAB does not meet physically 
except at IETF meetings.  Instead, we have monthly conference calls.  We do 
hold workshops (which is expressly provided for in RFC 1601); the last such 
workshop was in Utrecht.  Not all IAB members attend all workshops; a number of 
outsiders are invited.
> 
> You could doubtless fix those modest hassles with the wording of this
> demand that RFC 2418 be honored, but what is the point?  Unless you going
> to slide the IETF the rest of the way into the ITU/IEEE/ANSI swamp, won't
> the mailing lists continue to be the only official forums for the working
> groups?  Won't the working group meetings continue to be effectively
> informal, slightly more than social gatherings? 

The point is that some things are better accomplished in a high-bandwidth 
environment.  
> 
> In other words and politically correct pretense asside, the IETF is not
> an international organization.  Despite its posturing, the IETF is a U.S.
> or perhaps North American organization that welcomes non-U.S. participants
> and occasionally spends a lot of its U.S. participants' time and money to
> try to make people outside of North America feel welcome.  If the IETF
> did honestly aspire to be an international organization, it would need
> the characteristics of the ITU (e.g. translators and high prices for
> documents).  Do you think that would be a good thing?
> 

I'm afraid I don't follow the logic of your penultimate sententce.  The 
current schedule has about 1 meeting out of 3 outside of North America.

		--Steve Bellovin




From owner-ietf-outbound@ietf.org  Mon Feb 14 21:03:08 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29847
	for <ietf-web-archive@odin.ietf.org>; Mon, 14 Feb 2000 21:03:07 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA09594;
	Mon, 14 Feb 2000 21:01:03 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id VAA29667
	for ietf-outbound.10@ietf.org; Mon, 14 Feb 2000 21:00:02 -0500 (EST)
Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29456
	for <ietf@ietf.org>; Mon, 14 Feb 2000 20:53:47 -0500 (EST)
Received: from postal.research.att.com (postal.research.att.com [135.207.23.30])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id 670E44CE22; Mon, 14 Feb 2000 20:53:48 -0500 (EST)
Received: from SIGABA.research.att.com (sigaba.research.att.com [135.207.23.169])
	by postal.research.att.com (8.8.7/8.8.7) with ESMTP id UAA05510;
	Mon, 14 Feb 2000 20:53:47 -0500 (EST)
Received: by SIGABA.research.att.com (Postfix, from userid 54047)
	id 735FB41F16; Mon, 14 Feb 2000 20:53:47 -0500 (EST)
Received: from roc (localhost [127.0.0.1])
	by SIGABA.research.att.com (Postfix) with ESMTP
	id 645E6400B5; Mon, 14 Feb 2000 20:53:42 -0500 (EST)
X-Mailer: exmh version 2.1.1 10/15/1999
From: "Steven M. Bellovin" <smb@research.att.com>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
Cc: ietf@ietf.org
Subject: Re: IETF Adelaide and interim meetings for APPS WGs 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 14 Feb 2000 20:53:42 -0500
Sender: smb@research.att.com
Message-Id: <20000215015347.735FB41F16@SIGABA.research.att.com>
X-Loop: ietf@ietf.org

In message <200002150045.RAA08041@calcite.rhyolite.com>, Vernon Schryver writes
:

> I'm not a lawyer, but that sounds like it might conflict with the U.S.
> Constitution's provisions concerning freedom of assembly.

(a) The U.S. constitution applies to the Federal government (and sometimes to 
the state governments); it does not apply to private groups.
(b) No one ever said that these folks can't meet; they just can't do it under 
the imprimatur of the IETF. 

>  It also sounds
> hard to police; if some working group participants encounter each other
> in an airport waiting room, are they not allowed to talk business?  What
> about participants who work for the same outfit and see each other daily?
> 
> Are you going to apply the same rules to meetings of the IAB and IESG?

??  I'll let the IESG speak for itself.  The IAB does not meet physically 
except at IETF meetings.  Instead, we have monthly conference calls.  We do 
hold workshops (which is expressly provided for in RFC 1601); the last such 
workshop was in Utrecht.  Not all IAB members attend all workshops; a number of 
outsiders are invited.
> 
> You could doubtless fix those modest hassles with the wording of this
> demand that RFC 2418 be honored, but what is the point?  Unless you going
> to slide the IETF the rest of the way into the ITU/IEEE/ANSI swamp, won't
> the mailing lists continue to be the only official forums for the working
> groups?  Won't the working group meetings continue to be effectively
> informal, slightly more than social gatherings? 

The point is that some things are better accomplished in a high-bandwidth 
environment.  
> 
> In other words and politically correct pretense asside, the IETF is not
> an international organization.  Despite its posturing, the IETF is a U.S.
> or perhaps North American organization that welcomes non-U.S. participants
> and occasionally spends a lot of its U.S. participants' time and money to
> try to make people outside of North America feel welcome.  If the IETF
> did honestly aspire to be an international organization, it would need
> the characteristics of the ITU (e.g. translators and high prices for
> documents).  Do you think that would be a good thing?
> 

I'm afraid I don't follow the logic of your penultimate sententce.  The 
current schedule has about 1 meeting out of 3 outside of North America.

		--Steve Bellovin




From owner-ietf-outbound  Mon Feb 14 21:10:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA00035
	for ietf-outbound.10@ietf.org; Mon, 14 Feb 2000 21:10:03 -0500 (EST)
Received: from kickme.cisco.com (kickme.cisco.com [198.92.30.42])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29466
	for <ietf@ietf.org>; Mon, 14 Feb 2000 20:54:13 -0500 (EST)
Received: from rhino (rhino.cisco.com [172.20.9.57])
	by kickme.cisco.com (8.9.1a/8.9.1) with ESMTP id RAA25842;
	Mon, 14 Feb 2000 17:44:07 -0800 (PST)
Received: from p7020-img-nt (fred-hm-dhcp1.cisco.com [171.69.128.116]) by rhino (SMI-8.6/CISCO.WS.1.1) with SMTP id RAA27167; Mon, 14 Feb 2000 17:58:51 -0800
Message-Id: <4.1.20000214173955.01b25e30@flipper.cisco.com>
X-Sender: fred@flipper.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Mon, 14 Feb 2000 17:53:07 -0800
To: Vernon Schryver <vjs@calcite.rhyolite.com>
From: Fred Baker <fred@cisco.com>
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
Cc: ietf@ietf.org
In-Reply-To: <200002150045.RAA08041@calcite.rhyolite.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 05:45 PM 2/14/00 -0700, Vernon Schryver wrote:
>Unless you going
>to slide the IETF the rest of the way into the ITU/IEEE/ANSI swamp, won't
>the mailing lists continue to be the only official forums for the working
>groups?  Won't the working group meetings continue to be effectively
>informal, slightly more than social gatherings? 

I realize that you have not been (ahem) a regular attendee at IETF
meetings, but in my experience this has never been the case. Yes, we do
most of our work on mailing lists, and we check meeting consensus on
mailing lists before declaring it sealed in blood. But Face to Face
meetings have always been places where high bandwidth discussions take
place to clarify and progress work which is also being done on the mailing
list. They are official meetings.

So, by the way, are interim meetings, under RFC 2418. We could discuss
major initiatives which have made effective use of them  the entire SNMP
development, the development of RSVP and Diff-serv, the development of
OSPF, and many more. PPP development has happened as much at the
interoperability workshops held by Pac Bell and the PPP Consortium as they
have at IETF meetings.

Declaring an interim meeting to make progress is a Good Thing, and we don't
see a problem with that. But we need to make sure that the process is open
to all who choose to participate, and to that end the authors of RFC 2418
specified that there needed to be AD approval, sufficient notice, a strong
agenda, and minutes just as there are at the plenary meetings. Declaring an
interim meeting for the purpose of avoiding a plenary meeting is a slap in
the face to the many engineers who come from all over to the interim and
plenary meetings that we have had for lo these 14 years. They have paid
quite a bit of money and time to be intimately involved in the process. It
would be much easier, from a planning perspective, to have the meetings in
one or two spots, as the ITU does in Geneva, but we have always worked on
an ethic that says "if I am contributing to the work, the meeting must
occasionally be near me."

One sixth or more of our contributors come from Europe. A relatively small
contingent comes from the South Pacific. Quite a large percentage come from
North America. Hence, we put about one meeting in six in Europe and most of
our meetings in North America. Is it not fair to put one meeting in 47 in
the South Pacific? And why is it not an affront to those who have
faithfully come from there, have contributed and chaired working groups
from there, to complain about doing once what they have been doing for over
a decade?



From owner-ietf-outbound@ietf.org  Mon Feb 14 21:12:21 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA00130
	for <ietf-web-archive@odin.ietf.org>; Mon, 14 Feb 2000 21:12:21 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA09736;
	Mon, 14 Feb 2000 21:10:21 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id VAA00035
	for ietf-outbound.10@ietf.org; Mon, 14 Feb 2000 21:10:03 -0500 (EST)
Received: from kickme.cisco.com (kickme.cisco.com [198.92.30.42])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29466
	for <ietf@ietf.org>; Mon, 14 Feb 2000 20:54:13 -0500 (EST)
Received: from rhino (rhino.cisco.com [172.20.9.57])
	by kickme.cisco.com (8.9.1a/8.9.1) with ESMTP id RAA25842;
	Mon, 14 Feb 2000 17:44:07 -0800 (PST)
Received: from p7020-img-nt (fred-hm-dhcp1.cisco.com [171.69.128.116]) by rhino (SMI-8.6/CISCO.WS.1.1) with SMTP id RAA27167; Mon, 14 Feb 2000 17:58:51 -0800
Message-Id: <4.1.20000214173955.01b25e30@flipper.cisco.com>
X-Sender: fred@flipper.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Mon, 14 Feb 2000 17:53:07 -0800
To: Vernon Schryver <vjs@calcite.rhyolite.com>
From: Fred Baker <fred@cisco.com>
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
Cc: ietf@ietf.org
In-Reply-To: <200002150045.RAA08041@calcite.rhyolite.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 05:45 PM 2/14/00 -0700, Vernon Schryver wrote:
>Unless you going
>to slide the IETF the rest of the way into the ITU/IEEE/ANSI swamp, won't
>the mailing lists continue to be the only official forums for the working
>groups?  Won't the working group meetings continue to be effectively
>informal, slightly more than social gatherings? 

I realize that you have not been (ahem) a regular attendee at IETF
meetings, but in my experience this has never been the case. Yes, we do
most of our work on mailing lists, and we check meeting consensus on
mailing lists before declaring it sealed in blood. But Face to Face
meetings have always been places where high bandwidth discussions take
place to clarify and progress work which is also being done on the mailing
list. They are official meetings.

So, by the way, are interim meetings, under RFC 2418. We could discuss
major initiatives which have made effective use of them  the entire SNMP
development, the development of RSVP and Diff-serv, the development of
OSPF, and many more. PPP development has happened as much at the
interoperability workshops held by Pac Bell and the PPP Consortium as they
have at IETF meetings.

Declaring an interim meeting to make progress is a Good Thing, and we don't
see a problem with that. But we need to make sure that the process is open
to all who choose to participate, and to that end the authors of RFC 2418
specified that there needed to be AD approval, sufficient notice, a strong
agenda, and minutes just as there are at the plenary meetings. Declaring an
interim meeting for the purpose of avoiding a plenary meeting is a slap in
the face to the many engineers who come from all over to the interim and
plenary meetings that we have had for lo these 14 years. They have paid
quite a bit of money and time to be intimately involved in the process. It
would be much easier, from a planning perspective, to have the meetings in
one or two spots, as the ITU does in Geneva, but we have always worked on
an ethic that says "if I am contributing to the work, the meeting must
occasionally be near me."

One sixth or more of our contributors come from Europe. A relatively small
contingent comes from the South Pacific. Quite a large percentage come from
North America. Hence, we put about one meeting in six in Europe and most of
our meetings in North America. Is it not fair to put one meeting in 47 in
the South Pacific? And why is it not an affront to those who have
faithfully come from there, have contributed and chaired working groups
from there, to complain about doing once what they have been doing for over
a decade?



From owner-ietf-outbound  Mon Feb 14 21:30:26 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA00537
	for ietf-outbound.10@ietf.org; Mon, 14 Feb 2000 21:30:03 -0500 (EST)
Received: from kuji.off.connect.com.au (kuji.off.connect.com.au [203.63.69.33])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA00474
	for <ietf@ietf.org>; Mon, 14 Feb 2000 21:28:29 -0500 (EST)
Received: from connect.com.au (mrp@localhost) by kuji.off.connect.com.au with ESMTP id MAA27866
  (8.8.8/IDA-1.6 for <ietf@ietf.org>); Tue, 15 Feb 2000 12:57:58 +1030 (CST)
Message-ID: <200002150227.MAA27866@kuji.off.connect.com.au>
To: ietf@ietf.org
Reply-to: ietf47@connect.com.au
Subject: Who is interested in wireless cards for the Adelaide IETF meeting?
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <27864.950581677.1@connect.com.au>
Date: Tue, 15 Feb 2000 12:57:57 +1030
From: Mark Prior <mrp@connect.com.au>
X-Loop: ietf@ietf.org

Lucent will be making available 802.11 DS wireless technology for the
forthcoming meeting in Adelaide. They have offered a similar deal to
Nortel at the last meeting where IETFers can loan a card for the
duration of the meeting and/or buy a card. They would like to get some
idea of how many people attending the meeting would like to take up
this offer so they can ensure they have sufficent stocks to meet the
demand.

The package being offered is a WaveLAN IEEE Turbo 11Mbps PC card for
AU$276.36 (approx US$175). Drivers are available from Lucent for (at
least) Windows 95, 98, NT, CE, 2000, MacOS and Linux.

Could people that are interested please send expressions of interest
to ietf47@connect.com.au so I can let Lucent know how many cards are
needed.

Thanks,
Mark.



From owner-ietf-outbound@ietf.org  Mon Feb 14 21:32:43 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA00709
	for <ietf-web-archive@odin.ietf.org>; Mon, 14 Feb 2000 21:32:43 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA10149;
	Mon, 14 Feb 2000 21:30:42 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id VAA00537
	for ietf-outbound.10@ietf.org; Mon, 14 Feb 2000 21:30:03 -0500 (EST)
Received: from kuji.off.connect.com.au (kuji.off.connect.com.au [203.63.69.33])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA00474
	for <ietf@ietf.org>; Mon, 14 Feb 2000 21:28:29 -0500 (EST)
Received: from connect.com.au (mrp@localhost) by kuji.off.connect.com.au with ESMTP id MAA27866
  (8.8.8/IDA-1.6 for <ietf@ietf.org>); Tue, 15 Feb 2000 12:57:58 +1030 (CST)
Message-ID: <200002150227.MAA27866@kuji.off.connect.com.au>
To: ietf@ietf.org
Reply-to: ietf47@connect.com.au
Subject: Who is interested in wireless cards for the Adelaide IETF meeting?
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <27864.950581677.1@connect.com.au>
Date: Tue, 15 Feb 2000 12:57:57 +1030
From: Mark Prior <mrp@connect.com.au>
X-Loop: ietf@ietf.org

Lucent will be making available 802.11 DS wireless technology for the
forthcoming meeting in Adelaide. They have offered a similar deal to
Nortel at the last meeting where IETFers can loan a card for the
duration of the meeting and/or buy a card. They would like to get some
idea of how many people attending the meeting would like to take up
this offer so they can ensure they have sufficent stocks to meet the
demand.

The package being offered is a WaveLAN IEEE Turbo 11Mbps PC card for
AU$276.36 (approx US$175). Drivers are available from Lucent for (at
least) Windows 95, 98, NT, CE, 2000, MacOS and Linux.

Could people that are interested please send expressions of interest
to ietf47@connect.com.au so I can let Lucent know how many cards are
needed.

Thanks,
Mark.



From owner-ietf-outbound  Mon Feb 14 22:10:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA02568
	for ietf-outbound.10@ietf.org; Mon, 14 Feb 2000 22:10:02 -0500 (EST)
Received: from senie.com (anise.senie.com [199.125.85.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02349
	for <IETF@ietf.org>; Mon, 14 Feb 2000 22:01:14 -0500 (EST)
Received: from senie.com (anise.senie.com [199.125.85.28])
	by senie.com (8.8.7/8.8.7) with ESMTP id VAA06183;
	Mon, 14 Feb 2000 21:57:26 -0500
Message-ID: <38A8C096.80DC1631@senie.com>
Date: Mon, 14 Feb 2000 21:57:26 -0500
From: Daniel Senie <dts@senie.com>
Organization: Amaranth Networks Inc.
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Charles E. Perkins" <charliep@iprg.nokia.com>
CC: Robert Elz <kre@munnari.OZ.AU>,
        "Donald E. Eastlake 3rd" <dee3@TORQUE.POTHOLE.COM>, IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
References: <15516.950526307@munnari.OZ.AU> <38A89295.F17D1153@iprg.nokia.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

"Charles E. Perkins" wrote:
> 
> Robert Elz wrote:
> 
> >                                             There's no good purpose
> > in sending packets with incorrect source addresses I can think of, and
> > stopping the practice is the basic intent of the filters.
> 
> Mobile IP would like to send out packets with the mobile node's
> home address, while it is attached to a network in a foreign
> domain.  The home address is likely to look "incorrect" from
> the standpoint of such a filter.

Mobile IP took advantage of a convenient occurrence of the Internet as
it was, believing all routing would occur based on destination address
only. That is no longer a valid assumption. In response to this changing
world, the Mobile IP folks went back to the drawing board and created
RFC 2344. I suggest folks go implement it. Tunnels are the topologially
correct answer when you're trying to do something like Mobile IP.

Mobile IP also took advantage of directed broadcast in the original
designs, though it is less clear whether anyone actually implemented
using it. See the discussion on this topic in RFC 2644 for more details
on that.

> 
> Plus I don't think the gain is worth the pain.  I'd rather see
> a technology that actually solves the problem instead of swatting
> at gnats with a sledge hammer.

Routing based on source and destination address in combination is
already a possible approach for traffic shaping and firewalling
purposes.

> 
> What if routers could preferentially keep track of things like SYN
> packets and so on for a few seconds, and we had some traceback management
> software and security associations with our neighbors enough to do
> some automatic detection?

So, you'd prefer to have the routers on the Internet be stateful
devices? Somehow, I thought we really didn't want to go there. There are
known issues with some equipment which does fast switching based on
setting up "flows." A design that several folks have come up with relies
on a general purpose processor to program "flow" information into a
silicon-assisted fabric. Such implementations suffer greatly at the
hands of a DoS attack, where flows are coming in at extremely high rate.
State isn't necessarily the answer.

> 
> It might cost 2% more for the memory buffers, geez I don't know.

The memory cost isn't the issue. You're going to pay more for a lot of
ASICs to be doing that operation at wire speed. The work to do what you
suggest adds considerably more complexity than doing filtering at wire
speeds in ASICs (a capability which is available on products shipping
today).

-- 
-----------------------------------------------------------------
Daniel Senie                                        dts@senie.com
Amaranth Networks Inc.            http://www.amaranthnetworks.com



From owner-ietf-outbound@ietf.org  Mon Feb 14 22:13:39 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02711
	for <ietf-web-archive@odin.ietf.org>; Mon, 14 Feb 2000 22:13:39 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA10967;
	Mon, 14 Feb 2000 22:11:06 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id WAA02568
	for ietf-outbound.10@ietf.org; Mon, 14 Feb 2000 22:10:02 -0500 (EST)
Received: from senie.com (anise.senie.com [199.125.85.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02349
	for <IETF@ietf.org>; Mon, 14 Feb 2000 22:01:14 -0500 (EST)
Received: from senie.com (anise.senie.com [199.125.85.28])
	by senie.com (8.8.7/8.8.7) with ESMTP id VAA06183;
	Mon, 14 Feb 2000 21:57:26 -0500
Message-ID: <38A8C096.80DC1631@senie.com>
Date: Mon, 14 Feb 2000 21:57:26 -0500
From: Daniel Senie <dts@senie.com>
Organization: Amaranth Networks Inc.
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Charles E. Perkins" <charliep@iprg.nokia.com>
CC: Robert Elz <kre@munnari.OZ.AU>,
        "Donald E. Eastlake 3rd" <dee3@TORQUE.POTHOLE.COM>, IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
References: <15516.950526307@munnari.OZ.AU> <38A89295.F17D1153@iprg.nokia.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

"Charles E. Perkins" wrote:
> 
> Robert Elz wrote:
> 
> >                                             There's no good purpose
> > in sending packets with incorrect source addresses I can think of, and
> > stopping the practice is the basic intent of the filters.
> 
> Mobile IP would like to send out packets with the mobile node's
> home address, while it is attached to a network in a foreign
> domain.  The home address is likely to look "incorrect" from
> the standpoint of such a filter.

Mobile IP took advantage of a convenient occurrence of the Internet as
it was, believing all routing would occur based on destination address
only. That is no longer a valid assumption. In response to this changing
world, the Mobile IP folks went back to the drawing board and created
RFC 2344. I suggest folks go implement it. Tunnels are the topologially
correct answer when you're trying to do something like Mobile IP.

Mobile IP also took advantage of directed broadcast in the original
designs, though it is less clear whether anyone actually implemented
using it. See the discussion on this topic in RFC 2644 for more details
on that.

> 
> Plus I don't think the gain is worth the pain.  I'd rather see
> a technology that actually solves the problem instead of swatting
> at gnats with a sledge hammer.

Routing based on source and destination address in combination is
already a possible approach for traffic shaping and firewalling
purposes.

> 
> What if routers could preferentially keep track of things like SYN
> packets and so on for a few seconds, and we had some traceback management
> software and security associations with our neighbors enough to do
> some automatic detection?

So, you'd prefer to have the routers on the Internet be stateful
devices? Somehow, I thought we really didn't want to go there. There are
known issues with some equipment which does fast switching based on
setting up "flows." A design that several folks have come up with relies
on a general purpose processor to program "flow" information into a
silicon-assisted fabric. Such implementations suffer greatly at the
hands of a DoS attack, where flows are coming in at extremely high rate.
State isn't necessarily the answer.

> 
> It might cost 2% more for the memory buffers, geez I don't know.

The memory cost isn't the issue. You're going to pay more for a lot of
ASICs to be doing that operation at wire speed. The work to do what you
suggest adds considerably more complexity than doing filtering at wire
speeds in ASICs (a capability which is available on products shipping
today).

-- 
-----------------------------------------------------------------
Daniel Senie                                        dts@senie.com
Amaranth Networks Inc.            http://www.amaranthnetworks.com



From owner-ietf-outbound  Mon Feb 14 22:20:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA02807
	for ietf-outbound.10@ietf.org; Mon, 14 Feb 2000 22:20:02 -0500 (EST)
Received: from senie.com (anise.senie.com [199.125.85.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02433
	for <IETF@ietf.org>; Mon, 14 Feb 2000 22:05:14 -0500 (EST)
Received: from senie.com (anise.senie.com [199.125.85.28])
	by senie.com (8.8.7/8.8.7) with ESMTP id WAA06299;
	Mon, 14 Feb 2000 22:05:12 -0500
Message-ID: <38A8C268.33BAF536@senie.com>
Date: Mon, 14 Feb 2000 22:05:12 -0500
From: Daniel Senie <dts@senie.com>
Organization: Amaranth Networks Inc.
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Phil Karn <karn@QUALCOMM.COM>
CC: lists.anders@feder.dk, IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
References: <200002150004.QAA04489@servo.qualcomm.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Phil Karn wrote:
> 
> >tomorrow demands. And, agreed,  bogus source IPs _does_ at present time
> >look like nothing but the devils work. But in, say, 10 years a new flashy
> >techology could be requiring that you have the ability to stamp packets with
> >other IPs than your own. Unfortunately, back in year 2000, somebody put in
> 
> There already are some perfectly legitimate reasons to send packets
> with "alien" IP source addresses. Mobile IP is the best example, but
> various virtual private networking schemes also do this. For example,
> I have a VPN set up over my cable modem so I can have a block of
> static IP addresses for my home network. I had to do some work to
> evade the $#@!! source IP address ingress filtering in my cable
> network. I do it by tunneling the upstream packets through a machine
> at work.

Yes, and you chose the CORRECT solution. Think about it... VPN in most
cases also means encryption, and at that probably back to a central
site.

Gabriel wrote RFC 2344 for reverse tunnels, and it does essentially what
you did.

> 
> Being forced to tunnel not only increases the size of each packet, but
> also entails suboptimum routing and reliance on yet more network
> elements.  I use the new Linux policy routing mechanisms to tunnel
> only those packets that have to be tunneled, which helps. But it would
> sure be nice if I didn't have to tunnel my outbound packets at all.

Sorry. You're at the point where technology meets policy. Fact is, your
host identifier in the IP stack is the source IP address. Enforcing the
validity of that identifier has become necessary.

> 
> Source address ingress filtering is one of those ideas that seems like
> a good one when you first think about it, but it just doesn't pan out.
> It interferes with some perfectly legitimate activities, it doesn't
> really stop the bad guys, and it deflects attention away from the real
> solutions.

The case for "legitimate use" of source spoofing has not been
sufficiently made. Operational reality is such that it's not
sustainable.



-- 
-----------------------------------------------------------------
Daniel Senie                                        dts@senie.com
Amaranth Networks Inc.            http://www.amaranthnetworks.com



From owner-ietf-outbound@ietf.org  Mon Feb 14 22:22:48 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02919
	for <ietf-web-archive@odin.ietf.org>; Mon, 14 Feb 2000 22:22:48 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA11128;
	Mon, 14 Feb 2000 22:20:47 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id WAA02807
	for ietf-outbound.10@ietf.org; Mon, 14 Feb 2000 22:20:02 -0500 (EST)
Received: from senie.com (anise.senie.com [199.125.85.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02433
	for <IETF@ietf.org>; Mon, 14 Feb 2000 22:05:14 -0500 (EST)
Received: from senie.com (anise.senie.com [199.125.85.28])
	by senie.com (8.8.7/8.8.7) with ESMTP id WAA06299;
	Mon, 14 Feb 2000 22:05:12 -0500
Message-ID: <38A8C268.33BAF536@senie.com>
Date: Mon, 14 Feb 2000 22:05:12 -0500
From: Daniel Senie <dts@senie.com>
Organization: Amaranth Networks Inc.
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Phil Karn <karn@QUALCOMM.COM>
CC: lists.anders@feder.dk, IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
References: <200002150004.QAA04489@servo.qualcomm.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Phil Karn wrote:
> 
> >tomorrow demands. And, agreed,  bogus source IPs _does_ at present time
> >look like nothing but the devils work. But in, say, 10 years a new flashy
> >techology could be requiring that you have the ability to stamp packets with
> >other IPs than your own. Unfortunately, back in year 2000, somebody put in
> 
> There already are some perfectly legitimate reasons to send packets
> with "alien" IP source addresses. Mobile IP is the best example, but
> various virtual private networking schemes also do this. For example,
> I have a VPN set up over my cable modem so I can have a block of
> static IP addresses for my home network. I had to do some work to
> evade the $#@!! source IP address ingress filtering in my cable
> network. I do it by tunneling the upstream packets through a machine
> at work.

Yes, and you chose the CORRECT solution. Think about it... VPN in most
cases also means encryption, and at that probably back to a central
site.

Gabriel wrote RFC 2344 for reverse tunnels, and it does essentially what
you did.

> 
> Being forced to tunnel not only increases the size of each packet, but
> also entails suboptimum routing and reliance on yet more network
> elements.  I use the new Linux policy routing mechanisms to tunnel
> only those packets that have to be tunneled, which helps. But it would
> sure be nice if I didn't have to tunnel my outbound packets at all.

Sorry. You're at the point where technology meets policy. Fact is, your
host identifier in the IP stack is the source IP address. Enforcing the
validity of that identifier has become necessary.

> 
> Source address ingress filtering is one of those ideas that seems like
> a good one when you first think about it, but it just doesn't pan out.
> It interferes with some perfectly legitimate activities, it doesn't
> really stop the bad guys, and it deflects attention away from the real
> solutions.

The case for "legitimate use" of source spoofing has not been
sufficiently made. Operational reality is such that it's not
sustainable.



-- 
-----------------------------------------------------------------
Daniel Senie                                        dts@senie.com
Amaranth Networks Inc.            http://www.amaranthnetworks.com



From owner-ietf-outbound  Mon Feb 14 22:30:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA03067
	for ietf-outbound.10@ietf.org; Mon, 14 Feb 2000 22:30:02 -0500 (EST)
Received: from lint.cisco.com (lint.cisco.com [171.68.224.209])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02777
	for <ietf@ietf.org>; Mon, 14 Feb 2000 22:19:06 -0500 (EST)
Received: from eleardell (elear-isdn.cisco.com [171.70.252.70]) by lint.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with SMTP id TAA06575; Mon, 14 Feb 2000 19:18:35 -0800 (PST)
Message-ID: <016401bf7763$4b82e380$0300000a@cisco.com>
From: "Eliot Lear" <lear@cisco.com>
To: "Stephen Kent" <kent@bbn.com>
Cc: <ietf@ietf.org>
Subject: RE: Internet SYN Flooding, spoofing attacks
Date: Mon, 14 Feb 2000 19:18:10 -0800
Organization: Cisco Systems
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 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Steve,

Let's be clear: a DOS attack is something the end point itself can do
very little to prevent, since it usually fails or succeeds upstream of
that end point.  Therefore, the end point relies on its upstream ISPs to
"do the right thing" and indeed, each of those ISPs relies on other ISPs
to similarly filter.  Each point can mitigate the damage to the point
where in sum these attacks become ineffective.  Each RPF check can
remove bad packets.  Each violated ACL can remove and LOG the bad
packets.  These are the best controls available today.  Shall we not use
them?

Also, we raise the bar from some kid injecting packets to someone
breaking into an ISP, a more difficult challenge (at least a level 3
attack on my Dungeons and Dragons guide of Hackers ;-).


----- Original Message -----
From: Stephen Kent <kent@bbn.com>
Newsgroups: cisco.external.ietf
Sent: Saturday, February 12, 2000 1:55 PM
Subject: Re: Internet SYN Flooding, spoofing attacks


> Paul,
>
> >
> >>When one suggests that a first tier ISP would not need to filter
> >>traffic from down stream providers, because IF they do the
filtering,
> >>then the problem will not arise via those links, one is suggesting
> >>precisely this sort of model.
> >
> >You're approaching this from the wrong perspective, in my opinion.
> >
> >There is no assumption implied that RFC2267 filtering is needed --
> >it is required. What good is it if one or two or 300 people do
> >it, and another 157,000 do not?
> >
> >Well, there is a little good, but the more people that do it, the
> >better off we all are.
> >
> >The bottom line here is that RFC2267-style filtering (or unicast
> >RPF checks, or what have you) stops spoofed source address packets
> >from being transmitted into the Internet from places they have no
> >business being originated from to begin with.
> >
> >In even the worst case, those conscientious network admins that
> >_do_ do it can say without remorse that they are doing their part,
> >and can at least be assured that DoS attacks using spoofed source
> >addresses are not being originated from their customer base.
> >
> >And this is a Bad Thing?
>
> it is a bad thing if one bases defenses on the assumption that ALL
> the access points into the Internet will perform such filtering, and
> will do it consistently.  Even if all ISPs, and down stream providers
> performed the filtering, there is no guarantee that attackers could
> not circumvent the filter controls, either through direct attack on
> the routers, or through indirect attack on the management stations
> used to configure them.  I'm just saying that while edge filtering is
> potentially useful, it would not be a good idea to assume that it
> will be effective.
>
> >
> >>Edge filtering would often be helpful, but it is not a panacea, as
> >>pointed out by others in regard to the current set of attacks, nor
is
> >>the performance impact trivial with most current routers.
> >
> >It is negligible at the edge in most cases, but you really need to
> >define "edge" a little better. In some cases, it is very low speed
> >links, in others it is an OC-12.
>
> In talking with the operations folks at GTE-I, they expressed concern
> over the performance hit for many of their edge routers, based on the
> number of subscribers involved and other configuration
> characteristics.
>
> >
> >>Because
> >>most routers are optimized for transit traffic forwarding, the
> >>ability to filter on the interface cards is limited, as I'm sure you
> >>know.
> >
> >No, I don't know that at all. _Backbone_routers_ are optimized for
> >packet forwarding -- I do know that.
>
> I would state that devices that examine IP headers and make routing
> decisions entirely on interface cards are optimized for traffic
> forwarding, vs. firewall-style devices that focus on header
> examination and ACL checking, and which typically do this by passing
> a packet through a general purpose processor, vs. in I/O interfaces.
> But, these are just generalizations.
>
> >
> >>  Also, several of the distributed DoS attacks we are seeing do
> >>not use fake source addresses from other sites, so simple filtering
> >>of the sort proposed in 2267 would not be effective in these cases.
> >
> >Again, you're missing the point.
> >
> >If attackers are limited to launching DoS attacks using traceable
> >addresses, then not only can their zombies be traced & found, but
> >so can their controller (the perpetrator himself). Of this, make no
> >mistake.
>
> Not necessarily. The traffic from a controller to the clients may be
> sufficiently offset in time as to make tracing back to the controller
> hard.  I agree that tracing to the traffic sources (or at least to
> the sites where the traffic sources are) would be easier if edge
> filtering were in place, and if it were not compromised.
>
> >
> >>Finally, I am aware of new routers for which this sort of filtering
> >>would be child's play, but they are not yet deployed.  One ought not
> >>suggest that edge filtering is not being applied simply because of
> >>laziness on the part of ISPs.
> >
> >Steve, you said that -- I didn't. I think ISP's will do what their
> >customers pay them to do.
>
> ISPs do what they perceive is appropriate to maintain and gain market
> share, consistent with their cost models and router product
> availability. Different ISPs have different ideas of how to deploy
> routers and switches to aggregate traffic, which are driven by their
> traffic models, by economics, and by vendors.
>
> Note that this is an international problem, not just a domestic one.
> Our operations folks tell me that many attacks are traceable to
> foreign sources, where the ability to ensure adherence to policies
> such as edge filtering is rather difficult.  Also, from a national
> security perspective, one would hardly rely on other countries
> enforcing such policies in their ISP domains.  That's why I think the
> best, long term approach to these problems requires a combination of
> improved host security and monitoring for attacks near the hosts
> (both appropriate measures when the hosts are servers with a vested
> interest in maintaining availability), plus rapid, automated response
> to detected attacks, and an ability to activate and adjust filters at
> all ISP interfaces, not just at subscriber interfaces.  This
> combination of measures does not rely on every ISP in the world doing
> the right thing, although it would benefit from such behavior.  It
> embodies a notion of self-protection, both at the subscriber and ISP
> levels, in support of the principle of least privilege.
>
> Steve
>



From owner-ietf-outbound@ietf.org  Mon Feb 14 22:32:55 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA03928
	for <ietf-web-archive@odin.ietf.org>; Mon, 14 Feb 2000 22:32:55 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA11346;
	Mon, 14 Feb 2000 22:30:57 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id WAA03067
	for ietf-outbound.10@ietf.org; Mon, 14 Feb 2000 22:30:02 -0500 (EST)
Received: from lint.cisco.com (lint.cisco.com [171.68.224.209])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02777
	for <ietf@ietf.org>; Mon, 14 Feb 2000 22:19:06 -0500 (EST)
Received: from eleardell (elear-isdn.cisco.com [171.70.252.70]) by lint.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with SMTP id TAA06575; Mon, 14 Feb 2000 19:18:35 -0800 (PST)
Message-ID: <016401bf7763$4b82e380$0300000a@cisco.com>
From: "Eliot Lear" <lear@cisco.com>
To: "Stephen Kent" <kent@bbn.com>
Cc: <ietf@ietf.org>
Subject: RE: Internet SYN Flooding, spoofing attacks
Date: Mon, 14 Feb 2000 19:18:10 -0800
Organization: Cisco Systems
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 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Steve,

Let's be clear: a DOS attack is something the end point itself can do
very little to prevent, since it usually fails or succeeds upstream of
that end point.  Therefore, the end point relies on its upstream ISPs to
"do the right thing" and indeed, each of those ISPs relies on other ISPs
to similarly filter.  Each point can mitigate the damage to the point
where in sum these attacks become ineffective.  Each RPF check can
remove bad packets.  Each violated ACL can remove and LOG the bad
packets.  These are the best controls available today.  Shall we not use
them?

Also, we raise the bar from some kid injecting packets to someone
breaking into an ISP, a more difficult challenge (at least a level 3
attack on my Dungeons and Dragons guide of Hackers ;-).


----- Original Message -----
From: Stephen Kent <kent@bbn.com>
Newsgroups: cisco.external.ietf
Sent: Saturday, February 12, 2000 1:55 PM
Subject: Re: Internet SYN Flooding, spoofing attacks


> Paul,
>
> >
> >>When one suggests that a first tier ISP would not need to filter
> >>traffic from down stream providers, because IF they do the
filtering,
> >>then the problem will not arise via those links, one is suggesting
> >>precisely this sort of model.
> >
> >You're approaching this from the wrong perspective, in my opinion.
> >
> >There is no assumption implied that RFC2267 filtering is needed --
> >it is required. What good is it if one or two or 300 people do
> >it, and another 157,000 do not?
> >
> >Well, there is a little good, but the more people that do it, the
> >better off we all are.
> >
> >The bottom line here is that RFC2267-style filtering (or unicast
> >RPF checks, or what have you) stops spoofed source address packets
> >from being transmitted into the Internet from places they have no
> >business being originated from to begin with.
> >
> >In even the worst case, those conscientious network admins that
> >_do_ do it can say without remorse that they are doing their part,
> >and can at least be assured that DoS attacks using spoofed source
> >addresses are not being originated from their customer base.
> >
> >And this is a Bad Thing?
>
> it is a bad thing if one bases defenses on the assumption that ALL
> the access points into the Internet will perform such filtering, and
> will do it consistently.  Even if all ISPs, and down stream providers
> performed the filtering, there is no guarantee that attackers could
> not circumvent the filter controls, either through direct attack on
> the routers, or through indirect attack on the management stations
> used to configure them.  I'm just saying that while edge filtering is
> potentially useful, it would not be a good idea to assume that it
> will be effective.
>
> >
> >>Edge filtering would often be helpful, but it is not a panacea, as
> >>pointed out by others in regard to the current set of attacks, nor
is
> >>the performance impact trivial with most current routers.
> >
> >It is negligible at the edge in most cases, but you really need to
> >define "edge" a little better. In some cases, it is very low speed
> >links, in others it is an OC-12.
>
> In talking with the operations folks at GTE-I, they expressed concern
> over the performance hit for many of their edge routers, based on the
> number of subscribers involved and other configuration
> characteristics.
>
> >
> >>Because
> >>most routers are optimized for transit traffic forwarding, the
> >>ability to filter on the interface cards is limited, as I'm sure you
> >>know.
> >
> >No, I don't know that at all. _Backbone_routers_ are optimized for
> >packet forwarding -- I do know that.
>
> I would state that devices that examine IP headers and make routing
> decisions entirely on interface cards are optimized for traffic
> forwarding, vs. firewall-style devices that focus on header
> examination and ACL checking, and which typically do this by passing
> a packet through a general purpose processor, vs. in I/O interfaces.
> But, these are just generalizations.
>
> >
> >>  Also, several of the distributed DoS attacks we are seeing do
> >>not use fake source addresses from other sites, so simple filtering
> >>of the sort proposed in 2267 would not be effective in these cases.
> >
> >Again, you're missing the point.
> >
> >If attackers are limited to launching DoS attacks using traceable
> >addresses, then not only can their zombies be traced & found, but
> >so can their controller (the perpetrator himself). Of this, make no
> >mistake.
>
> Not necessarily. The traffic from a controller to the clients may be
> sufficiently offset in time as to make tracing back to the controller
> hard.  I agree that tracing to the traffic sources (or at least to
> the sites where the traffic sources are) would be easier if edge
> filtering were in place, and if it were not compromised.
>
> >
> >>Finally, I am aware of new routers for which this sort of filtering
> >>would be child's play, but they are not yet deployed.  One ought not
> >>suggest that edge filtering is not being applied simply because of
> >>laziness on the part of ISPs.
> >
> >Steve, you said that -- I didn't. I think ISP's will do what their
> >customers pay them to do.
>
> ISPs do what they perceive is appropriate to maintain and gain market
> share, consistent with their cost models and router product
> availability. Different ISPs have different ideas of how to deploy
> routers and switches to aggregate traffic, which are driven by their
> traffic models, by economics, and by vendors.
>
> Note that this is an international problem, not just a domestic one.
> Our operations folks tell me that many attacks are traceable to
> foreign sources, where the ability to ensure adherence to policies
> such as edge filtering is rather difficult.  Also, from a national
> security perspective, one would hardly rely on other countries
> enforcing such policies in their ISP domains.  That's why I think the
> best, long term approach to these problems requires a combination of
> improved host security and monitoring for attacks near the hosts
> (both appropriate measures when the hosts are servers with a vested
> interest in maintaining availability), plus rapid, automated response
> to detected attacks, and an ability to activate and adjust filters at
> all ISP interfaces, not just at subscriber interfaces.  This
> combination of measures does not rely on every ISP in the world doing
> the right thing, although it would benefit from such behavior.  It
> embodies a notion of self-protection, both at the subscriber and ISP
> levels, in support of the principle of least privilege.
>
> Steve
>



From owner-ietf-outbound  Mon Feb 14 22:40:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA04264
	for ietf-outbound.10@ietf.org; Mon, 14 Feb 2000 22:40:03 -0500 (EST)
Received: from mailman.cisco.com (mailman.cisco.com [171.68.225.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02959
	for <IETF@ietf.org>; Mon, 14 Feb 2000 22:25:06 -0500 (EST)
Received: from bigger-dawgs (pferguso-isdn.cisco.com [171.70.114.134]) by mailman.cisco.com (8.8.8+Sun/CISCO.SERVER.1.2) with ESMTP id TAA13143; Mon, 14 Feb 2000 19:24:36 -0800 (PST)
Message-Id: <4.2.2.20000214222414.00a65b00@lint.cisco.com>
X-Sender: pferguso@lint.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Mon, 14 Feb 2000 22:24:28 -0500
To: IETF@ietf.org
From: Paul Ferguson <ferguson@cisco.com>
Subject: DoS (Denial of Service) Attack resource page
Cc: dts@senie.com
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

Folks,

Dan Senie and I got tired of keeping separate browser
bookmarks on a myriad of DoS Attack technical info, and
so we decided to slap together a web page which contains
some "good technical resources" on these DoS attacks:

  http://www.denialinfo.com/

Of course, it is pretty raw right now, but we'll make it
easier on the eyes over time, as well as add more content.
In fact, I think the page counter on the main page is broken
right now, but works on the mirror. Minor problems (it's the
content that counts, right?).

In any event, this is where you come in -- we would like to
solicit the community at-large to send along pertinent pointers
to any additional resources which we may have overlooked, or
that we just didn't know about in the first place.

Contact info is available on the web page, and so is a
URL for a mirror.

Thanks,

- paul and dan

ps. Thanks much to Kevin Siers, political cartoonist at the
Charlotte Observer, for letting use his awesome cartoon. ;-)



From owner-ietf-outbound@ietf.org  Mon Feb 14 22:42:35 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04493
	for <ietf-web-archive@odin.ietf.org>; Mon, 14 Feb 2000 22:42:35 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA11493;
	Mon, 14 Feb 2000 22:40:35 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id WAA04264
	for ietf-outbound.10@ietf.org; Mon, 14 Feb 2000 22:40:03 -0500 (EST)
Received: from mailman.cisco.com (mailman.cisco.com [171.68.225.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02959
	for <IETF@ietf.org>; Mon, 14 Feb 2000 22:25:06 -0500 (EST)
Received: from bigger-dawgs (pferguso-isdn.cisco.com [171.70.114.134]) by mailman.cisco.com (8.8.8+Sun/CISCO.SERVER.1.2) with ESMTP id TAA13143; Mon, 14 Feb 2000 19:24:36 -0800 (PST)
Message-Id: <4.2.2.20000214222414.00a65b00@lint.cisco.com>
X-Sender: pferguso@lint.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Mon, 14 Feb 2000 22:24:28 -0500
To: IETF@ietf.org
From: Paul Ferguson <ferguson@cisco.com>
Subject: DoS (Denial of Service) Attack resource page
Cc: dts@senie.com
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

Folks,

Dan Senie and I got tired of keeping separate browser
bookmarks on a myriad of DoS Attack technical info, and
so we decided to slap together a web page which contains
some "good technical resources" on these DoS attacks:

  http://www.denialinfo.com/

Of course, it is pretty raw right now, but we'll make it
easier on the eyes over time, as well as add more content.
In fact, I think the page counter on the main page is broken
right now, but works on the mirror. Minor problems (it's the
content that counts, right?).

In any event, this is where you come in -- we would like to
solicit the community at-large to send along pertinent pointers
to any additional resources which we may have overlooked, or
that we just didn't know about in the first place.

Contact info is available on the web page, and so is a
URL for a mirror.

Thanks,

- paul and dan

ps. Thanks much to Kevin Siers, political cartoonist at the
Charlotte Observer, for letting use his awesome cartoon. ;-)



From owner-ietf-outbound  Mon Feb 14 22:50:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id WAA04607
	for ietf-outbound.10@ietf.org; Mon, 14 Feb 2000 22:50:02 -0500 (EST)
Received: from thorn.blackrose.org (thorn.blackrose.org [204.212.44.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04168
	for <ietf@ietf.org>; Mon, 14 Feb 2000 22:36:40 -0500 (EST)
Received: (from dorian@localhost)
	by thorn.blackrose.org (8.9.3/8.9.3) id WAA06452;
	Mon, 14 Feb 2000 22:31:17 -0500 (EST)
Date: Mon, 14 Feb 2000 22:31:16 -0500
From: Dorian Kim <dorian@BLACKROSE.ORG>
To: ietf47@connect.com.au
Cc: ietf@ietf.org
Subject: Re: Who is interested in wireless cards for the Adelaide IETF meeting?
Message-ID: <20000214223116.C1640@blackrose.org>
Mail-Followup-To: ietf47@connect.com.au, ietf@ietf.org
References: <200002150227.MAA27866@kuji.off.connect.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
In-Reply-To: <200002150227.MAA27866@kuji.off.connect.com.au>
X-Loop: ietf@ietf.org

On Tue, Feb 15, 2000 at 12:57:57PM +1030, Mark Prior wrote:
> The package being offered is a WaveLAN IEEE Turbo 11Mbps PC card for
> AU$276.36 (approx US$175). Drivers are available from Lucent for (at
> least) Windows 95, 98, NT, CE, 2000, MacOS and Linux.
> 
> Could people that are interested please send expressions of interest
> to ietf47@connect.com.au so I can let Lucent know how many cards are
> needed.

I'd be interested in borrowing a pair of wavelan cards.

-dorian



From owner-ietf-outbound@ietf.org  Mon Feb 14 22:52:22 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04682
	for <ietf-web-archive@odin.ietf.org>; Mon, 14 Feb 2000 22:52:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA11680;
	Mon, 14 Feb 2000 22:50:24 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id WAA04607
	for ietf-outbound.10@ietf.org; Mon, 14 Feb 2000 22:50:02 -0500 (EST)
Received: from thorn.blackrose.org (thorn.blackrose.org [204.212.44.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04168
	for <ietf@ietf.org>; Mon, 14 Feb 2000 22:36:40 -0500 (EST)
Received: (from dorian@localhost)
	by thorn.blackrose.org (8.9.3/8.9.3) id WAA06452;
	Mon, 14 Feb 2000 22:31:17 -0500 (EST)
Date: Mon, 14 Feb 2000 22:31:16 -0500
From: Dorian Kim <dorian@BLACKROSE.ORG>
To: ietf47@connect.com.au
Cc: ietf@ietf.org
Subject: Re: Who is interested in wireless cards for the Adelaide IETF meeting?
Message-ID: <20000214223116.C1640@blackrose.org>
Mail-Followup-To: ietf47@connect.com.au, ietf@ietf.org
References: <200002150227.MAA27866@kuji.off.connect.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
In-Reply-To: <200002150227.MAA27866@kuji.off.connect.com.au>
X-Loop: ietf@ietf.org

On Tue, Feb 15, 2000 at 12:57:57PM +1030, Mark Prior wrote:
> The package being offered is a WaveLAN IEEE Turbo 11Mbps PC card for
> AU$276.36 (approx US$175). Drivers are available from Lucent for (at
> least) Windows 95, 98, NT, CE, 2000, MacOS and Linux.
> 
> Could people that are interested please send expressions of interest
> to ietf47@connect.com.au so I can let Lucent know how many cards are
> needed.

I'd be interested in borrowing a pair of wavelan cards.

-dorian



From owner-ietf-outbound  Mon Feb 14 23:00:26 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA04828
	for ietf-outbound.10@ietf.org; Mon, 14 Feb 2000 23:00:02 -0500 (EST)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04199
	for <ietf@ietf.org>; Mon, 14 Feb 2000 22:37:48 -0500 (EST)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id UAA13992
	for ietf@ietf.org  env-from <vjs>;
	Mon, 14 Feb 2000 20:37:49 -0700 (MST)
Date: Mon, 14 Feb 2000 20:37:49 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200002150337.UAA13992@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
X-Loop: ietf@ietf.org

> From: "Steven M. Bellovin" <smb@research.att.com>

> ...
> > I'm not a lawyer, but that sounds like it might conflict with the U.S.
> > Constitution's provisions concerning freedom of assembly.
>
> (a) The U.S. constitution applies to the Federal government (and sometimes to 
> the state governments); it does not apply to private groups.

How arms-length is the connection between the IETF and the Federal
government?  No more NFS money, but what about the ITU entanglements?
Could Civil Service employees find it hard to get travel requests approved
for attending meetings of an outfit that gets carried away in its rules
and regulations on who can talk to whom?

> (b) No one ever said that these folks can't meet; they just can't do it under 
> the imprimatur of the IETF. 

I read the dictum as stronger than that.  Didn't it say something
about prohibiting meetings that are nominally not WG meetings for
the purpose of subverting RFC 2418?  That's why I quoted

}                                                 or otherwise 
}   labelled to distinguish them from official working group meetings.

That's the part that I don't see as enforcable or wise, although I
sympathize with the motivation.


> ...
> The point is that some things are better accomplished in a high-bandwidth 
> environment.  

Yes, that's often true, but the talk of "high-bandwidth" has always been
exaggerated.  As I've said, I've never attended an IETF meeting, but
I've read an awful lot of minutes over the last >dozen years.  I haven't
read many that showed evidence effective use of that high bandwidth.
(Perhaps I'm too unimpressed by simply letting people have their say
before continuing with what was inevitable.)

> >                                                      ...   If the IETF
> > did honestly aspire to be an international organization, it would need
> > the characteristics of the ITU (e.g. translators and high prices for
> > documents). ...

> I'm afraid I don't follow the logic of your penultimate sententce.  The 
> current schedule has about 1 meeting out of 3 outside of North America.

The locations of meetings do not make the IETF international any more than
Congressional junkets do the same for Congress.  (That there is no need
to specify which congress I'm talking about is emblematic of the reality
that contradicts the politically correct posturing.)

The U.N. and the ITU are international organizations.  I've attended
as many meetings of them as of the IETF, so maybe my distinct
impression that they do things differently than the IETF is mistaken.
Let's see, how many RFC's are not in English?  How many WG meetings
or mailinglists?

That the IETF is de facto an U.S. outfit is not by itself a bad thing.
There are and for centuries have been many organizations in many places
that are not really international, but that welcome distant participants.
It is bad to refuse to call a "digging implement adapted for being pushed
into the ground with the foot" a spade.


] From fred@cisco.com Mon Feb 14 18:54:53 2000

]                                                        ...   Yes, we do
] most of our work on mailing lists, and we check meeting consensus on
] mailing lists before declaring it sealed in blood. But Face to Face
] meetings have always been places where high bandwidth discussions take
] place to clarify and progress work which is also being done on the mailing
] list. They are official meetings.

"High-bandwidth" does not need official sanction.  You can have productive
technical discussions without any official sanction, and usually better
without the burdens of officialness.  What is the difference between
"official but nothing is signed in blood" and "where things are signed in
blood"?  If nothing can be finally decided (i.e. signed in blood), what
is the substance, of "official" besides ensuring that accountants accept
expense reports?

] So, by the way, are interim meetings, under RFC 2418. We could discuss
] major initiatives which have made effective use of them  the entire SNMP
] development, the development of RSVP and Diff-serv, the development of
] OSPF, and many more. PPP development has happened as much at the
] interoperability workshops held by Pac Bell and the PPP Consortium as they
] have at IETF meetings.

Those are good examples of the distinction between engineering and official
meetings.  The PPP development I saw at Pac Bell's San Ramon facility was
a matter individuals talking semi-privately.  The semi-formal discussions
at the ends of the days announced but did not decide anything.  Note also
that at least some of those meetings did not have any IETF sanction.

I wonder if the uglier parts of the SNMP saga would not have come out far
better without one or two of the official IETF WG meetings.


]                                                           ...  Declaring an
] interim meeting for the purpose of avoiding a plenary meeting is a slap in
] the face ...

That's certainly true, but I don't see how you're going to fix that problem
without killing the mailinglists.  Working groups that fail to have quorums
at official meetings can and will still get work done.  As I know you know
too well, individuals will meet with or without IETF sanction, write
drafts, and the WG can and will progress (or not) regardless.

]                                         ...  but we have always worked on
] an ethic that says "if I am contributing to the work, the meeting must
] occasionally be near me."

That's not bad, especially for those with deep corporate or government
pockets to pay for travel.  It is good politics and fun.  However, very
little technical work is ever done in any committee meeting of a few hours,
no matter where it is held or with what official sanction.

] One sixth or more of our contributors come from Europe. A relatively small
] contingent comes from the South Pacific. Quite a large percentage come from
] North America. Hence, we put about one meeting in six in Europe and most of
] our meetings in North America. Is it not fair to put one meeting in 47 in
] the South Pacific? And why is it not an affront to those who have
] faithfully come from there, have contributed and chaired working groups
] from there, to complain about doing once what they have been doing for over
] a decade?

It's impossible to disagree with that.  I assume it's intended to
show that the IETF is an "international organization," but it does
not convince me.

Speaking of slaps in faces, I wonder if I were not a U.S. citizen if I
wouldn't feel some sting from the continual claims by the IETF that it is
an international organzation.  For example, how many AD's and IAB members
have not been U.S. residents?  Of those few that haven't been, how many
could not have "passed" as U.S. residents?--at least in email, none that
I can recall.  (I hope they'll they'll take that as a compliment on their
social skills instead of an affront to their national pride.)


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound@ietf.org  Mon Feb 14 23:02:53 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA04975
	for <ietf-web-archive@odin.ietf.org>; Mon, 14 Feb 2000 23:02:53 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA11966;
	Mon, 14 Feb 2000 23:00:53 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id XAA04828
	for ietf-outbound.10@ietf.org; Mon, 14 Feb 2000 23:00:02 -0500 (EST)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04199
	for <ietf@ietf.org>; Mon, 14 Feb 2000 22:37:48 -0500 (EST)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id UAA13992
	for ietf@ietf.org  env-from <vjs>;
	Mon, 14 Feb 2000 20:37:49 -0700 (MST)
Date: Mon, 14 Feb 2000 20:37:49 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200002150337.UAA13992@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
X-Loop: ietf@ietf.org

> From: "Steven M. Bellovin" <smb@research.att.com>

> ...
> > I'm not a lawyer, but that sounds like it might conflict with the U.S.
> > Constitution's provisions concerning freedom of assembly.
>
> (a) The U.S. constitution applies to the Federal government (and sometimes to 
> the state governments); it does not apply to private groups.

How arms-length is the connection between the IETF and the Federal
government?  No more NFS money, but what about the ITU entanglements?
Could Civil Service employees find it hard to get travel requests approved
for attending meetings of an outfit that gets carried away in its rules
and regulations on who can talk to whom?

> (b) No one ever said that these folks can't meet; they just can't do it under 
> the imprimatur of the IETF. 

I read the dictum as stronger than that.  Didn't it say something
about prohibiting meetings that are nominally not WG meetings for
the purpose of subverting RFC 2418?  That's why I quoted

}                                                 or otherwise 
}   labelled to distinguish them from official working group meetings.

That's the part that I don't see as enforcable or wise, although I
sympathize with the motivation.


> ...
> The point is that some things are better accomplished in a high-bandwidth 
> environment.  

Yes, that's often true, but the talk of "high-bandwidth" has always been
exaggerated.  As I've said, I've never attended an IETF meeting, but
I've read an awful lot of minutes over the last >dozen years.  I haven't
read many that showed evidence effective use of that high bandwidth.
(Perhaps I'm too unimpressed by simply letting people have their say
before continuing with what was inevitable.)

> >                                                      ...   If the IETF
> > did honestly aspire to be an international organization, it would need
> > the characteristics of the ITU (e.g. translators and high prices for
> > documents). ...

> I'm afraid I don't follow the logic of your penultimate sententce.  The 
> current schedule has about 1 meeting out of 3 outside of North America.

The locations of meetings do not make the IETF international any more than
Congressional junkets do the same for Congress.  (That there is no need
to specify which congress I'm talking about is emblematic of the reality
that contradicts the politically correct posturing.)

The U.N. and the ITU are international organizations.  I've attended
as many meetings of them as of the IETF, so maybe my distinct
impression that they do things differently than the IETF is mistaken.
Let's see, how many RFC's are not in English?  How many WG meetings
or mailinglists?

That the IETF is de facto an U.S. outfit is not by itself a bad thing.
There are and for centuries have been many organizations in many places
that are not really international, but that welcome distant participants.
It is bad to refuse to call a "digging implement adapted for being pushed
into the ground with the foot" a spade.


] From fred@cisco.com Mon Feb 14 18:54:53 2000

]                                                        ...   Yes, we do
] most of our work on mailing lists, and we check meeting consensus on
] mailing lists before declaring it sealed in blood. But Face to Face
] meetings have always been places where high bandwidth discussions take
] place to clarify and progress work which is also being done on the mailing
] list. They are official meetings.

"High-bandwidth" does not need official sanction.  You can have productive
technical discussions without any official sanction, and usually better
without the burdens of officialness.  What is the difference between
"official but nothing is signed in blood" and "where things are signed in
blood"?  If nothing can be finally decided (i.e. signed in blood), what
is the substance, of "official" besides ensuring that accountants accept
expense reports?

] So, by the way, are interim meetings, under RFC 2418. We could discuss
] major initiatives which have made effective use of them  the entire SNMP
] development, the development of RSVP and Diff-serv, the development of
] OSPF, and many more. PPP development has happened as much at the
] interoperability workshops held by Pac Bell and the PPP Consortium as they
] have at IETF meetings.

Those are good examples of the distinction between engineering and official
meetings.  The PPP development I saw at Pac Bell's San Ramon facility was
a matter individuals talking semi-privately.  The semi-formal discussions
at the ends of the days announced but did not decide anything.  Note also
that at least some of those meetings did not have any IETF sanction.

I wonder if the uglier parts of the SNMP saga would not have come out far
better without one or two of the official IETF WG meetings.


]                                                           ...  Declaring an
] interim meeting for the purpose of avoiding a plenary meeting is a slap in
] the face ...

That's certainly true, but I don't see how you're going to fix that problem
without killing the mailinglists.  Working groups that fail to have quorums
at official meetings can and will still get work done.  As I know you know
too well, individuals will meet with or without IETF sanction, write
drafts, and the WG can and will progress (or not) regardless.

]                                         ...  but we have always worked on
] an ethic that says "if I am contributing to the work, the meeting must
] occasionally be near me."

That's not bad, especially for those with deep corporate or government
pockets to pay for travel.  It is good politics and fun.  However, very
little technical work is ever done in any committee meeting of a few hours,
no matter where it is held or with what official sanction.

] One sixth or more of our contributors come from Europe. A relatively small
] contingent comes from the South Pacific. Quite a large percentage come from
] North America. Hence, we put about one meeting in six in Europe and most of
] our meetings in North America. Is it not fair to put one meeting in 47 in
] the South Pacific? And why is it not an affront to those who have
] faithfully come from there, have contributed and chaired working groups
] from there, to complain about doing once what they have been doing for over
] a decade?

It's impossible to disagree with that.  I assume it's intended to
show that the IETF is an "international organization," but it does
not convince me.

Speaking of slaps in faces, I wonder if I were not a U.S. citizen if I
wouldn't feel some sting from the continual claims by the IETF that it is
an international organzation.  For example, how many AD's and IAB members
have not been U.S. residents?  Of those few that haven't been, how many
could not have "passed" as U.S. residents?--at least in email, none that
I can recall.  (I hope they'll they'll take that as a compliment on their
social skills instead of an affront to their national pride.)


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Mon Feb 14 23:10:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA05135
	for ietf-outbound.10@ietf.org; Mon, 14 Feb 2000 23:10:02 -0500 (EST)
Received: from thorn.blackrose.org (thorn.blackrose.org [204.212.44.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04209
	for <ietf@ietf.org>; Mon, 14 Feb 2000 22:37:56 -0500 (EST)
Received: (from dorian@localhost)
	by thorn.blackrose.org (8.9.3/8.9.3) id WAA06481
	for ietf@ietf.org; Mon, 14 Feb 2000 22:32:47 -0500 (EST)
Date: Mon, 14 Feb 2000 22:32:47 -0500
From: Dorian Kim <dorian@BLACKROSE.ORG>
To: ietf@ietf.org
Subject: Re: Who is interested in wireless cards for the Adelaide IETF meeting?
Message-ID: <20000214223247.D1640@blackrose.org>
Mail-Followup-To: ietf@ietf.org
References: <200002150227.MAA27866@kuji.off.connect.com.au> <20000214223116.C1640@blackrose.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
In-Reply-To: <20000214223116.C1640@blackrose.org>
X-Loop: ietf@ietf.org

On Mon, Feb 14, 2000 at 10:31:16PM -0500, Dorian Kim wrote:
> I'd be interested in borrowing a pair of wavelan cards.

*sigh*

apologies for not watching the cc: line. 

-dorian



From owner-ietf-outbound@ietf.org  Mon Feb 14 23:12:28 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05238
	for <ietf-web-archive@odin.ietf.org>; Mon, 14 Feb 2000 23:12:28 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA12176;
	Mon, 14 Feb 2000 23:10:30 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id XAA05135
	for ietf-outbound.10@ietf.org; Mon, 14 Feb 2000 23:10:02 -0500 (EST)
Received: from thorn.blackrose.org (thorn.blackrose.org [204.212.44.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04209
	for <ietf@ietf.org>; Mon, 14 Feb 2000 22:37:56 -0500 (EST)
Received: (from dorian@localhost)
	by thorn.blackrose.org (8.9.3/8.9.3) id WAA06481
	for ietf@ietf.org; Mon, 14 Feb 2000 22:32:47 -0500 (EST)
Date: Mon, 14 Feb 2000 22:32:47 -0500
From: Dorian Kim <dorian@BLACKROSE.ORG>
To: ietf@ietf.org
Subject: Re: Who is interested in wireless cards for the Adelaide IETF meeting?
Message-ID: <20000214223247.D1640@blackrose.org>
Mail-Followup-To: ietf@ietf.org
References: <200002150227.MAA27866@kuji.off.connect.com.au> <20000214223116.C1640@blackrose.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
In-Reply-To: <20000214223116.C1640@blackrose.org>
X-Loop: ietf@ietf.org

On Mon, Feb 14, 2000 at 10:31:16PM -0500, Dorian Kim wrote:
> I'd be interested in borrowing a pair of wavelan cards.

*sigh*

apologies for not watching the cc: line. 

-dorian



From owner-ietf-outbound  Tue Feb 15 00:40:28 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA06866
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 00:40:02 -0500 (EST)
Received: from foxhound.cisco.com (foxhound.cisco.com [171.69.192.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06772
	for <ietf@ietf.org>; Tue, 15 Feb 2000 00:35:29 -0500 (EST)
Received: (from kzm@localhost)
	by foxhound.cisco.com (8.8.8/2.5.1/Cisco List Logging/8.8.8) id VAA21885;
	Mon, 14 Feb 2000 21:34:38 -0800 (PST)
From: Keith McCloghrie <kzm@cisco.com>
Message-Id: <200002150534.VAA21885@foxhound.cisco.com>
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
To: vjs@calcite.rhyolite.com (Vernon Schryver)
Date: Mon, 14 Feb 2000 21:34:38 -0800 (PST)
Cc: ietf@ietf.org
In-Reply-To: <200002150337.UAA13992@calcite.rhyolite.com> from "Vernon Schryver" at Feb 14, 2000 08:37:49 PM
X-Mailer: ELM [version 2.5 PL1]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

> Let's see, how many RFC's are not in English?  How many WG meetings
> or mailinglists?
> 
> That the IETF is de facto an U.S. outfit is not by itself a bad thing.

You seem to be making the assumption that the English language is the
property of the USA.  Perhaps, you have forgotten that the English
language was spoken in a quite a lot of the world before the USA existed.

Keith.



From owner-ietf-outbound@ietf.org  Tue Feb 15 00:43:42 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06934
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Feb 2000 00:43:42 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA13745;
	Tue, 15 Feb 2000 00:41:40 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id AAA06866
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 00:40:02 -0500 (EST)
Received: from foxhound.cisco.com (foxhound.cisco.com [171.69.192.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06772
	for <ietf@ietf.org>; Tue, 15 Feb 2000 00:35:29 -0500 (EST)
Received: (from kzm@localhost)
	by foxhound.cisco.com (8.8.8/2.5.1/Cisco List Logging/8.8.8) id VAA21885;
	Mon, 14 Feb 2000 21:34:38 -0800 (PST)
From: Keith McCloghrie <kzm@cisco.com>
Message-Id: <200002150534.VAA21885@foxhound.cisco.com>
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
To: vjs@calcite.rhyolite.com (Vernon Schryver)
Date: Mon, 14 Feb 2000 21:34:38 -0800 (PST)
Cc: ietf@ietf.org
In-Reply-To: <200002150337.UAA13992@calcite.rhyolite.com> from "Vernon Schryver" at Feb 14, 2000 08:37:49 PM
X-Mailer: ELM [version 2.5 PL1]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> Let's see, how many RFC's are not in English?  How many WG meetings
> or mailinglists?
> 
> That the IETF is de facto an U.S. outfit is not by itself a bad thing.

You seem to be making the assumption that the English language is the
property of the USA.  Perhaps, you have forgotten that the English
language was spoken in a quite a lot of the world before the USA existed.

Keith.



From owner-ietf-outbound  Tue Feb 15 02:10:39 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA18334
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 02:10:02 -0500 (EST)
Received: from dfssl.exchange.microsoft.com ([131.107.88.59])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA14302
	for <ietf@ietf.org>; Tue, 15 Feb 2000 02:02:22 -0500 (EST)
Received: from 127.0.0.1 by dfssl.exchange.microsoft.com (InterScan E-Mail VirusWall NT); Mon, 14 Feb 2000 22:59:37 -0800 (Pacific Standard Time)
Received: by dfssl with Internet Mail Service (5.5.2650.21)
	id <198B1763>; Mon, 14 Feb 2000 22:59:37 -0800
Message-ID: <726A4C58DBA56E409F3D3563A8BF953CFDDA@airstream-corp.platinum.corp.microsoft.com>
From: Josh Cohen <joshco@Exchange.Microsoft.com>
To: ietf@ietf.org
Subject: RE: IETF Adelaide and interim meetings for APPS WGs
Date: Mon, 14 Feb 2000 22:57:09 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
X-Loop: ietf@ietf.org

well said!

> -----Original Message-----
> From: Keith Moore [mailto:moore@cs.utk.edu]
> Sent: Monday, February 14, 2000 3:37 PM
> Cc: ietf@ietf.org
> Subject: IETF Adelaide and interim meetings for APPS WGs
> 
> 
> It has come to the attention of the Applications Area Directors
> that one or more Applications area working groups have elected
> to not meet in Adelaide, and instead to hold an "interim meeting"
> in the United States, presumably because of distance and/or 
> cost issues.
> 
> IETF is an international organization, and it is IETF's longstanding 
> practice to hold its meetings in various locations around the planet.
> This serves both to encourage wider participation in IETF and also
> to more fairly distribute travel costs and inconvenience (over time) 
> among all participants.  The scheduleing of an interim WG meeting in 
> the US in lieu of a WG meeting in Adelaide undermines this policy.  
> This is insulting to non-US participants of IETF (many of whom have 
> attended meetings in the US for years), embarassing to IETF as 
> a whole, and a threat to IETF's international stature.
> 
> Even if a working group has few participants outside the United
> States, a working group does not work in isolation from other
> working groups.  Attendance at IETF meetings is an invaluable 
> mechanism for cross-group collaboration.  
> 
> RFC 2418 states:
> 
>    Interim meetings are subject to the
>    same rules for advance notification, reporting, open participation,
>    and process, which apply to other working group meetings.
> 
> Since normal working group meetings require advance notification
> via email to the entire IETF list, and the process for 
> getting a meeting
> slot involves prior approval of the Area Directors, the same
> requirements apply to interim working group meetings.  Part of the 
> reason for prior approval being required is to ensure that the 
> locations of the meetings are not being chosen to favor certain 
> participants over others.  
> 
> There have been several violations of this policy since publication
> of RFC 2418.
> 
> Therefore,
> 
> - All interim meetings within the Applications Area which were not
>   previously and explicitly approved by the Applications Area 
> Directors, 
>   are hereby cancelled.
> 
> - No Applications Area group will hold any interim meeting prior
>   to April 15.
> 
> - No Applications Area group which does not hold a meeting in 
>   Adelaide, will hold any interim meeting prior to July 31.
>   (i.e. prior to the Pittsburg IETF meeting)
> 
> - This applies to all face to face meetings held for the purpose 
>   of conducting working group discussion and to which the working 
>   group is invited, even if labelled "informal" or otherwise 
>   labelled to distinguish them from official working group meetings.
> 
> - Exceptions to this policy may be made for recently chartered groups,
>   but Area Director approval is still required for such groups to
>   schedule interim meetings.
> 
> 
> for the Applications Area Directors,
> 
> Keith Moore
> 



From owner-ietf-outbound@ietf.org  Tue Feb 15 02:16:37 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA18776
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Feb 2000 02:16:37 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA24637;
	Tue, 15 Feb 2000 02:14:35 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id CAA18334
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 02:10:02 -0500 (EST)
Received: from dfssl.exchange.microsoft.com ([131.107.88.59])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA14302
	for <ietf@ietf.org>; Tue, 15 Feb 2000 02:02:22 -0500 (EST)
Received: from 127.0.0.1 by dfssl.exchange.microsoft.com (InterScan E-Mail VirusWall NT); Mon, 14 Feb 2000 22:59:37 -0800 (Pacific Standard Time)
Received: by dfssl with Internet Mail Service (5.5.2650.21)
	id <198B1763>; Mon, 14 Feb 2000 22:59:37 -0800
Message-ID: <726A4C58DBA56E409F3D3563A8BF953CFDDA@airstream-corp.platinum.corp.microsoft.com>
From: Josh Cohen <joshco@Exchange.Microsoft.com>
To: ietf@ietf.org
Subject: RE: IETF Adelaide and interim meetings for APPS WGs
Date: Mon, 14 Feb 2000 22:57:09 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
X-Loop: ietf@ietf.org

well said!

> -----Original Message-----
> From: Keith Moore [mailto:moore@cs.utk.edu]
> Sent: Monday, February 14, 2000 3:37 PM
> Cc: ietf@ietf.org
> Subject: IETF Adelaide and interim meetings for APPS WGs
> 
> 
> It has come to the attention of the Applications Area Directors
> that one or more Applications area working groups have elected
> to not meet in Adelaide, and instead to hold an "interim meeting"
> in the United States, presumably because of distance and/or 
> cost issues.
> 
> IETF is an international organization, and it is IETF's longstanding 
> practice to hold its meetings in various locations around the planet.
> This serves both to encourage wider participation in IETF and also
> to more fairly distribute travel costs and inconvenience (over time) 
> among all participants.  The scheduleing of an interim WG meeting in 
> the US in lieu of a WG meeting in Adelaide undermines this policy.  
> This is insulting to non-US participants of IETF (many of whom have 
> attended meetings in the US for years), embarassing to IETF as 
> a whole, and a threat to IETF's international stature.
> 
> Even if a working group has few participants outside the United
> States, a working group does not work in isolation from other
> working groups.  Attendance at IETF meetings is an invaluable 
> mechanism for cross-group collaboration.  
> 
> RFC 2418 states:
> 
>    Interim meetings are subject to the
>    same rules for advance notification, reporting, open participation,
>    and process, which apply to other working group meetings.
> 
> Since normal working group meetings require advance notification
> via email to the entire IETF list, and the process for 
> getting a meeting
> slot involves prior approval of the Area Directors, the same
> requirements apply to interim working group meetings.  Part of the 
> reason for prior approval being required is to ensure that the 
> locations of the meetings are not being chosen to favor certain 
> participants over others.  
> 
> There have been several violations of this policy since publication
> of RFC 2418.
> 
> Therefore,
> 
> - All interim meetings within the Applications Area which were not
>   previously and explicitly approved by the Applications Area 
> Directors, 
>   are hereby cancelled.
> 
> - No Applications Area group will hold any interim meeting prior
>   to April 15.
> 
> - No Applications Area group which does not hold a meeting in 
>   Adelaide, will hold any interim meeting prior to July 31.
>   (i.e. prior to the Pittsburg IETF meeting)
> 
> - This applies to all face to face meetings held for the purpose 
>   of conducting working group discussion and to which the working 
>   group is invited, even if labelled "informal" or otherwise 
>   labelled to distinguish them from official working group meetings.
> 
> - Exceptions to this policy may be made for recently chartered groups,
>   but Area Director approval is still required for such groups to
>   schedule interim meetings.
> 
> 
> for the Applications Area Directors,
> 
> Keith Moore
> 



From owner-ietf-outbound  Tue Feb 15 02:50:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA20423
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 02:50:02 -0500 (EST)
Received: from carbon.btinternet.com (carbon.btinternet.com [194.73.73.92])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA20382
	for <ietf@ietf.org>; Tue, 15 Feb 2000 02:45:16 -0500 (EST)
Received: from [213.1.183.136] (helo=patonmj)
	by carbon.btinternet.com with smtp (Exim 2.05 #1)
	id 12KcfZ-0001lR-00
	for ietf@ietf.org; Tue, 15 Feb 2000 07:45:13 +0000
From: "mark.paton" <mark.paton@btinternet.com>
To: "Ietf@Ietf. Org" <ietf@ietf.org>
Subject: RE: Proposal: reclassify RFC2549, 1149 as historical
Date: Tue, 15 Feb 2000 07:45:20 -0000
Message-ID: <NCBBINIKLKLJEEDCGLOAAEPFCDAA.mark.paton@btinternet.com>
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0012_01BF7788.9C380D80"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Importance: Normal
In-Reply-To: <Pine.SOL.4.10.10002142113530.5614-100000@petra.ee.surrey.ac.uk>
X-Loop: ietf@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_0012_01BF7788.9C380D80
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

I would tend to agree with Lloyd

Regards

Mark Paton CEO/DIR. Internet Network Eng
Mercury Network Systems Limited
+44 585 649051
http://www.mnsl.org

"Mercury Network Systems - The Unstoppable Force"

This e-mail is intended only for the addressee
named above. As this e-mail may contain
confidential or privileged information if you are
not, or suspect that you are not, the named
addressee or the person responsible for delivering
the message to the named addressee, please
telephone us immediately. Please note that we
cannot guarantee that this message or any
attachment is virus free or has not been
intercepted and amended. The views of the author
may not necessarily reflect those of the Company.


-----Original Message-----
From: Lloyd Wood [mailto:l.wood@eim.surrey.ac.uk]
Sent: 14 February 2000 21:26
To: ietf@ietf.org
Subject: Proposal: reclassify RFC2549,
1149 as historical


I move we reclassify RFC2549 and RFC1149
as historical.

Evidence to support this: 'end of an era'
according to
http://www.telegraph.co.uk/et?ac=000111464
113065&pg=/et/00/2/14/wpig14.html
below.

In particular, I don't think the QoS
additions have ever been fully
field tested; the WFQ proposal leads to
observable instances of
dropped tails during measurement.

L.

don't you just hate thinking about
sending yourself valentines?

<L.Wood@surrey.ac.uk>PGP<http://www.ee.sur
rey.ac.uk/Personal/L.Wood/>


ELECTRONIC TELEGRAPH, ISSUE 1725

Monday 14 February 2000

Spread of radio switches off political pigeon post
By Jon Stock in New Delhi

MORE than 600 Indian police carrier
pigeons face early retirement
after officials decided to replace them
with radios.

The decision to ground the birds before
Wednesday's state assembly
elections in Orissa, eastern India, marks
the end of an era. They
previously played a unique role in
India's electoral process.

They last saw active duty during last
year's general election, when
they carried messages to and from
far-flung polling booths in the
remote Orissa districts of Koraput and
Dhenkanal. The messages
detailed the law and order situation
during polling. The pigeons are
kept in 28 lofts throughout the state and
will now become showpieces
used solely for ceremonial purposes,
according to Baikunthanath Das,
Superintendent of Police (Signals), who
looks after them.

Their demise has been caused by what he
called the advent of new
technology. He said: "Even the most
remote interior areas now have VHF
radios."

The service was the only one of its kind
in India. It was started in
1946 during British rule by the state
police's Signal Establishment,
which bought more than 1,000 pigeons from
the Indian Army after the
Second World War.


------=_NextPart_000_0012_01BF7788.9C380D80
Content-Type: text/x-vcard;
	name="Mark. J.S Paton.vcf"
Content-Disposition: attachment;
	filename="Mark. J.S Paton.vcf"
Content-Transfer-Encoding: quoted-printable

BEGIN:VCARD
VERSION:2.1
N:Paton;Mark.;J.S;;
FN:Mark. J.S Paton
ORG:Mnsl;Consultancy
TITLE:Network Design / Support
TEL;WORK;VOICE:+44 0585 649051
TEL;CELL;VOICE:+44 (0585) 649051
ADR;WORK;ENCODING=3DQUOTED-PRINTABLE:;Basingstoke;Willow =
Cottage=3D0D=3D0AReading Road;Mattingley;Hampshire;RG27 8JU;=3D
United Kingdom
LABEL;WORK;ENCODING=3DQUOTED-PRINTABLE:Basingstoke=3D0D=3D0AWillow =
Cottage=3D0D=3D0AReading Road=3D0D=3D0AMattingley, Hampshire=3D
 RG27 8JU=3D0D=3D0AUnited Kingdom
URL:
URL:http://www.mnsl.org
EMAIL;PREF;INTERNET:mark.paton@mnsl.org
REV:19990422T133901Z
END:VCARD

------=_NextPart_000_0012_01BF7788.9C380D80--



From owner-ietf-outbound@ietf.org  Tue Feb 15 02:56:29 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA20517
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Feb 2000 02:56:29 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA26048;
	Tue, 15 Feb 2000 02:54:26 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id CAA20423
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 02:50:02 -0500 (EST)
Received: from carbon.btinternet.com (carbon.btinternet.com [194.73.73.92])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA20382
	for <ietf@ietf.org>; Tue, 15 Feb 2000 02:45:16 -0500 (EST)
Received: from [213.1.183.136] (helo=patonmj)
	by carbon.btinternet.com with smtp (Exim 2.05 #1)
	id 12KcfZ-0001lR-00
	for ietf@ietf.org; Tue, 15 Feb 2000 07:45:13 +0000
From: "mark.paton" <mark.paton@btinternet.com>
To: "Ietf@Ietf. Org" <ietf@ietf.org>
Subject: RE: Proposal: reclassify RFC2549, 1149 as historical
Date: Tue, 15 Feb 2000 07:45:20 -0000
Message-ID: <NCBBINIKLKLJEEDCGLOAAEPFCDAA.mark.paton@btinternet.com>
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0012_01BF7788.9C380D80"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Importance: Normal
In-Reply-To: <Pine.SOL.4.10.10002142113530.5614-100000@petra.ee.surrey.ac.uk>
X-Loop: ietf@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_0012_01BF7788.9C380D80
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

I would tend to agree with Lloyd

Regards

Mark Paton CEO/DIR. Internet Network Eng
Mercury Network Systems Limited
+44 585 649051
http://www.mnsl.org

"Mercury Network Systems - The Unstoppable Force"

This e-mail is intended only for the addressee
named above. As this e-mail may contain
confidential or privileged information if you are
not, or suspect that you are not, the named
addressee or the person responsible for delivering
the message to the named addressee, please
telephone us immediately. Please note that we
cannot guarantee that this message or any
attachment is virus free or has not been
intercepted and amended. The views of the author
may not necessarily reflect those of the Company.


-----Original Message-----
From: Lloyd Wood [mailto:l.wood@eim.surrey.ac.uk]
Sent: 14 February 2000 21:26
To: ietf@ietf.org
Subject: Proposal: reclassify RFC2549,
1149 as historical


I move we reclassify RFC2549 and RFC1149
as historical.

Evidence to support this: 'end of an era'
according to
http://www.telegraph.co.uk/et?ac=000111464
113065&pg=/et/00/2/14/wpig14.html
below.

In particular, I don't think the QoS
additions have ever been fully
field tested; the WFQ proposal leads to
observable instances of
dropped tails during measurement.

L.

don't you just hate thinking about
sending yourself valentines?

<L.Wood@surrey.ac.uk>PGP<http://www.ee.sur
rey.ac.uk/Personal/L.Wood/>


ELECTRONIC TELEGRAPH, ISSUE 1725

Monday 14 February 2000

Spread of radio switches off political pigeon post
By Jon Stock in New Delhi

MORE than 600 Indian police carrier
pigeons face early retirement
after officials decided to replace them
with radios.

The decision to ground the birds before
Wednesday's state assembly
elections in Orissa, eastern India, marks
the end of an era. They
previously played a unique role in
India's electoral process.

They last saw active duty during last
year's general election, when
they carried messages to and from
far-flung polling booths in the
remote Orissa districts of Koraput and
Dhenkanal. The messages
detailed the law and order situation
during polling. The pigeons are
kept in 28 lofts throughout the state and
will now become showpieces
used solely for ceremonial purposes,
according to Baikunthanath Das,
Superintendent of Police (Signals), who
looks after them.

Their demise has been caused by what he
called the advent of new
technology. He said: "Even the most
remote interior areas now have VHF
radios."

The service was the only one of its kind
in India. It was started in
1946 during British rule by the state
police's Signal Establishment,
which bought more than 1,000 pigeons from
the Indian Army after the
Second World War.


------=_NextPart_000_0012_01BF7788.9C380D80
Content-Type: text/x-vcard;
	name="Mark. J.S Paton.vcf"
Content-Disposition: attachment;
	filename="Mark. J.S Paton.vcf"
Content-Transfer-Encoding: quoted-printable

BEGIN:VCARD
VERSION:2.1
N:Paton;Mark.;J.S;;
FN:Mark. J.S Paton
ORG:Mnsl;Consultancy
TITLE:Network Design / Support
TEL;WORK;VOICE:+44 0585 649051
TEL;CELL;VOICE:+44 (0585) 649051
ADR;WORK;ENCODING=3DQUOTED-PRINTABLE:;Basingstoke;Willow =
Cottage=3D0D=3D0AReading Road;Mattingley;Hampshire;RG27 8JU;=3D
United Kingdom
LABEL;WORK;ENCODING=3DQUOTED-PRINTABLE:Basingstoke=3D0D=3D0AWillow =
Cottage=3D0D=3D0AReading Road=3D0D=3D0AMattingley, Hampshire=3D
 RG27 8JU=3D0D=3D0AUnited Kingdom
URL:
URL:http://www.mnsl.org
EMAIL;PREF;INTERNET:mark.paton@mnsl.org
REV:19990422T133901Z
END:VCARD

------=_NextPart_000_0012_01BF7788.9C380D80--



From owner-ietf-outbound  Tue Feb 15 06:32:04 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA21996
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 06:30:04 -0500 (EST)
Received: from prue.eim.surrey.ac.uk (IDENT:exim@prue.eim.surrey.ac.uk [131.227.76.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA21939
	for <IETF@ietf.org>; Tue, 15 Feb 2000 06:20:22 -0500 (EST)
Received: from petra.ee.surrey.ac.uk ([131.227.88.13] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.03 #1)
	id 12KfxN-0004ds-00; Tue, 15 Feb 2000 11:15:49 +0000
Date: Tue, 15 Feb 2000 11:15:25 +0000 (GMT)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-Sender: eep1lw@petra.ee.surrey.ac.uk
Reply-To: L.Wood@eim.surrey.ac.uk
To: Anders Feder <lists.anders@feder.dk>, Robert Elz <kre@munnari.OZ.AU>
cc: IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
In-Reply-To: <004801bf7735$7d3bb420$1000000a@DIC>
Message-ID: <Pine.SOL.4.10.10002151109510.7412-100000@petra.ee.surrey.ac.uk>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Mon, 14 Feb 2000, Anders Feder wrote:

> Robert Elz <kre@munnari.OZ.AU> wrote:
> >I'm not sure there is a good analogy there.    There's no good purpose
> >in sending packets with incorrect source addresses I can think of,

Crypto- and security-related, I should think. Randomising the source
address makes tracking the existence of communications between a given
source and a given destination that much harder; they know who they're
talking to based on encrypted message content, but no-one else has to.

A lot of surveillance can be based on 'if A is talking to B, then A
must be as guilty as B', and message content is irrelevant. This
helps counters that.

(This is vaguely analogous to OpenBSD using non-sequential packet IDs,
yes? Bet it's not in IPSEC.)

> It is rarely very easy to see what requirements the future will bring and
> particularly in this business you can't be sure what the technology of
> tomorrow demands.

Indeed.

L.

<L.Wood@surrey.ac.uk>PGP<http://www.ee.surrey.ac.uk/Personal/L.Wood/>



From owner-ietf-outbound@ietf.org  Tue Feb 15 06:38:08 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22472
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Feb 2000 06:38:08 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA02078;
	Tue, 15 Feb 2000 06:36:03 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id GAA21996
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 06:30:04 -0500 (EST)
Received: from prue.eim.surrey.ac.uk (IDENT:exim@prue.eim.surrey.ac.uk [131.227.76.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA21939
	for <IETF@ietf.org>; Tue, 15 Feb 2000 06:20:22 -0500 (EST)
Received: from petra.ee.surrey.ac.uk ([131.227.88.13] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.03 #1)
	id 12KfxN-0004ds-00; Tue, 15 Feb 2000 11:15:49 +0000
Date: Tue, 15 Feb 2000 11:15:25 +0000 (GMT)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-Sender: eep1lw@petra.ee.surrey.ac.uk
Reply-To: L.Wood@eim.surrey.ac.uk
To: Anders Feder <lists.anders@feder.dk>, Robert Elz <kre@munnari.OZ.AU>
cc: IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
In-Reply-To: <004801bf7735$7d3bb420$1000000a@DIC>
Message-ID: <Pine.SOL.4.10.10002151109510.7412-100000@petra.ee.surrey.ac.uk>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Mon, 14 Feb 2000, Anders Feder wrote:

> Robert Elz <kre@munnari.OZ.AU> wrote:
> >I'm not sure there is a good analogy there.    There's no good purpose
> >in sending packets with incorrect source addresses I can think of,

Crypto- and security-related, I should think. Randomising the source
address makes tracking the existence of communications between a given
source and a given destination that much harder; they know who they're
talking to based on encrypted message content, but no-one else has to.

A lot of surveillance can be based on 'if A is talking to B, then A
must be as guilty as B', and message content is irrelevant. This
helps counters that.

(This is vaguely analogous to OpenBSD using non-sequential packet IDs,
yes? Bet it's not in IPSEC.)

> It is rarely very easy to see what requirements the future will bring and
> particularly in this business you can't be sure what the technology of
> tomorrow demands.

Indeed.

L.

<L.Wood@surrey.ac.uk>PGP<http://www.ee.surrey.ac.uk/Personal/L.Wood/>



From owner-ietf-outbound  Tue Feb 15 07:10:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA23493
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 07:10:02 -0500 (EST)
Received: from mailman.cisco.com (mailman.cisco.com [171.68.225.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22989
	for <IETF@ietf.org>; Tue, 15 Feb 2000 07:00:50 -0500 (EST)
Received: from bigger-dawgs (pferguso-isdn.cisco.com [171.70.114.134]) by mailman.cisco.com (8.8.8+Sun/CISCO.SERVER.1.2) with ESMTP id DAA06695; Tue, 15 Feb 2000 03:52:28 -0800 (PST)
Message-Id: <4.2.2.20000215065124.00a635a0@lint.cisco.com>
X-Sender: pferguso@lint.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Tue, 15 Feb 2000 06:52:19 -0500
To: L.Wood@eim.surrey.ac.uk
From: Paul Ferguson <ferguson@cisco.com>
Subject: Re: Internet SYN Flooding, spoofing attacks
Cc: Anders Feder <lists.anders@feder.dk>, Robert Elz <kre@munnari.OZ.AU>,
        IETF@ietf.org
In-Reply-To: <Pine.SOL.4.10.10002151109510.7412-100000@petra.ee.surrey.a
 c.uk>
References: <004801bf7735$7d3bb420$1000000a@DIC>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 11:15 AM 02/15/2000 +0000, Lloyd Wood wrote:

>A lot of surveillance can be based on 'if A is talking to B, then A
>must be as guilty as B', and message content is irrelevant. This
>helps counters that.

Well, get over it. ;-)

(Smiley included for the humor impaired.)

- paul



From owner-ietf-outbound@ietf.org  Tue Feb 15 07:17:26 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23900
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Feb 2000 07:17:25 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA02829;
	Tue, 15 Feb 2000 07:15:22 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id HAA23493
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 07:10:02 -0500 (EST)
Received: from mailman.cisco.com (mailman.cisco.com [171.68.225.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22989
	for <IETF@ietf.org>; Tue, 15 Feb 2000 07:00:50 -0500 (EST)
Received: from bigger-dawgs (pferguso-isdn.cisco.com [171.70.114.134]) by mailman.cisco.com (8.8.8+Sun/CISCO.SERVER.1.2) with ESMTP id DAA06695; Tue, 15 Feb 2000 03:52:28 -0800 (PST)
Message-Id: <4.2.2.20000215065124.00a635a0@lint.cisco.com>
X-Sender: pferguso@lint.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Tue, 15 Feb 2000 06:52:19 -0500
To: L.Wood@eim.surrey.ac.uk
From: Paul Ferguson <ferguson@cisco.com>
Subject: Re: Internet SYN Flooding, spoofing attacks
Cc: Anders Feder <lists.anders@feder.dk>, Robert Elz <kre@munnari.OZ.AU>,
        IETF@ietf.org
In-Reply-To: <Pine.SOL.4.10.10002151109510.7412-100000@petra.ee.surrey.a
 c.uk>
References: <004801bf7735$7d3bb420$1000000a@DIC>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 11:15 AM 02/15/2000 +0000, Lloyd Wood wrote:

>A lot of surveillance can be based on 'if A is talking to B, then A
>must be as guilty as B', and message content is irrelevant. This
>helps counters that.

Well, get over it. ;-)

(Smiley included for the humor impaired.)

- paul



From owner-ietf-outbound  Tue Feb 15 08:00:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA26537
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 08:00:02 -0500 (EST)
Received: from monsoon.mail.pipex.net (monsoon.mail.pipex.net [158.43.128.69])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA26261
	for <ietf@ietf.org>; Tue, 15 Feb 2000 07:55:39 -0500 (EST)
Received: (qmail 20497 invoked from network); 15 Feb 2000 12:55:38 -0000
Received: from userl416.uk.uudial.com (HELO GK-VAIO) (193.149.74.229)
  by smtp.dial.pipex.com with SMTP; 15 Feb 2000 12:55:38 -0000
Message-Id: <4.2.2.20000215110344.00a3e100@pop.dial.pipex.com>
X-Sender: maiw03@pop.dial.pipex.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Tue, 15 Feb 2000 11:11:50 +0000
To: Vernon Schryver <vjs@calcite.rhyolite.com>
From: Graham Klyne <GK@Dial.pipex.com>
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
Cc: ietf@ietf.org
In-Reply-To: <200002150045.RAA08041@calcite.rhyolite.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 05:45 PM 2/14/00 -0700, Vernon Schryver wrote:
>In other words and politically correct pretense asside, the IETF is not
>an international organization.  Despite its posturing, the IETF is a U.S.
>or perhaps North American organization that welcomes non-U.S. participants
>and occasionally spends a lot of its U.S. participants' time and money to
>try to make people outside of North America feel welcome.

As a non-US IETF participant, I found this statement mildly insulting.  But 
then I have to ask myself "why?".  It is true that a majority of IETF 
participation is US-based.  It is true that the IETF secretariat is wholly 
US-based.  It is true that the IETF is an outgrowth of a US national 
organization.  So on the face of it, your statement appears entirely true.

But I am still uncomfortable with it.  It implies that, somehow, any non-US 
participant is somehow a second class citizen, who is permitted to attend 
purely as a concession by the US elite whose organization this is.  Maybe 
that also is true -- but I don't have to like it.  I very much prefer the 
"pretense" that the IETF is an organization that provides technical 
direction for a truly global facility, and that it aspires to do so for the 
benefit of all the world's people, with equal status and consideration 
allowed to any who can participate, from wherever they may originate.

#g
--

------------
Graham Klyne
(GK@ACM.ORG)



From owner-ietf-outbound@ietf.org  Tue Feb 15 08:08:05 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27084
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Feb 2000 08:08:00 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA03995;
	Tue, 15 Feb 2000 08:05:24 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id IAA26537
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 08:00:02 -0500 (EST)
Received: from monsoon.mail.pipex.net (monsoon.mail.pipex.net [158.43.128.69])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA26261
	for <ietf@ietf.org>; Tue, 15 Feb 2000 07:55:39 -0500 (EST)
Received: (qmail 20497 invoked from network); 15 Feb 2000 12:55:38 -0000
Received: from userl416.uk.uudial.com (HELO GK-VAIO) (193.149.74.229)
  by smtp.dial.pipex.com with SMTP; 15 Feb 2000 12:55:38 -0000
Message-Id: <4.2.2.20000215110344.00a3e100@pop.dial.pipex.com>
X-Sender: maiw03@pop.dial.pipex.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Tue, 15 Feb 2000 11:11:50 +0000
To: Vernon Schryver <vjs@calcite.rhyolite.com>
From: Graham Klyne <GK@Dial.pipex.com>
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
Cc: ietf@ietf.org
In-Reply-To: <200002150045.RAA08041@calcite.rhyolite.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 05:45 PM 2/14/00 -0700, Vernon Schryver wrote:
>In other words and politically correct pretense asside, the IETF is not
>an international organization.  Despite its posturing, the IETF is a U.S.
>or perhaps North American organization that welcomes non-U.S. participants
>and occasionally spends a lot of its U.S. participants' time and money to
>try to make people outside of North America feel welcome.

As a non-US IETF participant, I found this statement mildly insulting.  But 
then I have to ask myself "why?".  It is true that a majority of IETF 
participation is US-based.  It is true that the IETF secretariat is wholly 
US-based.  It is true that the IETF is an outgrowth of a US national 
organization.  So on the face of it, your statement appears entirely true.

But I am still uncomfortable with it.  It implies that, somehow, any non-US 
participant is somehow a second class citizen, who is permitted to attend 
purely as a concession by the US elite whose organization this is.  Maybe 
that also is true -- but I don't have to like it.  I very much prefer the 
"pretense" that the IETF is an organization that provides technical 
direction for a truly global facility, and that it aspires to do so for the 
benefit of all the world's people, with equal status and consideration 
allowed to any who can participate, from wherever they may originate.

#g
--

------------
Graham Klyne
(GK@ACM.ORG)



From owner-ietf-outbound  Tue Feb 15 08:10:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA27231
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 08:10:02 -0500 (EST)
Received: from mailman.cisco.com (mailman.cisco.com [171.68.225.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27187
	for <IETF@ietf.org>; Tue, 15 Feb 2000 08:09:40 -0500 (EST)
Received: from bigger-dawgs (pferguso-isdn.cisco.com [171.70.114.134]) by mailman.cisco.com (8.8.8+Sun/CISCO.SERVER.1.2) with ESMTP id FAA13955; Tue, 15 Feb 2000 05:09:09 -0800 (PST)
Message-Id: <4.2.2.20000214222414.00a65b00@lint.cisco.com>
X-Sender: pferguso@lint.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Mon, 14 Feb 2000 22:34:52 -0500
To: IETF@ietf.org
From: Paul Ferguson <ferguson@cisco.com>
Subject: DoS (Denial of Service) Attack resource page
Cc: dts@senie.com
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

Folks,

Dan Senie and I got tired of keeping separate browser
bookmarks on a myriad of DoS Attack technical info, and
so we decided to slap together a web page which contains
some "good technical resources" on these DoS attacks:

  http://www.denialinfo.com/

Of course, it is pretty raw right now, but we'll make it
easier on the eyes over time, as well as add more content.
In fact, I think the page counter on the main page is broken
right now, but works on the mirror. Minor problems (it's the
content that counts, right?).

In any event, this is where you come in -- we would like to
solicit the community at-large to send along pertinent pointers
to any additional resources which we may have overlooked, or
that we just didn't know about in the first place.

Contact info is available on the web page, and so is a
URL for a mirror.

Thanks,

- paul and dan

ps. Thanks much to Kevin Siers, political cartoonist at the
Charlotte Observer, for letting use his awesome cartoon. ;-)



From owner-ietf-outbound@ietf.org  Tue Feb 15 08:16:48 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27865
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Feb 2000 08:16:48 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA04226;
	Tue, 15 Feb 2000 08:15:10 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id IAA27231
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 08:10:02 -0500 (EST)
Received: from mailman.cisco.com (mailman.cisco.com [171.68.225.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27187
	for <IETF@ietf.org>; Tue, 15 Feb 2000 08:09:40 -0500 (EST)
Received: from bigger-dawgs (pferguso-isdn.cisco.com [171.70.114.134]) by mailman.cisco.com (8.8.8+Sun/CISCO.SERVER.1.2) with ESMTP id FAA13955; Tue, 15 Feb 2000 05:09:09 -0800 (PST)
Message-Id: <4.2.2.20000214222414.00a65b00@lint.cisco.com>
X-Sender: pferguso@lint.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Mon, 14 Feb 2000 22:34:52 -0500
To: IETF@ietf.org
From: Paul Ferguson <ferguson@cisco.com>
Subject: DoS (Denial of Service) Attack resource page
Cc: dts@senie.com
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

Folks,

Dan Senie and I got tired of keeping separate browser
bookmarks on a myriad of DoS Attack technical info, and
so we decided to slap together a web page which contains
some "good technical resources" on these DoS attacks:

  http://www.denialinfo.com/

Of course, it is pretty raw right now, but we'll make it
easier on the eyes over time, as well as add more content.
In fact, I think the page counter on the main page is broken
right now, but works on the mirror. Minor problems (it's the
content that counts, right?).

In any event, this is where you come in -- we would like to
solicit the community at-large to send along pertinent pointers
to any additional resources which we may have overlooked, or
that we just didn't know about in the first place.

Contact info is available on the web page, and so is a
URL for a mirror.

Thanks,

- paul and dan

ps. Thanks much to Kevin Siers, political cartoonist at the
Charlotte Observer, for letting use his awesome cartoon. ;-)



From owner-ietf-outbound  Tue Feb 15 08:30:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA28751
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 08:30:02 -0500 (EST)
Received: from kuji.off.connect.com.au (kuji.off.connect.com.au [203.63.69.33])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28088
	for <ietf@ietf.org>; Tue, 15 Feb 2000 08:20:30 -0500 (EST)
Received: from [203.63.69.49] (ppp01.ade.off.connect.com.au [203.63.69.49]) by kuji.off.connect.com.au with SMTP id XAA04842
  (8.8.8/IDA-1.6 for <ietf@ietf.org>); Tue, 15 Feb 2000 23:49:54 +1030 (CST)
From: Mark Prior <mrp@connect.com.au>
Reply-to: Mark Prior <mrp@connect.com.au>
To: ietf@ietf.org
Subject: Static addresses for the Adelaide IETF
Date: Tue, 15 Feb 2000 23:48:48 +0930
Message-ID: <n09dBvhfQDpW.N3Y4dJR1@kuji.off.connect.com.au>
X-Mailer: EPOC Email Version 2.00
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Language: i-default
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id IAA28088
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit

Just another question :-) For people who will want static IPs rather than dynamic (I assume for firewall configuration), will you want to use wireless? I'm told to keep MBONE/wired and wireless LANs apart and so I'm trying to determine if I need more than one static address pool.

Note this is not the time to request a static assignment! This is just question time :-)

Mark.



From owner-ietf-outbound@ietf.org  Tue Feb 15 08:37:46 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29395
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Feb 2000 08:37:46 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA04896;
	Tue, 15 Feb 2000 08:35:42 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id IAA28751
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 08:30:02 -0500 (EST)
Received: from kuji.off.connect.com.au (kuji.off.connect.com.au [203.63.69.33])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28088
	for <ietf@ietf.org>; Tue, 15 Feb 2000 08:20:30 -0500 (EST)
Received: from [203.63.69.49] (ppp01.ade.off.connect.com.au [203.63.69.49]) by kuji.off.connect.com.au with SMTP id XAA04842
  (8.8.8/IDA-1.6 for <ietf@ietf.org>); Tue, 15 Feb 2000 23:49:54 +1030 (CST)
From: Mark Prior <mrp@connect.com.au>
Reply-to: Mark Prior <mrp@connect.com.au>
To: ietf@ietf.org
Subject: Static addresses for the Adelaide IETF
Date: Tue, 15 Feb 2000 23:48:48 +0930
Message-ID: <n09dBvhfQDpW.N3Y4dJR1@kuji.off.connect.com.au>
X-Mailer: EPOC Email Version 2.00
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Language: i-default
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id IAA28088
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Just another question :-) For people who will want static IPs rather than dynamic (I assume for firewall configuration), will you want to use wireless? I'm told to keep MBONE/wired and wireless LANs apart and so I'm trying to determine if I need more than one static address pool.

Note this is not the time to request a static assignment! This is just question time :-)

Mark.



From owner-ietf-outbound  Tue Feb 15 09:50:26 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA05666
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 09:50:03 -0500 (EST)
Received: from tsx-prime.MIT.EDU (TSX-PRIME.MIT.EDU [18.86.0.76])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA05490
	for <ietf@ietf.org>; Tue, 15 Feb 2000 09:48:24 -0500 (EST)
Received: by tsx-prime.MIT.EDU 
	with sendmail-SMI-8.6/1.2, id JAA14304; Tue, 15 Feb 2000 09:48:15 -0500
Date: Tue, 15 Feb 2000 09:48:15 -0500
Message-Id: <200002151448.JAA14304@tsx-prime.MIT.EDU>
From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: Keith McCloghrie <kzm@cisco.com>
CC: vjs@calcite.rhyolite.com, ietf@ietf.org
In-reply-to: Keith McCloghrie's message of Mon, 14 Feb 2000 21:34:38 -0800
	(PST), <200002150534.VAA21885@foxhound.cisco.com>
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
Phone: (781) 391-3464
X-Loop: ietf@ietf.org

   From: Keith McCloghrie <kzm@cisco.com>
   Date: Mon, 14 Feb 2000 21:34:38 -0800 (PST)

   > Let's see, how many RFC's are not in English?  How many WG meetings
   > or mailinglists?
   > 
   > That the IETF is de facto an U.S. outfit is not by itself a bad thing.

   You seem to be making the assumption that the English language is the
   property of the USA.  Perhaps, you have forgotten that the English
   language was spoken in a quite a lot of the world before the USA existed.

For better or worse (and I'm sure I'm going to piss off some number of
Frenchmen and Quebecois by saying this), English has become the Lingua
Franca of the Internet.

I was amazed when I first found out about the attitudes of a number of
non-native-English-speaking programmers who consider it bad programming
style to write use non-English variables, comments, or function names in
their programs.  This was for maintainability reasons.  Even if a German
were maintaining a program today, a year from now perhaps someone from
the Netherlands or Belgium might need to pick and understand the
software project.  While this is attitude is most prevalent in the Open
Source community, it even applies to some (many?) large commercial
programming shops.  (I first heard about this from a friend of mine who
works for SAP AG, who pointed out that they had programmers from all
over Europe.)

This phenomenon is of course not unique to programming.  I recall
reading about some E.C. meetings where the committee members waived
translation services and elected to conduct their exclusively in some
common language, often English, simply to save money and because it's
much less awkward than having to edit a document in three different
languages simultaneously.  (Presumably they would edit it once in
English, and once the master document was agreed to, they would then
translate it to other languages.)

Perhaps it's not fair that English has won this privileged place, and
not some other language, like French, or Esparanto.  Speaking selfishly,
it means that I never have a chance to practice my (by now very rusty)
six years of Spanish that I took in high school and college.  But if I
had access to the source code of the universe and could give it a quick
edit and recompile, I'd make many other changes, including outlawing
software patents and #ifdef'ing out the MPAA.  But fortunately or
unfortunately, this is not one of our options for making changes in the
world.  :-)

							- Ted



From owner-ietf-outbound@ietf.org  Tue Feb 15 09:57:22 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06384
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Feb 2000 09:57:17 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA07348;
	Tue, 15 Feb 2000 09:55:08 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id JAA05666
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 09:50:03 -0500 (EST)
Received: from tsx-prime.MIT.EDU (TSX-PRIME.MIT.EDU [18.86.0.76])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA05490
	for <ietf@ietf.org>; Tue, 15 Feb 2000 09:48:24 -0500 (EST)
Received: by tsx-prime.MIT.EDU 
	with sendmail-SMI-8.6/1.2, id JAA14304; Tue, 15 Feb 2000 09:48:15 -0500
Date: Tue, 15 Feb 2000 09:48:15 -0500
Message-Id: <200002151448.JAA14304@tsx-prime.MIT.EDU>
From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: Keith McCloghrie <kzm@cisco.com>
CC: vjs@calcite.rhyolite.com, ietf@ietf.org
In-reply-to: Keith McCloghrie's message of Mon, 14 Feb 2000 21:34:38 -0800
	(PST), <200002150534.VAA21885@foxhound.cisco.com>
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
Phone: (781) 391-3464
X-Loop: ietf@ietf.org

   From: Keith McCloghrie <kzm@cisco.com>
   Date: Mon, 14 Feb 2000 21:34:38 -0800 (PST)

   > Let's see, how many RFC's are not in English?  How many WG meetings
   > or mailinglists?
   > 
   > That the IETF is de facto an U.S. outfit is not by itself a bad thing.

   You seem to be making the assumption that the English language is the
   property of the USA.  Perhaps, you have forgotten that the English
   language was spoken in a quite a lot of the world before the USA existed.

For better or worse (and I'm sure I'm going to piss off some number of
Frenchmen and Quebecois by saying this), English has become the Lingua
Franca of the Internet.

I was amazed when I first found out about the attitudes of a number of
non-native-English-speaking programmers who consider it bad programming
style to write use non-English variables, comments, or function names in
their programs.  This was for maintainability reasons.  Even if a German
were maintaining a program today, a year from now perhaps someone from
the Netherlands or Belgium might need to pick and understand the
software project.  While this is attitude is most prevalent in the Open
Source community, it even applies to some (many?) large commercial
programming shops.  (I first heard about this from a friend of mine who
works for SAP AG, who pointed out that they had programmers from all
over Europe.)

This phenomenon is of course not unique to programming.  I recall
reading about some E.C. meetings where the committee members waived
translation services and elected to conduct their exclusively in some
common language, often English, simply to save money and because it's
much less awkward than having to edit a document in three different
languages simultaneously.  (Presumably they would edit it once in
English, and once the master document was agreed to, they would then
translate it to other languages.)

Perhaps it's not fair that English has won this privileged place, and
not some other language, like French, or Esparanto.  Speaking selfishly,
it means that I never have a chance to practice my (by now very rusty)
six years of Spanish that I took in high school and college.  But if I
had access to the source code of the universe and could give it a quick
edit and recompile, I'd make many other changes, including outlawing
software patents and #ifdef'ing out the MPAA.  But fortunately or
unfortunately, this is not one of our options for making changes in the
world.  :-)

							- Ted



From owner-ietf-outbound  Tue Feb 15 10:20:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA08338
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 10:20:02 -0500 (EST)
Received: from jhawk-foo.bbnplanet.com (jhawk-foo.bbnplanet.com [199.94.208.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08188
	for <IETF@ietf.org>; Tue, 15 Feb 2000 10:17:34 -0500 (EST)
Received: (from jhawk@localhost)
	by jhawk-foo.bbnplanet.com (8.8.8+Sun/8.8.8) id KAA05581;
	Tue, 15 Feb 2000 10:17:28 -0500 (EST)
Date: Tue, 15 Feb 2000 10:17:28 -0500
From: John Hawkinson <jhawk@bbnplanet.com>
To: Daniel Senie <dts@senie.com>
Cc: Phil Karn <karn@QUALCOMM.COM>, IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
Message-ID: <20000215101728.R19709@jhawk-foo.bbnplanet.com>
References: <200002150004.QAA04489@servo.qualcomm.com> <38A8C268.33BAF536@senie.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.1.1i
In-Reply-To: <38A8C268.33BAF536@senie.com>; from dts@senie.com on Mon, Feb 14, 2000 at 10:05:12PM -0500
X-Loop: ietf@ietf.org

> From: Daniel Senie <dts@senie.com>
> Phil Karn wrote:

...

> > Being forced to tunnel not only increases the size of each packet, but
> > also entails suboptimum routing and reliance on yet more network
> > elements.  I use the new Linux policy routing mechanisms to tunnel
> > only those packets that have to be tunneled, which helps. But it would
> > sure be nice if I didn't have to tunnel my outbound packets at all.
> 
> Sorry. You're at the point where technology meets policy. Fact is, your
> host identifier in the IP stack is the source IP address. Enforcing the
> validity of that identifier has become necessary.

The correct "solution" here is for Phil to communicate with his
provider who presently does ingress filtering and notify them that he
is sourcing packets from a particular set of source addresses (because
of tunneling), and request they add these to the ingress filter list.

I think we recognize this may be politically infeasable for many
people to do, because tunneling is often used to circumvent
administrative restrictions, but that really is a different degree of
the problem.


More generally:

It seems to me that there has been a lot of wasted discussion on this
list on this topic. I think it is a well-accepted conclusion within
the provider community that ingress filtering is a necessary thing
(perhaps a "necessary evil" to some, perhaps a "good" to others).  In
the vast majority of cases, the router CPU resource consumption issues
are not relevent, either.

If people within the IETF feel differently, they should realize that
they are currently against recently-accepted-operational-practice.

I don't think everyone who has to date spoken is aware of that.

--jhawk



From owner-ietf-outbound@ietf.org  Tue Feb 15 10:27:28 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08780
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Feb 2000 10:27:28 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA08459;
	Tue, 15 Feb 2000 10:25:26 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id KAA08338
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 10:20:02 -0500 (EST)
Received: from jhawk-foo.bbnplanet.com (jhawk-foo.bbnplanet.com [199.94.208.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08188
	for <IETF@ietf.org>; Tue, 15 Feb 2000 10:17:34 -0500 (EST)
Received: (from jhawk@localhost)
	by jhawk-foo.bbnplanet.com (8.8.8+Sun/8.8.8) id KAA05581;
	Tue, 15 Feb 2000 10:17:28 -0500 (EST)
Date: Tue, 15 Feb 2000 10:17:28 -0500
From: John Hawkinson <jhawk@bbnplanet.com>
To: Daniel Senie <dts@senie.com>
Cc: Phil Karn <karn@QUALCOMM.COM>, IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
Message-ID: <20000215101728.R19709@jhawk-foo.bbnplanet.com>
References: <200002150004.QAA04489@servo.qualcomm.com> <38A8C268.33BAF536@senie.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.1.1i
In-Reply-To: <38A8C268.33BAF536@senie.com>; from dts@senie.com on Mon, Feb 14, 2000 at 10:05:12PM -0500
X-Loop: ietf@ietf.org

> From: Daniel Senie <dts@senie.com>
> Phil Karn wrote:

...

> > Being forced to tunnel not only increases the size of each packet, but
> > also entails suboptimum routing and reliance on yet more network
> > elements.  I use the new Linux policy routing mechanisms to tunnel
> > only those packets that have to be tunneled, which helps. But it would
> > sure be nice if I didn't have to tunnel my outbound packets at all.
> 
> Sorry. You're at the point where technology meets policy. Fact is, your
> host identifier in the IP stack is the source IP address. Enforcing the
> validity of that identifier has become necessary.

The correct "solution" here is for Phil to communicate with his
provider who presently does ingress filtering and notify them that he
is sourcing packets from a particular set of source addresses (because
of tunneling), and request they add these to the ingress filter list.

I think we recognize this may be politically infeasable for many
people to do, because tunneling is often used to circumvent
administrative restrictions, but that really is a different degree of
the problem.


More generally:

It seems to me that there has been a lot of wasted discussion on this
list on this topic. I think it is a well-accepted conclusion within
the provider community that ingress filtering is a necessary thing
(perhaps a "necessary evil" to some, perhaps a "good" to others).  In
the vast majority of cases, the router CPU resource consumption issues
are not relevent, either.

If people within the IETF feel differently, they should realize that
they are currently against recently-accepted-operational-practice.

I don't think everyone who has to date spoken is aware of that.

--jhawk



From owner-ietf-outbound  Tue Feb 15 10:30:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA09090
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 10:30:02 -0500 (EST)
Received: from localhost.localdomain ([216.52.68.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08448
	for <ietf@ietf.org>; Tue, 15 Feb 2000 10:21:07 -0500 (EST)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id KAA16756
	for <ietf@ietf.org>; Tue, 15 Feb 2000 10:20:54 -0500
Sender: francis@localhost.localdomain
Message-ID: <38A96ED6.F0E81DF1@ecal.com>
Date: Tue, 15 Feb 2000 10:20:54 -0500
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.2.12-20 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
References: <4.2.2.20000215110344.00a3e100@pop.dial.pipex.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Graham Klyne wrote:

> But I am still uncomfortable with it.  It implies that, somehow, any non-US
> participant is somehow a second class citizen, who is permitted to attend
> purely as a concession by the US elite whose organization this is.  Maybe
> that also is true -- but I don't have to like it.  I very much prefer the
> "pretense"

In other words, the pretense is self-fulfilling: by claiming (and striving) to
be global, the IETF avoids driving away non-US participants, which makes the
IETF more truly global.

--
/================================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.  |
|Chief Scientist |===============================================|
|eCal Corp.      |Yes, sir, we've graphed the data. It's a smiley|
|francis@ecal.com|face, sir.                                     |
\================================================================/





From owner-ietf-outbound@ietf.org  Tue Feb 15 10:36:28 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09596
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Feb 2000 10:36:28 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA08773;
	Tue, 15 Feb 2000 10:34:25 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id KAA09090
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 10:30:02 -0500 (EST)
Received: from localhost.localdomain ([216.52.68.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08448
	for <ietf@ietf.org>; Tue, 15 Feb 2000 10:21:07 -0500 (EST)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id KAA16756
	for <ietf@ietf.org>; Tue, 15 Feb 2000 10:20:54 -0500
Sender: francis@localhost.localdomain
Message-ID: <38A96ED6.F0E81DF1@ecal.com>
Date: Tue, 15 Feb 2000 10:20:54 -0500
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.2.12-20 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
References: <4.2.2.20000215110344.00a3e100@pop.dial.pipex.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Graham Klyne wrote:

> But I am still uncomfortable with it.  It implies that, somehow, any non-US
> participant is somehow a second class citizen, who is permitted to attend
> purely as a concession by the US elite whose organization this is.  Maybe
> that also is true -- but I don't have to like it.  I very much prefer the
> "pretense"

In other words, the pretense is self-fulfilling: by claiming (and striving) to
be global, the IETF avoids driving away non-US participants, which makes the
IETF more truly global.

--
/================================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.  |
|Chief Scientist |===============================================|
|eCal Corp.      |Yes, sir, we've graphed the data. It's a smiley|
|francis@ecal.com|face, sir.                                     |
\================================================================/





From owner-ietf-outbound  Tue Feb 15 10:50:37 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA10626
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 10:50:03 -0500 (EST)
Received: from mailext02.compaq.com (mailext02.compaq.com [207.18.199.33])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10158
	for <ietf@ietf.org>; Tue, 15 Feb 2000 10:44:27 -0500 (EST)
Received: by mailext02.compaq.com (Postfix, from userid 12345)
	id C52559A811; Tue, 15 Feb 2000 09:44:28 -0600 (CST)
Received: from mailint02.im.hou.compaq.com (mailint02.compaq.com [207.18.199.35])
	by mailext02.compaq.com (Postfix) with ESMTP id BFF0690D83
	for <ietf@ietf.org>; Tue, 15 Feb 2000 09:44:28 -0600 (CST)
Received: by mailint02.im.hou.compaq.com (Postfix, from userid 12345)
	id 891BABC4C9; Tue, 15 Feb 2000 09:44:21 -0600 (CST)
Received: from excreo-gh02.reo.cpqcorp.net (excreo-gh02.reo.cpqcorp.net [16.37.150.254])
	by mailint02.im.hou.compaq.com (Postfix) with ESMTP id 20661B2A43
	for <ietf@ietf.org>; Tue, 15 Feb 2000 09:44:21 -0600 (CST)
Received: by excreo-gh02.reo.cpqcorp.net with Internet Mail Service (5.5.2650.21)
	id <10YV4JTQ>; Tue, 15 Feb 2000 15:44:27 -0000
Message-ID: <71C4C55F198BD211B24F0000F842F15804B06C81@reoexc6.reo.cpqcorp.net>
From: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>
To: ietf@ietf.org
Subject: RE: IETF Adelaide and interim meetings for APPS WGs
Date: Tue, 15 Feb 2000 15:44:23 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

There is more than America out there ?

;-)



-----Original Message-----
From: John Stracke [mailto:francis@ECAL.COM]
Sent: Tuesday, February 15, 2000 3:21 PM
To: ietf@ietf.org
Subject: Re: IETF Adelaide and interim meetings for APPS WGs


Graham Klyne wrote:

> But I am still uncomfortable with it.  It implies that, somehow, any
non-US
> participant is somehow a second class citizen, who is permitted to attend
> purely as a concession by the US elite whose organization this is.  Maybe
> that also is true -- but I don't have to like it.  I very much prefer the
> "pretense"

In other words, the pretense is self-fulfilling: by claiming (and striving)
to
be global, the IETF avoids driving away non-US participants, which makes the
IETF more truly global.

--
/================================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.  |
|Chief Scientist |===============================================|
|eCal Corp.      |Yes, sir, we've graphed the data. It's a smiley|
|francis@ecal.com|face, sir.                                     |
\================================================================/




From owner-ietf-outbound@ietf.org  Tue Feb 15 10:58:32 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11105
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Feb 2000 10:58:31 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA09312;
	Tue, 15 Feb 2000 10:56:30 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id KAA10626
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 10:50:03 -0500 (EST)
Received: from mailext02.compaq.com (mailext02.compaq.com [207.18.199.33])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10158
	for <ietf@ietf.org>; Tue, 15 Feb 2000 10:44:27 -0500 (EST)
Received: by mailext02.compaq.com (Postfix, from userid 12345)
	id C52559A811; Tue, 15 Feb 2000 09:44:28 -0600 (CST)
Received: from mailint02.im.hou.compaq.com (mailint02.compaq.com [207.18.199.35])
	by mailext02.compaq.com (Postfix) with ESMTP id BFF0690D83
	for <ietf@ietf.org>; Tue, 15 Feb 2000 09:44:28 -0600 (CST)
Received: by mailint02.im.hou.compaq.com (Postfix, from userid 12345)
	id 891BABC4C9; Tue, 15 Feb 2000 09:44:21 -0600 (CST)
Received: from excreo-gh02.reo.cpqcorp.net (excreo-gh02.reo.cpqcorp.net [16.37.150.254])
	by mailint02.im.hou.compaq.com (Postfix) with ESMTP id 20661B2A43
	for <ietf@ietf.org>; Tue, 15 Feb 2000 09:44:21 -0600 (CST)
Received: by excreo-gh02.reo.cpqcorp.net with Internet Mail Service (5.5.2650.21)
	id <10YV4JTQ>; Tue, 15 Feb 2000 15:44:27 -0000
Message-ID: <71C4C55F198BD211B24F0000F842F15804B06C81@reoexc6.reo.cpqcorp.net>
From: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>
To: ietf@ietf.org
Subject: RE: IETF Adelaide and interim meetings for APPS WGs
Date: Tue, 15 Feb 2000 15:44:23 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

There is more than America out there ?

;-)



-----Original Message-----
From: John Stracke [mailto:francis@ECAL.COM]
Sent: Tuesday, February 15, 2000 3:21 PM
To: ietf@ietf.org
Subject: Re: IETF Adelaide and interim meetings for APPS WGs


Graham Klyne wrote:

> But I am still uncomfortable with it.  It implies that, somehow, any
non-US
> participant is somehow a second class citizen, who is permitted to attend
> purely as a concession by the US elite whose organization this is.  Maybe
> that also is true -- but I don't have to like it.  I very much prefer the
> "pretense"

In other words, the pretense is self-fulfilling: by claiming (and striving)
to
be global, the IETF avoids driving away non-US participants, which makes the
IETF more truly global.

--
/================================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.  |
|Chief Scientist |===============================================|
|eCal Corp.      |Yes, sir, we've graphed the data. It's a smiley|
|francis@ecal.com|face, sir.                                     |
\================================================================/




From owner-ietf-outbound  Tue Feb 15 11:30:33 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA12467
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 11:30:03 -0500 (EST)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12095
	for <ietf@ietf.org>; Tue, 15 Feb 2000 11:20:19 -0500 (EST)
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.0.Beta13/8.10.0.Beta13) with ESMTP id e1FGKH926982;
	Tue, 15 Feb 2000 11:20:17 -0500
Message-Id: <200002151620.e1FGKH926982@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>
cc: ietf@ietf.org
Subject: Re: IETF Adelaide and interim meetings for APPS WGs 
In-reply-to: Your message of "Tue, 15 Feb 2000 15:44:23 GMT."
             <71C4C55F198BD211B24F0000F842F15804B06C81@reoexc6.reo.cpqcorp.net> 
From: Valdis.Kletnieks@vt.edu
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <71C4C55F198BD211B24F0000F842F15804B06C81@reoexc6.reo.cpqcorp.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 15 Feb 2000 11:20:17 -0500
X-Loop: ietf@ietf.org

On Tue, 15 Feb 2000 15:44:23 GMT, "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>  said:
> There is more than America out there ?

There's a lot more out there.  It's to make up for the fact that in reality,
Idaho, Wyoming, and Rhode Island don't really exist - anybody claiming to
be from one of these 3 states is obviously an alien impostor. ;)

-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound@ietf.org  Tue Feb 15 11:37:24 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12901
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Feb 2000 11:37:24 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA10328;
	Tue, 15 Feb 2000 11:35:19 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id LAA12467
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 11:30:03 -0500 (EST)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12095
	for <ietf@ietf.org>; Tue, 15 Feb 2000 11:20:19 -0500 (EST)
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.0.Beta13/8.10.0.Beta13) with ESMTP id e1FGKH926982;
	Tue, 15 Feb 2000 11:20:17 -0500
Message-Id: <200002151620.e1FGKH926982@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>
cc: ietf@ietf.org
Subject: Re: IETF Adelaide and interim meetings for APPS WGs 
In-reply-to: Your message of "Tue, 15 Feb 2000 15:44:23 GMT."
             <71C4C55F198BD211B24F0000F842F15804B06C81@reoexc6.reo.cpqcorp.net> 
From: Valdis.Kletnieks@vt.edu
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <71C4C55F198BD211B24F0000F842F15804B06C81@reoexc6.reo.cpqcorp.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 15 Feb 2000 11:20:17 -0500
X-Loop: ietf@ietf.org

On Tue, 15 Feb 2000 15:44:23 GMT, "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>  said:
> There is more than America out there ?

There's a lot more out there.  It's to make up for the fact that in reality,
Idaho, Wyoming, and Rhode Island don't really exist - anybody claiming to
be from one of these 3 states is obviously an alien impostor. ;)

-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Tue Feb 15 11:50:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA13325
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 11:50:03 -0500 (EST)
Received: from arthur.axion.bt.co.uk (arthur.axion.bt.co.uk [132.146.5.4])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13156
	for <ietf@ietf.org>; Tue, 15 Feb 2000 11:44:24 -0500 (EST)
Received: from piglet.planet.bt.co.uk by arthur (local) with ESMTP;
          Tue, 15 Feb 2000 16:43:38 +0000
Received: from castor (castor [132.146.73.50]) 
          by piglet.planet.bt.co.uk (8.8.5/8.8.5/BT-SVR-1.0) with SMTP 
          id QAA29030 for <ietf@ietf.org>; Tue, 15 Feb 2000 16:40:26 GMT
Message-Id: <200002151640.QAA29030@piglet.planet.bt.co.uk>
Date: Tue, 15 Feb 2000 16:40:25 +0000 (GMT)
From: Iain Hanson <hansonik@PLANET.BT.CO.UK>
Reply-To: Iain Hanson <hansonik@PLANET.BT.CO.UK>
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: N7xmaMVc0OFGmJQ05Es69Q==
X-Mailer: dtmail 1.2.0 CDE Version 1.2 SunOS 5.6 sun4u sparc 
X-Loop: ietf@ietf.org

John Stracke wrote:

>In other words, the pretense is self-fulfilling: by claiming (and striving) to
>be global, the IETF avoids driving away non-US participants, which makes the
>IETF more truly global.

Definately!

/ikh



From owner-ietf-outbound@ietf.org  Tue Feb 15 11:56:46 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13533
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Feb 2000 11:56:46 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA11142;
	Tue, 15 Feb 2000 11:54:42 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id LAA13325
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 11:50:03 -0500 (EST)
Received: from arthur.axion.bt.co.uk (arthur.axion.bt.co.uk [132.146.5.4])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13156
	for <ietf@ietf.org>; Tue, 15 Feb 2000 11:44:24 -0500 (EST)
Received: from piglet.planet.bt.co.uk by arthur (local) with ESMTP;
          Tue, 15 Feb 2000 16:43:38 +0000
Received: from castor (castor [132.146.73.50]) 
          by piglet.planet.bt.co.uk (8.8.5/8.8.5/BT-SVR-1.0) with SMTP 
          id QAA29030 for <ietf@ietf.org>; Tue, 15 Feb 2000 16:40:26 GMT
Message-Id: <200002151640.QAA29030@piglet.planet.bt.co.uk>
Date: Tue, 15 Feb 2000 16:40:25 +0000 (GMT)
From: Iain Hanson <hansonik@PLANET.BT.CO.UK>
Reply-To: Iain Hanson <hansonik@PLANET.BT.CO.UK>
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: N7xmaMVc0OFGmJQ05Es69Q==
X-Mailer: dtmail 1.2.0 CDE Version 1.2 SunOS 5.6 sun4u sparc 
X-Loop: ietf@ietf.org

John Stracke wrote:

>In other words, the pretense is self-fulfilling: by claiming (and striving) to
>be global, the IETF avoids driving away non-US participants, which makes the
>IETF more truly global.

Definately!

/ikh



From owner-ietf-outbound  Tue Feb 15 12:00:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA13689
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 12:00:03 -0500 (EST)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13349
	for <IETF@ietf.org>; Tue, 15 Feb 2000 11:50:41 -0500 (EST)
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.0.Beta13/8.10.0.Beta13) with ESMTP id e1FGod928224;
	Tue, 15 Feb 2000 11:50:39 -0500
Message-Id: <200002151650.e1FGod928224@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Phil Karn <karn@qualcomm.com>
cc: IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks 
In-reply-to: Your message of "Mon, 14 Feb 2000 16:04:28 PST."
             <200002150004.QAA04489@servo.qualcomm.com> 
From: Valdis.Kletnieks@vt.edu
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <200002150004.QAA04489@servo.qualcomm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 15 Feb 2000 11:50:38 -0500
X-Loop: ietf@ietf.org

On Mon, 14 Feb 2000 16:04:28 PST, Phil Karn said:
> Source address ingress filtering is one of those ideas that seems like
> a good one when you first think about it, but it just doesn't pan out.
> It interferes with some perfectly legitimate activities, it doesn't
> really stop the bad guys, and it deflects attention away from the real
> solutions.

Well.. as soon as somebody presents us with "the real solution", we'll start
implementing.  In the meantime, filtering is the best we know how to do.

> In the case of MS-DOS (Multiple Source-Denial of Service) attacks like
> the ones we saw last week, we need to deploy better inter-router
> mechanisms to deal with congestion by moving the packet drop points as
> far upstream as possible toward the senders. And if these mechanisms
> can work for deliberate flooding attacks, they'll also deal with
> non-deliberate congestion.

The problem here is that there is often a limit to how far away you
can move the detection.  In the case of multiple sources, it's
*probable* that the inbound packets will arrive on as many as 5 to 20
different links, and not get aggregated onto one path until the
last-hop link to the victim's site.

And if you have 20 inbound links into a routing swamp, each one will
only see a 5% fluctiation in load in order to cause a 100% congestion
on the victim link.  If you move the detection 2 hops out, you may be
trying to spot a 1% ripple in the traffic, if there's 100 different
paths that far out.

The more hops you try to move the detection away, the smaller the
"ripple" you need to be able to detect *without a high rate of false
positives*.

There's another issue, in that if you're trying to do this 2-3 hops
out, you will need *secure* *low-bandwidth* communications regarding
who is talking to whom, at what rates.  And you get transitivity
problems - some of our border routers are 3 hops from a vBNS gateway,
and therefor would need to talk to them, plus are 3 hops from other
routers that are probably NOT going to want the vBNS information.  So
you end up with a ugly mess of many overlapping "circles" containing
different subsets of routers.  This gets you into key management
issues, and the like....

I'm sure there's other issues that need to be solved as well, these are
just the first few problems that come to mind...

-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech

P.S.  Please note that MS-DOS is the trademark of a *SINGLE*-source vendor
of denial of service ;)




From owner-ietf-outbound@ietf.org  Tue Feb 15 12:09:39 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14064
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Feb 2000 12:09:39 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA11682;
	Tue, 15 Feb 2000 12:07:35 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id MAA13689
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 12:00:03 -0500 (EST)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13349
	for <IETF@ietf.org>; Tue, 15 Feb 2000 11:50:41 -0500 (EST)
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.0.Beta13/8.10.0.Beta13) with ESMTP id e1FGod928224;
	Tue, 15 Feb 2000 11:50:39 -0500
Message-Id: <200002151650.e1FGod928224@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Phil Karn <karn@qualcomm.com>
cc: IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks 
In-reply-to: Your message of "Mon, 14 Feb 2000 16:04:28 PST."
             <200002150004.QAA04489@servo.qualcomm.com> 
From: Valdis.Kletnieks@vt.edu
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <200002150004.QAA04489@servo.qualcomm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 15 Feb 2000 11:50:38 -0500
X-Loop: ietf@ietf.org

On Mon, 14 Feb 2000 16:04:28 PST, Phil Karn said:
> Source address ingress filtering is one of those ideas that seems like
> a good one when you first think about it, but it just doesn't pan out.
> It interferes with some perfectly legitimate activities, it doesn't
> really stop the bad guys, and it deflects attention away from the real
> solutions.

Well.. as soon as somebody presents us with "the real solution", we'll start
implementing.  In the meantime, filtering is the best we know how to do.

> In the case of MS-DOS (Multiple Source-Denial of Service) attacks like
> the ones we saw last week, we need to deploy better inter-router
> mechanisms to deal with congestion by moving the packet drop points as
> far upstream as possible toward the senders. And if these mechanisms
> can work for deliberate flooding attacks, they'll also deal with
> non-deliberate congestion.

The problem here is that there is often a limit to how far away you
can move the detection.  In the case of multiple sources, it's
*probable* that the inbound packets will arrive on as many as 5 to 20
different links, and not get aggregated onto one path until the
last-hop link to the victim's site.

And if you have 20 inbound links into a routing swamp, each one will
only see a 5% fluctiation in load in order to cause a 100% congestion
on the victim link.  If you move the detection 2 hops out, you may be
trying to spot a 1% ripple in the traffic, if there's 100 different
paths that far out.

The more hops you try to move the detection away, the smaller the
"ripple" you need to be able to detect *without a high rate of false
positives*.

There's another issue, in that if you're trying to do this 2-3 hops
out, you will need *secure* *low-bandwidth* communications regarding
who is talking to whom, at what rates.  And you get transitivity
problems - some of our border routers are 3 hops from a vBNS gateway,
and therefor would need to talk to them, plus are 3 hops from other
routers that are probably NOT going to want the vBNS information.  So
you end up with a ugly mess of many overlapping "circles" containing
different subsets of routers.  This gets you into key management
issues, and the like....

I'm sure there's other issues that need to be solved as well, these are
just the first few problems that come to mind...

-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech

P.S.  Please note that MS-DOS is the trademark of a *SINGLE*-source vendor
of denial of service ;)




From owner-ietf-outbound  Tue Feb 15 12:10:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA14152
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 12:10:03 -0500 (EST)
Received: from smtpproxy1.mitre.org (mbunix.mitre.org [129.83.20.100])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13652
	for <ietf@ietf.org>; Tue, 15 Feb 2000 11:59:58 -0500 (EST)
Received: from avsrv1.mitre.org (avsrv1.mitre.org [129.83.20.58])
	by smtpproxy1.mitre.org (8.9.3/8.9.3) with ESMTP id LAA08542
	for <ietf@ietf.org>; Tue, 15 Feb 2000 11:59:48 -0500 (EST)
Received: from MAILHUB2 (mailhub2.mitre.org [129.83.221.18])
	by smtpsrv1.mitre.org (8.9.3/8.9.3) with ESMTP id LAA16086
	for <ietf@ietf.org>; Tue, 15 Feb 2000 11:59:06 -0500 (EST)
Received: from dhcp-105-228.mitre.org (128.29.105.228) by mailhub2.mitre.org with SMTP
        id 2687013; Tue, 15 Feb 2000 11:59:56 EST
Message-ID: <38A98688.B1636CE3@mitre.org>
Date: Tue, 15 Feb 2000 12:02:00 -0500
From: Kathy Dally <kdally@MITRE.ORG>
Organization: The MITRE Corporation
X-Mailer: Mozilla 4.61 [en]C-19990607M  (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
References: <200002142337.SAA00271@astro.cs.utk.edu>
Content-Type: multipart/mixed;
 boundary="------------3DEE6F37C7F078C676D79841"
X-Loop: ietf@ietf.org

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

Hi Keith!

Your message and actions are right on!!!!  In addition to the reasons
and consequences you mentioned, such behavior opens the IETF to
restraint of trade challenges at least in the U.S.

Thanks,
Kathy Dally
MITRE Corp.



Keith Moore wrote:
> 
> It has come to the attention of the Applications Area Directors
> that one or more Applications area working groups have elected
> to not meet in Adelaide, and instead to hold an "interim meeting"
> in the United States, presumably because of distance and/or cost issues.
> 
> IETF is an international organization, and it is IETF's longstanding
> practice to hold its meetings in various locations around the planet.
> This serves both to encourage wider participation in IETF and also
> to more fairly distribute travel costs and inconvenience (over time)
> among all participants.  The scheduleing of an interim WG meeting in
> the US in lieu of a WG meeting in Adelaide undermines this policy.
> This is insulting to non-US participants of IETF (many of whom have
> attended meetings in the US for years), embarassing to IETF as
> a whole, and a threat to IETF's international stature.
> 
> Even if a working group has few participants outside the United
> States, a working group does not work in isolation from other
> working groups.  Attendance at IETF meetings is an invaluable
> mechanism for cross-group collaboration.
> 
> RFC 2418 states:
> 
>    Interim meetings are subject to the
>    same rules for advance notification, reporting, open participation,
>    and process, which apply to other working group meetings.
> 
> Since normal working group meetings require advance notification
> via email to the entire IETF list, and the process for getting a meeting
> slot involves prior approval of the Area Directors, the same
> requirements apply to interim working group meetings.  Part of the
> reason for prior approval being required is to ensure that the
> locations of the meetings are not being chosen to favor certain
> participants over others.
> 
> There have been several violations of this policy since publication
> of RFC 2418.
> 
> Therefore,
> 
> - All interim meetings within the Applications Area which were not
>   previously and explicitly approved by the Applications Area Directors,
>   are hereby cancelled.
> 
> - No Applications Area group will hold any interim meeting prior
>   to April 15.
> 
> - No Applications Area group which does not hold a meeting in
>   Adelaide, will hold any interim meeting prior to July 31.
>   (i.e. prior to the Pittsburg IETF meeting)
> 
> - This applies to all face to face meetings held for the purpose
>   of conducting working group discussion and to which the working
>   group is invited, even if labelled "informal" or otherwise
>   labelled to distinguish them from official working group meetings.
> 
> - Exceptions to this policy may be made for recently chartered groups,
>   but Area Director approval is still required for such groups to
>   schedule interim meetings.
> 
> for the Applications Area Directors,
> 
> Keith Moore
--------------3DEE6F37C7F078C676D79841
Content-Type: text/x-vcard; charset=us-ascii;
 name="kdally.vcf"
Content-Description: Card for Kathy Dally
Content-Disposition: attachment;
 filename="kdally.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Dally;Kathy
tel;fax:(703) 883-7142
tel;work:(703) 883-6058
x-mozilla-html:FALSE
org:MITRE Corp.;Network and Communications Engineering
adr:;;1820 Dolley Madison Blvd., W650;McLean;VA;22102;U.S.A.
version:2.1
email;internet:kdally@mitre.org
title:Senior Technical Staff
x-mozilla-cpt:;-13520
fn:Kathy
end:vcard

--------------3DEE6F37C7F078C676D79841--




From owner-ietf-outbound@ietf.org  Tue Feb 15 12:16:28 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14621
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Feb 2000 12:16:28 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA11865;
	Tue, 15 Feb 2000 12:14:24 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id MAA14152
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 12:10:03 -0500 (EST)
Received: from smtpproxy1.mitre.org (mbunix.mitre.org [129.83.20.100])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13652
	for <ietf@ietf.org>; Tue, 15 Feb 2000 11:59:58 -0500 (EST)
Received: from avsrv1.mitre.org (avsrv1.mitre.org [129.83.20.58])
	by smtpproxy1.mitre.org (8.9.3/8.9.3) with ESMTP id LAA08542
	for <ietf@ietf.org>; Tue, 15 Feb 2000 11:59:48 -0500 (EST)
Received: from MAILHUB2 (mailhub2.mitre.org [129.83.221.18])
	by smtpsrv1.mitre.org (8.9.3/8.9.3) with ESMTP id LAA16086
	for <ietf@ietf.org>; Tue, 15 Feb 2000 11:59:06 -0500 (EST)
Received: from dhcp-105-228.mitre.org (128.29.105.228) by mailhub2.mitre.org with SMTP
        id 2687013; Tue, 15 Feb 2000 11:59:56 EST
Message-ID: <38A98688.B1636CE3@mitre.org>
Date: Tue, 15 Feb 2000 12:02:00 -0500
From: Kathy Dally <kdally@MITRE.ORG>
Organization: The MITRE Corporation
X-Mailer: Mozilla 4.61 [en]C-19990607M  (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
References: <200002142337.SAA00271@astro.cs.utk.edu>
Content-Type: multipart/mixed;
 boundary="------------3DEE6F37C7F078C676D79841"
X-Loop: ietf@ietf.org

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

Hi Keith!

Your message and actions are right on!!!!  In addition to the reasons
and consequences you mentioned, such behavior opens the IETF to
restraint of trade challenges at least in the U.S.

Thanks,
Kathy Dally
MITRE Corp.



Keith Moore wrote:
> 
> It has come to the attention of the Applications Area Directors
> that one or more Applications area working groups have elected
> to not meet in Adelaide, and instead to hold an "interim meeting"
> in the United States, presumably because of distance and/or cost issues.
> 
> IETF is an international organization, and it is IETF's longstanding
> practice to hold its meetings in various locations around the planet.
> This serves both to encourage wider participation in IETF and also
> to more fairly distribute travel costs and inconvenience (over time)
> among all participants.  The scheduleing of an interim WG meeting in
> the US in lieu of a WG meeting in Adelaide undermines this policy.
> This is insulting to non-US participants of IETF (many of whom have
> attended meetings in the US for years), embarassing to IETF as
> a whole, and a threat to IETF's international stature.
> 
> Even if a working group has few participants outside the United
> States, a working group does not work in isolation from other
> working groups.  Attendance at IETF meetings is an invaluable
> mechanism for cross-group collaboration.
> 
> RFC 2418 states:
> 
>    Interim meetings are subject to the
>    same rules for advance notification, reporting, open participation,
>    and process, which apply to other working group meetings.
> 
> Since normal working group meetings require advance notification
> via email to the entire IETF list, and the process for getting a meeting
> slot involves prior approval of the Area Directors, the same
> requirements apply to interim working group meetings.  Part of the
> reason for prior approval being required is to ensure that the
> locations of the meetings are not being chosen to favor certain
> participants over others.
> 
> There have been several violations of this policy since publication
> of RFC 2418.
> 
> Therefore,
> 
> - All interim meetings within the Applications Area which were not
>   previously and explicitly approved by the Applications Area Directors,
>   are hereby cancelled.
> 
> - No Applications Area group will hold any interim meeting prior
>   to April 15.
> 
> - No Applications Area group which does not hold a meeting in
>   Adelaide, will hold any interim meeting prior to July 31.
>   (i.e. prior to the Pittsburg IETF meeting)
> 
> - This applies to all face to face meetings held for the purpose
>   of conducting working group discussion and to which the working
>   group is invited, even if labelled "informal" or otherwise
>   labelled to distinguish them from official working group meetings.
> 
> - Exceptions to this policy may be made for recently chartered groups,
>   but Area Director approval is still required for such groups to
>   schedule interim meetings.
> 
> for the Applications Area Directors,
> 
> Keith Moore
--------------3DEE6F37C7F078C676D79841
Content-Type: text/x-vcard; charset=us-ascii;
 name="kdally.vcf"
Content-Description: Card for Kathy Dally
Content-Disposition: attachment;
 filename="kdally.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Dally;Kathy
tel;fax:(703) 883-7142
tel;work:(703) 883-6058
x-mozilla-html:FALSE
org:MITRE Corp.;Network and Communications Engineering
adr:;;1820 Dolley Madison Blvd., W650;McLean;VA;22102;U.S.A.
version:2.1
email;internet:kdally@mitre.org
title:Senior Technical Staff
x-mozilla-cpt:;-13520
fn:Kathy
end:vcard

--------------3DEE6F37C7F078C676D79841--




From owner-ietf-outbound  Tue Feb 15 12:30:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA15262
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 12:30:03 -0500 (EST)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14966
	for <IETF@ietf.org>; Tue, 15 Feb 2000 12:22:46 -0500 (EST)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id KAA28768
	for IETF@ietf.org  env-from <vjs>;
	Tue, 15 Feb 2000 10:22:46 -0700 (MST)
Date: Tue, 15 Feb 2000 10:22:46 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200002151722.KAA28768@calcite.rhyolite.com>
To: IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
X-Loop: ietf@ietf.org

> From: Valdis.Kletnieks@vt.edu

> ...
> Well.. as soon as somebody presents us with "the real solution", we'll start
> implementing.  In the meantime, filtering is the best we know how to do.
> ...

I really wish "we" actually knew how to filter.

Just as I feared when the news broke, I'm seeing more paths where neither
traceroute nor ping work, apparently because some of "us" are so expert
that we turn off all of ICMP, and never mind intermittent blackholes from
Path MTU Discovery or diagnosing routing or other mere technical problems.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound@ietf.org  Tue Feb 15 12:37:56 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15661
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Feb 2000 12:37:55 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA12494;
	Tue, 15 Feb 2000 12:35:47 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id MAA15262
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 12:30:03 -0500 (EST)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14966
	for <IETF@ietf.org>; Tue, 15 Feb 2000 12:22:46 -0500 (EST)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id KAA28768
	for IETF@ietf.org  env-from <vjs>;
	Tue, 15 Feb 2000 10:22:46 -0700 (MST)
Date: Tue, 15 Feb 2000 10:22:46 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200002151722.KAA28768@calcite.rhyolite.com>
To: IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
X-Loop: ietf@ietf.org

> From: Valdis.Kletnieks@vt.edu

> ...
> Well.. as soon as somebody presents us with "the real solution", we'll start
> implementing.  In the meantime, filtering is the best we know how to do.
> ...

I really wish "we" actually knew how to filter.

Just as I feared when the news broke, I'm seeing more paths where neither
traceroute nor ping work, apparently because some of "us" are so expert
that we turn off all of ICMP, and never mind intermittent blackholes from
Path MTU Discovery or diagnosing routing or other mere technical problems.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Tue Feb 15 12:40:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA15741
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 12:40:03 -0500 (EST)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15019
	for <ietf@ietf.org>; Tue, 15 Feb 2000 12:24:22 -0500 (EST)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id KAA28787
	env-from <vjs>;
	Tue, 15 Feb 2000 10:24:21 -0700 (MST)
Date: Tue, 15 Feb 2000 10:24:21 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200002151724.KAA28787@calcite.rhyolite.com>
To: GK@Dial.pipex.com, vjs@calcite.rhyolite.com
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
Cc: ietf@ietf.org
X-Loop: ietf@ietf.org

> From: Graham Klyne <GK@Dial.pipex.com>

> >In other words and politically correct pretense asside, the IETF is not
> >an international organization.  ...

> As a non-US IETF participant, I found this statement mildly insulting.  But 
> then I have to ask myself "why?".  It is true that a majority of IETF 
> participation is US-based.  It is true that the IETF secretariat is wholly 
> US-based.  It is true that the IETF is an outgrowth of a US national 
> organization.  So on the face of it, your statement appears entirely true.
>
> But I am still uncomfortable with it.

Except for the cognitive dissonance caused by the political fiction,
why feel insulted?  There are many non-U.S. institutions that variously
refuse, deign to allow, or eagerly invite and encourage participation
by U.S. citizens.  If the IETF only grudgingly allowed non-U.S.
participation, you might have reason to feel insulted.

The purpose of political correctness is to allow people to ignore and
not deal with inconvenient facts.  That more than one person found my
statement offensive instead of silly shows its accuracy.  Indignation
is the mildest reaction to attacks on political correctness.  In the
U.S. we laws against disturbing some fig leaves, the Constitution not
withstanding.  I'll not be specific, since those messes are irrelevant,
and I don't want to be lynched.

>                                      It implies that, somehow, any non-US 
> participant is somehow a second class citizen, who is permitted to attend 
> purely as a concession by the US elite whose organization this is.  Maybe 
> that also is true -- but I don't have to like it.  

From where are the notions of "US elite" and "second class"?  None of the
real IETF participants I've met have considered themselves members of an
elite, aside from occasional weaknesses in suffering fools gladly.  Like
many U.S. institutions, the IETF has viewed non-U.S. participants as
wonderful, as showing the IETF matters.  Recall that the cachet of non-U.S.
origin was a major part of the attraction of the ISO OSI protocol suite.

>                                                  I very much prefer the 
> "pretense" that the IETF is an organization that provides technical 
> direction for a truly global facility, and that it aspires to do so for the 
> benefit of all the world's people, with equal status and consideration 
> allowed to any who can participate, from wherever they may originate.

Exactly.


] From: John Stracke <francis@ecal.com>

] In other words, the pretense is self-fulfilling: by claiming (and striving) to
] be global, the IETF avoids driving away non-US participants, which makes the
] IETF more truly global.

I don't know about self-fulfilling, but eventually the IETF might
become an international organization.  If it avoids the worst
aspects of the ITU and the U.N., that could be a good thing.

The biggest obstacle to the IETF becoming more international are the
meetings, no matter where they are held.  A major reason the IETF is
as international as it is is its history of emphasizing email discussions.
It can be hard to notice national origin in email.  As that emphasis
declines (and it has significantly in practice if not rule), the IETF
risks becoming more instead of less insular and elitist.  That a
meeting in Washington is a long trip from Japan is not mitigated by
the distance to Australia from Europe.  SMTP doesn't care.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound@ietf.org  Tue Feb 15 12:46:38 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15960
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Feb 2000 12:46:37 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA12746;
	Tue, 15 Feb 2000 12:44:36 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id MAA15741
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 12:40:03 -0500 (EST)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15019
	for <ietf@ietf.org>; Tue, 15 Feb 2000 12:24:22 -0500 (EST)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id KAA28787
	env-from <vjs>;
	Tue, 15 Feb 2000 10:24:21 -0700 (MST)
Date: Tue, 15 Feb 2000 10:24:21 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200002151724.KAA28787@calcite.rhyolite.com>
To: GK@Dial.pipex.com, vjs@calcite.rhyolite.com
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
Cc: ietf@ietf.org
X-Loop: ietf@ietf.org

> From: Graham Klyne <GK@Dial.pipex.com>

> >In other words and politically correct pretense asside, the IETF is not
> >an international organization.  ...

> As a non-US IETF participant, I found this statement mildly insulting.  But 
> then I have to ask myself "why?".  It is true that a majority of IETF 
> participation is US-based.  It is true that the IETF secretariat is wholly 
> US-based.  It is true that the IETF is an outgrowth of a US national 
> organization.  So on the face of it, your statement appears entirely true.
>
> But I am still uncomfortable with it.

Except for the cognitive dissonance caused by the political fiction,
why feel insulted?  There are many non-U.S. institutions that variously
refuse, deign to allow, or eagerly invite and encourage participation
by U.S. citizens.  If the IETF only grudgingly allowed non-U.S.
participation, you might have reason to feel insulted.

The purpose of political correctness is to allow people to ignore and
not deal with inconvenient facts.  That more than one person found my
statement offensive instead of silly shows its accuracy.  Indignation
is the mildest reaction to attacks on political correctness.  In the
U.S. we laws against disturbing some fig leaves, the Constitution not
withstanding.  I'll not be specific, since those messes are irrelevant,
and I don't want to be lynched.

>                                      It implies that, somehow, any non-US 
> participant is somehow a second class citizen, who is permitted to attend 
> purely as a concession by the US elite whose organization this is.  Maybe 
> that also is true -- but I don't have to like it.  

From where are the notions of "US elite" and "second class"?  None of the
real IETF participants I've met have considered themselves members of an
elite, aside from occasional weaknesses in suffering fools gladly.  Like
many U.S. institutions, the IETF has viewed non-U.S. participants as
wonderful, as showing the IETF matters.  Recall that the cachet of non-U.S.
origin was a major part of the attraction of the ISO OSI protocol suite.

>                                                  I very much prefer the 
> "pretense" that the IETF is an organization that provides technical 
> direction for a truly global facility, and that it aspires to do so for the 
> benefit of all the world's people, with equal status and consideration 
> allowed to any who can participate, from wherever they may originate.

Exactly.


] From: John Stracke <francis@ecal.com>

] In other words, the pretense is self-fulfilling: by claiming (and striving) to
] be global, the IETF avoids driving away non-US participants, which makes the
] IETF more truly global.

I don't know about self-fulfilling, but eventually the IETF might
become an international organization.  If it avoids the worst
aspects of the ITU and the U.N., that could be a good thing.

The biggest obstacle to the IETF becoming more international are the
meetings, no matter where they are held.  A major reason the IETF is
as international as it is is its history of emphasizing email discussions.
It can be hard to notice national origin in email.  As that emphasis
declines (and it has significantly in practice if not rule), the IETF
risks becoming more instead of less insular and elitist.  That a
meeting in Washington is a long trip from Japan is not mitigated by
the distance to Australia from Europe.  SMTP doesn't care.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Tue Feb 15 13:00:28 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA16424
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 13:00:04 -0500 (EST)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16264
	for <ietf@ietf.org>; Tue, 15 Feb 2000 12:55:44 -0500 (EST)
Received: from sp3at21.hursley.ibm.com (sp3at21.hursley.ibm.com [9.20.45.21]) by mail-gw.hursley.ibm.com (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id RAA113208; Tue, 15 Feb 2000 17:55:11 GMT
Received: from hursley.ibm.com ([9.242.210.10]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id RAA19966; Tue, 15 Feb 2000 17:55:08 GMT
Message-ID: <38A96EB9.2B32028A@hursley.ibm.com>
Date: Tue, 15 Feb 2000 09:20:25 -0600
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en,fr
MIME-Version: 1.0
To: Vernon Schryver <vjs@calcite.rhyolite.com>
CC: ietf@ietf.org
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
References: <200002150337.UAA13992@calcite.rhyolite.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Vern,

The IETF has no dependency of any kind on any government and as you yourself
observed it does its decision taking in cyberspace, not geographical space.
It is as international as any organization I have ever known, and I spent more 
20 years working for an international treaty organisation.

I agree with Fred. Objecting to crossing the Pacific once in 47 meetings
is not right. (Not talking about you personally of course.)

   Brian



From owner-ietf-outbound@ietf.org  Tue Feb 15 13:08:55 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16768
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Feb 2000 13:08:54 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA13327;
	Tue, 15 Feb 2000 13:06:51 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id NAA16424
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 13:00:04 -0500 (EST)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16264
	for <ietf@ietf.org>; Tue, 15 Feb 2000 12:55:44 -0500 (EST)
Received: from sp3at21.hursley.ibm.com (sp3at21.hursley.ibm.com [9.20.45.21]) by mail-gw.hursley.ibm.com (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id RAA113208; Tue, 15 Feb 2000 17:55:11 GMT
Received: from hursley.ibm.com ([9.242.210.10]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id RAA19966; Tue, 15 Feb 2000 17:55:08 GMT
Message-ID: <38A96EB9.2B32028A@hursley.ibm.com>
Date: Tue, 15 Feb 2000 09:20:25 -0600
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en,fr
MIME-Version: 1.0
To: Vernon Schryver <vjs@calcite.rhyolite.com>
CC: ietf@ietf.org
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
References: <200002150337.UAA13992@calcite.rhyolite.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Vern,

The IETF has no dependency of any kind on any government and as you yourself
observed it does its decision taking in cyberspace, not geographical space.
It is as international as any organization I have ever known, and I spent more 
20 years working for an international treaty organisation.

I agree with Fred. Objecting to crossing the Pacific once in 47 meetings
is not right. (Not talking about you personally of course.)

   Brian



From owner-ietf-outbound  Tue Feb 15 13:20:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA17063
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 13:20:02 -0500 (EST)
Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA16967
	for <ietf@ietf.org>; Tue, 15 Feb 2000 13:15:56 -0500 (EST)
Received: from grazie.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.20230-0@bells.cs.ucl.ac.uk>; Tue, 15 Feb 2000 18:15:51 +0000
To: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>
cc: ietf@ietf.org
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
In-reply-to: Your message of "Tue, 15 Feb 2000 15:44:23 GMT." <71C4C55F198BD211B24F0000F842F15804B06C81@reoexc6.reo.cpqcorp.net>
Date: Tue, 15 Feb 2000 18:15:47 +0000
Message-ID: <2480.950638547@cs.ucl.ac.uk>
From: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
X-Loop: ietf@ietf.org


In message <71C4C55F198BD211B24F0000F842F15804B06C81@reoexc6.reo.cpqcorp.net>, 
"Parkinson, Jonathan" typed:

 >>There is more than America out there ?
 >>;-)
 

you mean america still exists - i thought it was actually a myth like
atlantis....


 >>
 >>
 >>-----Original Message-----
 >>From: John Stracke [mailto:francis@ECAL.COM]
 >>Sent: Tuesday, February 15, 2000 3:21 PM
 >>To: ietf@ietf.org
 >>Subject: Re: IETF Adelaide and interim meetings for APPS WGs
 >>
 >>
 >>Graham Klyne wrote:
 >>
 >>> But I am still uncomfortable with it.  It implies that, somehow, any
 >>non-US
 >>> participant is somehow a second class citizen, who is permitted to attend
 >>> purely as a concession by the US elite whose organization this is.  Maybe
 >>> that also is true -- but I don't have to like it.  I very much prefer the
 >>> "pretense"
 >>
 >>In other words, the pretense is self-fulfilling: by claiming (and striving)
 >>to
 >>be global, the IETF avoids driving away non-US participants, which makes the
 >>IETF more truly global.
 >>
 >>--
 >>/================================================================\
 >>|John Stracke    | http://www.ecal.com |My opinions are my own.  |
 >>|Chief Scientist |===============================================|
 >>|eCal Corp.      |Yes, sir, we've graphed the data. It's a smiley|
 >>|francis@ecal.com|face, sir.                                     |
 >>\================================================================/
 >>
 >>

 cheers

   jon



From owner-ietf-outbound@ietf.org  Tue Feb 15 13:26:38 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17268
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Feb 2000 13:26:38 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA13755;
	Tue, 15 Feb 2000 13:24:34 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id NAA17063
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 13:20:02 -0500 (EST)
Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA16967
	for <ietf@ietf.org>; Tue, 15 Feb 2000 13:15:56 -0500 (EST)
Received: from grazie.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.20230-0@bells.cs.ucl.ac.uk>; Tue, 15 Feb 2000 18:15:51 +0000
To: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>
cc: ietf@ietf.org
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
In-reply-to: Your message of "Tue, 15 Feb 2000 15:44:23 GMT." <71C4C55F198BD211B24F0000F842F15804B06C81@reoexc6.reo.cpqcorp.net>
Date: Tue, 15 Feb 2000 18:15:47 +0000
Message-ID: <2480.950638547@cs.ucl.ac.uk>
From: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
X-Loop: ietf@ietf.org


In message <71C4C55F198BD211B24F0000F842F15804B06C81@reoexc6.reo.cpqcorp.net>, 
"Parkinson, Jonathan" typed:

 >>There is more than America out there ?
 >>;-)
 

you mean america still exists - i thought it was actually a myth like
atlantis....


 >>
 >>
 >>-----Original Message-----
 >>From: John Stracke [mailto:francis@ECAL.COM]
 >>Sent: Tuesday, February 15, 2000 3:21 PM
 >>To: ietf@ietf.org
 >>Subject: Re: IETF Adelaide and interim meetings for APPS WGs
 >>
 >>
 >>Graham Klyne wrote:
 >>
 >>> But I am still uncomfortable with it.  It implies that, somehow, any
 >>non-US
 >>> participant is somehow a second class citizen, who is permitted to attend
 >>> purely as a concession by the US elite whose organization this is.  Maybe
 >>> that also is true -- but I don't have to like it.  I very much prefer the
 >>> "pretense"
 >>
 >>In other words, the pretense is self-fulfilling: by claiming (and striving)
 >>to
 >>be global, the IETF avoids driving away non-US participants, which makes the
 >>IETF more truly global.
 >>
 >>--
 >>/================================================================\
 >>|John Stracke    | http://www.ecal.com |My opinions are my own.  |
 >>|Chief Scientist |===============================================|
 >>|eCal Corp.      |Yes, sir, we've graphed the data. It's a smiley|
 >>|francis@ecal.com|face, sir.                                     |
 >>\================================================================/
 >>
 >>

 cheers

   jon



From owner-ietf-outbound  Tue Feb 15 13:30:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA17367
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 13:30:02 -0500 (EST)
Received: from ns-inetext.inet.com (ns-inetext.inet.com [199.171.211.140])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17101
	for <ietf@ietf.org>; Tue, 15 Feb 2000 13:20:56 -0500 (EST)
Received: from harpo.inetint.com (harpo [172.16.99.60])
	by ns-inetext.inet.com (8.9.2/8.9.2) with ESMTP id MAA06194
	for <ietf@ietf.org>; Tue, 15 Feb 2000 12:19:38 -0600 (CST)
Received: from inet.com ([172.16.63.49]) by harpo.inetint.com
          (Netscape Messaging Server 3.6)  with ESMTP id AAA1751
          for <ietf@ietf.org>; Tue, 15 Feb 2000 12:24:58 -0600
Message-ID: <38A998FC.72501901@inet.com>
Date: Tue, 15 Feb 2000 12:20:44 -0600
From: Mart Nurmet <mart.nurmet@inet.com>
Organization: Product Line Management
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
References: <200002142337.SAA00271@astro.cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Keith:

How do I go about geting the schedule for the meetings for the rest of the
year?

I'm new to this forum and will be the Inet Technologies representative in
the future.

Best regards,
Mart Nurmet
972 543-3791



From owner-ietf-outbound@ietf.org  Tue Feb 15 13:36:40 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17719
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Feb 2000 13:36:40 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA14046;
	Tue, 15 Feb 2000 13:34:35 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id NAA17367
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 13:30:02 -0500 (EST)
Received: from ns-inetext.inet.com (ns-inetext.inet.com [199.171.211.140])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17101
	for <ietf@ietf.org>; Tue, 15 Feb 2000 13:20:56 -0500 (EST)
Received: from harpo.inetint.com (harpo [172.16.99.60])
	by ns-inetext.inet.com (8.9.2/8.9.2) with ESMTP id MAA06194
	for <ietf@ietf.org>; Tue, 15 Feb 2000 12:19:38 -0600 (CST)
Received: from inet.com ([172.16.63.49]) by harpo.inetint.com
          (Netscape Messaging Server 3.6)  with ESMTP id AAA1751
          for <ietf@ietf.org>; Tue, 15 Feb 2000 12:24:58 -0600
Message-ID: <38A998FC.72501901@inet.com>
Date: Tue, 15 Feb 2000 12:20:44 -0600
From: Mart Nurmet <mart.nurmet@inet.com>
Organization: Product Line Management
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
References: <200002142337.SAA00271@astro.cs.utk.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Keith:

How do I go about geting the schedule for the meetings for the rest of the
year?

I'm new to this forum and will be the Inet Technologies representative in
the future.

Best regards,
Mart Nurmet
972 543-3791



From owner-ietf-outbound  Tue Feb 15 13:40:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA17877
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 13:40:02 -0500 (EST)
Received: from watsun.cc.columbia.edu (IDENT:cu51491@watsun.cc.columbia.edu [128.59.39.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17388
	for <ietf@ietf.org>; Tue, 15 Feb 2000 13:30:07 -0500 (EST)
Received: (from jaltman@localhost)
	by watsun.cc.columbia.edu (8.8.5/8.8.5) id NAA11739
	for ietf@ietf.org; Tue, 15 Feb 2000 13:30:06 -0500 (EST)
Date: Tue, 15 Feb 2000 13:30:05 EST
From: Jeffrey Altman <jaltman@columbia.edu>
Reply-To: jaltman@columbia.edu
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
To: ietf@ietf.org
Message-ID: <CMM.0.90.4.950639405.jaltman@watsun.cc.columbia.edu>
X-Loop: ietf@ietf.org

The problem I have with the Adelaide meeting is very simple.  With so
few working groups holding sessions, I can't justify making the trip.
This would be true for a meeting at any location more than 400 miles
away.  If only one group that I am interested in is holding a session,
I can't go.  The powers that be just won't approve it.

So the side effect of not holding a session is that not only have the
working groups decided that they do not want the interest and
participation of non-U.S. members, but they don't want the interest
and participation of U.S. members either.  

This leads me to question why the working group is in fact a working
group in the IETF.  



    Jeffrey Altman * Sr.Software Designer * Kermit-95 for Win32 and OS/2
                 The Kermit Project * Columbia University
              612 West 115th St #716 * New York, NY * 10025
  http://www.kermit-project.org/k95.html * kermit-support@kermit-project.org




From owner-ietf-outbound@ietf.org  Tue Feb 15 13:49:47 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18210
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Feb 2000 13:49:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA14327;
	Tue, 15 Feb 2000 13:47:41 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id NAA17877
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 13:40:02 -0500 (EST)
Received: from watsun.cc.columbia.edu (IDENT:cu51491@watsun.cc.columbia.edu [128.59.39.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17388
	for <ietf@ietf.org>; Tue, 15 Feb 2000 13:30:07 -0500 (EST)
Received: (from jaltman@localhost)
	by watsun.cc.columbia.edu (8.8.5/8.8.5) id NAA11739
	for ietf@ietf.org; Tue, 15 Feb 2000 13:30:06 -0500 (EST)
Date: Tue, 15 Feb 2000 13:30:05 EST
From: Jeffrey Altman <jaltman@columbia.edu>
Reply-To: jaltman@columbia.edu
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
To: ietf@ietf.org
Message-ID: <CMM.0.90.4.950639405.jaltman@watsun.cc.columbia.edu>
X-Loop: ietf@ietf.org

The problem I have with the Adelaide meeting is very simple.  With so
few working groups holding sessions, I can't justify making the trip.
This would be true for a meeting at any location more than 400 miles
away.  If only one group that I am interested in is holding a session,
I can't go.  The powers that be just won't approve it.

So the side effect of not holding a session is that not only have the
working groups decided that they do not want the interest and
participation of non-U.S. members, but they don't want the interest
and participation of U.S. members either.  

This leads me to question why the working group is in fact a working
group in the IETF.  



    Jeffrey Altman * Sr.Software Designer * Kermit-95 for Win32 and OS/2
                 The Kermit Project * Columbia University
              612 West 115th St #716 * New York, NY * 10025
  http://www.kermit-project.org/k95.html * kermit-support@kermit-project.org




From owner-ietf-outbound  Tue Feb 15 14:10:25 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA19025
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 14:10:02 -0500 (EST)
Received: from alcove.wittsend.com (IDENT:root@alcove.wittsend.com [130.205.0.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18582
	for <IETF@ietf.org>; Tue, 15 Feb 2000 14:00:16 -0500 (EST)
Received: (from mhw@localhost)
	by alcove.wittsend.com (8.9.3/8.9.3) id NAA21890;
	Tue, 15 Feb 2000 13:59:58 -0500
Date: Tue, 15 Feb 2000 13:59:58 -0500
From: "Michael H. Warfield" <mhw@wittsend.com>
To: Vernon Schryver <vjs@CALCITE.RHYOLITE.COM>
Cc: IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
Message-ID: <20000215135958.F8192@alcove.wittsend.com>
References: <200002151722.KAA28768@calcite.rhyolite.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.1.2i
In-Reply-To: <200002151722.KAA28768@calcite.rhyolite.com>; from vjs@CALCITE.RHYOLITE.COM on Tue, Feb 15, 2000 at 10:22:46AM -0700
X-Loop: ietf@ietf.org

On Tue, Feb 15, 2000 at 10:22:46AM -0700, Vernon Schryver wrote:
> > From: Valdis.Kletnieks@vt.edu

> > ...
> > Well.. as soon as somebody presents us with "the real solution", we'll start
> > implementing.  In the meantime, filtering is the best we know how to do.
> > ...

> I really wish "we" actually knew how to filter.

> Just as I feared when the news broke, I'm seeing more paths where neither
> traceroute nor ping work, apparently because some of "us" are so expert
> that we turn off all of ICMP, and never mind intermittent blackholes from
> Path MTU Discovery or diagnosing routing or other mere technical problems.

	But some of us turn off ICMP except for ICMP_FRAG_NEEDED and keep
MTU discovery alive while cutting off the ICMP food fights and script
kiddie probes that seem to be endemic in our current mess.

	You betcha traceroute and ping are broken (figuratively and
literally).  Just as broken as I can make them.  You don't need to be
tracerouting or pinging into my network and that's my choice to make.
I can break them without breaking MTU discovery.  You want to diagnose
routing or other technical problems, why aren't you contacting me?

	You cut off ICMP_ECHOREPLY and all but a tightly restricted set
of UDP and you have just starved these DDoS zombies of the vast majority
of their communications facility.  TCP is much easier to trace, if they
fall back to that (I don't see how TFN2K could - it utilizes a blind
forward-only non-responding channel).  Blocking spoofed packets won't
do nearly as good a job since a lot of the packets aren't spoofed.  Doesn't
help at all in some examples I have some first hand experience with.

	Edge filtering and spoof protection would have been absolutely no
help for one site I was help with forensics after TFN2K.  They were a
source of ICMP_ECHOREPLY packets in one of the storms.  We STILL
haven't located the zombie amongst the hundreds of potential Windows
boxes (we already cleared the single Solaris and single RedHat box on
the subnet and TFN2K is known to run on Windows).

	No spoofed packets crossed router boundries.  The TFN2K command
sequence was executed well before anyone noticed any bandwidth anomolies,
so there's no track back to the master.  (Who would have noticed 20
ICMP_ECHOREPLY packets that merely didn't correspond to any internal
request?)  The slaves shut down after two hours and before the admins
realized that the smurf was being generated internally.  They did find a
bug in a router blocking of directed broadcasts.  That red-herring slowed
them down, thinking it was externally generated.  No trace back of the
smurf triggers back to the zombie (having that MAC address would do wonders)
was caught since it quiet before they started sniffing the network.

	They broke it's back by blocking ICMP_ECHO and ICMP_ECHOREPLY
(fortunately, this attack was not using one of the UDP options).

	I have not heard if any of the TFN scanners have turned up
anything yet.  TFN2K zombies are a real bummer since it can lay dormant
on a network until triggered and they don't reply back to the master.
These guys are on a machine by machine, file by file snark hunt looking
for files that could be any one of a number of names on systems that are
all different anyways.  Don't you know they're having fun?

	The attackers are gaining in sophistication.  We are begining to
see effort at "covert channels" for communications.  The tricks of
communicating via ICMP_ECHOREPLY packets with commands in the payload
and sending blobs of forward only commands with no reverse channel
responses are just examples.  How long before they start sneaking past
those defenses by sending ICMP_UNREACHABLE/ICMP_FRAG_NEEDED with
a command data payload?

	They don't have to resort to spoofing to pull off a lot of this.
Long command time delays, covert channels, and unidirection command
direction can make it just as difficult to track down as spoofing.

	Diagnostics are fine.  Performance is fine.  Diagnostics and/or
performance at the expense of security and/or robustness is not.

> Vernon Schryver    vjs@rhyolite.com

	Mike
-- 
 Michael H. Warfield    |  (770) 985-6132   |  mhw@WittsEnd.com
  (The Mad Wizard)      |  (770) 331-2437   |  http://www.wittsend.com/mhw/
  NIC whois:  MHW9      |  An optimist believes we live in the best of all
 PGP Key: 0xDF1DD471    |  possible worlds.  A pessimist is sure of it!



From owner-ietf-outbound@ietf.org  Tue Feb 15 14:20:07 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19282
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Feb 2000 14:20:03 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA15124;
	Tue, 15 Feb 2000 14:17:59 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id OAA19025
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 14:10:02 -0500 (EST)
Received: from alcove.wittsend.com (IDENT:root@alcove.wittsend.com [130.205.0.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18582
	for <IETF@ietf.org>; Tue, 15 Feb 2000 14:00:16 -0500 (EST)
Received: (from mhw@localhost)
	by alcove.wittsend.com (8.9.3/8.9.3) id NAA21890;
	Tue, 15 Feb 2000 13:59:58 -0500
Date: Tue, 15 Feb 2000 13:59:58 -0500
From: "Michael H. Warfield" <mhw@wittsend.com>
To: Vernon Schryver <vjs@CALCITE.RHYOLITE.COM>
Cc: IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
Message-ID: <20000215135958.F8192@alcove.wittsend.com>
References: <200002151722.KAA28768@calcite.rhyolite.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.1.2i
In-Reply-To: <200002151722.KAA28768@calcite.rhyolite.com>; from vjs@CALCITE.RHYOLITE.COM on Tue, Feb 15, 2000 at 10:22:46AM -0700
X-Loop: ietf@ietf.org

On Tue, Feb 15, 2000 at 10:22:46AM -0700, Vernon Schryver wrote:
> > From: Valdis.Kletnieks@vt.edu

> > ...
> > Well.. as soon as somebody presents us with "the real solution", we'll start
> > implementing.  In the meantime, filtering is the best we know how to do.
> > ...

> I really wish "we" actually knew how to filter.

> Just as I feared when the news broke, I'm seeing more paths where neither
> traceroute nor ping work, apparently because some of "us" are so expert
> that we turn off all of ICMP, and never mind intermittent blackholes from
> Path MTU Discovery or diagnosing routing or other mere technical problems.

	But some of us turn off ICMP except for ICMP_FRAG_NEEDED and keep
MTU discovery alive while cutting off the ICMP food fights and script
kiddie probes that seem to be endemic in our current mess.

	You betcha traceroute and ping are broken (figuratively and
literally).  Just as broken as I can make them.  You don't need to be
tracerouting or pinging into my network and that's my choice to make.
I can break them without breaking MTU discovery.  You want to diagnose
routing or other technical problems, why aren't you contacting me?

	You cut off ICMP_ECHOREPLY and all but a tightly restricted set
of UDP and you have just starved these DDoS zombies of the vast majority
of their communications facility.  TCP is much easier to trace, if they
fall back to that (I don't see how TFN2K could - it utilizes a blind
forward-only non-responding channel).  Blocking spoofed packets won't
do nearly as good a job since a lot of the packets aren't spoofed.  Doesn't
help at all in some examples I have some first hand experience with.

	Edge filtering and spoof protection would have been absolutely no
help for one site I was help with forensics after TFN2K.  They were a
source of ICMP_ECHOREPLY packets in one of the storms.  We STILL
haven't located the zombie amongst the hundreds of potential Windows
boxes (we already cleared the single Solaris and single RedHat box on
the subnet and TFN2K is known to run on Windows).

	No spoofed packets crossed router boundries.  The TFN2K command
sequence was executed well before anyone noticed any bandwidth anomolies,
so there's no track back to the master.  (Who would have noticed 20
ICMP_ECHOREPLY packets that merely didn't correspond to any internal
request?)  The slaves shut down after two hours and before the admins
realized that the smurf was being generated internally.  They did find a
bug in a router blocking of directed broadcasts.  That red-herring slowed
them down, thinking it was externally generated.  No trace back of the
smurf triggers back to the zombie (having that MAC address would do wonders)
was caught since it quiet before they started sniffing the network.

	They broke it's back by blocking ICMP_ECHO and ICMP_ECHOREPLY
(fortunately, this attack was not using one of the UDP options).

	I have not heard if any of the TFN scanners have turned up
anything yet.  TFN2K zombies are a real bummer since it can lay dormant
on a network until triggered and they don't reply back to the master.
These guys are on a machine by machine, file by file snark hunt looking
for files that could be any one of a number of names on systems that are
all different anyways.  Don't you know they're having fun?

	The attackers are gaining in sophistication.  We are begining to
see effort at "covert channels" for communications.  The tricks of
communicating via ICMP_ECHOREPLY packets with commands in the payload
and sending blobs of forward only commands with no reverse channel
responses are just examples.  How long before they start sneaking past
those defenses by sending ICMP_UNREACHABLE/ICMP_FRAG_NEEDED with
a command data payload?

	They don't have to resort to spoofing to pull off a lot of this.
Long command time delays, covert channels, and unidirection command
direction can make it just as difficult to track down as spoofing.

	Diagnostics are fine.  Performance is fine.  Diagnostics and/or
performance at the expense of security and/or robustness is not.

> Vernon Schryver    vjs@rhyolite.com

	Mike
-- 
 Michael H. Warfield    |  (770) 985-6132   |  mhw@WittsEnd.com
  (The Mad Wizard)      |  (770) 331-2437   |  http://www.wittsend.com/mhw/
  NIC whois:  MHW9      |  An optimist believes we live in the best of all
 PGP Key: 0xDF1DD471    |  possible worlds.  A pessimist is sure of it!



From owner-ietf-outbound  Tue Feb 15 14:20:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA19279
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 14:20:02 -0500 (EST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19134
	for <ietf@ietf.org>; Tue, 15 Feb 2000 14:14:38 -0500 (EST)
Received: from zed.isi.edu (zed-e.isi.edu [128.9.160.57])
	by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id LAA24020;
	Tue, 15 Feb 2000 11:14:38 -0800 (PST)
From: Bill Manning <bmanning@ISI.EDU>
Received: (from bmanning@localhost)
	by zed.isi.edu (8.8.7/8.8.6) id LAA20085;
	Tue, 15 Feb 2000 11:14:26 -0800 (PST)
Message-Id: <200002151914.LAA20085@zed.isi.edu>
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
To: mart.nurmet@inet.com (Mart Nurmet)
Date: Tue, 15 Feb 2000 11:14:26 -0800 (PST)
Cc: ietf@ietf.org
In-Reply-To: <38A998FC.72501901@inet.com> from "Mart Nurmet" at Feb 15, 2000 12:20:44 PM
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

% Keith:
% 
% How do I go about geting the schedule for the meetings for the rest of the
% year?
% 
% I'm new to this forum and will be the Inet Technologies representative in
% the future.
% 
% Best regards,
% Mart Nurmet
% 972 543-3791


I'm not keith but can answer your question.

	www.ietf.org

and note that the IETF is composed of indivduals, not corporations. 
You should not presume to "represent" a corporate entity within the
IETF. Your just the best engineer you can be.


--bill



From owner-ietf-outbound@ietf.org  Tue Feb 15 14:26:40 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19506
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Feb 2000 14:26:40 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA15271;
	Tue, 15 Feb 2000 14:24:36 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id OAA19279
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 14:20:02 -0500 (EST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19134
	for <ietf@ietf.org>; Tue, 15 Feb 2000 14:14:38 -0500 (EST)
Received: from zed.isi.edu (zed-e.isi.edu [128.9.160.57])
	by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id LAA24020;
	Tue, 15 Feb 2000 11:14:38 -0800 (PST)
From: Bill Manning <bmanning@ISI.EDU>
Received: (from bmanning@localhost)
	by zed.isi.edu (8.8.7/8.8.6) id LAA20085;
	Tue, 15 Feb 2000 11:14:26 -0800 (PST)
Message-Id: <200002151914.LAA20085@zed.isi.edu>
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
To: mart.nurmet@inet.com (Mart Nurmet)
Date: Tue, 15 Feb 2000 11:14:26 -0800 (PST)
Cc: ietf@ietf.org
In-Reply-To: <38A998FC.72501901@inet.com> from "Mart Nurmet" at Feb 15, 2000 12:20:44 PM
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

% Keith:
% 
% How do I go about geting the schedule for the meetings for the rest of the
% year?
% 
% I'm new to this forum and will be the Inet Technologies representative in
% the future.
% 
% Best regards,
% Mart Nurmet
% 972 543-3791


I'm not keith but can answer your question.

	www.ietf.org

and note that the IETF is composed of indivduals, not corporations. 
You should not presume to "represent" a corporate entity within the
IETF. Your just the best engineer you can be.


--bill



From owner-ietf-outbound  Tue Feb 15 14:50:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA20306
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 14:50:02 -0500 (EST)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20040
	for <IETF@ietf.org>; Tue, 15 Feb 2000 14:40:46 -0500 (EST)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id MAA01628
	for IETF@ietf.org  env-from <vjs>;
	Tue, 15 Feb 2000 12:40:42 -0700 (MST)
Date: Tue, 15 Feb 2000 12:40:42 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200002151940.MAA01628@calcite.rhyolite.com>
To: IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
X-Loop: ietf@ietf.org

> From: "Michael H. Warfield" <mhw@wittsend.com>

> ...
> 	But some of us turn off ICMP except for ICMP_FRAG_NEEDED and keep
> MTU discovery alive while cutting off the ICMP food fights and script
> kiddie probes that seem to be endemic in our current mess.

Why couldn't you do as has been frequently suggested and only throttle
ICMP Echo-Request/Reply?


> 	You betcha traceroute and ping are broken (figuratively and
> literally).  Just as broken as I can make them.  You don't need to be
> tracerouting or pinging into my network and that's my choice to make.

As we all agree, what you do with your own network is only your business.
However, rest assured that if you're an ISP that breaks traceroute,
then you also break arbitrary UDP applications, and that means you
don't get any business from anyone with any sense.


> I can break them without breaking MTU discovery.  You want to diagnose
> routing or other technical problems, why aren't you contacting me?

(Hypothetically, of course) Because I do not know where the problem
is.  Without traceroute, how should I figure out to call you?  How
do I discover that you're running a transit network between here
and the other and that is trashing my packets)?

Nonsense about calling arround is exactly why traceroute was invented,
and that was back when there were a lot fewer usual suspects messing with
things.  Before traceroute, the only way to figure out what was wrong
was to call the far end and the first hop...well, besides intelligent
and laborous use of `ping` and other manual, hop-by-hop probing.
Since you turn off ICMP Echo-Requests, no one can tell.
You probably also turn of Record-Route, lest someone discover that your
routers are in the path.


> 	You cut off ICMP_ECHOREPLY and all but a tightly restricted set
> of UDP and you have just starved these DDoS zombies of the vast majority
> of their communications facility.  TCP is much easier to trace, if they
> fall back to that (I don't see how TFN2K could - it utilizes a blind

No, TCP is not more traceable because has no more IP source addresses
than UDP.  Yes, unidirectional TCP is not terribly useful for
legitimate traffic, but that also applies to UDP.

You have a such narrow view of the possibilities for a DDoS attack
that it is dangerously wrong.  If you accept any packets that cause
your systems to do any work, then I can write a distributed program
that can trash your systems, your network, or both.  All you can
do is force me increase the size of my army of zombie proxies.

If you do not accept any packets that cause your system to do any work
(including merely sending "puzzles" or checking answers), then your system
is useless.  Who would send any packets to a system that does nothing?


>                                        Blocking spoofed packets won't
> do nearly as good a job since a lot of the packets aren't spoofed.

Yes, as has been repeatedly pointed out.  
RFC 2267 filtering is good even if it is not a pancea.  The reasons
advanced for bogus IP source addresses are not compelling.


> ...
> 	They broke it's back by blocking ICMP_ECHO and ICMP_ECHOREPLY
> (fortunately, this attack was not using one of the UDP options).

It is also fortunate that it was not based on TCP packets to port 80
or UDP to or from port 53.
I'd wonder why they didn't use a distributed, very low rate per zombie
SYN attack, except I know such people are fundamentally stupid.


> ...
> 	The attackers are gaining in sophistication.  We are begining to
> see effort at "covert channels" for communications.  The tricks of
> communicating via ICMP_ECHOREPLY packets with commands in the payload
> and sending blobs of forward only commands with no reverse channel
> responses are just examples.  How long before they start sneaking past
> those defenses by sending ICMP_UNREACHABLE/ICMP_FRAG_NEEDED with
> a command data payload?

Also think about putting commands in packets to port 53 or 80.  Yes,
including TCP port 80.  If you've broken into a system, you may as well
listen to all raw packets and not just what the local TCP state machine
thinks are kosher and not only what `ping` and `traceroute` use.

Given all of that, could you remind me of why it is rational to filter
ICMP-Echo's when by your own words the bad guys don't need to use them?

As in the spam war, filtering ICMP-Echo's only advances the day whey
they use other schemes that are harder to filter.  Unlike the spam
war, it is technically easy to make bad traffic that cannot be filtered
(press releases from security outfits notwithstanding).


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound@ietf.org  Tue Feb 15 15:00:49 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20585
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Feb 2000 15:00:49 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA16198;
	Tue, 15 Feb 2000 14:58:43 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id OAA20306
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 14:50:02 -0500 (EST)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20040
	for <IETF@ietf.org>; Tue, 15 Feb 2000 14:40:46 -0500 (EST)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id MAA01628
	for IETF@ietf.org  env-from <vjs>;
	Tue, 15 Feb 2000 12:40:42 -0700 (MST)
Date: Tue, 15 Feb 2000 12:40:42 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200002151940.MAA01628@calcite.rhyolite.com>
To: IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
X-Loop: ietf@ietf.org

> From: "Michael H. Warfield" <mhw@wittsend.com>

> ...
> 	But some of us turn off ICMP except for ICMP_FRAG_NEEDED and keep
> MTU discovery alive while cutting off the ICMP food fights and script
> kiddie probes that seem to be endemic in our current mess.

Why couldn't you do as has been frequently suggested and only throttle
ICMP Echo-Request/Reply?


> 	You betcha traceroute and ping are broken (figuratively and
> literally).  Just as broken as I can make them.  You don't need to be
> tracerouting or pinging into my network and that's my choice to make.

As we all agree, what you do with your own network is only your business.
However, rest assured that if you're an ISP that breaks traceroute,
then you also break arbitrary UDP applications, and that means you
don't get any business from anyone with any sense.


> I can break them without breaking MTU discovery.  You want to diagnose
> routing or other technical problems, why aren't you contacting me?

(Hypothetically, of course) Because I do not know where the problem
is.  Without traceroute, how should I figure out to call you?  How
do I discover that you're running a transit network between here
and the other and that is trashing my packets)?

Nonsense about calling arround is exactly why traceroute was invented,
and that was back when there were a lot fewer usual suspects messing with
things.  Before traceroute, the only way to figure out what was wrong
was to call the far end and the first hop...well, besides intelligent
and laborous use of `ping` and other manual, hop-by-hop probing.
Since you turn off ICMP Echo-Requests, no one can tell.
You probably also turn of Record-Route, lest someone discover that your
routers are in the path.


> 	You cut off ICMP_ECHOREPLY and all but a tightly restricted set
> of UDP and you have just starved these DDoS zombies of the vast majority
> of their communications facility.  TCP is much easier to trace, if they
> fall back to that (I don't see how TFN2K could - it utilizes a blind

No, TCP is not more traceable because has no more IP source addresses
than UDP.  Yes, unidirectional TCP is not terribly useful for
legitimate traffic, but that also applies to UDP.

You have a such narrow view of the possibilities for a DDoS attack
that it is dangerously wrong.  If you accept any packets that cause
your systems to do any work, then I can write a distributed program
that can trash your systems, your network, or both.  All you can
do is force me increase the size of my army of zombie proxies.

If you do not accept any packets that cause your system to do any work
(including merely sending "puzzles" or checking answers), then your system
is useless.  Who would send any packets to a system that does nothing?


>                                        Blocking spoofed packets won't
> do nearly as good a job since a lot of the packets aren't spoofed.

Yes, as has been repeatedly pointed out.  
RFC 2267 filtering is good even if it is not a pancea.  The reasons
advanced for bogus IP source addresses are not compelling.


> ...
> 	They broke it's back by blocking ICMP_ECHO and ICMP_ECHOREPLY
> (fortunately, this attack was not using one of the UDP options).

It is also fortunate that it was not based on TCP packets to port 80
or UDP to or from port 53.
I'd wonder why they didn't use a distributed, very low rate per zombie
SYN attack, except I know such people are fundamentally stupid.


> ...
> 	The attackers are gaining in sophistication.  We are begining to
> see effort at "covert channels" for communications.  The tricks of
> communicating via ICMP_ECHOREPLY packets with commands in the payload
> and sending blobs of forward only commands with no reverse channel
> responses are just examples.  How long before they start sneaking past
> those defenses by sending ICMP_UNREACHABLE/ICMP_FRAG_NEEDED with
> a command data payload?

Also think about putting commands in packets to port 53 or 80.  Yes,
including TCP port 80.  If you've broken into a system, you may as well
listen to all raw packets and not just what the local TCP state machine
thinks are kosher and not only what `ping` and `traceroute` use.

Given all of that, could you remind me of why it is rational to filter
ICMP-Echo's when by your own words the bad guys don't need to use them?

As in the spam war, filtering ICMP-Echo's only advances the day whey
they use other schemes that are harder to filter.  Unlike the spam
war, it is technically easy to make bad traffic that cannot be filtered
(press releases from security outfits notwithstanding).


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Tue Feb 15 16:20:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA23108
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 16:20:02 -0500 (EST)
Received: from ibd.ar.com (adsl-63-194-205-75.dsl.snfc21.pacbell.net [63.194.205.75])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22995
	for <ietf@ietf.org>; Tue, 15 Feb 2000 16:15:01 -0500 (EST)
Received: from loki (wessorh@loki.ar.com [10.10.10.88])
	by ibd.ar.com (8.9.0.Beta5/8.9.0.Beta5) with ESMTP id NAA05138
	for <ietf@ietf.org>; Tue, 15 Feb 2000 13:14:59 -0800 (PST)
Date: Tue, 15 Feb 2000 13:14:58 -0800 (PST)
From: Rick H Wesson <wessorh@ar.com>
To: ietf@ietf.org
Subject: Common Indexing Protocol (CIP)
Message-ID: <Pine.LNX.4.10.10002151313550.1108-100000@loki.ar.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org


does anyone know of any implementations of CIP? 

thanks,

-rick




From owner-ietf-outbound@ietf.org  Tue Feb 15 16:29:40 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23363
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Feb 2000 16:29:40 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA18248;
	Tue, 15 Feb 2000 16:27:34 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id QAA23108
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 16:20:02 -0500 (EST)
Received: from ibd.ar.com (adsl-63-194-205-75.dsl.snfc21.pacbell.net [63.194.205.75])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22995
	for <ietf@ietf.org>; Tue, 15 Feb 2000 16:15:01 -0500 (EST)
Received: from loki (wessorh@loki.ar.com [10.10.10.88])
	by ibd.ar.com (8.9.0.Beta5/8.9.0.Beta5) with ESMTP id NAA05138
	for <ietf@ietf.org>; Tue, 15 Feb 2000 13:14:59 -0800 (PST)
Date: Tue, 15 Feb 2000 13:14:58 -0800 (PST)
From: Rick H Wesson <wessorh@ar.com>
To: ietf@ietf.org
Subject: Common Indexing Protocol (CIP)
Message-ID: <Pine.LNX.4.10.10002151313550.1108-100000@loki.ar.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org


does anyone know of any implementations of CIP? 

thanks,

-rick




From owner-ietf-outbound  Tue Feb 15 16:30:18 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA23395
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 16:30:02 -0500 (EST)
Received: from marcos.networkcs.com (marcos.networkcs.com [137.66.16.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23171
	for <ietf@ietf.org>; Tue, 15 Feb 2000 16:22:34 -0500 (EST)
Received: from us.networkcs.com (us.networkcs.com [137.66.11.15])
	by marcos.networkcs.com (8.9.3/8.9.3) with ESMTP id PAA73355
	for <ietf@ietf.org>; Tue, 15 Feb 2000 15:22:33 -0600 (CST)
	(envelope-from salo@us.networkcs.com)
Received: (from salo@localhost)
	by us.networkcs.com (8.9.2/8.9.2) id PAA87218
	for ietf@ietf.org; Tue, 15 Feb 2000 15:22:33 -0600 (CST)
	(envelope-from salo)
Date: Tue, 15 Feb 2000 15:22:33 -0600 (CST)
From: Tim Salo <salo@networkcs.com>
Message-Id: <200002152122.PAA87218@us.networkcs.com>
To: ietf@ietf.org
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
In-Reply-To: <200002151914.LAA20085@zed.isi.edu>
X-Loop: ietf@ietf.org

> From: Bill Manning <bmanning@ISI.EDU>
> Subject: Re: IETF Adelaide and interim meetings for APPS WGs
> To: mart.nurmet@inet.com (Mart Nurmet)
> Date: Tue, 15 Feb 2000 11:14:26 -0800 (PST)
> Cc: ietf@ietf.org
> 	[...]
> and note that the IETF is composed of indivduals, not corporations. 
> You should not presume to "represent" a corporate entity within the
> IETF. Your just the best engineer you can be.

I believe that whether an individual is expected to represent the 
interests of an organization is largely a matter between that individual
and the organization, (regardless of what the IETF says).  The IETF may
recognize individuals, not organizations, but that's far different than
the IETF promising participants that they can say anything they want without
the prospect of repercussions when they return home.

The original poster may, in a very real sense, actually be representing a
company, whether the IETF wants to believe it or not.

Of course, that leads to the rather interesting dilemma that we don't know
whether an individual is speaking on behalf or his or her self or on behalf
of an organization, (again, even if we tell that person that _we_ know
which it is).

-tjs



From owner-ietf-outbound@ietf.org  Tue Feb 15 16:36:50 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23741
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Feb 2000 16:36:46 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA18476;
	Tue, 15 Feb 2000 16:34:44 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id QAA23395
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 16:30:02 -0500 (EST)
Received: from marcos.networkcs.com (marcos.networkcs.com [137.66.16.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23171
	for <ietf@ietf.org>; Tue, 15 Feb 2000 16:22:34 -0500 (EST)
Received: from us.networkcs.com (us.networkcs.com [137.66.11.15])
	by marcos.networkcs.com (8.9.3/8.9.3) with ESMTP id PAA73355
	for <ietf@ietf.org>; Tue, 15 Feb 2000 15:22:33 -0600 (CST)
	(envelope-from salo@us.networkcs.com)
Received: (from salo@localhost)
	by us.networkcs.com (8.9.2/8.9.2) id PAA87218
	for ietf@ietf.org; Tue, 15 Feb 2000 15:22:33 -0600 (CST)
	(envelope-from salo)
Date: Tue, 15 Feb 2000 15:22:33 -0600 (CST)
From: Tim Salo <salo@networkcs.com>
Message-Id: <200002152122.PAA87218@us.networkcs.com>
To: ietf@ietf.org
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
In-Reply-To: <200002151914.LAA20085@zed.isi.edu>
X-Loop: ietf@ietf.org

> From: Bill Manning <bmanning@ISI.EDU>
> Subject: Re: IETF Adelaide and interim meetings for APPS WGs
> To: mart.nurmet@inet.com (Mart Nurmet)
> Date: Tue, 15 Feb 2000 11:14:26 -0800 (PST)
> Cc: ietf@ietf.org
> 	[...]
> and note that the IETF is composed of indivduals, not corporations. 
> You should not presume to "represent" a corporate entity within the
> IETF. Your just the best engineer you can be.

I believe that whether an individual is expected to represent the 
interests of an organization is largely a matter between that individual
and the organization, (regardless of what the IETF says).  The IETF may
recognize individuals, not organizations, but that's far different than
the IETF promising participants that they can say anything they want without
the prospect of repercussions when they return home.

The original poster may, in a very real sense, actually be representing a
company, whether the IETF wants to believe it or not.

Of course, that leads to the rather interesting dilemma that we don't know
whether an individual is speaking on behalf or his or her self or on behalf
of an organization, (again, even if we tell that person that _we_ know
which it is).

-tjs



From owner-ietf-outbound  Tue Feb 15 16:40:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA23953
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 16:40:02 -0500 (EST)
Received: from infidel.boolean.net (root@router.boolean.net [198.144.206.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23687
	for <ietf@ietf.org>; Tue, 15 Feb 2000 16:35:45 -0500 (EST)
Received: from gypsy (gypsy.boolean.net [198.144.202.243])
	by infidel.boolean.net (8.9.3/8.9.3) with SMTP id VAA25474
	for <ietf@ietf.org>; Tue, 15 Feb 2000 21:35:44 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <3.0.5.32.20000215133544.0096d530@infidel.boolean.net>
X-Sender: guru@infidel.boolean.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Tue, 15 Feb 2000 13:35:44 -0800
To: ietf@ietf.org
From: "Kurt D. Zeilenga" <Kurt@OPENLDAP.ORG>
Subject: product tags, vendor information in Internet protocols
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

A number of protocols/services expose product tags describing
the vendor implementation for a variety purposes.  These tags
generally include the "vendor" and some "version" information
and are often used by protocol peers to alter behavior.  In some
cases, like HTTP (RFC 2616), they may include vendor/version
information of subsystems.

I am looking for references to technical specifications,
considerations, and discussions concerning the use of product
tags in Internet protocols.  I would also be interested in
any published materials describing operational experience
using (or abusing) such information.

Please note that this message is not intended to start a
discussion or debate concerning the use (	or abuse) of product
tags, we've likely "been there, done that".  So, please, just
references to existing works.

Regards, Kurt



From owner-ietf-outbound@ietf.org  Tue Feb 15 16:48:33 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24422
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Feb 2000 16:48:33 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA18655;
	Tue, 15 Feb 2000 16:46:31 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id QAA23953
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 16:40:02 -0500 (EST)
Received: from infidel.boolean.net (root@router.boolean.net [198.144.206.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23687
	for <ietf@ietf.org>; Tue, 15 Feb 2000 16:35:45 -0500 (EST)
Received: from gypsy (gypsy.boolean.net [198.144.202.243])
	by infidel.boolean.net (8.9.3/8.9.3) with SMTP id VAA25474
	for <ietf@ietf.org>; Tue, 15 Feb 2000 21:35:44 GMT
	(envelope-from Kurt@OpenLDAP.org)
Message-Id: <3.0.5.32.20000215133544.0096d530@infidel.boolean.net>
X-Sender: guru@infidel.boolean.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Tue, 15 Feb 2000 13:35:44 -0800
To: ietf@ietf.org
From: "Kurt D. Zeilenga" <Kurt@OPENLDAP.ORG>
Subject: product tags, vendor information in Internet protocols
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

A number of protocols/services expose product tags describing
the vendor implementation for a variety purposes.  These tags
generally include the "vendor" and some "version" information
and are often used by protocol peers to alter behavior.  In some
cases, like HTTP (RFC 2616), they may include vendor/version
information of subsystems.

I am looking for references to technical specifications,
considerations, and discussions concerning the use of product
tags in Internet protocols.  I would also be interested in
any published materials describing operational experience
using (or abusing) such information.

Please note that this message is not intended to start a
discussion or debate concerning the use (	or abuse) of product
tags, we've likely "been there, done that".  So, please, just
references to existing works.

Regards, Kurt



From owner-ietf-outbound  Tue Feb 15 16:50:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA24573
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 16:50:03 -0500 (EST)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23762
	for <IETF@ietf.org>; Tue, 15 Feb 2000 16:37:53 -0500 (EST)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id NAA09072;
	Tue, 15 Feb 2000 13:36:51 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.9.3/8.9.3-VIRSCAN) id NAA16446;
	Tue, 15 Feb 2000 13:26:25 -0800
X-Virus-Scanned:  Tue, 15 Feb 2000 13:26:25 -0800 Nokia Silicon Valley, The Future is Here | High Security Email Exploit Scanner
Received: from <charliep@iprg.nokia.com> (charliep.iprg.nokia.com [205.226.2.89]) by darkstar.iprg.nokia.com  SMTP/WTS (12.69)
 xma016275; Tue, 15 Feb 00 13:26:17 -0800
Sender: charliep@iprg.nokia.com
Message-ID: <38A9C6E9.37203AE6@iprg.nokia.com>
Date: Tue, 15 Feb 2000 13:36:41 -0800
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Vernon Schryver <vjs@calcite.rhyolite.com>
CC: IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
References: <200002151722.KAA28768@calcite.rhyolite.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit


Hello Vernon,

> > Well.. as soon as somebody presents us with "the real solution", we'll start
> > implementing.  In the meantime, filtering is the best we know how to do.
> > ...
> 
> I really wish "we" actually knew how to filter.

But maybe filtering is putting the cart before the horse.

I compare the recent problems with phone harassment.  We can
install all sorts of doodads, but if we can identify the source
of the harassment we can bring charges against them.

From that analogy, I claim that the appropriate action is to
develop tracing systems that will help to identify a wrongdoer.
Here is a possible design.
- Create a router feature, able to be remotely activated, to keep
  track of "suspicious" packets for a few seconds up to maybe a
  couple dozen seconds.  Suspicious packets might be SYNs, or
  even packets with "incorrect" source addresses.
- If a violation is noticed, determine the interface on which a
  bad packet was received, and send a request to that neighbor
  along with appropriate credentials that can be checked.
- If, on the other hand, a neighbor sends a request for tracing
  a problematic packet, check the credentials that accompany the
  request and look at the stored data for that packet.  If no
  stored data exists, send back the bad news, and possibly enable
  the pattern-matchine function to capture similarly featured
  packets in case of future requests.
- If a neighbor's request refers to a stored packet, figure out
  what interface the stored packet arrived on.  If the packet
  came from another neighbor, forward the request.  Otherwise,
  look for the malicious source internal to the domain.

The basic idea then would be to trace back bad packets that
conform to some typically innocent, but occasionally troublesome,
profiles.  The profiles will become self-evident with experience,
and once people know they will be caught by this traceback
system they will think twice before spreading their crap around.

According to one knowledgeable source, this strategy is undesirable
because it would cause routers to maintain more state.  But, I claim
that we have to maintain state to do any tracing, and I also claim
that we need to enable tracing in order to detect and identify
wrongdoers.  Since the features should be activated by request
from trusted neighbors, in the usual case there should not be
any significant performance degradation.  Clearly, such requests
have to be checked for authenticity.

So the costs boil down to more memory, more software, some
pattern-matching hardware, and maintaining security relationships
with your routing partners.

I think it's a very worthwhile tradeoff.  Much better than mostly
ineffective measures that have big negative effects and small
positive effects, characteristics of ingress filtering as I
understand it.

Plus I don't like the attitude of blaming the victim without
giving the victim any tools with which to find the perpetrators.

Regards,
Charlie P.



From owner-ietf-outbound@ietf.org  Tue Feb 15 16:57:40 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24897
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Feb 2000 16:57:40 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA18843;
	Tue, 15 Feb 2000 16:55:39 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id QAA24573
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 16:50:03 -0500 (EST)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23762
	for <IETF@ietf.org>; Tue, 15 Feb 2000 16:37:53 -0500 (EST)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id NAA09072;
	Tue, 15 Feb 2000 13:36:51 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.9.3/8.9.3-VIRSCAN) id NAA16446;
	Tue, 15 Feb 2000 13:26:25 -0800
X-Virus-Scanned:  Tue, 15 Feb 2000 13:26:25 -0800 Nokia Silicon Valley, The Future is Here | High Security Email Exploit Scanner
Received: from <charliep@iprg.nokia.com> (charliep.iprg.nokia.com [205.226.2.89]) by darkstar.iprg.nokia.com  SMTP/WTS (12.69)
 xma016275; Tue, 15 Feb 00 13:26:17 -0800
Sender: charliep@iprg.nokia.com
Message-ID: <38A9C6E9.37203AE6@iprg.nokia.com>
Date: Tue, 15 Feb 2000 13:36:41 -0800
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Vernon Schryver <vjs@calcite.rhyolite.com>
CC: IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
References: <200002151722.KAA28768@calcite.rhyolite.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Hello Vernon,

> > Well.. as soon as somebody presents us with "the real solution", we'll start
> > implementing.  In the meantime, filtering is the best we know how to do.
> > ...
> 
> I really wish "we" actually knew how to filter.

But maybe filtering is putting the cart before the horse.

I compare the recent problems with phone harassment.  We can
install all sorts of doodads, but if we can identify the source
of the harassment we can bring charges against them.

From that analogy, I claim that the appropriate action is to
develop tracing systems that will help to identify a wrongdoer.
Here is a possible design.
- Create a router feature, able to be remotely activated, to keep
  track of "suspicious" packets for a few seconds up to maybe a
  couple dozen seconds.  Suspicious packets might be SYNs, or
  even packets with "incorrect" source addresses.
- If a violation is noticed, determine the interface on which a
  bad packet was received, and send a request to that neighbor
  along with appropriate credentials that can be checked.
- If, on the other hand, a neighbor sends a request for tracing
  a problematic packet, check the credentials that accompany the
  request and look at the stored data for that packet.  If no
  stored data exists, send back the bad news, and possibly enable
  the pattern-matchine function to capture similarly featured
  packets in case of future requests.
- If a neighbor's request refers to a stored packet, figure out
  what interface the stored packet arrived on.  If the packet
  came from another neighbor, forward the request.  Otherwise,
  look for the malicious source internal to the domain.

The basic idea then would be to trace back bad packets that
conform to some typically innocent, but occasionally troublesome,
profiles.  The profiles will become self-evident with experience,
and once people know they will be caught by this traceback
system they will think twice before spreading their crap around.

According to one knowledgeable source, this strategy is undesirable
because it would cause routers to maintain more state.  But, I claim
that we have to maintain state to do any tracing, and I also claim
that we need to enable tracing in order to detect and identify
wrongdoers.  Since the features should be activated by request
from trusted neighbors, in the usual case there should not be
any significant performance degradation.  Clearly, such requests
have to be checked for authenticity.

So the costs boil down to more memory, more software, some
pattern-matching hardware, and maintaining security relationships
with your routing partners.

I think it's a very worthwhile tradeoff.  Much better than mostly
ineffective measures that have big negative effects and small
positive effects, characteristics of ingress filtering as I
understand it.

Plus I don't like the attitude of blaming the victim without
giving the victim any tools with which to find the perpetrators.

Regards,
Charlie P.



From owner-ietf-outbound  Tue Feb 15 17:00:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA24998
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 17:00:03 -0500 (EST)
Received: from ns01.newbridge.com (ns01.newbridge.com [192.75.23.67])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24719
	for <ietf@ietf.org>; Tue, 15 Feb 2000 16:51:55 -0500 (EST)
Received: (from smtpd@localhost)
	by ns01.newbridge.com (8.9.2/8.9.2) id QAA22123
	for <ietf@ietf.org>; Tue, 15 Feb 2000 16:46:45 -0500 (EST)
Received: from portal1.newbridge.com(192.75.23.76), claiming to be "kanata-mh1.ca.newbridge.com"
 via SMTP by ns01.newbridge.com, id smtpdAAA0IUuQQ; Tue Feb 15 16:46:43 2000
Received: from kanmail01.ca.newbridge.com by kanata-mh1.ca.newbridge.com with ESMTP for ietf@ietf.org; Tue, 15 Feb 2000 16:51:51 -0500
Received: from pcswbdesk ([138.120.49.76]) by kanmail01.ca.newbridge.com
          (Netscape Messaging Server 3.6)  with ESMTP id AAB547A
          for <ietf@ietf.org>; Tue, 15 Feb 2000 16:51:49 -0500
Message-Id: <4.2.2.20000215165106.00aae4f0@kanmail01.ca.newbridge.com>
X-Sender: swb@kanmail01.ca.newbridge.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Tue, 15 Feb 2000 16:51:44 -0500
To: ietf@ietf.org
From: "Scott W Brim" <swb@newbridge.com>
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
In-Reply-To: <200002152122.PAA87218@us.networkcs.com>
References: <200002151914.LAA20085@zed.isi.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

Why does the IETF registration form ask for a company name?

> > From: Bill Manning <bmanning@ISI.EDU>
> > Subject: Re: IETF Adelaide and interim meetings for APPS WGs
> > To: mart.nurmet@inet.com (Mart Nurmet)
> > Date: Tue, 15 Feb 2000 11:14:26 -0800 (PST)
> > Cc: ietf@ietf.org
> >       [...]
> > and note that the IETF is composed of indivduals, not corporations.
> > You should not presume to "represent" a corporate entity within the
> > IETF. Your just the best engineer you can be.



From owner-ietf-outbound@ietf.org  Tue Feb 15 17:06:07 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25275
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Feb 2000 17:06:07 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA19112;
	Tue, 15 Feb 2000 17:04:06 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id RAA24998
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 17:00:03 -0500 (EST)
Received: from ns01.newbridge.com (ns01.newbridge.com [192.75.23.67])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24719
	for <ietf@ietf.org>; Tue, 15 Feb 2000 16:51:55 -0500 (EST)
Received: (from smtpd@localhost)
	by ns01.newbridge.com (8.9.2/8.9.2) id QAA22123
	for <ietf@ietf.org>; Tue, 15 Feb 2000 16:46:45 -0500 (EST)
Received: from portal1.newbridge.com(192.75.23.76), claiming to be "kanata-mh1.ca.newbridge.com"
 via SMTP by ns01.newbridge.com, id smtpdAAA0IUuQQ; Tue Feb 15 16:46:43 2000
Received: from kanmail01.ca.newbridge.com by kanata-mh1.ca.newbridge.com with ESMTP for ietf@ietf.org; Tue, 15 Feb 2000 16:51:51 -0500
Received: from pcswbdesk ([138.120.49.76]) by kanmail01.ca.newbridge.com
          (Netscape Messaging Server 3.6)  with ESMTP id AAB547A
          for <ietf@ietf.org>; Tue, 15 Feb 2000 16:51:49 -0500
Message-Id: <4.2.2.20000215165106.00aae4f0@kanmail01.ca.newbridge.com>
X-Sender: swb@kanmail01.ca.newbridge.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Tue, 15 Feb 2000 16:51:44 -0500
To: ietf@ietf.org
From: "Scott W Brim" <swb@newbridge.com>
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
In-Reply-To: <200002152122.PAA87218@us.networkcs.com>
References: <200002151914.LAA20085@zed.isi.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

Why does the IETF registration form ask for a company name?

> > From: Bill Manning <bmanning@ISI.EDU>
> > Subject: Re: IETF Adelaide and interim meetings for APPS WGs
> > To: mart.nurmet@inet.com (Mart Nurmet)
> > Date: Tue, 15 Feb 2000 11:14:26 -0800 (PST)
> > Cc: ietf@ietf.org
> >       [...]
> > and note that the IETF is composed of indivduals, not corporations.
> > You should not presume to "represent" a corporate entity within the
> > IETF. Your just the best engineer you can be.



From owner-ietf-outbound  Tue Feb 15 17:10:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA25390
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 17:10:03 -0500 (EST)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25302
	for <IETF@ietf.org>; Tue, 15 Feb 2000 17:06:41 -0500 (EST)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id PAA04668
	for IETF@ietf.org  env-from <vjs>;
	Tue, 15 Feb 2000 15:06:42 -0700 (MST)
Date: Tue, 15 Feb 2000 15:06:42 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200002152206.PAA04668@calcite.rhyolite.com>
To: IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
X-Loop: ietf@ietf.org

> From: "Charles E. Perkins" <charliep@iprg.nokia.com>

> ...
> > I really wish "we" actually knew how to filter.
>
> But maybe filtering is putting the cart before the horse.

I agree.


> ...
> >From that analogy, I claim that the appropriate action is to
> develop tracing systems that will help to identify a wrongdoer.
> Here is a possible design.
> - Create a router feature, able to be remotely activated, to keep
> ...

How is that different from RMON?
Or better, how does it not fit naturally into RMON?


> ...
> The basic idea then would be to trace back bad packets that
> conform to some typically innocent, but occasionally troublesome,
> profiles.  The profiles will become self-evident with experience,
> and once people know they will be caught by this traceback
> system they will think twice before spreading their crap around.

If I were building a DDoS engine today, I'd write a conventional
(Microsoft) DOS virus that does nothing except once every 3 minutes do
the equivalent of:

    echo "GET /index.html HTTP/1.0"; echo) | telnet -r $1 80

(maybe instead with a random request instead of /index.html)

After a few 1,000,000 desktops have been infected by familiar virus
vectors, the victim might notice the traffic.
How would you filter for them?  Even if you could give routers
enough processing power, what would you learn from the filtering
that you'd care to apply?


> ...
> So the costs boil down to more memory, more software, some
> pattern-matching hardware, and maintaining security relationships
> with your routing partners.

that's easy to say, but it doesn't sound likely to happen in my world.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound@ietf.org  Tue Feb 15 17:16:25 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25613
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Feb 2000 17:16:20 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA19281;
	Tue, 15 Feb 2000 17:14:19 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id RAA25390
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 17:10:03 -0500 (EST)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25302
	for <IETF@ietf.org>; Tue, 15 Feb 2000 17:06:41 -0500 (EST)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id PAA04668
	for IETF@ietf.org  env-from <vjs>;
	Tue, 15 Feb 2000 15:06:42 -0700 (MST)
Date: Tue, 15 Feb 2000 15:06:42 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200002152206.PAA04668@calcite.rhyolite.com>
To: IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
X-Loop: ietf@ietf.org

> From: "Charles E. Perkins" <charliep@iprg.nokia.com>

> ...
> > I really wish "we" actually knew how to filter.
>
> But maybe filtering is putting the cart before the horse.

I agree.


> ...
> >From that analogy, I claim that the appropriate action is to
> develop tracing systems that will help to identify a wrongdoer.
> Here is a possible design.
> - Create a router feature, able to be remotely activated, to keep
> ...

How is that different from RMON?
Or better, how does it not fit naturally into RMON?


> ...
> The basic idea then would be to trace back bad packets that
> conform to some typically innocent, but occasionally troublesome,
> profiles.  The profiles will become self-evident with experience,
> and once people know they will be caught by this traceback
> system they will think twice before spreading their crap around.

If I were building a DDoS engine today, I'd write a conventional
(Microsoft) DOS virus that does nothing except once every 3 minutes do
the equivalent of:

    echo "GET /index.html HTTP/1.0"; echo) | telnet -r $1 80

(maybe instead with a random request instead of /index.html)

After a few 1,000,000 desktops have been infected by familiar virus
vectors, the victim might notice the traffic.
How would you filter for them?  Even if you could give routers
enough processing power, what would you learn from the filtering
that you'd care to apply?


> ...
> So the costs boil down to more memory, more software, some
> pattern-matching hardware, and maintaining security relationships
> with your routing partners.

that's easy to say, but it doesn't sound likely to happen in my world.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Tue Feb 15 17:30:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA25964
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 17:30:02 -0500 (EST)
Received: from orion.nlanr.net (hwb.extern.ucsd.edu [137.110.73.213])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25936
	for <ietf@ietf.org>; Tue, 15 Feb 2000 17:29:08 -0500 (EST)
Received: (from hwb@localhost)
	by orion.nlanr.net (8.9.3/8.9.3) id OAA05627;
	Tue, 15 Feb 2000 14:29:02 -0800
Message-ID: <20000215142900.16813@nlanr.net>
Date: Tue, 15 Feb 2000 14:29:00 -0800
From: Hans-Werner Braun <hwb@nlanr.net>
To: ietf@ietf.org
Subject: NATimes announcement
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Loop: ietf@ietf.org

We are pleased to announce the release of the first issue of our
newsletter of the NLANR measurement and network analysis team: The Network
Analysis Times.  It is available at: http://moat.nlanr.net/NATimes/.

This issue includes brief overviews and the current status of each of the
areas that form the core of our measurement and network analysis research:
passive header trace data and active performance measurements.  Also
presented in this issue are an article on the Cichlid 3-D visualization
system, as well as notes and updates from some of our collaborators on
their research projects.

We plan to use this electronic newsletter to share information about our
research and start dialogues on issues of mutual interest in network
analysis. There are many possibilities for new areas of research that
will build upon our current Network Analysis Infrastructure and give us
more understanding of areas such as Internet workload profiles, service
characteristics and performance, models, metrics, and simulation.

We look forward to receiving feedback from you, and working together to
gain more insight and knowledge into the inner workings of the Internet
and continue to work towards maximizing it as a resource.

If you want to get notification of new issues, please let us know at
natimes@nlanr.net. In addition, if you have questions or comments,
or would like to add short articles to future issues of the NATimes,
please discuss it with us at the same address.



From owner-ietf-outbound@ietf.org  Tue Feb 15 17:36:58 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26237
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Feb 2000 17:36:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA19719;
	Tue, 15 Feb 2000 17:34:56 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id RAA25964
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 17:30:02 -0500 (EST)
Received: from orion.nlanr.net (hwb.extern.ucsd.edu [137.110.73.213])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25936
	for <ietf@ietf.org>; Tue, 15 Feb 2000 17:29:08 -0500 (EST)
Received: (from hwb@localhost)
	by orion.nlanr.net (8.9.3/8.9.3) id OAA05627;
	Tue, 15 Feb 2000 14:29:02 -0800
Message-ID: <20000215142900.16813@nlanr.net>
Date: Tue, 15 Feb 2000 14:29:00 -0800
From: Hans-Werner Braun <hwb@nlanr.net>
To: ietf@ietf.org
Subject: NATimes announcement
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Loop: ietf@ietf.org

We are pleased to announce the release of the first issue of our
newsletter of the NLANR measurement and network analysis team: The Network
Analysis Times.  It is available at: http://moat.nlanr.net/NATimes/.

This issue includes brief overviews and the current status of each of the
areas that form the core of our measurement and network analysis research:
passive header trace data and active performance measurements.  Also
presented in this issue are an article on the Cichlid 3-D visualization
system, as well as notes and updates from some of our collaborators on
their research projects.

We plan to use this electronic newsletter to share information about our
research and start dialogues on issues of mutual interest in network
analysis. There are many possibilities for new areas of research that
will build upon our current Network Analysis Infrastructure and give us
more understanding of areas such as Internet workload profiles, service
characteristics and performance, models, metrics, and simulation.

We look forward to receiving feedback from you, and working together to
gain more insight and knowledge into the inner workings of the Internet
and continue to work towards maximizing it as a resource.

If you want to get notification of new issues, please let us know at
natimes@nlanr.net. In addition, if you have questions or comments,
or would like to add short articles to future issues of the NATimes,
please discuss it with us at the same address.



From owner-ietf-outbound  Tue Feb 15 18:00:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA26808
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 18:00:02 -0500 (EST)
Received: from jhawk-foo.bbnplanet.com (jhawk-foo.bbnplanet.com [199.94.208.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26716
	for <IETF@ietf.org>; Tue, 15 Feb 2000 17:58:13 -0500 (EST)
Received: (from jhawk@localhost)
	by jhawk-foo.bbnplanet.com (8.8.8+Sun/8.8.8) id RAA07368;
	Tue, 15 Feb 2000 17:58:02 -0500 (EST)
Date: Tue, 15 Feb 2000 17:58:02 -0500
From: John Hawkinson <jhawk@bbnplanet.com>
To: "Charles E. Perkins" <charliep@iprg.nokia.com>
Cc: IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
Message-ID: <20000215175802.G19709@jhawk-foo.bbnplanet.com>
References: <200002151722.KAA28768@calcite.rhyolite.com> <38A9C6E9.37203AE6@iprg.nokia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.1.1i
In-Reply-To: <38A9C6E9.37203AE6@iprg.nokia.com>; from charliep@iprg.nokia.com on Tue, Feb 15, 2000 at 01:36:41PM -0800
X-Loop: ietf@ietf.org

> But maybe filtering is putting the cart before the horse.

I believe in general we have been having a discussion about
operational practices, not really about theoretical ideas
of what we might be able to do twelve to eighteen months
out.

But discussing those theoretical things is good too, but I think
it's important to make clear what the scope of any
particular message in this thread here is, otherwise
confusion runs rampant.

Incidently, while we're here, you might look at Stefan Savage's paper
"http://www.cs.washington.edu/homes/savage/traceback.html", which kc
pointed NANOG at yesterday. I describe it as "having each router
probabilitically mark transit IP packets with a router-specific
locational referent in the ip_id field."

> >From that analogy, I claim that the appropriate action is to
> develop tracing systems that will help to identify a wrongdoer.
> Here is a possible design.

> - Create a router feature, able to be remotely activated, to keep
>   track of "suspicious" packets for a few seconds up to maybe a
>   couple dozen seconds.  Suspicious packets might be SYNs, or
>   even packets with "incorrect" source addresses.

That is a lot of suspicious packets. Is a packet to a random UDP port
"suspicious"? If not, then this scheme is mostly useless against our
most recent series of attacks. If it is suspicious, then the attackers
will switch to TCP packets -- are those suspicious too?  Are all
packets suspicious?

> - If a violation is noticed, determine the interface on which a
>   bad packet was received, and send a request to that neighbor
>   along with appropriate credentials that can be checked.

This generates more traffic in the network for each of these; when the
problem is traffic flooding, as it has been most recently, this may be
unwise.

What would a credential check involve? Where would these
credentials be issued from and how-validated?

> - If, on the other hand, a neighbor sends a request for tracing
>   a problematic packet, check the credentials that accompany the
>   request and look at the stored data for that packet.  If no
>   stored data exists, send back the bad news, and possibly enable
>   the pattern-matchine function to capture similarly featured
>   packets in case of future requests.

This suggests some sort of AI, or at least relatively clever
heuristics.  My brain says "research problem--IRTF--bye!" Perhaps
that's unfair?

> - If a neighbor's request refers to a stored packet, figure out
>   what interface the stored packet arrived on.  If the packet
>   came from another neighbor, forward the request.  Otherwise,
>   look for the malicious source internal to the domain.

Where look for is "send a message to an operator"? How does this work
across multiple routing domains (e.g. provider boundaries)?

> The basic idea then would be to trace back bad packets that
> conform to some typically innocent, but occasionally troublesome,
> profiles.  The profiles will become self-evident with experience,
> and once people know they will be caught by this traceback
> system they will think twice before spreading their crap around.
> 
> According to one knowledgeable source, this strategy is undesirable
> because it would cause routers to maintain more state.

It appears to imply state on the order of 1 unit for each packet the
router transits. That's an immense amount of state.

> But, I claim that we have to maintain state to do any tracing, and I
> also claim that we need to enable tracing in order to detect and
> identify wrongdoers.

Yes, tracing requires state. How to distribute or limit that state is
the essessence of most of the discussion of tracing schemes.  Marking
packets puts the state inside them. Only collecting state on some
kinds of flows or in response to some trigger also limits the state.

> So the costs boil down to more memory, more software, some
> pattern-matching hardware, and maintaining security relationships
> with your routing partners.

Sure.

I think that doing anything other than what already has been done that
might loosely fit your description is likely to be terribly
unpractical and feels like a research problem.

> I think it's a very worthwhile tradeoff.  Much better than mostly
> ineffective measures that have big negative effects and small
> positive effects, characteristics of ingress filtering as I
> understand it.

Ingress filtering is something we can do today, and has a very small
negative effect -- it limits the ability of some people who use the
network in non-traditional ways (half-tunneled setups, etc.), and
those people can simply request a broader ingress filter; I haven't
seen an example of how that fails, except when the people doing
the ingress filtering refuse, and that's not a problem with ingress
filtering, but instead a problem of politics.

--jhawk



From owner-ietf-outbound@ietf.org  Tue Feb 15 18:07:50 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27007
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Feb 2000 18:07:50 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA20431;
	Tue, 15 Feb 2000 18:05:50 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id SAA26808
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 18:00:02 -0500 (EST)
Received: from jhawk-foo.bbnplanet.com (jhawk-foo.bbnplanet.com [199.94.208.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26716
	for <IETF@ietf.org>; Tue, 15 Feb 2000 17:58:13 -0500 (EST)
Received: (from jhawk@localhost)
	by jhawk-foo.bbnplanet.com (8.8.8+Sun/8.8.8) id RAA07368;
	Tue, 15 Feb 2000 17:58:02 -0500 (EST)
Date: Tue, 15 Feb 2000 17:58:02 -0500
From: John Hawkinson <jhawk@bbnplanet.com>
To: "Charles E. Perkins" <charliep@iprg.nokia.com>
Cc: IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
Message-ID: <20000215175802.G19709@jhawk-foo.bbnplanet.com>
References: <200002151722.KAA28768@calcite.rhyolite.com> <38A9C6E9.37203AE6@iprg.nokia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.1.1i
In-Reply-To: <38A9C6E9.37203AE6@iprg.nokia.com>; from charliep@iprg.nokia.com on Tue, Feb 15, 2000 at 01:36:41PM -0800
X-Loop: ietf@ietf.org

> But maybe filtering is putting the cart before the horse.

I believe in general we have been having a discussion about
operational practices, not really about theoretical ideas
of what we might be able to do twelve to eighteen months
out.

But discussing those theoretical things is good too, but I think
it's important to make clear what the scope of any
particular message in this thread here is, otherwise
confusion runs rampant.

Incidently, while we're here, you might look at Stefan Savage's paper
"http://www.cs.washington.edu/homes/savage/traceback.html", which kc
pointed NANOG at yesterday. I describe it as "having each router
probabilitically mark transit IP packets with a router-specific
locational referent in the ip_id field."

> >From that analogy, I claim that the appropriate action is to
> develop tracing systems that will help to identify a wrongdoer.
> Here is a possible design.

> - Create a router feature, able to be remotely activated, to keep
>   track of "suspicious" packets for a few seconds up to maybe a
>   couple dozen seconds.  Suspicious packets might be SYNs, or
>   even packets with "incorrect" source addresses.

That is a lot of suspicious packets. Is a packet to a random UDP port
"suspicious"? If not, then this scheme is mostly useless against our
most recent series of attacks. If it is suspicious, then the attackers
will switch to TCP packets -- are those suspicious too?  Are all
packets suspicious?

> - If a violation is noticed, determine the interface on which a
>   bad packet was received, and send a request to that neighbor
>   along with appropriate credentials that can be checked.

This generates more traffic in the network for each of these; when the
problem is traffic flooding, as it has been most recently, this may be
unwise.

What would a credential check involve? Where would these
credentials be issued from and how-validated?

> - If, on the other hand, a neighbor sends a request for tracing
>   a problematic packet, check the credentials that accompany the
>   request and look at the stored data for that packet.  If no
>   stored data exists, send back the bad news, and possibly enable
>   the pattern-matchine function to capture similarly featured
>   packets in case of future requests.

This suggests some sort of AI, or at least relatively clever
heuristics.  My brain says "research problem--IRTF--bye!" Perhaps
that's unfair?

> - If a neighbor's request refers to a stored packet, figure out
>   what interface the stored packet arrived on.  If the packet
>   came from another neighbor, forward the request.  Otherwise,
>   look for the malicious source internal to the domain.

Where look for is "send a message to an operator"? How does this work
across multiple routing domains (e.g. provider boundaries)?

> The basic idea then would be to trace back bad packets that
> conform to some typically innocent, but occasionally troublesome,
> profiles.  The profiles will become self-evident with experience,
> and once people know they will be caught by this traceback
> system they will think twice before spreading their crap around.
> 
> According to one knowledgeable source, this strategy is undesirable
> because it would cause routers to maintain more state.

It appears to imply state on the order of 1 unit for each packet the
router transits. That's an immense amount of state.

> But, I claim that we have to maintain state to do any tracing, and I
> also claim that we need to enable tracing in order to detect and
> identify wrongdoers.

Yes, tracing requires state. How to distribute or limit that state is
the essessence of most of the discussion of tracing schemes.  Marking
packets puts the state inside them. Only collecting state on some
kinds of flows or in response to some trigger also limits the state.

> So the costs boil down to more memory, more software, some
> pattern-matching hardware, and maintaining security relationships
> with your routing partners.

Sure.

I think that doing anything other than what already has been done that
might loosely fit your description is likely to be terribly
unpractical and feels like a research problem.

> I think it's a very worthwhile tradeoff.  Much better than mostly
> ineffective measures that have big negative effects and small
> positive effects, characteristics of ingress filtering as I
> understand it.

Ingress filtering is something we can do today, and has a very small
negative effect -- it limits the ability of some people who use the
network in non-traditional ways (half-tunneled setups, etc.), and
those people can simply request a broader ingress filter; I haven't
seen an example of how that fails, except when the people doing
the ingress filtering refuse, and that's not a problem with ingress
filtering, but instead a problem of politics.

--jhawk



From owner-ietf-outbound  Tue Feb 15 18:40:32 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA27602
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 18:40:02 -0500 (EST)
Received: from fepC.post.tele.dk (fepC.post.tele.dk [195.41.46.147])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27468
	for <ietf@ietf.org>; Tue, 15 Feb 2000 18:31:58 -0500 (EST)
Received: from Anders ([194.239.165.175]) by fepC.post.tele.dk
          (InterMail vM.4.01.02.00 201-229-116) with SMTP
          id <20000215233159.HSPB706.fepC.post.tele.dk@Anders>
          for <ietf@ietf.org>; Wed, 16 Feb 2000 00:31:59 +0100
Message-ID: <005401bf780c$e3029080$1000000a@DIC>
From: "Anders Feder" <anders@feder.dk>
To: <ietf@ietf.org>
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
Date: Wed, 16 Feb 2000 00:32:03 +0100
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 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

I think that, believing that the world is no bigger than America is a common
problem among many US citizens. No offense, so would I if I lived in US,
because after all there is quite a few states and cities to keep track of.
But my point is that we, including the Americans, speak so proudly of the
Internet as this global network interconnecting millions of computers around
the world providing a relatively cheap means of communicating and informing
across borders. Europe, Asia, Africa and Australia have all payed their part
of what makes up this Internet, just like the US have. And yet some US
citizens feel that the 'net somehow belongs to them and that they are
superior in deciding its future. Luckily, German Daimler-Benz wasn't that
short-sighted when they invented the automobile a century ago.

- Anders Feder



From owner-ietf-outbound@ietf.org  Tue Feb 15 18:44:47 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27710
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Feb 2000 18:44:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA21166;
	Tue, 15 Feb 2000 18:42:47 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id SAA27602
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 18:40:02 -0500 (EST)
Received: from fepC.post.tele.dk (fepC.post.tele.dk [195.41.46.147])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27468
	for <ietf@ietf.org>; Tue, 15 Feb 2000 18:31:58 -0500 (EST)
Received: from Anders ([194.239.165.175]) by fepC.post.tele.dk
          (InterMail vM.4.01.02.00 201-229-116) with SMTP
          id <20000215233159.HSPB706.fepC.post.tele.dk@Anders>
          for <ietf@ietf.org>; Wed, 16 Feb 2000 00:31:59 +0100
Message-ID: <005401bf780c$e3029080$1000000a@DIC>
From: "Anders Feder" <anders@feder.dk>
To: <ietf@ietf.org>
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
Date: Wed, 16 Feb 2000 00:32:03 +0100
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 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I think that, believing that the world is no bigger than America is a common
problem among many US citizens. No offense, so would I if I lived in US,
because after all there is quite a few states and cities to keep track of.
But my point is that we, including the Americans, speak so proudly of the
Internet as this global network interconnecting millions of computers around
the world providing a relatively cheap means of communicating and informing
across borders. Europe, Asia, Africa and Australia have all payed their part
of what makes up this Internet, just like the US have. And yet some US
citizens feel that the 'net somehow belongs to them and that they are
superior in deciding its future. Luckily, German Daimler-Benz wasn't that
short-sighted when they invented the automobile a century ago.

- Anders Feder



From owner-ietf-outbound  Tue Feb 15 18:50:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA27842
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 18:50:02 -0500 (EST)
Received: from leonid.genesyslab.com (pbinat33.genesyslab.com [209.233.177.33])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27573
	for <IETF@ietf.org>; Tue, 15 Feb 2000 18:39:14 -0500 (EST)
Received: (from egoshin@localhost)
	by leonid.genesyslab.com (8.9.3/8.9.3) id QAA01543
	for IETF@ietf.org; Tue, 15 Feb 2000 16:45:38 -0800
Date: Tue, 15 Feb 2000 16:45:38 -0800
From: Leonid Yegoshin <egoshin@genesyslab.com>
Message-Id: <200002160045.QAA01543@leonid.genesyslab.com>
To: IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
X-Loop: ietf@ietf.org

>From: Vernon Schryver <vjs@calcite.rhyolite.com>
>
>> ...
>> The basic idea then would be to trace back bad packets that
>> conform to some typically innocent, but occasionally troublesome,
>> profiles.  The profiles will become self-evident with experience,
>> and once people know they will be caught by this traceback
>> system they will think twice before spreading their crap around.
>
>If I were building a DDoS engine today, I'd write a conventional
>(Microsoft) DOS virus that does nothing except once every 3 minutes do
>the equivalent of:
>
>    echo "GET /index.html HTTP/1.0"; echo) | telnet -r $1 80
>
>(maybe instead with a random request instead of /index.html)
>
>After a few 1,000,000 desktops have been infected by familiar virus
>vectors, the victim might notice the traffic.
>How would you filter for them?  Even if you could give routers
>enough processing power, what would you learn from the filtering
>that you'd care to apply?

  It is possible to get more big bang in this case: virus may asks
DNS servers about some generated domain names. Algoritm to fight
negative caching effect is simple. With millions names in .com
there is a long way to keep asking.

			       - Leonid Yegoshin, LY22



From owner-ietf-outbound@ietf.org  Tue Feb 15 18:53:04 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27898
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Feb 2000 18:53:03 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA21315;
	Tue, 15 Feb 2000 18:51:04 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id SAA27842
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 18:50:02 -0500 (EST)
Received: from leonid.genesyslab.com (pbinat33.genesyslab.com [209.233.177.33])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27573
	for <IETF@ietf.org>; Tue, 15 Feb 2000 18:39:14 -0500 (EST)
Received: (from egoshin@localhost)
	by leonid.genesyslab.com (8.9.3/8.9.3) id QAA01543
	for IETF@ietf.org; Tue, 15 Feb 2000 16:45:38 -0800
Date: Tue, 15 Feb 2000 16:45:38 -0800
From: Leonid Yegoshin <egoshin@genesyslab.com>
Message-Id: <200002160045.QAA01543@leonid.genesyslab.com>
To: IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
X-Loop: ietf@ietf.org

>From: Vernon Schryver <vjs@calcite.rhyolite.com>
>
>> ...
>> The basic idea then would be to trace back bad packets that
>> conform to some typically innocent, but occasionally troublesome,
>> profiles.  The profiles will become self-evident with experience,
>> and once people know they will be caught by this traceback
>> system they will think twice before spreading their crap around.
>
>If I were building a DDoS engine today, I'd write a conventional
>(Microsoft) DOS virus that does nothing except once every 3 minutes do
>the equivalent of:
>
>    echo "GET /index.html HTTP/1.0"; echo) | telnet -r $1 80
>
>(maybe instead with a random request instead of /index.html)
>
>After a few 1,000,000 desktops have been infected by familiar virus
>vectors, the victim might notice the traffic.
>How would you filter for them?  Even if you could give routers
>enough processing power, what would you learn from the filtering
>that you'd care to apply?

  It is possible to get more big bang in this case: virus may asks
DNS servers about some generated domain names. Algoritm to fight
negative caching effect is simple. With millions names in .com
there is a long way to keep asking.

			       - Leonid Yegoshin, LY22



From owner-ietf-outbound  Tue Feb 15 19:00:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA28025
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 19:00:02 -0500 (EST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27633
	for <ietf@ietf.org>; Tue, 15 Feb 2000 18:40:57 -0500 (EST)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200002152339.IAA17427@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id IAA17427; Wed, 16 Feb 2000 08:38:51 +0859
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
To: jaltman@columbia.edu
Date: Wed, 16 Feb 0 8:38:49 JST
Cc: ietf@ietf.org
In-Reply-To: <CMM.0.90.4.950639405.jaltman@watsun.cc.columbia.edu>; from "Jeffrey Altman" at Feb 16, 100 4:52 am
X-Mailer: ELM [version 2.3 PL11]
X-Loop: ietf@ietf.org

Jeffry;

IETF is certainly US and English centric.

The current rules of IETF does not explicitely prefer some country
so much, though many important organizations have addresses in US
and English is the language of the rules. However, the rules keep
or amplify the US centric tendency, because a large number of US
participants means a large number of IAB/IESG members is likely to
be nominated.

Moreover, English centric IETF meetings are hard to be actively
attended by people whose primary language is not English. Compared
to other International organizations, IETF requires too much in
English capability. Worse, in IETF, inactive participation is
nothing.

Having a meeting in AU does not solve the latter, English, problem.

However,

> The problem I have with the Adelaide meeting is very simple.  With so
> few working groups holding sessions, I can't justify making the trip.
> This would be true for a meeting at any location more than 400 miles
> away.  If only one group that I am interested in is holding a session,
> I can't go.  The powers that be just won't approve it.

it is a good solution for the first, US, problem.

Moreover, you are saying that the recent problem of IETF that there are
too many bogus WGs with too many people is also solved.

Very good.

So, all the future IETF meetings should be held in areas far away
from US and, in addition, where English is not the major language.

There many be an exception once in 10 years, of course.

							Masataka Ohta



From owner-ietf-outbound@ietf.org  Tue Feb 15 19:03:05 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28173
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Feb 2000 19:03:05 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA21568;
	Tue, 15 Feb 2000 19:01:05 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id TAA28025
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 19:00:02 -0500 (EST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27633
	for <ietf@ietf.org>; Tue, 15 Feb 2000 18:40:57 -0500 (EST)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200002152339.IAA17427@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id IAA17427; Wed, 16 Feb 2000 08:38:51 +0859
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
To: jaltman@columbia.edu
Date: Wed, 16 Feb 0 8:38:49 JST
Cc: ietf@ietf.org
In-Reply-To: <CMM.0.90.4.950639405.jaltman@watsun.cc.columbia.edu>; from "Jeffrey Altman" at Feb 16, 100 4:52 am
X-Mailer: ELM [version 2.3 PL11]
X-Loop: ietf@ietf.org

Jeffry;

IETF is certainly US and English centric.

The current rules of IETF does not explicitely prefer some country
so much, though many important organizations have addresses in US
and English is the language of the rules. However, the rules keep
or amplify the US centric tendency, because a large number of US
participants means a large number of IAB/IESG members is likely to
be nominated.

Moreover, English centric IETF meetings are hard to be actively
attended by people whose primary language is not English. Compared
to other International organizations, IETF requires too much in
English capability. Worse, in IETF, inactive participation is
nothing.

Having a meeting in AU does not solve the latter, English, problem.

However,

> The problem I have with the Adelaide meeting is very simple.  With so
> few working groups holding sessions, I can't justify making the trip.
> This would be true for a meeting at any location more than 400 miles
> away.  If only one group that I am interested in is holding a session,
> I can't go.  The powers that be just won't approve it.

it is a good solution for the first, US, problem.

Moreover, you are saying that the recent problem of IETF that there are
too many bogus WGs with too many people is also solved.

Very good.

So, all the future IETF meetings should be held in areas far away
from US and, in addition, where English is not the major language.

There many be an exception once in 10 years, of course.

							Masataka Ohta



From owner-ietf-outbound  Tue Feb 15 19:10:15 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA28394
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 19:10:02 -0500 (EST)
Received: from fepC.post.tele.dk (fepC.post.tele.dk [195.41.46.147])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27650
	for <ietf@ietf.org>; Tue, 15 Feb 2000 18:41:33 -0500 (EST)
Received: from Anders ([194.239.165.175]) by fepC.post.tele.dk
          (InterMail vM.4.01.02.00 201-229-116) with SMTP
          id <20000215234135.HTCB706.fepC.post.tele.dk@Anders>
          for <ietf@ietf.org>; Wed, 16 Feb 2000 00:41:35 +0100
Message-ID: <007201bf780e$38918780$1000000a@DIC>
From: "Anders Feder" <lists.anders@feder.dk>
To: <ietf@ietf.org>
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
Date: Wed, 16 Feb 2000 00:41:39 +0100
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 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

I think that, believing that the world is no bigger than America is a common
problem among many US citizens. No offense, so would I if I lived in US,
because after all there is quite a few states and cities to keep track of.
But my point is that we, including the Americans, speak so proudly of the
Internet as this global network interconnecting millions of computers around
the world providing a relatively cheap means of communicating and informing
across borders. Europe, Asia, Africa and Australia have all payed their part
of what makes up this Internet, just like the US have. And yet some US
citizens feel that the 'net somehow belongs to them and that they are
superior in deciding its future. Luckily, German Daimler-Benz wasn't that
short-sighted when they invented the automobile a century ago.

- Anders Feder



From owner-ietf-outbound@ietf.org  Tue Feb 15 19:12:39 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28541
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Feb 2000 19:12:39 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA21822;
	Tue, 15 Feb 2000 19:10:39 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id TAA28394
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 19:10:02 -0500 (EST)
Received: from fepC.post.tele.dk (fepC.post.tele.dk [195.41.46.147])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27650
	for <ietf@ietf.org>; Tue, 15 Feb 2000 18:41:33 -0500 (EST)
Received: from Anders ([194.239.165.175]) by fepC.post.tele.dk
          (InterMail vM.4.01.02.00 201-229-116) with SMTP
          id <20000215234135.HTCB706.fepC.post.tele.dk@Anders>
          for <ietf@ietf.org>; Wed, 16 Feb 2000 00:41:35 +0100
Message-ID: <007201bf780e$38918780$1000000a@DIC>
From: "Anders Feder" <lists.anders@feder.dk>
To: <ietf@ietf.org>
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
Date: Wed, 16 Feb 2000 00:41:39 +0100
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 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I think that, believing that the world is no bigger than America is a common
problem among many US citizens. No offense, so would I if I lived in US,
because after all there is quite a few states and cities to keep track of.
But my point is that we, including the Americans, speak so proudly of the
Internet as this global network interconnecting millions of computers around
the world providing a relatively cheap means of communicating and informing
across borders. Europe, Asia, Africa and Australia have all payed their part
of what makes up this Internet, just like the US have. And yet some US
citizens feel that the 'net somehow belongs to them and that they are
superior in deciding its future. Luckily, German Daimler-Benz wasn't that
short-sighted when they invented the automobile a century ago.

- Anders Feder



From owner-ietf-outbound  Tue Feb 15 19:20:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA28709
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 19:20:04 -0500 (EST)
Received: from A4.JCK.COM (ns.jck.com [63.65.7.140])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28641
	for <ietf@ietf.org>; Tue, 15 Feb 2000 19:17:42 -0500 (EST)
Received: from p2.jck.com ("port 2825"@[63.65.7.138])
 by a4.jck.com (PMDF V6.0-20 #40360) with ESMTP id <0FPZ002BPY5SM1@a4.jck.com>
 for ietf@ietf.org; Tue, 15 Feb 2000 19:17:52 -0500 (EST)
Date: Tue, 15 Feb 2000 19:17:45 -0500
From: John C Klensin <klensin@jck.com>
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
In-reply-to: <200002152122.PAA87218@us.networkcs.com>
To: Tim Salo <salo@networkcs.com>
Cc: ietf@ietf.org
Message-id: <1454492894.950642265@p2.jck.com>
MIME-version: 1.0
X-Mailer: Mulberry/2.0.0b8 (Win32)
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7bit
Content-disposition: inline
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

--On Tuesday, 15 February, 2000 15:22 -0600 Tim Salo 
<salo@networkcs.com> wrote:

> Of course, that leads to the rather interesting dilemma that
> we don't know whether an individual is speaking on behalf or
> his or her self or on behalf of an organization, (again, even
> if we tell that person that _we_ know which it is).

FWIW, in some other standards bodies, there is a policy that, if 
one wants to (or is constrained to) speak on behalf of an 
organization, or arrives with instructions as to what to say 
that the individual cannot change after hearing arguments in the 
meeting, those restrictions/relationships must be disclosed. 
The rule is unenforceable, but provides some protection to the 
individual (especially in "my company is full of idiots, but 
please don't mistake me for one" situations) and for the 
standards group.

   john



From owner-ietf-outbound@ietf.org  Tue Feb 15 19:22:35 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28788
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Feb 2000 19:22:35 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA22120;
	Tue, 15 Feb 2000 19:20:34 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id TAA28709
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 19:20:04 -0500 (EST)
Received: from A4.JCK.COM (ns.jck.com [63.65.7.140])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28641
	for <ietf@ietf.org>; Tue, 15 Feb 2000 19:17:42 -0500 (EST)
Received: from p2.jck.com ("port 2825"@[63.65.7.138])
 by a4.jck.com (PMDF V6.0-20 #40360) with ESMTP id <0FPZ002BPY5SM1@a4.jck.com>
 for ietf@ietf.org; Tue, 15 Feb 2000 19:17:52 -0500 (EST)
Date: Tue, 15 Feb 2000 19:17:45 -0500
From: John C Klensin <klensin@jck.com>
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
In-reply-to: <200002152122.PAA87218@us.networkcs.com>
To: Tim Salo <salo@networkcs.com>
Cc: ietf@ietf.org
Message-id: <1454492894.950642265@p2.jck.com>
MIME-version: 1.0
X-Mailer: Mulberry/2.0.0b8 (Win32)
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7bit
Content-disposition: inline
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

--On Tuesday, 15 February, 2000 15:22 -0600 Tim Salo 
<salo@networkcs.com> wrote:

> Of course, that leads to the rather interesting dilemma that
> we don't know whether an individual is speaking on behalf or
> his or her self or on behalf of an organization, (again, even
> if we tell that person that _we_ know which it is).

FWIW, in some other standards bodies, there is a policy that, if 
one wants to (or is constrained to) speak on behalf of an 
organization, or arrives with instructions as to what to say 
that the individual cannot change after hearing arguments in the 
meeting, those restrictions/relationships must be disclosed. 
The rule is unenforceable, but provides some protection to the 
individual (especially in "my company is full of idiots, but 
please don't mistake me for one" situations) and for the 
standards group.

   john



From owner-ietf-outbound  Tue Feb 15 21:41:57 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA01111
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 21:40:03 -0500 (EST)
Received: from torque.pothole.com ([209.94.126.195])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01024
	for <ietf@ietf.org>; Tue, 15 Feb 2000 21:33:28 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by torque.pothole.com (8.8.2/8.8.8) with SMTP id VAA18269
	for ietf@ietf.org; Tue, 15 Feb 2000 21:33:52 -0500 (EST)
Message-Id: <200002160233.VAA18269@torque.pothole.com>
X-Authentication-Warning: torque.pothole.com: localhost [127.0.0.1] didn't use HELO protocol
To: ietf@ietf.org
Subject: Re: IETF Adelaide and interim meetings for APPS WGs 
In-reply-to: Your message of "Tue, 15 Feb 2000 16:51:44 EST."
             <4.2.2.20000215165106.00aae4f0@kanmail01.ca.newbridge.com> 
Date: Tue, 15 Feb 2000 21:33:52 -0500
From: "Donald E. Eastlake 3rd" <dee3@torque.pothole.com>
X-Mts: smtp
X-Loop: ietf@ietf.org


It is traditional that most IETF meeting attendees have given the
organization they are affiliated with for identification purposes,
whether it is an educational institution, government, other non-profit
group or company.

Donald

PS: I don't see "being international" as a binary thing.  Or at least
I don't know of any orgnaization, including the UN, that you can claim
is "perfectly" international.  After all, there are plenty of
languages that are not official UN languages and there are always
distinctions based on whether you are privileged to have a permanent
seat on the Security Council or have the UN HQ in your country, etc.

The primary concern in the IETF is producing good protocols.  I would
hope that anyone whose primary concern is how international the IETF
is would find more fertile ground in some other organization.

From:  "Scott W Brim" <swb@NEWBRIDGE.COM>
Message-Id:  <4.2.2.20000215165106.00aae4f0@kanmail01.ca.newbridge.com>
Date:  Tue, 15 Feb 2000 16:51:44 -0500
To:  ietf@ietf.org
In-Reply-To:  <200002152122.PAA87218@us.networkcs.com>
References:  <200002151914.LAA20085@zed.isi.edu>

>Why does the IETF registration form ask for a company name?
>
>> > From: Bill Manning <bmanning@ISI.EDU>
>> > Subject: Re: IETF Adelaide and interim meetings for APPS WGs
>> > To: mart.nurmet@inet.com (Mart Nurmet)
>> > Date: Tue, 15 Feb 2000 11:14:26 -0800 (PST)
>> > Cc: ietf@ietf.org
>> >       [...]
>> > and note that the IETF is composed of indivduals, not corporations.
>> > You should not presume to "represent" a corporate entity within the
>> > IETF. Your just the best engineer you can be.
>



From owner-ietf-outbound@ietf.org  Tue Feb 15 21:45:36 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01756
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Feb 2000 21:45:36 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA26443;
	Tue, 15 Feb 2000 21:43:32 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id VAA01111
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 21:40:03 -0500 (EST)
Received: from torque.pothole.com ([209.94.126.195])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01024
	for <ietf@ietf.org>; Tue, 15 Feb 2000 21:33:28 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by torque.pothole.com (8.8.2/8.8.8) with SMTP id VAA18269
	for ietf@ietf.org; Tue, 15 Feb 2000 21:33:52 -0500 (EST)
Message-Id: <200002160233.VAA18269@torque.pothole.com>
X-Authentication-Warning: torque.pothole.com: localhost [127.0.0.1] didn't use HELO protocol
To: ietf@ietf.org
Subject: Re: IETF Adelaide and interim meetings for APPS WGs 
In-reply-to: Your message of "Tue, 15 Feb 2000 16:51:44 EST."
             <4.2.2.20000215165106.00aae4f0@kanmail01.ca.newbridge.com> 
Date: Tue, 15 Feb 2000 21:33:52 -0500
From: "Donald E. Eastlake 3rd" <dee3@torque.pothole.com>
X-Mts: smtp
X-Loop: ietf@ietf.org


It is traditional that most IETF meeting attendees have given the
organization they are affiliated with for identification purposes,
whether it is an educational institution, government, other non-profit
group or company.

Donald

PS: I don't see "being international" as a binary thing.  Or at least
I don't know of any orgnaization, including the UN, that you can claim
is "perfectly" international.  After all, there are plenty of
languages that are not official UN languages and there are always
distinctions based on whether you are privileged to have a permanent
seat on the Security Council or have the UN HQ in your country, etc.

The primary concern in the IETF is producing good protocols.  I would
hope that anyone whose primary concern is how international the IETF
is would find more fertile ground in some other organization.

From:  "Scott W Brim" <swb@NEWBRIDGE.COM>
Message-Id:  <4.2.2.20000215165106.00aae4f0@kanmail01.ca.newbridge.com>
Date:  Tue, 15 Feb 2000 16:51:44 -0500
To:  ietf@ietf.org
In-Reply-To:  <200002152122.PAA87218@us.networkcs.com>
References:  <200002151914.LAA20085@zed.isi.edu>

>Why does the IETF registration form ask for a company name?
>
>> > From: Bill Manning <bmanning@ISI.EDU>
>> > Subject: Re: IETF Adelaide and interim meetings for APPS WGs
>> > To: mart.nurmet@inet.com (Mart Nurmet)
>> > Date: Tue, 15 Feb 2000 11:14:26 -0800 (PST)
>> > Cc: ietf@ietf.org
>> >       [...]
>> > and note that the IETF is composed of indivduals, not corporations.
>> > You should not presume to "represent" a corporate entity within the
>> > IETF. Your just the best engineer you can be.
>



From owner-ietf-outbound  Tue Feb 15 23:20:50 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA04966
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 23:20:02 -0500 (EST)
Received: from off.org (peace.off.org [206.163.206.2])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA04897
	for <ietf@ietf.org>; Tue, 15 Feb 2000 23:16:49 -0500 (EST)
Received: (qmail 23713 invoked by uid 1001); 16 Feb 2000 04:14:52 -0000
Date: Tue, 15 Feb 2000 20:14:52 -0800
From: Austin Schutz <tex@OFF.ORG>
To: ietf@ietf.org
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
Message-ID: <20000215201452.F20408@off.org>
References: <CMM.0.90.4.950639405.jaltman@watsun.cc.columbia.edu> <200002152339.IAA17427@necom830.hpcl.titech.ac.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <200002152339.IAA17427@necom830.hpcl.titech.ac.jp>; from mohta@necom830.hpcl.titech.ac.jp on Mon, Mar 24, 2036 at 03:07:05PM +0900
X-Loop: ietf@ietf.org

> Moreover, English centric IETF meetings are hard to be actively
> attended by people whose primary language is not English. Compared
> to other International organizations, IETF requires too much in
> English capability. Worse, in IETF, inactive participation is
> nothing.

	It wouuld be possible to have all the mailing lists redistributed
using some babelfish-like mechanism for translation, though obviously that
wouldn't cover all languages and wouldn't do any well. Maybe better than
nothing.
	Reality is there has to be a standard language unless you have the
vast resources of the UN. While I can fully understand why the rest of the
world wouldn't be happy with English as the choice for that language, there
isn't really any fundamental reason why it shouldn't be English.

	Austin



From owner-ietf-outbound@ietf.org  Tue Feb 15 23:23:29 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05097
	for <ietf-web-archive@odin.ietf.org>; Tue, 15 Feb 2000 23:23:29 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA29148;
	Tue, 15 Feb 2000 23:21:28 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id XAA04966
	for ietf-outbound.10@ietf.org; Tue, 15 Feb 2000 23:20:02 -0500 (EST)
Received: from off.org (peace.off.org [206.163.206.2])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA04897
	for <ietf@ietf.org>; Tue, 15 Feb 2000 23:16:49 -0500 (EST)
Received: (qmail 23713 invoked by uid 1001); 16 Feb 2000 04:14:52 -0000
Date: Tue, 15 Feb 2000 20:14:52 -0800
From: Austin Schutz <tex@OFF.ORG>
To: ietf@ietf.org
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
Message-ID: <20000215201452.F20408@off.org>
References: <CMM.0.90.4.950639405.jaltman@watsun.cc.columbia.edu> <200002152339.IAA17427@necom830.hpcl.titech.ac.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <200002152339.IAA17427@necom830.hpcl.titech.ac.jp>; from mohta@necom830.hpcl.titech.ac.jp on Mon, Mar 24, 2036 at 03:07:05PM +0900
X-Loop: ietf@ietf.org

> Moreover, English centric IETF meetings are hard to be actively
> attended by people whose primary language is not English. Compared
> to other International organizations, IETF requires too much in
> English capability. Worse, in IETF, inactive participation is
> nothing.

	It wouuld be possible to have all the mailing lists redistributed
using some babelfish-like mechanism for translation, though obviously that
wouldn't cover all languages and wouldn't do any well. Maybe better than
nothing.
	Reality is there has to be a standard language unless you have the
vast resources of the UN. While I can fully understand why the rest of the
world wouldn't be happy with English as the choice for that language, there
isn't really any fundamental reason why it shouldn't be English.

	Austin



From owner-ietf-outbound  Wed Feb 16 00:50:27 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA06644
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 00:50:02 -0500 (EST)
Received: from mail4.microsoft.com (mail4.microsoft.com [131.107.3.122])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA06602
	for <ietf@ietf.org>; Wed, 16 Feb 2000 00:44:54 -0500 (EST)
Received: from 157.54.9.103 by mail4.microsoft.com (InterScan E-Mail VirusWall NT); Tue, 15 Feb 2000 21:44:20 -0800 (Pacific Standard Time)
Received: by INET-IMC-04 with Internet Mail Service (5.5.2651.58)
	id <FADPYB4Z>; Tue, 15 Feb 2000 21:44:16 -0800
Message-ID: <D5922CA42F8CD31189D800805F19A16C020610FE@RED-MSG-48>
From: Ian King <iking@microsoft.com>
To: "'Masataka Ohta'" <mohta@necom830.hpcl.titech.ac.jp>, jaltman@columbia.edu
Cc: ietf@ietf.org
Subject: RE: IETF Adelaide and interim meetings for APPS WGs
Date: Tue, 15 Feb 2000 21:44:14 -0800
X-Mailer: Internet Mail Service (5.5.2651.58)
X-Loop: ietf@ietf.org

IMHO, people are reading way too much into this.  

Most of the participation is by folks from the US -- that stat is raised at
every meeting.  BTW, the Internet started in the US, those neat maps
displayed at plenary sessions show an overwhelming focus of connectivity in
the US, and many many technology companies are located in the US.  

Notwithstanding, the organization does hold meetings both inside and outside
the US, because the Internet is a global entity with international
involvement.  While this is IMHO a Good Thing, reality is that the longer
trips sometimes pose a problem for some participants -- whether that's
traveling from the US to Australia, or Australia to the US.  Statistically,
the burden hits more people for meetings outside the US, simply because
regardless of where we hold the meetings, there are more attendees from the
US than from any other place.  (At this juncture, I would like to salute the
folks from outside the US who nonetheless attend the majority of US-based
meetings.)  

To those of you outside the US who don't think there are enough meetings
outside the US: IF YOU SPONSOR THEM, WE WILL COME.  I've seen the open,
standing invitations to sponsor meetings -- so step up and sponsor.  

For those who think Australia is a long way to go: you're right, if you are
in North America or Europe.  Many WG chairs may be making an 'economic'
decision -- or their employers have made it for them.  (I'm not going
because I don't want to be away from my new baby daughter yet.)  But since
the work REALLY gets done on the mailing lists (so we say, officially), you
can still make a difference, if you so choose.  Not to say I don't think
there's a lot of value to the face-to-face meetings, but when I chaired a
WG, I got a lot of great input from people who never attended a single WG
session in person.  

Bottom line: go if you can and wish to, don't whine if you can't or won't.
And please quit with the "conspiracy theories" about US-centricity -- it's
an accident of history, nothing more.  Don't expect us Americans (or US
residents) to feel guilty or go slit our wrists over it.  And for whatever
reason, English does seem to serve as a common tongue in the world of
technology -- again, I'm not going to apologize for it.  (And it doesn't
stop us from working hard to figure out how to represent ALL the languages
of humanity in digital form....)  

Please forgive my typing -- my daughter is keeping one arm busy.  
-- Ian King, Speech Product Group, MICROSOFT CORPORATION

-----Original Message-----
From: Masataka Ohta [mailto:mohta@necom830.hpcl.titech.ac.jp]
Sent: Tuesday, February 15, 2000 3:39 PM
To: jaltman@columbia.edu
Cc: ietf@ietf.org
Subject: Re: IETF Adelaide and interim meetings for APPS WGs


Jeffry;

IETF is certainly US and English centric.

The current rules of IETF does not explicitely prefer some country
so much, though many important organizations have addresses in US
and English is the language of the rules. However, the rules keep
or amplify the US centric tendency, because a large number of US
participants means a large number of IAB/IESG members is likely to
be nominated.

Moreover, English centric IETF meetings are hard to be actively
attended by people whose primary language is not English. Compared
to other International organizations, IETF requires too much in
English capability. Worse, in IETF, inactive participation is
nothing.

Having a meeting in AU does not solve the latter, English, problem.

However,

> The problem I have with the Adelaide meeting is very simple.  With so
> few working groups holding sessions, I can't justify making the trip.
> This would be true for a meeting at any location more than 400 miles
> away.  If only one group that I am interested in is holding a session,
> I can't go.  The powers that be just won't approve it.

it is a good solution for the first, US, problem.

Moreover, you are saying that the recent problem of IETF that there are
too many bogus WGs with too many people is also solved.

Very good.

So, all the future IETF meetings should be held in areas far away
from US and, in addition, where English is not the major language.

There many be an exception once in 10 years, of course.

							Masataka Ohta



From owner-ietf-outbound@ietf.org  Wed Feb 16 00:53:12 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06718
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Feb 2000 00:53:12 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA02022;
	Wed, 16 Feb 2000 00:50:36 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id AAA06644
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 00:50:02 -0500 (EST)
Received: from mail4.microsoft.com (mail4.microsoft.com [131.107.3.122])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA06602
	for <ietf@ietf.org>; Wed, 16 Feb 2000 00:44:54 -0500 (EST)
Received: from 157.54.9.103 by mail4.microsoft.com (InterScan E-Mail VirusWall NT); Tue, 15 Feb 2000 21:44:20 -0800 (Pacific Standard Time)
Received: by INET-IMC-04 with Internet Mail Service (5.5.2651.58)
	id <FADPYB4Z>; Tue, 15 Feb 2000 21:44:16 -0800
Message-ID: <D5922CA42F8CD31189D800805F19A16C020610FE@RED-MSG-48>
From: Ian King <iking@microsoft.com>
To: "'Masataka Ohta'" <mohta@necom830.hpcl.titech.ac.jp>, jaltman@columbia.edu
Cc: ietf@ietf.org
Subject: RE: IETF Adelaide and interim meetings for APPS WGs
Date: Tue, 15 Feb 2000 21:44:14 -0800
X-Mailer: Internet Mail Service (5.5.2651.58)
X-Loop: ietf@ietf.org

IMHO, people are reading way too much into this.  

Most of the participation is by folks from the US -- that stat is raised at
every meeting.  BTW, the Internet started in the US, those neat maps
displayed at plenary sessions show an overwhelming focus of connectivity in
the US, and many many technology companies are located in the US.  

Notwithstanding, the organization does hold meetings both inside and outside
the US, because the Internet is a global entity with international
involvement.  While this is IMHO a Good Thing, reality is that the longer
trips sometimes pose a problem for some participants -- whether that's
traveling from the US to Australia, or Australia to the US.  Statistically,
the burden hits more people for meetings outside the US, simply because
regardless of where we hold the meetings, there are more attendees from the
US than from any other place.  (At this juncture, I would like to salute the
folks from outside the US who nonetheless attend the majority of US-based
meetings.)  

To those of you outside the US who don't think there are enough meetings
outside the US: IF YOU SPONSOR THEM, WE WILL COME.  I've seen the open,
standing invitations to sponsor meetings -- so step up and sponsor.  

For those who think Australia is a long way to go: you're right, if you are
in North America or Europe.  Many WG chairs may be making an 'economic'
decision -- or their employers have made it for them.  (I'm not going
because I don't want to be away from my new baby daughter yet.)  But since
the work REALLY gets done on the mailing lists (so we say, officially), you
can still make a difference, if you so choose.  Not to say I don't think
there's a lot of value to the face-to-face meetings, but when I chaired a
WG, I got a lot of great input from people who never attended a single WG
session in person.  

Bottom line: go if you can and wish to, don't whine if you can't or won't.
And please quit with the "conspiracy theories" about US-centricity -- it's
an accident of history, nothing more.  Don't expect us Americans (or US
residents) to feel guilty or go slit our wrists over it.  And for whatever
reason, English does seem to serve as a common tongue in the world of
technology -- again, I'm not going to apologize for it.  (And it doesn't
stop us from working hard to figure out how to represent ALL the languages
of humanity in digital form....)  

Please forgive my typing -- my daughter is keeping one arm busy.  
-- Ian King, Speech Product Group, MICROSOFT CORPORATION

-----Original Message-----
From: Masataka Ohta [mailto:mohta@necom830.hpcl.titech.ac.jp]
Sent: Tuesday, February 15, 2000 3:39 PM
To: jaltman@columbia.edu
Cc: ietf@ietf.org
Subject: Re: IETF Adelaide and interim meetings for APPS WGs


Jeffry;

IETF is certainly US and English centric.

The current rules of IETF does not explicitely prefer some country
so much, though many important organizations have addresses in US
and English is the language of the rules. However, the rules keep
or amplify the US centric tendency, because a large number of US
participants means a large number of IAB/IESG members is likely to
be nominated.

Moreover, English centric IETF meetings are hard to be actively
attended by people whose primary language is not English. Compared
to other International organizations, IETF requires too much in
English capability. Worse, in IETF, inactive participation is
nothing.

Having a meeting in AU does not solve the latter, English, problem.

However,

> The problem I have with the Adelaide meeting is very simple.  With so
> few working groups holding sessions, I can't justify making the trip.
> This would be true for a meeting at any location more than 400 miles
> away.  If only one group that I am interested in is holding a session,
> I can't go.  The powers that be just won't approve it.

it is a good solution for the first, US, problem.

Moreover, you are saying that the recent problem of IETF that there are
too many bogus WGs with too many people is also solved.

Very good.

So, all the future IETF meetings should be held in areas far away
from US and, in addition, where English is not the major language.

There many be an exception once in 10 years, of course.

							Masataka Ohta



From owner-ietf-outbound  Wed Feb 16 01:00:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id BAA06783
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 01:00:02 -0500 (EST)
Received: from server.jad.net ([202.134.2.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06736
	for <ietf@ietf.org>; Wed, 16 Feb 2000 00:55:13 -0500 (EST)
Received: from oke.com (cf-isrlab7.comp.nus.edu.sg [137.132.85.181])
	by server.jad.net (8.9.2/8.9.2) with ESMTP id NAA68369;
	Wed, 16 Feb 2000 13:55:30 +0700 (JAVT)
	(envelope-from rms46@oke.com)
Sender: ibrahim@server.jad.net
Message-ID: <38AA3B3C.91FD5121@oke.com>
Date: Wed, 16 Feb 2000 13:53:01 +0800
From: "Rahmat M. Samik-Ibrahim" <rms46@oke.com>
Reply-To: rms46.oke.com@vlsm.org
Organization: VLSM-TJT
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5-22 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: MILIS IETF <ietf@ietf.org>
CC: MILIS gnM-DICK <dick@egroups.com>
Subject: Re: IETF Adelaide and interim meetings for APPS WGs 
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Donald E. Eastlake 3rd:

> The primary concern in the IETF is producing good protocols.

I believe that the IETF model -- for better or for worse -- is a
good thing for developing countries, compared to a membership
organization like ISOC. Having said, it does not mean that 
organizational improvement should be banned.

P.S. the aging board and steering group members reminds me to
     the late stagnated Soviet Union empire... :^).

regards,

-- 
- Rahmat M. Samik-Ibrahim --  VLSM-TJT --  http://rms46.vlsm.org/ -
- DOTCOM... coma coma banana fana coma dotcom... -- the DNS game --



From owner-ietf-outbound@ietf.org  Wed Feb 16 01:02:22 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA06910
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Feb 2000 01:02:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA02371;
	Wed, 16 Feb 2000 01:00:15 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id BAA06783
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 01:00:02 -0500 (EST)
Received: from server.jad.net ([202.134.2.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06736
	for <ietf@ietf.org>; Wed, 16 Feb 2000 00:55:13 -0500 (EST)
Received: from oke.com (cf-isrlab7.comp.nus.edu.sg [137.132.85.181])
	by server.jad.net (8.9.2/8.9.2) with ESMTP id NAA68369;
	Wed, 16 Feb 2000 13:55:30 +0700 (JAVT)
	(envelope-from rms46@oke.com)
Sender: ibrahim@server.jad.net
Message-ID: <38AA3B3C.91FD5121@oke.com>
Date: Wed, 16 Feb 2000 13:53:01 +0800
From: "Rahmat M. Samik-Ibrahim" <rms46@oke.com>
Reply-To: rms46.oke.com@vlsm.org
Organization: VLSM-TJT
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5-22 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: MILIS IETF <ietf@ietf.org>
CC: MILIS gnM-DICK <dick@egroups.com>
Subject: Re: IETF Adelaide and interim meetings for APPS WGs 
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Donald E. Eastlake 3rd:

> The primary concern in the IETF is producing good protocols.

I believe that the IETF model -- for better or for worse -- is a
good thing for developing countries, compared to a membership
organization like ISOC. Having said, it does not mean that 
organizational improvement should be banned.

P.S. the aging board and steering group members reminds me to
     the late stagnated Soviet Union empire... :^).

regards,

-- 
- Rahmat M. Samik-Ibrahim --  VLSM-TJT --  http://rms46.vlsm.org/ -
- DOTCOM... coma coma banana fana coma dotcom... -- the DNS game --



From owner-ietf-outbound  Wed Feb 16 03:12:06 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA20174
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 03:10:02 -0500 (EST)
Received: from online.no (pilt-e.online.no [148.122.208.24])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA20134
	for <ietf@ietf.org>; Wed, 16 Feb 2000 03:06:16 -0500 (EST)
Received: from hph ([195.225.6.229])
	by online.no (8.9.3/8.9.1) with SMTP id JAA16605
	for <ietf@ietf.org>; Wed, 16 Feb 2000 09:06:12 +0100 (MET)
Message-ID: <01f101bf7854$b0d1f900$e506e1c3@asp.infostream.no>
From: "Hans Petter Holen" <hph@infostream.no>
To: <ietf@ietf.org>
References: <200002150045.RAA08041@calcite.rhyolite.com>
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
Date: Wed, 16 Feb 2000 09:05:42 +0100
Organization: Infostream ASP
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 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

----- Original Message -----
From: "Vernon Schryver" <vjs@calcite.rhyolite.com>
> In other words and politically correct pretense asside, the IETF is not
> an international organization.  Despite its posturing, the IETF is a U.S.
> or perhaps North American organization that welcomes non-U.S. participants
> and occasionally spends a lot of its U.S. participants' time and money to
> try to make people outside of North America feel welcome.  If the IETF
> did honestly aspire to be an international organization, it would need
> the characteristics of the ITU (e.g. translators and high prices for
> documents).  Do you think that would be a good thing?

Now if this were to be the case, we should definitely set up an
European Internet Engineering Task Force and so on.

In such a scenario, maybe different parts of the world would even
choose different working languages.

This would definitely be a win towards reducing US centricness.

But would it be a win to the Internet ?

-hph



From owner-ietf-outbound@ietf.org  Wed Feb 16 03:17:51 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA20280
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Feb 2000 03:17:51 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA12964;
	Wed, 16 Feb 2000 03:15:47 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id DAA20174
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 03:10:02 -0500 (EST)
Received: from online.no (pilt-e.online.no [148.122.208.24])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA20134
	for <ietf@ietf.org>; Wed, 16 Feb 2000 03:06:16 -0500 (EST)
Received: from hph ([195.225.6.229])
	by online.no (8.9.3/8.9.1) with SMTP id JAA16605
	for <ietf@ietf.org>; Wed, 16 Feb 2000 09:06:12 +0100 (MET)
Message-ID: <01f101bf7854$b0d1f900$e506e1c3@asp.infostream.no>
From: "Hans Petter Holen" <hph@infostream.no>
To: <ietf@ietf.org>
References: <200002150045.RAA08041@calcite.rhyolite.com>
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
Date: Wed, 16 Feb 2000 09:05:42 +0100
Organization: Infostream ASP
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 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

----- Original Message -----
From: "Vernon Schryver" <vjs@calcite.rhyolite.com>
> In other words and politically correct pretense asside, the IETF is not
> an international organization.  Despite its posturing, the IETF is a U.S.
> or perhaps North American organization that welcomes non-U.S. participants
> and occasionally spends a lot of its U.S. participants' time and money to
> try to make people outside of North America feel welcome.  If the IETF
> did honestly aspire to be an international organization, it would need
> the characteristics of the ITU (e.g. translators and high prices for
> documents).  Do you think that would be a good thing?

Now if this were to be the case, we should definitely set up an
European Internet Engineering Task Force and so on.

In such a scenario, maybe different parts of the world would even
choose different working languages.

This would definitely be a win towards reducing US centricness.

But would it be a win to the Internet ?

-hph



From owner-ietf-outbound  Wed Feb 16 03:31:03 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA20395
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 03:30:02 -0500 (EST)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA20356
	for <ietf@ietf.org>; Wed, 16 Feb 2000 03:26:19 -0500 (EST)
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.0.Beta13/8.10.0.Beta13) with ESMTP id e1G8Q1937032
	for <ietf@ietf.org>; Wed, 16 Feb 2000 03:26:01 -0500
Message-Id: <200002160826.e1G8Q1937032@black-ice.cc.vt.edu>
To: ietf@ietf.org
Subject: Re: IETF Adelaide and interim meetings for APPS WGs 
In-reply-to: Your message of "Wed, 16 Feb 2000 08:38:49 +0900."
             <200002152339.IAA17427@necom830.hpcl.titech.ac.jp> 
From: Valdis.Kletnieks@vt.edu
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <200002152339.IAA17427@necom830.hpcl.titech.ac.jp>
Date: Wed, 16 Feb 2000 03:26:01 -0500
X-Loop: ietf@ietf.org

On Wed, 16 Feb 2000 08:38:49 +0900, Masataka Ohta said:
> So, all the future IETF meetings should be held in areas far away
> from US and, in addition, where English is not the major language.

"My hovercraft is full of eels" -- J. Cleese



From owner-ietf-outbound@ietf.org  Wed Feb 16 03:38:59 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA20554
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Feb 2000 03:38:59 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA13512;
	Wed, 16 Feb 2000 03:36:54 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id DAA20395
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 03:30:02 -0500 (EST)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA20356
	for <ietf@ietf.org>; Wed, 16 Feb 2000 03:26:19 -0500 (EST)
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.0.Beta13/8.10.0.Beta13) with ESMTP id e1G8Q1937032
	for <ietf@ietf.org>; Wed, 16 Feb 2000 03:26:01 -0500
Message-Id: <200002160826.e1G8Q1937032@black-ice.cc.vt.edu>
To: ietf@ietf.org
Subject: Re: IETF Adelaide and interim meetings for APPS WGs 
In-reply-to: Your message of "Wed, 16 Feb 2000 08:38:49 +0900."
             <200002152339.IAA17427@necom830.hpcl.titech.ac.jp> 
From: Valdis.Kletnieks@vt.edu
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <200002152339.IAA17427@necom830.hpcl.titech.ac.jp>
Date: Wed, 16 Feb 2000 03:26:01 -0500
X-Loop: ietf@ietf.org

On Wed, 16 Feb 2000 08:38:49 +0900, Masataka Ohta said:
> So, all the future IETF meetings should be held in areas far away
> from US and, in addition, where English is not the major language.

"My hovercraft is full of eels" -- J. Cleese



From owner-ietf-outbound  Wed Feb 16 06:50:51 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA22785
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 06:50:01 -0500 (EST)
Received: from sj-mailhub-3.cisco.com (sj-mailhub-3.cisco.com [171.68.224.215])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22748
	for <ietf@ietf.org>; Wed, 16 Feb 2000 06:49:39 -0500 (EST)
Received: from rhino (rhino.cisco.com [172.20.9.57])
	by sj-mailhub-3.cisco.com (8.9.1a/8.9.1) with ESMTP id EAA11459;
	Wed, 16 Feb 2000 04:10:16 -0800 (PST)
Received: from p7020-img-nt (sj-dial-1-83.cisco.com [171.68.179.84]) by rhino (SMI-8.6/CISCO.WS.1.1) with SMTP id DAA27333; Wed, 16 Feb 2000 03:53:46 -0800
Message-Id: <4.1.20000216034346.0195ccf0@flipper.cisco.com>
X-Sender: fred@flipper.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Wed, 16 Feb 2000 03:47:29 -0800
To: Ian King <iking@microsoft.com>
From: Fred Baker <fred@cisco.com>
Subject: RE: IETF Adelaide and interim meetings for APPS WGs
Cc: ietf@ietf.org
In-Reply-To: <D5922CA42F8CD31189D800805F19A16C020610FE@RED-MSG-48>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 09:44 PM 2/15/00 -0800, Ian King wrote:
>To those of you outside the US who don't think there are enough meetings
>outside the US: IF YOU SPONSOR THEM, WE WILL COME.  I've seen the open,
>standing invitations to sponsor meetings -- so step up and sponsor.  

for the record, we have quite a few potential sponsors outside the US. We
are considering future meetings in London and Tokyo, and have been offered
sites in Geneva, Naples, Beijing, and other places. What tends to be
interesting to find is the US sponsors, not the non-US ones.

>Bottom line: go if you can and wish to, don't whine if you can't or won't.
>And please quit with the "conspiracy theories" about US-centricity.

Agreed. It is readily argued that there is strong US involvement. Going
from there to some of the places this thread has taken it is quite a leap.



From owner-ietf-outbound@ietf.org  Wed Feb 16 06:54:09 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22862
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Feb 2000 06:54:09 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA17721;
	Wed, 16 Feb 2000 06:52:05 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id GAA22785
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 06:50:01 -0500 (EST)
Received: from sj-mailhub-3.cisco.com (sj-mailhub-3.cisco.com [171.68.224.215])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22748
	for <ietf@ietf.org>; Wed, 16 Feb 2000 06:49:39 -0500 (EST)
Received: from rhino (rhino.cisco.com [172.20.9.57])
	by sj-mailhub-3.cisco.com (8.9.1a/8.9.1) with ESMTP id EAA11459;
	Wed, 16 Feb 2000 04:10:16 -0800 (PST)
Received: from p7020-img-nt (sj-dial-1-83.cisco.com [171.68.179.84]) by rhino (SMI-8.6/CISCO.WS.1.1) with SMTP id DAA27333; Wed, 16 Feb 2000 03:53:46 -0800
Message-Id: <4.1.20000216034346.0195ccf0@flipper.cisco.com>
X-Sender: fred@flipper.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Wed, 16 Feb 2000 03:47:29 -0800
To: Ian King <iking@microsoft.com>
From: Fred Baker <fred@cisco.com>
Subject: RE: IETF Adelaide and interim meetings for APPS WGs
Cc: ietf@ietf.org
In-Reply-To: <D5922CA42F8CD31189D800805F19A16C020610FE@RED-MSG-48>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 09:44 PM 2/15/00 -0800, Ian King wrote:
>To those of you outside the US who don't think there are enough meetings
>outside the US: IF YOU SPONSOR THEM, WE WILL COME.  I've seen the open,
>standing invitations to sponsor meetings -- so step up and sponsor.  

for the record, we have quite a few potential sponsors outside the US. We
are considering future meetings in London and Tokyo, and have been offered
sites in Geneva, Naples, Beijing, and other places. What tends to be
interesting to find is the US sponsors, not the non-US ones.

>Bottom line: go if you can and wish to, don't whine if you can't or won't.
>And please quit with the "conspiracy theories" about US-centricity.

Agreed. It is readily argued that there is strong US involvement. Going
from there to some of the places this thread has taken it is quite a leap.



From owner-ietf-outbound  Wed Feb 16 07:00:16 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA22999
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 07:00:02 -0500 (EST)
Received: from sj-mailhub-3.cisco.com (sj-mailhub-3.cisco.com [171.68.224.215])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22749
	for <ietf@ietf.org>; Wed, 16 Feb 2000 06:49:39 -0500 (EST)
Received: from rhino (rhino.cisco.com [172.20.9.57])
	by sj-mailhub-3.cisco.com (8.9.1a/8.9.1) with ESMTP id EAA11451;
	Wed, 16 Feb 2000 04:10:14 -0800 (PST)
Received: from p7020-img-nt (sj-dial-1-83.cisco.com [171.68.179.84]) by rhino (SMI-8.6/CISCO.WS.1.1) with SMTP id DAA27331; Wed, 16 Feb 2000 03:53:44 -0800
Message-Id: <4.1.20000216032758.0195f690@flipper.cisco.com>
X-Sender: fred@flipper.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Wed, 16 Feb 2000 03:40:21 -0800
To: Mart Nurmet <mart.nurmet@inet.com>
From: Fred Baker <fred@cisco.com>
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
Cc: ietf@ietf.org
In-Reply-To: <38A998FC.72501901@inet.com>
References: <200002142337.SAA00271@astro.cs.utk.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 12:20 PM 2/15/00 -0600, Mart Nurmet wrote:
>Keith:
>
>How do I go about geting the schedule for the meetings for the rest of the
>year?

If you go to the IETF web site, click on "Meetings", and click on "list of
future meetings", you will find a pointer the file
http://www.ietf.org/meetings/0mtg-sites.txt



From owner-ietf-outbound@ietf.org  Wed Feb 16 07:03:57 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23186
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Feb 2000 07:03:57 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA17975;
	Wed, 16 Feb 2000 07:01:37 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id HAA22999
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 07:00:02 -0500 (EST)
Received: from sj-mailhub-3.cisco.com (sj-mailhub-3.cisco.com [171.68.224.215])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22749
	for <ietf@ietf.org>; Wed, 16 Feb 2000 06:49:39 -0500 (EST)
Received: from rhino (rhino.cisco.com [172.20.9.57])
	by sj-mailhub-3.cisco.com (8.9.1a/8.9.1) with ESMTP id EAA11451;
	Wed, 16 Feb 2000 04:10:14 -0800 (PST)
Received: from p7020-img-nt (sj-dial-1-83.cisco.com [171.68.179.84]) by rhino (SMI-8.6/CISCO.WS.1.1) with SMTP id DAA27331; Wed, 16 Feb 2000 03:53:44 -0800
Message-Id: <4.1.20000216032758.0195f690@flipper.cisco.com>
X-Sender: fred@flipper.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Wed, 16 Feb 2000 03:40:21 -0800
To: Mart Nurmet <mart.nurmet@inet.com>
From: Fred Baker <fred@cisco.com>
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
Cc: ietf@ietf.org
In-Reply-To: <38A998FC.72501901@inet.com>
References: <200002142337.SAA00271@astro.cs.utk.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 12:20 PM 2/15/00 -0600, Mart Nurmet wrote:
>Keith:
>
>How do I go about geting the schedule for the meetings for the rest of the
>year?

If you go to the IETF web site, click on "Meetings", and click on "list of
future meetings", you will find a pointer the file
http://www.ietf.org/meetings/0mtg-sites.txt



From owner-ietf-outbound  Wed Feb 16 07:20:50 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA23733
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 07:20:02 -0500 (EST)
Received: from msw.mimesweeper.com (msw.mimesweeper.com [194.168.90.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23643
	for <ietf@ietf.org>; Wed, 16 Feb 2000 07:15:41 -0500 (EST)
Received: from bell.mimesweeper.com (unverified) by msw.mimesweeper.com
 (Content Technologies SMTPRS 4.1.5) with ESMTP id <Tc2a85a12704a66c0626a@msw.mimesweeper.com>;
 Wed, 16 Feb 2000 12:17:44 +0000
Received: from GK-VAIO (gk-vaio.mimesweeper.com [194.168.90.137]) by bell.mimesweeper.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0)
	id DKP3H992; Wed, 16 Feb 2000 12:16:58 -0000
Message-Id: <4.2.2.20000215214321.00a3f710@pop.dial.pipex.com>
X-Sender: maiw03@pop.dial.pipex.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Tue, 15 Feb 2000 21:45:24 +0000
To: jaltman@columbia.edu
From: Graham Klyne <GK@dial.pipex.com>
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
Cc: ietf@ietf.org
In-Reply-To: <CMM.0.90.4.950639405.jaltman@watsun.cc.columbia.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 01:30 PM 2/15/00 -0500, Jeffrey Altman wrote:
>The problem I have with the Adelaide meeting is very simple.  With so
>few working groups holding sessions, I can't justify making the trip.

I'd like to offer a personal observation.  Yes, the working group sessions 
are useful but, for me, the most valuable stuff happens between the sessions.

#g

------------
Graham Klyne
(GK@ACM.ORG)



From owner-ietf-outbound@ietf.org  Wed Feb 16 07:24:36 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23897
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Feb 2000 07:24:35 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA18395;
	Wed, 16 Feb 2000 07:22:33 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id HAA23733
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 07:20:02 -0500 (EST)
Received: from msw.mimesweeper.com (msw.mimesweeper.com [194.168.90.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23643
	for <ietf@ietf.org>; Wed, 16 Feb 2000 07:15:41 -0500 (EST)
Received: from bell.mimesweeper.com (unverified) by msw.mimesweeper.com
 (Content Technologies SMTPRS 4.1.5) with ESMTP id <Tc2a85a12704a66c0626a@msw.mimesweeper.com>;
 Wed, 16 Feb 2000 12:17:44 +0000
Received: from GK-VAIO (gk-vaio.mimesweeper.com [194.168.90.137]) by bell.mimesweeper.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0)
	id DKP3H992; Wed, 16 Feb 2000 12:16:58 -0000
Message-Id: <4.2.2.20000215214321.00a3f710@pop.dial.pipex.com>
X-Sender: maiw03@pop.dial.pipex.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Tue, 15 Feb 2000 21:45:24 +0000
To: jaltman@columbia.edu
From: Graham Klyne <GK@dial.pipex.com>
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
Cc: ietf@ietf.org
In-Reply-To: <CMM.0.90.4.950639405.jaltman@watsun.cc.columbia.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 01:30 PM 2/15/00 -0500, Jeffrey Altman wrote:
>The problem I have with the Adelaide meeting is very simple.  With so
>few working groups holding sessions, I can't justify making the trip.

I'd like to offer a personal observation.  Yes, the working group sessions 
are useful but, for me, the most valuable stuff happens between the sessions.

#g

------------
Graham Klyne
(GK@ACM.ORG)



From owner-ietf-outbound  Wed Feb 16 08:21:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA26149
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 08:20:03 -0500 (EST)
Received: from mailsrvnt01.ssdi.sharp.co.in ([203.197.160.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25778
	for <ietf@ietf.org>; Wed, 16 Feb 2000 08:08:23 -0500 (EST)
Received: by mailsrvnt01.ssdi.sharp.co.in with Internet Mail Service (5.5.2650.21)
	id <106XWS0J>; Wed, 16 Feb 2000 18:41:53 +0530
Message-ID: <9753A88725D7D3119BE0009027CC6CA202B904@mailsrvnt01.ssdi.sharp.co.in>
From: Sriram Shanmugam <SSriram@ssdi.sharp.co.in>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Need HELP for SNMP 
Date: Wed, 16 Feb 2000 18:41:53 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

Hai Everybody,

	I am working on SNMP , i would like to know how to start the coding
for SNMP , is there any web site from where i can get an introductory
material (Code) , or any books which deal with coding ? . I have read many
books but most or in fact all of them deal with the theoretical part alone.

	I would like to a develop the code do discover all the SNMP Agents
present on the Network , how do i go abt it?.

Eagerly waiting for the reply

S.Sriram

	



From owner-ietf-outbound@ietf.org  Wed Feb 16 08:30:28 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26586
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Feb 2000 08:30:28 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA19967;
	Wed, 16 Feb 2000 08:28:22 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id IAA26149
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 08:20:03 -0500 (EST)
Received: from mailsrvnt01.ssdi.sharp.co.in ([203.197.160.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25778
	for <ietf@ietf.org>; Wed, 16 Feb 2000 08:08:23 -0500 (EST)
Received: by mailsrvnt01.ssdi.sharp.co.in with Internet Mail Service (5.5.2650.21)
	id <106XWS0J>; Wed, 16 Feb 2000 18:41:53 +0530
Message-ID: <9753A88725D7D3119BE0009027CC6CA202B904@mailsrvnt01.ssdi.sharp.co.in>
From: Sriram Shanmugam <SSriram@ssdi.sharp.co.in>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Need HELP for SNMP 
Date: Wed, 16 Feb 2000 18:41:53 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

Hai Everybody,

	I am working on SNMP , i would like to know how to start the coding
for SNMP , is there any web site from where i can get an introductory
material (Code) , or any books which deal with coding ? . I have read many
books but most or in fact all of them deal with the theoretical part alone.

	I would like to a develop the code do discover all the SNMP Agents
present on the Network , how do i go abt it?.

Eagerly waiting for the reply

S.Sriram

	



From owner-ietf-outbound  Wed Feb 16 09:01:39 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA27686
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 09:00:06 -0500 (EST)
Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA27482
	for <ietf@ietf.org>; Wed, 16 Feb 2000 08:53:26 -0500 (EST)
Received: from sonic.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.25633-0@bells.cs.ucl.ac.uk>; Wed, 16 Feb 2000 13:53:17 +0000
to: ietf@ietf.org
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
In-reply-to: Your message of "Wed, 16 Feb 2000 03:47:29 PST." <4.1.20000216034346.0195ccf0@flipper.cisco.com>
Date: Wed, 16 Feb 2000 13:53:11 +0000
Message-ID: <15681.950709191@cs.ucl.ac.uk>
From: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
X-Loop: ietf@ietf.org



to people that think that the internet is mostly US centric, and will
go on being so, and that this is relevant to the IETF anyhow -
wrong, wrong, and also wrong!

um the Internet is now mostly commercial - the Eu and Asia each have MORE
money than the US, and also have growth economies. if you work for a
vendor (s/w, h/w, services) and can't find a reason to visit, then yo
uare missing an opportunity to "enhance shareholder value" - as a
shareholder, i would be shocked and dismayed....and think hard about
other vendors...

as an academic/researcher, too, generally, i can easly find good reasons to 
visit people with other viewpoints, and requirements and inventions...
 

note that microsoft and cisco (examples - there are lots more)
 both set up strong european presences
recently for these reasons. They also have strong asia/pacific
presence - 

using current IETF national representation as a marker for where to
hold meetings is going to lag, rather than lead the right thing to do
imho

note also, that provided the IETF doesnt start mimicing ITU in
choosing
meeting location, a lot of places outside the US offset travel costs
by cheaper accomodation costs.....significantly in some cases
(i admit london england is not a good example for this, though it is
pretty cheap to get to from just about anywhere on average:-)


 cheers

   jon



From owner-ietf-outbound@ietf.org  Wed Feb 16 09:12:14 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28365
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Feb 2000 09:12:14 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA21101;
	Wed, 16 Feb 2000 09:10:09 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id JAA27686
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 09:00:06 -0500 (EST)
Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA27482
	for <ietf@ietf.org>; Wed, 16 Feb 2000 08:53:26 -0500 (EST)
Received: from sonic.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.25633-0@bells.cs.ucl.ac.uk>; Wed, 16 Feb 2000 13:53:17 +0000
to: ietf@ietf.org
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
In-reply-to: Your message of "Wed, 16 Feb 2000 03:47:29 PST." <4.1.20000216034346.0195ccf0@flipper.cisco.com>
Date: Wed, 16 Feb 2000 13:53:11 +0000
Message-ID: <15681.950709191@cs.ucl.ac.uk>
From: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
X-Loop: ietf@ietf.org



to people that think that the internet is mostly US centric, and will
go on being so, and that this is relevant to the IETF anyhow -
wrong, wrong, and also wrong!

um the Internet is now mostly commercial - the Eu and Asia each have MORE
money than the US, and also have growth economies. if you work for a
vendor (s/w, h/w, services) and can't find a reason to visit, then yo
uare missing an opportunity to "enhance shareholder value" - as a
shareholder, i would be shocked and dismayed....and think hard about
other vendors...

as an academic/researcher, too, generally, i can easly find good reasons to 
visit people with other viewpoints, and requirements and inventions...
 

note that microsoft and cisco (examples - there are lots more)
 both set up strong european presences
recently for these reasons. They also have strong asia/pacific
presence - 

using current IETF national representation as a marker for where to
hold meetings is going to lag, rather than lead the right thing to do
imho

note also, that provided the IETF doesnt start mimicing ITU in
choosing
meeting location, a lot of places outside the US offset travel costs
by cheaper accomodation costs.....significantly in some cases
(i admit london england is not a good example for this, though it is
pretty cheap to get to from just about anywhere on average:-)


 cheers

   jon



From owner-ietf-outbound  Wed Feb 16 09:21:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA28758
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 09:20:02 -0500 (EST)
Received: from localhost.localdomain (3.144.8.207.in-addr.arpa [207.8.144.3] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28474
	for <ietf@ietf.org>; Wed, 16 Feb 2000 09:14:54 -0500 (EST)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id JAA19110
	for <ietf@ietf.org>; Wed, 16 Feb 2000 09:14:24 -0500
Sender: francis@localhost.localdomain
Message-ID: <38AAB0BF.F638F2E5@ecal.com>
Date: Wed, 16 Feb 2000 09:14:23 -0500
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.2.12-20 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
References: <CMM.0.90.4.950639405.jaltman@watsun.cc.columbia.edu> <200002152339.IAA17427@necom830.hpcl.titech.ac.jp> <20000215201452.F20408@off.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Austin Schutz wrote:

>         It wouuld be possible to have all the mailing lists redistributed
> using some babelfish-like mechanism for translation, though obviously that
> wouldn't cover all languages and wouldn't do any well. Maybe better than
> nothing.

Probably worse than nothing, unless there are much better translators than
babelfish out there.  WG discussions get down to really niggly points; a
translator that doesn't work *perfectly* is likely to make things worse.  At
least today, if we're talking through a language barrier, there's a human
brain doing the translation, able to recognize problems and rephrase as
needed.

--
/==============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.|
|Chief Scientist |=============================================|
|eCal Corp.      |Never mind the GUIs--Unix won't be for the   |
|francis@ecal.com|masses until we fix backspace & delete.      |
\==============================================================/





From owner-ietf-outbound@ietf.org  Wed Feb 16 09:31:37 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29396
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Feb 2000 09:31:37 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA21595;
	Wed, 16 Feb 2000 09:29:33 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id JAA28758
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 09:20:02 -0500 (EST)
Received: from localhost.localdomain (3.144.8.207.in-addr.arpa [207.8.144.3] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28474
	for <ietf@ietf.org>; Wed, 16 Feb 2000 09:14:54 -0500 (EST)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id JAA19110
	for <ietf@ietf.org>; Wed, 16 Feb 2000 09:14:24 -0500
Sender: francis@localhost.localdomain
Message-ID: <38AAB0BF.F638F2E5@ecal.com>
Date: Wed, 16 Feb 2000 09:14:23 -0500
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.2.12-20 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
References: <CMM.0.90.4.950639405.jaltman@watsun.cc.columbia.edu> <200002152339.IAA17427@necom830.hpcl.titech.ac.jp> <20000215201452.F20408@off.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Austin Schutz wrote:

>         It wouuld be possible to have all the mailing lists redistributed
> using some babelfish-like mechanism for translation, though obviously that
> wouldn't cover all languages and wouldn't do any well. Maybe better than
> nothing.

Probably worse than nothing, unless there are much better translators than
babelfish out there.  WG discussions get down to really niggly points; a
translator that doesn't work *perfectly* is likely to make things worse.  At
least today, if we're talking through a language barrier, there's a human
brain doing the translation, able to recognize problems and rephrase as
needed.

--
/==============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.|
|Chief Scientist |=============================================|
|eCal Corp.      |Never mind the GUIs--Unix won't be for the   |
|francis@ecal.com|masses until we fix backspace & delete.      |
\==============================================================/





From owner-ietf-outbound  Wed Feb 16 10:12:02 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA00985
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 10:10:02 -0500 (EST)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00900
	for <ietf@ietf.org>; Wed, 16 Feb 2000 10:08:25 -0500 (EST)
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.0.Beta13/8.10.0.Beta13) with ESMTP id e1GF7f930646;
	Wed, 16 Feb 2000 10:07:45 -0500
Message-Id: <200002161507.e1GF7f930646@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Sriram Shanmugam <SSriram@ssdi.sharp.co.in>
cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: Need HELP for SNMP 
In-reply-to: Your message of "Wed, 16 Feb 2000 18:41:53 +0530."
             <9753A88725D7D3119BE0009027CC6CA202B904@mailsrvnt01.ssdi.sharp.co.in> 
From: Valdis.Kletnieks@vt.edu
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <9753A88725D7D3119BE0009027CC6CA202B904@mailsrvnt01.ssdi.sharp.co.in>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 16 Feb 2000 10:07:41 -0500
X-Loop: ietf@ietf.org

On Wed, 16 Feb 2000 18:41:53 +0530, Sriram Shanmugam <SSriram@ssdi.sharp.co.in>  said:
> 	I would like to a develop the code do discover all the SNMP Agents
> present on the Network , how do i go abt it?.

Step 1: Send a ping to the subnet's broadcast address.

Step 2: For each machine that answers, contact its port 161, and see if
you get 'port unreachable'.

Step 3: For each machine that did ping, but doesn't say 'port unreachable',
try talking SNMP to the port.

Step 4: Make sure you've talked to the network/security administrator BEFORE
you do this, so you are not lynched by the admins of machines that have
tripwired port 161 to detect portscans....

In other words, be *VERY* sure that you have management backing before trying
it.  Failing to ask first can be quite a Career Limiting Move....

-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound@ietf.org  Wed Feb 16 10:18:34 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01510
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Feb 2000 10:18:33 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA23048;
	Wed, 16 Feb 2000 10:16:20 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id KAA00985
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 10:10:02 -0500 (EST)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00900
	for <ietf@ietf.org>; Wed, 16 Feb 2000 10:08:25 -0500 (EST)
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.0.Beta13/8.10.0.Beta13) with ESMTP id e1GF7f930646;
	Wed, 16 Feb 2000 10:07:45 -0500
Message-Id: <200002161507.e1GF7f930646@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Sriram Shanmugam <SSriram@ssdi.sharp.co.in>
cc: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: Re: Need HELP for SNMP 
In-reply-to: Your message of "Wed, 16 Feb 2000 18:41:53 +0530."
             <9753A88725D7D3119BE0009027CC6CA202B904@mailsrvnt01.ssdi.sharp.co.in> 
From: Valdis.Kletnieks@vt.edu
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <9753A88725D7D3119BE0009027CC6CA202B904@mailsrvnt01.ssdi.sharp.co.in>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 16 Feb 2000 10:07:41 -0500
X-Loop: ietf@ietf.org

On Wed, 16 Feb 2000 18:41:53 +0530, Sriram Shanmugam <SSriram@ssdi.sharp.co.in>  said:
> 	I would like to a develop the code do discover all the SNMP Agents
> present on the Network , how do i go abt it?.

Step 1: Send a ping to the subnet's broadcast address.

Step 2: For each machine that answers, contact its port 161, and see if
you get 'port unreachable'.

Step 3: For each machine that did ping, but doesn't say 'port unreachable',
try talking SNMP to the port.

Step 4: Make sure you've talked to the network/security administrator BEFORE
you do this, so you are not lynched by the admins of machines that have
tripwired port 161 to detect portscans....

In other words, be *VERY* sure that you have management backing before trying
it.  Failing to ask first can be quite a Career Limiting Move....

-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Wed Feb 16 10:41:09 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA02556
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 10:40:02 -0500 (EST)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02326
	for <ietf@ietf.org>; Wed, 16 Feb 2000 10:34:41 -0500 (EST)
Received: from sp3at21.hursley.ibm.com (sp3at21.hursley.ibm.com [9.20.45.21]) by mail-gw.hursley.ibm.com (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id PAA89152 for <ietf@ietf.org>; Wed, 16 Feb 2000 15:34:04 GMT
Received: from hursley.ibm.com (ss3.bld.socks.ibm.com [9.14.4.68]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id PAA17432 for <ietf@ietf.org>; Wed, 16 Feb 2000 15:34:03 GMT
Message-ID: <38AAB135.5C5FCCF8@hursley.ibm.com>
Date: Wed, 16 Feb 2000 08:16:21 -0600
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en,fr
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
References: <4.2.2.20000215214321.00a3f710@pop.dial.pipex.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

It is not the case that few WGs are holding meetings. The published agenda
just isn't complete yet; it never is at this stage.

  Brian

Graham Klyne wrote:
> 
> At 01:30 PM 2/15/00 -0500, Jeffrey Altman wrote:
> >The problem I have with the Adelaide meeting is very simple.  With so
> >few working groups holding sessions, I can't justify making the trip.
> 
> I'd like to offer a personal observation.  Yes, the working group sessions
> are useful but, for me, the most valuable stuff happens between the sessions.
> 
> #g
> 
> ------------
> Graham Klyne
> (GK@ACM.ORG)



From owner-ietf-outbound@ietf.org  Wed Feb 16 10:46:37 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02956
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Feb 2000 10:46:37 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA23873;
	Wed, 16 Feb 2000 10:44:30 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id KAA02556
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 10:40:02 -0500 (EST)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02326
	for <ietf@ietf.org>; Wed, 16 Feb 2000 10:34:41 -0500 (EST)
Received: from sp3at21.hursley.ibm.com (sp3at21.hursley.ibm.com [9.20.45.21]) by mail-gw.hursley.ibm.com (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id PAA89152 for <ietf@ietf.org>; Wed, 16 Feb 2000 15:34:04 GMT
Received: from hursley.ibm.com (ss3.bld.socks.ibm.com [9.14.4.68]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id PAA17432 for <ietf@ietf.org>; Wed, 16 Feb 2000 15:34:03 GMT
Message-ID: <38AAB135.5C5FCCF8@hursley.ibm.com>
Date: Wed, 16 Feb 2000 08:16:21 -0600
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en,fr
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
References: <4.2.2.20000215214321.00a3f710@pop.dial.pipex.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

It is not the case that few WGs are holding meetings. The published agenda
just isn't complete yet; it never is at this stage.

  Brian

Graham Klyne wrote:
> 
> At 01:30 PM 2/15/00 -0500, Jeffrey Altman wrote:
> >The problem I have with the Adelaide meeting is very simple.  With so
> >few working groups holding sessions, I can't justify making the trip.
> 
> I'd like to offer a personal observation.  Yes, the working group sessions
> are useful but, for me, the most valuable stuff happens between the sessions.
> 
> #g
> 
> ------------
> Graham Klyne
> (GK@ACM.ORG)



From owner-ietf-outbound  Wed Feb 16 10:50:47 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA03123
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 10:50:02 -0500 (EST)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03082
	for <ietf@ietf.org>; Wed, 16 Feb 2000 10:49:39 -0500 (EST)
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.0.Beta13/8.10.0.Beta13) with ESMTP id e1GFnY926128
	for <ietf@ietf.org>; Wed, 16 Feb 2000 10:49:35 -0500
Message-Id: <200002161549.e1GFnY926128@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: ietf@ietf.org
Subject: Question re: an Internet-Draft and testing/deployment
From: Valdis.Kletnieks@vt.edu
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face-Viewer: See ftp://cs.indiana.edu/pub/faces/index.html to decode picture
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 16 Feb 2000 10:49:32 -0500
X-Loop: ietf@ietf.org

Noticed this one this morning:

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


	Title		: Compatible Internationalized Domain Names Using 
                          Compression
	Author(s)	: P. Hoffman
	Filename	: draft-hoffman-idn-cidnuc-02.txt
	Pages		: 12
	Date		: 15-Feb-00
	
This protocol describes a transformation method for representing non-
ASCII characters in domain names in a fashion that is completely
compatible with the current DNS. It meets the many requirements for
internationalization of domain names.

Note: this protocol is quite experimental and should not be deployed in
the Internet until it reaches standards track in the IETF.
--- end excerpt

Regarding the Note: - is there any coherent plan regarding testing/deployement
in regards to moving this from Experimental to Standards Track?

-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound@ietf.org  Wed Feb 16 10:55:50 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03442
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Feb 2000 10:55:49 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA24165;
	Wed, 16 Feb 2000 10:53:46 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id KAA03123
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 10:50:02 -0500 (EST)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03082
	for <ietf@ietf.org>; Wed, 16 Feb 2000 10:49:39 -0500 (EST)
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.0.Beta13/8.10.0.Beta13) with ESMTP id e1GFnY926128
	for <ietf@ietf.org>; Wed, 16 Feb 2000 10:49:35 -0500
Message-Id: <200002161549.e1GFnY926128@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: ietf@ietf.org
Subject: Question re: an Internet-Draft and testing/deployment
From: Valdis.Kletnieks@vt.edu
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face-Viewer: See ftp://cs.indiana.edu/pub/faces/index.html to decode picture
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 16 Feb 2000 10:49:32 -0500
X-Loop: ietf@ietf.org

Noticed this one this morning:

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


	Title		: Compatible Internationalized Domain Names Using 
                          Compression
	Author(s)	: P. Hoffman
	Filename	: draft-hoffman-idn-cidnuc-02.txt
	Pages		: 12
	Date		: 15-Feb-00
	
This protocol describes a transformation method for representing non-
ASCII characters in domain names in a fashion that is completely
compatible with the current DNS. It meets the many requirements for
internationalization of domain names.

Note: this protocol is quite experimental and should not be deployed in
the Internet until it reaches standards track in the IETF.
--- end excerpt

Regarding the Note: - is there any coherent plan regarding testing/deployement
in regards to moving this from Experimental to Standards Track?

-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Wed Feb 16 11:00:58 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA03622
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 11:00:02 -0500 (EST)
Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03397
	for <ietf@ietf.org>; Wed, 16 Feb 2000 10:55:17 -0500 (EST)
Received: from amontillado.research.att.com (amontillado.research.att.com [135.207.24.32])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id D1DD04CE14; Wed, 16 Feb 2000 10:55:13 -0500 (EST)
Received: from SIGABA.research.att.com (sigaba.research.att.com [135.207.23.169])
	by amontillado.research.att.com (8.8.7/8.8.7) with ESMTP id KAA28131;
	Wed, 16 Feb 2000 10:55:57 -0500 (EST)
Received: by SIGABA.research.att.com (Postfix, from userid 54047)
	id 4BF1D41F16; Wed, 16 Feb 2000 10:55:13 -0500 (EST)
Received: from roc (localhost [127.0.0.1])
	by SIGABA.research.att.com (Postfix) with ESMTP
	id 30BBC400B5; Wed, 16 Feb 2000 10:55:08 -0500 (EST)
X-Mailer: exmh version 2.1.1 10/15/1999
From: "Steven M. Bellovin" <smb@research.att.com>
To: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
Cc: ietf@ietf.org
Subject: Re: IETF Adelaide and interim meetings for APPS WGs 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 16 Feb 2000 10:55:08 -0500
Sender: smb@research.att.com
Message-Id: <20000216155513.4BF1D41F16@SIGABA.research.att.com>
X-Loop: ietf@ietf.org

In message <15681.950709191@cs.ucl.ac.uk>, Jon Crowcroft writes:

> note also, that provided the IETF doesnt start mimicing ITU in
> choosing
> meeting location, a lot of places outside the US offset travel costs
> by cheaper accomodation costs.....significantly in some cases
> (i admit london england is not a good example for this, though it is
> pretty cheap to get to from just about anywhere on average:-)

And you may find that quirks in airfares can offset the distance factor.  
Given airline load factors, I don't seem to be able to qualify for discounts 
on my trips to San Francisco from New Jersey -- which means that my tickets to 
Adelaide are only very slightly more expensive.

		--Steve Bellovin




From owner-ietf-outbound@ietf.org  Wed Feb 16 11:05:58 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03941
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Feb 2000 11:05:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA24551;
	Wed, 16 Feb 2000 11:03:53 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id LAA03622
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 11:00:02 -0500 (EST)
Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03397
	for <ietf@ietf.org>; Wed, 16 Feb 2000 10:55:17 -0500 (EST)
Received: from amontillado.research.att.com (amontillado.research.att.com [135.207.24.32])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id D1DD04CE14; Wed, 16 Feb 2000 10:55:13 -0500 (EST)
Received: from SIGABA.research.att.com (sigaba.research.att.com [135.207.23.169])
	by amontillado.research.att.com (8.8.7/8.8.7) with ESMTP id KAA28131;
	Wed, 16 Feb 2000 10:55:57 -0500 (EST)
Received: by SIGABA.research.att.com (Postfix, from userid 54047)
	id 4BF1D41F16; Wed, 16 Feb 2000 10:55:13 -0500 (EST)
Received: from roc (localhost [127.0.0.1])
	by SIGABA.research.att.com (Postfix) with ESMTP
	id 30BBC400B5; Wed, 16 Feb 2000 10:55:08 -0500 (EST)
X-Mailer: exmh version 2.1.1 10/15/1999
From: "Steven M. Bellovin" <smb@research.att.com>
To: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
Cc: ietf@ietf.org
Subject: Re: IETF Adelaide and interim meetings for APPS WGs 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 16 Feb 2000 10:55:08 -0500
Sender: smb@research.att.com
Message-Id: <20000216155513.4BF1D41F16@SIGABA.research.att.com>
X-Loop: ietf@ietf.org

In message <15681.950709191@cs.ucl.ac.uk>, Jon Crowcroft writes:

> note also, that provided the IETF doesnt start mimicing ITU in
> choosing
> meeting location, a lot of places outside the US offset travel costs
> by cheaper accomodation costs.....significantly in some cases
> (i admit london england is not a good example for this, though it is
> pretty cheap to get to from just about anywhere on average:-)

And you may find that quirks in airfares can offset the distance factor.  
Given airline load factors, I don't seem to be able to qualify for discounts 
on my trips to San Francisco from New Jersey -- which means that my tickets to 
Adelaide are only very slightly more expensive.

		--Steve Bellovin




From owner-ietf-outbound  Wed Feb 16 11:10:43 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA04171
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 11:10:02 -0500 (EST)
Received: from po1.bbn.com (PO1.BBN.COM [192.1.50.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04046
	for <ietf@ietf.org>; Wed, 16 Feb 2000 11:07:03 -0500 (EST)
Received: from [171.78.30.107] (comsec.bbn.com [171.78.30.107])
	by po1.bbn.com (8.9.1/8.9.1) with ESMTP id LAA00306;
	Wed, 16 Feb 2000 11:06:54 -0500 (EST)
Mime-Version: 1.0
X-Sender: kent@po1.bbn.com
Message-Id: <v04220802b4d078236d2c@[171.78.30.107]>
In-Reply-To: <016401bf7763$4b82e380$0300000a@cisco.com>
References: <016401bf7763$4b82e380$0300000a@cisco.com>
Date: Wed, 16 Feb 2000 11:03:25 -0500
To: "Eliot Lear" <lear@cisco.com>
From: Stephen Kent <kent@bbn.com>
Subject: RE: Internet SYN Flooding, spoofing attacks
Cc: <ietf@ietf.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

Eliot,

Some of the DoS attacks we saw last week were good, old-fashioned SYN 
floods.  Hosts do have a responsibility here, more than ISPs, since 
it is quite feasible to tie up a host's pool of TCBs with a small 
number of packets, even if the attack tool does not use spoofed 
sourced addresses (or if the spoofed addresses are from a legitimate 
pool allocated to a subscriber site).

The point I have tried to make, unsuccessfully, is not that 
performing ingress filtering is bad, and thus should not be 
performed.  Rather, I am pointing out that it is a bad idea to rely 
on such filtering as a primary means of defense. There are several 
reasons for saying this:
	- not all ISPs will find it feasible to provide such filtering
	- not all ISPs are trusted to do the filtering (in the global Internet)
	- a number of DDoS attacks can be launched without using 
spoofed addresses outside of those "appropriate" to the subscriber 
site
	- some applications may legitimately make use of non-local 
addresses, as others have suggested

I have seen a long history of suggested solutions to security 
problems which are only partially effective against current forms of 
attacks, vs. providing protection against a larger class of attacks. 
I'm trying to suggest that we not follow this pattern.

Finally, there is a diminishing difference between what a script 
kiddie can do, vs. a clever attacker, because the clever attackers 
are freely distributing higher quality attack tools.  "Empowerment" 
is a hallmark of modern Internet attacks :-).

Steve



From owner-ietf-outbound@ietf.org  Wed Feb 16 11:16:53 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04423
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Feb 2000 11:16:53 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA24864;
	Wed, 16 Feb 2000 11:14:20 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id LAA04171
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 11:10:02 -0500 (EST)
Received: from po1.bbn.com (PO1.BBN.COM [192.1.50.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04046
	for <ietf@ietf.org>; Wed, 16 Feb 2000 11:07:03 -0500 (EST)
Received: from [171.78.30.107] (comsec.bbn.com [171.78.30.107])
	by po1.bbn.com (8.9.1/8.9.1) with ESMTP id LAA00306;
	Wed, 16 Feb 2000 11:06:54 -0500 (EST)
Mime-Version: 1.0
X-Sender: kent@po1.bbn.com
Message-Id: <v04220802b4d078236d2c@[171.78.30.107]>
In-Reply-To: <016401bf7763$4b82e380$0300000a@cisco.com>
References: <016401bf7763$4b82e380$0300000a@cisco.com>
Date: Wed, 16 Feb 2000 11:03:25 -0500
To: "Eliot Lear" <lear@cisco.com>
From: Stephen Kent <kent@bbn.com>
Subject: RE: Internet SYN Flooding, spoofing attacks
Cc: <ietf@ietf.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

Eliot,

Some of the DoS attacks we saw last week were good, old-fashioned SYN 
floods.  Hosts do have a responsibility here, more than ISPs, since 
it is quite feasible to tie up a host's pool of TCBs with a small 
number of packets, even if the attack tool does not use spoofed 
sourced addresses (or if the spoofed addresses are from a legitimate 
pool allocated to a subscriber site).

The point I have tried to make, unsuccessfully, is not that 
performing ingress filtering is bad, and thus should not be 
performed.  Rather, I am pointing out that it is a bad idea to rely 
on such filtering as a primary means of defense. There are several 
reasons for saying this:
	- not all ISPs will find it feasible to provide such filtering
	- not all ISPs are trusted to do the filtering (in the global Internet)
	- a number of DDoS attacks can be launched without using 
spoofed addresses outside of those "appropriate" to the subscriber 
site
	- some applications may legitimately make use of non-local 
addresses, as others have suggested

I have seen a long history of suggested solutions to security 
problems which are only partially effective against current forms of 
attacks, vs. providing protection against a larger class of attacks. 
I'm trying to suggest that we not follow this pattern.

Finally, there is a diminishing difference between what a script 
kiddie can do, vs. a clever attacker, because the clever attackers 
are freely distributing higher quality attack tools.  "Empowerment" 
is a hallmark of modern Internet attacks :-).

Steve



From owner-ietf-outbound  Wed Feb 16 11:31:32 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA04921
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 11:30:02 -0500 (EST)
Received: from velma.seeglasgow.com (velma.seeglasgow.com [212.250.141.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04690
	for <ietf@ietf.org>; Wed, 16 Feb 2000 11:23:30 -0500 (EST)
Received: by velma.seeglasgow.com with Internet Mail Service (5.5.2650.21)
	id <DY5CK4T8>; Wed, 16 Feb 2000 16:23:12 -0000
Message-ID: <91FBC84CBEF8D211AE2E0008C79F8A9517C4D5@velma.seeglasgow.com>
From: Stewart Nolan <stewart.nolan@seeglasgow.com>
To: "'John Stracke'" <francis@ecal.com>, ietf@ietf.org
Subject: RE: IETF Adelaide and interim meetings for APPS WGs
Date: Wed, 16 Feb 2000 16:23:10 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

> -----Original Message-----
> From: John Stracke [mailto:francis@ecal.com]

> Probably worse than nothing, unless there are much better 
> translators than babelfish out there.  WG discussions get
> down to really niggly points; a translator that doesn't
> work *perfectly* is likely to make things worse.  At
> least today, if we're talking through a language barrier, 
> there's a human brain doing the translation, able to
> recognize problems and rephrase as needed.

Via babelfish.altavista.com, and translated from English to German and back

Probably falsely than nothing, it is it many better compilers/translators
than babelfish gives out there. WG discussions down on really arrive niggly
points; a compiler/translator, that does not operate * perfectly * is
probable to form things falsely. At least today, if we speak by a language
barrier, a human brain give it, which does the translation, able, to detect
and again-formulate problems, how uses.  

And English/French/English:-

Probably worse than anything, unless there are translators much better than
the babelfish outside there. The discussions of WP descend really niggly at
the points; a translator who does not function * perfectly * is likely to
make things worse. At least today, if we speak by a linguistic barrier,
there let us be a human making translation, able brain identify problems and
reformulate them like necessary.

You can see the decay in the clarity of the original message. 
If I had received something similar purporting to be from an IETF member in
a country that I didn't speak the language of, I would assume someone had
reinitialized Mark V. Chaney.

cheers,
Stewart



From owner-ietf-outbound@ietf.org  Wed Feb 16 11:36:49 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05268
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Feb 2000 11:36:49 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA25417;
	Wed, 16 Feb 2000 11:34:43 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id LAA04921
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 11:30:02 -0500 (EST)
Received: from velma.seeglasgow.com (velma.seeglasgow.com [212.250.141.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04690
	for <ietf@ietf.org>; Wed, 16 Feb 2000 11:23:30 -0500 (EST)
Received: by velma.seeglasgow.com with Internet Mail Service (5.5.2650.21)
	id <DY5CK4T8>; Wed, 16 Feb 2000 16:23:12 -0000
Message-ID: <91FBC84CBEF8D211AE2E0008C79F8A9517C4D5@velma.seeglasgow.com>
From: Stewart Nolan <stewart.nolan@seeglasgow.com>
To: "'John Stracke'" <francis@ecal.com>, ietf@ietf.org
Subject: RE: IETF Adelaide and interim meetings for APPS WGs
Date: Wed, 16 Feb 2000 16:23:10 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

> -----Original Message-----
> From: John Stracke [mailto:francis@ecal.com]

> Probably worse than nothing, unless there are much better 
> translators than babelfish out there.  WG discussions get
> down to really niggly points; a translator that doesn't
> work *perfectly* is likely to make things worse.  At
> least today, if we're talking through a language barrier, 
> there's a human brain doing the translation, able to
> recognize problems and rephrase as needed.

Via babelfish.altavista.com, and translated from English to German and back

Probably falsely than nothing, it is it many better compilers/translators
than babelfish gives out there. WG discussions down on really arrive niggly
points; a compiler/translator, that does not operate * perfectly * is
probable to form things falsely. At least today, if we speak by a language
barrier, a human brain give it, which does the translation, able, to detect
and again-formulate problems, how uses.  

And English/French/English:-

Probably worse than anything, unless there are translators much better than
the babelfish outside there. The discussions of WP descend really niggly at
the points; a translator who does not function * perfectly * is likely to
make things worse. At least today, if we speak by a linguistic barrier,
there let us be a human making translation, able brain identify problems and
reformulate them like necessary.

You can see the decay in the clarity of the original message. 
If I had received something similar purporting to be from an IETF member in
a country that I didn't speak the language of, I would assume someone had
reinitialized Mark V. Chaney.

cheers,
Stewart



From owner-ietf-outbound  Wed Feb 16 12:11:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA06622
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 12:10:02 -0500 (EST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06285
	for <ietf@ietf.org>; Wed, 16 Feb 2000 12:03:48 -0500 (EST)
Received: from zed.isi.edu (zed-e.isi.edu [128.9.160.57])
	by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id JAA26904;
	Wed, 16 Feb 2000 09:03:44 -0800 (PST)
From: Bill Manning <bmanning@ISI.EDU>
Received: (from bmanning@localhost)
	by zed.isi.edu (8.8.7/8.8.6) id JAA06652;
	Wed, 16 Feb 2000 09:03:32 -0800 (PST)
Message-Id: <200002161703.JAA06652@zed.isi.edu>
Subject: Re: Question re: an Internet-Draft and testing/deployment
To: Valdis.Kletnieks@vt.edu
Date: Wed, 16 Feb 2000 09:03:32 -0800 (PST)
Cc: ietf@ietf.org
In-Reply-To: <200002161549.e1GFnY926128@black-ice.cc.vt.edu> from "Valdis.Kletnieks@vt.edu" at Feb 16, 2000 10:49:32 AM
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

% --- start excerpt
% A New Internet-Draft is available from the on-line Internet-Drafts directories.
% 
% 
% 	Title		: Compatible Internationalized Domain Names Using 
%                           Compression
% 	Author(s)	: P. Hoffman
% 	Filename	: draft-hoffman-idn-cidnuc-02.txt
% 	Pages		: 12
% 	Date		: 15-Feb-00
% 	
% This protocol describes a transformation method for representing non-
% ASCII characters in domain names in a fashion that is completely
% compatible with the current DNS. It meets the many requirements for
% internationalization of domain names.
% 
% Note: this protocol is quite experimental and should not be deployed in
% the Internet until it reaches standards track in the IETF.
% --- end excerpt
% 
% Regarding the Note: - is there any coherent plan regarding testing/deployement
% in regards to moving this from Experimental to Standards Track?
% 
% -- 
% 				Valdis Kletnieks
% 				Operating Systems Analyst
% 				Virginia Tech

I hope not, This will be the first IETF where this WG meets. This is -one-
of several methods being discussed. We haven't even reached closure on
the appropriate scope. This draft is an attempt to walk one vector of 
the problem space. 

-- 
--bill



From owner-ietf-outbound@ietf.org  Wed Feb 16 12:16:26 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06837
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Feb 2000 12:16:26 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA26800;
	Wed, 16 Feb 2000 12:14:23 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id MAA06622
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 12:10:02 -0500 (EST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06285
	for <ietf@ietf.org>; Wed, 16 Feb 2000 12:03:48 -0500 (EST)
Received: from zed.isi.edu (zed-e.isi.edu [128.9.160.57])
	by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id JAA26904;
	Wed, 16 Feb 2000 09:03:44 -0800 (PST)
From: Bill Manning <bmanning@ISI.EDU>
Received: (from bmanning@localhost)
	by zed.isi.edu (8.8.7/8.8.6) id JAA06652;
	Wed, 16 Feb 2000 09:03:32 -0800 (PST)
Message-Id: <200002161703.JAA06652@zed.isi.edu>
Subject: Re: Question re: an Internet-Draft and testing/deployment
To: Valdis.Kletnieks@vt.edu
Date: Wed, 16 Feb 2000 09:03:32 -0800 (PST)
Cc: ietf@ietf.org
In-Reply-To: <200002161549.e1GFnY926128@black-ice.cc.vt.edu> from "Valdis.Kletnieks@vt.edu" at Feb 16, 2000 10:49:32 AM
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

% --- start excerpt
% A New Internet-Draft is available from the on-line Internet-Drafts directories.
% 
% 
% 	Title		: Compatible Internationalized Domain Names Using 
%                           Compression
% 	Author(s)	: P. Hoffman
% 	Filename	: draft-hoffman-idn-cidnuc-02.txt
% 	Pages		: 12
% 	Date		: 15-Feb-00
% 	
% This protocol describes a transformation method for representing non-
% ASCII characters in domain names in a fashion that is completely
% compatible with the current DNS. It meets the many requirements for
% internationalization of domain names.
% 
% Note: this protocol is quite experimental and should not be deployed in
% the Internet until it reaches standards track in the IETF.
% --- end excerpt
% 
% Regarding the Note: - is there any coherent plan regarding testing/deployement
% in regards to moving this from Experimental to Standards Track?
% 
% -- 
% 				Valdis Kletnieks
% 				Operating Systems Analyst
% 				Virginia Tech

I hope not, This will be the first IETF where this WG meets. This is -one-
of several methods being discussed. We haven't even reached closure on
the appropriate scope. This draft is an attempt to walk one vector of 
the problem space. 

-- 
--bill



From owner-ietf-outbound  Wed Feb 16 12:20:45 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA07051
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 12:20:03 -0500 (EST)
Received: from jazz.viagenie.qc.ca (jazz.viagenie.qc.ca [206.123.31.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06336
	for <ietf@ietf.org>; Wed, 16 Feb 2000 12:05:15 -0500 (EST)
Received: from classic (modemcable128.194-200-24.que.mc.videotron.net [24.200.194.128])
	by jazz.viagenie.qc.ca (Viagenie/8.9.3) with ESMTP id MAA48461;
	Wed, 16 Feb 2000 12:07:03 -0500 (EST)
Message-Id: <4.2.2.20000216115721.020796f8@mail.viagenie.qc.ca>
X-Sender: blanchet@mail.viagenie.qc.ca
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Wed, 16 Feb 2000 12:05:18 -0500
To: Valdis.Kletnieks@vt.edu, ietf@ietf.org
From: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>
Subject: Re: Question re: an Internet-Draft and testing/deployment
In-Reply-To: <200002161549.e1GFnY926128@black-ice.cc.vt.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 10:49 2000-02-16 -0500, Valdis.Kletnieks@vt.edu wrote:
>Noticed this one this morning:
>
>--- start excerpt
>A New Internet-Draft is available from the on-line Internet-Drafts 
>directories.
>
>
>         Title           : Compatible Internationalized Domain Names Using
>                           Compression
>         Author(s)       : P. Hoffman
>         Filename        : draft-hoffman-idn-cidnuc-02.txt
>         Pages           : 12
>         Date            : 15-Feb-00
>
>This protocol describes a transformation method for representing non-
>ASCII characters in domain names in a fashion that is completely
>compatible with the current DNS. It meets the many requirements for
>internationalization of domain names.
>
>Note: this protocol is quite experimental and should not be deployed in
>the Internet until it reaches standards track in the IETF.
>--- end excerpt
>
>Regarding the Note: - is there any coherent plan regarding testing/deployement
>in regards to moving this from Experimental to Standards Track?

- this is an individual submission, not a idn wg draft
- this is interesting work that is currently discussed in idn wg mailing 
list, while the current charter do not cover new protocols. the wg charter 
is currently on requirements and documenting current implementations.
- while there is a wide interest and rough concensus (my own opinion) that 
an idn solution has to be engineered and deployed, it is premature at this 
stage to identify which proposal(s) is going to be on standards 
track.  And, unless the IESG would accept that individual submission and 
put it on standard track, the proposal who will go on standard track should 
be discussed in a wg (my own opinion), since the impact of deploying idn 
will be important. The idn wg is probably today the only one in the IETF 
related to that topic.
- I would suggest you to join our wg mailing list:  idn-request@ops.ietf.org

Marc, co-chair of idn wg.




>--
>                                 Valdis Kletnieks
>                                 Operating Systems Analyst
>                                 Virginia Tech




From owner-ietf-outbound@ietf.org  Wed Feb 16 12:25:16 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07244
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Feb 2000 12:25:16 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA27116;
	Wed, 16 Feb 2000 12:23:12 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id MAA07051
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 12:20:03 -0500 (EST)
Received: from jazz.viagenie.qc.ca (jazz.viagenie.qc.ca [206.123.31.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06336
	for <ietf@ietf.org>; Wed, 16 Feb 2000 12:05:15 -0500 (EST)
Received: from classic (modemcable128.194-200-24.que.mc.videotron.net [24.200.194.128])
	by jazz.viagenie.qc.ca (Viagenie/8.9.3) with ESMTP id MAA48461;
	Wed, 16 Feb 2000 12:07:03 -0500 (EST)
Message-Id: <4.2.2.20000216115721.020796f8@mail.viagenie.qc.ca>
X-Sender: blanchet@mail.viagenie.qc.ca
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Wed, 16 Feb 2000 12:05:18 -0500
To: Valdis.Kletnieks@vt.edu, ietf@ietf.org
From: Marc Blanchet <Marc.Blanchet@viagenie.qc.ca>
Subject: Re: Question re: an Internet-Draft and testing/deployment
In-Reply-To: <200002161549.e1GFnY926128@black-ice.cc.vt.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 10:49 2000-02-16 -0500, Valdis.Kletnieks@vt.edu wrote:
>Noticed this one this morning:
>
>--- start excerpt
>A New Internet-Draft is available from the on-line Internet-Drafts 
>directories.
>
>
>         Title           : Compatible Internationalized Domain Names Using
>                           Compression
>         Author(s)       : P. Hoffman
>         Filename        : draft-hoffman-idn-cidnuc-02.txt
>         Pages           : 12
>         Date            : 15-Feb-00
>
>This protocol describes a transformation method for representing non-
>ASCII characters in domain names in a fashion that is completely
>compatible with the current DNS. It meets the many requirements for
>internationalization of domain names.
>
>Note: this protocol is quite experimental and should not be deployed in
>the Internet until it reaches standards track in the IETF.
>--- end excerpt
>
>Regarding the Note: - is there any coherent plan regarding testing/deployement
>in regards to moving this from Experimental to Standards Track?

- this is an individual submission, not a idn wg draft
- this is interesting work that is currently discussed in idn wg mailing 
list, while the current charter do not cover new protocols. the wg charter 
is currently on requirements and documenting current implementations.
- while there is a wide interest and rough concensus (my own opinion) that 
an idn solution has to be engineered and deployed, it is premature at this 
stage to identify which proposal(s) is going to be on standards 
track.  And, unless the IESG would accept that individual submission and 
put it on standard track, the proposal who will go on standard track should 
be discussed in a wg (my own opinion), since the impact of deploying idn 
will be important. The idn wg is probably today the only one in the IETF 
related to that topic.
- I would suggest you to join our wg mailing list:  idn-request@ops.ietf.org

Marc, co-chair of idn wg.




>--
>                                 Valdis Kletnieks
>                                 Operating Systems Analyst
>                                 Virginia Tech




From owner-ietf-outbound  Wed Feb 16 12:30:51 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA07462
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 12:30:02 -0500 (EST)
Received: from senie.com (anise.senie.com [199.125.85.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07096
	for <ietf@ietf.org>; Wed, 16 Feb 2000 12:20:55 -0500 (EST)
Received: from senie.com (anise.senie.com [199.125.85.28])
	by senie.com (8.8.7/8.8.7) with ESMTP id MAA05815
	for <ietf@ietf.org>; Wed, 16 Feb 2000 12:20:52 -0500
Message-ID: <38AADC73.A638874D@senie.com>
Date: Wed, 16 Feb 2000 12:20:51 -0500
From: Daniel Senie <dts@senie.com>
Organization: Amaranth Networks Inc.
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
References: <016401bf7763$4b82e380$0300000a@cisco.com> <v04220802b4d078236d2c@[171.78.30.107]>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Stephen Kent wrote:
> 
> Eliot,
> 
> Some of the DoS attacks we saw last week were good, old-fashioned SYN
> floods.  Hosts do have a responsibility here, more than ISPs, since
> it is quite feasible to tie up a host's pool of TCBs with a small
> number of packets, even if the attack tool does not use spoofed
> sourced addresses (or if the spoofed addresses are from a legitimate
> pool allocated to a subscriber site).

And at least one of the attacks last week indeed was a smurf. Filters
would have helped in some cases and not others.

> 
> The point I have tried to make, unsuccessfully, is not that
> performing ingress filtering is bad, and thus should not be
> performed.  Rather, I am pointing out that it is a bad idea to rely
> on such filtering as a primary means of defense. There are several
> reasons for saying this:

Reliance on any single method will be insufficient. It will take several
methods.

>         - not all ISPs will find it feasible to provide such filtering

This needs to be addressed. Feasible due to expense of equipment,
loading, what? ISPs need to implement this now or soon. When purchasing
new gear, the ability to do filtering without affecting performance
should be on the list of features given to manufacturers.

When we first started the drafts for RFC 2267, back in 1996, concerns
were raised that equipment couldn't handle the load. The suggestion then
was the same. NEXT TIME you order equipment, make it a requirement. It
is possible to build the gear to do the filtering. If ISPs don't demand
it of their vendors, they won't get it, though.

>         - not all ISPs are trusted to do the filtering (in the global Internet)

This issue can be addressed by their upstream providers with terms of
service agreements. Will it be perfect? Unlikely.

>         - a number of DDoS attacks can be launched without using
> spoofed addresses outside of those "appropriate" to the subscriber
> site

Which is NO reason to permit attacks which DO spoof. Filtering is going
to limit the types of attacks which can be launched, and permits
idenitification of the systems and networks where the packets come from.
It may still be necessary to chase down those sites and get action, but
at least it's possible to know WHICH SITES are the sources.

>         - some applications may legitimately make use of non-local
> addresses, as others have suggested

A point which is in dispute. Beyond that, operational reality is that
filtering DOES occur, and may occur somewhere neither you nor your
upstream ISP can control. To at least some extent it's useful to
understand present operational reality in choosing methodologies.

> 
> I have seen a long history of suggested solutions to security
> problems which are only partially effective against current forms of
> attacks, vs. providing protection against a larger class of attacks.
> I'm trying to suggest that we not follow this pattern.

Please suggest another course of action. To date, the IETF has spent a
considerable amount of its security mindshare on IPSec. While developing
that functionality, operational reality resulted in the deployment of
huge numbers of NAT boxes, and IPSec and NAT aren't interoperable.
Another case of operational reality and design colliding.

Ingress filtering does not provide a complete solution. Neither did the
patches to operating systems to guard against SYN flooding. By using
both of those, we limit the effectiveness of those types of attacks. I
expect we will have to add a whole suite of techniques to bring the
problems under some reasonable level of control. What is unclear is why
some think we could or should do nothing in the short term.



-- 
-----------------------------------------------------------------
Daniel Senie                                        dts@senie.com
Amaranth Networks Inc.            http://www.amaranthnetworks.com



From owner-ietf-outbound@ietf.org  Wed Feb 16 12:35:54 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07733
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Feb 2000 12:35:54 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA27535;
	Wed, 16 Feb 2000 12:33:21 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id MAA07462
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 12:30:02 -0500 (EST)
Received: from senie.com (anise.senie.com [199.125.85.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07096
	for <ietf@ietf.org>; Wed, 16 Feb 2000 12:20:55 -0500 (EST)
Received: from senie.com (anise.senie.com [199.125.85.28])
	by senie.com (8.8.7/8.8.7) with ESMTP id MAA05815
	for <ietf@ietf.org>; Wed, 16 Feb 2000 12:20:52 -0500
Message-ID: <38AADC73.A638874D@senie.com>
Date: Wed, 16 Feb 2000 12:20:51 -0500
From: Daniel Senie <dts@senie.com>
Organization: Amaranth Networks Inc.
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
References: <016401bf7763$4b82e380$0300000a@cisco.com> <v04220802b4d078236d2c@[171.78.30.107]>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Stephen Kent wrote:
> 
> Eliot,
> 
> Some of the DoS attacks we saw last week were good, old-fashioned SYN
> floods.  Hosts do have a responsibility here, more than ISPs, since
> it is quite feasible to tie up a host's pool of TCBs with a small
> number of packets, even if the attack tool does not use spoofed
> sourced addresses (or if the spoofed addresses are from a legitimate
> pool allocated to a subscriber site).

And at least one of the attacks last week indeed was a smurf. Filters
would have helped in some cases and not others.

> 
> The point I have tried to make, unsuccessfully, is not that
> performing ingress filtering is bad, and thus should not be
> performed.  Rather, I am pointing out that it is a bad idea to rely
> on such filtering as a primary means of defense. There are several
> reasons for saying this:

Reliance on any single method will be insufficient. It will take several
methods.

>         - not all ISPs will find it feasible to provide such filtering

This needs to be addressed. Feasible due to expense of equipment,
loading, what? ISPs need to implement this now or soon. When purchasing
new gear, the ability to do filtering without affecting performance
should be on the list of features given to manufacturers.

When we first started the drafts for RFC 2267, back in 1996, concerns
were raised that equipment couldn't handle the load. The suggestion then
was the same. NEXT TIME you order equipment, make it a requirement. It
is possible to build the gear to do the filtering. If ISPs don't demand
it of their vendors, they won't get it, though.

>         - not all ISPs are trusted to do the filtering (in the global Internet)

This issue can be addressed by their upstream providers with terms of
service agreements. Will it be perfect? Unlikely.

>         - a number of DDoS attacks can be launched without using
> spoofed addresses outside of those "appropriate" to the subscriber
> site

Which is NO reason to permit attacks which DO spoof. Filtering is going
to limit the types of attacks which can be launched, and permits
idenitification of the systems and networks where the packets come from.
It may still be necessary to chase down those sites and get action, but
at least it's possible to know WHICH SITES are the sources.

>         - some applications may legitimately make use of non-local
> addresses, as others have suggested

A point which is in dispute. Beyond that, operational reality is that
filtering DOES occur, and may occur somewhere neither you nor your
upstream ISP can control. To at least some extent it's useful to
understand present operational reality in choosing methodologies.

> 
> I have seen a long history of suggested solutions to security
> problems which are only partially effective against current forms of
> attacks, vs. providing protection against a larger class of attacks.
> I'm trying to suggest that we not follow this pattern.

Please suggest another course of action. To date, the IETF has spent a
considerable amount of its security mindshare on IPSec. While developing
that functionality, operational reality resulted in the deployment of
huge numbers of NAT boxes, and IPSec and NAT aren't interoperable.
Another case of operational reality and design colliding.

Ingress filtering does not provide a complete solution. Neither did the
patches to operating systems to guard against SYN flooding. By using
both of those, we limit the effectiveness of those types of attacks. I
expect we will have to add a whole suite of techniques to bring the
problems under some reasonable level of control. What is unclear is why
some think we could or should do nothing in the short term.



-- 
-----------------------------------------------------------------
Daniel Senie                                        dts@senie.com
Amaranth Networks Inc.            http://www.amaranthnetworks.com



From owner-ietf-outbound  Wed Feb 16 12:51:43 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA08093
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 12:50:05 -0500 (EST)
Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08061
	for <ietf@ietf.org>; Wed, 16 Feb 2000 12:49:27 -0500 (EST)
Received: from hermes.research.att.com (hermes.research.att.com [135.207.16.38])
	by mail-green.research.att.com (Postfix) with ESMTP
	id 162871E038; Wed, 16 Feb 2000 12:49:16 -0500 (EST)
Received: from SIGABA.research.att.com (sigaba.research.att.com [135.207.23.169])
	by hermes.research.att.com (8.8.7/8.8.7) with ESMTP id MAA15966;
	Wed, 16 Feb 2000 12:50:00 -0500 (EST)
Received: by SIGABA.research.att.com (Postfix, from userid 54047)
	id 2CC7041F16; Wed, 16 Feb 2000 12:49:15 -0500 (EST)
Received: from roc (localhost [127.0.0.1])
	by SIGABA.research.att.com (Postfix) with ESMTP
	id 1DC15400B5; Wed, 16 Feb 2000 12:49:10 -0500 (EST)
X-Mailer: exmh version 2.1.1 10/15/1999
From: "Steven M. Bellovin" <smb@research.att.com>
To: Stephen Kent <kent@bbn.com>
Cc: "Eliot Lear" <lear@cisco.com>, ietf@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 16 Feb 2000 12:49:10 -0500
Sender: smb@research.att.com
Message-Id: <20000216174915.2CC7041F16@SIGABA.research.att.com>
X-Loop: ietf@ietf.org

In message <v04220802b4d078236d2c@[171.78.30.107]>, Stephen Kent writes:
> Eliot,
> 
> Some of the DoS attacks we saw last week were good, old-fashioned SYN 
> floods.  Hosts do have a responsibility here, more than ISPs, since 
> it is quite feasible to tie up a host's pool of TCBs with a small 
> number of packets, even if the attack tool does not use spoofed 
> sourced addresses (or if the spoofed addresses are from a legitimate 
> pool allocated to a subscriber site).

Yes, though it isn't clear to me that most of those forged SYNs got through...
> 
> The point I have tried to make, unsuccessfully, is not that 
> performing ingress filtering is bad, and thus should not be 
> performed.  Rather, I am pointing out that it is a bad idea to rely 
> on such filtering as a primary means of defense. There are several 
> reasons for saying this:
> 	- not all ISPs will find it feasible to provide such filtering
> 	- not all ISPs are trusted to do the filtering (in the global Internet)
> 	- a number of DDoS attacks can be launched without using 
> spoofed addresses outside of those "appropriate" to the subscriber 
> site
> 	- some applications may legitimately make use of non-local 
> addresses, as others have suggested
> 

The problem here is that flooding attacks target the network, not the host.  
The host is thus not capable of mounting a defense -- it's not the victim, in 
some sense.

Conventional security methodology would say that the aggrieved party should do 
the authentication.  Of course, that's hard on the Internet -- in fact, we 
don't *want* people to have to authenticate themselves to the network elements 
in order to transmit.  (There are, of course, networks that do have such 
requirements.  The most common form is known as the telephone system.  I don't 
think we want to reinvent that.)  Filtering is a very coarse form of 
address-based authentication to the first outside hop; I don't see a better 
choice.

Perhaps the network can use beefed-up congestion control mechanisms to stop 
such floods.  I hope so, but it seems to be a research issue; I'd be surprised 
if such new mechanisms could be deployed sooner than 2002.  What do we do in 
the meantime?  (Trying to secure all of the myriad endpoints is even more 
hopeless than trying to get all ISPs to do proper filtering.)  Do you have any 
specific suggestions?  Seriously -- what do you recommend as a defense against 
flooding attacks?

		--Steve Bellovin




From owner-ietf-outbound@ietf.org  Wed Feb 16 12:58:00 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08274
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Feb 2000 12:57:59 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA28157;
	Wed, 16 Feb 2000 12:55:53 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id MAA08093
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 12:50:05 -0500 (EST)
Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08061
	for <ietf@ietf.org>; Wed, 16 Feb 2000 12:49:27 -0500 (EST)
Received: from hermes.research.att.com (hermes.research.att.com [135.207.16.38])
	by mail-green.research.att.com (Postfix) with ESMTP
	id 162871E038; Wed, 16 Feb 2000 12:49:16 -0500 (EST)
Received: from SIGABA.research.att.com (sigaba.research.att.com [135.207.23.169])
	by hermes.research.att.com (8.8.7/8.8.7) with ESMTP id MAA15966;
	Wed, 16 Feb 2000 12:50:00 -0500 (EST)
Received: by SIGABA.research.att.com (Postfix, from userid 54047)
	id 2CC7041F16; Wed, 16 Feb 2000 12:49:15 -0500 (EST)
Received: from roc (localhost [127.0.0.1])
	by SIGABA.research.att.com (Postfix) with ESMTP
	id 1DC15400B5; Wed, 16 Feb 2000 12:49:10 -0500 (EST)
X-Mailer: exmh version 2.1.1 10/15/1999
From: "Steven M. Bellovin" <smb@research.att.com>
To: Stephen Kent <kent@bbn.com>
Cc: "Eliot Lear" <lear@cisco.com>, ietf@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 16 Feb 2000 12:49:10 -0500
Sender: smb@research.att.com
Message-Id: <20000216174915.2CC7041F16@SIGABA.research.att.com>
X-Loop: ietf@ietf.org

In message <v04220802b4d078236d2c@[171.78.30.107]>, Stephen Kent writes:
> Eliot,
> 
> Some of the DoS attacks we saw last week were good, old-fashioned SYN 
> floods.  Hosts do have a responsibility here, more than ISPs, since 
> it is quite feasible to tie up a host's pool of TCBs with a small 
> number of packets, even if the attack tool does not use spoofed 
> sourced addresses (or if the spoofed addresses are from a legitimate 
> pool allocated to a subscriber site).

Yes, though it isn't clear to me that most of those forged SYNs got through...
> 
> The point I have tried to make, unsuccessfully, is not that 
> performing ingress filtering is bad, and thus should not be 
> performed.  Rather, I am pointing out that it is a bad idea to rely 
> on such filtering as a primary means of defense. There are several 
> reasons for saying this:
> 	- not all ISPs will find it feasible to provide such filtering
> 	- not all ISPs are trusted to do the filtering (in the global Internet)
> 	- a number of DDoS attacks can be launched without using 
> spoofed addresses outside of those "appropriate" to the subscriber 
> site
> 	- some applications may legitimately make use of non-local 
> addresses, as others have suggested
> 

The problem here is that flooding attacks target the network, not the host.  
The host is thus not capable of mounting a defense -- it's not the victim, in 
some sense.

Conventional security methodology would say that the aggrieved party should do 
the authentication.  Of course, that's hard on the Internet -- in fact, we 
don't *want* people to have to authenticate themselves to the network elements 
in order to transmit.  (There are, of course, networks that do have such 
requirements.  The most common form is known as the telephone system.  I don't 
think we want to reinvent that.)  Filtering is a very coarse form of 
address-based authentication to the first outside hop; I don't see a better 
choice.

Perhaps the network can use beefed-up congestion control mechanisms to stop 
such floods.  I hope so, but it seems to be a research issue; I'd be surprised 
if such new mechanisms could be deployed sooner than 2002.  What do we do in 
the meantime?  (Trying to secure all of the myriad endpoints is even more 
hopeless than trying to get all ISPs to do proper filtering.)  Do you have any 
specific suggestions?  Seriously -- what do you recommend as a defense against 
flooding attacks?

		--Steve Bellovin




From owner-ietf-outbound  Wed Feb 16 13:00:36 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA08322
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 13:00:02 -0500 (EST)
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08219
	for <ietf@ietf.org>; Wed, 16 Feb 2000 12:56:13 -0500 (EST)
Received: from laptop (ip12.proper.com [165.227.249.12])
	by ns.secondary.com (8.9.3/8.9.3) with ESMTP id JAA08538
	for <ietf@ietf.org>; Wed, 16 Feb 2000 09:52:35 -0800 (PST)
Message-Id: <4.2.1.20000216095346.00bba480@mail.imc.org>
X-Sender: phoffman@mail.imc.org
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.1 
Date: Wed, 16 Feb 2000 09:57:45 -0800
To: ietf@ietf.org
From: Paul Hoffman / IMC <phoffman@IMC.ORG>
Subject: Re: Question re: an Internet-Draft and testing/deployment
In-Reply-To: <200002161549.e1GFnY926128@black-ice.cc.vt.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 10:49 AM 2/16/00 -0500, Valdis.Kletnieks@vt.edu wrote:
>Note: this protocol is quite experimental and should not be deployed in
>the Internet until it reaches standards track in the IETF.
>--- end excerpt
>
>Regarding the Note: - is there any coherent plan regarding testing/deployement
>in regards to moving this from Experimental to Standards Track?

As the draft author, let me assure you that it is far from being an 
Experimental RFC. I put these words in so that, if someone tripped across 
the draft and said "hey, let's implement this", they wouldn't think anyone 
else was. As others have said, there are a variety of IDN proposals at this 
time, and it would be downright silly for anyone to assume which, if any, 
of them will even look like the one that might be chosen down the line.

The note shouldn't be needed, given the definition of an Internet Draft, 
but it appears that many folks have forgotten that definition.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-ietf-outbound@ietf.org  Wed Feb 16 13:04:41 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08594
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Feb 2000 13:04:41 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA28448;
	Wed, 16 Feb 2000 13:02:36 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id NAA08322
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 13:00:02 -0500 (EST)
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08219
	for <ietf@ietf.org>; Wed, 16 Feb 2000 12:56:13 -0500 (EST)
Received: from laptop (ip12.proper.com [165.227.249.12])
	by ns.secondary.com (8.9.3/8.9.3) with ESMTP id JAA08538
	for <ietf@ietf.org>; Wed, 16 Feb 2000 09:52:35 -0800 (PST)
Message-Id: <4.2.1.20000216095346.00bba480@mail.imc.org>
X-Sender: phoffman@mail.imc.org
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.1 
Date: Wed, 16 Feb 2000 09:57:45 -0800
To: ietf@ietf.org
From: Paul Hoffman / IMC <phoffman@IMC.ORG>
Subject: Re: Question re: an Internet-Draft and testing/deployment
In-Reply-To: <200002161549.e1GFnY926128@black-ice.cc.vt.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 10:49 AM 2/16/00 -0500, Valdis.Kletnieks@vt.edu wrote:
>Note: this protocol is quite experimental and should not be deployed in
>the Internet until it reaches standards track in the IETF.
>--- end excerpt
>
>Regarding the Note: - is there any coherent plan regarding testing/deployement
>in regards to moving this from Experimental to Standards Track?

As the draft author, let me assure you that it is far from being an 
Experimental RFC. I put these words in so that, if someone tripped across 
the draft and said "hey, let's implement this", they wouldn't think anyone 
else was. As others have said, there are a variety of IDN proposals at this 
time, and it would be downright silly for anyone to assume which, if any, 
of them will even look like the one that might be chosen down the line.

The note shouldn't be needed, given the definition of an Internet Draft, 
but it appears that many folks have forgotten that definition.

--Paul Hoffman, Director
--Internet Mail Consortium



From owner-ietf-outbound  Wed Feb 16 13:21:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA09019
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 13:20:02 -0500 (EST)
Received: from fwns1.raleigh.ibm.com (fwns1d.raleigh.ibm.com [204.146.167.235])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08920
	for <ietf@ietf.org>; Wed, 16 Feb 2000 13:17:02 -0500 (EST)
Received: from rtpmail02.raleigh.ibm.com (rtpmail02.raleigh.ibm.com [9.37.172.48])
	by fwns1.raleigh.ibm.com (8.9.0/8.9.0/RTP-FW-1.2) with ESMTP id NAA20162
	for <ietf@ietf.org>; Wed, 16 Feb 2000 13:16:53 -0500
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.37.82.31])
	by rtpmail02.raleigh.ibm.com (8.8.5/8.8.5/RTP-ral-1.1) with ESMTP id NAA26184;
	Wed, 16 Feb 2000 13:16:53 -0500
Received: from rotala.raleigh.ibm.com (localhost [127.0.0.1]) by rotala.raleigh.ibm.com (8.9.3/8.7/RTP-ral-1.0) with ESMTP id NAA15938; Wed, 16 Feb 2000 13:17:02 -0500
Message-Id: <200002161817.NAA15938@rotala.raleigh.ibm.com>
To: Brian E Carpenter <brian@hursley.ibm.com>
cc: ietf@ietf.org
Subject: Re: IETF Adelaide and interim meetings for APPS WGs 
In-Reply-To: Message from Brian E Carpenter <brian@hursley.ibm.com> 
   of "Wed, 16 Feb 2000 08:16:21 CST." <38AAB135.5C5FCCF8@hursley.ibm.com> 
Date: Wed, 16 Feb 2000 13:17:02 -0500
From: Thomas Narten <narten@raleigh.ibm.com>
X-Loop: ietf@ietf.org

> It is not the case that few WGs are holding meetings. The published agenda
> just isn't complete yet; it never is at this stage.

This is very true. Looking at the Internet Area, I expect all but one
of the WGs that normally have face-to-face meetings to meet in
Adelaide. Plus, there are three potential BOFs in the works, none of
which have been approved yet, and thus, also do not yet appear on the
agenda.

Thomas



From owner-ietf-outbound@ietf.org  Wed Feb 16 13:29:18 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09183
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Feb 2000 13:29:18 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA29052;
	Wed, 16 Feb 2000 13:27:06 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id NAA09019
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 13:20:02 -0500 (EST)
Received: from fwns1.raleigh.ibm.com (fwns1d.raleigh.ibm.com [204.146.167.235])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08920
	for <ietf@ietf.org>; Wed, 16 Feb 2000 13:17:02 -0500 (EST)
Received: from rtpmail02.raleigh.ibm.com (rtpmail02.raleigh.ibm.com [9.37.172.48])
	by fwns1.raleigh.ibm.com (8.9.0/8.9.0/RTP-FW-1.2) with ESMTP id NAA20162
	for <ietf@ietf.org>; Wed, 16 Feb 2000 13:16:53 -0500
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.37.82.31])
	by rtpmail02.raleigh.ibm.com (8.8.5/8.8.5/RTP-ral-1.1) with ESMTP id NAA26184;
	Wed, 16 Feb 2000 13:16:53 -0500
Received: from rotala.raleigh.ibm.com (localhost [127.0.0.1]) by rotala.raleigh.ibm.com (8.9.3/8.7/RTP-ral-1.0) with ESMTP id NAA15938; Wed, 16 Feb 2000 13:17:02 -0500
Message-Id: <200002161817.NAA15938@rotala.raleigh.ibm.com>
To: Brian E Carpenter <brian@hursley.ibm.com>
cc: ietf@ietf.org
Subject: Re: IETF Adelaide and interim meetings for APPS WGs 
In-Reply-To: Message from Brian E Carpenter <brian@hursley.ibm.com> 
   of "Wed, 16 Feb 2000 08:16:21 CST." <38AAB135.5C5FCCF8@hursley.ibm.com> 
Date: Wed, 16 Feb 2000 13:17:02 -0500
From: Thomas Narten <narten@raleigh.ibm.com>
X-Loop: ietf@ietf.org

> It is not the case that few WGs are holding meetings. The published agenda
> just isn't complete yet; it never is at this stage.

This is very true. Looking at the Internet Area, I expect all but one
of the WGs that normally have face-to-face meetings to meet in
Adelaide. Plus, there are three potential BOFs in the works, none of
which have been approved yet, and thus, also do not yet appear on the
agenda.

Thomas



From owner-ietf-outbound  Wed Feb 16 13:30:53 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA09221
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 13:30:03 -0500 (EST)
Received: from po1.bbn.com (PO1.BBN.COM [192.1.50.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09142
	for <ietf@ietf.org>; Wed, 16 Feb 2000 13:26:46 -0500 (EST)
Received: from [171.78.30.107] (comsec.bbn.com [171.78.30.107])
	by po1.bbn.com (8.9.1/8.9.1) with ESMTP id NAA19504;
	Wed, 16 Feb 2000 13:26:37 -0500 (EST)
Mime-Version: 1.0
X-Sender: kent@po1.bbn.com
Message-Id: <v0422080cb4d099a84d13@[171.78.30.107]>
In-Reply-To: <20000216174915.2CC7041F16@SIGABA.research.att.com>
References: <20000216174915.2CC7041F16@SIGABA.research.att.com>
Date: Wed, 16 Feb 2000 13:18:11 -0500
To: "Steven M. Bellovin" <smb@research.att.com>
From: Stephen Kent <kent@bbn.com>
Subject: Re: Internet SYN Flooding, spoofing attacks
Cc: ietf@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

Steve,

The AT&T experiences might be different, but at GTE-I, a SYN flood 
was the primary attack mechanism for one major web site that we host. 
Also, it is not at all clear that our network had a problem handling 
the other flooded traffic (ICMP Echo Reply and UDP traffic) that was 
sent to 3 other targets on our net, but the web hosts that were 
targets certainly did suffer from processing the traffic.

Steve

P.S.  Nice photo and quotes in Newsweek!



From owner-ietf-outbound@ietf.org  Wed Feb 16 13:37:45 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09467
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Feb 2000 13:37:45 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA29337;
	Wed, 16 Feb 2000 13:35:41 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id NAA09221
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 13:30:03 -0500 (EST)
Received: from po1.bbn.com (PO1.BBN.COM [192.1.50.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09142
	for <ietf@ietf.org>; Wed, 16 Feb 2000 13:26:46 -0500 (EST)
Received: from [171.78.30.107] (comsec.bbn.com [171.78.30.107])
	by po1.bbn.com (8.9.1/8.9.1) with ESMTP id NAA19504;
	Wed, 16 Feb 2000 13:26:37 -0500 (EST)
Mime-Version: 1.0
X-Sender: kent@po1.bbn.com
Message-Id: <v0422080cb4d099a84d13@[171.78.30.107]>
In-Reply-To: <20000216174915.2CC7041F16@SIGABA.research.att.com>
References: <20000216174915.2CC7041F16@SIGABA.research.att.com>
Date: Wed, 16 Feb 2000 13:18:11 -0500
To: "Steven M. Bellovin" <smb@research.att.com>
From: Stephen Kent <kent@bbn.com>
Subject: Re: Internet SYN Flooding, spoofing attacks
Cc: ietf@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

Steve,

The AT&T experiences might be different, but at GTE-I, a SYN flood 
was the primary attack mechanism for one major web site that we host. 
Also, it is not at all clear that our network had a problem handling 
the other flooded traffic (ICMP Echo Reply and UDP traffic) that was 
sent to 3 other targets on our net, but the web hosts that were 
targets certainly did suffer from processing the traffic.

Steve

P.S.  Nice photo and quotes in Newsweek!



From owner-ietf-outbound  Wed Feb 16 13:51:03 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA09807
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 13:50:02 -0500 (EST)
Received: from joy.songbird.com (IDENT:root@joy.songbird.com [208.184.79.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09752
	for <ietf@ietf.org>; Wed, 16 Feb 2000 13:48:26 -0500 (EST)
Received: from 1Cust96.tnt20.sfo3.da.uu.net (1Cust96.tnt20.sfo3.da.uu.net [63.27.224.96])
	by joy.songbird.com (8.9.3/8.9.3) with SMTP id KAA15901;
	Wed, 16 Feb 2000 10:48:01 -0800
X-Authentication-Warning: joy.songbird.com: 1Cust96.tnt20.sfo3.da.uu.net [63.27.224.96] didn't use HELO protocol
Message-Id: <4.3.0.39.0.20000216104434.00ba3240@mail.bayarea.net>
X-Sender: dcrocker@mail.bayarea.net
X-Mailer: QUALCOMM Windows Eudora Version 4.3.0.39 (Beta)
Date: Wed, 16 Feb 2000 10:46:26 -0800
To: "Steven M. Bellovin" <smb@research.att.com>
From: Dave Crocker <dcrocker@brandenburg.com>
Subject: Re: IETF Adelaide and interim meetings for APPS WGs 
Cc: ietf@ietf.org
In-Reply-To: <20000216155513.4BF1D41F16@SIGABA.research.att.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 10:55 AM 2/16/2000 -0500, Steven M. Bellovin wrote:
>Given airline load factors, I don't seem to be able to qualify for discounts
>on my trips to San Francisco from New Jersey -- which means that my 
>tickets to
>Adelaide are only very slightly more expensive.


only San Francisco? I thought the airline loading factor was because so 
many people want to leave New Jersey...

On the other hand, it would be amusing to imagine that high mortgage costs, 
or whatever, has people wanting to leave San Francisco... for New Jersey?

d/


=-=-=-=-=
Dave Crocker  <dcrocker@brandenburg.com>
Brandenburg Consulting  <www.brandenburg.com>
Tel: +1.408.246.8253,  Fax: +1.408.273.6464
675 Spruce Drive,  Sunnyvale, CA 94086 USA

Gong Xi Fa Cai   /  Selamat Tahun Baru Cina



From owner-ietf-outbound@ietf.org  Wed Feb 16 13:56:57 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09994
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Feb 2000 13:56:57 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA29706;
	Wed, 16 Feb 2000 13:54:52 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id NAA09807
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 13:50:02 -0500 (EST)
Received: from joy.songbird.com (IDENT:root@joy.songbird.com [208.184.79.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09752
	for <ietf@ietf.org>; Wed, 16 Feb 2000 13:48:26 -0500 (EST)
Received: from 1Cust96.tnt20.sfo3.da.uu.net (1Cust96.tnt20.sfo3.da.uu.net [63.27.224.96])
	by joy.songbird.com (8.9.3/8.9.3) with SMTP id KAA15901;
	Wed, 16 Feb 2000 10:48:01 -0800
X-Authentication-Warning: joy.songbird.com: 1Cust96.tnt20.sfo3.da.uu.net [63.27.224.96] didn't use HELO protocol
Message-Id: <4.3.0.39.0.20000216104434.00ba3240@mail.bayarea.net>
X-Sender: dcrocker@mail.bayarea.net
X-Mailer: QUALCOMM Windows Eudora Version 4.3.0.39 (Beta)
Date: Wed, 16 Feb 2000 10:46:26 -0800
To: "Steven M. Bellovin" <smb@research.att.com>
From: Dave Crocker <dcrocker@brandenburg.com>
Subject: Re: IETF Adelaide and interim meetings for APPS WGs 
Cc: ietf@ietf.org
In-Reply-To: <20000216155513.4BF1D41F16@SIGABA.research.att.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 10:55 AM 2/16/2000 -0500, Steven M. Bellovin wrote:
>Given airline load factors, I don't seem to be able to qualify for discounts
>on my trips to San Francisco from New Jersey -- which means that my 
>tickets to
>Adelaide are only very slightly more expensive.


only San Francisco? I thought the airline loading factor was because so 
many people want to leave New Jersey...

On the other hand, it would be amusing to imagine that high mortgage costs, 
or whatever, has people wanting to leave San Francisco... for New Jersey?

d/


=-=-=-=-=
Dave Crocker  <dcrocker@brandenburg.com>
Brandenburg Consulting  <www.brandenburg.com>
Tel: +1.408.246.8253,  Fax: +1.408.273.6464
675 Spruce Drive,  Sunnyvale, CA 94086 USA

Gong Xi Fa Cai   /  Selamat Tahun Baru Cina



From owner-ietf-outbound  Wed Feb 16 14:01:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA10078
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 14:00:02 -0500 (EST)
Received: from joy.songbird.com (IDENT:root@joy.songbird.com [208.184.79.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09917
	for <ietf@ietf.org>; Wed, 16 Feb 2000 13:53:19 -0500 (EST)
Received: from 1Cust96.tnt20.sfo3.da.uu.net (1Cust96.tnt20.sfo3.da.uu.net [63.27.224.96])
	by joy.songbird.com (8.9.3/8.9.3) with SMTP id KAA15937;
	Wed, 16 Feb 2000 10:53:09 -0800
X-Authentication-Warning: joy.songbird.com: 1Cust96.tnt20.sfo3.da.uu.net [63.27.224.96] didn't use HELO protocol
Message-Id: <4.3.0.39.0.20000216104119.00b944d0@mail.bayarea.net>
X-Sender: dcrocker@mail.bayarea.net
X-Mailer: QUALCOMM Windows Eudora Version 4.3.0.39 (Beta)
Date: Wed, 16 Feb 2000 10:42:28 -0800
To: Bill Manning <bmanning@ISI.EDU>
From: Dave Crocker <dcrocker@brandenburg.com>
Subject: Re: Question re: an Internet-Draft and testing/deployment
Cc: Valdis.Kletnieks@vt.edu, ietf@ietf.org
In-Reply-To: <200002161703.JAA06652@zed.isi.edu>
References: <200002161549.e1GFnY926128@black-ice.cc.vt.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 09:03 AM 2/16/2000 -0800, Bill Manning wrote:
>I hope not, This will be the first IETF where this WG meets. This is -one-
>of several methods being discussed. We haven't even reached closure on
>the appropriate scope. This draft is an attempt to walk one vector of
>the problem space.

Not just "discussed".  Tin Tan Wee has been working on this publicly for a 
couple of years and now has a well-supported, fully operational service.

d/

=-=-=-=-=
Dave Crocker  <dcrocker@brandenburg.com>
Brandenburg Consulting  <www.brandenburg.com>
Tel: +1.408.246.8253,  Fax: +1.408.273.6464
675 Spruce Drive,  Sunnyvale, CA 94086 USA

Gong Xi Fa Cai   /  Selamat Tahun Baru Cina



From owner-ietf-outbound@ietf.org  Wed Feb 16 14:08:37 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10403
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Feb 2000 14:08:37 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA00077;
	Wed, 16 Feb 2000 14:06:34 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id OAA10078
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 14:00:02 -0500 (EST)
Received: from joy.songbird.com (IDENT:root@joy.songbird.com [208.184.79.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09917
	for <ietf@ietf.org>; Wed, 16 Feb 2000 13:53:19 -0500 (EST)
Received: from 1Cust96.tnt20.sfo3.da.uu.net (1Cust96.tnt20.sfo3.da.uu.net [63.27.224.96])
	by joy.songbird.com (8.9.3/8.9.3) with SMTP id KAA15937;
	Wed, 16 Feb 2000 10:53:09 -0800
X-Authentication-Warning: joy.songbird.com: 1Cust96.tnt20.sfo3.da.uu.net [63.27.224.96] didn't use HELO protocol
Message-Id: <4.3.0.39.0.20000216104119.00b944d0@mail.bayarea.net>
X-Sender: dcrocker@mail.bayarea.net
X-Mailer: QUALCOMM Windows Eudora Version 4.3.0.39 (Beta)
Date: Wed, 16 Feb 2000 10:42:28 -0800
To: Bill Manning <bmanning@ISI.EDU>
From: Dave Crocker <dcrocker@brandenburg.com>
Subject: Re: Question re: an Internet-Draft and testing/deployment
Cc: Valdis.Kletnieks@vt.edu, ietf@ietf.org
In-Reply-To: <200002161703.JAA06652@zed.isi.edu>
References: <200002161549.e1GFnY926128@black-ice.cc.vt.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 09:03 AM 2/16/2000 -0800, Bill Manning wrote:
>I hope not, This will be the first IETF where this WG meets. This is -one-
>of several methods being discussed. We haven't even reached closure on
>the appropriate scope. This draft is an attempt to walk one vector of
>the problem space.

Not just "discussed".  Tin Tan Wee has been working on this publicly for a 
couple of years and now has a well-supported, fully operational service.

d/

=-=-=-=-=
Dave Crocker  <dcrocker@brandenburg.com>
Brandenburg Consulting  <www.brandenburg.com>
Tel: +1.408.246.8253,  Fax: +1.408.273.6464
675 Spruce Drive,  Sunnyvale, CA 94086 USA

Gong Xi Fa Cai   /  Selamat Tahun Baru Cina



From owner-ietf-outbound  Wed Feb 16 14:11:00 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA10451
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 14:10:02 -0500 (EST)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10080
	for <ietf@ietf.org>; Wed, 16 Feb 2000 14:00:01 -0500 (EST)
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.0.Beta13/8.10.0.Beta13) with ESMTP id e1GIxp928040;
	Wed, 16 Feb 2000 13:59:51 -0500
Message-Id: <200002161859.e1GIxp928040@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Paul Hoffman / IMC <phoffman@IMC.ORG>
cc: ietf@ietf.org
Subject: Re: Question re: an Internet-Draft and testing/deployment 
In-reply-to: Your message of "Wed, 16 Feb 2000 09:57:45 PST."
             <4.2.1.20000216095346.00bba480@mail.imc.org> 
From: Valdis.Kletnieks@vt.edu
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <4.2.1.20000216095346.00bba480@mail.imc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 16 Feb 2000 13:59:51 -0500
X-Loop: ietf@ietf.org

On Wed, 16 Feb 2000 09:57:45 PST, Paul Hoffman / IMC <phoffman@imc.org>  said:
> The note shouldn't be needed, given the definition of an Internet Draft, 
> but it appears that many folks have forgotten that definition.

Ahh.. <enlightment occurs>.  I was reading it as being even *more*
cautionary than the usual paranoia that should be created just from
its I-D status.  If the intent was just to remind people "Hey, it's
just an I-D, don't do this unless you're testing it", that's another
story.

/Valdis



From owner-ietf-outbound@ietf.org  Wed Feb 16 14:18:09 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10741
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Feb 2000 14:18:09 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA00306;
	Wed, 16 Feb 2000 14:16:05 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id OAA10451
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 14:10:02 -0500 (EST)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10080
	for <ietf@ietf.org>; Wed, 16 Feb 2000 14:00:01 -0500 (EST)
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.0.Beta13/8.10.0.Beta13) with ESMTP id e1GIxp928040;
	Wed, 16 Feb 2000 13:59:51 -0500
Message-Id: <200002161859.e1GIxp928040@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Paul Hoffman / IMC <phoffman@IMC.ORG>
cc: ietf@ietf.org
Subject: Re: Question re: an Internet-Draft and testing/deployment 
In-reply-to: Your message of "Wed, 16 Feb 2000 09:57:45 PST."
             <4.2.1.20000216095346.00bba480@mail.imc.org> 
From: Valdis.Kletnieks@vt.edu
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <4.2.1.20000216095346.00bba480@mail.imc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 16 Feb 2000 13:59:51 -0500
X-Loop: ietf@ietf.org

On Wed, 16 Feb 2000 09:57:45 PST, Paul Hoffman / IMC <phoffman@imc.org>  said:
> The note shouldn't be needed, given the definition of an Internet Draft, 
> but it appears that many folks have forgotten that definition.

Ahh.. <enlightment occurs>.  I was reading it as being even *more*
cautionary than the usual paranoia that should be created just from
its I-D status.  If the intent was just to remind people "Hey, it's
just an I-D, don't do this unless you're testing it", that's another
story.

/Valdis



From owner-ietf-outbound  Wed Feb 16 15:12:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA12041
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 15:10:02 -0500 (EST)
Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11847
	for <ietf@ietf.org>; Wed, 16 Feb 2000 15:00:12 -0500 (EST)
Received: from hermes.research.att.com (hermes.research.att.com [135.207.16.38])
	by mail-green.research.att.com (Postfix) with ESMTP
	id 0FC0D1E002; Wed, 16 Feb 2000 15:00:02 -0500 (EST)
Received: from SIGABA.research.att.com (sigaba.research.att.com [135.207.23.169])
	by hermes.research.att.com (8.8.7/8.8.7) with ESMTP id PAA19256;
	Wed, 16 Feb 2000 15:00:45 -0500 (EST)
Received: by SIGABA.research.att.com (Postfix, from userid 54047)
	id F186C41F16; Wed, 16 Feb 2000 15:00:00 -0500 (EST)
Received: from roc (localhost [127.0.0.1])
	by SIGABA.research.att.com (Postfix) with ESMTP
	id E48AF400B5; Wed, 16 Feb 2000 14:59:55 -0500 (EST)
X-Mailer: exmh version 2.1.1 10/15/1999
From: "Steven M. Bellovin" <smb@research.att.com>
To: Stephen Kent <kent@bbn.com>
Cc: ietf@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 16 Feb 2000 14:59:55 -0500
Sender: smb@research.att.com
Message-Id: <20000216200000.F186C41F16@SIGABA.research.att.com>
X-Loop: ietf@ietf.org

In message <v0422080cb4d099a84d13@[171.78.30.107]>, Stephen Kent writes:
> Steve,
> 
> The AT&T experiences might be different, but at GTE-I, a SYN flood 
> was the primary attack mechanism for one major web site that we host. 
> Also, it is not at all clear that our network had a problem handling 
> the other flooded traffic (ICMP Echo Reply and UDP traffic) that was 
> sent to 3 other targets on our net, but the web hosts that were 
> targets certainly did suffer from processing the traffic.

Right.  Yahoo, though, was flooded mostly by the volume.  I worry about 
high-volume TCP garbage sent to port 80, which you can't filter.
> 
> Steve
> 
> P.S.  Nice photo and quotes in Newsweek!
> 
Thanks.

		--Steve Bellovin




From owner-ietf-outbound@ietf.org  Wed Feb 16 15:24:19 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12470
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Feb 2000 15:24:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA02265;
	Wed, 16 Feb 2000 15:22:15 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id PAA12041
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 15:10:02 -0500 (EST)
Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11847
	for <ietf@ietf.org>; Wed, 16 Feb 2000 15:00:12 -0500 (EST)
Received: from hermes.research.att.com (hermes.research.att.com [135.207.16.38])
	by mail-green.research.att.com (Postfix) with ESMTP
	id 0FC0D1E002; Wed, 16 Feb 2000 15:00:02 -0500 (EST)
Received: from SIGABA.research.att.com (sigaba.research.att.com [135.207.23.169])
	by hermes.research.att.com (8.8.7/8.8.7) with ESMTP id PAA19256;
	Wed, 16 Feb 2000 15:00:45 -0500 (EST)
Received: by SIGABA.research.att.com (Postfix, from userid 54047)
	id F186C41F16; Wed, 16 Feb 2000 15:00:00 -0500 (EST)
Received: from roc (localhost [127.0.0.1])
	by SIGABA.research.att.com (Postfix) with ESMTP
	id E48AF400B5; Wed, 16 Feb 2000 14:59:55 -0500 (EST)
X-Mailer: exmh version 2.1.1 10/15/1999
From: "Steven M. Bellovin" <smb@research.att.com>
To: Stephen Kent <kent@bbn.com>
Cc: ietf@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 16 Feb 2000 14:59:55 -0500
Sender: smb@research.att.com
Message-Id: <20000216200000.F186C41F16@SIGABA.research.att.com>
X-Loop: ietf@ietf.org

In message <v0422080cb4d099a84d13@[171.78.30.107]>, Stephen Kent writes:
> Steve,
> 
> The AT&T experiences might be different, but at GTE-I, a SYN flood 
> was the primary attack mechanism for one major web site that we host. 
> Also, it is not at all clear that our network had a problem handling 
> the other flooded traffic (ICMP Echo Reply and UDP traffic) that was 
> sent to 3 other targets on our net, but the web hosts that were 
> targets certainly did suffer from processing the traffic.

Right.  Yahoo, though, was flooded mostly by the volume.  I worry about 
high-volume TCP garbage sent to port 80, which you can't filter.
> 
> Steve
> 
> P.S.  Nice photo and quotes in Newsweek!
> 
Thanks.

		--Steve Bellovin




From owner-ietf-outbound  Wed Feb 16 15:20:54 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA12356
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 15:20:02 -0500 (EST)
Received: from mailer1.lut.ac.uk (mailer1.lut.ac.uk [158.125.1.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12079
	for <ietf@ietf.org>; Wed, 16 Feb 2000 15:11:04 -0500 (EST)
Received: from jon (helo=localhost)
	by mailer1.lut.ac.uk with local-smtp (Exim 2.10 #1)
	id 12LAmZ-0006Uy-00; Wed, 16 Feb 2000 20:10:43 +0000
Date: Wed, 16 Feb 2000 20:10:43 +0000 (GMT)
From: Jon Knight <J.P.Knight@lboro.ac.uk>
X-Sender: jon@mailer1
To: Rick H Wesson <wessorh@ar.com>
cc: ietf@ietf.org
Subject: Re: Common Indexing Protocol (CIP)
In-Reply-To: <Pine.LNX.4.10.10002151313550.1108-100000@loki.ar.com>
Message-ID: <Pine.SOL.3.96.1000216201027.12017Q-100000@mailer1>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Tue, 15 Feb 2000, Rick H Wesson wrote:
> does anyone know of any implementations of CIP? 

ROADS <URL:http://www.roads.lut.ac.uk/>.

Tatty bye,

Jim'll



From owner-ietf-outbound@ietf.org  Wed Feb 16 15:27:44 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12573
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Feb 2000 15:27:44 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA02328;
	Wed, 16 Feb 2000 15:25:40 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id PAA12356
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 15:20:02 -0500 (EST)
Received: from mailer1.lut.ac.uk (mailer1.lut.ac.uk [158.125.1.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12079
	for <ietf@ietf.org>; Wed, 16 Feb 2000 15:11:04 -0500 (EST)
Received: from jon (helo=localhost)
	by mailer1.lut.ac.uk with local-smtp (Exim 2.10 #1)
	id 12LAmZ-0006Uy-00; Wed, 16 Feb 2000 20:10:43 +0000
Date: Wed, 16 Feb 2000 20:10:43 +0000 (GMT)
From: Jon Knight <J.P.Knight@lboro.ac.uk>
X-Sender: jon@mailer1
To: Rick H Wesson <wessorh@ar.com>
cc: ietf@ietf.org
Subject: Re: Common Indexing Protocol (CIP)
In-Reply-To: <Pine.LNX.4.10.10002151313550.1108-100000@loki.ar.com>
Message-ID: <Pine.SOL.3.96.1000216201027.12017Q-100000@mailer1>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Tue, 15 Feb 2000, Rick H Wesson wrote:
> does anyone know of any implementations of CIP? 

ROADS <URL:http://www.roads.lut.ac.uk/>.

Tatty bye,

Jim'll



From owner-ietf-outbound  Wed Feb 16 15:31:00 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA12618
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 15:30:02 -0500 (EST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12090
	for <ietf@ietf.org>; Wed, 16 Feb 2000 15:11:33 -0500 (EST)
Received: from zed.isi.edu (zed-e.isi.edu [128.9.160.57])
	by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id MAA16549;
	Wed, 16 Feb 2000 12:11:20 -0800 (PST)
From: Bill Manning <bmanning@ISI.EDU>
Received: (from bmanning@localhost)
	by zed.isi.edu (8.8.7/8.8.6) id MAA09042;
	Wed, 16 Feb 2000 12:11:08 -0800 (PST)
Message-Id: <200002162011.MAA09042@zed.isi.edu>
Subject: Re: Question re: an Internet-Draft and testing/deployment
To: dcrocker@brandenburg.com (Dave Crocker)
Date: Wed, 16 Feb 2000 12:11:07 -0800 (PST)
Cc: bmanning@ISI.EDU (Bill Manning), Valdis.Kletnieks@vt.edu, ietf@ietf.org
In-Reply-To: <4.3.0.39.0.20000216104119.00b944d0@mail.bayarea.net> from "Dave Crocker" at Feb 16, 2000 10:42:28 AM
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

% At 09:03 AM 2/16/2000 -0800, Bill Manning wrote:
% >I hope not, This will be the first IETF where this WG meets. This is -one-
% >of several methods being discussed. We haven't even reached closure on
% >the appropriate scope. This draft is an attempt to walk one vector of
% >the problem space.
% 
% Not just "discussed".  Tin Tan Wee has been working on this publicly for a 
% couple of years and now has a well-supported, fully operational service.
% 
% Dave Crocker  <dcrocker@brandenburg.com>

	I am very aware of the APNG work on iDNS. However within the
	context of the IETF and the IDN wg, there remain a number of
	methods under discussion, including Tin Tan Wee's work. 

-- 
--bill



From owner-ietf-outbound@ietf.org  Wed Feb 16 15:37:12 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12905
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Feb 2000 15:37:11 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA02683;
	Wed, 16 Feb 2000 15:35:08 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id PAA12618
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 15:30:02 -0500 (EST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12090
	for <ietf@ietf.org>; Wed, 16 Feb 2000 15:11:33 -0500 (EST)
Received: from zed.isi.edu (zed-e.isi.edu [128.9.160.57])
	by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id MAA16549;
	Wed, 16 Feb 2000 12:11:20 -0800 (PST)
From: Bill Manning <bmanning@ISI.EDU>
Received: (from bmanning@localhost)
	by zed.isi.edu (8.8.7/8.8.6) id MAA09042;
	Wed, 16 Feb 2000 12:11:08 -0800 (PST)
Message-Id: <200002162011.MAA09042@zed.isi.edu>
Subject: Re: Question re: an Internet-Draft and testing/deployment
To: dcrocker@brandenburg.com (Dave Crocker)
Date: Wed, 16 Feb 2000 12:11:07 -0800 (PST)
Cc: bmanning@ISI.EDU (Bill Manning), Valdis.Kletnieks@vt.edu, ietf@ietf.org
In-Reply-To: <4.3.0.39.0.20000216104119.00b944d0@mail.bayarea.net> from "Dave Crocker" at Feb 16, 2000 10:42:28 AM
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

% At 09:03 AM 2/16/2000 -0800, Bill Manning wrote:
% >I hope not, This will be the first IETF where this WG meets. This is -one-
% >of several methods being discussed. We haven't even reached closure on
% >the appropriate scope. This draft is an attempt to walk one vector of
% >the problem space.
% 
% Not just "discussed".  Tin Tan Wee has been working on this publicly for a 
% couple of years and now has a well-supported, fully operational service.
% 
% Dave Crocker  <dcrocker@brandenburg.com>

	I am very aware of the APNG work on iDNS. However within the
	context of the IETF and the IDN wg, there remain a number of
	methods under discussion, including Tin Tan Wee's work. 

-- 
--bill



From owner-ietf-outbound  Wed Feb 16 16:22:49 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA14183
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 16:20:02 -0500 (EST)
Received: from po1.bbn.com (PO1.BBN.COM [192.1.50.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14090
	for <ietf@ietf.org>; Wed, 16 Feb 2000 16:16:28 -0500 (EST)
Received: from [171.78.30.107] (comsec.bbn.com [171.78.30.107])
	by po1.bbn.com (8.9.1/8.9.1) with ESMTP id QAA12783;
	Wed, 16 Feb 2000 16:16:12 -0500 (EST)
Mime-Version: 1.0
X-Sender: kent@po1.bbn.com
Message-Id: <v04220813b4d0c122939d@[171.78.30.107]>
In-Reply-To: <38AADC73.A638874D@senie.com>
References: <016401bf7763$4b82e380$0300000a@cisco.com>
 <v04220802b4d078236d2c@[171.78.30.107]> <38AADC73.A638874D@senie.com>
Date: Wed, 16 Feb 2000 16:16:43 -0500
To: Daniel Senie <dts@senie.com>
From: Stephen Kent <kent@bbn.com>
Subject: Re: Internet SYN Flooding, spoofing attacks
Cc: ietf@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

Dan,

I'll suggest one course of action, but I keep emphasizing the issue 
is not one of alternates, but of recognizing the limitations of 
proposals now on the table and considering approaches that may work 
irrespective of whether everyone performs filtering.

With regard to a wide range of DoS or DDoS attacks, it seems quite 
feasible to monitor traffic to the web site to detect such attacks 
irrespective of whether source addresses are spoofed or not.  (this 
differs from IDS for broader attacks, where the recognition problem 
is much harder and the false negative rate is on the order of 20%.) 
Such monitoring can be done by a web hosting facility through purely 
passive monitoring, so as not to adversely affect the performance of 
the network used by a web hosting site.  Once an attack is detected, 
one can trigger a semi-automated response.  If one believes that the 
source addresses are not spoofed, then one can use this to direct 
filtering to selected ingress points, but the filtering can now be 
very focused, based o the characteristics of the detected DoS 
traffic. If one believes that source addressed might be spoofed, then 
one needs to activate the selective filtering on a much wider range 
of ingress points.  Since the true sources may be outside of the 
ISP's sphere of control, filtering at connections to other ISPs may 
be required in either case.

If the response is rapid enough, the attack may not have significant 
impact, which reduces the attraction of mounting such an attack in 
the first place.  One can begin disabling the filters once the 
offending traffic flows have diminished, which provides another means 
of determining the sources of traffic, as others have noted in 
previous published work on this topic.

An advantage of this style of approach is that while it can be even 
more effective if source address filtering is widespread, it also 
would work if such filtering is not completely effective, which is 
the sort of self-defense approach I prefer  It supports what the 
security community refers to as the Principle of Least Privilege.

Steve



From owner-ietf-outbound@ietf.org  Wed Feb 16 16:31:14 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14484
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Feb 2000 16:31:14 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA04052;
	Wed, 16 Feb 2000 16:29:09 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id QAA14183
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 16:20:02 -0500 (EST)
Received: from po1.bbn.com (PO1.BBN.COM [192.1.50.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14090
	for <ietf@ietf.org>; Wed, 16 Feb 2000 16:16:28 -0500 (EST)
Received: from [171.78.30.107] (comsec.bbn.com [171.78.30.107])
	by po1.bbn.com (8.9.1/8.9.1) with ESMTP id QAA12783;
	Wed, 16 Feb 2000 16:16:12 -0500 (EST)
Mime-Version: 1.0
X-Sender: kent@po1.bbn.com
Message-Id: <v04220813b4d0c122939d@[171.78.30.107]>
In-Reply-To: <38AADC73.A638874D@senie.com>
References: <016401bf7763$4b82e380$0300000a@cisco.com>
 <v04220802b4d078236d2c@[171.78.30.107]> <38AADC73.A638874D@senie.com>
Date: Wed, 16 Feb 2000 16:16:43 -0500
To: Daniel Senie <dts@senie.com>
From: Stephen Kent <kent@bbn.com>
Subject: Re: Internet SYN Flooding, spoofing attacks
Cc: ietf@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Loop: ietf@ietf.org

Dan,

I'll suggest one course of action, but I keep emphasizing the issue 
is not one of alternates, but of recognizing the limitations of 
proposals now on the table and considering approaches that may work 
irrespective of whether everyone performs filtering.

With regard to a wide range of DoS or DDoS attacks, it seems quite 
feasible to monitor traffic to the web site to detect such attacks 
irrespective of whether source addresses are spoofed or not.  (this 
differs from IDS for broader attacks, where the recognition problem 
is much harder and the false negative rate is on the order of 20%.) 
Such monitoring can be done by a web hosting facility through purely 
passive monitoring, so as not to adversely affect the performance of 
the network used by a web hosting site.  Once an attack is detected, 
one can trigger a semi-automated response.  If one believes that the 
source addresses are not spoofed, then one can use this to direct 
filtering to selected ingress points, but the filtering can now be 
very focused, based o the characteristics of the detected DoS 
traffic. If one believes that source addressed might be spoofed, then 
one needs to activate the selective filtering on a much wider range 
of ingress points.  Since the true sources may be outside of the 
ISP's sphere of control, filtering at connections to other ISPs may 
be required in either case.

If the response is rapid enough, the attack may not have significant 
impact, which reduces the attraction of mounting such an attack in 
the first place.  One can begin disabling the filters once the 
offending traffic flows have diminished, which provides another means 
of determining the sources of traffic, as others have noted in 
previous published work on this topic.

An advantage of this style of approach is that while it can be even 
more effective if source address filtering is widespread, it also 
would work if such filtering is not completely effective, which is 
the sort of self-defense approach I prefer  It supports what the 
security community refers to as the Principle of Least Privilege.

Steve



From owner-ietf-outbound  Wed Feb 16 16:51:10 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA15584
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 16:50:03 -0500 (EST)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15409
	for <ietf@ietf.org>; Wed, 16 Feb 2000 16:46:09 -0500 (EST)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id QAA14151;
        Wed, 16 Feb 2000 16:45:08 -0500 (EST)
Message-Id: <200002162145.QAA14151@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Dave Crocker <dcrocker@brandenburg.com>
cc: Bill Manning <bmanning@ISI.EDU>, Valdis.Kletnieks@VT.EDU, ietf@ietf.org
Subject: Re: Question re: an Internet-Draft and testing/deployment 
In-reply-to: Your message of "Wed, 16 Feb 2000 10:42:28 PST."
             <4.3.0.39.0.20000216104119.00b944d0@mail.bayarea.net> 
Date: Wed, 16 Feb 2000 16:45:08 -0500
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> Not just "discussed".  Tin Tan Wee has been working on this publicly for a 
> couple of years and now has a well-supported, fully operational service.

which doesn't even begin to address a large number of problems.

anyone who believes they have running code for iDNS is deluding themselves.

Keith



From owner-ietf-outbound@ietf.org  Wed Feb 16 16:58:05 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15937
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Feb 2000 16:58:04 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA04966;
	Wed, 16 Feb 2000 16:56:01 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id QAA15584
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 16:50:03 -0500 (EST)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15409
	for <ietf@ietf.org>; Wed, 16 Feb 2000 16:46:09 -0500 (EST)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id QAA14151;
        Wed, 16 Feb 2000 16:45:08 -0500 (EST)
Message-Id: <200002162145.QAA14151@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Dave Crocker <dcrocker@brandenburg.com>
cc: Bill Manning <bmanning@ISI.EDU>, Valdis.Kletnieks@VT.EDU, ietf@ietf.org
Subject: Re: Question re: an Internet-Draft and testing/deployment 
In-reply-to: Your message of "Wed, 16 Feb 2000 10:42:28 PST."
             <4.3.0.39.0.20000216104119.00b944d0@mail.bayarea.net> 
Date: Wed, 16 Feb 2000 16:45:08 -0500
Sender: moore@cs.utk.edu
X-Loop: ietf@ietf.org

> Not just "discussed".  Tin Tan Wee has been working on this publicly for a 
> couple of years and now has a well-supported, fully operational service.

which doesn't even begin to address a large number of problems.

anyone who believes they have running code for iDNS is deluding themselves.

Keith



From owner-ietf-outbound  Wed Feb 16 17:01:28 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA15980
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 17:00:02 -0500 (EST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15642
	for <ietf@ietf.org>; Wed, 16 Feb 2000 16:51:07 -0500 (EST)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200002162148.GAA24943@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id GAA24943; Thu, 17 Feb 2000 06:48:39 +0900
Subject: Re: Question re: an Internet-Draft and testing/deployment
To: dcrocker@brandenburg.com (Dave Crocker)
Date: Thu, 17 Feb 0 6:48:38 JST
Cc: bmanning@ISI.EDU, Valdis.Kletnieks@VT.EDU, ietf@ietf.org
In-Reply-To: <4.3.0.39.0.20000216104119.00b944d0@mail.bayarea.net>; from "Dave Crocker" at Feb 17, 100 5:22 am
X-Mailer: ELM [version 2.3 PL11]
X-Loop: ietf@ietf.org

Dave;

> >I hope not, This will be the first IETF where this WG meets. This is -one-
> >of several methods being discussed. We haven't even reached closure on
> >the appropriate scope. This draft is an attempt to walk one vector of
> >the problem space.
> 
> Not just "discussed".  Tin Tan Wee has been working on this publicly for a 
> couple of years and now has a well-supported, fully operational service.

The problem is that the problem to be solved (or discussed) is not
well defined.

You can still have well-supported, fully operational, but, purposeless
services.

							Masataka Ohta



From owner-ietf-outbound@ietf.org  Wed Feb 16 17:07:59 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16245
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Feb 2000 17:07:59 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA05440;
	Wed, 16 Feb 2000 17:05:52 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id RAA15980
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 17:00:02 -0500 (EST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15642
	for <ietf@ietf.org>; Wed, 16 Feb 2000 16:51:07 -0500 (EST)
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <200002162148.GAA24943@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1)
	id GAA24943; Thu, 17 Feb 2000 06:48:39 +0900
Subject: Re: Question re: an Internet-Draft and testing/deployment
To: dcrocker@brandenburg.com (Dave Crocker)
Date: Thu, 17 Feb 0 6:48:38 JST
Cc: bmanning@ISI.EDU, Valdis.Kletnieks@VT.EDU, ietf@ietf.org
In-Reply-To: <4.3.0.39.0.20000216104119.00b944d0@mail.bayarea.net>; from "Dave Crocker" at Feb 17, 100 5:22 am
X-Mailer: ELM [version 2.3 PL11]
X-Loop: ietf@ietf.org

Dave;

> >I hope not, This will be the first IETF where this WG meets. This is -one-
> >of several methods being discussed. We haven't even reached closure on
> >the appropriate scope. This draft is an attempt to walk one vector of
> >the problem space.
> 
> Not just "discussed".  Tin Tan Wee has been working on this publicly for a 
> couple of years and now has a well-supported, fully operational service.

The problem is that the problem to be solved (or discussed) is not
well defined.

You can still have well-supported, fully operational, but, purposeless
services.

							Masataka Ohta



From owner-ietf-outbound  Wed Feb 16 21:12:41 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA19895
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 21:10:02 -0500 (EST)
Received: from homer.ka9q.ampr.org (dt039nf6.san.rr.com [24.30.144.246])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19851
	for <IETF@ietf.org>; Wed, 16 Feb 2000 21:03:14 -0500 (EST)
Received: (from karn@localhost)
	by homer.ka9q.ampr.org (8.9.3/8.9.3/Debian/GNU) id SAA06407;
	Wed, 16 Feb 2000 18:02:38 -0800
Date: Wed, 16 Feb 2000 18:02:38 -0800
Message-Id: <200002170202.SAA06407@homer.ka9q.ampr.org>
From: Phil Karn <karn@ka9q.ampr.org>
To: dts@senie.com
CC: lists.anders@feder.dk, IETF@ietf.org
In-reply-to: <38A8C268.33BAF536@senie.com> (message from Daniel Senie on Mon,
	14 Feb 2000 22:05:12 -0500)
Subject: Re: Internet SYN Flooding, spoofing attacks
Reply-to: karn@qualcomm.com
References: <200002150004.QAA04489@servo.qualcomm.com> <38A8C268.33BAF536@senie.com>
X-Loop: ietf@ietf.org

>Yes, and you chose the CORRECT solution. Think about it... VPN in most
>cases also means encryption, and at that probably back to a central
>site.

Yes, I often use encryption, but not to a central site. Generally I
apply it at the application layer (SSH/SSL) so the peer is whoever I happen
to be talking to. However, this is irrelevant to the issue of upstream
IP address filtering.

>Sorry. You're at the point where technology meets policy. Fact is, your
>host identifier in the IP stack is the source IP address. Enforcing the
>validity of that identifier has become necessary.

This makes no sense at all. I've shown both that there are legitimate
reasons to send packets that the ISP might consider "alien", and also
how easy it is to circumvent ingress filtering if you are so motivated.

By the way, ingress filtering breaks things other than Mobile IP.
Consider the DirecPC service, which gives you a one-way (forward)
satellite channel at 400 kb/s. Your return link is via local dialup
service provider. If the local ISP (or its upstream provider) does
source filtering, you can't send your perfectly legitimate packets
into the network over that ISP without tunneling them all through
DirecPC's own network connection, which may be on the other side of
the continent.

>The case for "legitimate use" of source spoofing has not been
>sufficiently made. Operational reality is such that it's not
>sustainable.

The operational reality is that you'll never be able to implement
ingress filtering widely enough to provide much of a benefit. Even if
you do, it'll be circumventable (consider the many Linux and Unix
boxes out there that support IP-in-IP tunneling). And the energy you
spend doing so will be energy that could have been better spent
implementing other mechanisms to defend the Internet against MS-DOS
(multiple source denial of service) attacks.

Phil



From owner-ietf-outbound@ietf.org  Wed Feb 16 21:17:56 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19968
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Feb 2000 21:17:55 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA13489;
	Wed, 16 Feb 2000 21:15:51 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id VAA19895
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 21:10:02 -0500 (EST)
Received: from homer.ka9q.ampr.org (dt039nf6.san.rr.com [24.30.144.246])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19851
	for <IETF@ietf.org>; Wed, 16 Feb 2000 21:03:14 -0500 (EST)
Received: (from karn@localhost)
	by homer.ka9q.ampr.org (8.9.3/8.9.3/Debian/GNU) id SAA06407;
	Wed, 16 Feb 2000 18:02:38 -0800
Date: Wed, 16 Feb 2000 18:02:38 -0800
Message-Id: <200002170202.SAA06407@homer.ka9q.ampr.org>
From: Phil Karn <karn@ka9q.ampr.org>
To: dts@senie.com
CC: lists.anders@feder.dk, IETF@ietf.org
In-reply-to: <38A8C268.33BAF536@senie.com> (message from Daniel Senie on Mon,
	14 Feb 2000 22:05:12 -0500)
Subject: Re: Internet SYN Flooding, spoofing attacks
Reply-to: karn@qualcomm.com
References: <200002150004.QAA04489@servo.qualcomm.com> <38A8C268.33BAF536@senie.com>
X-Loop: ietf@ietf.org

>Yes, and you chose the CORRECT solution. Think about it... VPN in most
>cases also means encryption, and at that probably back to a central
>site.

Yes, I often use encryption, but not to a central site. Generally I
apply it at the application layer (SSH/SSL) so the peer is whoever I happen
to be talking to. However, this is irrelevant to the issue of upstream
IP address filtering.

>Sorry. You're at the point where technology meets policy. Fact is, your
>host identifier in the IP stack is the source IP address. Enforcing the
>validity of that identifier has become necessary.

This makes no sense at all. I've shown both that there are legitimate
reasons to send packets that the ISP might consider "alien", and also
how easy it is to circumvent ingress filtering if you are so motivated.

By the way, ingress filtering breaks things other than Mobile IP.
Consider the DirecPC service, which gives you a one-way (forward)
satellite channel at 400 kb/s. Your return link is via local dialup
service provider. If the local ISP (or its upstream provider) does
source filtering, you can't send your perfectly legitimate packets
into the network over that ISP without tunneling them all through
DirecPC's own network connection, which may be on the other side of
the continent.

>The case for "legitimate use" of source spoofing has not been
>sufficiently made. Operational reality is such that it's not
>sustainable.

The operational reality is that you'll never be able to implement
ingress filtering widely enough to provide much of a benefit. Even if
you do, it'll be circumventable (consider the many Linux and Unix
boxes out there that support IP-in-IP tunneling). And the energy you
spend doing so will be energy that could have been better spent
implementing other mechanisms to defend the Internet against MS-DOS
(multiple source denial of service) attacks.

Phil



From owner-ietf-outbound  Wed Feb 16 21:30:24 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA20115
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 21:30:03 -0500 (EST)
Received: from homer.ka9q.ampr.org (dt039nf6.san.rr.com [24.30.144.246])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20002
	for <IETF@ietf.org>; Wed, 16 Feb 2000 21:20:47 -0500 (EST)
Received: (from karn@localhost)
	by homer.ka9q.ampr.org (8.9.3/8.9.3/Debian/GNU) id SAA06416;
	Wed, 16 Feb 2000 18:20:43 -0800
Date: Wed, 16 Feb 2000 18:20:43 -0800
Message-Id: <200002170220.SAA06416@homer.ka9q.ampr.org>
From: Phil Karn <karn@ka9q.ampr.org>
To: jhawk@bbnplanet.com
CC: dts@senie.com, IETF@ietf.org
In-reply-to: <20000215101728.R19709@jhawk-foo.bbnplanet.com> (message from
	John Hawkinson on Tue, 15 Feb 2000 10:17:28 -0500)
Subject: Re: Internet SYN Flooding, spoofing attacks
Reply-to: karn@qualcomm.com
References: <200002150004.QAA04489@servo.qualcomm.com> <38A8C268.33BAF536@senie.com> <20000215101728.R19709@jhawk-foo.bbnplanet.com>
X-Loop: ietf@ietf.org

>I think we recognize this may be politically infeasable for many
>people to do, because tunneling is often used to circumvent
>administrative restrictions, but that really is a different degree of
>the problem.

Bingo. I tunnel because my cable modem provider requires residential
users to use DHCP to get IP addresses that can change at any time.  If
you want a static IP address, or additional IP addresses, you must pay
a considerable premium.

It's not because fixed addresses actually cost them more. Indeed,
another cable modem provider in the other part of town allocates fixed
addresses in an otherwise identical service that's $5/mo cheaper. No,
my provider does it simply because they can. They're a monopoly in
their service area.  Even if I could find somebody at their help desk
who understood a request to open up their filter to my own IP addresses,
they would have no incentive to do so.

This all boils down to a basic issue of who controls the Internet
address space -- the users, or the monopolies who have long controlled
the Internet's underlying transmission media and who are now moving up
the stack to aggressively control the IP layer and are imposing
restrictions on the content of their user's traffic.

Fortunately, secure tunneling protocols will always make it possible
for knowledgeable users to overcome these administrative restrictions
and to keep the carriers down at the physical level where they belong,
albeit with a loss in efficiency.

The question, then, is not whether users will be able to send packets
with arbitrary source addresses. They will. The question is whether we
get rid of the inefficiencies associated with a failed attempt to keep
them from doing so, and redirect our energies to better alternatives
for dealing with denial of service attacks.

Phil



From owner-ietf-outbound@ietf.org  Wed Feb 16 21:32:16 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20229
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Feb 2000 21:32:16 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA13940;
	Wed, 16 Feb 2000 21:30:12 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id VAA20115
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 21:30:03 -0500 (EST)
Received: from homer.ka9q.ampr.org (dt039nf6.san.rr.com [24.30.144.246])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20002
	for <IETF@ietf.org>; Wed, 16 Feb 2000 21:20:47 -0500 (EST)
Received: (from karn@localhost)
	by homer.ka9q.ampr.org (8.9.3/8.9.3/Debian/GNU) id SAA06416;
	Wed, 16 Feb 2000 18:20:43 -0800
Date: Wed, 16 Feb 2000 18:20:43 -0800
Message-Id: <200002170220.SAA06416@homer.ka9q.ampr.org>
From: Phil Karn <karn@ka9q.ampr.org>
To: jhawk@bbnplanet.com
CC: dts@senie.com, IETF@ietf.org
In-reply-to: <20000215101728.R19709@jhawk-foo.bbnplanet.com> (message from
	John Hawkinson on Tue, 15 Feb 2000 10:17:28 -0500)
Subject: Re: Internet SYN Flooding, spoofing attacks
Reply-to: karn@qualcomm.com
References: <200002150004.QAA04489@servo.qualcomm.com> <38A8C268.33BAF536@senie.com> <20000215101728.R19709@jhawk-foo.bbnplanet.com>
X-Loop: ietf@ietf.org

>I think we recognize this may be politically infeasable for many
>people to do, because tunneling is often used to circumvent
>administrative restrictions, but that really is a different degree of
>the problem.

Bingo. I tunnel because my cable modem provider requires residential
users to use DHCP to get IP addresses that can change at any time.  If
you want a static IP address, or additional IP addresses, you must pay
a considerable premium.

It's not because fixed addresses actually cost them more. Indeed,
another cable modem provider in the other part of town allocates fixed
addresses in an otherwise identical service that's $5/mo cheaper. No,
my provider does it simply because they can. They're a monopoly in
their service area.  Even if I could find somebody at their help desk
who understood a request to open up their filter to my own IP addresses,
they would have no incentive to do so.

This all boils down to a basic issue of who controls the Internet
address space -- the users, or the monopolies who have long controlled
the Internet's underlying transmission media and who are now moving up
the stack to aggressively control the IP layer and are imposing
restrictions on the content of their user's traffic.

Fortunately, secure tunneling protocols will always make it possible
for knowledgeable users to overcome these administrative restrictions
and to keep the carriers down at the physical level where they belong,
albeit with a loss in efficiency.

The question, then, is not whether users will be able to send packets
with arbitrary source addresses. They will. The question is whether we
get rid of the inefficiencies associated with a failed attempt to keep
them from doing so, and redirect our energies to better alternatives
for dealing with denial of service attacks.

Phil



From owner-ietf-outbound  Wed Feb 16 23:10:43 2000
Received: by ietf.org (8.9.1a/8.9.1a) id XAA22911
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 23:10:01 -0500 (EST)
Received: from munnari.OZ.AU (munnari.OZ.AU [128.250.1.21])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA22750
	for <IETF@ietf.org>; Wed, 16 Feb 2000 23:00:05 -0500 (EST)
Received: from mundamutti.cs.mu.OZ.AU ([128.250.1.5])
	by munnari.OZ.AU with SMTP (5.83--+1.3.1+0.59) id DA03795;
	Thu, 17 Feb 2000 14:59:59 +1100 (from kre@munnari.OZ.AU)
From: Robert Elz <kre@munnari.OZ.AU>
To: karn@qualcomm.com
Cc: IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks 
In-Reply-To: Your message of "Wed, 16 Feb 2000 18:20:43 -0800."
             <200002170220.SAA06416@homer.ka9q.ampr.org> 
Date: Thu, 17 Feb 2000 14:59:59 +1100
Message-Id: <12304.950759999@munnari.OZ.AU>
Sender: kre@munnari.OZ.AU
X-Loop: ietf@ietf.org

    Date:        Wed, 16 Feb 2000 18:20:43 -0800
    From:        Phil Karn <karn@ka9q.ampr.org>
    Message-ID:  <200002170220.SAA06416@homer.ka9q.ampr.org>

  | Even if I could find somebody at their help desk
  | who understood a request to open up their filter to my own IP addresses,
  | they would have no incentive to do so.

In an earlier message you just told us that ingress filtering would
never become widespread enough to really matter - but it seems to
have managed to trap you...

  | This all boils down to a basic issue of who controls the Internet
  | address space -- the users, or the monopolies who have long controlled

The address space is controlled by the routing system - that's
what the addresses are for.

  | Fortunately, secure tunneling protocols will always make it possible
  | for knowledgeable users to overcome these administrative restrictions
  | and to keep the carriers down at the physical level where they belong,
  | albeit with a loss in efficiency.

Well not always - it is possible to imagine an ISP that only permits
connections via their proxies, and blocks everything else.  They could
even market it as a "premium extra secure internet service - no nasty
packets from outside will ever reach your system" ...

But aside from that nonsense, tunneling is not a problem for ingres
filtering, it isn't defeating it (or not its purpose) at all.
To tunnel, you need a remote tunnel endpoint - and then you can only
send source addresses through the tunnel (and from there to the
universe) with addresses from the remote-endpoint's address range
(assuming ingress filtering is being done there as well).

That's all fine then, you're just acting as if you were a node
at their location (which is the point, more or less), and packets
you send that way are attributed to them, just the same as any
other packet sent from there.

If some site is willing to decapsulate packets from any random source
and forward them, then they take the heat for any packets that are
sent that way.

kre



From owner-ietf-outbound@ietf.org  Wed Feb 16 23:12:15 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23003
	for <ietf-web-archive@odin.ietf.org>; Wed, 16 Feb 2000 23:12:15 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA15815;
	Wed, 16 Feb 2000 23:10:11 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id XAA22911
	for ietf-outbound.10@ietf.org; Wed, 16 Feb 2000 23:10:01 -0500 (EST)
Received: from munnari.OZ.AU (munnari.OZ.AU [128.250.1.21])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA22750
	for <IETF@ietf.org>; Wed, 16 Feb 2000 23:00:05 -0500 (EST)
Received: from mundamutti.cs.mu.OZ.AU ([128.250.1.5])
	by munnari.OZ.AU with SMTP (5.83--+1.3.1+0.59) id DA03795;
	Thu, 17 Feb 2000 14:59:59 +1100 (from kre@munnari.OZ.AU)
From: Robert Elz <kre@munnari.OZ.AU>
To: karn@qualcomm.com
Cc: IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks 
In-Reply-To: Your message of "Wed, 16 Feb 2000 18:20:43 -0800."
             <200002170220.SAA06416@homer.ka9q.ampr.org> 
Date: Thu, 17 Feb 2000 14:59:59 +1100
Message-Id: <12304.950759999@munnari.OZ.AU>
Sender: kre@munnari.OZ.AU
X-Loop: ietf@ietf.org

    Date:        Wed, 16 Feb 2000 18:20:43 -0800
    From:        Phil Karn <karn@ka9q.ampr.org>
    Message-ID:  <200002170220.SAA06416@homer.ka9q.ampr.org>

  | Even if I could find somebody at their help desk
  | who understood a request to open up their filter to my own IP addresses,
  | they would have no incentive to do so.

In an earlier message you just told us that ingress filtering would
never become widespread enough to really matter - but it seems to
have managed to trap you...

  | This all boils down to a basic issue of who controls the Internet
  | address space -- the users, or the monopolies who have long controlled

The address space is controlled by the routing system - that's
what the addresses are for.

  | Fortunately, secure tunneling protocols will always make it possible
  | for knowledgeable users to overcome these administrative restrictions
  | and to keep the carriers down at the physical level where they belong,
  | albeit with a loss in efficiency.

Well not always - it is possible to imagine an ISP that only permits
connections via their proxies, and blocks everything else.  They could
even market it as a "premium extra secure internet service - no nasty
packets from outside will ever reach your system" ...

But aside from that nonsense, tunneling is not a problem for ingres
filtering, it isn't defeating it (or not its purpose) at all.
To tunnel, you need a remote tunnel endpoint - and then you can only
send source addresses through the tunnel (and from there to the
universe) with addresses from the remote-endpoint's address range
(assuming ingress filtering is being done there as well).

That's all fine then, you're just acting as if you were a node
at their location (which is the point, more or less), and packets
you send that way are attributed to them, just the same as any
other packet sent from there.

If some site is willing to decapsulate packets from any random source
and forward them, then they take the heat for any packets that are
sent that way.

kre



From owner-ietf-outbound  Thu Feb 17 03:41:00 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA07808
	for ietf-outbound.10@ietf.org; Thu, 17 Feb 2000 03:40:02 -0500 (EST)
Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA07729
	for <ietf@ietf.org>; Thu, 17 Feb 2000 03:34:51 -0500 (EST)
Received: from sonic.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.03967-0@bells.cs.ucl.ac.uk>; Thu, 17 Feb 2000 08:34:44 +0000
To: "Steven M. Bellovin" <smb@research.att.com>
cc: Stephen Kent <kent@bbn.com>, ietf@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
In-reply-to: Your message of "Wed, 16 Feb 2000 14:59:55 EST." <20000216200000.F186C41F16@SIGABA.research.att.com>
Date: Thu, 17 Feb 2000 08:34:42 +0000
Message-ID: <2039.950776482@cs.ucl.ac.uk>
From: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
X-Loop: ietf@ietf.org


In message <20000216200000.F186C41F16@SIGABA.research.att.com>, "Steven M. Bell
ovin" typed:

 >>Right.  Yahoo, though, was flooded mostly by the volume.  I worry about 
 >>high-volume TCP garbage sent to port 80, which you can't filter.
 
Steve

so in the case that the server resource is overloaded, but not the
link, what you can do is extend the servers scheduling discipline
(e.g. in dealing with existing connexions at a higher priority than
new ones, and applying filters to new ones based on content/application
level metrics (e.g. popularity indices, which is something many 
web servers have got anyhow), to priortise and starve the bad guys...

if the links/routers near you are also being clobbered, than some form
of "loose unicast RPF source quench" mechanism would be a
semi-automated way that server sites could extend this scheduling back
"towards" the bad guys - the idea is to take a mix of modified
versions of the resource control messages such as 
	icmp source quench
	ECN
	RSVP Reject
etc, and use them to install soft state upstream towarasd the bad guy

this state can either block, or just add a weighted RED higher 
drop probability, or eeven move traffic into a lower class in a
diffserv priority, CBQ, WFQ or other...

- but note unlike intserv/rsvp, this state doesnt have to be in all
hops - just the appropriate border/choke point....so it has lots of
nice scaling properties (its only their for a minority of
addresses/flows/ports, its only in a few places, and only when you
need it) - now if someone spoofs a real source address, this
represrents a problem since you can use this mechanism or something
like it to launch an indirect attack using this ....but there are ways
to block that (including making it mandatory to use ipsec to use this
mechanism...)

anyhow, its basically a sort of BGP policy controllable, interne
friendly scalable automated version of phoning up your ISP
and having them back track through all the further ISPs...

 cheers

   jon



From owner-ietf-outbound@ietf.org  Thu Feb 17 03:42:57 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA07864
	for <ietf-web-archive@odin.ietf.org>; Thu, 17 Feb 2000 03:42:57 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA27727;
	Thu, 17 Feb 2000 03:40:50 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id DAA07808
	for ietf-outbound.10@ietf.org; Thu, 17 Feb 2000 03:40:02 -0500 (EST)
Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA07729
	for <ietf@ietf.org>; Thu, 17 Feb 2000 03:34:51 -0500 (EST)
Received: from sonic.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP 
          id <g.03967-0@bells.cs.ucl.ac.uk>; Thu, 17 Feb 2000 08:34:44 +0000
To: "Steven M. Bellovin" <smb@research.att.com>
cc: Stephen Kent <kent@bbn.com>, ietf@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
In-reply-to: Your message of "Wed, 16 Feb 2000 14:59:55 EST." <20000216200000.F186C41F16@SIGABA.research.att.com>
Date: Thu, 17 Feb 2000 08:34:42 +0000
Message-ID: <2039.950776482@cs.ucl.ac.uk>
From: Jon Crowcroft <J.Crowcroft@CS.UCL.AC.UK>
X-Loop: ietf@ietf.org


In message <20000216200000.F186C41F16@SIGABA.research.att.com>, "Steven M. Bell
ovin" typed:

 >>Right.  Yahoo, though, was flooded mostly by the volume.  I worry about 
 >>high-volume TCP garbage sent to port 80, which you can't filter.
 
Steve

so in the case that the server resource is overloaded, but not the
link, what you can do is extend the servers scheduling discipline
(e.g. in dealing with existing connexions at a higher priority than
new ones, and applying filters to new ones based on content/application
level metrics (e.g. popularity indices, which is something many 
web servers have got anyhow), to priortise and starve the bad guys...

if the links/routers near you are also being clobbered, than some form
of "loose unicast RPF source quench" mechanism would be a
semi-automated way that server sites could extend this scheduling back
"towards" the bad guys - the idea is to take a mix of modified
versions of the resource control messages such as 
	icmp source quench
	ECN
	RSVP Reject
etc, and use them to install soft state upstream towarasd the bad guy

this state can either block, or just add a weighted RED higher 
drop probability, or eeven move traffic into a lower class in a
diffserv priority, CBQ, WFQ or other...

- but note unlike intserv/rsvp, this state doesnt have to be in all
hops - just the appropriate border/choke point....so it has lots of
nice scaling properties (its only their for a minority of
addresses/flows/ports, its only in a few places, and only when you
need it) - now if someone spoofs a real source address, this
represrents a problem since you can use this mechanism or something
like it to launch an indirect attack using this ....but there are ways
to block that (including making it mandatory to use ipsec to use this
mechanism...)

anyhow, its basically a sort of BGP policy controllable, interne
friendly scalable automated version of phoning up your ISP
and having them back track through all the further ISPs...

 cheers

   jon



From owner-ietf-outbound  Thu Feb 17 07:51:02 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA10760
	for ietf-outbound.10@ietf.org; Thu, 17 Feb 2000 07:50:02 -0500 (EST)
Received: from prue.eim.surrey.ac.uk (IDENT:exim@prue.eim.surrey.ac.uk [131.227.76.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10509
	for <IETF@ietf.org>; Thu, 17 Feb 2000 07:43:11 -0500 (EST)
Received: from petra.ee.surrey.ac.uk ([131.227.88.13] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.03 #1)
	id 12LQG4-0000rc-00; Thu, 17 Feb 2000 12:42:12 +0000
Date: Thu, 17 Feb 2000 12:42:04 +0000 (GMT)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-Sender: eep1lw@petra.ee.surrey.ac.uk
Reply-To: L.Wood@eim.surrey.ac.uk
To: karn@qualcomm.com
cc: jhawk@bbnplanet.com, dts@senie.com, IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
In-Reply-To: <200002170220.SAA06416@homer.ka9q.ampr.org>
Message-ID: <Pine.SOL.4.10.10002171240390.14006-100000@petra.ee.surrey.ac.uk>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Wed, 16 Feb 2000, Phil Karn wrote:

> This all boils down to a basic issue of who controls the Internet
> address space -- the users, or the monopolies who have long controlled
> the Internet's underlying transmission media and who are now moving up
> the stack to aggressively control the IP layer and are imposing
> restrictions on the content of their user's traffic.

There is no longer a single Internet address space.

We're going to have to start calling it the InterNAT.

L.

Hey, that means the Internet is InterNATional.

<L.Wood@surrey.ac.uk>PGP<http://www.ee.surrey.ac.uk/Personal/L.Wood/>



From owner-ietf-outbound@ietf.org  Thu Feb 17 07:52:05 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10900
	for <ietf-web-archive@odin.ietf.org>; Thu, 17 Feb 2000 07:52:05 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA03714;
	Thu, 17 Feb 2000 07:50:00 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id HAA10760
	for ietf-outbound.10@ietf.org; Thu, 17 Feb 2000 07:50:02 -0500 (EST)
Received: from prue.eim.surrey.ac.uk (IDENT:exim@prue.eim.surrey.ac.uk [131.227.76.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10509
	for <IETF@ietf.org>; Thu, 17 Feb 2000 07:43:11 -0500 (EST)
Received: from petra.ee.surrey.ac.uk ([131.227.88.13] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.03 #1)
	id 12LQG4-0000rc-00; Thu, 17 Feb 2000 12:42:12 +0000
Date: Thu, 17 Feb 2000 12:42:04 +0000 (GMT)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-Sender: eep1lw@petra.ee.surrey.ac.uk
Reply-To: L.Wood@eim.surrey.ac.uk
To: karn@qualcomm.com
cc: jhawk@bbnplanet.com, dts@senie.com, IETF@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
In-Reply-To: <200002170220.SAA06416@homer.ka9q.ampr.org>
Message-ID: <Pine.SOL.4.10.10002171240390.14006-100000@petra.ee.surrey.ac.uk>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Wed, 16 Feb 2000, Phil Karn wrote:

> This all boils down to a basic issue of who controls the Internet
> address space -- the users, or the monopolies who have long controlled
> the Internet's underlying transmission media and who are now moving up
> the stack to aggressively control the IP layer and are imposing
> restrictions on the content of their user's traffic.

There is no longer a single Internet address space.

We're going to have to start calling it the InterNAT.

L.

Hey, that means the Internet is InterNATional.

<L.Wood@surrey.ac.uk>PGP<http://www.ee.surrey.ac.uk/Personal/L.Wood/>



From owner-ietf-outbound  Thu Feb 17 08:30:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA12028
	for ietf-outbound.10@ietf.org; Thu, 17 Feb 2000 08:30:02 -0500 (EST)
Received: from poptart.corp.home.net (poptart.svr.home.net [24.0.26.24])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11947
	for <ietf@ietf.org>; Thu, 17 Feb 2000 08:27:50 -0500 (EST)
Received: from c8-a.snvl1.sfba.home.com ([24.0.25.77])
          by poptart.corp.home.net (Netscape Messaging Server 3.54)
           with ESMTP id AAA6D6 for <ietf@ietf.org>;
          Thu, 17 Feb 2000 05:27:40 -0800
Message-Id: <4.2.0.58.20000217082233.0095be30@avarice.inner.net>
X-Sender: rja@avarice.inner.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Thu, 17 Feb 2000 08:29:03 +0000
To: ietf@ietf.org
From: RJ Atkinson <rja@inet.org>
Subject: RE: Internet SYN Flooding, spoofing attacks
In-Reply-To: <016401bf7763$4b82e380$0300000a@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org


I'm uncomfortable with the tone of some of the responses on
this thread.  I don't think there is a need for anyone to
be adversarial about this issue.

Steve Kent's point that we in the Internet community need to work 
on other better mechanisms besides RPF checks is well taken.
It is also the case that at present RPF checks provide significant
operational risk reduction for most operators (whether enterprise,
school, or ISP) and at a reasonable cost.  Nearly all of the security
mechanisms currently deployed are only providing risk reduction --
I'm not aware of any operationally deployed perfect security solution.
The trick as a community is finding cost-effective mechanisms for
reducing individual and collective risks, IMHO.

For example, @Home has found it straight forward to deploy RPF checks
in our network.  Our original motivation was merely to be a good
Internet citizen.  However, we have also found that it reduces our 
operational costs to have such filters in place (e.g. less time spent 
handling alleged abuse cases).  Other ISPs might have different situations 
leading to different conclusions.

Ran
rja@inet.org




From owner-ietf-outbound@ietf.org  Thu Feb 17 08:32:01 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA12152
	for <ietf-web-archive@odin.ietf.org>; Thu, 17 Feb 2000 08:32:01 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA04569;
	Thu, 17 Feb 2000 08:29:56 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id IAA12028
	for ietf-outbound.10@ietf.org; Thu, 17 Feb 2000 08:30:02 -0500 (EST)
Received: from poptart.corp.home.net (poptart.svr.home.net [24.0.26.24])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11947
	for <ietf@ietf.org>; Thu, 17 Feb 2000 08:27:50 -0500 (EST)
Received: from c8-a.snvl1.sfba.home.com ([24.0.25.77])
          by poptart.corp.home.net (Netscape Messaging Server 3.54)
           with ESMTP id AAA6D6 for <ietf@ietf.org>;
          Thu, 17 Feb 2000 05:27:40 -0800
Message-Id: <4.2.0.58.20000217082233.0095be30@avarice.inner.net>
X-Sender: rja@avarice.inner.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Thu, 17 Feb 2000 08:29:03 +0000
To: ietf@ietf.org
From: RJ Atkinson <rja@inet.org>
Subject: RE: Internet SYN Flooding, spoofing attacks
In-Reply-To: <016401bf7763$4b82e380$0300000a@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org


I'm uncomfortable with the tone of some of the responses on
this thread.  I don't think there is a need for anyone to
be adversarial about this issue.

Steve Kent's point that we in the Internet community need to work 
on other better mechanisms besides RPF checks is well taken.
It is also the case that at present RPF checks provide significant
operational risk reduction for most operators (whether enterprise,
school, or ISP) and at a reasonable cost.  Nearly all of the security
mechanisms currently deployed are only providing risk reduction --
I'm not aware of any operationally deployed perfect security solution.
The trick as a community is finding cost-effective mechanisms for
reducing individual and collective risks, IMHO.

For example, @Home has found it straight forward to deploy RPF checks
in our network.  Our original motivation was merely to be a good
Internet citizen.  However, we have also found that it reduces our 
operational costs to have such filters in place (e.g. less time spent 
handling alleged abuse cases).  Other ISPs might have different situations 
leading to different conclusions.

Ran
rja@inet.org




From owner-ietf-outbound  Thu Feb 17 08:40:28 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA12374
	for ietf-outbound.10@ietf.org; Thu, 17 Feb 2000 08:40:02 -0500 (EST)
Received: from poptart.corp.home.net (poptart.svr.home.net [24.0.26.24])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA12177
	for <ietf@ietf.org>; Thu, 17 Feb 2000 08:32:39 -0500 (EST)
Received: from c8-a.snvl1.sfba.home.com ([24.0.25.77])
          by poptart.corp.home.net (Netscape Messaging Server 3.54)
           with ESMTP id AAAC4C; Thu, 17 Feb 2000 05:32:31 -0800
Message-Id: <4.2.0.58.20000217083000.00958ba0@avarice.inner.net>
X-Sender: rja@avarice.inner.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Thu, 17 Feb 2000 08:33:57 +0000
To: Vernon Schryver <vjs@calcite.rhyolite.com>
From: RJ Atkinson <rja@inet.org>
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
Cc: ietf@ietf.org
In-Reply-To: <200002150337.UAA13992@calcite.rhyolite.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 03:37 15-02-00 , Vernon Schryver wrote:

>Could Civil Service employees find it hard to get travel requests approved
>for attending meetings of an outfit that gets carried away in its rules
>and regulations on who can talk to whom?

No.  Been there, done that.  Lots of pain being part of the US Civil Service,
but your specific speculation isn't reality. 

Ran
rja@inet.org



From owner-ietf-outbound@ietf.org  Thu Feb 17 08:43:25 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA12509
	for <ietf-web-archive@odin.ietf.org>; Thu, 17 Feb 2000 08:43:25 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA04877;
	Thu, 17 Feb 2000 08:41:21 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id IAA12374
	for ietf-outbound.10@ietf.org; Thu, 17 Feb 2000 08:40:02 -0500 (EST)
Received: from poptart.corp.home.net (poptart.svr.home.net [24.0.26.24])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA12177
	for <ietf@ietf.org>; Thu, 17 Feb 2000 08:32:39 -0500 (EST)
Received: from c8-a.snvl1.sfba.home.com ([24.0.25.77])
          by poptart.corp.home.net (Netscape Messaging Server 3.54)
           with ESMTP id AAAC4C; Thu, 17 Feb 2000 05:32:31 -0800
Message-Id: <4.2.0.58.20000217083000.00958ba0@avarice.inner.net>
X-Sender: rja@avarice.inner.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Thu, 17 Feb 2000 08:33:57 +0000
To: Vernon Schryver <vjs@calcite.rhyolite.com>
From: RJ Atkinson <rja@inet.org>
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
Cc: ietf@ietf.org
In-Reply-To: <200002150337.UAA13992@calcite.rhyolite.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 03:37 15-02-00 , Vernon Schryver wrote:

>Could Civil Service employees find it hard to get travel requests approved
>for attending meetings of an outfit that gets carried away in its rules
>and regulations on who can talk to whom?

No.  Been there, done that.  Lots of pain being part of the US Civil Service,
but your specific speculation isn't reality. 

Ran
rja@inet.org



From owner-ietf-outbound  Thu Feb 17 08:50:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA12700
	for ietf-outbound.10@ietf.org; Thu, 17 Feb 2000 08:50:03 -0500 (EST)
Received: from poptart.corp.home.net (poptart.svr.home.net [24.0.26.24])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA12545
	for <ietf@ietf.org>; Thu, 17 Feb 2000 08:44:59 -0500 (EST)
Received: from c8-a.snvl1.sfba.home.com ([24.0.25.77])
          by poptart.corp.home.net (Netscape Messaging Server 3.54)
           with ESMTP id AAA1414; Thu, 17 Feb 2000 05:44:50 -0800
Message-Id: <4.2.0.58.20000217084224.0095a220@avarice.inner.net>
X-Sender: rja@avarice.inner.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Thu, 17 Feb 2000 08:46:15 +0000
To: Tim Salo <salo@networkcs.com>
From: RJ Atkinson <rja@inet.org>
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
Cc: ietf@ietf.org
In-Reply-To: <200002152122.PAA87218@us.networkcs.com>
References: <200002151914.LAA20085@zed.isi.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 21:22 15-02-00 , Tim Salo wrote:
>The original poster may, in a very real sense, actually be representing a
>company, whether the IETF wants to believe it or not.
>
>Of course, that leads to the rather interesting dilemma that we don't know
>whether an individual is speaking on behalf or his or her self or on behalf
>of an organization, (again, even if we tell that person that _we_ know
>which it is).

The IETF philosophy has always been that a bunch of engineers get together
via IETF to solve technical problems, largely aside from pecuniary and petty
corporate interests.  

This does break down on occasion, but having this philosophy has (IMHO) helped 
the IETF be more productive than a lot of the alternative standards bodies,
where people absolutely do represent a specific entity.  This philosophy has
also helped ensure that better technical solutions arise than would be the case
otherwise, IMHO.

The IETF is far from perfect, but its the best setup we've found so far.

Regards,

Ran
rja@inet.org



From owner-ietf-outbound@ietf.org  Thu Feb 17 08:53:52 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA12819
	for <ietf-web-archive@odin.ietf.org>; Thu, 17 Feb 2000 08:53:51 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA05080;
	Thu, 17 Feb 2000 08:51:44 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id IAA12700
	for ietf-outbound.10@ietf.org; Thu, 17 Feb 2000 08:50:03 -0500 (EST)
Received: from poptart.corp.home.net (poptart.svr.home.net [24.0.26.24])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA12545
	for <ietf@ietf.org>; Thu, 17 Feb 2000 08:44:59 -0500 (EST)
Received: from c8-a.snvl1.sfba.home.com ([24.0.25.77])
          by poptart.corp.home.net (Netscape Messaging Server 3.54)
           with ESMTP id AAA1414; Thu, 17 Feb 2000 05:44:50 -0800
Message-Id: <4.2.0.58.20000217084224.0095a220@avarice.inner.net>
X-Sender: rja@avarice.inner.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Thu, 17 Feb 2000 08:46:15 +0000
To: Tim Salo <salo@networkcs.com>
From: RJ Atkinson <rja@inet.org>
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
Cc: ietf@ietf.org
In-Reply-To: <200002152122.PAA87218@us.networkcs.com>
References: <200002151914.LAA20085@zed.isi.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 21:22 15-02-00 , Tim Salo wrote:
>The original poster may, in a very real sense, actually be representing a
>company, whether the IETF wants to believe it or not.
>
>Of course, that leads to the rather interesting dilemma that we don't know
>whether an individual is speaking on behalf or his or her self or on behalf
>of an organization, (again, even if we tell that person that _we_ know
>which it is).

The IETF philosophy has always been that a bunch of engineers get together
via IETF to solve technical problems, largely aside from pecuniary and petty
corporate interests.  

This does break down on occasion, but having this philosophy has (IMHO) helped 
the IETF be more productive than a lot of the alternative standards bodies,
where people absolutely do represent a specific entity.  This philosophy has
also helped ensure that better technical solutions arise than would be the case
otherwise, IMHO.

The IETF is far from perfect, but its the best setup we've found so far.

Regards,

Ran
rja@inet.org



From owner-ietf-outbound  Thu Feb 17 09:10:30 2000
Received: by ietf.org (8.9.1a/8.9.1a) id JAA13224
	for ietf-outbound.10@ietf.org; Thu, 17 Feb 2000 09:10:01 -0500 (EST)
Received: from poptart.corp.home.net (poptart.svr.home.net [24.0.26.24])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13033
	for <IETF@ietf.org>; Thu, 17 Feb 2000 09:01:16 -0500 (EST)
Received: from c8-a.snvl1.sfba.home.com ([24.0.25.77])
          by poptart.corp.home.net (Netscape Messaging Server 3.54)
           with ESMTP id AAA1E79; Thu, 17 Feb 2000 06:01:09 -0800
Message-Id: <4.2.0.58.20000217085848.00968310@avarice.inner.net>
X-Sender: rja@avarice.inner.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Thu, 17 Feb 2000 09:02:35 +0000
To: karn@qualcomm.com
From: RJ Atkinson <rja@inet.org>
Subject: Re: Internet SYN Flooding, spoofing attacks
Cc: IETF@ietf.org
In-Reply-To: <200002170220.SAA06416@homer.ka9q.ampr.org>
References: <20000215101728.R19709@jhawk-foo.bbnplanet.com>
 <200002150004.QAA04489@servo.qualcomm.com>
 <38A8C268.33BAF536@senie.com>
 <20000215101728.R19709@jhawk-foo.bbnplanet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 02:20 17-02-00 , Phil Karn wrote:

>It's not because fixed addresses actually cost them more. Indeed,
>another cable modem provider in the other part of town allocates fixed
>addresses in an otherwise identical service that's $5/mo cheaper. No,
>my provider does it simply because they can. They're a monopoly in
>their service area.  Even if I could find somebody at their help desk
>who understood a request to open up their filter to my own IP addresses,
>they would have no incentive to do so.

Phil,

The other cable provider in the other part of town also has Source IP
Address filters in place.  The cost of not having such filters is
too high to bear at our prices (and thin margin).  The vast majority
of users are comfortable with this.    As near as I can tell, most ISPs
(whether dialup, ISDN, DSL, or Cable) have Source IP Address filters in
place for the same reasons (i.e. controlling operational cost).

I am with those who thing that an encrypted VPN tunnel is the right answer 
to the telecommuter problem you've outlined, btw.

Ran
rja@inet.org



From owner-ietf-outbound@ietf.org  Thu Feb 17 09:14:47 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13387
	for <ietf-web-archive@odin.ietf.org>; Thu, 17 Feb 2000 09:14:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA05755;
	Thu, 17 Feb 2000 09:12:42 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id JAA13224
	for ietf-outbound.10@ietf.org; Thu, 17 Feb 2000 09:10:01 -0500 (EST)
Received: from poptart.corp.home.net (poptart.svr.home.net [24.0.26.24])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13033
	for <IETF@ietf.org>; Thu, 17 Feb 2000 09:01:16 -0500 (EST)
Received: from c8-a.snvl1.sfba.home.com ([24.0.25.77])
          by poptart.corp.home.net (Netscape Messaging Server 3.54)
           with ESMTP id AAA1E79; Thu, 17 Feb 2000 06:01:09 -0800
Message-Id: <4.2.0.58.20000217085848.00968310@avarice.inner.net>
X-Sender: rja@avarice.inner.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Thu, 17 Feb 2000 09:02:35 +0000
To: karn@qualcomm.com
From: RJ Atkinson <rja@inet.org>
Subject: Re: Internet SYN Flooding, spoofing attacks
Cc: IETF@ietf.org
In-Reply-To: <200002170220.SAA06416@homer.ka9q.ampr.org>
References: <20000215101728.R19709@jhawk-foo.bbnplanet.com>
 <200002150004.QAA04489@servo.qualcomm.com>
 <38A8C268.33BAF536@senie.com>
 <20000215101728.R19709@jhawk-foo.bbnplanet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 02:20 17-02-00 , Phil Karn wrote:

>It's not because fixed addresses actually cost them more. Indeed,
>another cable modem provider in the other part of town allocates fixed
>addresses in an otherwise identical service that's $5/mo cheaper. No,
>my provider does it simply because they can. They're a monopoly in
>their service area.  Even if I could find somebody at their help desk
>who understood a request to open up their filter to my own IP addresses,
>they would have no incentive to do so.

Phil,

The other cable provider in the other part of town also has Source IP
Address filters in place.  The cost of not having such filters is
too high to bear at our prices (and thin margin).  The vast majority
of users are comfortable with this.    As near as I can tell, most ISPs
(whether dialup, ISDN, DSL, or Cable) have Source IP Address filters in
place for the same reasons (i.e. controlling operational cost).

I am with those who thing that an encrypted VPN tunnel is the right answer 
to the telecommuter problem you've outlined, btw.

Ran
rja@inet.org



From owner-ietf-outbound  Thu Feb 17 12:31:42 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA19540
	for ietf-outbound.10@ietf.org; Thu, 17 Feb 2000 12:30:01 -0500 (EST)
Received: from saint.heaven.net (saint.heaven.net [198.69.28.164])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19400
	for <ietf@ietf.org>; Thu, 17 Feb 2000 12:25:48 -0500 (EST)
Received: (from stpeters@localhost)
	by saint.heaven.net (8.9.3/8.9.3) id MAA27933;
	Thu, 17 Feb 2000 12:25:40 -0500
From: "Dick St.Peters" <stpeters@NetHeaven.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14508.12051.246837.202894@saint.heaven.net>
Date: Thu, 17 Feb 2000 12:25:39 -0500 (EST)
To: ietf@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
In-Reply-To: <200002170202.SAA06407@homer.ka9q.ampr.org>
References: <200002150004.QAA04489@servo.qualcomm.com>
	<38A8C268.33BAF536@senie.com>
	<200002170202.SAA06407@homer.ka9q.ampr.org>
X-Mailer: VM 6.72 under Emacs 19.34.1
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Phil Karn writes:
> By the way, ingress filtering breaks things other than Mobile IP.
> Consider the DirecPC service, which gives you a one-way (forward)
> satellite channel at 400 kb/s. Your return link is via local dialup
> service provider. If the local ISP (or its upstream provider) does
> source filtering, you can't send your perfectly legitimate packets
> into the network over that ISP without tunneling them all through
> DirecPC's own network connection, which may be on the other side of
> the continent.

Filtering does not break my users' DirecPC.

It also does not break their VPN.

It does keep a lot of martian packets off my network, and in several
instances it has blocked spoofed-source-IP DoS attempts by my users.

--
Dick St.Peters, stpeters@NetHeaven.com 
Gatekeeper, NetHeaven, Saratoga Springs, NY
Saratoga/Albany/Amsterdam/BoltonLanding/Cobleskill/Greenwich/
GlensFalls/LakePlacid/NorthCreek/Plattsburgh/...
    Oldest Internet service based in the Adirondack-Albany region



From owner-ietf-outbound@ietf.org  Thu Feb 17 12:36:14 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19910
	for <ietf-web-archive@odin.ietf.org>; Thu, 17 Feb 2000 12:36:14 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA11435;
	Thu, 17 Feb 2000 12:34:10 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id MAA19540
	for ietf-outbound.10@ietf.org; Thu, 17 Feb 2000 12:30:01 -0500 (EST)
Received: from saint.heaven.net (saint.heaven.net [198.69.28.164])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19400
	for <ietf@ietf.org>; Thu, 17 Feb 2000 12:25:48 -0500 (EST)
Received: (from stpeters@localhost)
	by saint.heaven.net (8.9.3/8.9.3) id MAA27933;
	Thu, 17 Feb 2000 12:25:40 -0500
From: "Dick St.Peters" <stpeters@NetHeaven.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14508.12051.246837.202894@saint.heaven.net>
Date: Thu, 17 Feb 2000 12:25:39 -0500 (EST)
To: ietf@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
In-Reply-To: <200002170202.SAA06407@homer.ka9q.ampr.org>
References: <200002150004.QAA04489@servo.qualcomm.com>
	<38A8C268.33BAF536@senie.com>
	<200002170202.SAA06407@homer.ka9q.ampr.org>
X-Mailer: VM 6.72 under Emacs 19.34.1
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Phil Karn writes:
> By the way, ingress filtering breaks things other than Mobile IP.
> Consider the DirecPC service, which gives you a one-way (forward)
> satellite channel at 400 kb/s. Your return link is via local dialup
> service provider. If the local ISP (or its upstream provider) does
> source filtering, you can't send your perfectly legitimate packets
> into the network over that ISP without tunneling them all through
> DirecPC's own network connection, which may be on the other side of
> the continent.

Filtering does not break my users' DirecPC.

It also does not break their VPN.

It does keep a lot of martian packets off my network, and in several
instances it has blocked spoofed-source-IP DoS attempts by my users.

--
Dick St.Peters, stpeters@NetHeaven.com 
Gatekeeper, NetHeaven, Saratoga Springs, NY
Saratoga/Albany/Amsterdam/BoltonLanding/Cobleskill/Greenwich/
GlensFalls/LakePlacid/NorthCreek/Plattsburgh/...
    Oldest Internet service based in the Adirondack-Albany region



From owner-ietf-outbound  Fri Feb 18 14:21:28 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA29521
	for ietf-outbound.10@ietf.org; Fri, 18 Feb 2000 14:20:02 -0500 (EST)
Received: from mail1.digital.com (mail1.digital.com [204.123.2.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29375
	for <ietf@ietf.org>; Fri, 18 Feb 2000 14:10:57 -0500 (EST)
Received: from pachyderm.pa.dec.com (pachyderm.pa.dec.com [16.4.16.23])
	by mail1.digital.com (8.9.2/8.9.3/WV2.0h) with ESMTP id LAA18969
	for <ietf@ietf.org>; Fri, 18 Feb 2000 11:10:57 -0800 (PST)
Received: by pachyderm.pa.dec.com; id LAA08388; Fri, 18 Feb 2000 11:10:34 -0800 (PST)
Date: Fri, 18 Feb 2000 11:10:34 -0800 (PST)
From: jg@pa.dec.com (Jim Gettys)
Message-Id: <200002181910.LAA08388@pachyderm.pa.dec.com>
X-Mailer: Pachyderm (client pachyderm.pa-x.dec.com, user jg)
To: ietf@ietf.org
In-Reply-To: <200002142337.SAA00271@astro.cs.utk.edu>
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
Mime-Version: 1.0
Content-Type: text/plain
X-Loop: ietf@ietf.org

Bravo!
--
Jim Gettys
Technology and Corporate Development
Compaq Computer Corporation
jg@pa.dec.com



From owner-ietf-outbound@ietf.org  Fri Feb 18 14:23:43 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29654
	for <ietf-web-archive@odin.ietf.org>; Fri, 18 Feb 2000 14:23:43 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA08485;
	Fri, 18 Feb 2000 14:21:37 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id OAA29521
	for ietf-outbound.10@ietf.org; Fri, 18 Feb 2000 14:20:02 -0500 (EST)
Received: from mail1.digital.com (mail1.digital.com [204.123.2.50])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29375
	for <ietf@ietf.org>; Fri, 18 Feb 2000 14:10:57 -0500 (EST)
Received: from pachyderm.pa.dec.com (pachyderm.pa.dec.com [16.4.16.23])
	by mail1.digital.com (8.9.2/8.9.3/WV2.0h) with ESMTP id LAA18969
	for <ietf@ietf.org>; Fri, 18 Feb 2000 11:10:57 -0800 (PST)
Received: by pachyderm.pa.dec.com; id LAA08388; Fri, 18 Feb 2000 11:10:34 -0800 (PST)
Date: Fri, 18 Feb 2000 11:10:34 -0800 (PST)
From: jg@pa.dec.com (Jim Gettys)
Message-Id: <200002181910.LAA08388@pachyderm.pa.dec.com>
X-Mailer: Pachyderm (client pachyderm.pa-x.dec.com, user jg)
To: ietf@ietf.org
In-Reply-To: <200002142337.SAA00271@astro.cs.utk.edu>
Subject: Re: IETF Adelaide and interim meetings for APPS WGs
Mime-Version: 1.0
Content-Type: text/plain
X-Loop: ietf@ietf.org

Bravo!
--
Jim Gettys
Technology and Corporate Development
Compaq Computer Corporation
jg@pa.dec.com



From owner-ietf-outbound  Mon Feb 21 00:03:41 2000
Received: by ietf.org (8.9.1a/8.9.1a) id AAA17649
	for ietf-outbound.10@ietf.org; Mon, 21 Feb 2000 00:00:04 -0500 (EST)
Received: from server.jad.net ([202.134.2.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA17614
	for <ietf@ietf.org>; Sun, 20 Feb 2000 23:58:55 -0500 (EST)
Received: from oke.com (cf-isrlab7.comp.nus.edu.sg [137.132.85.181])
	by server.jad.net (8.9.2/8.9.2) with ESMTP id MAA42718;
	Mon, 21 Feb 2000 12:59:53 +0700 (JAVT)
	(envelope-from rms46@oke.com)
Sender: ibrahim@server.jad.net
Message-ID: <38B0C5B8.80543FAF@oke.com>
Date: Mon, 21 Feb 2000 12:57:28 +0800
From: "Rahmat M. Samik-Ibrahim" <rms46@oke.com>
Reply-To: rms46.oke.com@vlsm.org
Organization: VLSM-TJT
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5-22 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: MILIS IETF <ietf@ietf.org>
Subject: Need Clues: procmail configuration for IETF-Announce
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Hello:

For the first time in my life, last weekend I read the fine 
procmail manual. I need some clues on how to configure procmail 
for splitting the IETF-Announce list; especially separating the 
I-D ACTION part. If you have one, would you please send me the 
procmail part of filtering IETF-Announce?

See also:

   http://www.egroups.com/group/ietf-rfc/
   http://www.egroups.com/group/ietf-wg_action/
   http://www.egroups.com/group/ietf-wg_review/
   http://www.egroups.com/group/ietf-announce/
   http://www.egroups.com/group/ietf-document_action/
   http://www.egroups.com/group/ietf-protocol_action/
   http://www.egroups.com/group/ietf-last_call/
   http://www.egroups.com/group/ietf-i-d_action/

regards,

-- 
- Rahmat M. Samik-Ibrahim --  VLSM-TJT --  http://rms46.vlsm.org/ -
What've I got to do, when sorry seems to be the hardest word-John81




From owner-ietf-outbound@ietf.org  Mon Feb 21 00:08:10 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17750
	for <ietf-web-archive@odin.ietf.org>; Mon, 21 Feb 2000 00:08:10 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA27225;
	Mon, 21 Feb 2000 00:05:27 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id AAA17649
	for ietf-outbound.10@ietf.org; Mon, 21 Feb 2000 00:00:04 -0500 (EST)
Received: from server.jad.net ([202.134.2.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA17614
	for <ietf@ietf.org>; Sun, 20 Feb 2000 23:58:55 -0500 (EST)
Received: from oke.com (cf-isrlab7.comp.nus.edu.sg [137.132.85.181])
	by server.jad.net (8.9.2/8.9.2) with ESMTP id MAA42718;
	Mon, 21 Feb 2000 12:59:53 +0700 (JAVT)
	(envelope-from rms46@oke.com)
Sender: ibrahim@server.jad.net
Message-ID: <38B0C5B8.80543FAF@oke.com>
Date: Mon, 21 Feb 2000 12:57:28 +0800
From: "Rahmat M. Samik-Ibrahim" <rms46@oke.com>
Reply-To: rms46.oke.com@vlsm.org
Organization: VLSM-TJT
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5-22 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: MILIS IETF <ietf@ietf.org>
Subject: Need Clues: procmail configuration for IETF-Announce
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hello:

For the first time in my life, last weekend I read the fine 
procmail manual. I need some clues on how to configure procmail 
for splitting the IETF-Announce list; especially separating the 
I-D ACTION part. If you have one, would you please send me the 
procmail part of filtering IETF-Announce?

See also:

   http://www.egroups.com/group/ietf-rfc/
   http://www.egroups.com/group/ietf-wg_action/
   http://www.egroups.com/group/ietf-wg_review/
   http://www.egroups.com/group/ietf-announce/
   http://www.egroups.com/group/ietf-document_action/
   http://www.egroups.com/group/ietf-protocol_action/
   http://www.egroups.com/group/ietf-last_call/
   http://www.egroups.com/group/ietf-i-d_action/

regards,

-- 
- Rahmat M. Samik-Ibrahim --  VLSM-TJT --  http://rms46.vlsm.org/ -
What've I got to do, when sorry seems to be the hardest word-John81




From owner-ietf-outbound  Mon Feb 21 03:10:46 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA01124
	for ietf-outbound.10@ietf.org; Mon, 21 Feb 2000 03:10:02 -0500 (EST)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01100
	for <ietf@ietf.org>; Mon, 21 Feb 2000 03:07:17 -0500 (EST)
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.0.Beta13/8.10.0.Beta13) with ESMTP id e1L841c29354;
	Mon, 21 Feb 2000 03:04:01 -0500
Message-Id: <200002210804.e1L841c29354@black-ice.cc.vt.edu>
To: rms46.oke.com@vlsm.org
cc: MILIS IETF <ietf@ietf.org>, valdis@black-ice.cc.vt.edu
Subject: Re: Need Clues: procmail configuration for IETF-Announce 
In-reply-to: Your message of "Mon, 21 Feb 2000 12:57:28 +0800."
             <38B0C5B8.80543FAF@oke.com> 
From: Valdis.Kletnieks@vt.edu
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <38B0C5B8.80543FAF@oke.com>
Date: Mon, 21 Feb 2000 03:03:54 -0500
X-Loop: ietf@ietf.org

On Mon, 21 Feb 2000 12:57:28 +0800, "Rahmat M. Samik-Ibrahim" <rms46@oke.com>  said:
> For the first time in my life, last weekend I read the fine 
> procmail manual. I need some clues on how to configure procmail 
> for splitting the IETF-Announce list; especially separating the 
> I-D ACTION part. If you have one, would you please send me the 
> procmail part of filtering IETF-Announce?

I use something like this:

:0 E  :ietf-drafts/$LOCKEXT
*^(To:|cc:).*ietf-announce
*^Subject:.*I-D ACTION:
|rcv  -exmh -nobeep +ietf-drafts

:0 E:ietf-announce/$LOCKEXT
*^(To:|cc:).*ietf-announce
|rcv  -exmh -nobeep +ietf-announce

:0 E:ietf-822/$LOCKEXT
*^(To:|cc:).*ietf-822
|rcv  -exmh -nobeep +ietf-822

:0 E:ietf-smtp/$LOCKEXT
*^(To:|cc:).*ietf-smtp
|rcv  -exmh -nobeep +ietf-smtp

:0 E:ietf/$LOCKEXT
*^(To:|cc:).*ietf
|rcv  -exmh -nobeep +ietf

Note that you need to filter them off in the right order, most
restrictive match first...



From owner-ietf-outbound@ietf.org  Mon Feb 21 03:12:14 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01184
	for <ietf-web-archive@odin.ietf.org>; Mon, 21 Feb 2000 03:12:14 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA08112;
	Mon, 21 Feb 2000 03:10:01 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id DAA01124
	for ietf-outbound.10@ietf.org; Mon, 21 Feb 2000 03:10:02 -0500 (EST)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01100
	for <ietf@ietf.org>; Mon, 21 Feb 2000 03:07:17 -0500 (EST)
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.0.Beta13/8.10.0.Beta13) with ESMTP id e1L841c29354;
	Mon, 21 Feb 2000 03:04:01 -0500
Message-Id: <200002210804.e1L841c29354@black-ice.cc.vt.edu>
To: rms46.oke.com@vlsm.org
cc: MILIS IETF <ietf@ietf.org>, valdis@black-ice.cc.vt.edu
Subject: Re: Need Clues: procmail configuration for IETF-Announce 
In-reply-to: Your message of "Mon, 21 Feb 2000 12:57:28 +0800."
             <38B0C5B8.80543FAF@oke.com> 
From: Valdis.Kletnieks@vt.edu
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <38B0C5B8.80543FAF@oke.com>
Date: Mon, 21 Feb 2000 03:03:54 -0500
X-Loop: ietf@ietf.org

On Mon, 21 Feb 2000 12:57:28 +0800, "Rahmat M. Samik-Ibrahim" <rms46@oke.com>  said:
> For the first time in my life, last weekend I read the fine 
> procmail manual. I need some clues on how to configure procmail 
> for splitting the IETF-Announce list; especially separating the 
> I-D ACTION part. If you have one, would you please send me the 
> procmail part of filtering IETF-Announce?

I use something like this:

:0 E  :ietf-drafts/$LOCKEXT
*^(To:|cc:).*ietf-announce
*^Subject:.*I-D ACTION:
|rcv  -exmh -nobeep +ietf-drafts

:0 E:ietf-announce/$LOCKEXT
*^(To:|cc:).*ietf-announce
|rcv  -exmh -nobeep +ietf-announce

:0 E:ietf-822/$LOCKEXT
*^(To:|cc:).*ietf-822
|rcv  -exmh -nobeep +ietf-822

:0 E:ietf-smtp/$LOCKEXT
*^(To:|cc:).*ietf-smtp
|rcv  -exmh -nobeep +ietf-smtp

:0 E:ietf/$LOCKEXT
*^(To:|cc:).*ietf
|rcv  -exmh -nobeep +ietf

Note that you need to filter them off in the right order, most
restrictive match first...



From owner-ietf-outbound  Mon Feb 21 06:30:36 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA02659
	for ietf-outbound.10@ietf.org; Mon, 21 Feb 2000 06:30:04 -0500 (EST)
Received: from server.jad.net ([202.134.2.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02618
	for <ietf@ietf.org>; Mon, 21 Feb 2000 06:27:39 -0500 (EST)
Received: from oke.com (cf-isrlab7.comp.nus.edu.sg [137.132.85.181])
	by server.jad.net (8.9.2/8.9.2) with ESMTP id TAA48904;
	Mon, 21 Feb 2000 19:28:59 +0700 (JAVT)
	(envelope-from rms46@oke.com)
Sender: ibrahim@server.jad.net
Message-ID: <38B12108.BF562E45@oke.com>
Date: Mon, 21 Feb 2000 19:27:04 +0800
From: "Rahmat M. Samik-Ibrahim" <rms46@oke.com>
Reply-To: rms46.oke.com@vlsm.org
Organization: VLSM-TJT
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5-22 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: MILIS IETF <ietf@ietf.org>
Subject: Re: Need Clues: procmail configuration for IETF-Announce
References: <38B0C5B8.80543FAF@oke.com> <200002210804.e1L841c29354@black-ice.cc.vt.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Valdis Kletnieks wrote:
 
> I use something like this:
> [...]

Comrades:

thank for all replies that I have received. I still need
clues on how to rewrite the email headers so that errors
do not bounce to unwanted destinations. The split of the 
IETF Announce list prototype is now available at

      http://ittf.vlsm.org/announce.html

It is provided "as is" with no liability.


regards,

-- 
- Rahmat M. Samik-Ibrahim --  VLSM-TJT --  http://rms46.vlsm.org/ -
Here we are,poised on the precipice of suicide slope-Calvin 20Feb89



From owner-ietf-outbound@ietf.org  Mon Feb 21 06:31:49 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02757
	for <ietf-web-archive@odin.ietf.org>; Mon, 21 Feb 2000 06:31:49 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA12142;
	Mon, 21 Feb 2000 06:29:36 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id GAA02659
	for ietf-outbound.10@ietf.org; Mon, 21 Feb 2000 06:30:04 -0500 (EST)
Received: from server.jad.net ([202.134.2.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02618
	for <ietf@ietf.org>; Mon, 21 Feb 2000 06:27:39 -0500 (EST)
Received: from oke.com (cf-isrlab7.comp.nus.edu.sg [137.132.85.181])
	by server.jad.net (8.9.2/8.9.2) with ESMTP id TAA48904;
	Mon, 21 Feb 2000 19:28:59 +0700 (JAVT)
	(envelope-from rms46@oke.com)
Sender: ibrahim@server.jad.net
Message-ID: <38B12108.BF562E45@oke.com>
Date: Mon, 21 Feb 2000 19:27:04 +0800
From: "Rahmat M. Samik-Ibrahim" <rms46@oke.com>
Reply-To: rms46.oke.com@vlsm.org
Organization: VLSM-TJT
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5-22 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: MILIS IETF <ietf@ietf.org>
Subject: Re: Need Clues: procmail configuration for IETF-Announce
References: <38B0C5B8.80543FAF@oke.com> <200002210804.e1L841c29354@black-ice.cc.vt.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Valdis Kletnieks wrote:
 
> I use something like this:
> [...]

Comrades:

thank for all replies that I have received. I still need
clues on how to rewrite the email headers so that errors
do not bounce to unwanted destinations. The split of the 
IETF Announce list prototype is now available at

      http://ittf.vlsm.org/announce.html

It is provided "as is" with no liability.


regards,

-- 
- Rahmat M. Samik-Ibrahim --  VLSM-TJT --  http://rms46.vlsm.org/ -
Here we are,poised on the precipice of suicide slope-Calvin 20Feb89



From owner-ietf-outbound  Mon Feb 21 14:01:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA14625
	for ietf-outbound.10@ietf.org; Mon, 21 Feb 2000 14:00:02 -0500 (EST)
Received: from magic.adaptec.com (magic.adaptec.com [208.236.45.80])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14493
	for <ietf@ietf.org>; Mon, 21 Feb 2000 13:52:52 -0500 (EST)
Received: from kingdom.adaptec.com (kingdom.adaptec.com [162.62.50.10])
	by magic.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id KAA05423
	for <ietf@ietf.org>; Mon, 21 Feb 2000 10:52:19 -0800 (PST)
Received: from btcexc01.btc.adaptec.com (btcexc01.btc.adaptec.com [162.62.147.10])
	by kingdom.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id KAA07096
	for <ietf@ietf.org>; Mon, 21 Feb 2000 10:52:18 -0800 (PST)
Received: by btcexc01.btc.adaptec.com with Internet Mail Service (5.5.2650.21)
	id <FAJVQXSS>; Mon, 21 Feb 2000 11:54:02 -0700
Message-ID: <3CFAB2A312A9D311BB300000D11ABE920D3037@btcexc01.btc.adaptec.com>
From: "Bradley, Mark" <mark_bradley@btc.adaptec.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: IPS Reflector (IP storage)
Date: Mon, 21 Feb 2000 11:53:58 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

ips@ece.cmu.edu is the reflector address.  

If you  want to add yourself from this mailing list,
you can send mail to <Majordomo@ece.cmu.edu> with the following
command in the body of your email message:

    subscribe ips

or from another account, besides mark_bradley@btc.adaptec.com:

    subscribe ips yourEmailAddress



From owner-ietf-outbound@ietf.org  Mon Feb 21 14:03:39 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14767
	for <ietf-web-archive@odin.ietf.org>; Mon, 21 Feb 2000 14:03:39 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA25736;
	Mon, 21 Feb 2000 14:01:27 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id OAA14625
	for ietf-outbound.10@ietf.org; Mon, 21 Feb 2000 14:00:02 -0500 (EST)
Received: from magic.adaptec.com (magic.adaptec.com [208.236.45.80])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14493
	for <ietf@ietf.org>; Mon, 21 Feb 2000 13:52:52 -0500 (EST)
Received: from kingdom.adaptec.com (kingdom.adaptec.com [162.62.50.10])
	by magic.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id KAA05423
	for <ietf@ietf.org>; Mon, 21 Feb 2000 10:52:19 -0800 (PST)
Received: from btcexc01.btc.adaptec.com (btcexc01.btc.adaptec.com [162.62.147.10])
	by kingdom.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id KAA07096
	for <ietf@ietf.org>; Mon, 21 Feb 2000 10:52:18 -0800 (PST)
Received: by btcexc01.btc.adaptec.com with Internet Mail Service (5.5.2650.21)
	id <FAJVQXSS>; Mon, 21 Feb 2000 11:54:02 -0700
Message-ID: <3CFAB2A312A9D311BB300000D11ABE920D3037@btcexc01.btc.adaptec.com>
From: "Bradley, Mark" <mark_bradley@btc.adaptec.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: IPS Reflector (IP storage)
Date: Mon, 21 Feb 2000 11:53:58 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

ips@ece.cmu.edu is the reflector address.  

If you  want to add yourself from this mailing list,
you can send mail to <Majordomo@ece.cmu.edu> with the following
command in the body of your email message:

    subscribe ips

or from another account, besides mark_bradley@btc.adaptec.com:

    subscribe ips yourEmailAddress



From owner-ietf-outbound  Mon Feb 21 17:40:27 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA18632
	for ietf-outbound.10@ietf.org; Mon, 21 Feb 2000 17:40:02 -0500 (EST)
Received: from magic.adaptec.com (magic.adaptec.com [208.236.45.80])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18582
	for <ietf@ietf.org>; Mon, 21 Feb 2000 17:37:51 -0500 (EST)
Received: from kingdom.adaptec.com (kingdom.adaptec.com [162.62.50.10])
	by magic.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id OAA18054
	for <ietf@ietf.org>; Mon, 21 Feb 2000 14:37:22 -0800 (PST)
Received: from btcexc01.btc.adaptec.com (btcexc01.btc.adaptec.com [162.62.147.10])
	by kingdom.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id OAA18718
	for <ietf@ietf.org>; Mon, 21 Feb 2000 14:37:20 -0800 (PST)
Received: by btcexc01.btc.adaptec.com with Internet Mail Service (5.5.2650.21)
	id <FAJVQXXG>; Mon, 21 Feb 2000 15:39:04 -0700
Message-ID: <3CFAB2A312A9D311BB300000D11ABE920D303A@btcexc01.btc.adaptec.com>
From: "Bradley, Mark" <mark_bradley@btc.adaptec.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: FW: IPS Reflector (IP storage) 
Date: Mon, 21 Feb 2000 15:39:01 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

BTW, the purpose of this reflector is to enable discussions
regarding the charter of a proposed WG and issues w.r.t. 
enabling storage over IP.  The protocarter discusses 1)the 
area of encapsulating storage protocols and 2)another to 
address the needs that are unique to storage over IP, including 
such issues as latency, reliability, privacy and manageability.

-----Original Message-----
From: Donald E. Eastlake 3rd [mailto:dee3@torque.pothole.com]
Sent: Monday, February 21, 2000 12:56 PM
To: Bradley, Mark
Subject: Re: IPS Reflector (IP storage) 


I can't figure out from this message what this ips mailin glist
is about.

Donald

From:  "Bradley, Mark" <mark_bradley@btc.adaptec.com>
Message-ID:
<3CFAB2A312A9D311BB300000D11ABE920D3037@btcexc01.btc.adaptec.com>
To:  "'ietf@ietf.org'" <ietf@ietf.org>
Date:  Mon, 21 Feb 2000 11:53:58 -0700

>ips@ece.cmu.edu is the reflector address.  
>
>If you  want to add yourself from this mailing list,
>you can send mail to <Majordomo@ece.cmu.edu> with the following
>command in the body of your email message:
>
>    subscribe ips
>
>or from another account, besides mark_bradley@btc.adaptec.com:
>
>    subscribe ips yourEmailAddress
>



From owner-ietf-outbound@ietf.org  Mon Feb 21 17:43:12 2000
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18709
	for <ietf-web-archive@odin.ietf.org>; Mon, 21 Feb 2000 17:43:12 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA00861;
	Mon, 21 Feb 2000 17:41:03 -0500 (EST)
Received: by ietf.org (8.9.1a/8.9.1a) id RAA18632
	for ietf-outbound.10@ietf.org; Mon, 21 Feb 2000 17:40:02 -0500 (EST)
Received: from magic.adaptec.com (magic.adaptec.com [208.236.45.80])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18582
	for <ietf@ietf.org>; Mon, 21 Feb 2000 17:37:51 -0500 (EST)
Received: from kingdom.adaptec.com (kingdom.adaptec.com [162.62.50.10])
	by magic.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id OAA18054
	for <ietf@ietf.org>; Mon, 21 Feb 2000 14:37:22 -0800 (PST)
Received: from btcexc01.btc.adaptec.com (btcexc01.btc.adaptec.com [162.62.147.10])
	by kingdom.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id OAA18718
	for <ietf@ietf.org>; Mon, 21 Feb 2000 14:37:20 -0800 (PST)
Received: by btcexc01.btc.adaptec.com with Internet Mail Service (5.5.2650.21)
	id <FAJVQXXG>; Mon, 21 Feb 2000 15:39:04 -0700
Message-ID: <3CFAB2A312A9D311BB300000D11ABE920D303A@btcexc01.btc.adaptec.com>
From: "Bradley, Mark" <mark_bradley@btc.adaptec.com>
To: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: FW: IPS Reflector (IP storage) 
Date: Mon, 21 Feb 2000 15:39:01 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

BTW, the purpose of this reflector is to enable discussions
regarding the charter of a proposed WG and issues w.r.t. 
enabling storage over IP.  The protocarter discusses 1)the 
area of encapsulating storage protocols and 2)another to 
address the needs that are unique to storage over IP, including 
such issues as latency, reliability, privacy and manageability.

-----Original Message-----
From: Donald E. Eastlake 3rd [mailto:dee3@torque.pothole.com]
Sent: Monday, February 21, 2000 12:56 PM
To: Bradley, Mark
Subject: Re: IPS Reflector (IP storage) 


I can't figure out from this message what this ips mailin glist
is about.

Donald

From:  "Bradley, Mark" <mark_bradley@btc.adaptec.com>
Message-ID:
<3CFAB2A312A9D311BB300000D11ABE920D3037@btcexc01.btc.adaptec.com>
To:  "'ietf@ietf.org'" <ietf@ietf.org>
Date:  Mon, 21 Feb 2000 11:53:58 -0700

>ips@ece.cmu.edu is the reflector address.  
>
>If you  want to add yourself from this mailing list,
>you can send mail to <Majordomo@ece.cmu.edu> with the following
>command in the body of your email message:
>
>    subscribe ips
>
>or from another account, besides mark_bradley@btc.adaptec.com:
>
>    subscribe ips yourEmailAddress
>



From owner-ietf-outbound  Tue Feb 22 02:53:08 2000
Received: by ietf.org (8.9.1a/8.9.1a) id CAA07144
	for ietf-outbound.10@ietf.org; Tue, 22 Feb 2000 02:50:01 -0500 (EST)
Received: from dokka.maxware.no (dokka.maxware.no [195.139.236.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA07113
	for <ietf@ietf.org>; Tue, 22 Feb 2000 02:44:59 -0500 (EST)
Received: from alden ([10.128.167.143])
	by dokka.maxware.no (8.9.3/8.9.3) with ESMTP id IAA02959;
	Tue, 22 Feb 2000 08:44:36 +0100
Message-Id: <4.2.0.58.20000222084730.03a57db0@dokka.maxware.no>
X-Sender: hta@dokka.maxware.no
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Tue, 22 Feb 2000 08:48:06 +0100
To: "Bradley, Mark" <mark_bradley@btc.adaptec.com>,
        "'ietf@ietf.org'" <ietf@ietf.org>
From: Harald Tveit Alvestrand <Harald@Alvestrand.no>
Subject: Re: FW: IPS Reflector (IP storage) 
In-Reply-To: <3CFAB2A312A9D311BB300000D11ABE920D303A@btcexc01.btc.adapte
 c.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 15:39 21.02.00 -0700, Bradley, Mark wrote:
>BTW, the purpose of this reflector is to enable discussions
>regarding the charter of a proposed WG and issues w.r.t.
>enabling storage over IP.  The protocarter discusses 1)the
>area of encapsulating storage protocols and 2)another to
>address the needs that are unique to storage over IP, including
>such issues as latency, reliability, privacy and manageability.

How does "storage" differ from "filing", as in "NFSv4"?

              Harald

--
Harald Tveit Alvestrand, EDB Maxware, Norway
Harald.Alvestrand@edb.maxware.no



From owner-ietf-outbound  Tue Feb 22 17:51:21 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA26361
	for ietf-outbound.10@ietf.org; Tue, 22 Feb 2000 17:50:02 -0500 (EST)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26336
	for <ietf@ietf.org>; Tue, 22 Feb 2000 17:49:27 -0500 (EST)
Received: from csapuntz-u1.cisco.com (csapuntz-u1.cisco.com [171.69.199.29])
	by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id OAA18649
	for <ietf@ietf.org>; Tue, 22 Feb 2000 14:49:43 -0800 (PST)
Received: (csapuntz@localhost) by csapuntz-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id OAA17927; Tue, 22 Feb 2000 14:48:56 -0800 (PST)
Date: Tue, 22 Feb 2000 14:48:56 -0800 (PST)
Message-Id: <200002222248.OAA17927@csapuntz-u1.cisco.com>
From: Costa Sapuntzakis <csapuntz@cisco.com>
To: ietf@ietf.org
Subject: Proposed working group: IP Storage
X-Loop: ietf@ietf.org


I have tried to send this to the IETF mailing list a couple times without
luck. I'm sorry if you received duplicate copies.

Announcement of IP Storage (IPS) proposed working group
-------------------------------------------------------

While file storage protocols like NFS and AFS have long operated over
IP-based networks, block storage protocols such as SCSI and ATA have
yet to make the leap from non-IP based interconnects to IP-based
networks. With the emergence of gigabit and 10-gigabit IP networks,
transporting block storage over IP networks is increasingly
attractive.

An IETF working group is the right forum to deal with the many
technical issues associated with IP storage. These issues include the
following.

* A standard, interoperable, high-performance, reliable transport
  protocol for SCSI over IP is needed. Current thinking is that a simple
  protocol over TCP can do the job. Transport of ATA over IP is related,
  but there is no agreement as to need to support it.

* Methods for configuring and discovering storage devices need to be 
  defined. As part of the work, the group will need to determine whether
  and how to leverage other IETF work in this area (e.g. zeroconf, LDAP, 
  Service Location Protocol).

* Methods for the reduction of network stack processing overhead at
  the storage clients and servers need to be considered and possibly
  incorporated into the protocol

* Integration of secure communication mechanisms that support
  high-speed data transfer and restricted access to storage devices 
  -- leveraging existing security solutions (e.g., IPsec, SCSI 
  Access Control) whenever possible.

* Bridging to other SCSI-based interconnects (including Fibre Channel) 
  needs to be defined

* SNMP MIBs and/or CIM object models for SCSI-based devices may be necessary

* QoS issues need to be considered

* IPv6 and NAT interoperability

The ANSI T10, T11, and T13 committees currently control the SCSI,
Fibre Channel, and ATA storage standards. The working group will need
to determine the extent of its collaboration with those committees.

Some progress on these issues has been made already:

* To get the ball rolling, Julian Satran and others have posted a
  preliminary SCSI over TCP draft. It can be found at:
  ftp://ftp.ietf.org/internet-drafts/draft-satran-scot-00.txt
  ftp://ftp.isi.edu/internet-drafts/draft-satran-scot-00.txt

Birds of Feather (BOF)
----------------------

To discuss these issues further and to gain consensus on a charter for
an IP Storage WG, the IETF will host a Birds of Feather (BOF) session
on IP Storage at the 47th IETF in Adelaide, Australia.

A proposed agenda for the BOF is appended to the message.

Mailing List
------------

The ips@ece.cmu.edu mailing list will act as the focal point for
discussions related to this activity. You can subscribe to
ips@ece.cmu.edu by sending mail to majordomo@ece.cmu.edu with a blank
Subject line and "subscribe ips" as the first line of the body.

Web Site
--------

CMU is also maintaining an IPS web site. You can find archives
of the mailing lists, IPS documents, and more at
http://www.ece.cmu.edu/~ips/.

BOF agenda (proposed)
---------------------

This will probably change before the final BOF:

5 min Review of BOF agenda and objectives (D. Lee/M. Bradley)
20 min IP Storage Goals (D. Nagle/A. Wilson)
35 min Discussion
20 min Approaches (5 minutes each)
o C. Sapuntzakis
o A. Wilson
o ISI's NetSCSI (?)
o Other (?)
10 min Proposed charter (D. Lee/M. Bradley)
30 min Discussion






From owner-ietf-outbound  Wed Feb 23 03:22:19 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA16588
	for ietf-outbound.10@ietf.org; Wed, 23 Feb 2000 03:20:02 -0500 (EST)
Received: from muncher.math.uic.edu (muncher.math.uic.edu [131.193.178.181])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA16524
	for <ietf@ietf.org>; Wed, 23 Feb 2000 03:13:28 -0500 (EST)
Received: (qmail 29867 invoked by uid 1001); 23 Feb 2000 08:13:50 -0000
Date: 23 Feb 2000 08:13:50 -0000
Message-ID: <20000223081350.27092.qmail@cr.yp.to>
From: "D. J. Bernstein" <djb@cr.yp.to>
To: namedroppers@ops.ietf.org
Cc: ietf@ietf.org
Subject: Re: a.dns.int
References: <20000215191952.24273.qmail@cr.yp.to> <20000220195445.21265.qmail@cr.yp.to> <4.2.0.58.20000222094532.01be2ed0@dokka.maxware.no> <20000222201111.2486.qmail@cr.yp.to> <E12NOpR-000DdX-00@rip.psg.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Loop: ietf@ietf.org

Randy Bush writes, on the DNSEXT mailing list:
> as we have real work to do in preparation for adelaide, this digression and
> pissing contest will have to move off this list at the end of today.

This ``digression'' is an attempt to fix a serious interoperability
problem. The discussion is clearly within the DNSEXT charter.

Several people have already confirmed that the problem exists, despite a
message from Bush suggesting otherwise.

Several people have expressed interest in eliminating the problem---
although Bush has discarded messages from some of them, in an attempt to
make his position seem more popular than it actually is.

This, unfortunately, isn't new behavior for Bush. See

   http://cr.yp.to/dnscache/namedroppers.html

for documentation of several previous incidents. I'm cc'ing this message
to ietf@ietf.org because Bush generally doesn't allow criticism of his
own behavior on the DNSEXT mailing list.

---Dan



From owner-ietf-outbound  Wed Feb 23 06:00:34 2000
Received: by ietf.org (8.9.1a/8.9.1a) id GAA17987
	for ietf-outbound.10@ietf.org; Wed, 23 Feb 2000 06:00:02 -0500 (EST)
Received: from prue.eim.surrey.ac.uk (IDENT:exim@prue.eim.surrey.ac.uk [131.227.76.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17954
	for <ietf@ietf.org>; Wed, 23 Feb 2000 05:57:53 -0500 (EST)
Received: from petra.ee.surrey.ac.uk ([131.227.88.13] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.03 #1)
	id 12NZUN-0003UF-00; Wed, 23 Feb 2000 10:57:51 +0000
Date: Wed, 23 Feb 2000 10:57:48 +0000 (GMT)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-Sender: eep1lw@petra.ee.surrey.ac.uk
Reply-To: L.Wood@eim.surrey.ac.uk
To: Costa Sapuntzakis <csapuntz@cisco.com>
cc: ietf@ietf.org
Subject: Re: Proposed working group: IP Storage
In-Reply-To: <200002222248.OAA17927@csapuntz-u1.cisco.com>
Message-ID: <Pine.GSO.4.21.0002231052580.1765-100000@petra.ee.surrey.ac.uk>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Tue, 22 Feb 2000, Costa Sapuntzakis wrote:

> Announcement of IP Storage (IPS) proposed working group
> -------------------------------------------------------
> 
> While file storage protocols like NFS and AFS have long operated over
> IP-based networks, block storage protocols such as SCSI and ATA have
> yet to make the leap from non-IP based interconnects to IP-based
> networks. With the emergence of gigabit and 10-gigabit IP networks,
> transporting block storage over IP networks is increasingly
> attractive.
> 
> An IETF working group is the right forum to deal with the many
> technical issues associated with IP storage. These issues include the
> following.
> 
> * A standard, interoperable, high-performance, reliable transport
>   protocol for SCSI over IP is needed.

I have one question here.

Why?

L.

what next? HDLC over HTTP?

<L.Wood@surrey.ac.uk>PGP<http://www.ee.surrey.ac.uk/Personal/L.Wood/>

>   Current thinking is that a simple
>   protocol over TCP can do the job. Transport of ATA over IP is related,
>   but there is no agreement as to need to support it.
> 
> * Methods for configuring and discovering storage devices need to be 
>   defined. As part of the work, the group will need to determine whether
>   and how to leverage other IETF work in this area (e.g. zeroconf, LDAP, 
>   Service Location Protocol).
> 
> * Methods for the reduction of network stack processing overhead at
>   the storage clients and servers need to be considered and possibly
>   incorporated into the protocol
> 
> * Integration of secure communication mechanisms that support
>   high-speed data transfer and restricted access to storage devices 
>   -- leveraging existing security solutions (e.g., IPsec, SCSI 
>   Access Control) whenever possible.
> 
> * Bridging to other SCSI-based interconnects (including Fibre Channel) 
>   needs to be defined
> 
> * SNMP MIBs and/or CIM object models for SCSI-based devices may be necessary
> 
> * QoS issues need to be considered
> 
> * IPv6 and NAT interoperability
> 
> The ANSI T10, T11, and T13 committees currently control the SCSI,
> Fibre Channel, and ATA storage standards. The working group will need
> to determine the extent of its collaboration with those committees.
> 
> Some progress on these issues has been made already:
> 
> * To get the ball rolling, Julian Satran and others have posted a
>   preliminary SCSI over TCP draft. It can be found at:
>   ftp://ftp.ietf.org/internet-drafts/draft-satran-scot-00.txt
>   ftp://ftp.isi.edu/internet-drafts/draft-satran-scot-00.txt
> 
> Birds of Feather (BOF)
> ----------------------
> 
> To discuss these issues further and to gain consensus on a charter for
> an IP Storage WG, the IETF will host a Birds of Feather (BOF) session
> on IP Storage at the 47th IETF in Adelaide, Australia.
> 
> A proposed agenda for the BOF is appended to the message.
> 
> Mailing List
> ------------
> 
> The ips@ece.cmu.edu mailing list will act as the focal point for
> discussions related to this activity. You can subscribe to
> ips@ece.cmu.edu by sending mail to majordomo@ece.cmu.edu with a blank
> Subject line and "subscribe ips" as the first line of the body.
> 
> Web Site
> --------
> 
> CMU is also maintaining an IPS web site. You can find archives
> of the mailing lists, IPS documents, and more at
> http://www.ece.cmu.edu/~ips/.
> 
> BOF agenda (proposed)
> ---------------------
> 
> This will probably change before the final BOF:
> 
> 5 min Review of BOF agenda and objectives (D. Lee/M. Bradley)
> 20 min IP Storage Goals (D. Nagle/A. Wilson)
> 35 min Discussion
> 20 min Approaches (5 minutes each)
> o C. Sapuntzakis
> o A. Wilson
> o ISI's NetSCSI (?)
> o Other (?)
> 10 min Proposed charter (D. Lee/M. Bradley)
> 30 min Discussion



From owner-ietf-outbound  Wed Feb 23 10:12:06 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA23546
	for ietf-outbound.10@ietf.org; Wed, 23 Feb 2000 10:10:02 -0500 (EST)
Received: from dokka.maxware.no (dokka.maxware.no [195.139.236.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23471
	for <ietf@ietf.org>; Wed, 23 Feb 2000 10:05:15 -0500 (EST)
Received: from alden (alden.maxware.no [10.128.1.246])
	by dokka.maxware.no (8.9.3/8.9.3) with ESMTP id QAA17199;
	Wed, 23 Feb 2000 16:04:39 +0100
Message-Id: <4.2.0.58.20000223155811.01ec7180@dokka.maxware.no>
X-Sender: hta@dokka.maxware.no
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Wed, 23 Feb 2000 16:02:56 +0100
To: L.Wood@eim.surrey.ac.uk, Costa Sapuntzakis <csapuntz@cisco.com>
From: Harald Tveit Alvestrand <Harald@Alvestrand.no>
Subject: Re: Proposed working group: IP Storage
Cc: ietf@ietf.org
In-Reply-To: <Pine.GSO.4.21.0002231052580.1765-100000@petra.ee.surrey.ac
 .uk>
References: <200002222248.OAA17927@csapuntz-u1.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 10:57 23.02.00 +0000, Lloyd Wood wrote:
>On Tue, 22 Feb 2000, Costa Sapuntzakis wrote:
>
> > Announcement of IP Storage (IPS) proposed working group
> > -------------------------------------------------------
>
> > * A standard, interoperable, high-performance, reliable transport
> >   protocol for SCSI over IP is needed.
>
>I have one question here.
>
>Why?

Because 100 m Cat5 cabling is cheaper than 5 m of current SCSI cabling?

My personal worry is the set of failure modes that can occur when someone 
uses Mobile-IP to move his PC to his GSM phone in his car, while the disk 
remains at the office, and similar absurdities that people *will* try to do.

BTW, SCSI is used for lots more things than storage - my favourite 
application was the one that used SCSI to control a laser rangefinder....

                    Harald

--
Harald Tveit Alvestrand, EDB Maxware, Norway
Harald.Alvestrand@edb.maxware.no



From owner-ietf-outbound  Wed Feb 23 12:52:47 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA28269
	for ietf-outbound.10@ietf.org; Wed, 23 Feb 2000 12:50:02 -0500 (EST)
Received: from kickme.cisco.com (kickme.cisco.com [198.92.30.42])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27886
	for <ietf@ietf.org>; Wed, 23 Feb 2000 12:32:55 -0500 (EST)
Received: from rhino (rhino.cisco.com [172.20.9.57])
	by kickme.cisco.com (8.9.1a/8.9.1) with ESMTP id JAA09625;
	Wed, 23 Feb 2000 09:21:24 -0800 (PST)
Received: from p7020-img-nt (fred-hm-dhcp1.cisco.com [171.69.128.116]) by rhino (SMI-8.6/CISCO.WS.1.1) with SMTP id JAA28197; Wed, 23 Feb 2000 09:36:22 -0800
Message-Id: <4.1.20000223082352.00ae3230@flipper.cisco.com>
X-Sender: fred@flipper.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Wed, 23 Feb 2000 08:25:20 -0800
To: Costa Sapuntzakis <csapuntz@cisco.com>
From: Fred Baker <fred@cisco.com>
Subject: Re: Proposed working group: IP Storage
Cc: ietf@ietf.org
In-Reply-To: <200002222248.OAA17927@csapuntz-u1.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Loop: ietf@ietf.org

At 02:48 PM 2/22/00 -0800, Costa Sapuntzakis wrote:
>Announcement of IP Storage (IPS) proposed working group
>-------------------------------------------------------

I have a quick question. Has any Area Director signed up to support this
proposed working group and schedule a BOF? Or are you announcing that you
have a desire to open a working group and would like people to support you?



From owner-ietf-outbound  Wed Feb 23 13:21:35 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA29076
	for ietf-outbound.10@ietf.org; Wed, 23 Feb 2000 13:20:02 -0500 (EST)
Received: from localhost.localdomain ([216.52.68.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29053
	for <ietf@ietf.org>; Wed, 23 Feb 2000 13:19:57 -0500 (EST)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id NAA02360
	for <ietf@ietf.org>; Wed, 23 Feb 2000 13:20:22 -0500
Sender: francis@localhost.localdomain
Message-ID: <38B424E4.5C2952A4@ecal.com>
Date: Wed, 23 Feb 2000 13:20:20 -0500
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.2.12-20 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Proposed working group: IP Storage
References: <200002222248.OAA17927@csapuntz-u1.cisco.com> <4.2.0.58.20000223155811.01ec7180@dokka.maxware.no>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Harald Tveit Alvestrand wrote:

> At 10:57 23.02.00 +0000, Lloyd Wood wrote:
>
> >Why?
>
> Because 100 m Cat5 cabling is cheaper than 5 m of current SCSI cabling?
> [...]
> BTW, SCSI is used for lots more things than storage - my favourite
> application was the one that used SCSI to control a laser rangefinder....

So write a laser rangefinder protocol over TCP, rip out the SCSI interface, and
put in Ethernet.  The silicon's cheaper, and you'll probably get better
performance by reducing the layers.  Alternatively, if you've got a legacy
device, attach it to a host running the laser rangefinder protocol in software
(which'll probably be easier to write than a generic SCSI bridge).  Only
problem is if you've got an existing laser rangefinder GUI that you want to run
remotely, and that you can't convert to use the new protocol.

The second most common SCSI application (after disk drives, for which we have
NFS) seems to be scanners, for which remote use doesn't make much sense; you
have to be physically at the scanner to put the paper in.

Mind you, if people want to work on this, I'll assume they have a use for it;
I'm just bemused.

--
/==============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.|
|Chief Scientist |=============================================|
|eCal Corp.      |If at first you don't succeed, don't go      |
|francis@ecal.com|skydiving.                                   |
\==============================================================/





From owner-ietf-outbound  Wed Feb 23 15:11:54 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA01823
	for ietf-outbound.10@ietf.org; Wed, 23 Feb 2000 15:10:01 -0500 (EST)
Received: from mail.perspex.com (IDENT:tlilley@mail.perspex.com [12.5.16.108])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01695
	for <ietf@ietf.org>; Wed, 23 Feb 2000 15:03:03 -0500 (EST)
Received: from localhost (tlilley@localhost) by mail.perspex.com (8.8.7/8.7.3) with SMTP id PAA03134; Wed, 23 Feb 2000 15:05:04 -0500
Date: Wed, 23 Feb 2000 15:05:04 -0500 (EST)
From: Tripp Lilley <tlilley@perspex.com>
To: John Stracke <francis@ecal.com>
cc: ietf@ietf.org
Subject: Re: Proposed working group: IP Storage
In-Reply-To: <38B424E4.5C2952A4@ecal.com>
Message-ID: <Pine.LNX.3.96.1000223150119.31690K-100000@mail.perspex.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Wed, 23 Feb 2000, John Stracke wrote:

> The second most common SCSI application (after disk drives, for which we have
> NFS) seems to be scanners, for which remote use doesn't make much sense; you
> have to be physically at the scanner to put the paper in.

Actually, there are valid scenarios for remote scanning. Specifically,
the high-volume document management scanners are often hooked up in such a
way that you dump a load of paper in them (ie: several thousand sheets),
hit the "go" button, and they're whisked away to somewhere else on the
'net where they're actually processed.

It's easier on the vendors if they only have to support one command set
(ie: SCSI) with potentially multiple transports, than if they have to
throw in new core firmware for each transport. 

-- 
   Tripp Lilley  *  tripp@perspex.com  *  http://stargate.sg505.net/~tlilley/
------------------------------------------------------------------------------
  "'The Fragile' embodies everything wrong with this decade--hype, letdown,
   technological fetishism, empty rage, financial bloat, bombast, self-
   loathing, and indifference to anything truly important and interesting..."

   - Brent DiCrescenzo in
   http://www.pitchforkmedia.com/record-reviews/n/nine-inch-nails/fragile.shtml



From owner-ietf-outbound  Wed Feb 23 20:43:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id UAA06484
	for ietf-outbound.10@ietf.org; Wed, 23 Feb 2000 20:40:02 -0500 (EST)
Received: from wclarke.netzit.com.br (bbking.netzit.com.br [200.210.86.4])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06315
	for <ietf@ietf.org>; Wed, 23 Feb 2000 20:30:03 -0500 (EST)
Received: from linuxbr.com (dial74.spo.netzit.com.br [200.210.86.74] (may be forged))
	by wclarke.netzit.com.br (8.9.3/8.8.7) with ESMTP id WAA20056
	for <ietf@ietf.org>; Wed, 23 Feb 2000 22:44:36 -0300
Sender: root@wclarke.netzit.com.br
Message-ID: <38B5CFBE.26F60242@linuxbr.com>
Date: Fri, 25 Feb 2000 00:41:34 +0000
From: Jean Paul Sartre <sartre@linuxbr.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.15pre9 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
References: <016401bf7763$4b82e380$0300000a@cisco.com>
	 <v04220802b4d078236d2c@[171.78.30.107]> <38AADC73.A638874D@senie.com> <v04220813b4d0c122939d@[171.78.30.107]>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Stephen Kent wrote:

> I'll suggest one course of action, but I keep emphasizing the issue
> is not one of alternates, but of recognizing the limitations of
> proposals now on the table and considering approaches that may work
> irrespective of whether everyone performs filtering.

	I am willing to write a document on the means of packet filtering and
how rules should work for different configurations and environments.
Such configurations should be very well thought and I think an official
Internet draft should be written to advice many networks and common
people on what attacks regard/not their Internet access, should they be
providers, common people browsing/surfing and so on.

> With regard to a wide range of DoS or DDoS attacks, it seems quite
> feasible to monitor traffic to the web site to detect such attacks
> irrespective of whether source addresses are spoofed or not.

	Source-routed packets from untrusted hosts, as many of us know, have to
be dropped/ignored. I do not know if there is another kind of attack
regarding the forging of IP headers, as I didn't study ( :( ) the TCP/IP
RFCs.

> (this differs from IDS for broader attacks, where the recognition problem
> is much harder and the false negative rate is on the order of 20%.)
> Such monitoring can be done by a web hosting facility through purely
> passive monitoring, so as not to adversely affect the performance of
> the network used by a web hosting site.  Once an attack is detected,
> one can trigger a semi-automated response.  If one believes that the
> source addresses are not spoofed, then one can use this to direct
> filtering to selected ingress points, but the filtering can now be
> very focused, based o the characteristics of the detected DoS
> traffic. If one believes that source addressed might be spoofed, then
> one needs to activate the selective filtering on a much wider range
> of ingress points.  Since the true sources may be outside of the
> ISP's sphere of control, filtering at connections to other ISPs may
> be required in either case.

	In this case, I would suggest route and interface changing in an
automatic fashion like OSPF would do (but under attacks) (correct me if
I am wrong). DoS is very dangerous on bandwidth-limited sites that
cannot choose between different routers/gateways. The interface just
gets flooded and in some cases normal traffic disappears and one must
simply disable the interface until the attack ceases.

> If the response is rapid enough, the attack may not have significant
> impact, which reduces the attraction of mounting such an attack in
> the first place.  One can begin disabling the filters once the
> offending traffic flows have diminished, which provides another means
> of determining the sources of traffic, as others have noted in
> previous published work on this topic.
> An advantage of this style of approach is that while it can be even
> more effective if source address filtering is widespread, it also
> would work if such filtering is not completely effective, which is
> the sort of self-defense approach I prefer  It supports what the
> security community refers to as the Principle of Least Privilege.

	As attacks can come from much different sources, if a backbone can at
least log, if not ignore, strangely high traffic from a unique site (but
it cannot, again, prevent DDoS), we should at least diminish the risks
of suffering an attack.

	Cesar



From owner-ietf-outbound  Wed Feb 23 21:31:37 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA07080
	for ietf-outbound.10@ietf.org; Wed, 23 Feb 2000 21:30:02 -0500 (EST)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA06975
	for <ietf@ietf.org>; Wed, 23 Feb 2000 21:20:43 -0500 (EST)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.9.3/calcite) id TAA22428
	for ietf@ietf.org  env-from <vjs>;
	Wed, 23 Feb 2000 19:20:44 -0700 (MST)
Date: Wed, 23 Feb 2000 19:20:44 -0700 (MST)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200002240220.TAA22428@calcite.rhyolite.com>
To: ietf@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
X-Loop: ietf@ietf.org

> 	Source-routed packets from untrusted hosts, as many of us know, have to
> be dropped/ignored. I do not know if there is another kind of attack
> regarding the forging of IP headers, as I didn't study ( :( ) the TCP/IP
> RFCs.

Actually, those who understand the security problem of IP source routes
knows something else.  IP source route options are not problems except to
broken hosts.  It would be nice to think there are no longer such broken
hosts on the net, but that is too much to expect.  In a reasonable world,
we would expect anyone who cannot install non-broken software on their
hosts to install filters against IP source routes where they will do the
least damage, close to the broken hosts.

However, in this world, the news about the irredeemable evil of all ICMP
packets will join year-old news about the utter evil and uselessness of
IP source routes and IEEE 802.3 collisions.  We'll be hearing about all
three for the next 50 years.  (From my poking around, it appears that more
than half of the Internet is now filtering all ICMP TTL-Exceeded, so the
damage done to `traceroute -g`, `ping -R`, and other things by filtering
IP source routes does not matter.)


> 	As attacks can come from much different sources, if a backbone can at
> least log, if not ignore, strangely high traffic from a unique site (but
> it cannot, again, prevent DDoS), we should at least diminish the risks
> of suffering an attack.

Assuming there is an algorithmic definition of "strangely high
traffic from a unique site", how would a backbone and so Terabit/sec
router log anything about it?  Is it easy to define, detect, and
record state for streams if they are strangely high, and the reports
about the difficulties of maintaining state for "multimedia" and
similar buzzword streams do not apply?


Judging from their volume, the world needs a lot more documents about
network or computer security that are more repetitions of trade rag rumors
and security vendor marketing wishes than facts.  However, there's no
reason for the IETF to compete with the current publishers of such works.


Vernon Schryver    vjs@rhyolite.com



From owner-ietf-outbound  Wed Feb 23 21:41:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id VAA07264
	for ietf-outbound.10@ietf.org; Wed, 23 Feb 2000 21:40:02 -0500 (EST)
Received: from jindo.cisco.com (jindo.cisco.com [171.69.11.73])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA07037
	for <ietf@ietf.org>; Wed, 23 Feb 2000 21:26:17 -0500 (EST)
Received: from csapuntz-u1.cisco.com (csapuntz-u1.cisco.com [171.69.199.29])
	by jindo.cisco.com (8.8.8/2.5.1/Cisco List Logging/8.8.8) with ESMTP id SAA28611;
	Wed, 23 Feb 2000 18:25:45 -0800 (PST)
Date: Wed, 23 Feb 2000 18:25:48 -0800 (PST)
From: Costa Sapuntzakis <csapuntz@cisco.com>
To: ietf@ietf.org
cc: ips@ece.cmu.edu
Subject: Clarification of IP Storage announcement
Message-ID: <Pine.GSO.4.10.10002231736590.18614-100000@csapuntz-u1.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org


To clarify a couple items in relation to the announcement
posted earlier on IP storage:

* it is NOT an announcement of an IETF working group.

* IP Storage has not been sanctioned/endorsed by the IESG/IAB/IETF in any
way

My apologies for any confusion resulting from the original posting.

-Costa



From owner-ietf-outbound  Thu Feb 24 07:20:53 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA26637
	for ietf-outbound.10@ietf.org; Thu, 24 Feb 2000 07:20:02 -0500 (EST)
Received: from prue.eim.surrey.ac.uk (IDENT:exim@prue.eim.surrey.ac.uk [131.227.76.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26569
	for <ietf@ietf.org>; Thu, 24 Feb 2000 07:17:54 -0500 (EST)
Received: from petra.ee.surrey.ac.uk ([131.227.88.13] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.03 #1)
	id 12NxCv-0002Ds-00; Thu, 24 Feb 2000 12:17:25 +0000
Date: Thu, 24 Feb 2000 12:17:22 +0000 (GMT)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-Sender: eep1lw@petra.ee.surrey.ac.uk
Reply-To: L.Wood@eim.surrey.ac.uk
To: Jean Paul Sartre <sartre@linuxbr.com>
cc: ietf@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
In-Reply-To: <38B5CFBE.26F60242@linuxbr.com>
Message-ID: <Pine.GSO.4.21.0002241215020.5081-100000@petra.ee.surrey.ac.uk>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Fri, 25 Feb 2000, Jean Paul Sartre wrote:

> Stephen Kent wrote:
> 
> > I'll suggest one course of action, but I keep emphasizing the issue
> > is not one of alternates, but of recognizing the limitations of
> > proposals now on the table and considering approaches that may work
> > irrespective of whether everyone performs filtering.
> 
> 	I am willing to write a document on the means of packet filtering and
> how rules should work for different configurations and environments.

You can't, because you died in 1980.

hth,

L.

<L.Wood@surrey.ac.uk>PGP<http://www.ee.surrey.ac.uk/Personal/L.Wood/>



From owner-ietf-outbound  Thu Feb 24 07:40:31 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA27310
	for ietf-outbound.10@ietf.org; Thu, 24 Feb 2000 07:40:02 -0500 (EST)
Received: from zmamail01.zma.compaq.com (zmamail01.zma.compaq.com [161.114.64.101])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27086
	for <ietf@ietf.org>; Thu, 24 Feb 2000 07:33:45 -0500 (EST)
Received: by zmamail01.zma.compaq.com (Postfix, from userid 12345)
	id 2F7712D6; Thu, 24 Feb 2000 07:33:10 -0500 (EST)
Received: from excreo-gh01.reo.dec.com (unknown [16.41.128.40])
	by zmamail01.zma.compaq.com (Postfix) with ESMTP
	id AD5EB520; Thu, 24 Feb 2000 07:33:09 -0500 (EST)
Received: by EXCREO-GH01 with Internet Mail Service (5.5.2650.21)
	id <10Y4J83Z>; Thu, 24 Feb 2000 12:33:08 -0000
Message-ID: <71C4C55F198BD211B24F0000F842F15804B06DAA@reoexc6.reo.cpqcorp.net>
From: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>
To: "'L.Wood@eim.surrey.ac.uk'" <L.Wood@eim.surrey.ac.uk>,
        Jean Paul Sartre <sartre@linuxbr.com>
Cc: ietf@ietf.org
Subject: RE: Internet SYN Flooding, spoofing attacks
Date: Thu, 24 Feb 2000 12:33:08 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

Well he's obviously devoted to this mailing list and hey, perhaps they have
the same problems with the Internet on the other side !

-----Original Message-----
From: Lloyd Wood [mailto:l.wood@eim.surrey.ac.uk]
Sent: Thursday, February 24, 2000 12:17 PM
To: Jean Paul Sartre
Cc: ietf@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks


On Fri, 25 Feb 2000, Jean Paul Sartre wrote:

> Stephen Kent wrote:
> 
> > I'll suggest one course of action, but I keep emphasizing the issue
> > is not one of alternates, but of recognizing the limitations of
> > proposals now on the table and considering approaches that may work
> > irrespective of whether everyone performs filtering.
> 
> 	I am willing to write a document on the means of packet filtering
and
> how rules should work for different configurations and environments.

You can't, because you died in 1980.

hth,

L.

<L.Wood@surrey.ac.uk>PGP<http://www.ee.surrey.ac.uk/Personal/L.Wood/>



From owner-ietf-outbound  Thu Feb 24 08:40:27 2000
Received: by ietf.org (8.9.1a/8.9.1a) id IAA29115
	for ietf-outbound.10@ietf.org; Thu, 24 Feb 2000 08:40:02 -0500 (EST)
Received: from prosyst.com (server.prosyst.com [195.14.248.34] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA28848
	for <ietf@ietf.org>; Thu, 24 Feb 2000 08:32:10 -0500 (EST)
Message-ID: <000a01bf7ec9$69a9df90$0bcea8c0@plamen>
From: "Plamen Kosseff" <p_kosseff@prosyst.com>
To: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>,
        <L.Wood@eim.surrey.ac.uk>, "Jean Paul Sartre" <sartre@linuxbr.com>
Cc: <ietf@ietf.org>
Subject: Re: Internet SYN Flooding, spoofing attacks
Date: Thu, 24 Feb 2000 15:16:45 +0200
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 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit


i think that his only problem was to connect to this side but so far hi is
doing very well


-----Original Message-----
From: Parkinson, Jonathan <Jonathan.Parkinson@compaq.com>
To: 'L.Wood@eim.surrey.ac.uk' <L.Wood@eim.surrey.ac.uk>; Jean Paul Sartre
<sartre@linuxbr.com>
Cc: ietf@ietf.org <ietf@ietf.org>
Date: Thursday, February 24, 2000 14:40
Subject: RE: Internet SYN Flooding, spoofing attacks


>Well he's obviously devoted to this mailing list and hey, perhaps they have
>the same problems with the Internet on the other side !
>
>-----Original Message-----
>From: Lloyd Wood [mailto:l.wood@eim.surrey.ac.uk]
>Sent: Thursday, February 24, 2000 12:17 PM
>To: Jean Paul Sartre
>Cc: ietf@ietf.org
>Subject: Re: Internet SYN Flooding, spoofing attacks
>
>


>On Fri, 25 Feb 2000, Jean Paul Sartre wrote:
>
>> Stephen Kent wrote:
>>
>> > I'll suggest one course of action, but I keep emphasizing the issue
>> > is not one of alternates, but of recognizing the limitations of
>> > proposals now on the table and considering approaches that may work
>> > irrespective of whether everyone performs filtering.
>>
>> I am willing to write a document on the means of packet filtering
>and
>> how rules should work for different configurations and environments.
>
>You can't, because you died in 1980.
>
>hth,
>
>L.
>
><L.Wood@surrey.ac.uk>PGP<http://www.ee.surrey.ac.uk/Personal/L.Wood/>



From owner-ietf-outbound  Thu Feb 24 10:11:03 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA02066
	for ietf-outbound.10@ietf.org; Thu, 24 Feb 2000 10:10:02 -0500 (EST)
Received: from localhost.localdomain (3.144.8.207.in-addr.arpa [207.8.144.3] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01951
	for <ietf@ietf.org>; Thu, 24 Feb 2000 10:03:52 -0500 (EST)
Received: from ecal.com (localhost [127.0.0.1])
	by localhost.localdomain (8.9.3/8.9.3) with ESMTP id KAA03456
	for <ietf@ietf.org>; Thu, 24 Feb 2000 10:03:53 -0500
Sender: francis@localhost.localdomain
Message-ID: <38B54859.EAA937FF@ecal.com>
Date: Thu, 24 Feb 2000 10:03:53 -0500
From: John Stracke <francis@ecal.com>
X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.2.12-20 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
References: <Pine.GSO.4.21.0002241215020.5081-100000@petra.ee.surrey.ac.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Lloyd Wood wrote:

> On Fri, 25 Feb 2000, Jean Paul Sartre wrote:
>
> >       I am willing to write a document on the means of packet filtering and
> > how rules should work for different configurations and environments.
>
> You can't, because you died in 1980.

His TTL ran out.

--
/==============================================================\
|John Stracke    | http://www.ecal.com |My opinions are my own.|
|Chief Scientist |=============================================|
|eCal Corp.      |Life is like a metaphor.                     |
|francis@ecal.com|                                             |
\==============================================================/





From owner-ietf-outbound  Thu Feb 24 10:20:28 2000
Received: by ietf.org (8.9.1a/8.9.1a) id KAA02363
	for ietf-outbound.10@ietf.org; Thu, 24 Feb 2000 10:20:02 -0500 (EST)
Received: from ns2.a1plus.at (ns2.a1plus.at [193.154.168.4])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02306
	for <ietf@ietf.org>; Thu, 24 Feb 2000 10:19:22 -0500 (EST)
Received: from mwelser (b058.dialup.a1plus.at [193.154.219.58])
	by ns2.a1plus.at (8.9.3/8.9.1) with SMTP id QAA16523;
	Thu, 24 Feb 2000 16:18:34 +0100 (MET)
Reply-To: <mwelser@highway.telekom.at>
From: "Michael Welser" <michael.welser@A1Plus.at>
To: "Plamen Kosseff" <p_kosseff@prosyst.com>,
        "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>,
        <L.Wood@eim.surrey.ac.uk>, "Jean Paul Sartre" <sartre@linuxbr.com>
Cc: <ietf@ietf.org>
Subject: RE: Internet SYN Flooding, spoofing attacks
Date: Thu, 24 Feb 2000 16:22:15 +0100
Message-ID: <NCBBKPFPMLHLEIJAJJLLCEAMDDAA.michael.welser@a1plus.at>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
In-Reply-To: <000a01bf7ec9$69a9df90$0bcea8c0@plamen>
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Furthermore, he was posting from the future...

> -----Original Message-----
> From: Plamen Kosseff [mailto:p_kosseff@prosyst.com]
> Sent: Thursday, February 24, 2000 2:17 PM
> To: Parkinson, Jonathan; L.Wood@eim.surrey.ac.uk; Jean Paul Sartre
> Cc: ietf@ietf.org
> Subject: Re: Internet SYN Flooding, spoofing attacks
> 
> i think that his only problem was to connect to this side but so far hi is
> doing very well
> 
> -----Original Message-----
> From: Parkinson, Jonathan <Jonathan.Parkinson@compaq.com>
> To: 'L.Wood@eim.surrey.ac.uk' <L.Wood@eim.surrey.ac.uk>; Jean Paul Sartre
> <sartre@linuxbr.com>
> Cc: ietf@ietf.org <ietf@ietf.org>
> Date: Thursday, February 24, 2000 14:40
> Subject: RE: Internet SYN Flooding, spoofing attacks
> 
> >Well he's obviously devoted to this mailing list and hey, perhaps they have
> >the same problems with the Internet on the other side !
>
> >-----Original Message-----
> >From: Lloyd Wood [mailto:l.wood@eim.surrey.ac.uk]
> >Sent: Thursday, February 24, 2000 12:17 PM
> >To: Jean Paul Sartre
> >Cc: ietf@ietf.org
> >Subject: Re: Internet SYN Flooding, spoofing attacks
> 
> >On Fri, 25 Feb 2000, Jean Paul Sartre wrote:
> >
> >> Stephen Kent wrote:
> >>
> >> > I'll suggest one course of action, but I keep emphasizing the issue
> >> > is not one of alternates, but of recognizing the limitations of
> >> > proposals now on the table and considering approaches that may work
> >> > irrespective of whether everyone performs filtering.
> >>
> >> I am willing to write a document on the means of packet filtering
> >and
> >> how rules should work for different configurations and environments.
> >
> >You can't, because you died in 1980.
> >
> >hth,
> >
> >L.
> >
> ><L.Wood@surrey.ac.uk>PGP<http://www.ee.surrey.ac.uk/Personal/L.Wood/>



From owner-ietf-outbound  Thu Feb 24 11:20:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id LAA04657
	for ietf-outbound.10@ietf.org; Thu, 24 Feb 2000 11:20:03 -0500 (EST)
Received: from velma.seeglasgow.com (velma.seeglasgow.com [212.250.141.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04589
	for <ietf@ietf.org>; Thu, 24 Feb 2000 11:19:04 -0500 (EST)
Received: by velma.seeglasgow.com with Internet Mail Service (5.5.2650.21)
	id <FP7QRRJZ>; Thu, 24 Feb 2000 16:19:03 -0000
Message-ID: <91FBC84CBEF8D211AE2E0008C79F8A953028EC@velma.seeglasgow.com>
From: Stewart Nolan <stewart.nolan@seeglasgow.com>
To: "'mwelser@highway.telekom.at'" <mwelser@highway.telekom.at>,
        Plamen Kosseff <p_kosseff@prosyst.com>,
        "Parkinson, Jonathan"
	 <Jonathan.Parkinson@compaq.com>,
        L.Wood@eim.surrey.ac.uk, Jean Paul Sartre <sartre@linuxbr.com>
Cc: ietf@ietf.org
Subject: RE: Internet SYN Flooding, spoofing attacks
Date: Thu, 24 Feb 2000 16:19:00 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

Aha! I guess that means Time Travel must be discovered tomorrow, and he
really *is* Jean Paul Sartre...

> -----Original Message-----
> From: Michael Welser [mailto:michael.welser@A1Plus.at]
> Sent: 24 February 2000 15:22
> To: Plamen Kosseff; Parkinson, Jonathan; L.Wood@eim.surrey.ac.uk; Jean
> Paul Sartre
> Cc: ietf@ietf.org
> Subject: RE: Internet SYN Flooding, spoofing attacks
> 
> 
> Furthermore, he was posting from the future...

<snip>



From owner-ietf-outbound  Thu Feb 24 12:10:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA05993
	for ietf-outbound.10@ietf.org; Thu, 24 Feb 2000 12:10:03 -0500 (EST)
Received: from rgfsparc.cr.usgs.gov (rgfsparc.cr.usgs.gov [136.177.164.192])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05745
	for <ietf@ietf.org>; Thu, 24 Feb 2000 12:00:18 -0500 (EST)
Received: from rgfsparc.cr.usgs.gov (rgfsparc.cr.usgs.gov [136.177.164.192])
	by rgfsparc.cr.usgs.gov (8.9.1b+Sun/8.9.1) with SMTP id LAA06102
	for <ietf@ietf.org>; Thu, 24 Feb 2000 11:00:03 -0600 (CST)
Message-Id: <200002241700.LAA06102@rgfsparc.cr.usgs.gov>
Date: Thu, 24 Feb 2000 11:00:03 -0600 (CST)
From: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Reply-To: "Robert G. Ferrell" <root@rgfsparc.cr.usgs.gov>
Subject: Re: Internet SYN Flooding, spoofing attacks
To: ietf@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: RV6/ZN+aYj/gWr/P00ji8A==
X-Mailer: dtmail 1.3.0 CDE Version 1.3 SunOS 5.7 sun4u sparc 
X-Loop: ietf@ietf.org

>You can't, because you died in 1980.

Existentialists don't "die," they just go from being to nothingness.

RGF

Robert G. Ferrell, CISSP
Information Security Officer
National Business Center, US DoI
Robert_G_Ferrell@nbc.gov
------------------------------------------------------------
Nothing I have ever said should be construed as even vaguely
representing an official statement by the NBC or DoI.
------------------------------------------------------------



From owner-ietf-outbound  Thu Feb 24 12:40:32 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA06941
	for ietf-outbound.10@ietf.org; Thu, 24 Feb 2000 12:40:02 -0500 (EST)
Received: from zmamail01.zma.compaq.com (zmamail01.zma.compaq.com [161.114.64.101])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06611
	for <ietf@ietf.org>; Thu, 24 Feb 2000 12:30:37 -0500 (EST)
Received: by zmamail01.zma.compaq.com (Postfix, from userid 12345)
	id 3AFDD607; Thu, 24 Feb 2000 12:30:07 -0500 (EST)
Received: from excreo-gh01.reo.dec.com (unknown [16.41.128.40])
	by zmamail01.zma.compaq.com (Postfix) with ESMTP
	id 3DDC5446; Thu, 24 Feb 2000 12:30:07 -0500 (EST)
Received: by EXCREO-GH01 with Internet Mail Service (5.5.2650.21)
	id <10Y4K10G>; Thu, 24 Feb 2000 17:30:06 -0000
Message-ID: <71C4C55F198BD211B24F0000F842F15804B06DE2@reoexc6.reo.cpqcorp.net>
From: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>
To: "'Robert G. Ferrell'" <root@rgfsparc.cr.usgs.gov>, ietf@ietf.org
Subject: RE: Internet SYN Flooding, spoofing attacks
Date: Thu, 24 Feb 2000 17:30:05 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Loop: ietf@ietf.org

Gosub with No Return ? 

-----Original Message-----
From: Robert G. Ferrell [mailto:root@rgfsparc.cr.usgs.gov]
Sent: Thursday, February 24, 2000 5:00 PM
To: ietf@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks


>You can't, because you died in 1980.

Existentialists don't "die," they just go from being to nothingness.

RGF

Robert G. Ferrell, CISSP
Information Security Officer
National Business Center, US DoI
Robert_G_Ferrell@nbc.gov
------------------------------------------------------------
Nothing I have ever said should be construed as even vaguely
representing an official statement by the NBC or DoI.
------------------------------------------------------------



From owner-ietf-outbound  Thu Feb 24 13:10:43 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA07657
	for ietf-outbound.10@ietf.org; Thu, 24 Feb 2000 13:10:01 -0500 (EST)
Received: from keith.fenris.net (keith.fenris.net [158.222.0.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07538
	for <ietf@ietf.org>; Thu, 24 Feb 2000 13:04:59 -0500 (EST)
Received: from localhost (brian@localhost)
	by keith.fenris.net (8.9.3/8.9.3) with ESMTP id KAA17294;
	Thu, 24 Feb 2000 10:04:30 -0800 (PST)
Date: Thu, 24 Feb 2000 10:04:30 -0800 (PST)
From: Brian Lloyd <brian@lloyd.com>
X-Sender: brian@keith.fenris.net
To: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>
cc: "'L.Wood@eim.surrey.ac.uk'" <L.Wood@eim.surrey.ac.uk>,
        Jean Paul Sartre <sartre@linuxbr.com>, ietf@ietf.org
Subject: RE: Internet SYN Flooding, spoofing attacks
In-Reply-To: <71C4C55F198BD211B24F0000F842F15804B06DAA@reoexc6.reo.cpqcorp.net>
Message-ID: <Pine.GSO.4.21.0002240927410.17088-100000@keith.fenris.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Thu, 24 Feb 2000, Parkinson, Jonathan wrote:

> Well he's obviously devoted to this mailing list and hey, perhaps they have
> the same problems with the Internet on the other side !

Talk about cognitive dissonance, can you imagine the shock felt by an
existentialist to discover that there is life after death?  Most would
become nonfunctional but he is trying to participate in productive
activities.  My hat is off to him.

Brian Lloyd
brian@lloyd.com
+1.530.676.6513



From owner-ietf-outbound  Thu Feb 24 16:31:23 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA10841
	for ietf-outbound.10@ietf.org; Thu, 24 Feb 2000 16:30:02 -0500 (EST)
Received: from web1803.mail.yahoo.com (web1803.mail.yahoo.com [128.11.23.46])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA10801
	for <IETF@ietf.org>; Thu, 24 Feb 2000 16:27:10 -0500 (EST)
Received: (qmail 28260 invoked by uid 60001); 24 Feb 2000 21:27:09 -0000
Message-ID: <20000224212709.28259.qmail@web1803.mail.yahoo.com>
Received: from [216.185.31.146] by web1803.mail.yahoo.com; Thu, 24 Feb 2000 13:27:09 PST
Date: Thu, 24 Feb 2000 13:27:09 -0800 (PST)
From: Casey Farrell <oh_yeah_dot_net@yahoo.com>
Subject: : Proposed design: "WIRELESS GIANTS PAC BELL TEE?"
To: please_speak_into_the_french_bread@egroups.com
Cc: IETF@ietf.org
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-1649760492-951427629=:27888"
X-Loop: ietf@ietf.org

--0-1649760492-951427629=:27888
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

 COMPARE this proposal to today's YAHOO news-

   SPY NETWORKS      FEB 24, 2000

     Wow! Lots of interesting stuff on "NUMBERS!"

......wonder if they will ever..."Cut the Baloney!"
So that 'Artists' can get a little of THEIR
stuff-which is being 'appropriated by the minute...'
up on the world market in the form of that which can
be purchased? It seems like you got to wait forever
'like Clapton said'...for it to clear with the 'Boss!'
Sheesh

Note: forwarded message attached.


=====
Casey Farrell; Designer

oh_yeah_dot_net@yahoo.com

 This Letter and All Contents Copyright 1999 Casey Farrell
              All Rights Reserved
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com
--0-1649760492-951427629=:27888
Content-Type: message/rfc822

Received: from [216.185.31.146] by web1804.mail.yahoo.com; Thu, 24 Feb 2000 13:20:24 PST
Date: Thu, 24 Feb 2000 13:20:24 -0800 (PST)
From: Casey Farrell <oh_yeah_dot_net@yahoo.com>
Subject: Proposed design: "WIRELESS GIANTS PAC BELL TEE?"
To: pmarineau@levi.com
Cc: irdial@irdialsys.win-uk.net
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Length: 1495

Casey Farrell; Designer                    Thursday
San Francisco, California            February 24, 2000

                                  RE: 614275

Attn: Philip Marineau; CEO
c/o   LEVI STRAUSS & COMPANY
      San Francisco, California     

 
  Dear Mr. Marineau,

     Would LEVI's possible be interested in trying to
"get with' the Internet convergence, as it is
centering
in the San Francisco Bay area, in the way of perhaps
acquiring a Tee-Shirt design-associatinging it with 
WIRELESS PHONE activity and the new PAC BELL BALLPARK?
I can not speak for the GIANTS or PAC BELL-have not
heard really from anyone of note-perhaps this is the 
right moment for LEVI's to try something different?

  Please see:

             http://www.slip.net/~o614275

 This is meant to be an 'optical allusion!' Alluding
to
the common cultural icon of the times, the
phone-pad/key-board 'look!' This is of course if
LEVI's thought they could get the Tee-Shirts made, get
PACIFIC BELL COMPANY to 'tandem advertise' and squared
it with the GIANTS Baseball Club.

  I would like to answer any questions this may
present
please contact me as soon as possible;

  Thank you,

  Casey Farrell

tel: (415) 664-2489

    

=====
Casey Farrell; Designer

oh_yeah_dot_net@yahoo.com

 This Letter and All Contents Copyright 1999 Casey Farrell
              All Rights Reserved
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com

--0-1649760492-951427629=:27888--



From owner-ietf-outbound  Thu Feb 24 17:00:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA11512
	for ietf-outbound.10@ietf.org; Thu, 24 Feb 2000 17:00:02 -0500 (EST)
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11356
	for <IETF@ietf.org>; Thu, 24 Feb 2000 16:54:14 -0500 (EST)
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.10.0.Beta13/8.10.0.Beta13) with ESMTP id e1OLrtc29114;
	Thu, 24 Feb 2000 16:53:55 -0500
Message-Id: <200002242153.e1OLrtc29114@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Casey Farrell <oh_yeah_dot_net@yahoo.com>
cc: please_speak_into_the_french_bread@egroups.com, IETF@ietf.org
Subject: Re: : Proposed design: "WIRELESS GIANTS PAC BELL TEE?" 
In-reply-to: Your message of "Thu, 24 Feb 2000 13:27:09 PST."
             <20000224212709.28259.qmail@web1803.mail.yahoo.com> 
From: Valdis.Kletnieks@vt.edu
X-URL: http://black-ice.cc.vt.edu/~valdis/
X-Face: 34C9$Ewd2zeX+\!i1BA\j{ex+$/V'JBG#;3_noWWYPa"|,I#`R"{n@w>#:{)FXyiAS7(8t(
 ^*w5O*!8O9YTe[r{e%7(yVRb|qxsRYw`7J!`AM}m_SHaj}f8eb@d^L>BrX7iO[<!v4-0bVIpaxF#-)
 %9#a9h6JXI|T|8o6t\V?kGl]Q!1V]GtNliUtz:3},0"hkPeBuu%E,j(:\iOX-P,t7lRR#
References: <20000224212709.28259.qmail@web1803.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 24 Feb 2000 16:53:55 -0500
X-Loop: ietf@ietf.org

On Thu, 24 Feb 2000 13:27:09 PST, Casey Farrell said:
> Subject: Proposed design: "WIRELESS GIANTS PAC BELL TEE?"

Hmm.. We've had crypto-export by tshirt. I must have missed the Internet Draft
on "IP Encapsulation on Hanes XL networks" that makes this posting at all
relevant to the IETF.  Either that, or I need to update my bozo filters. ;)
-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech



From owner-ietf-outbound  Thu Feb 24 17:20:17 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA11811
	for ietf-outbound.10@ietf.org; Thu, 24 Feb 2000 17:20:02 -0500 (EST)
Received: from mail1.rdc3.on.home.com (mail1.rdc3.on.home.com [24.2.9.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11780
	for <ietf@ietf.org>; Thu, 24 Feb 2000 17:18:07 -0500 (EST)
Received: from home.com ([24.114.113.69]) by mail1.rdc3.on.home.com
          (InterMail v4.01.01.00 201-229-111) with ESMTP
          id <20000224221801.GVFW24445.mail1.rdc3.on.home.com@home.com>
          for <ietf@ietf.org>; Thu, 24 Feb 2000 14:18:01 -0800
Message-ID: <38B5AE54.E83D7729@home.com>
Date: Thu, 24 Feb 2000 17:19:00 -0500
From: Garreth Jeremiah <garrethj@home.com>
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks 
References: <016401bf7763$4b82e380$0300000a@cisco.com>
		 <v04220802b4d078236d2c@[171.78.30.107]> <38AADC73.A638874D@senie.com> <v04220813b4d0c122939d@[171.78.30.107]> <38B5CFBE.26F60242@linuxbr.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Please excuse my incessant ramblings, but I am sure some of this makes sense.  I am
tired and thies email proves it.....most of this is in the context of DDos

Obviously the very nature of the distributed attack makes it difficult to protect
against.  Employing packet chokes, or CAR at some border router is at best reactive
and must be carefully monitored.  TOdays "farms" of servers make this possability
even less realistic as all of the requirements of all the servers behind the said
router must be taken into consideration.  Clamping UDP to 10% of the total
bandwidth may well be fine for most situations ( Web servers only doing name
resolution for example ) but then where one of those servers relies on UDP that 10%
would be quickly eradicated by "normal" traffic, disabeling the functionality of
this server.  The same may be true ( but far less likley ) for ICMP.

Lets talk ICMP for a moment...... why do you want ICMP data from the internet any
way.... or if you say you have some need, why can we not have 1 machine/device
respond for all of the others.

Surely with the processing power of today we can develop devices to pass off ICMP
processing or "abnormal packet processing" off to another, less powerfull processor
leaving the core tasks directed to the main processing unit.  If the APPP (abnormal
packet processing processor - oh my god) can server no more requests or handle no
more packets, HARD LUCK.  The core functionality of the unit is still being met and
packets outside its traffic pattern are being resirected to the other processor,
which because it is over worked is merely ignoring the packets.

as said all of this is reactive...  To my mind there are a number of proactive
solution, mostly impracticle ones..alas we can dream.  Packet choking implimented
on the end systems such that for example once more than say 30% of traffic is ICMP
it gets ignored ( this still has th problems of the traffic is still being sent,
but as bandwith is used up datagrams are the first to be dropped from the route
such as ICMP and UDP )  this would of course have its own overhead of continually
analysing traffic in each endsystem.

An alternative is one that I do not like as it destroys the essence of "you can do
anything on the internet".  This would be to distribute the defence effort.....
begin looking for the signs of communication between the clients/masters
masters/daemons but in reality, if this could be done then we would have allready
irradicated the common "rpc" issues that allow DDoS daemons to become established.

Oh well life is like a box of sticky brown things that make you fat like me....but
can apparently be good for the heart. G.



From owner-ietf-outbound  Thu Feb 24 17:30:13 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA11979
	for ietf-outbound.10@ietf.org; Thu, 24 Feb 2000 17:30:02 -0500 (EST)
Received: from fb00.eng00.mindspring.net (fb00.eng00.mindspring.net [207.69.200.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11870
	for <IETF@ietf.org>; Thu, 24 Feb 2000 17:22:14 -0500 (EST)
Received: from laptop (pool-209-138-5-165.ipls.grid.net [209.138.5.165])
	by fb00.eng00.mindspring.net (8.9.3/8.8.5) with ESMTP id RAA24229;
	Thu, 24 Feb 2000 17:22:08 -0500 (EST)
Message-Id: <4.2.0.58.20000224161947.00a58be0@127.0.0.1>
X-Sender: rshockey/popd.ix.netcom.com@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Thu, 24 Feb 2000 16:21:42 -0600
To: Valdis.Kletnieks@vt.edu
From: Richard Shockey <rshockey@ix.netcom.com>
Subject: April 1 is coming up you know...
Cc: IETF@ietf.org
In-Reply-To: <200002242153.e1OLrtc29114@black-ice.cc.vt.edu>
References: <Your message of "Thu, 24 Feb 2000 13:27:09 PST." <20000224212709.28259.qmail@web1803.mail.yahoo.com>
 <20000224212709.28259.qmail@web1803.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Loop: ietf@ietf.org

At 04:53 PM 2/24/2000 -0500, Valdis.Kletnieks@vt.edu wrote:
>On Thu, 24 Feb 2000 13:27:09 PST, Casey Farrell said:
> > Subject: Proposed design: "WIRELESS GIANTS PAC BELL TEE?"
>
>Hmm.. We've had crypto-export by tshirt. I must have missed the Internet Draft
>on "IP Encapsulation on Hanes XL networks"

I see possibilities here... :-)




 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey
Shockey Consulting LLC
8045 Big Bend Blvd. Suite 110
St. Louis, MO 63119
Voice 314.918.9020
eFAX Fax to EMail 815.333.1237 (Preferred for Fax)
INTERNET Mail & IFAX : rshockey@ix.netcom.com
GSTN Fax 314.918.9015
MediaGate iPost VoiceMail and Fax 800.260.4464
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<



From owner-ietf-outbound  Fri Feb 25 03:20:44 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA03533
	for ietf-outbound.10@ietf.org; Fri, 25 Feb 2000 03:20:01 -0500 (EST)
Received: from prue.eim.surrey.ac.uk (IDENT:exim@prue.eim.surrey.ac.uk [131.227.76.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA03468
	for <ietf@ietf.org>; Fri, 25 Feb 2000 03:05:49 -0500 (EST)
Received: from petra.ee.surrey.ac.uk ([131.227.88.13] ident=eep1lw)
	by prue.eim.surrey.ac.uk with esmtp (Exim 3.03 #1)
	id 12OFko-0004nz-00; Fri, 25 Feb 2000 08:05:38 +0000
Date: Fri, 25 Feb 2000 08:05:34 +0000 (GMT)
From: Lloyd Wood <l.wood@eim.surrey.ac.uk>
X-Sender: eep1lw@petra.ee.surrey.ac.uk
Reply-To: L.Wood@eim.surrey.ac.uk
To: Vernon Schryver <vjs@calcite.rhyolite.com>
cc: ips@ece.cmu.edu, tcp-impl@grc.nasa.gov, ietf@ietf.org
Subject: Re: TCP RDMA option to accelerate NFS, CIFS, SCSI, etc.
In-Reply-To: <200002250223.TAA25413@calcite.rhyolite.com>
Message-ID: <Pine.GSO.4.21.0002250727470.7870-100000@petra.ee.surrey.ac.uk>
Organization: speaking for none
X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/
X-no-archive: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Loop: ietf@ietf.org

On Thu, 24 Feb 2000, Vernon Schryver wrote:

> > From: Erik Nordmark <Erik.Nordmark@Eng.Sun.COM>
> 
> > > A draft describing the TCP RDMA option can be found at:
> > > ftp://ftpeng.cisco.com/pub/rdma/draft-csapuntz-tcprdma-00.txt

If this _was_ a draft, it would be available from
http://www.ietf.org/internet-drafts/

(and I imagine that it wouldn't go against RFC2026, or be copyright
Cisco. I see that e.g.
ftp://ftp.ietf.org/internet-drafts/draft-satran-scot-00.txt
has similar wording. How widespread is this practice?)


> > There is no DNS entry for ftpeng.cisco.com so I can't access the document.
> 
> ftpeng.cisco.com resolves for me to 198.92.30.33, and the URL works

It's an alias for ftp-eng.
there doesn't appear to be a reverse DNS entry, though.


> ftpeng.cisco.com does not answer ICMP Echo-Requests.  It also seems that
> Cisco is filtering ICMP TTL Exceeded.
> 
> Oh, well.  I predict that soon traceroute and ping will be as
> effective as if the Internet were run by the old line telco managers
> who went great lengths to keep their technical problems quite.

Bear in mind that both traceroute and ping were effective one-person
opportunistic hacks based on using an existing infrastructure in
unexpected ways.

If they'd first been tediously designed by a committee, standardised
and mandated, things might be different. they probably wouldn't work
as well, but they'd be on buzzword-compliant feature lists.


> I'm even less impressed about the proposal than Erik Nordmark,

Note the mentions of SCSI and SCSI/TCP and the tie-in with the
proposed IP Storage efforts (recent ietf general list discussion).

I'd still like to know _why_.

L.

SCSI DMA over TCP? What _is_ all this aiming for - trying to build
distributed RAID arrays with really poor performance that are subject
to WAN outages and DoS attacks?

<L.Wood@surrey.ac.uk>PGP<http://www.ee.surrey.ac.uk/Personal/L.Wood/>







From owner-ietf-outbound  Fri Feb 25 14:01:12 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA17645
	for ietf-outbound.10@ietf.org; Fri, 25 Feb 2000 14:00:02 -0500 (EST)
Received: from web1806.mail.yahoo.com (web1806.mail.yahoo.com [128.11.23.49])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA17533
	for <IETF@ietf.org>; Fri, 25 Feb 2000 13:56:50 -0500 (EST)
Received: (qmail 26842 invoked by uid 60001); 25 Feb 2000 18:56:49 -0000
Message-ID: <20000225185649.26841.qmail@web1806.mail.yahoo.com>
Received: from [216.185.31.49] by web1806.mail.yahoo.com; Fri, 25 Feb 2000 10:56:49 PST
Date: Fri, 25 Feb 2000 10:56:49 -0800 (PST)
From: Casey Farrell <oh_yeah_dot_net@yahoo.com>
Subject: IETF was wright as usual! Dey said "No Tanks'... litter felluh!"
To: IETF@ietf.org
Cc: totally_schwag@egroups.com
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-596516649-951505009=:24273"
X-Loop: ietf@ietf.org

--0-596516649-951505009=:24273
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline



Note: forwarded message attached.


=====
Casey Farrell; Designer

oh_yeah_dot_net@yahoo.com

 This Letter and All Contents Copyright 1999 Casey Farrell
              All Rights Reserved
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com
--0-596516649-951505009=:24273
Content-Type: message/rfc822

X-Apparently-To: oh_yeah_dot_net@yahoo.com via web1806.mail.yahoo.com
X-Track2: 2
X-Track: 1: 40
Received: from unknown (HELO naexims.levi.com) (155.57.254.4)
  by mta125.mail.yahoo.com with SMTP; 25 Feb 2000 18:00:38 -0000
Received: from na1.levi.com ([155.57.254.1]) by naexims.levi.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0)
	id F44YYKVK; Fri, 25 Feb 2000 10:01:51 -0800
Received: from SFOEXIMS by na1.levi.com
          via smtpd (for [155.57.254.4]) with SMTP; 25 Feb 2000 17:55:10 UT
Received: by sfoexims.na.levi.com with Internet Mail Service (5.5.2448.0)
	id <FS0JCV2Z>; Fri, 25 Feb 2000 10:00:58 -0800
Message-ID: <D07D0E453FEFD111966400805F15CE8F010E1F08@sfoex8.na.levi.com>
From: questions@levi.com
To: oh_yeah_dot_net@yahoo.com
Subject: RE: Your Comment/Question
Date: Fri, 25 Feb 2000 10:04:22 -0800
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Length: 2620
MIME-Version: 1.0

Dear Casey:
 
Thanks for your recent e-mail message regarding your idea 
for a the promotional t-shirt for the Pac Bell Ballpark.  We're 
flattered that you thought of Levi Strauss & Co. for your idea.  Mr 
Marineau has forwarded your information to me for response.

We have a staff of product design and marketing development 
professionals dedicated exclusively to creating promotions 
that meet the needs of our consumers.  While we appreciate your 
interest, we are unable to consider your promotional idea.  Our 
existing contracts make any involvement impossible for us.  
However, we wish you all the best with this promotion.

Thanks again for taking the time to contact us.  We wish you luck 
and success in your endeavors.

Sincerely,

Shawn Rossiter
Levi Strauss & Co - Executive Office
sharos1685264

--------------------< you wrote >--------------------
-----Original Message-----
From: Casey Farrell 
[mailto:oh_yeah_dot_net@yahoo.com] 
Sent: Thursday, February 24, 2000 1:20 PM
To: Marineau, Phil
Cc: irdial@irdialsys.win-uk.net
Subject: Proposed design: "WIRELESS GIANTS PAC 
BELL TEE?"


Casey Farrell; Designer                    
Thursday
San Francisco, California            February 
24, 2000

                                  RE: 614275

Attn: Philip Marineau; CEO
c/o   LEVI STRAUSS & COMPANY
      San Francisco, California     

 
  Dear Mr. Marineau,

     Would LEVI's possible be interested in 
trying to
"get with' the Internet convergence, as it is
centering
in the San Francisco Bay area, in the way of 
perhaps
acquiring a Tee-Shirt design-associatinging it 
with 
WIRELESS PHONE activity and the new PAC BELL 
BALLPARK?
I can not speak for the GIANTS or PAC BELL-
have not
heard really from anyone of note-perhaps this 
is the 
right moment for LEVI's to try something 
different?

  Please see:

             http://www.slip.net/~o614275

 This is meant to be an 'optical allusion!' 
Alluding
to
the common cultural icon of the times, the
phone-pad/key-board 'look!' This is of course 
if
LEVI's thought they could get the Tee-Shirts 
made, get
PACIFIC BELL COMPANY to 'tandem advertise' and 
squared
it with the GIANTS Baseball Club.

  I would like to answer any questions this 
may
present
please contact me as soon as possible;

  Thank you,

  Casey Farrell

tel: (415) 664-2489

    

=====
Casey Farrell; Designer

oh_yeah_dot_net@yahoo.com

 This Letter and All Contents Copyright 1999 
Casey Farrell
              All Rights Reserved
______________________________________________
____
Do You Yahoo!?
Talk to your friends online with Yahoo! 
Messenger.
http://im.yahoo.com



--0-596516649-951505009=:24273--



From owner-ietf-outbound  Fri Feb 25 16:30:34 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA21217
	for ietf-outbound.10@ietf.org; Fri, 25 Feb 2000 16:30:02 -0500 (EST)
Received: from newdev.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21099
	for <ietf@ietf.org>; Fri, 25 Feb 2000 16:26:21 -0500 (EST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.9.3/8.9.3) id QAA04044
	for ietf@ietf.org; Fri, 25 Feb 2000 16:26:21 -0500 (EST)
Date: Fri, 25 Feb 2000 16:26:21 -0500 (EST)
From: Scott Bradner <sob@harvard.edu>
Message-Id: <200002252126.QAA04044@newdev.harvard.edu>
To: ietf@ietf.org
Subject: a request for input (formal or otherwise) to the FCC
X-Loop: ietf@ietf.org


Dave is an old friend of the IETF - he has now undertaken an assignment
at the US Federal Communications Commission and asked me to forward
his invitation to contact him in his new role.


Scott

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

Date: Wed, 23 Feb 2000 16:00:29 -0500
From: "David Farber" <DFARBER@fcc.gov>
Subject: IP: Open letter to my internet friends and even non-friends :-)

I have been at the Federal Communications Commission as Chief Technologist
for about a month including several snow storms and a trip or so.

I am focusing my long term contribution on understanding and articulating
the impact of internet technology and practices  on those aspects of the
communications industry that the FCC currently regulates.

Please note I am NOT doing this for any ulterior motives but rather
to  help the staff and  Commissioners understand the issues and to help
them "do no harm"

I welcome your inputs and invite you to email them to me and/or stop by at
the FCC and talk. I hope to get to some of the meetings , like the  IETF,

I would prefer not to discuss areas of active regulatory action 
since the ethics rules that cover such conversations may require 
their disclosure, or prohibit those discussions outright.

Please please take advantage of the opportunity offered by "one of us"
being at the FCC.

Dave

David Farber
Chief Technologist
Federal Communications Commission
202 418 2046





From owner-ietf-outbound  Sat Feb 26 15:32:05 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA18361
	for ietf-outbound.10@ietf.org; Sat, 26 Feb 2000 15:30:01 -0500 (EST)
Received: from shell9.ba.best.com (root@shell9.ba.best.com [206.184.139.140])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18337
	for <ietf@ietf.org>; Sat, 26 Feb 2000 15:28:27 -0500 (EST)
Received: (from bovik@localhost)
	by shell9.ba.best.com (8.9.3/8.9.2/best.sh) id MAA20481
	for ietf@ietf.org; Sat, 26 Feb 2000 12:28:11 -0800 (PST)
Date: Sat, 26 Feb 2000 12:28:11 -0800 (PST)
From: "James P. Salsman" <bovik@best.com>
Message-Id: <200002262028.MAA20481@shell9.ba.best.com>
To: ietf@ietf.org
Subject: URGENT: W3C web form standards for device input and upload
X-Loop: ietf@ietf.org


PLEASE DISTRIBUTE WIDELY -- especially in Mac and Linux communities

Thursday evening I spoke with a member of the W3C HTML Working
Group who removed all my remaining doubt that the HTML WG has any
serious support for open, non-proprietary web form upload standards
for non-wintel platforms.  The HTML WG keeps including Microsoft's
OBJECT catch-all element tag, even in "scaled down" versions of
HTML, but refuses to support the non-proprietary device upload
proposal.  Your help is needed to correct this situation.

Please read and endorse this petition:  http://www.bovik.org/devup-petition

We need as many people as possible to request these features and
support for the standard.  Thank you for your help with this effort.

Cheers,
James Salsman



From owner-ietf-outbound  Mon Feb 28 03:23:20 2000
Received: by ietf.org (8.9.1a/8.9.1a) id DAA01435
	for ietf-outbound.10@ietf.org; Mon, 28 Feb 2000 03:20:01 -0500 (EST)
Received: from munnari.OZ.AU (munnari.OZ.AU [128.250.1.21])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA01369;
	Mon, 28 Feb 2000 03:12:52 -0500 (EST)
Received: from mundamutti.cs.mu.OZ.AU ([128.250.1.5])
	by munnari.OZ.AU with SMTP (5.83--+1.3.1+0.59) id IA14653;
	Mon, 28 Feb 2000 19:11:41 +1100 (from kre@munnari.OZ.AU)
From: Robert Elz <kre@munnari.OZ.AU>
To: iesg@ietf.org
Cc: dnsop@cafax.se, ietf@ietf.org
Subject: Re: Last Call: Root Name Server Operational Requirements to BCP 
In-Reply-To: Your message of "Fri, 25 Feb 2000 09:38:09 CDT."
             <200002251438.JAA09126@ietf.org> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 28 Feb 2000 19:11:36 +1100
Message-Id: <13585.951725496@munnari.OZ.AU>
Sender: kre@munnari.OZ.AU
X-Loop: ietf@ietf.org

    Date:        Fri, 25 Feb 2000 09:38:09 -0500
    From:        The IESG <iesg-secretary@ietf.org>
    Message-ID:  <200002251438.JAA09126@ietf.org>

  | The IESG has received a request from the Domain Name Server Operations
  | Working Group to consider Root Name Server Operational Requirements
  | <draft-ietf-dnsop-root-opreq-03.txt> as a BCP.

One minor point - section 2.8 ...

   2.8 Servers MUST generate checksums when sending UDP datagrams and
       MUST verify checksums when receiving UDP datagrams.

could perhaps be read as suggesting that a root server must discard a
UDP packet received without a checksum (checksum field set to 0), as in
such a packet the checksum cannot be verified.   I see no reason why a
root server shouldn't process such requests, however dumb some may consider
sending such things.   So, I'd propose rewording that sentence to...

   2.8 Servers MUST generate checksums when sending UDP datagrams and
       MUST verify checksums when receiving UDP datagrams containing
       a non-zero checksum.

to make it quite clear that the point is that the servers aren't allowed
to "optimise" away the checksum check, which I assume was the point.

kre



From owner-ietf-outbound  Mon Feb 28 12:30:37 2000
Received: by ietf.org (8.9.1a/8.9.1a) id MAA15561
	for ietf-outbound.10@ietf.org; Mon, 28 Feb 2000 12:30:02 -0500 (EST)
Received: from hera.cwi.nl (hera.cwi.nl [192.16.191.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15322
	for <ietf@ietf.org>; Mon, 28 Feb 2000 12:21:01 -0500 (EST)
Received: from pembo (pembo.cwi.nl [192.16.201.136]) by hera.cwi.nl with SMTP
	id SAA10340 for ; Mon, 28 Feb 2000 18:19:12 +0100 (MET)
Message-ID: <007d01bf8210$138f28a0$88c910c0@cwi.nl>
From: "Steven Pemberton" <Steven.Pemberton@cwi.nl>
To: <ietf@ietf.org>, <www-html@W3.ORG>, <jpalme@DSV.SU.SE>,
        <ghobbs@onebox.com>, <walter@natural-innovations.com>
Cc: "HTML WG" <w3c-html-wg@W3.ORG>
Subject: Device upload for all platforms -- the official HTML WG position
Date: Mon, 28 Feb 2000 18:20:13 +0100
Organization: CWI
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_007A_01BF8218.74E73A40"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
X-Loop: ietf@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_007A_01BF8218.74E73A40
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

>From: "James P. Salsman" <bovik@best.com>
>Subject: URGENT: W3C web form standards for device input and upload
>
>Thursday evening I spoke with a member of the W3C HTML Working
>Group who removed all my remaining doubt that the HTML WG has any
>serious support for open, non-proprietary web form upload standards
>for non-wintel platforms.  The HTML WG keeps including Microsoft's
>OBJECT catch-all element tag, even in "scaled down" versions of
>HTML, but refuses to support the non-proprietary device upload
>proposal.  Your help is needed to correct this situation.

I think that as chair of the HTML WG, I had better quickly put this
straight.

James Salsman sent the HTML Working Group a proposal sometime ago for device
upload. We read it, and sent back details to him of how it could be improved
(for instance for device independence). However, he declined to make
changes, claiming that it was fine as it was. We said that we couldn't
accept it flawed as it was, and offered him ways to get involved.

Since then he has been sending messages like the above, apparently thinking
that the problems in his proposal can be solved by petition.

The HTML WG has no problems with device upload, and has never refused to
support device upload; we think it is a good idea. James Salsman's proposal
is flawed, and we have commented on how it could be repaired.

The WG is currently working on revised forms, and any device upload would be
in the context of that work.

The <object> element is a part of HTML 4, which was created by a group of
representatives from many companies. It is not a platform-dependent or
vendor-dependent element.

Best wishes,

Steven Pemberton
Chair, W3C HTML WG

------=_NextPart_000_007A_01BF8218.74E73A40
Content-Type: text/x-vcard;
	name="Steven Pemberton.vcf"
Content-Disposition: attachment;
	filename="Steven Pemberton.vcf"
Content-Transfer-Encoding: quoted-printable

BEGIN:VCARD
VERSION:2.1
N:Pemberton;Steven
FN:Steven Pemberton
ORG:CWI
TEL;WORK;VOICE:+31-20-592 4138
TEL;HOME;VOICE:+31-20-638 5568
TEL;CELL;VOICE:+31-624 671 668
TEL;WORK;FAX:+31-20-592 4199
ADR;WORK:;;Kruislaan 413;1098 SJ Amsterdam;;;The Netherlands
LABEL;WORK;ENCODING=3DQUOTED-PRINTABLE:Kruislaan 413=3D0D=3D0A1098 SJ =
Amsterdam=3D0D=3D0AThe Netherlands
X-WAB-GENDER:2
URL:http://www.cwi.nl/~steven/
EMAIL;PREF;INTERNET:steven.pemberton@cwi.nl
REV:20000228T172013Z
END:VCARD

------=_NextPart_000_007A_01BF8218.74E73A40--



From owner-ietf-outbound  Mon Feb 28 13:00:27 2000
Received: by ietf.org (8.9.1a/8.9.1a) id NAA16305
	for ietf-outbound.10@ietf.org; Mon, 28 Feb 2000 13:00:02 -0500 (EST)
Received: from shell9.ba.best.com (root@shell9.ba.best.com [206.184.139.140])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16193
	for <ietf@ietf.org>; Mon, 28 Feb 2000 12:56:22 -0500 (EST)
Received: (from bovik@localhost)
	by shell9.ba.best.com (8.9.3/8.9.2/best.sh) id JAA03783;
	Mon, 28 Feb 2000 09:55:23 -0800 (PST)
Date: Mon, 28 Feb 2000 09:55:23 -0800 (PST)
From: "James P. Salsman" <bovik@best.com>
Message-Id: <200002281755.JAA03783@shell9.ba.best.com>
To: Steven.Pemberton@cwi.nl
Subject: Re: Device upload for all platforms -- the official HTML WG position
Cc: ietf@ietf.org, www-html@W3.ORG
In-Reply-To: <007d01bf8210$138f28a0$88c910c0@cwi.nl>
X-Loop: ietf@ietf.org

Dear Dr. Pemberton,

Thank you for your message.  I hope this one gets through.  Some 
of my email to W3C lists (e.g., www-forms) has not appeared in 
the archives.

You state that there are comments regarding how the device upload 
proposal can be improved.  Please publish them, with my replies to 
them.  My understanding is that there are no unresolved issues.

> for instance for device independence

The device upload proposal -- http://www.bovik.org/device-upload.html
is the epitome of device independence -- it has an extensible 
"device" attribute, after all.  This line of argument is disingenuous,
and I hope it is not representative of the official position of the
W3C.  Please let me know.

> The WG is currently working on revised forms, and any device upload
> would be in the context of that work.

You refer to the extensive re-design of forms using XML, which 
will require substantial replacement of both client and server
software.  I do not wish my work to be associated with that 
effort.  First, the device upload proposal requires only changes 
in web clients, not CGI script processing software or other 
server software.  More importantly, the "XForms" work is 
currently scheduled for completion in the forth quarter.  Why 
should people on non-wintel platforms wait that long for a way 
to record audio?  As you know, I participated in the XForms work,
but I think it would be a mistake for me to resume participation.

Please accept the device upload submission from General Magic 
as a Working Draft, on Recommendation track.

Cheers,
James Salsman



From owner-ietf-outbound  Mon Feb 28 16:01:22 2000
Received: by ietf.org (8.9.1a/8.9.1a) id QAA19860
	for ietf-outbound.10@ietf.org; Mon, 28 Feb 2000 16:00:02 -0500 (EST)
Received: from shell9.ba.best.com (root@shell9.ba.best.com [206.184.139.140])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19832
	for <ietf@ietf.org>; Mon, 28 Feb 2000 15:59:25 -0500 (EST)
Received: (from bovik@localhost)
	by shell9.ba.best.com (8.9.3/8.9.2/best.sh) id MAA01376
	for ietf@ietf.org; Mon, 28 Feb 2000 12:58:47 -0800 (PST)
Date: Mon, 28 Feb 2000 12:58:47 -0800 (PST)
From: "James P. Salsman" <bovik@best.com>
Message-Id: <200002282058.MAA01376@shell9.ba.best.com>
To: ietf@ietf.org
Subject: thanks and IMS Question & Test Interop. announcement
X-Loop: ietf@ietf.org

My heartfelt thanks go out to the great number of IETF participants who
have endorsed the device upload proposal.  Sadly, my W3C sources tell me
that there is still insufficient support for the device upload proposal
within the W3C HTML Working Group.  The most substantial objection to
device upload is currently that it overlaps with future work planned for
"XForms."  I participated in the XForms effort for most of last year, and
it has left me very discouraged about the W3C process.  In November, the
Chair of the XForms group told me that it would take two years to
completion (although the published "HTML Roadmap" claims that it will be
ready around the end of the year.)  The complete redesign of forms that
they are undertaking will in my honest opinion serve no purposes that
aren't addressed by server-side software in widespread use today.  The
enormity of the effort, and my experiences with its leadership, leave me
with the impression that it could take several years to reach implementation.

In the mean time, non-wintel web browsers will still not be able to record
audio.  I have devoted my last three years to rectifying this situation,
and I ask that you continue your polite requests that the W3C HTML Working
Group formally Recommend the device upload proposal.

Now, along the subject of distance education, forms, and XML, I would like
to announce that the Instructional Management System (IMS) Project has
released their Question and Test Interoperability (Q&TI)  specification,
and has requested public review and comment:

  http://www.imsproject.org/question/index.html

Given that web-based distance education is growing quickly, these Q&TI
specifications will prove to be very useful and important for the
publication and exchange of, and thereby the development of a market in,
assessment content.  A number of companies have stated that they intend to
support assessment import and export based on these IMS standards.  IMS
managed to get research scientists from Educational Testing Service to
contribute to the requirements and the specification, so few should
question the pedigree of the spec.

As a practical matter, the spec covers almost every kind of assessment 
in modern web-based instructional systems:  multiple choice,
fill-in-the-blank, etc.  I hope as many companies as possible will
participate in the interoperability trials being conducted by the IMS
Project over the next three months.  I have no doubt that those 
companies adopting the Q&TI spec will benefit significantly from doing so.

My only concerns with the v.1 specifications is that the results 
processing directives do not yet provide a way to score the 
correctness of the results of a "Standard Order Objects" question,
although such questions can be represented as items -- see:
  http://www.imsproject.org/question/qtbest01.html#4.1.9
  http://www.imsproject.org/question/qtinfo01.html#A1.10

Also, the "other" condition method, "explicit undefined condition 
processing," is very unclear, being used as a catch-all without 
any given logical semantics.  There are numerous uses of "other"
in the examples that do provide some hints as to when it should 
return true, but it really needs to be defined.  I am sure that 
these problems will be addressed.  I hope that the "Standard Order 
Objects" questions allow partial-order answer keys so that such 
questions can easily include more than one correct answer without
enumerating all of them.

Cheers,
James Salsman



From owner-ietf-outbound  Mon Feb 28 17:50:27 2000
Received: by ietf.org (8.9.1a/8.9.1a) id RAA22774
	for ietf-outbound.10@ietf.org; Mon, 28 Feb 2000 17:50:03 -0500 (EST)
Received: from wclarke.netzit.com.br (bbking.netzit.com.br [200.210.86.4])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22582
	for <ietf@ietf.org>; Mon, 28 Feb 2000 17:40:48 -0500 (EST)
Received: from linuxbr.com (core.netzit.com.br [200.210.86.8] (may be forged))
	by wclarke.netzit.com.br (8.9.3/8.8.7) with ESMTP id TAA23531
	for <ietf@ietf.org>; Mon, 28 Feb 2000 19:55:19 -0300
Sender: root@wclarke.netzit.com.br
Message-ID: <38BB0B86.7E39BD14@linuxbr.com>
Date: Mon, 28 Feb 2000 20:57:58 -0300
From: Jean Paul Sartre <sartre@linuxbr.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.15pre9 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Internet SYN Flooding, spoofing attacks
References: <200002240220.TAA22428@calcite.rhyolite.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

Vernon Schryver wrote:

> Actually, those who understand the security problem of IP source routes
> knows something else.  IP source route options are not problems except to
> broken hosts.  It would be nice to think there are no longer such broken
> hosts on the net, but that is too much to expect.  In a reasonable world,
> we would expect anyone who cannot install non-broken software on their
> hosts to install filters against IP source routes where they will do the
> least damage, close to the broken hosts.

	That is one of the reasons I think cryptography between servers
(SSH/IPsec, for an example) and another technologies will be of great
use. Although I am studying many other standards and haven't yet a
consistent oppinion.

> However, in this world, the news about the irredeemable evil of all ICMP
> packets will join year-old news about the utter evil and uselessness of
> IP source routes and IEEE 802.3 collisions.  We'll be hearing about all
> three for the next 50 years.  (From my poking around, it appears that more
> than half of the Internet is now filtering all ICMP TTL-Exceeded, so the
> damage done to `traceroute -g`, `ping -R`, and other things by filtering
> IP source routes does not matter.)

	Unfortunately those other fifty percent do matter in this world where
people poke around exceedingly, as I have been experiencing here in
Brazil. I expect to be publishing security news in *Portuguese*, as the
brazilian community needs a public site regarding security..

> Assuming there is an algorithmic definition of "strangely high
> traffic from a unique site", how would a backbone and so Terabit/sec
> router log anything about it?  Is it easy to define, detect, and
> record state for streams if they are strangely high, and the reports
> about the difficulties of maintaining state for "multimedia" and
> similar buzzword streams do not apply?

	Well, there is not exactly a way to determine, only by probing
deterministic situations on packets written in the network, but it still
can be dangerous for innocent hosts. Only by writing a completely
trusting network and it is, unfortunately, impossible when the enormity
of the Internet is seen..

> Judging from their volume, the world needs a lot more documents about
> network or computer security that are more repetitions of trade rag rumors
> and security vendor marketing wishes than facts.  However, there's no
> reason for the IETF to compete with the current publishers of such works.

	Fortunately I will try to distribute certain informations about network
security. But I need some tips and I will be grateful if the IETF can
contribute. Sincerely, it would be very nice to see IETF names floating
by my side.

	As always, the most information you inject into the network, the better
it becomes..

	Cesar Suga <sartre@linuxbr.com>



From owner-ietf-outbound  Mon Feb 28 18:00:14 2000
Received: by ietf.org (8.9.1a/8.9.1a) id SAA23016
	for ietf-outbound.10@ietf.org; Mon, 28 Feb 2000 18:00:02 -0500 (EST)
Received: from wclarke.netzit.com.br (bbking.netzit.com.br [200.210.86.4])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22687
	for <ietf@ietf.org>; Mon, 28 Feb 2000 17:47:07 -0500 (EST)
Received: from linuxbr.com (core.netzit.com.br [200.210.86.8] (may be forged))
	by wclarke.netzit.com.br (8.9.3/8.8.7) with ESMTP id UAA23598;
	Mon, 28 Feb 2000 20:01:39 -0300
Sender: root@wclarke.netzit.com.br
Message-ID: <38BB0D02.D5ACC000@linuxbr.com>
Date: Mon, 28 Feb 2000 21:04:18 -0300
From: Jean Paul Sartre <sartre@linuxbr.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.15pre9 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
CC: "Parkinson, Jonathan" <Jonathan.Parkinson@compaq.com>
Subject: Re: Internet SYN Flooding, spoofing attacks
References: <71C4C55F198BD211B24F0000F842F15804B06DAA@reoexc6.reo.cpqcorp.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

"Parkinson, Jonathan" wrote:

> Well he's obviously devoted to this mailing list and hey, perhaps they have
> the same problems with the Internet on the other side !

	Well, I actually have that problems. Even working as a ghost, I am
making efforts to contribute to this really large network that is the
Internet. :)

> >       I am willing to write a document on the means of packet filtering and
> > how rules should work for different configurations and environments.
> 
> You can't, because you died in 1980.
> 
> <L.Wood@surrey.ac.uk>PGP<http://www.ee.surrey.ac.uk/Personal/L.Wood/>

	Actually I was born in 1980.

	Cesar Suga <sartre@linuxbr.com>



From owner-ietf-outbound  Tue Feb 29 07:21:53 2000
Received: by ietf.org (8.9.1a/8.9.1a) id HAA15530
	for ietf-outbound.10@ietf.org; Tue, 29 Feb 2000 07:20:02 -0500 (EST)
Received: from hera.cwi.nl (hera.cwi.nl [192.16.191.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15451
	for <ietf@ietf.org>; Tue, 29 Feb 2000 07:13:29 -0500 (EST)
Received: from pembo (pembo.cwi.nl [192.16.201.136]) by hera.cwi.nl with SMTP
	id NAA20546 for ; Tue, 29 Feb 2000 13:12:26 +0100 (MET)
Message-ID: <00fe01bf82ae$667f4380$88c910c0@cwi.nl>
From: "Steven Pemberton" <Steven.Pemberton@cwi.nl>
To: "James P. Salsman" <bovik@best.com>
Cc: <ietf@ietf.org>, <www-html@W3.ORG>, "HTML WG" <w3c-html-wg@W3.ORG>
References: <200002281755.JAA03783@shell9.ba.best.com>
Subject: Re: Device upload for all platforms -- the official HTML WG position
Date: Tue, 29 Feb 2000 13:13:31 +0100
Organization: CWI
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 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Content-Transfer-Encoding: 7bit
X-Loop: ietf@ietf.org
Content-Transfer-Encoding: 7bit

From: "James P. Salsman" <bovik@best.com>
> Thank you for your message.  I hope this one gets through.  Some
> of my email to W3C lists (e.g., www-forms) has not appeared in
> the archives.

Some W3C lists are not public, and intended for members of the group only.

> You state that there are comments regarding how the device upload
> proposal can be improved.  Please publish them, with my replies to
> them.  My understanding is that there are no unresolved issues.

They are already published, and there is no need to repeat them here.

> The device upload proposal -- http://www.bovik.org/device-upload.html
> is the epitome of device independence -- it has an extensible
> "device" attribute, after all.

My suspicion, James, since you continue to repeat this, is that you don't
understand the issues. Other replies to the www-html mailing list are only
repeating the comments we gave you in the early stages of this discussion,
so I suggest you read them carefully.

> You refer to the extensive re-design of forms using XML, which
> will require substantial replacement of both client and server
> software.  I do not wish my work to be associated with that
> effort.

Then you are out of luck, because that is the only place where work on forms
is happening within W3C.

> Why
> should people on non-wintel platforms wait that long for a way
> to record audio?

This non-wintel issue is a red herring, and has nothing to do with it.

> As you know, I participated in the XForms work,
> but I think it would be a mistake for me to resume participation.

I concur.

> Please accept the device upload submission from General Magic
> as a Working Draft, on Recommendation track.

It was submitted to us once, and we have replied. It would serve no purpose
to submit it again, even if you did represent General Magic.

Steven Pemberton
Chair W3C HTML WG



From owner-ietf-outbound  Tue Feb 29 14:10:46 2000
Received: by ietf.org (8.9.1a/8.9.1a) id OAA29710
	for ietf-outbound.10@ietf.org; Tue, 29 Feb 2000 14:10:02 -0500 (EST)
Received: from shell9.ba.best.com (root@shell9.ba.best.com [206.184.139.140])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29513
	for <ietf@ietf.org>; Tue, 29 Feb 2000 14:01:20 -0500 (EST)
Received: (from bovik@localhost)
	by shell9.ba.best.com (8.9.3/8.9.2/best.sh) id LAA21505;
	Tue, 29 Feb 2000 11:00:48 -0800 (PST)
Date: Tue, 29 Feb 2000 11:00:48 -0800 (PST)
From: "James P. Salsman" <bovik@best.com>
Message-Id: <200002291900.LAA21505@shell9.ba.best.com>
To: Steven.Pemberton@cwi.nl
Subject: Re: Device upload for all platforms -- the official HTML WG position
Cc: ietf@ietf.org, www-html@W3.ORG
In-Reply-To: <00fe01bf82ae$667f4380$88c910c0@cwi.nl>
X-Loop: ietf@ietf.org

> From: "Steven Pemberton" <Steven.Pemberton@cwi.nl>
> 
> > You state that there are comments regarding how the device upload
> > proposal can be improved.  Please publish them, with my replies to
> > them.  My understanding is that there are no unresolved issues.
> 
> They are already published, and there is no need to repeat them here.

Where are they published?  They are in the private W3C members-only 
archives, in the w3c-html-wg archives around October-November 1999, 
with nearly the same discussion in the private w3c-forms list earlier.

> This non-wintel issue is a red herring, and has nothing to do with it.

The fact remains that non-wintel web users are excluded from a range 
of very useful services involving device input and upload.  If the 
HTML Working Group had incorporated device upload into specifications
when they were first submitted as an internet-draft in 1997, after 
the implementation on the WebTV Plus, then all this would be a 
non-issue.  But as things stand, the W3C is contributing to wintel 
dominance, and disenfranchising Unix and Mac users.

Delaying device upload standardization to coincide with the XForms 
overhaul of HTML forms might be attractive to the HTML Working Group 
because it increases the chance that XForms will be accepted.  But 
is that an ethical justification for delaying a technology that 
enables a wide range of educational services?  

Tying device upload to XForms will certainly delay both, and could 
make it less likely that the device upload work will be implemented.  
If the XForms work is so important, then shouldn't it be able to 
stand on its own?

Cheers,
James



From owner-ietf-outbound  Tue Feb 29 15:10:29 2000
Received: by ietf.org (8.9.1a/8.9.1a) id PAA01206
	for ietf-outbound.10@ietf.org; Tue, 29 Feb 2000 15:10:02 -0500 (EST)
Received: from inetco.com (strauss.inetco.com [207.102.246.97])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01013
	for <ietf@ietf.org>; Tue, 29 Feb 2000 15:02:47 -0500 (EST)
Received: from dixon.inetco.com ([192.168.168.56]) by strauss.inetco.com with ESMTP id <115206>; Tue, 29 Feb 2000 12:03:43 -0800
Received: by dixon.inetco.com with Internet Mail Service (5.5.2448.0)
	id <FZCQHAGN>; Tue, 29 Feb 2000 12:03:54 -0800
Message-ID: <72AC01E5ABECD311A1BD0080C8E3273F06D826@dixon.inetco.com>
From: Cameron Young <Cameron_Young@inetco.com>
To: ietf@ietf.org
Subject: RE: Device upload for all platforms -- the official HTML WG posit
	ion
Date:  Tue, 29 Feb 2000 12:03:45 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain; charset="iso-8859-1"
X-Loop: ietf@ietf.org

OK, I'll bite.

I'm totally independent of this issue, but am curious how open the process
is.

Please point me to the published change requests so I can form my own
opinion.  You don't need to publish them in this forum.  You only need to
point me at them.  

Presumably, you can do that, I'll read them and find them reasonable, and
therefore sleep better tonight!  (Along with the help of a little Dimetapp
to offset the head cold I've picked up in this infernally wet climate in
Vancouver.)

Regards,
Cameron Young

-----Original Message-----
From: James P. Salsman [mailto:bovik@best.com]
Sent: Tuesday, February 29, 2000 11:01 AM
To: Steven.Pemberton@cwi.nl
Cc: ietf@ietf.org; www-html@w3.org
Subject: Re: Device upload for all platforms -- the official HTML WG
position


> From: "Steven Pemberton" <Steven.Pemberton@cwi.nl>
> 
> > You state that there are comments regarding how the device upload
> > proposal can be improved.  Please publish them, with my replies to
> > them.  My understanding is that there are no unresolved issues.
> 
> They are already published, and there is no need to repeat them here.

Where are they published?  They are in the private W3C members-only 
archives, in the w3c-html-wg archives around October-November 1999, 
with nearly the same discussion in the private w3c-forms list earlier.

> This non-wintel issue is a red herring, and has nothing to do with it.

The fact remains that non-wintel web users are excluded from a range 
of very useful services involving device input and upload.  If the 
HTML Working Group had incorporated device upload into specifications
when they were first submitted as an internet-draft in 1997, after 
the implementation on the WebTV Plus, then all this would be a 
non-issue.  But as things stand, the W3C is contributing to wintel 
dominance, and disenfranchising Unix and Mac users.

Delaying device upload standardization to coincide with the XForms 
overhaul of HTML forms might be attractive to the HTML Working Group 
because it increases the chance that XForms will be accepted.  But 
is that an ethical justification for delaying a technology that 
enables a wide range of educational services?  

Tying device upload to XForms will certainly delay both, and could 
make it less likely that the device upload work will be implemented.  
If the XForms work is so important, then shouldn't it be able to 
stand on its own?

Cheers,
James



From owner-ietf-outbound  Tue Feb 29 19:20:46 2000
Received: by ietf.org (8.9.1a/8.9.1a) id TAA05539
	for ietf-outbound.10@ietf.org; Tue, 29 Feb 2000 19:20:02 -0500 (EST)
Received: from dokka.maxware.no (dokka.maxware.no [195.139.236.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05470
	for <ietf@ietf.org>; Tue, 29 Feb 2000 19:15:08 -0500 (EST)
Received: (from hta@localhost)
	by dokka.maxware.no (8.9.3/8.9.3) id BAA17111
	for ietf@ietf.org; Wed, 1 Mar 2000 01:15:03 +0100
Date: Wed, 1 Mar 2000 01:15:03 +0100
From: Harald Tveit Alvestrand <hta@dokka.maxware.no>
Message-Id: <200003010015.BAA17111@dokka.maxware.no>
To: ietf@ietf.org
Subject: FAQ: The IETF+Censored list
X-Loop: ietf@ietf.org


                        The IETF+Censored mailing list
                                       
   At times, the IETF list is subject to debates that have little to do
   with the purposes for which the IETF list was created. Some people
   would appreciate a "quieter" forum for the relevant debates that take
   place, but the IETF's policy of openness has so far prevented the IETF
   from imposing any censorship policy on the IETF@ietf.org list.
   
   To give people an alternative, there is a list called
   "ietf+censored@alvestrand.no".
   
   This list is a sublist (that is, it gets the same messages as) the
   open IETF discussion list. However, this list will not forward all
   messages; in particular, the filters have been set so that persons and
   discussions that are, in the view of Harald Alvestrand, irrelevant to
   the IETF list are not forwarded.
   
   Because this filter is automated, the criteria include:
     * Well known troublemakers
     * Well known crosspostings
     * Subjects that have led to recent non-conclusive exchanges
     * Some ways to say "unsubscribe"
       
   To join the list, [1]send the word "subscribe" in the BODY of a
   message to ietf+censored-request@alvestrand.no (the URL here is an RFC
   2368 mailto URL that does the Right Thing).
   
   For fun, there is a special list for the rejected messages:
   ietf+censored-rejects@alvestrand.no - subscribe in the same fashion,
   by [2]mail to ietf+censored-rejects-request@alvestrand.no
   
   By public request, the current set of filters are listed at
   [3]http://www.alvestrand.no/cgi-bin/hta/ietf+censored-filters
   
   Some statistics on postings, which may be useful in getting a
   perspective on the effects of the filter, are at
   [4]posting-counts.html (started Oct 14, 1998).
   
   This page is http://www.alvestrand.no/ietf+censored.html, and is
   posted monthly in text form to ietf@ietf.org
     _________________________________________________________________
   
   Harald Tveit Alvestrand [5]< Harald@Alvestrand.no>

References

   1. mailto:ietf+censored-request@alvestrand.no?body=subscribe
   2. mailto:ietf+censored-rejects-request@alvestrand.no?body=subscribe
   3. http://www.alvestrand.no/cgi-bin/hta/ietf+censored-filters
   4. http://www.alvestrand.no/posting-counts.html
   5. mailto:harald@alvestrand.no



